Description of problem: There has been some discussion around the provision_demo option and it's impact on the successful execution of packstack. Packstack can successfully deploy an openstack environment but fail while setting up a demo environment which leaves the installer in a awkward state. The primary goal of packstack is to deploy an openstack environment, so we believe changing the default to provision_demo=n or removing it completely is a reasonable option. Users can rerun packstack w/ config_provision_demo=y and config_tempest=y once the deployment has completed and packstack successfully exits. Since there is ongoing work to certify a Red Hat built tempest rpm there is also an opportunity to completely replace the provision_demo and config_tempest options with tempest rpm and its configuration script. http://koji.fedoraproject.org/koji/packageinfo?packageID=18966 AFAICT, the current tempest rpm can setup the same kind of environment in openstack that the provision_demo option can and it of course provides tempest and configures the tempest.conf for the user. I do not believe we would be loosing any function if we made a move to deprecate the packstack options and move to the tempest rpm.
The git repo for tempest is here: https://github.com/redhat-openstack/tempest
After chatting w/ Martin Magr, Alvaro Ortega and Mike Orazi we've come to the conclusion that config_demo and config_tempest should remain a part of packstack. The source of setup will move from the puppet provision module and upstream tempest to the tempest rpm. CONFIG_PROVISION_DEMO will call and execute the config_tempest script to setup demo users, tenant, networks etc.. CONFIG_TEMPEST will also be provided by the tempest rpm. The two options rely on each other for configuration and settings that would be difficult to manage if they were coming from two different sources. Packstack will install the Red Hat tempest rpm and execute the tools/config_tempest script to provide the current function.
> Packstack will install the Red Hat tempest rpm and execute the > tools/config_tempest script to provide the current function. Please DO NOT make that default with --allinone! --allinone should just print instructions what's the next step to load demo data. It could be a separate script or re-running packstack with --demo option.
David, I understand the current Packstack setup already covers Tempest installation, so it would fulfill the requirements in this bz, right?
@Javier tempest is currently installed from upstream source, no matter if Packstack is installed from source or from binary packages. There is indeed github.com/redhat-openstack/tempest which is a fork of upstream tempest. This repository is currently used as the source of the openstack-tempest package. There is a bug opened with puppet-tempest to provide support for binary installation: https://bugs.launchpad.net/puppet-tempest/+bug/1549366 - If the need is to install, configure and run tempest, this is fulfilled. - If the need is to use the fork of tempest (either from source or from binary) this is unfulfilled I do not agree with using the fork of tempest in RDO.
Wes: based on David's comment #7, would you consider this bug solved?
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.