aeolus-configure parameters - Was: Aeolus Community Assessment

Mo Morsi mmorsi at redhat.com
Fri Jun 8 07:12:28 UTC 2012


On 06/07/2012 08:47 PM, Jason Guiditta wrote:
> On 07/06/12 05:44 +1000, Justin Clift wrote:
>> On 07/06/2012, at 4:42 AM, Matt Wagner wrote:
>> <snip>
>>> I think aeolus-configure is really slick and makes things 100 times
>>> easier than it used to be, but "edit this yaml file based on what this
>>> wiki page suggests" is _still_ not very intuitive for RHEV and vSphere
>>> configs. I'm not sure just yet on how we can solve that, but it's
>>> definitely something deserving some attention.
>>
>> Other ways we could get info from the user:
>>
> <snip>
>
> Justin, I like the direction of these ideas, and I would further say,
> maybe now is the time to get rid of these 'files on system' as part of
> this 'improve ease of use' effort.  Conductor already stores account
> details, why not also all these kinds of details about a given
> provider?  If done properly, it could keep in the modular theme, be
> fully accessible via api, and save us munging files on the system, or
> expecting users to do the same.
>
> -j

-1

I still think the idea of being able to configure cloud resources and
instances using config files a good idea. It doesn't matter what is
doing the configuration and how it gets propagated to the conductor db,
so long as the admin can simply configure things from a single config
file (as with many other popular services).

In any case this is a working feature at the moment and doesn't detract
anything, so I don't think it should be removed. Plus the original
concern can just be alleviated with additional documentation on the
website pertaining to valid options that can be set in the config files.

  -Mo



More information about the aeolus-devel mailing list