Bobcares

Docker in oVirt – how we configured ‘Container as a Service’ in oVirt

by | Dec 22, 2015

2015 State of the Cloud Survey showed that adoption of Docker technology was a rising trend, with around 48% DevOps companies using it. Docker is an open source project that package applications and run-time binaries into Linux containers. With Docker, developers can define project environments and deploy their apps quickly.

In a recent post, we covered how ‘oVirt was used to build an open source Cloud solution’. This cloud system was used by many software businesses, who wanted quick application deployment, resource scalability and faster project turn-around time.

We implemented this using Docker containers and Docker Swarm as management software (aka Orchestrator). This model is commonly known as ‘Container as a Service’ (CaaS).

See how our WHMCS oVirt plugin helps you!

Creating Docker containers in oVirt

The first stage in CaaS implementation was to setup the containers. But oVirt didn’t support container-based virtualization. To resolve this, we built a system that created Docker containers within oVirt VMs. For quick provisioning of Docker VMs, we created templates pre-configured with Docker service. Once these containers were provisioned, our custom script linked them to a cluster managed by Docker Swarm.

Docker Swarm is an open-source container orchestration software that enables quick provisioning of containers, multi-container management and configuration management. It allows quick scaling up of container resources by managing Docker hosts as clusters and allocating containers from one host to another.

To enable easy management of Docker Swarm, we setup an open source software called Shipyard in each VM. Its key feature was the GUI, which helped users to create, manage and scale their containers. A secure repository was configured in each VM for users to easily download and upload their Docker images. Here is the architecture of our oVirt cloud setup for Docker implementation.

 

oVirt-Docker

Docker Containers in oVirt

 

In this post, we will discuss the details of how we deployed Docker containers in oVirt.

1. Importing the OS image

For creating a VM with Docker support, an OS image with Docker service had to be used. We imported a minimal CentOS image with Docker support, from the oVirt external repository.

 

ovirt-docker-image

Choosing OS image with Docker service

 

2. Creating the first VM

We created the first VM with the downloaded OS image, as seen here:

 

oVirt-VM-create

Creating our first Docker VM

 

VM configuration parameters such as Authentication, Network, Hostname and memory were set and VM was created with Docker support.

3. Creating Docker containers

We created Docker containers in the VM with different images, specific to each application. A demo Docker VM is shown here.

 

docker-VM

Docker containers in VM

 

We then proceeded with installation and configuration of Shipyard GUI and the Docker Swarm. Providing Docker image repository and Shipyard GUI made things easy for end-users. The GUI helped users to easily create containers and scale them up.

[ Looking for custom plugins to manage your portals? Contact us to get tailor-made plugins to serve your business purposes. ]

The image repository was used to upload their Docker images and reuse them to create containers. The fully configured VM was secured and a template was created using it. This enabled easy cloning of more Docker VMs. We will discuss these details in our next post.

Fast provisioning is a core feature in any cloud hosting solution. Here we’ve covered how Docker VM provisioning was implemented for a server virtualization system. Bobcares helps cloud providers, data centers and web hosts deliver industry standard cloud services through custom configuration and maintenance of cloud systems.

 

LATEST - WHMCS PLUGIN FOR OVIRT

Efficient 2-in-1 WHMCS plugin for managing your oVirt VMs easily

CLICK HERE FOR WHMCS OVIRT PLUGIN

var google_conversion_label = "zWG9CLOojHIQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF