Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-28 Thread Ladislav Smola
On 02/27/2014 05:02 PM, Ana Krivokapic wrote: On 02/27/2014 04:41 PM, Tzu-Mainn Chen wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-28 Thread Ladislav Smola
On 02/27/2014 04:30 PM, Dougal Matthews wrote: On 27/02/14 15:08, Ladislav Smola wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Dougal Matthews
On 26/02/14 19:43, Jay Dobies wrote: * Even at this level, it exposes the underlying guts. There are calls to nova baremetal listed in there, but eventually those will turn into ironic calls. It doesn't give us a ton of flexibility in terms of underlying technology if that knowledge bubbles up

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Dougal Matthews
On 26/02/14 13:34, Jiří Stránský wrote: Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 This is great, thanks for taking the time to put it together. Another thing to add to my list of

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Jiří Stránský
On 26.2.2014 20:43, Jay Dobies wrote: I'd say it's still an open question whether we'll want to give better UX than that ^^ and at what cost (this is very much tied to the benefits and drawbacks of various solutions we discussed in December [1]). All in all it's not as bad as i expected it to be

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Jiří Stránský
On 27.2.2014 10:16, Dougal Matthews wrote: On 26/02/14 13:34, Jiří Stránský wrote: get Tuskar UI a bit closer back to the fact that Undercloud is OpenStack too, and keep the name Flavors instead of changing it to Node Profiles. I wonder if that would be unwelcome to the Tuskar UI UX, though.

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Jiří Stránský
On 26.2.2014 21:34, Dean Troyer wrote: On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies jason.dob...@redhat.com wrote: I like the notion of OpenStackClient. I'll talk ideals for a second. If we had a standard framework and each project provided a command abstraction that plugged in, we could pick

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Dean Troyer
On Thu, Feb 27, 2014 at 6:36 AM, Jiří Stránský ji...@redhat.com wrote: Thanks for bringing this up. It looks really interesting. Is it possible to not only add commands to the OpenStackClient, but also purposefully blacklist some from appearing? As Jay mentioned in his reply, we don't make

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Jay Dobies
Yeah. This is a double bladed axe but i'm leaning towards naming flavors consistently a bit more too. Here's an attempt at +/- summary: node profile + a bit more descriptive for a newcomer imho - CLI renaming/reimplementing mentioned before - inconsistency dangers lurking in the deep - e.g.

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Ladislav Smola
Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will debug issues. So it would have to be

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Tzu-Mainn Chen
Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will debug issues. So it would have to

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Ana Krivokapic
On 02/27/2014 04:41 PM, Tzu-Mainn Chen wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-27 Thread Dougal Matthews
On 27/02/14 15:08, Ladislav Smola wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will

[openstack-dev] [TripleO] Tuskar CLI UX

2014-02-26 Thread Jiří Stránský
Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 I'd say it's still an open question whether we'll want to give better UX than that ^^ and at what cost (this is very much tied to the

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-26 Thread Jay Dobies
Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 This is excellent to see it all laid out like this, thanks for writing it up. I'd say it's still an open question whether we'll want to

Re: [openstack-dev] [TripleO] Tuskar CLI UX

2014-02-26 Thread Dean Troyer
On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies jason.dob...@redhat.com wrote: I like the notion of OpenStackClient. I'll talk ideals for a second. If we had a standard framework and each project provided a command abstraction that plugged in, we could pick and choose what we included under the