On Jun 13, 2013, at 8:41 AM, Jaroslav Henner <jhen...@redhat.com> wrote:
> Hi, > > We wish to create some tool for automated preparation of stack for full > tempest run. We need it to be able to work with deployment that has been > prepared by Packstack [1]. I'm working on this already, and will have something usable for CI by Tuesday of next week at the latest. > Packstack can give as an output some "answer file", which is actually an ini > file. We can parse that file, take some other values as input, for example > images locations, ... and create a tempest.conf accordingly. > > The questions now are: > * Should this be a part of Tempest? > * Should this be a separate project? Maybe in the future, but not yet. > * Should this be a part of the Packstack? For now, yes. The immediate need is to allow Packstack to configure Tempest, so the work is best done there. > * What about other deploying tools - should that tool have several frond-ends? > * Does anybody have something already? > > Any comments? Each deployment mechanism (devstack/puppet/chef, and Packstack is just glue on puppet) needs to be able to perform base configuration to support Tempest. I'm not sure this would be best implemented in a separate tool, though, given that puppet and chef need to be able to natively manage of OpenStack resources and a separate tool would inevitably duplicate such functionality. m. > > [1] https://wiki.openstack.org/wiki/Packstack > > PS: As Attila Fazekas pointed, most things we can find dynamically from the > keystone/nova. True, but I don't quite like the idea to ssh to nova host to > get nova SQL password and tricks like that. > > Jaroslav Henner -- Mailing list: https://launchpad.net/~openstack-qa-team Post to : openstack-qa-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-qa-team More help : https://help.launchpad.net/ListHelp
