Bug 890527 - Quantum CLI help usage is not friendly / intuitive
Summary: Quantum CLI help usage is not friendly / intuitive
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.0
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-27 14:43 UTC by Ofer Blaut
Modified: 2016-04-26 16:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 07:36:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Quantum CLI output vs Nova output (3.01 KB, text/plain)
2012-12-27 14:43 UTC, Ofer Blaut
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1237820 0 None None None Never

Description Ofer Blaut 2012-12-27 14:43:31 UTC
Created attachment 669601 [details]
Quantum CLI output vs Nova output

Description of problem:

Qunatum CLI help usage is not friendly / intuitive.

There are few issues with the CLI help:

1. too much output like :
- output formatters 
- positional arguments:
- shell formatter 

2. There is no explain on what values are used like :
-admin-state-down -  No explain about ( True | False ) 

3. addtional info which relates to the plugin used is not added , like 

--provider:network_type vlan 
--providerhysical_network <phys-net-name> 
--provider:segmentation_id <VID>

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. run quantum net-create --help and check if it is easy to see 
- vlans 
- dns server add list
- DHCP disable option 
and others options 
2. IMHO when using plugings its commands should be added automatically
3. Attached Nova network CLI command output vs Quantum network CLI 

This is also apply to horizon where lots of options are missing 
  
Actual results:


Expected results:


Additional info:

Comment 2 Chris Wright 2013-01-03 20:34:03 UTC
Needs an upstream discussion and bug filed

Comment 3 lpeer 2013-11-11 07:36:25 UTC
After discussing with ofer we'll track this bug u/s only


Note You need to log in before you can comment on or make changes to this bug.