Re: [ovirt-users] Docker images for oVirt engine

2017-06-05 Thread Jason Brooks
>
> Once the images are built, you can deploy the complete oVirt application
> running this:
>
>   make deploy

This is awesome, I've been playing w/ this on a centos host running
origin 1.5.1.

I've gotten stopped when I've tried to approve the host in the engine,
that fails with an error message like: "Host vdsc-ds-615nl
installation failed. Failed to get the session.." Any idea what what's
going wrong there?

Jason


>
> Would be great to have you testing this, giving feedback and reporting
> any issues you find. But be aware that this is in a very early stage of
> development and should be considered experimental.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-30 Thread Leni Kadali Mutungi
On 5/22/17, Leni Kadali Mutungi  wrote:
> Step 26/34 : RUN sed -i 's/multipathd.service //g'
> /usr/lib/systemd/system/vdsmd.service
>  ---> Running in 67d580645333
> sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or
> directory
> The command '/bin/sh -c sed -i 's/multipathd.service //g'
> /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
> Failed to build image 'ovirt/vdsc:master'
>
> Is vdsm a dependency for ovirt-containers? If so, how do I get the container
> to successfully locate the service it seems to be looking for?
It has occured to me that the error may be related to OpenShift and
how I'm using it. Is OpenShift supposed to be a service that is
running when building the oVirt container? How does it interact with
the ovirt-containers?

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-21 Thread Leni Kadali Mutungi
On 5/22/17, Leni Kadali Mutungi  wrote:
On 5/19/17, Juan Hernández  wrote:
> On 05/19/2017 05:20 AM, Leni Kadali Mutungi wrote:
>> Running `make build` went fine until I saw this error:
>>
>> Step 26/34 : RUN sed -i 's/multipathd.service //g'
>> /usr/lib/systemd/system/vdsmd.service
>>  ---> Running in 6a0948c94798
>> ERRO[0104] containerd: notify OOM events error=cgroup
>> path for memory not found
>> sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or
>> directory
>> The command '/bin/sh -c sed -i 's/multipathd.service //g'
>> /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
>> Failed to build image 'ovirt/vdsc:master'
>>
>> I tried restarting the Docker daemon and re-running `make build`,
>> since before this I got this error:
>>
>> Message from syslogd@localhost at May 19 06:07:57 ... kernel:[
>> 7498.623027] unregister_netdevice: waiting for lo to become free.
>> Usage count = 1
>>
>
> Did that restart of the docker daemon resolve the problem?
>
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself. The message says
> OOM, out of memory, is that machine low on memory maybe?
>
> Restart of the docker daemon does not solve the issue. Will try to see
> how the memory issue can be solved, since I have enough memory (8GB),
> so the problem is not hardware.

Seems to be a problem related to the Debian Kernel. cgroup swap
accounting is not enabled. I tried adding `cgroup_enable=memory
swapaccount=1` to the GRUB_CMDLINE_LINUX_DEFAULT option in
/etc/default/grub
after the `quiet` option. After this I ran `sudo update-grub` and
restarted my computer. The memory error has disappeared, the RUN sed
instruction error has not.

Step 26/34 : RUN sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service
 ---> Running in 67d580645333
sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or directory
The command '/bin/sh -c sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
Failed to build image 'ovirt/vdsc:master'

Is vdsm a dependency for ovirt-containers? If so, how do I get the container to
successfully locate the service it seems to be looking for?

CCing Oved Ourfali since Juan Hernández is on vacation till May 29th.

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-21 Thread Leni Kadali Mutungi
On 5/19/17, Juan Hernández  wrote:
> Did that restart of the docker daemon resolve the problem?
>
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself. The message says
> OOM, out of memory, is that machine low on memory maybe?

Restart of the docker daemon does not solve the issue. Will try to see
how the memory issue can be solved, since I have enough memory (8GB),
so the problem is not hardware.


-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-19 Thread Juan Hernández
On 05/19/2017 05:20 AM, Leni Kadali Mutungi wrote:
> Running `make build` went fine until I saw this error:
> 
> Step 26/34 : RUN sed -i 's/multipathd.service //g'
> /usr/lib/systemd/system/vdsmd.service
>  ---> Running in 6a0948c94798
> ERRO[0104] containerd: notify OOM events error=cgroup
> path for memory not found
> sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or 
> directory
> The command '/bin/sh -c sed -i 's/multipathd.service //g'
> /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
> Failed to build image 'ovirt/vdsc:master'
> 
> I tried restarting the Docker daemon and re-running `make build`,
> since before this I got this error:
> 
> Message from syslogd@localhost at May 19 06:07:57 ... kernel:[
> 7498.623027] unregister_netdevice: waiting for lo to become free.
> Usage count = 1
> 

Did that restart of the docker daemon resolve the problem?

As far as I can tell that 'RUN sed' instruction that failed is correct.
I just re-checked it in my environment and it works correctly. Looks
more like a resources issue or a bug in docker itself. The message says
OOM, out of memory, is that machine low on memory maybe?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-18 Thread Leni Kadali Mutungi
Running `make build` went fine until I saw this error:

