[gluster-packaging] gdeploy-2.0.11 available for testing

[Niels de Vos]

On Tue, Feb 05, 2019 at 05:01:04PM +0530, Sachidananda URS wrote:
> On Thu, Jan 31, 2019 at 5:06 PM Niels de Vos <ndevos at redhat.com> wrote:
> 
> > On Thu, Jan 31, 2019 at 02:48:13PM +0530, Sachidananda URS wrote:
> > > On Thu, Jan 31, 2019 at 2:27 PM Niels de Vos <ndevos at redhat.com> wrote:
> > >
> > > > On Thu, Jan 31, 2019 at 09:37:15AM +0530, Ramakrishna Reddy Yekulla
> > wrote:
> > > > > On Tue, Jan 29, 2019 at 4:26 PM Niels de Vos <ndevos at redhat.com>
> > wrote:
> > > > >
> > > > > > gdeploy-2.0.11-1.el7 is available in the centos-gluster*-test
> > > > > > repositories from the CentOS Storage SIG. Please test the update
> > and
> > > > let
> > > > > > me know when the package can be marked for release.
> > > > > >
> > > > > >   # yum install centos-release-gluster
> > > > > >   # yum install --enablerepo=centos-gluster*-test gdeploy
> > > > > >   (test, test, test, ..)
> > > > > >
> > > > >
> > > > > It works, I have testing the install , remove and upgrade. The
> > Ansible >
> > > > > 2.5 pre requisites needs to
> > > > > be take care of.
> > > >
> > > > Can you explain what you mean to say with this? Is ansible > 2.5 not
> > > > availble in the standard repositories and you got the version from
> > > > somewhere else?
> > > >
> > > >
> > > Yeah, he was not able to get it from standard repository. User can get
> > one
> > > from EPEL or other repository.
> >
> > The content sets from the CentOS SIGs may not rely on 3rd party
> > repositories. That means we would have to include ansible 2.5+ somehow
> > in our repositories. I need to check how other SIGs do this, and what
> > the most suitable way for us is. Until that is resolved, we can't
> > release this update yet.
> >
> 
> Niels, I see a user comment:
> https://bugzilla.redhat.com/show_bug.cgi?id=1671559#c5
> that they get the Ansible from ovirt repo. Who are the sole consumers of
> gdeploy for
> setting up RHHI. Is it ok to release the package for their benefit?

It is not possible to release the package for a single project, but not
for others. The ansible dependency would still be a problem for all
other users that do not have the ovirt repository enabled.

However oVirt picks gdeploy from the testing repository. So it may get
included in a next oVirt build? Not sure how that works though...

https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;f=hc-basic-suite-master/reposync-config.repo;hb=HEAD#l63

Niels