Ok folks, this is a bit of bad news, but I'll come out with it. Because of the addition of Mesos at the Mitaka design summit, the main engineers working on the CLI decided they want to wait to provide a unified experience with Mesos and Ansible. Nobody is beating us up for a CLI or ReST API, although I think these things would be useful and necessary additions.
The short of it is, it looks as if the CLI work for the short term will be abandoned because the current cli codebase as is will have to be rewritten a-fresh. I will make a change to the governance repository to remove it from our list of deliverables. My apologies for the false start, but as with everything OpenStack, big changes happen at Summit, and the introduction of Mesos as an alternative orchestration engine (although not the one we lead with, which is Ansible), was one of our big decision points. In the future, if we do make a CLI, hopefully in the N cycle, I would highly prefer it be done from the start completely upstream rather then a code drop so the entire community is engaged in the process. If there are any thoughts or concerns from the CR team or other community members in general, fire away. Regards -steve
__________________________________________________________________________ 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