Step 26/34 : RUN sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service
 ---> Running in 6a0948c94798
ERRO[0104] containerd: notify OOM events error=cgroup
path for memory not found
sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or directory
The command '/bin/sh -c sed -i 's/multipathd.service //g'
/usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2
Failed to build image 'ovirt/vdsc:master'

I tried restarting the Docker daemon and re-running `make build`,
since before this I got this error:

Message from syslogd@localhost at May 19 06:07:57 ... kernel:[
7498.623027] unregister_netdevice: waiting for lo to become free.
Usage count = 1

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-18 Thread Juan Hernández
On 05/18/2017 05:29 AM, Leni Kadali Mutungi wrote:
> On 5/15/17, Juan Hernández  wrote:
>> The tool that builds and deploy the containers to the OpenShift cluster
>> is a program written in Go. It is compiled when you run 'make ...'. That
>> means that you need to have the go development environment installed.
>> For example, in CentOS or Fedora:
>>
>>   yum -y install golang
>>
>> Once you have it installed, try again 'make build' and 'make deploy'.
>>
>> I'll try to update the documentation to explain that.
> 
> Installed Go. For some reason, building still refuses to work.
> 
> user@localhost:~/ovirt-containers$ sudo make build
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/tools"" go get ${godep}; \
> done
> GOPATH=""/tools"" go install ovirt/cmd/build
> can't load package: package ovirt/cmd/build: cannot find package
> "ovirt/cmd/build" in any of:
> /usr/lib/go-1.7/src/ovirt/cmd/build (from $GOROOT)
> /tools/src/ovirt/cmd/build (from $GOPATH)
> Makefile:40: recipe for target 'tools/bin/build' failed
> make: *** [tools/bin/build] Error 1
> 
> I looked at the tools/src/ovirt/cmd/build directory and it had the
> build.go file. I don't have the ovirt subdirectory in the
> /usr/lib/go-1.7/src/ directory. Any ideas on how to get it there?
> 

The problem is that the Makefile uses the current working directory to
setup the GOPATH. When you use 'sudo' the current working directory is
the home of the root user, hence the Makefile won't work. Please try to
run the build with a non-root user, just go into the the source
directory and type 'make build'.

You will also need to make sure that the user has docker permissions, if
you didn't do it yet. To do so just add it to the 'docker' group. For
example, in Fedora or RHEL:

  usermod -aG docker youruser

Note that once you do that you will need to re-login to make it effective.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-17 Thread Leni Kadali Mutungi
On 5/15/17, Juan Hernández  wrote:
> The tool that builds and deploy the containers to the OpenShift cluster
> is a program written in Go. It is compiled when you run 'make ...'. That
> means that you need to have the go development environment installed.
> For example, in CentOS or Fedora:
>
>   yum -y install golang
>
> Once you have it installed, try again 'make build' and 'make deploy'.
>
> I'll try to update the documentation to explain that.

Installed Go. For some reason, building still refuses to work.

user@localhost:~/ovirt-containers$ sudo make build
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
GOPATH=""/tools"" go install ovirt/cmd/build
can't load package: package ovirt/cmd/build: cannot find package
"ovirt/cmd/build" in any of:
/usr/lib/go-1.7/src/ovirt/cmd/build (from $GOROOT)
/tools/src/ovirt/cmd/build (from $GOPATH)
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 1

I looked at the tools/src/ovirt/cmd/build directory and it had the
build.go file. I don't have the ovirt subdirectory in the
/usr/lib/go-1.7/src/ directory. Any ideas on how to get it there?

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-15 Thread Juan Hernández
On 05/15/2017 05:24 AM, Leni Kadali Mutungi wrote:
> Managed to run the OpenShift cluster well enough. When I went into the
> ovirt-containers directory and tried to run `make build`, I got the
> following error:
> 
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/home/herabus/ovirt-containers/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: Permission denied
> Makefile:40: recipe for target 'tools/bin/build' failed
> make: *** [tools/bin/build] Error 127
> 
> So I ran `sudo make build` instead and got the following error:
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: not found
> Makefile:40: recipe for target 'tools/bin/build' failed
> make: *** [tools/bin/build] Error 127
> 
> Running `sudo make deploy` gave me this error:
> 
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: not found
> Makefile:40: recipe for target 'tools/bin/deploy' failed
> make: *** [tools/bin/deploy] Error 127
> 

The tool that builds and deploy the containers to the OpenShift cluster
is a program written in Go. It is compiled when you run 'make ...'. That
means that you need to have the go development environment installed.
For example, in CentOS or Fedora:

  yum -y install golang

Once you have it installed, try again 'make build' and 'make deploy'.

I'll try to update the documentation to explain that.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-14 Thread Leni Kadali Mutungi
Managed to run the OpenShift cluster well enough. When I went into the
ovirt-containers directory and tried to run `make build`, I got the
following error:

for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/home/herabus/ovirt-containers/tools"" go get ${godep}; \
done
/bin/sh: 2: go: Permission denied
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 127

So I ran `sudo make build` instead and got the following error:
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
/bin/sh: 2: go: not found
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 127

