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.
For external network, I have created external network ext-net outside of script because we have to do some manual stuff here. For external networking make sure physical Ethernet port is added into external bridge br-ex and network configuration file ifcfg-br-ex and ifcfg-ethX is created with relevant info.
Add tenant network interface to router and set gateway of router to external network.
Create VM instance into tenant network.
Create and assign floating IP to VM
Add security rule for PING and SSH testing.
For external/outgoing access ping to 18.104.22.168 (google DNS) from VM and for floating incoming access ssh to VM using floating IP from outside.
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.
To access external API and internal API network I used curl utility to make API calls.
Using curl generate a new token first by providing tenant name, username, password and controller IP. We can be used admin auth_token as well but that token will fetch details related to admin tenant only. Here we can generate a token for any tenant.
This generates endpoint list with a token in the bottom.
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.
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).
# The loopback network interface
iface lo inet loopback
# The primary network interface
iface enp0s3 inet static