RE: ApacheConEU Cloud Track CFP
by Hugh O. Brock
Yes we absolutely need to be at these kinds of things...
-hugh
-------- Original Message --------
From: Justin Clift <jclift(a)redhat.com>
Sent: Sun, 29/07/2012 05:08 AM
To: Francesco Vollero <fvollero(a)redhat.com>
CC: Aeolus <aeolus-devel(a)lists.fedorahosted.org>
Subject: Fwd: ApacheConEU Cloud Track CFP
Hey Francesco,
Do you have time to check this out, see if it's right for us?
+ Justin
Begin forwarded message:
> From: David Nalley <david(a)gnsa.us>
> Subject: ApacheConEU Cloud Track CFP
> Date: 28 July 2012 12:41:30 AM AEST
> To: dev(a)deltacloud.apache.org
> Reply-To: dev(a)deltacloud.apache.org
>
> Hi folks,
>
> Pardon my intrusion - just wanted to call attention to the fact that
> ApacheConEU has a dedicated Cloud track, and CFP is now open (and
> imminently closing as well).
> Please do consider submitting cloud talk proposals,
>
> Important dates:
>
> 3rd August, 2012: Talk proposals due.
> 19th August, 2012: Selected talks announced, speakers notified.
> 27th August, 2012: Conference schedule announced.
> 5th - 8th November, 2012: ApacheCon Europe.
>
> Where to submit:
> http://www.apachecon.eu/cfp/
>
> Thanks,
>
> --David
--
Aeolus Community Manager
http://www.aeolusproject.org
11 years, 9 months
[PATCH conductor] Fix failing oauth tests
by John Eckersberg
The URIs in the cassette look like:
http://example.com:5000/katello/api/organizations
But the tests were initializing the oauth client with
http://example.com:5000/api and then issuing a GET on
/katello/api/organizations; so ultimately:
http://example.com:5000/api/katello/api/organizations
This didn't match the cassette, so VCR would pass the connection on to
the real source (example.org:5000) and would eventually timeout.
---
src/spec/lib/oauth_client_spec.rb | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/spec/lib/oauth_client_spec.rb b/src/spec/lib/oauth_client_spec.rb
index 8fd7627..9ce522a 100644
--- a/src/spec/lib/oauth_client_spec.rb
+++ b/src/spec/lib/oauth_client_spec.rb
@@ -26,11 +26,11 @@ describe OAuthClient do
it "should get authenticated resource with custom header" do
# These are the proper configurations
- SETTINGS_CONFIG[:oauth]['http://example.com:5000/api'] = {
+ SETTINGS_CONFIG[:oauth]['http://example.com:5000'] = {
:consumer_key => 'valid',
:consumer_secret => 'good_secret'
}
- client = OAuthClient.new('http://example.com:5000/api')
+ client = OAuthClient.new('http://example.com:5000')
consumer = client.instance_variable_get('@consumer')
# We need to stub out sign! since it's otherwise unique on every request
consumer.stub('sign!') do |request, *args|
@@ -42,11 +42,11 @@ describe OAuthClient do
end
it "should return a 401 for invalid credentials" do
- SETTINGS_CONFIG[:oauth]['http://example.com:5000/api'] = {
+ SETTINGS_CONFIG[:oauth]['http://example.com:5000'] = {
:consumer_key => 'test',
:consumer_secret => 'failure'
}
- client = OAuthClient.new('http://example.com:5000/api')
+ client = OAuthClient.new('http://example.com:5000')
consumer = client.instance_variable_get('@consumer')
consumer.stub('sign!') do |request, *args|
request['authorization'] = 'OAuth oauth_consumer_key="test", oauth_nonce="zoT39JgdwI0fjqg9ZfJ2xN4QxyJyIghW7wWUHAxfY", oauth_signature="UFM87n9CcQXGsOUbHttPJs9NQOg%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1317068970", oauth_version="1.0"'
--
1.7.11.2
11 years, 9 months
[PATCH conductor 1/1] Add README.md, intended to help developers get up and running quickly Removed README.creole so there is only one README.
by cwolferh
---
README.creole | 18 -------------
README.md | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 79 insertions(+), 18 deletions(-)
delete mode 100644 README.creole
create mode 100644 README.md
diff --git a/README.creole b/README.creole
deleted file mode 100644
index 8c60c96..0000000
--- a/README.creole
+++ /dev/null
@@ -1,18 +0,0 @@
-= Aeolus Conductor =
-Aeolus Conductor is the web front-end to the [[https://www.aeolusproject.org/|Aeolus Project]], a software suite which aims to free users from cloud lock-in by providing a single, consistent set of tools to build and manage organized groups of virtual machines across clouds.
-
-== Installation ==
-Conductor has a number of dependencies. They are best outlined [[https://www.aeolusproject.org/get_it.html|here]] for now, which includes instructions for setting up and using our [[http://repos.fedorapeople.org/repos/aeolus/conductor/|yum repos]].
-
-== Developers ==
-Developers may find the [[https://www.aeolusproject.org/developers.html|Documentation for Developers]] page helpful.
-
-== Documentation ==
-* [[https://www.aeolusproject.org/about.html|Project Overview]], and a [[https://www.aeolusproject.org/projects.html|Project List]] with explanations.
-* [[https://www.aeolusproject.org/redmine/projects/aeolus/wiki/|Aeolus Project wiki]] (which could use a little cleanup)
-* [[https://www.aeolusproject.org/redmine/rb/master_backlogs/aeolus|Sprint backlog]]
-* [[https://www.aeolusproject.org/use_it.html|Using Aeolus Conductor]]
-
-== Contact ==
-Team members can be found in #aeolus on [[http://freenode.net/using_the_network.shtml|Freenode]]. We also make heavy use of the [[https://fedorahosted.org/mailman/listinfo/aeolus-devel|aeolus-devel@lists.fedorahosted.org]] mailing list. (You may also find the [[https://fedorahosted.org/pipermail/aeolus-devel/|aeolus-devel list archives]] helpful.) Don't be shy!
-
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..0f3d8e6
--- /dev/null
+++ b/README.md
@@ -0,0 +1,79 @@
+Aeolus Conductor
+================
+
+About
+-----
+Aeolus Conductor is a Ruby-based web application for cloud management. It
+is one component of the [Aeolus Project](http://www.aeolusproject.org/).
+For a chart of how Conductor fits with the other components, see:
+[Aeolus Components](https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Ae...
+
+Just Want To Try It Out?
+------------------------
+
+If you just want to try it out, start here:
+[Get It](https://www.aeolusproject.org/get_it.html)
+
+Otherwise, if you are a developer who wants to set up a development
+environment using the latest upstream code, this document is for you.
+
+Setting Up a Development Environment Using Bundler
+--------------------------------------------------
+
+All ruby gems that our project relies on are installed locally in a
+sandbox via bundler (gem and bundler must already be
+installed). Of course, if other system-wide gems are installed that
+is fine too-- "bundle install" will pull in the version-specific
+dependencies it needs locally.
+
+### System Prerequisites ###
+
+There are a few things that need to be done as root or a sudo-enabled
+user before we check out the Conductor repository and fire up the
+development server.
+
+We rely on the system to provide some development libraries, ruby,
+gem, bundler and a database. Specifically for RHEL 6 or Fedora Core
+16 or 17, we can grab these dependencies with:
+
+ yum install -y postgresql-server postgresql postgresql-devel ruby
+ ruby-devel ruby-rdoc git libxml2 libxml2-devel libxslt
+ libxslt-devel gcc gcc-c++
+
+ ^^assumes using postgres as our back-end database, but we could
+ just as well use sqlite or mysql.
+
+This set of requirements is not unusual and should look familiar to
+the experienced Ruby developer. Of course, installing these libraries
+for another flavor of OS should also be relatively straightforward.
+
+As previously mentioned, gem and bundler also should be available on
+your system but no other system-wide gems are necessary.
+
+If you happen to be running RHEL6 or Fedora 16/17, you can download
+the script conductor-dev-root-prep.sh from
+https://gist.github.com/3178181 which installs the needed system
+dependencies and sets up postgres.
+
+Otherwise, you will need to adapt the steps in the script for your
+particular OS.
+
+### Setting Up a Development Workspace ###
+
+With the above prerequisites met, setting up a development environment
+is as easy as cloning the repository, bundle-installing the needed
+gems locally, and running a few rake commands. See the OS-agnostic
+script conductor-dev-setup.sh from https://gist.github.com/3178181
+which does just that. This script should *not* be run as root, rather
+as the non-privileged user you are going to do development with.
+
+Happy coding!
+
+Contact
+-------
+
+IRC: Team members can be found in #aeolus on [Freenode](http://freenode.net/using_the_network.shtml)
+
+Mailing List: We also make heavy use of the mailing list
+[aeolus-devel@lists.fedorahosted.org](https://fedorahosted.org/mailman/listinfo/aeolus-devel).
+You may also find the [aeolus-devel list archives](https://fedorahosted.org/pipermail/aeolus-devel/) helpful.
--
1.7.1
11 years, 9 months
[PATCH configure] Modify config to support ldap-fluff integration
by Scott Seago
---
recipes/aeolus/manifests/conductor.pp | 5 +++++
recipes/aeolus/templates/conductor-settings.yml | 12 +++++-------
recipes/aeolus/templates/etc-ldap_fluff.yml | 11 +++++++++++
3 files changed, 21 insertions(+), 7 deletions(-)
create mode 100644 recipes/aeolus/templates/etc-ldap_fluff.yml
diff --git a/recipes/aeolus/manifests/conductor.pp b/recipes/aeolus/manifests/conductor.pp
index 96405c1..30882c3 100644
--- a/recipes/aeolus/manifests/conductor.pp
+++ b/recipes/aeolus/manifests/conductor.pp
@@ -28,6 +28,11 @@ class aeolus::conductor inherits aeolus {
require => Package['aeolus-conductor'],
mode => 640, owner => 'root', group => 'aeolus'}
+ file{"/etc/ldap_fluff.yml":
+ content => template("aeolus/etc-ldap_fluff.yml"),
+ require => Package['aeolus-conductor'],
+ mode => 640, owner => 'root', group => 'aeolus'}
+
file{"/usr/share/aeolus-conductor/config/initializers/secret_token.rb":
content => template("aeolus/secret_token.rb"),
require => Package['aeolus-conductor']}
diff --git a/recipes/aeolus/templates/conductor-settings.yml b/recipes/aeolus/templates/conductor-settings.yml
index dec51d3..91fc83b 100644
--- a/recipes/aeolus/templates/conductor-settings.yml
+++ b/recipes/aeolus/templates/conductor-settings.yml
@@ -3,13 +3,11 @@
:auth:
# supported strategies: database, ldap
:strategy: database
- :ldap:
- :host: localhost
- # '%s' expression in username_dn string will be replaced
- # by user's login
- # username_dn: "deltacloud\%s"
- :username_dn: uid=%s,ou=People,dc=my-domain,dc=com
- # :port: 389
+:groups:
+ # allows locally-managed groups
+ :enable_local: true
+ # allows ldap-managed groups
+ :enable_ldap: true
:iwhd:
:url: http://localhost:9090
:oauth:
diff --git a/recipes/aeolus/templates/etc-ldap_fluff.yml b/recipes/aeolus/templates/etc-ldap_fluff.yml
new file mode 100644
index 0000000..b7dd04a
--- /dev/null
+++ b/recipes/aeolus/templates/etc-ldap_fluff.yml
@@ -0,0 +1,11 @@
+---
+host: localhost
+port: 389
+encryption:
+base_dn: ou=People,dc=my-domain,dc=com
+group_base: ou=Groups,dc=my-domain,dc=com
+server_type: :posix
+service_user:
+service_pass:
+anon_queries: false
+ad_domain:
--
1.7.6.5
11 years, 9 months
[PATCH conductor 0/4] LDAP user group support (rev 1)
by Scott Seago
To use this you need to install the ldap_fluff gem (or rpm). Configure
doesn't yet generate the /etc/ldap_fluff.yml config file so yo need
to configure that manually for now. Here's what's in mine that I used for testing:
$ cat /etc/ldap_fluff.yml
---
host: localhost
port: 389
encryption:
base_dn: ou=People,dc=my-domain,dc=com
group_base: ou=Groups,dc=my-domain,dc=com
server_type: :posix
ad_domain:
service_user:
service_pass:
anon_queries: false
ldap_fluff repo I used: https://github.com/jsomara/ldap_fluff.git
The gem is also on github.
Once ldap auth is activated we'll automatically created ldap groups in
the conductor database that correspond to a user's memberships when that
user logs in. You can also "pre-load" ldap groups by creating ldap
groups via the User Groups UI. This does not confirm that the group is currently
in ldap, so you can actually create it before the group exists on the ldap server.
This is harmless -- it just means that nobody will actually belong to
the group yet.
11 years, 9 months
Sprint End Code Freeze approaches
by steve linabery
Hi Aeolus Developers,
End of Day, Monday 30-July, will be the code freeze for the end of the current Sprint.
Please coerce other devs to review your patches, and seek out OPP (other people's patches) to review.
Thanks!
Steve Linabery
11 years, 9 months
