openstack team mailing list archive

[Joseph Heck <heckj@xxxxxxx>]

To answer my own question on the list (Thanks Vish & Trey):

The command to create a network should be updated - aka:

	nova-manage network create private 10.0.0.0/24 1 32

additionally, the "nova-manage floating create" also changed, and no longer requires a hostname in there.

Vish has updated his novascript (https://github.com/vishvananda/novascript/commit/d36f5775b2d8d6d736294cb866937bd9ccfd0d33) with the relevant changes. 

(as I write this, the cloudbuilders nova.sh script hasn't been updated - so it needs those little tweaks if you're using it with trunk)

-joe

On Jul 6, 2011, at 12:06 PM, Joseph Heck wrote:
> Afternoon!
> 
> I ran into an issue with the multi-nic addition that just hit trunk - wanted to see how best to resolve or if this is a bug.
> 
> The signature for the create() method in NetworkCommands (in nova/bin/nova-manage) changed - which means that the existing docs to create a network:
> 
> 	nova-manage network create 10.0.0.0/24 1 32
> 
> Fails with an index out of range error. The reason is that the arguments ['10.0.0.0/24', '1', '32'] no longer match up as expected with the arguments in create().
> 
> "Label=None" was added at the front of that method signature. So with multi-nic added in, does the command need to be updated, or should that Label component be pushed back in the positional list of arguments?
> 
> -joe
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp