Documentation: bare metal deployment of kolla with single network interface

[Ashish]

Deploying developer edition of kolla on a bare metal machine requires atleast 2 network interfaces. Kolla deployment on a machine with single network interface needs a second virtual interface. Current documentation does not give details on how to create a virtual interface and subsequently make use of it in kolla deployment.

[Ashish (ashish-jain14)]

My view about developer deployment of kolla on single NIC is that it should not be recommended. Specially when someone is trying to deploy directly on their laptop. Here are the reasons

1) You need a physical connection to the network as wifi cannot be used.
2) You need to have a static IP address of machine, which is really difficult if it is a laptop
3) As you move from one network to another your setup is not going to work
4) At times you may end up messing up with your machine network and hence it may not work at all
5) We are complicating the already complicated networking by creating bridges, veth-pair which would make it difficult to debug some of the issues/problems.

Instead of deploying kolla direcltly on a baremetal with a single NIC, the user should do the same on VM. The advantages are as follows

1) No need for physical connection to the network as wifi can be used
2) No need of static ip address for the host machine
3) The setup is network agnostic and hence will work on any networks
4) No impact on physical machine instead it just impacts the VM which can always be deleted/restored from a backup copy.
5) In a VM you can clearly define the network interfaces and hence it makes easier to understand an debug issues,

So in my opinion the documentation section for baremetal with single NIC should advice the user to use a VM instead of baremetal deployment.

[Steven Dake (sdake)]

docs wont be backported. moving to newton1.

[Swapnil Kulkarni (coolsvap-deactivatedaccount)]

Ashish, are you following up on adding the doc?

[Yee-Ting Li (yee379)]

i have nodes in production (not using kolla) using a single nic as my blade servers only have one actual network port. a bit of contention, but i'm using native openvswitch with a patch port rather than linuxbridge. i'm looking at replacing my existing setup with kolla and i would love to have this kolla support single nic bare metal hosts.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/413404
Reason: Very old

[Adrian Andreias (adrian-fleio)]

Is this still a valid point or should be closed as Won't Fix?

If it's a valid point, the original commit had only two lines added to Quick start,
so I think it won't make the Quick Start too long as a -1 comment says: https://review.opendev.org/413404

What do you think?

[Radosław Piliszek (yoctozepto)]

It seems valid. Maybe Kolla Ansible could also allow to skip the 2nd interface? (Though that would handicap the usefulness...)