[PATCH conductor] Point Gemfile at git repo to get image building working upstream.
by Jason Guiditta
This is a (likely) temporary change to point at master of aeolus-image
on github. It is likely we can set it back to a version once we do
another bugfix release of aeolus-image to rubygems.org, should we
chosse to flip it back. This patch should have no impact on setups
running from system ruby+rpms, just upstream+bundle dependencies.
---
src/Gemfile | 2 +-
src/Gemfile.lock | 19 ++++++++++++-------
2 files changed, 13 insertions(+), 8 deletions(-)
diff --git a/src/Gemfile b/src/Gemfile
index 761a653..bc13c46 100644
--- a/src/Gemfile
+++ b/src/Gemfile
@@ -17,7 +17,7 @@ gem 'thin'
gem 'json'
gem 'rails_warden'
gem 'ruby-net-ldap', :require => 'net/ldap'
-gem 'aeolus-image', '>= 0.4.0', :require => 'aeolus_image'
+gem 'aeolus-image', :git => "git://github.com/aeolusproject/aeolus-image-rubygem", :require => 'aeolus_image' #'>= 0.4.0',
gem 'oauth'
gem 'ldap_fluff'
gem 'compass'
diff --git a/src/Gemfile.lock b/src/Gemfile.lock
index 2beef47..0009d64 100644
--- a/src/Gemfile.lock
+++ b/src/Gemfile.lock
@@ -1,3 +1,13 @@
+GIT
+ remote: git://github.com/aeolusproject/aeolus-image-rubygem
+ revision: 4bffe3f60ce36a9815b479b6381544cf030d912a
+ specs:
+ aeolus-image (0.6.0)
+ activeresource
+ nokogiri
+ oauth (= 0.4.4)
+ rest-client
+
GEM
remote: http://rubygems.org/
specs:
@@ -29,11 +39,6 @@ GEM
i18n (~> 0.6)
multi_json (~> 1.0)
addressable (2.2.8)
- aeolus-image (0.5.1)
- activeresource
- nokogiri
- oauth
- rest-client
arel (3.0.2)
builder (3.0.0)
capybara (1.1.2)
@@ -103,7 +108,7 @@ GEM
mustache (0.99.4)
net-ldap (0.3.1)
nokogiri (1.5.2)
- oauth (0.4.6)
+ oauth (0.4.4)
paranoia (1.1.0)
activerecord (>= 3.0.0)
pg (0.13.2)
@@ -193,7 +198,7 @@ PLATFORMS
ruby
DEPENDENCIES
- aeolus-image (>= 0.4.0)
+ aeolus-image!
capybara
compass
compass-960-plugin
--
1.7.7.6
11 years, 7 months
Aeolus Presentation:Report
by Nitesh Narayan
Hi,
It was yet another talk on aeolus which I took , although this time it was in my class . There was a mixed experienced crowd some of them were already aware about the cloud management applications and for some of them it was a totally new experience . I had taken the template and few slides from David Lutterkort presentation and it helped me a lot .
I started the session by explaing a brief about cloud computing and then went on with the problems a user face while managing different vendors clouds . In continuation I had also explained the benefits of using aeolus .
Next was the architecture and the components aeolus use , so I told them about that in between I had also explained them about the Deltacloud and REST API and the benefits of using the same .
While concluding I had given them a breif about how they can contribute and communicate to the community if they like to at some point of time and told them about the IRC channel and the ML we have .
Regards
Nitesh Narayan Lal
Aeolus Contributor
11 years, 8 months
(no subject)
by Jason Guiditta
Once we get these pushed to master, we can then point conductor at
:git version until we get another bugfix release of aeolus-image out.
This should fix at least a couple more tests due to the fixes jstransk
recently added to aeolus-image.
-j
11 years, 8 months
Reminder: Common error messages wiki page
by Matt Wagner
Hi folks,
Since I had forgotten about it until it recently helped someone, I
thought I'd remind people of this old wiki page:
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Common_Error_M...
The idea is to list errors people run into and the fix. It's fairly
broad, from errors starting Image Warehouse to Factory errors with
plenty in-between.
Hopefully our in-app errors are specific enough, but the idea here is to
list all the configuration errors, common failures, and even problems
caused by user error that a user or fellow developer might run into. The
idea is to have something more concrete in those, "Oh, I remember
someone else hitting that same error last week..." situations. So please
think about updating it as you go along and run into errors that others
could hit.
-- Matt
11 years, 8 months
[PATCH conductor] BZ 804697 - User status: Inactive option does not function
by jzigmund＠redhat.com
From: Jozef Zigmund <jzigmund(a)redhat.com>
User status radio buttons were removed, because it was fake
(the attribute didn't exist in User model).
https://bugzilla.redhat.com/show_bug.cgi?id=804697
---
src/app/views/users/_form.html.haml | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/src/app/views/users/_form.html.haml b/src/app/views/users/_form.html.haml
index 9ac1a80..3185ab0 100644
--- a/src/app/views/users/_form.html.haml
+++ b/src/app/views/users/_form.html.haml
@@ -36,17 +36,6 @@
.input
= quota_form.text_field :maximum_running_instances
- %fieldset
- %legend=t'users.form.user_status'
- .field
- %ul.radio-group
- %li
- = label_tag "user_status_active", t("users.form.user_status_active")
- = radio_button_tag "user_status", t("users.form.user_status_active"), true
- %li
- = label_tag "user_status_inactive", t("users.form.user_status_inactive")
- = radio_button_tag "user_status", t("users.form.user_status_inactive"), false, :disabled => true
-
%fieldset.options
= form.submit "#{t'users.form.save_user'}", :class => "submit button pill"
--
1.7.11.4
11 years, 8 months
[PATCH aeolus-image 0/4 v3] Enable development with Bundler
by Jiří Stránský
Appending the OAuth dependency version fix to my previous Bundler patch.
With this, aeolus-image specs are green both upstream with Bundler and on F16
gems.
Tested building mock images with Conductor both upstream and on F16.
11 years, 8 months
Re: Aeolus Presentation:Report
by Nitesh Narayan
Hi,
Its all righty :) . Although I have another talk probably in the mid September still the dates has to be fixed .
The thing what I concluded from the talk from people response was that they would like to have some aeolus chrome extensions and firefox addons doing some small taks such as starting and stop instances etc .
I had worked on chrome extensions earlier so I can look into that but I am not sure when I can start with that as its been quite a busy schedule for me right now :P .
Print only if its necessary
Regards
Nitesh Narayan Lal
Contributor
11 years, 8 months
CloudForms UI Meetup Week of 8/20 Trip Report
by Jason Rist
The meetings last week had the purpose of some representatives from each
team getting together, meeting and getting to know one another, going
through both apps to discover what is working well and not working in
terms of converging on a common UI, and coming up with a somewhat
comprehensive list of the things that need to be done for not only 1.1
but also forward in the future and v.Next.
As many of you know, we have developed a shared UI infrastructure
designed for sharing common elements (header, footer, colors, fonts, js
and jquery plugins, and moving forward, forms, buttons, and common
IxD/UI patterns) called Converge-UI. Much of the week was spent making
sure that the right elements are situated within Converge-UI as well as
planning for future versions. A little about ConvergeUI:
The goal is to build and keep all common UI look/feel/interactions in
ConvergeUI and to generate reference implementations through ConvergeUI
Example application. This is currently a joint effort between Condcutor
and Katello teams and anyone who wishes to join may as it is an open
source project.
Planning and discussions now through Github Issues:
https://github.com/Katello/converge-ui/issues?milestone=&page=1&state=open
<https://github.com/Katello/converge-ui/issues?milestone=&page=1&state=open>
New #freenode channel for discussion: #converge-ui , existing internal
#cloudforms-ui geared toward specific brand and productization discussions.
Mailing list for discussions as well for those interested:
http://post-office.corp.redhat.com/mailman/listinfo/converge-ui-devel
Our agenda was the following:
M -
Introductions
Aeolus Conductor Walk-through
Katello Walk-through
Brian Stein CloudForms Vision
T -
More app walkthroughs, hacking on both apps for bug fixes and discussion
Extensive etherpadding
Product Management's CloudForms Vision
W -
More app walkthroughs, hacking on both apps for bug fixes and discussion
Extensive etherpadding
Matt Hicks from OpenShift team presented OpenShift's architecture and UI
infrastructure as well as going forward plans
Th -
More app walkthroughs, hacking on both apps for bug fixes and discussion
Extensive etherpadding
RDVO presentation on CloudForms UI plans, with the UX team and Product
Management
F -
Summarizing the week
Re-reading and prioritizing etherpad
Hacking and goodbyes
I'll have to apologize in advance in mentioning that Monday was a bit of
a blur - long story, (passenger medical emergency on the flight the day
before), hopefully Eric or some of the Conductor can fill it in a bit
better. Aside from the walk-throughs and hacking, Brian Stein came in
and gave an overview of how he thinks the two apps (Conductor and
Katello) should work together and why he wanted us all to get together
for the week. My take is that there are still a few things we can do on
both sides for v.Next that will make our apps work more nicely together
and it sounded like most of that was planned out.
On Tuesday, Product Management came and gave us a run down of what they
really want to see in v.Next:
• Foreman Abstraction
• Puppet Content Flow through the system
• Environment Lifecycle
∘ Content Versioning
∘ System Lifecycle
My understanding is that we have some of that in progress and we'll be
working toward that up to 1.1 and beyond for a possible Spring 2013 next
release. They also outlined a process improvement that they are working
on, which involves come up with Use Cases, working to build a Model of
those Use Cases, and then working with UXD (possibly including the
external group, RDVO) to build Wireframes and possibly even Concept type
work. Sounds good to me! Bring on the solid requirements!
On Wednesday, Matt Hicks went over OpenShift and did a
"developer-centric" presentation that we all felt was very fruitful.
The team that is putting together OpenShift is very talented. They sent
along the wiki for the project,
https://engineering.redhat.com/trac/Libra/ - take a look if you're
interested. I'm sure the team would talk to you about what they're
doing if you want to learn from them.
Thursday the external company RDVO came in and gave us a bit more detail
into the process that Product Management discussed on Tuesday. I've
put in a query with the partner from RDVO who worked with us to get
their docs which they mentioned that they were going to share.
That's about it! It was a great week overall, and we have a ton of stuff
that we now need to do for not only 1.1 but also v.Next. I think the
week was very fruitful and the overall experience was awesome.
Let me know if you have any questions and I'll try to fill them in as
best I can, hopefully with a bit of help from the other guys that were
there.
-Jason
--
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist
11 years, 8 months
