...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
...
| Info |
|---|
Steps described in this page are run by "ubuntu", a non-root user. |
| Table of Contents |
|---|
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 unbuntu user in for a ubuntu user within the VM:
| # | Purpose | Example |
|---|
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
| 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:
|
| 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
|
| 3 |
| Restart sshd to enable the new config | ubuntu@sdnc-k8s:~$ systemctl restart sshd |
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === |
==== 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.
...
ubuntu@sdnc-k8s:~$ |
Turn Off Firewall And Allow All Incoming HTTP Connections Through IPTABLES
As part of the investigation of into ODL clustering in kubernetes within a Kubernetes network, we turned off firewall by using the following commands:
sudo ufw disablesudo iptables -I INPUT -j ACCEPT
These commands disables disable the firewall and allow all incoming HTTP connections. It 's is not recommneded recommended to do this in the real production envrionment.environment!
We are using them as an easy alternative as we are still in progress of investigating in the development environment under within the kubernetes Kubernetes network.