1. Create the VM(s)

Steps described in this page are run by "ubuntu", a non-root user.

1 Create The VM(s)
2 Enable Password
3 Turn Off Firewall And Allow All Incoming HTTP Connections Through IPTABLES

Create The VM(s)

Create the VM(s) where you are going to install the SDN-C cluster on Kubernetes with the following specifications:

VCPUs	4
Disk	20 GB
RAM	16 GB

Enable Password

As ubuntu user is to be used for deploying and monitoring SDN-C cluster, we are enabling password in SSH for easier access to the VM using ubuntu user.

Do the following steps to enable password logging for a ubuntu user within the VM:

#	Purpose	Example

#	Purpose	Example
0	(Optional) Fix the "unable to resolve host" issue	ubuntu@sdnc-k8s:~$ sudo vi /etc/hosts sudo: unable to resolve host sdnc-k8s add the host name to the localhost in the following format: <IP address> <hostname> localhost
1	Create a password for the ubuntu user	ubuntu@sdnc-k8s:~$ sudo passwd ubuntu Enter new UNIX password: <enter password> Retype new UNIX password: <repeat entering the same password> passwd: password updated successfully
2	Config ssh "PasswordAuthentication" to yes	ubuntu@sdnc-k8s:~$ sudo vi /etc/ssh/sshd_config find PasswordAuthentication and set its value to yes, so that the line looks like # Change to no to disable tunnelled clear text passwords PasswordAuthentication yes
3	Restart sshd to enable the new config	ubuntu@sdnc-k8s:~$ systemctl restart sshd ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to restart 'ssh.service'. Authenticating as: Ubuntu (ubuntu) Password: ==== AUTHENTICATION COMPLETE === ubuntu@sdnc-k8s:~$

Turn Off Firewall And Allow All Incoming HTTP Connections Through IPTABLES

As part of the investigation into ODL clustering within a Kubernetes network, we turned off firewall by using the following commands:

^{sudo ufw disable}
^{sudo iptables -I INPUT -j ACCEPT}

These commands disable the firewall and allow all incoming HTTP connections. It is not recommended to do this in the real production environment!

We are using them as an easy alternative as we are still in progress of investigating the development environment within the Kubernetes network.