Open Stack

OK, I managed to delete the network through the console by scrubing the project first.  

Now I have no networks listed in my nova-manage network list but my old network is still showing up in Horizon.

Should I just delete and start over?




Steven Barnabas
Network Engineer 
Front Porch, Inc.
209-288-5580
209-652-7733 mobile
www.frontporch.com



On May 9, 2013, at 3:39 PM, Steven Barnabas <sbarnabas at frontporch.com> wrote:

> Ok, I did not boot from the console, I booted from Horizon.  So i did not use any options.  
>  
> I also assigned the 1.1.1.1/24 to that network in horizon.  It was already part of the project.  
> 
> When I did a nova-manage network list on the controller box, it was only showing the 1.1.1.1 network.
> 
> I deleted the 1.1.1.1 network to start over through horizon.
> 
> So now in Horizon, I see my original network, but when I do a nova-manage network list I still only see the 1.1.1.1  I tried to delete it but it says it cannot be found.
> 
> i think i messed something up by using Horizon.  I rebooted the Controller and the Compute box and it still just shows the 1.1.1.1 network.
> 
> 
> Steven Barnabas
> Network Engineer 
> Front Porch, Inc.
> 209-288-5580
> 209-652-7733 mobile
> www.frontporch.com
> 
> 
> 
> On May 9, 2013, at 2:44 PM, Joe Topjian <joe.topjian at cybera.ca> wrote:
> 
>> Hi Steven,
>> 
>> Great! Now, you might have to assign the network to the project which you will be launching instances from. It'll be something like:
>> 
>> nova-manage network modify --fixed_range=1.1.1.0/24 --project=<uuid of project>
>> 
>> check "nova-manage network modify" for more info.
>> 
>> Then if you do "nova-manage network list" you should see the project uuid listed for two different networks.
>> 
>> Thanks,
>> Joe
>> 
>> 
>> On Thu, May 9, 2013 at 3:16 PM, Steven Barnabas <sbarnabas at frontporch.com> wrote:
>> ok I did this:
>> nova-manage network create --fixed_range_v4=1.1.1.0/24 --num_networks=1 --network_size=256 --vlan=1 --label=IN-Interface --project=admin --bridge=br-eth4 --bridge_interface=eth4
>> 
>> And it worked! 
>> 
>> this was the output:
>> 2013-05-09 14:09:14 DEBUG nova.utils [req-55460cdf-fe87-4f86-9ffb-237dd8024ea9 None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:506
>> 
>> But….It did not add a secondary Interface when I launched my VNC console to the instance through the gui.  It actually replaced the first network with the second network.  Not adding the second interface.
>> 
>> Should I try launching it a different way?
>> 
>> 
>> Thanks.
>> 
>> 
>> Steven Barnabas
>> Network Engineer 
>> Front Porch, Inc.
>> 209-288-5580
>> 209-652-7733 mobile
>> www.frontporch.com
>> 
>> 
>> 
>> On May 7, 2013, at 7:18 AM, Joe Topjian <joe.topjian at cybera.ca> wrote:
>> 
>>> Hi Steven,
>>> 
>>> Have you tried the --bridge_interface option?
>>> 
>>> "nova-manage network create -h" shows both --bridge and --bridge_interface as options. 
>>> 
>>> Thanks,
>>> Joe
>>> 
>>> 
>>> On Mon, May 6, 2013 at 5:36 PM, Steven Barnabas <sbarnabas at frontporch.com> wrote:
>>> Ok I changed my /etc/network/interfaces eth-4 interface to manual
>>> 
>>> when I do a brctl show this is the output:
>>> root at FPCompute:~# brctl show
>>> bridge name	bridge id		STP enabled	interfaces
>>> br-eth0		0000.00151715ac78	no		eth0
>>> 							phy-br-eth0
>>> br-eth4		0000.00188b4c7e7a	no		eth4
>>> br-int		0000.d6e482502444	no		int-br-eth0
>>> qbr4ba9f712-ec		8000.7abe7483f8e4	no		qvb4ba9f712-ec
>>> 
>>> So the bridge is already there and the interface is mapped to it from what it looks like.  
>>> 
>>> When I do this:
>>> nova-manage network create --fixed_range_v4=1.1.1.0/24 --num_networks=1 --network_size=256 --vlan=1 --label=IN-Interface --project=admin --bridge=br-eth4
>>> I still get the:
>>> Command failed, please check log for more info
>>> 2013-05-06 16:18:07 CRITICAL nova [req-9d8bbe89-282c-4490-a3b1-643faeccc849 None None] bridge_interface is required to create a network.
>>> 2013-05-06 16:18:07 22953 TRACE nova Traceback (most recent call last):
>>> 2013-05-06 16:18:07 22953 TRACE nova   File "/usr/bin/nova-manage", line 1404, in <module>
>>> 2013-05-06 16:18:07 22953 TRACE nova     main()
>>> 2013-05-06 16:18:07 22953 TRACE nova   File "/usr/bin/nova-manage", line 1391, in main
>>> 2013-05-06 16:18:07 22953 TRACE nova     fn(*fn_args, **fn_kwargs)
>>> 2013-05-06 16:18:07 22953 TRACE nova   File "/usr/bin/nova-manage", line 480, in create
>>> 2013-05-06 16:18:07 22953 TRACE nova     net_manager.create_networks(context.get_admin_context(), **kwargs)
>>> 2013-05-06 16:18:07 22953 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 2105, in create_networks
>>> 2013-05-06 16:18:07 22953 TRACE nova     self, context, vpn=True, **kwargs)
>>> 2013-05-06 16:18:07 22953 TRACE nova   File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 1461, in create_networks
>>> 2013-05-06 16:18:07 22953 TRACE nova     raise exception.NetworkNotCreated(req=fld)
>>> 2013-05-06 16:18:07 22953 TRACE nova NetworkNotCreated: bridge_interface is required to create a network.
>>> 2013-05-06 16:18:07 22953 TRACE nova 
>>> 
>>> I even tried adding br-eth4 to my /etc/network/interfaces and it still did not work.  I removed that now.
>>> 
>>> 
>>> Steven Barnabas
>>> Network Engineer 
>>> Front Porch, Inc.
>>> 209-288-5580
>>> 209-652-7733 mobile
>>> www.frontporch.com
>>> 
>>> 
>>> 
>>> On May 4, 2013, at 7:42 AM, Joe Topjian <joe.topjian at cybera.ca> wrote:
>>> 
>>>>> nova-manage network create --fixed_range_v4=1.1.1.0/24 --num_networks=1 --network_size=256 --vlan=1 --label=IN-Interface --project=admin --bridge=br-2
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Joe Topjian
>>> Systems Administrator
>>> Cybera Inc.
>>> 
>>> www.cybera.ca
>>> 
>>> Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.
>> 
>> 
>> 
>> 
>> -- 
>> Joe Topjian
>> Systems Administrator
>> Cybera Inc.
>> 
>> www.cybera.ca
>> 
>> Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130509/a82dc862/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2919 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130509/a82dc862/attachment.bin>