We can create mulit-node kubernetes setup on Windows laptop/VM as well. Mostly if you want to learn or try and test Kubernetes concepts.
I am using Windows 2012 server, it will work on other Windows version as well.
We use Virtualbox and Vagrant to configure Kubernetes nodes.
Perform following steps as pre-requisites.
Many times we need test lab which includes two or more virtual machines and which should be built quickly on our laptop and test different scenarios of docker, Kubernetes and Ansible and tear down once done.
I used to install VirtualBox on my laptop and then install CentOS manually and then clone it for two or three VMs, this also works fine but it is time-consuming as my aim was to learn the docker, Kubernetes concepts or test Ansible playbooks, once done tear down the setup and start new one for other test cases.
There is one simple solution out there where we can use VirtualBox and Vagrant to set up a multinode environment using the configuration file and start the lab in a few mins.
I have summarized a few steps to quickly set up your own lab with VirtualBox and Vagrant.
You can create as many virtual machines you want but you need enough RAM on your laptop/desktop.
1. Download the VirtualBox software using the following link. Just check the latest/stable release wget https://download.virtualbox.org/virtualbox/6.0.4/VirtualBox-6.0-6.0.4_128413_el7-1.x86_64.rpm
Install the VirtualBox #rpm -ivh VirtualBox-6.0-6.0.4_128413_el7-1.x86_64.rpm
2. Download the Vagrant setup using the link
wget https://releases.hashicorp.com/vagrant/2.2.4/vagrant_2.2.4_x86_64.rpm
If you are getting timeout error while executing dry-run or actual deployment like following that means ansible is taking a long time to gather facts from managed hosts.
Generally, you will get an error like “Timer expired after 10 seconds”.
Continue reading “Timeout Error while Gathering Facts using Ansible Playbook”
This post describe quick steps to install KVM hypervisor on CentOS7. KVM (Kernel based Virtual Machine) is opensource hypervisor, lightweight and works/fits well into cloud.
For your personal lab you can use KVM hypervisor layer and utilize hardware for creation of multiple VMs. KVM support both linux and windows based VMs.
Check whether system CPU supports Hardware Virtualization. #grep -E ‘{vmx|svm}’ /proc/cpuinfo
if you get vmx or svm in output then you are good to go ahead otherwise your CPU doesn’t support virtualization.
External/Floating outgoing/incoming network
I have used following steps to test this.
Tenant to tenant networking with different subnet
For tenant to tenant networking I used following steps.
All test are performed from standalone VM outside of the OpenStack cloud. First, establish passwordless SSH authentication between Standalone VM and OpenStack controller. Use following method to invoke the script from standalone VM which will run o on controller VM and get the details.
ssh –T <controller hostname/ip> < script.sh
Here –T Disable pseudo-tty allocation from VM
External and Internal API networking.
I was busy studying OpenStack Foundation’s COA exam so couldn’t publish blog post for a while.
Luckily I have passed the COA exam and hard work pays off. As I have passed this so thought of sharing my experience with the exam.
This post is basically contains some tips/info about OpenStack Foundation (COA) Certified OpenStack Administrator exam.
Certified OpenStack Administrator (COA) is the first professional certification offered by the OpenStack Foundation. It’s designed to help companies identify top talent in the industry, and help job seekers demonstrate their skills.
The Certified OpenStack Administrator is a professional typically with at least six months of OpenStack experience, and has the skills required to provide day-to-day operation and management of an OpenStack cloud.
The current exam is based on the OpenStack Liberty version and covers the core compute, storage and networking services. To learn more about the knowledge requirements and domains covered in the exam, go to www.openstack.org/coa/requirements.
Continue reading “Tips to pass OpenStack Foundation (COA) Certified OpenStack Administrator exam.”
We can install Openstack using many tool Devstack and Packstack are two of them. In my last post I have shared Openstack Installation using Packstack on CentOS 7. In this post I am going through step by step Openstack installation using Devstack on Ubuntu 16.04.ive
I am using VirtualBox VM with following configuration.
OS – Ubuntu 16.04
RAM – 7168MB
Disk – 40GB
vCPU – 2
Network – One bridged ethernet adapter with static IP.
1. Install Ubuntu minimal server on VM and perform apt-get update and upgrade and reboot the machine.
2. Configure Bridged ethernet adapter with static IP and give relevant hostname to machine.
stack@Mitakastack:~/devstack$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto enp0s3
iface enp0s3 inet static
address 10.20.1.154
netmask 255.255.252.0
gateway 10.20.0.1
dns-nameservers 10.20.0.3
stack@Mitakastack:~/devstack$ cat /etc/hostname
Mitakastack
Continue reading “Openstack Mitaka Installation using Devstack on Ubuntu 16.04”
Mitaka is 13th release of Openstack. Following are some of the notable features in Mitaka.
Compute
Storage
Networking
I have configured allinone Openstack Mitaka setup on one Virtual VM using VirtaulBox.
My Virtual VM configuration are as follows.
OS – CentOS 7.2
RAM – 7168MB
Storage – 40GB
Network – One bridged adpater with static IP
vCPU – 2
Install CentOS 7.2 on VM and update to latest level and reboot the system.
Continue reading “Openstack Mitaka Installation using packstack on CentOS 7”
Technology evangelist 