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).
# The loopback network interface
iface lo inet loopback
# The primary network interface
iface enp0s3 inet static
stack@Mitakastack:~/devstack$ cat /etc/hostname
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.
- Real-time Kernel-based Virtual Machine (KVM) compute nodes and custom CPU thread policies
- Live migration improvements
- Rolling upgrades in Cinder
- Disaster recovery share-replication application programming interface (API) support
- Tenant resources cleanup
- Improved security groups performance
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”
I came across some good info about the difference between two major Iaas provider Openstack and VMware. So thought of sharing with this blog. Couple of differences are as follows.
Continue reading “Compare Openstack Vs VMware”
We saw volume creation with related issues and probable solutions.
Now we will see volume attach to VM. Create partition on it. Remove it and detach volume from VM.
Attach created volume to testvm. Following is command-line requirement for cinder volume-attach.
Volume ID will get it from cinder-list use auto to autoassign the new device.
You can check volume status is changed to in-use now and also changed attached with VM ID.
Continue reading “Basic Cinder (volume) service functionality in Openstack – Part2”
In this post I am going to show you basic functionality of openstack cinder (volume) service functionality by creating volume on internal storage. Attaching that volume to VM. Create partition on that volume in client machine and test partition remove and detaching volume from VM.
Lets take one running state vm for cinder testing as we can do this operation on the fly. I have one VM name testvm.
Check the disk and partitions on the VM. I can access the testvm using private IP and public IP. Lets access it using private IP using unique network namespace.
First check private-net network ID and test the ping to private IP of VM using network namespace. For more details about basic networking in openstack check my last blog posts.
Continue reading “Basic Cinder (volume) service functionality in Openstack – Part1”
In first part we saw how to create new VM in internal/private network now in this post we will see how to add external/public network to VM instance.
First check if our existing VM is in running state.
Now also check available network using CLI and using Openstack Dashboard.
Continue reading “Basic networking in Openstack Part2”
Once you install Openstack in single node or multinode setup next thing is to setup network. To understand networking in Openstack is little tedious job. This post is to describe basic Openstack networking concept by creating internal/external networking and testing the same.
First delete all default network like public and private which were created by default after Openstack installation using
#neutron net-delete <net-name>
Let us create new internal network first.
Create subnet for network private-net with subnet address 10.0.0.0/24
Continue reading “Basic networking in Openstack Part 1”