Open Stack

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 CLI will be just more confusing when
>> people will debug issues. So it would
>> have to be done very good.
>>
>> E.g calling 'openstack-client net-create' fails.
>> Where do you find error log?
>> Are you using nova-networking or Neutron?
>
> I would at least expect the debug/log of the tuskar client to show what
> calls its making on other clients so following this trail wouldn't be
> too hard.
>

Well sure, this is part of 'being done very good'.

Though a lot of calls makes some asynchronous jobs, that can result in 
errors
you will just not see when you call the clients.
So you will need to know where to look depending on what is acting weird.

What I am trying to say is, the Openstack is just complex, there is no way
around, sysadmins just need to understand, what they are doing.

If we are going to simplify that, we would need to build something like
we have in UI. So some abstraction layer that leads the user and won't
let him break it. Though this leads to limited functionality we are able 
to control.
Which I am not entirely convinced is what CLI users want.



> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev