tacker

Network "net_mgmt" in manual Tacker installation

Bug #1709549 reported by Roger Luethi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
In Progress
Wishlist
venkatamahesh

Bug Description

The sample sample-vnfd.yaml on that page uses a network_name "net_mgmt". The name is used by devstack, but these are the instructions for a manual installation which follows (according to the previous page of the instructions) the OpenStack install-guide. The correct network name is therefore not net_mgmt. Presumably, the best choice is "selfservice".

-----------------------------------
Release: 0.7.1.dev187 on 2017-08-08 01:24
SHA: 9677abff15f48c864002c9b43544d93c79caac44
Source: https://git.openstack.org/cgit/openstack/tacker/tree/doc/source/install/getting_started.rst
URL: https://docs.openstack.org/tacker/latest/install/getting_started.html

Revision history for this message
yong sheng gong (gongysh) wrote :

cannot quite understand.

Revision history for this message
Roger Luethi (rl-o) wrote :

Sorry, I will try to be more precise.

The getting_started.html page linked in the bug report above contains a sample-vnfd.yaml file. In that file, one line reads: "network_name: net_mgmt".

"net_mgmt" is the name of a network which has to exist already (it is not created in the Tacker installation instructions). The network is a prerequisite.

A network with the name, "net_mgmt" is created by devstack. However, the manual installation instructions for Tacker do not use devstack. If you go one step back to https://docs.openstack.org/tacker/latest/install/manual_installation.html, you will see that it links to the OpenStack documentation site which hosts the OpenStack install-guide (https://docs.openstack.org/ocata/install-guide-ubuntu/). Users who follow that install-guide will _not_ have a network called "net_mgmt". Therefore, the sample sample-vnfd.yaml will not work.

Of the networks that do exist in such a non-devstack, install-guide cluster, the most suitable replacement for "net_mgmt" is probably a network named "selfservice".

Does that make more sense?

I am currently building a Tacker installer for the OpenStack training-labs which is a fully automated installer for OpenStack. It follows the install-guide and the manual installation instructions for Tacker. That is why I am hitting this problem (and some others I reported).

venkatamahesh (venkatamaheshkotha)
Changed in tacker:
assignee: nobody → venkatamahesh (venkatamaheshkotha)
venkatamahesh (venkatamaheshkotha)
Changed in tacker:
importance: Undecided → Wishlist
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.openstack.org/519069

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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