aeolusproject / aeolus-configure Goto Github PK

Configure is almost certainly broken with puppet 3.0. Eggs just now hit an issue with a gem installed puppet 3.0 on f17 where it looks like the command line switches have changed. Needs investigating.

These names are being changed across all Aeolus subprojects:

• Image Template -> Component Outline
• Deployable -> AppForm Blueprint
• Deployment -> AppForm
• Pool Family/Environment-> Cloud Environment
• Pool -> Resource Zone
• Provider -> Cloud Provider

All related materials (docs, wikis etc.) should be updated as well.

Really should do some basic sanity tests on user input

Region id should be: ap-southeast-2 but it is worth double-checking the docs.

Greetings,

I am a security researcher, who is looking for security smells in Puppet scripts.
I noticed instances of hard-coded passwords, which are against the best practices
recommended by Common Weakness Enumeration (CWE) [https://cwe.mitre.org/data/definitions/259.html] and also by other security practitioners.
I suggest use of hiera to mitigate this smell. Feedback is welcome.

Pull request: #31

Basically adding keys to the vsphere_configure file which will be used to create imagefactory's vsphere.json config file which I required when working with clusters within vsphere

instead of aeolus-configure -p ec2 something like '-p ec2-useast, ec2-euwest'

With master conductor/configure, provider account creation is broken because the curl under web_request is infinitely chasing a 302 redirect. I'm almost positive it's related to aeolusproject/conductor@0fd6e18

Using aeolus-configure-2.8.0-0.20121219130032git6fc3414.fc17

notice: /Stage[main]/Aeolus::Conductor/Postgres::User[aeolus]/Exec[create_aeolus_postgres_user]/returns: executed successfully
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Create::Db[create_aeolus_database]/Exec[create_rails_database]/returns: executed successfully
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: rake aborted!
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: cannot load such file -- costengine/billingmodel
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns:
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: Tasks: TOP => db:migrate => environment
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: (See full trace by running task with --trace)
notice: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: Using gem require instead of bundler
err: /Stage[main]/Aeolus::Conductor/Aeolus::Rails::Migrate::Db[migrate_aeolus_database]/Exec[migrate_rails_database]/returns: change from notrun to 0 failed: rake db:migrate returned 1 instead of one of [0] at /usr/share/aeolus-configure/modules/aeolus/manifests/rails/migrate/db.pp:6