search

aeolusproject / conductor

Aeolus Conductor
http://www.aeolusproject.org/
Apache License 2.0
32 stars 27 forks source link

Tim integration - move /etc/imagefactory/(rhevm|vsphere).json under conductor #328

Open jprovaznik opened 11 years ago

jprovaznik commented 11 years ago

New imagefactory doesn't read /etc/imagefactory/(rhevm|vsphere).json files itself but requires params in these files to be sent in build/push requests. So now the files are used by Conductor to load params -> it would be better to move the files into some conductor dir.

sseago commented 11 years ago

On 01/11/2013 05:03 AM, Jan Provaznik wrote:

New imagefactory doesn't read /etc/imagefactory/(rhevm|vsphere).json files itself but requires params in these files to be sent in build/push requests. So now the files are used by Conductor to load params -> it would be better to move the files into some conductor dir.

— Reply to this email directly or view it on GitHub https://github.com/aeolusproject/conductor/issues/328.

Should we take those params and build them into the provider/provider type objects? The fact that new providers are configured in two different places (factory json file+conductor UI/API) is a long-standing issue that we initially proposed fixing over a year ago, but it's always been on the backlog. Now might be the time to resolve this.

Scott

morazi commented 11 years ago

+1 -- now seems like a reasonable time to do the needful to remove these files. When the work is complete, please close the related issue in bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=882986