e1f65e4f33
This patch includes the base elements needed for integrating Mistral and TripleO. For a development workflow, clone the source code and use the following steps: * Create additional actions in the /actions directory * Add an entry point in the setup.cfg file [entry_points] * See README for instructions on importing actions into Mistral Change-Id: Iac675122e79c6f9b2f41ba455c15d6422c796929 Co-Authored-By: Dan Prince <dprince@redhat.com> Co-Authored-By: Dougal Matthews <dmatthews@redhat.com> Blueprint: mistral-deployment-library Depends-On: Ibb98013d6ef283bd454f958bb036557d2b02997f
1.0 KiB
1.0 KiB
tripleo-common
A common library for TripleO workflows.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/tripleo-common
- Source: http://git.openstack.org/cgit/openstack/tripleo-common
- Bugs: http://bugs.launchpad.net/tripleo-common
Action Development
When developing new actions, you will checkout a copy of tripleo-common to an undercloud machine and add actions as needed. To test the actions they need to be installed and selected services need to be restarted. Use the following code below to accomplish these tasks.
sudo rm -Rf /usr/lib/python2.7/site-packages/tripleo_common* sudo python setup.py install sudo systemctl restart openstack-mistral-executor sudo systemctl restart openstack-mistral-engine # this loads the actions via entrypoints sudo mistral-db-manage populate # make sure the new actions got loaded mistral action-list | grep tripleo