[PATCH conductor] Fix spec file to not reference a missing file
by Pádraig Brady
Following on from commit d6b942de 2011-11-01,
Remove the reference to the no longer present style sheet.
---
aeolus-conductor.spec.in | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/aeolus-conductor.spec.in b/aeolus-conductor.spec.in
index 6bdcd9c..ca386fc 100644
--- a/aeolus-conductor.spec.in
+++ b/aeolus-conductor.spec.in
@@ -178,7 +178,6 @@ done
# precompile stylesheets
%{__mkdir} %{buildroot}%{app_root}/public/stylesheets/compiled
-sass --style compact ./src/app/stylesheets/application.scss %{buildroot}%{app_root}/public/stylesheets/compiled/application.css
sass --style compact ./src/app/stylesheets/custom.scss %{buildroot}%{app_root}/public/stylesheets/compiled/custom.css
sass --style compact ./src/app/stylesheets/layout.scss %{buildroot}%{app_root}/public/stylesheets/compiled/layout.css
sass --style compact ./src/app/stylesheets/login.scss %{buildroot}%{app_root}/public/stylesheets/compiled/login.css
--
1.7.6.4
12 years, 5 months
Error when use template show in aeolus site
by Julio Alberto Carrillo
Hi,
I have problems when use template in aeolus site, "install.img" not found
and i can't advance in create image.
how resolv this?
Thanks for regards
Julio
12 years, 5 months
Deployable XML Changes
by Greg Blomquist
Hey gang,
Up until this point, the deployable XML format has allowed for
configuration scripts to be expressed as URLs that get downloaded by the
Config Server during the instance launch process.
This works great as long as the Config Server can see the scripts that
it's downloading during the launch process. If it can't see the scripts
(e.g., firewall issues, etc.), then the scripts cannot be downloaded by
Config Server and the booting instance cannot get its configs.
To fix this issue, I'm proposing (at least for release 1.0, before we
can model deployables out in active record) that the configuration file
contents be stored in-line in the deployable XML file.
What changes does this mean?
The biggest risk to Conductor this imposes is that the data stored in
the deployments table could become unwieldy since it's storing not only
XML contents, but configuration scripts (in-line with the XML), as well.
This also means that the user is responsible for constructing an XML
file that contains the configuration script contents in-line (inside
cdata tags).
The technical changes that this boils down to are:
* The relaxNG file specifying the deployableXML file format changes to
disallow URL references to configuration scripts and start enforcing
file contents for configuration scripts
* The Config Server stops attempting to download the configuration
scripts and instead pull the contents directly from the data POSTed by
Conductor.
All other interactions remain the same.
These changes allow the user to not have to put the [most likely]
sensitive configuration scripts in a [most likely] public location in
order to be downloaded by the Config Server at launch time.
There are several other follow on changes that could be implemented.
But, largely I see any additional changes as time spent doing something
other than focusing on the problem of designing and building a solution
for constructing Deployables from within Conductor.
Thoughts? Rotten tomatoes?
Thanks!
---
Greg
12 years, 5 months
[PATCH configure] 2663 - write iwhd oauth config to users.js config instead of init script
by Mo Morsi
---
recipes/aeolus/manifests/iwhd.pp | 8 +++++++-
recipes/aeolus/templates/iwhd-users.js | 1 +
recipes/aeolus/templates/iwhd.init | 2 +-
3 files changed, 9 insertions(+), 2 deletions(-)
create mode 100644 recipes/aeolus/templates/iwhd-users.js
diff --git a/recipes/aeolus/manifests/iwhd.pp b/recipes/aeolus/manifests/iwhd.pp
index de0209b..2ceb03e 100644
--- a/recipes/aeolus/manifests/iwhd.pp
+++ b/recipes/aeolus/manifests/iwhd.pp
@@ -35,6 +35,11 @@ class aeolus::iwhd inherits aeolus {
mode => 755,
require => Package['iwhd'] }
+ file {"/etc/iwhd/users.js":
+ content => template("aeolus/iwhd-users.js"),
+ mode => 755,
+ require => Package['iwhd'] }
+
service { 'mongod':
ensure => 'running',
enable => true,
@@ -46,7 +51,8 @@ class aeolus::iwhd inherits aeolus {
hasstatus => true,
require => [Service[mongod],
File['/var/lib/iwhd',
- '/etc/init.d/iwhd']]}
+ '/etc/init.d/iwhd',
+ '/etc/iwhd/users.js']]}
# XXX ugly hack but iwhd might take some time to come up
exec{"iwhd_startup_pause":
diff --git a/recipes/aeolus/templates/iwhd-users.js b/recipes/aeolus/templates/iwhd-users.js
new file mode 100644
index 0000000..236a22e
--- /dev/null
+++ b/recipes/aeolus/templates/iwhd-users.js
@@ -0,0 +1 @@
+[ { "name":"<%= iwhd_oauth_user %>", "secret":"<%= iwhd_oauth_password %>" } ]
diff --git a/recipes/aeolus/templates/iwhd.init b/recipes/aeolus/templates/iwhd.init
index 12617a0..1247801 100755
--- a/recipes/aeolus/templates/iwhd.init
+++ b/recipes/aeolus/templates/iwhd.init
@@ -83,7 +83,7 @@ start() {
echo
printf %s $"Starting $SERVICE daemon: "
- $PROCESS -c "$CONFIG_JS" $IWHD_ARGS -o -U <%= iwhd_oauth_user %>:<%= iwhd_oauth_password %>&
+ $PROCESS -c "$CONFIG_JS" $IWHD_ARGS -o -u /etc/iwhd/users.js &
pid=$!
RETVAL=$?
if test $RETVAL = 0; then
--
1.7.6.4
12 years, 5 months
[PATCH aeolus-image-rubygem] adding icicle support
by Dan Radez
adds capabilities to pull the description and package list from the icicle
irb> i = Aeolus::Image::Warehouse::Icicle.first
=> #<Aeolus::Image::Warehouse::Icicle:0x7fef78533fa8 @object_type="icicle", @uuid="5029e280-9ec9-48e6-8919-9383d171b075">
irb> i.description
=> "rhel 6.1 x86_64 template with rhev v3.0 agent pkg"
irb> i.packages.find_all { |node| node =~ /zlib(.*)/ }
=> ["zlib-1.2.3-25.el6.x86_64"]
Radez
12 years, 5 months
[PATCH] Remove Red Hat branding
by Tomas Sedovic
As discussed earlier, we should remove the images trademarked by Red Hat.
There were two offending png files.
I also noticed that there are two stylesheet files that we don't use anymore
so I've deleted them as well to prevent confusion.
And while I were at it, I updated the footer (which used to contain the Red Hat
logo) to look more like what Ken has in his latest designs (which were sent
yesterday).
12 years, 5 months
Release Addendum: Aeolus 0.5.0 ready to roll
by steve linabery
Hello, aeolus community!
I'd like to expand on the previous aeolus 0.5.0 release announcement[0] to highlight some of the enhancements added since 0.4.0, as well as point community members to significant issues that were not deemed worthy of stopping the release (but should be noted nonetheless).
First, the highlights. As before, aeolus development effort is tracked in Aeolus' Redmine instance[1]. The stories that we knocked out for the 0.5.0 release are detailed in this query:
https://www.aeolusproject.org/redmine/projects/aeolus/issues?query_id=83
Particularly noteworthy are:
* submission of aeolus project for inclusion in Fedora 16 distro
* oauth integration
* aeolus-image cli tooling enhanced to use a REST api from conductor
* improved views by pool of catalogs and catalog entries
A complete list of open issues can be viewed in Red Hat Bugzilla[2], but one is especially important to mention. In order to get an ip address in aeolus when using rhevm guests, please see:
https://bugzilla.redhat.com/show_bug.cgi?id=725672
Aeolus is not yet feature complete, but I encourage everyone to test out the latest 0.5.0 release. As always, installation and use documentation can be found at the project website:
http://aeolusproject.org/get_it.html.
Please note that while there is still quite a bit of development underway APIs may be in flux so don't trust it with your production data just yet.
New (and experienced!) aeolus users may find this documentation page[3] useful in learning the aeolus way to build, push, and launch instances. Highly recommended reading! As with all aeolus components, your suggestions to improve our documentation are very welcome.
And again, many thanks to the many contributors who made this release possible. Let's get those clouds moving!
Cheers,
Steve Linabery
Software Engineer, Red Hat, Inc.
[0] https://fedorahosted.org/pipermail/aeolus-devel/2011-October/006218.html
[1] https://www.aeolusproject.org/redmine/
[2] http://goo.gl/nrUUF
[3] https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Launching_Inst...
12 years, 5 months
[PATCH conductor 0/1] Update RPM spec with aeolus-image version
by Matt Wagner
Since Conductor will fail to start if rubygem-aeolus-image is older than 0.1.0-4, the RPM spec should indicate that version requirement.
This updates the source aeolus-conductor.spec.in. As far as I can tell, autoconf will take care of versioning so there's no revision for me to bump. But I'm really kind of clueless about how autoconf works, so I'm hoping someone will review this patch before I commit it, even though it's trivial.
-- Matt
12 years, 5 months