Re: [Openstack] question about configuring FlatDHCPManager

[Xin Zhao]

OK, thanks for the info.

BTW, what's the "nova-manage project scrub projectname" do? Does it have 
the same effect as the manual steps you just mentioned do?


Xin

On 4/19/2012 1:01 PM, Vishvananda Ishaya wrote:
unfortunately there is a bug where deleting a network does not delete 
associated fixed ips:


https://bugs.launchpad.net/nova/+bug/754900

The fix has landed in trunk and is proposed for backport into stable/essex

https://review.openstack.org/6664

To work around this issue, you will have to delete the fixed ips 
manually from the database or drop and recreate the database.


Vish

On Apr 19, 2012, at 9:00 AM, Xin Zhao wrote:


Hello,

I run nova compute (diablo) on RHEL6. Following the instruction, I 
configured the network as following, and it works:


$>nova-manage network create ostester 10.0.0.0/24 1 256 --bridge=br0 
--bridge_interface=em1


Now I want to change it to use a new fixed_range, like 10.1.1.0/24, 
so I delete the network, then redefine it following the same
command format.  But it doesn't work, the instance starts still with 
the 10.0.0.X ip, and of course, network doesn't work in the

instances.

What do I miss here?

Thanks,
Xin
___
Mailing list: https://launchpad.net/~openstack 

Post to : openstack@lists.launchpad.net 

Unsubscribe : https://launchpad.net/~openstack 


More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] question about configuring FlatDHCPManager

[Vishvananda Ishaya]

unfortunately there is a bug where deleting a network does not delete 
associated fixed ips:

https://bugs.launchpad.net/nova/+bug/754900

The fix has landed in trunk and is proposed for backport into stable/essex

https://review.openstack.org/6664

To work around this issue, you will have to delete the fixed ips manually from 
the database or drop and recreate the database.

Vish

On Apr 19, 2012, at 9:00 AM, Xin Zhao wrote:

> Hello,
> 
> I run nova compute (diablo) on RHEL6. Following the instruction, I configured 
> the network as following, and it works: 
> 
> $>nova-manage network create ostester 10.0.0.0/24 1 256 --bridge=br0 
> --bridge_interface=em1
> 
> Now I want to change it to use a new fixed_range, like 10.1.1.0/24, so I 
> delete the network, then redefine it following the same 
> command format.  But it doesn't work, the instance starts still with the 
> 10.0.0.X ip, and of course, network doesn't work in the 
> instances. 
> 
> What do I miss here? 
> 
> Thanks,
> Xin
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] question about configuring FlatDHCPManager

[Xin Zhao]

Hello,

I run nova compute (diablo) on RHEL6. Following the instruction, I 
configured the network as following, and it works:


$>nova-manage network create ostester 10.0.0.0/24 1 256 --bridge=br0 
--bridge_interface=em1


Now I want to change it to use a new fixed_range, like 10.1.1.0/24, so I 
delete the network, then redefine it following the same
command format.  But it doesn't work, the instance starts still with the 
10.0.0.X ip, and of course, network doesn't work in the

instances.

What do I miss here?

Thanks,
Xin
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp