The Gluster Blog

Gluster blog stories provide high-level spotlights on our users all over the world

Ovirt + Docker

Gluster
2014-07-30

A small blog on how to put Ovirt inside a docker.

Install docker on your system.

Get an account in docker.

pull a base image from docker which ovirt supports. For example : Fedora and centos.

Let us install ovirt on centos, by pulling centos base image from docker.

Instructions to follow:

docker run -i -t centos /bin/bash – user will be logged into the bash prompt of centos machine.

Now install all the packages which ovirt requires on top of centos base image.

As a first step, add the official ovirt repository by running the command “yum localinstall http://resources.ovirt.org/releases/ovirt-release.noarch.rpm”

Add / enable the epel repo by running the command “rpm -ivh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm”

Install ovirt-engine by running the command “yum install -y ovirt-engine”

Before running the engine-setup, make sure /etc/sysconfig/network is present with the following contents

NETWORKING=yes
HOSTNAME=localhost.localdomain

With out the above, postgresql will not start and data base would not be created.

Run the engine-setup command , and when prompted with a question, “Do you wish to setup firewall as IPtables?” Input the answer as “No”, otherwise execution fail.

Once engine setup is done, browse through the URL “https://<ip>/ovirt-engine&#8221;.

Pushing Image back to docker central repository

To push the repository, user need to peform the below repository.

Exit from the centos with ovirt installed base image .

Run the command to commit the image which has been created recently “docker commit <commitid>  <docker_username>/<give the name for your image>”

Now push the docker image to the central repository so that others can make use of that by running the command “docker push <docker_username>/<name of newly created user>

That is it !!! Now newly created image that is centos + ovirt is pushed to the central repository.

You can verify the same by searching for the image pushed . Run the command “docker search <newly created docker image>”

There you go, in the result set returned you should see an image pushed by you.

 

 

 

BLOG

  • 03 Feb 2020
    Building a longer term focus for Gl...

    The initial rounds of conversation around the planning of content for release 8 has helped the project identify one key thing – the need to stagger out features and enhancements over multiple releases. Thus, while release 8 is unlikely to be feature heavy as previous releases, it will be the...

    Read more
  • 28 Nov 2019
    Planning ahead for Gluster releases

    In order to plan the content for upcoming releases, it is good to take a moment of pause, step back and attempt to look at the consumption of GlusterFS within large enterprises. With the enterprise architecture taking large strides towards cloud and more specifically, the hybrid cloud, continued efforts towards...

    Read more
  • 13 Nov 2019
    Announcing Gluster 7.0

    The Gluster community is pleased to announce the release of 7.0, our latest release. This is a major release that includes a range of code improvements and stability fixes along with a few features as noted below. A selection of the key features and bugs addressed are documented in this...

    Read more