Hey all, I've been working on GUIs that use the TripleO deployment methodology for a while now. Recent changes have started to diverge the CLI-supported deployment workflow from an API supported workflow. There is an increased amount of business logic in the CLI that GUIs cannot access.
To fix this divergence, I've created a spec targeted for mitaka (https://review.openstack.org/#/c/219754/ ) that proposes to take the business logic out of the CLI and place it into the tripleo-common library; and later, create a PoC REST API that allows GUIs to easily use the TripleO deployment workflow. What do people think? Thanks, Tzu-Mainn Chen __________________________________________________________________________ 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
