Updated rbovirt 0.0.36

Development
1

Hello,

I released rbovirt 0.0.36 backported version that brings some bugfixes
we need to have for Foreman:

https://github.com/abenari/rbovirt/commits/stable-0.0

Use bundler to update:

Packages on the way:

https://github.com/theforeman/foreman-packaging/pull/1067

Thanks for all involved for making this happen. It's a small step for
man…

··· -- Later, Lukas #lzap Zapletal
2

It would be useful to have a fog-ovirt gem too, extracting the provider
from Fog and shipping it independently. Updates can be made outside of
Fog's regular schedule (see fog-vsphere, -aws etc).

I wonder if you or the other new rbovirt maintainers would mind doing
this too?
https://github.com/fog/fog/wiki/Create-New-Provider-from-Scratch has
more info.

Almost all of our compute resources are now shipped like this, which
means we'll also be able to remove the dependency on 'fog' soon and
significantly reduce the installation size.

··· On 17/03/16 16:56, Lukas Zapletal wrote: > Hello, > > I released rbovirt 0.0.36 backported version that brings some bugfixes > we need to have for Foreman: > > https://github.com/abenari/rbovirt/commits/stable-0.0 > > Use bundler to update: > > https://rubygems.org/gems/rbovirt > > Packages on the way: > > https://github.com/theforeman/foreman-packaging/pull/1067 > > Thanks for all involved for making this happen. It's a small step for > man...

–
Dominic Cleal
dominic@cleal.org

3

Oh, I take that back - the Docker and DigitalOcean providers also need
extracting before this can happen.

··· On 30/03/16 08:52, Dominic Cleal wrote: > It would be useful to have a fog-ovirt gem too, extracting the provider > from Fog and shipping it independently. Updates can be made outside of > Fog's regular schedule (see fog-vsphere, -aws etc). > > I wonder if you or the other new rbovirt maintainers would mind doing > this too? > https://github.com/fog/fog/wiki/Create-New-Provider-from-Scratch has > more info. > > Almost all of our compute resources are now shipped like this, which > means we'll also be able to remove the dependency on 'fog' soon and > significantly reduce the installation size.

–
Dominic Cleal
dominic@cleal.org

4

> Oh, I take that back - the Docker and DigitalOcean providers also need
> extracting before this can happen.

Why before? I miss the reason somehow. Haven't followed all the steps to
follow yet.

··· -- Later, Lukas #lzap Zapletal
5

This was in reference to being able to remove the 'fog' gem dependency
and Bundler group from Foreman itself. While Docker and DigitalOcean Fog
providers remain in the main 'fog' gem, it'll need to remain.

Once oVirt, Docker and DigitalOcean providers are extracted from 'fog'
into fog-* gems, we can remove the dependency as nothing will be using it.

··· On 31/03/16 14:21, Lukas Zapletal wrote: >> Oh, I take that back - the Docker and DigitalOcean providers also need >> extracting before this can happen. > > Why before? I miss the reason somehow. Haven't followed all the steps to > follow yet.

–
Dominic Cleal
dominic@cleal.org

6

I think opennebula/one would also need extraction on the fog side then.

Regards

··· On Thu, Mar 31, 2016 at 02:25:08PM +0100, Dominic Cleal wrote: > Once oVirt, Docker and DigitalOcean providers are extracted from 'fog' > into fog-* gems, we can remove the dependency as nothing will be using it.

–
Michael Moll