Open Stack

I had this frustration, too, when doing this the first time.

FYI (and for the Googlers who stumble across this in the future), this 
patch [1] fixes the --max_number thing.

[1] https://review.openstack.org/#/c/175890/






On 7/27/15, 8:45 AM, "Jay Pipes" <jaypipes at gmail.com> wrote:

>On 07/26/2015 01:15 PM, Lars Kellogg-Stedman wrote:
>> So, the Kilo release notes say:
>>
>>      nova-manage migrate-flavor-data
>>
>> But nova-manage says:
>>
>>      nova-manage db migrate_flavor_data
>>
>> But that says:
>>
>>      Missing arguments: max_number
>>
>> And the help says:
>>
>>      usage: nova-manage db migrate_flavor_data [-h]
>>        [--max-number <number>]
>>
>> Which indicates that --max-number is optional, but whatever, so you
>> try:
>>
>>      nova-manage db migrate_flavor_data --max-number 100
>>
>> And that says:
>>
>>      Missing arguments: max_number
>>
>> So just for kicks you try:
>>
>>      nova-manage db migrate_flavor_data --max_number 100
>>
>> And that says:
>>
>>      nova-manage: error: unrecognized arguments: --max_number
>>
>> So finally you try:
>>
>>      nova-manage db migrate_flavor_data 100
>>
>> And holy poorly implement client, Batman, it works.
>
>LOL. Well, the important thing is that the thing eventually worked. ;P
>
>In all seriousness, though, yeah, the nova-manage CLI tool is entirely 
>different from the main python-novaclient CLI tool. It's not been a 
>priority whatsoever to clean it up, but I think it would be some pretty 
>low-hanging fruit to make the CLI consistent with the design of, say, 
>python-openstackclient...
>
>Perhaps something we should develop a backlog spec for.
>
>Best,
>-jay
>
>_______________________________________________
>Mailing list: 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to     : openstack at lists.openstack.org
>Unsubscribe : 
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack