1. Create the VM(s)

Create the VM(s)

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

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

#	Purpose	Example
1	Create a password for the ubuntu user	ubuntu@sdnc-k8s:~$ sudo passwd ubuntu sudo: unable to resolve host sdnc-k8s Enter new UNIX password: <enter password> Retype new UNIX password: <repeat entering the same password> passwd: password updated successfully
2	(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
3	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
4	Restart sshd to enable the new config	ubuntu@sdnc-k8s:~$ systemctl restart sshd passwd ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to restart 'ssh.service'. Authenticating as: Ubuntu (ubuntu) Password: ==== AUTHENTICATION COMPLETE === ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to restart 'passwd.service'. Authenticating as: Ubuntu (ubuntu) Password: ==== AUTHENTICATION COMPLETE === Failed to restart passwd.service: Unit passwd.service not found.

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.