Enabling Networking in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora  - havana

Bug #1243588 reported by Georg Hennemann
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openstack-manuals
Invalid
Undecided
Unassigned
Ubuntu
Invalid
Low
Unassigned

Bug Description

The command nova network-create doesnot work any more:
  invalid choice: 'network-create'

[root@compute1 ~]# nova network-create vmnet --fixed-range-v4=10.0.0.0/24 \
> --bridge-interface=br100 --multi-host=T
usage: nova [--version] [--debug] [--no-cache] [--timings]
            [--os-username <auth-user-name>] [--os-password <auth-password>]
            [--os-tenant-name <auth-tenant-name>] [--os-auth-url <auth-url>]
            [--os-region-name <region-name>] [--os-auth-system <auth-system>]
            [--service-type <service-type>] [--service-name <service-name>]
            [--volume-service-name <volume-service-name>]
            [--endpoint-type <endpoint-type>]
            [--os-compute-api-version <compute-api-ver>] [--insecure]
            [--bypass-url <bypass-url>]
            <subcommand> ...
error: argument <subcommand>: invalid choice: 'network-create'
Try 'nova help ' for more information.

-----------------------------------
Built: 2013-10-22T21:35:31 00:00
git SHA: 50decd73b5d6b2d91d8577e94e0f299c1c662939
URL: http://docs.openstack.org/havana/install-guide/install/yum/content/nova-network.html
source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-fedora/doc/install-guide/section_nova-network.xml
xml:id: nova-network

Revision history for this message
Tom Fifield (fifieldt) wrote :

Thanks for the report Georg - looking into this immediately.

Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi Georg,

I've read the code, and it seems like nova network-create is valid.

Is there a chance your python-novaclient package is out of date?

Changed in openstack-manuals:
status: New → Incomplete
Revision history for this message
Kodiak Firesmith (kfiresmith) wrote :

Hello Tom.

So the deal here I think is that the documentation never covered the process of setting up the network bridge "br100".

My position is that yes, there are other documents to cover doing this sort of thing (the RedHat deployment guide comes to mind), but if this documentation strives to be a complete walk through, it should cover not only the creation of the software bridge device br100, but also should discuss the iptables needs in a multi-host Openstack configuration, including allowing all of the management ports needed such as 5000, 8774, 9292, and 35357.

Revision history for this message
Tom Fifield (fifieldt) wrote :

br100 is automatically set up by nova-network, you do not need to manually create it.

Revision history for this message
Kodiak Firesmith (kfiresmith) wrote :

Oh, OK then I stand corrected. I can't confirm this particular page of docs until a couple days from now, I'm still waiting on compute hardware to come in. I'll zip through this page when my gear arrives and come back to confirm if I can reproduce his complaints or not.

Thanks Tom!

Revision history for this message
Tom Fifield (fifieldt) wrote :

Thanks Kodiak!

I'll ensure the doc gets updated to make this clearer :)

tags: added: install-guide
Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Incomplete → Triaged
importance: Undecided → Low
Revision history for this message
Aswin mohanan (aswinmohanan001) wrote :

Me too getting the following error

[root@server2 ~(keystone_admin)]# nova network-create vmnet --fixed-range-v4=192.168.1.0/24 \ --bridge-interface=br100 --multi-host=T
usage: nova [--version] [--debug] [--os-cache] [--timings]
            [--timeout <seconds>] [--os-username <auth-user-name>]
            [--os-password <auth-password>]
            [--os-tenant-name <auth-tenant-name>] [--os-auth-url <auth-url>]
            [--os-region-name <region-name>] [--os-auth-system <auth-system>]
            [--service-type <service-type>] [--service-name <service-name>]
            [--volume-service-name <volume-service-name>]
            [--endpoint-type <endpoint-type>]
            [--os-compute-api-version <compute-api-ver>]
            [--os-cacert <ca-certificate>] [--insecure]
            [--bypass-url <bypass-url>]
            <subcommand> ...
error: unrecognized arguments:
Try 'nova help ' for more information.

Revision history for this message
Amit (amit-gupta) wrote :

Seems tricky! Replace '-' with '_' and the error goes away.

For more info. check the command usage.

Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi Armit,

This is very likely because your client is out of date.

Ensure that you have set up the appropriate packages for the Havana version of the client.

Revision history for this message
Tom Fifield (fifieldt) wrote :

Made a new bug for tracking the comment about firewall setup/ports etc: https://bugs.launchpad.net/openstack-manuals/+bug/1261617

the original bug report here appears to be invalid for havana, so will close it. Please post comments on the new bug for the firewall/port information, or here if it has been closed in error.

Changed in openstack-manuals:
status: Triaged → Invalid
Revision history for this message
Aswin mohanan (aswinmohanan001) wrote :

Hi Amit,

Thank you for your comment on this, I got working that command by adding _ instead of -

BTW,

I am trying to create the floating ip address, but it seems it is adding ips but not listing, please have a look into the following snippet:

[root@server2 ~(keystone_admin)]# nova-manage floating create --ip_range=192.168.1.0/24 --pool Public
[root@server2 ~(keystone_admin)]# nova floating-ip-pool-list

[root@server2 ~(keystone_admin)]#

Changed in openstack-manuals:
status: Invalid → Confirmed
affects: openstack-manuals → ubuntu
Changed in ubuntu:
status: Confirmed → Invalid
Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

Georgios, why are you moving this to Ubuntu?

Changed in openstack-manuals:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.