Running `sudo make deploy` gave me this error:

for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
/bin/sh: 2: go: not found
Makefile:40: recipe for target 'tools/bin/deploy' failed
make: *** [tools/bin/deploy] Error 127




-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-11 Thread Juan Hernández
On 05/11/2017 08:54 AM, Barak Korren wrote:
> On 11 May 2017 at 06:02, Leni Kadali Mutungi  wrote:
>>> On 5/10/17, Barak Korren  wrote:
 That one is obsolete AFAIK. The oVirt container images are now being
 worked on in the 'ovirt-containers' repo.
>>
>> Checked it out. It seems more complicated than what I need, which
>> would be just a Dockerfile that pulls the required image. The
>> ovirt-containers repo seems to have a dependency on OpenCluster, which
>> I think I won't need since I'm after a basic install on one machine
>> for documentation purposes. Your advice is appreciated.
> 
> Adding ovirt-containers developers. Yaniv, Juan, Fabian, Sandro,
> Simone - can ovirt-containers be used for his purpose?
> 
> Also adding Rgolan since he did work in the past on a containerized
> dev environment for oVirt.
> 
> If you just want your own little oVirt install "in a box" for
> testing/dev purposes, you can look at Lago and the ovirt-system-tests
> projects.
> 
> 

You may be able to use the engine container independently, with some
effort. But this 'ovirt-containers' project isn't certainly intended for
that simple use case, it is intended to be able to deploy the complete
oVirt system in an OpenShift cluster.

If you are willing to give this a try, and you already have a docker
installation, creating an OpenShift cluster for testing purposes is
really simple. You can use 'oc cluster up'. It is a matter of
downloading the 'oc' tool from here:


https://github.com/openshift/origin/releases/download/v1.5.0/openshift-origin-client-tools-v1.5.0-031cbe4-linux-64bit.tar.gz

That contains the 'oc' binary. Put it in your path and then run this
command:

  oc cluster up

That will pull all the required images, and configure a simple OpenShift
cluster into your machine. Once that completes you can proceed to deploy
the oVirt application. First you need to build the images, as they
aren't yet available in a public repository. To build the images
checkout the code of the project:

  git clone git://gerrit.ovirt.org/ovirt-containers

Then go into that directory and run this:

  make build

That will take quite a long time, as it needs to build all the images,
and it requires downloading of the base images and of the RPMs that go
into the images being built. Be patient.

Once the images are built, you can deploy the complete oVirt application
running this:

  make deploy

Would be great to have you testing this, giving feedback and reporting
any issues you find. But be aware that this is in a very early stage of
development and should be considered experimental.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-11 Thread Barak Korren
On 11 May 2017 at 06:02, Leni Kadali Mutungi  wrote:
>> On 5/10/17, Barak Korren  wrote:
>>> That one is obsolete AFAIK. The oVirt container images are now being
>>> worked on in the 'ovirt-containers' repo.
>
> Checked it out. It seems more complicated than what I need, which
> would be just a Dockerfile that pulls the required image. The
> ovirt-containers repo seems to have a dependency on OpenCluster, which
> I think I won't need since I'm after a basic install on one machine
> for documentation purposes. Your advice is appreciated.

Adding ovirt-containers developers. Yaniv, Juan, Fabian, Sandro,
Simone - can ovirt-containers be used for his purpose?

Also adding Rgolan since he did work in the past on a containerized
dev environment for oVirt.

If you just want your own little oVirt install "in a box" for
testing/dev purposes, you can look at Lago and the ovirt-system-tests
projects.


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-10 Thread Leni Kadali Mutungi
> On 5/10/17, Barak Korren  wrote:
>> That one is obsolete AFAIK. The oVirt container images are now being
>> worked on in the 'ovirt-containers' repo.

Checked it out. It seems more complicated than what I need, which
would be just a Dockerfile that pulls the required image. The
ovirt-containers repo seems to have a dependency on OpenCluster, which
I think I won't need since I'm after a basic install on one machine
for documentation purposes. Your advice is appreciated.

-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-10 Thread Leni Kadali Mutungi
On 5/10/17, Barak Korren  wrote:
> That one is obsolete AFAIK. The oVirt container images are now being
> worked on in the 'ovirt-containers' repo.
>
> GitHub generally contains a read-only mirror on the oVirt sources,
> development work for most projects is done via gerrit.ovirt.org.
>
Thank you. Found it.


-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Docker images for oVirt engine

2017-05-10 Thread Barak Korren
On 10 May 2017 at 17:46, Leni Kadali Mutungi  wrote:
> I noticed that there had been some discussion regarding Docker images
> in the devel mailing list. I wanted to confirm that this:
> https://github.com/oVirt/ovirt-container-engine is alright to use with
> Docker. If this isn't the official source to use, pointers in the
> right direction would appreciated.

That one is obsolete AFAIK. The oVirt container images are now being
worked on in the 'ovirt-containers' repo.

GitHub generally contains a read-only mirror on the oVirt sources,
development work for most projects is done via gerrit.ovirt.org.

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users