[unoffical guide] Baremetal installation using dummy interfaces

@juan wrote:

Quick preface, I had quite a few issues when trying to setup VIRL as a baremetal install from the .ISO on a server with just 2 physical NICs. Thanks to @jobstfel I eventually got everything working. Just as everything was sorted I wiped the server and started the install again just so I could write a quick few steps about how to get it working.

Disclaimer - This works for me, it may not work for you, I hold no responsibility if following this guide breaks your server, datacentre or kills your dog. This is an unofficial guide not supported by Cisco but I welcome any feedback if it helps you.

My server had just 2 physical NICs and needed a static IP address.
So we start by following the offical instructions on here http://virl-dev-innovate.cisco.com/iso.bm.php

At Step 4 - Prepare for an Interface-Constrained Installation, we have to divert from the offical instructions.

Because Ubuntu (and linux in general) has changed it's interface naming scheme there are no more eth0, eth1 etc etc.

The interface naming now is em1, em2 etc for embedded NICs and p1p1, p1p2 for PCI cards.

Edit your network config file in '/etc/network/interfaces' to use em1 instead of eth0 and em2 instead of eth1
At this point I also changed em1 to use a static IP instead of DHCP (see step 5 of the offical guide)
Add the extra config to bring up the connection to the openstack services

up ip addr add 172.16.10.250/24 dev em1

Save and exit

edit the virl.ini file to have the following lines

public_port: em1
using_dhcp_on_the_public_port: False
l2_port: em2
l2_port2: dummy0
l3_port: dummy1
dummy_int: True
internalnet_port: dummy2

save and exit

reboot (not sure if needed actually)

Now run
vinstall salt
Then using cat /etc/salt/grains | grep -e dhcp -e em -e dummy - clarify the correct infomation is present, it should match the above settings.

At this point we need to skip forward to making sure the server is licensed.

Prepare for activation

Reset the SSH RSA key with the following

sudo apt-get remove -y openssh-server
sudo apt-get install -y openssh-server

Check KVM acceleration can be used

sudo kvm-ok

NTP must also be working to allow VIRL activation, check this with 'sudo ntpq -p'

You will probably have to edit '/etc/ntp.conf' to have the correct interface name, em1 instead of eth0.
'interface listen em1'

Save ane exit
Stop the NTP service and start it again

sudo service ntp stop
sudo service ntp start

Check with 'sudo ntpq -p' that the server now has NTP syncing.

At this point I will make a note that you now potentially have a server running with SSH access from the internet with a very very weak password and I'd advise to make sure you have some firewalling in place either on the server or in front of it.

Follow the instructions in Step 8: Activate VIRL to get activated

Once activated we can continue.

run the following commands

sudo salt-call saltutil.sync_all
sudo salt-call -l debug state.sls virl.host
sudo salt-call -l debug state.sls openstack
sudo salt-call -l debug state.sls openstack.setup
sudo salt-call -l debug state.sls openstack.restart

reboot

Check Openstack services are all and running now with the following

'nova service-list' - should all show status as 'enabled' and state as 'up'.
'neutron agent-list' - the alive column should have 4 x : - ) but give it a few minutes after booting to get these started up.

Hopefully at this point everything is now working for you. You can check the health status in the UWM area under "System status"

Posts: 1

Participants: 1

Read full topic