[Rdo-list] Request for testing: CentOS-7-x86_64 Generic Cloud image

[Kodiak Firesmith]

Has anyone proven that messing with what /etc/redhat-release returns will
not break Puppet's Facter operations related to OS release level?
(And maybe some of the other config managers, but I'm not familiar...)

This is a curiousity I may be able to test today.  We use Puppet's
osmajrelease in a case statement that hands out rhel 5/6/7 specific configs.

In my environment I rely on conveying image freshness via the image name,
which ends in 2014mm-r##.

-Kodiak
On Aug 28, 2014 4:36 AM, "Karanbir Singh" <mail-lists at karan.org> wrote:

> On 08/27/2014 09:54 PM, whayutin wrote:
> > On Wed, 2014-08-27 at 11:40 +0100, Karanbir Singh wrote:
> >> hi
> >>
> >> I've just pushed a GenericCloud image, that will become the gold
> >> standard to build all varients and environ specific images from.
> >> Requesting people to help test this image :
> >>
> >>
> http://cloud.centos.org/centos/7/devel/CentOS-7-x86_64-GenericCloud-20140826_02.qcow2
> >> ( ~ 922 MB)
> >> or
> >>
> http://cloud.centos.org/centos/7/devel/CentOS-7-x86_64-GenericCloud-20140826_02.qcow2.xz
> >> ( 261 MB)
> >>
> >> Sha256's;
> >>
> >> 3c049c21c19fb194cefdddbac2e4eb6a82664c043c7f2c7261bbeb32ec64023f
> >> CentOS-7-x86_64-GenericCloud-20140826_02.qcow2
> >> 4a16ca316d075b30e8fdc36946ebfd76c44b6882747a6e0c0e2a47a8885323b1
> >> CentOS-7-x86_64-GenericCloud-20140826_02.qcow2.xz
> >>
> >> please note: these images contain unsigned content ( cloud-init and
> >> cloud-utils-* ), and are therefore unsuiteable for use beyond validation
> >> on your environment.
> >>
> >> regards,
> >>
> >
> > Hey Karanbir,
> > Most everything seems to be working with the image, thank you for
> > posting it!!  Hopefully the CentOS release can be fixed, I believe it
> > should return 7.0
> >
> > e.g.
> > [centos at packstack ~]$ cat /etc/redhat-release
> > CentOS Linux release 7.0.1406 (Core)
>
> how much and where is this causing a problem ?
>
> We are trying to message around the idea that effectively there is no
> distro 7.0 or 7.1 etc, they are just various points in time on the
> CentOS-7 distro. We went through quite a few iterations around naming
> and numbering and adding a datestmp to the release number was the only
> really 'acceptable' setup. The 1406 then indicates age of the .0 base.
>
>
> >
> > The rdo public ci has successfully completed a packstack allinone run on
> > CentOS-7.0 [1] w/ a few workarounds.  I'll start to setup a foreman
> > based install soon.
>
> sounds good.
>
> We will have regular image builds up soon, would it be possible for you
> to automate a new-image-get and deploy, say every two weeks perhaps ?
>
> >
> > Thanks!!
> >
> > [1]
> https://prod-rdojenkins.rhcloud.com/job/khaleesi-rdo-icehouse-production-centos-70-aio-packstack-neutron-gre-rabbitmq/20/console
> > https://prod-rdojenkins.rhcloud.com/
> >
> > Workarounds used:
> > http://openstack.redhat.com/Workarounds
> >
> https://github.com/redhat-openstack/khaleesi/blob/master/workarounds/workarounds-pre-run-packstack.yml
> >
>
> nice!
>
>
> --
> Karanbir Singh
> +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
> GnuPG Key : http://www.karan.org/publickey.asc
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20140828/5382b157/attachment.html>