ANNOUNCE: New Deltacloud Cloud Engine release
by Mike Orazi
All,
We are pleased to announce a new release of Deltacloud Cloud Engine.
This is an incremental release with some updates to the pre-beta release
made available in November. Some of the key updates include:
* Code refactoring and bug fixes for Provider views
* Code refactoring and bug fixes for Accounts views
* Code refactoring and bug fixes for Users views
* Support for mapping between Provider Hardware Profiles and Aeolus
Hardware Profiles
* Object Browser Initial Layout
Deltacloud Cloud Engine (formerly Deltacloud Aggregator) provides a web
UI in front of the Deltacloud API to allow for the management and
monitoring of cloud images across multiple providers.
If you are interested in taking Cloud Engine for a spin, installation
instructions [1] and a usage guide [2] are available to help you get
started.
Bug reports can be filed under the 'Cloud Engine' component at
bugzilla.redhat.com. There is a a project contributor [3] page that
will help you get involved in testing, documenting, reporting issues,
and contributing code patches to the project.
[1] http://www.deltacloud.org/download.html
[2] http://www.deltacloud.org/use.html
[3] http://www.deltacloud.org/contribute.html
Thanks,
Mike
13 years, 5 months
[patch aggregator] first impl. of adapter for condor backend.
by lmartinc＠redhat.com
git: [patch aggregator] first impl. of adapter for condor backend.
Hey guys,
probably this is going to be very controversial patch. This patch should allow people
to be able to use different job-backend if they chose to. I have refactored Condor backend
to be easily subtituteable via Adapter pattern. The implementation is just begining, but
if at least some of you will like it I will continue to provide at least one other job-backend (DelayedJobs).
The intention isn't to replace Condor, but make it optional and not hardcoded.
If there will be no reply or dicussion I will drop this patch.
Thanks for your feedback.
13 years, 5 months
updating the aggregator to work with rails 3 (draft 2)
by Mo Morsi
This is a rework of the original deltacloud rails 3 patch to
split changes into multiple patches and add further support and
compatability fixes to make the deltacloud aggregator rails 3
compliant.
Once again the app itself and the spec suite are fully working
but there is a bit more work that needs tbd to get the cucumber
feature suite functional.
Here are some specific points of interest about this patch:
- I tested it on Fedora 14, shipping with Ruby 1.8.7, and with Rails 3
installed via 'sudo gem install rails -v 3.0.1'
- All usptream gem communities seem to be on the ball concerning
the adoption of rails 3. I did have to make a few changes to
authlogic (2.1.6) to get rid of some annoying deprecation warnings,
but these don't break anything and we can patch the rpm as needed.
These changes are in /usr/lib/ruby/gems/1.8/gems/authlogic-2.1.6/
lib/authlogic/session/callbacks.rb (s/save_without_session_maintenance(false)/save_without_session_maintenance(:validate => false))
lib/authlogic/acts_as_authentic/password.rb (s/save(false)/save(:validate => false)
lib/authlogic/acts_as_authentic/logged_in_status.rb (s/named_scope/scope)
- I took care of everything else outstanding for rails 3 adoption
outlined in the first patch (validation methods, error messages,
views and logging updates, etc) and merged the patch into the new
deltacloud updates from the next HEAD. The only remaining item AFAIK
is to fix the features suite
- Rails 3 has many various changes:
* gem dependencies are now managed via Bundler and listed in
the Gemfile. Install them with 'bundle install' (as opposed
to 'rake gems:install' as instructed in the install docs).
* routes.rb has been overhauled, and I had to make some
changes in the app to bring things in line
* all the scripts/ have been replaced with scripts/rails
* the '-' operator is no longer supported in haml,
rather use '=' for all ruby code
* many deprecations, api updates, and more
Have at it!
-Mo
13 years, 5 months
[PATCH aggregator] Integration of rack-restful_submit
by lmartinc＠redhat.com
As we already started to work on our new UI with new organizations of
our controllers I thought that we could also get better when it comes to
writing controllers RESTful way.
To fully accomplish RESTful architecture in our application where we
cannot rely on Javascript I have created project called rack-restful_submit
that actually emulates RESTful behaviour or our forms without Javascript
and with multiple submit buttons inside one form.
This patch is first integration patch of this work.
You can read more about it and look at the code here:
https://github.com/martincik/rack-restful_submit
It this email and everything else isn't enough for you to understand
let me know and I can write/explain more.
Thank you for review and happy RESTfulying. ;)
-- Ladislav
13 years, 5 months
Website update
by Chris Lalancette
Hey Tomas, others,
I just updated the deltacloud.org website (both the git repository,
and the live site). Note that I merged "next" onto master, pushed, and then
put my changes directly on master. Might I suggest that we stop using the
"next" branch for docs/, and instead always commit everything on master? I
know that is a change from what we have done before, but it just doesn't make
too much sense (to me) to have the split between master and next.
Thanks,
--
Chris Lalancette
13 years, 5 months
[PATCH aeolus] Switch between the layouts without needing JS
by Tomas Sedovic
From: Tomas Sedovic <tsedovic(a)redhat.com>
Going to:
http://example.com/set_layout?layout=newui
sets the new UI layout, going here:
http://example.com/set_layout?layout=aggregator
sets the old one.
---
src/app/controllers/application_controller.rb | 7 +++++++
src/config/routes.rb | 2 ++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/src/app/controllers/application_controller.rb b/src/app/controllers/application_controller.rb
index 7d0e931..fd1a92c 100644
--- a/src/app/controllers/application_controller.rb
+++ b/src/app/controllers/application_controller.rb
@@ -49,6 +49,13 @@ class ApplicationController < ActionController::Base
return @layout
end
+ def set_layout
+ if not params[:layout].blank?
+ cookies[:layout] = params[:layout]
+ end
+ render :text => "Current layout is: '#{cookies[:layout]}'"
+ end
+
def section_id
'generic'
end
diff --git a/src/config/routes.rb b/src/config/routes.rb
index f4e4bb8..c1964ec 100644
--- a/src/config/routes.rb
+++ b/src/config/routes.rb
@@ -40,6 +40,8 @@ ActionController::Routing::Routes.draw do |map|
r.resources :assemblies, :deployables, :templates
end
+ map.connect '/set_layout', :controller => 'application', :action => 'set_layout'
+
map.namespace 'admin' do |r|
r.resources :hardware_profiles, :pool_families, :providers, :provider_accounts, :realms, :roles, :settings, :users
end
--
1.7.3.3
13 years, 5 months
How To Write The New UI Code
by Tomas Sedovic
All,
I'm attaching a patch that partially implements the Pools page in the new UI.
While it's not done yet, you can look at the code to see how to code other
other pages for the new UI.
Here are some pointers:
1. We're using namespaced routes for the controllers/views.
The controllers are located in:
aeolus/src/app/controllers/$NAMESPACE/
The same thing for views.
The URLs look like this: http://example.com/image_factory/assemblies
The layout for the new UI is at: aeolus/src/views/layouts/newui.haml
2. Most of the time you will be using the "list" and the
"details" panes. You set their content using `content_for :list` and
`content_for :details` in the views.
When you don't specify the "details" content, the list will take up all the
vertical space.
3. The controllers use your typical restful/crud actions: index, show, new,
create, destroy, update. And they use the proper HTTP methods (PUT for
`update`, DELETE for destroy, etc.) -- you can run `rake routes` to see the
URLs, HTTP methods and the path helpers.
For nonstandard stuff feel free to add new actions of course.
4. Form submit:
When you have a form with GET or POST method, a single submit button and a
static form action URL, it's all good.
It gets trickier when you have a form full of checkboxes (e.g. the list pane)
and you want to do batch actions on them. Especially since it must work
without JavaScript and with non-GET or POST methods.
For that you can use the new `restful_submit_tag` helper that Ladislav cooked
up. You use it like this:
= restful_submit_tag "Delete", "delete", resources_pool((a)pool.id), 'DELETE'
(button text, button name, form action URL, HTTP method)
It will create some hidden fields that our app will translate to proper HTTP
methods.
Note that you can use multiple submit buttons with different form URLs. This
allows you to put "New Pool" and "Delete Selected Pools" along with "Edit
Selected Pool" buttons all into the same form and it'll all work.
If you're confused, I recomend that you look at the the attached patch. It
shows the stuff described here in action.
Feel free to ask me questions on IRC or this list.
Thomas
13 years, 5 months
[PATCH aggregator] Integration of rack-restful_submit
by lmartinc＠redhat.com
This patch isn't for review but just for people working on new UI in
this sprint (p2-s2). This patch adds:
1) Possibility to pass options to submit_tag()
2) RSpec tests for restful_submit_tag() helper
-- Ladislav
13 years, 5 months
[PATCH aggregator] Stubbed template upload method
by Jan Provazník
From: Jan Provaznik <jprovazn(a)redhat.com>
We need to stub template uploading because it's called when we are importing an image.
---
src/spec/models/image_spec.rb | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/src/spec/models/image_spec.rb b/src/spec/models/image_spec.rb
index 9f2d133..1e1e699 100644
--- a/src/spec/models/image_spec.rb
+++ b/src/spec/models/image_spec.rb
@@ -59,6 +59,12 @@ describe Image do
account.stub!(:connect).and_return(client)
account.stub!(:valid_credentials?).and_return(true)
account.save!
+ Template.stub!(:new).and_return do |*args|
+ tpl = Template.proxied_by_rspec__new(*args)
+ tpl.should_receive(:upload).and_return(true)
+ tpl
+ end
+
lambda do
lambda do
--
1.7.2.3
13 years, 5 months
Image import
by Jan Provazník
Sending again patchset extended with template uploading.
13 years, 5 months
