On Thu, Apr 5, 2018 at 10:38 AM, James Slagle <james.sla...@gmail.com> wrote: > I've pushed up for review a set of patches to switch us over to using > config-download by default: > > https://review.openstack.org/#/q/topic:bp/config-download-default > > I believe I've come up with the proper series of steps to switch > things over. Let me know if you have any feedback or foresee any > issues: > > FIrst, we update remaining multinode jobs > (https://review.openstack.org/558965) and ovb jobs > (https://review.openstack.org/559067) that run against master to > opt-in to config-download. This will expose any issues with these jobs > and config-download and let us fix those issues. > > We can then switch tripleoclient (https://review.openstack.org/558925) > over to use config-download by default. Since this also requires a > Heat environment, we must forcibly inject that environment via > tripleoclient. > > Once the tripleoclient patch lands, we can update > tripleo-heat-templates to use the mappings from config-download in the > default resource registry (https://review.openstack.org/558927).
I forgot to mention that at this point the UI would have to be working with config-download before we land that tripleo-heat-templates patch. Or, the UI could opt-in to the disable-config-download-environment.yaml that I'm providing with that patch. -- -- James Slagle -- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev