Open Stack

At the moment it is not clear if OpenStack packages will be shipped with
Fedora releases in the future. I am clarifing this at the moment. The
packages from Fedora releases will be removed in favor of using the
packages provided in the RDO repository. Our Installation Guide already
uses the packages from the RDO repository.

Christian.

-------- Forwarded Message --------
Subject: Re: [Rdo-list] Juno vs Kilo in Fedora 22
Date: Mon, 13 Apr 2015 12:46:21 +0200
From: Alan Pevec <apevec at gmail.com>
To: Matthias Runge <mrunge at redhat.com>
CC: Rdo-list at redhat.com <rdo-list at redhat.com>

2015-04-10 19:23 GMT+02:00 Matthias Runge <mrunge at redhat.com>:
> Did we had an outcome of this?

Status is that we missed F22 Beta freeze on Mar 31, now fesco freeze
exception is required and Kilo import is still not completed in
Rawhide.
I'm also having second thoughts after thinking about Ihar's feedback
last week on IRC where he questioned whether the price of maintaining
openstack-* packages in stable Fedora is worth it when nobody is
actually using them. Until proven otherwise, we're assuming typical
OpenStack user on Fedora is interested in development and wants only
latest packages, so CVE fixes and upstream stable point release
updates are wasted. Production users are expected to run OpenStack on
EL platform, which we provide through RDO.

Instead of rushing Kilo into F22, I was thinking about the following model:
(1) keep latest OpenStack release in Fedora Rawhide, starting from
milestone2.
      Delorean stays RDO Trunk as a place for tracking changes on
OpenStack master branch.
(2) deprecate openstack-* in released Fedora to avoid maintenance
overhead for no use
(3) provide Fedora Rawhide builds for current and previous Fedora in RDO
repo
      e.g. Kilo would be available for F22 and F21 through RDO
(4) document that for production EL platform is recommended

We cannot retire packages in released Fedora, so I'm not sure about
the process for (2).
f20 branches should definitely be closed since Havana is EOL upstream
and in RDO, so there will be no further updates.
When I tried fedpkg retire in openstack-keystone f20 branch,
"dead.package" commit in dist-git worked[*] but then pkgdb step
failed.
Ideally, we would push an "empty" update which would warn installed
user base that they're running EOLed packages and should migrate to
RDO but I'm not sure there's such mechanism in Fedora Bodhi.
I'd appreciate any and all feedback on the above plan, please point
out the holes it might have.
If the plan makes sense, F22 would stay Juno and it would be
irrelevant which OpenStack release ends up in Fedora >= 23.


Cheers,
Alan

[*]
http://pkgs.fedoraproject.org/cgit/openstack-keystone.git/commit/?h=f20&id=2fdfdd6c8eac32334c2a5018fef196b041468979

_______________________________________________
Rdo-list mailing list
Rdo-list at redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list

To unsubscribe: rdo-list-unsubscribe at redhat.com



-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537