I've pushed a change to how the aeolus-configure behaves by default.
Executing "aeolus-configure" without a -p option uses the default
profile. The default profile no longer adds providers to conductor. It
only starts up components, creates the site administrator account,
creates the aeolus bucket, and adds a default hardware profile.
Out of the box, four provider profiles are available: mock, ec2, rhevm,
and vsphere. Each of these are a superset of the default profile.
To configure a particular provider, use -p with the name of the
profile. For example, "aeolus-configure -p ec2" configures ec2. Some
profiles like rhevm and vsphere have additional parameters that may need
to be changed to suit your environment. The changes can be made in a
file named /etc/aeolus-configure/nodes/<profile name>.
You may also specify multiple profiles in a single command.
For example, "aeolus-configure -p ec2,rhevm,vsphere,mock" will execute
all four profiles and add all four providers to conductor.
This is equivalent to "aeolus-configure -p ec2; aeolus-configure -p
rhevm; aeolus-configure -p vsphere; aeolus-configure -p mock".
Having the default profile not configure ec2 by default is biggest
change. If this feels odd, we can switch the default profile to be ec2.
- Richard
Show replies by date