Hi TripleO devs, The patches ([1], [2], [3], [4]) implementing the deployment plan import/export feature have been up for review for some time. (The corresponding spec is at [5].) In this email, I'd like to explain how to review this feature.
Patch [1] adds the import functionality to the create and update plan actions in tripleo-common. Make sure your copy of the tripleo-heat-templates includes the plan-environment.yaml[6] file. On your undercloud, clone a local copy of the tripleo-common repo [7] and cherry-pick the patch [1] on top of it. Then run the steps outlined at [8] in order to install the newly cloned copy of tripleo-common. This will make the updated actions available to Mistral. Then you can use the plan create and plan update commands, then make sure that the contents of the plan-environment.yaml file get correctly imported into the Mistral environment. E.g: $ openstack overcloud plan create --templates /usr/share/openstack-tripleo-heat-templates/ new_plan $ mistral environment-get new_plan And similarly for plan update. Patch [2] adds an action and a workflow for exporting deployment plans and patch [3] adds a CLI command that triggers the workflow. You can test these two patches together, or if you want to test only [2] you can manually execute the Mistral workflow. For patch [2] the same instructions from above regarding installing a new copy of tripleo-common apply. You will also need to manually update the plan management workbook: $ mistral workbook-update tripleo-common/workbooks/plan_management.yaml Please note that patch [2] depends on patch [1] - you'll need both of them applied on your local copy of tripleo-common. As far as python-tripleoclient goes, it is enough to simply clone a fresh copy to your undercloud, apply patch [3] and run `python setup.py install`. This will make the new plan export command available to you: $ openstack overcloud plan export new_plan If all goes well, that should create a plan export tarball (new_plan.tar.gz) in the directory you ran the command from. You should check that the tarball contains all the relevant plan files, as well as the plan-environment.yaml file whose contents should be imported from the Mistral environment. Finally, patch [4] integrates the plan export functionality into the TripleO UI. You will need [1] and [2] applied on your undercloud. Then you can cherry pick [4] on top of your tripleo-ui checkout. Access the UI, navigate to Select Deployment -> Manage Deployments. Next to every plan, there should now be a new Export button which you can use to test the plan export functionality. Hope all of this makes sense - if it does not, or you have any other questions regarding this feature, please feel free to respond here or ping me on IRC. Thanks for your patience and I'll look forward to the reviews! [1] https://review.openstack.org/#/c/414169/ [2] https://review.openstack.org/#/c/422789/ [3] https://review.openstack.org/#/c/425858/ [4] https://review.openstack.org/#/c/437676/ [5] https://specs.openstack.org/openstack/tripleo-specs/specs/ocata/gui-plan-import-export.html [6] https://github.com/openstack/tripleo-heat-templates/blob/master/plan-environment.yaml [7] https://github.com/openstack/tripleo-common [8] https://docs.openstack.org/developer/tripleo-common/readme.html#action-development -- Regards, Ana Krivokapic Senior Software Engineer OpenStack team Red Hat Inc.
__________________________________________________________________________ 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