[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [rdo-list] [rdo] How does upgrades/hotfix scenarios work after integrating with RDO?



In general, RDO does not carry custom patches that have not yet landed
upstream and have been released, except in rare and carefully decided
circumstances with consensus from maintainers.

This allows RDO to be as "vanilla" as possible and, especially, test
with the same content and versions that the greater OpenStack
community develops and tests against.

So, if you have a bugfix for a package you would like to release in
RDO, it needs to:
1) Be merged in the upstream project
2) Be tagged in a dot release targetted at the ongoing stable release
(e.g, Ocata)
3) The spec file updated for the release accordingly (example here[1])
4) The rdoinfo reference to that package updated accordingly for the
-testing and -release tags (example here [2])
5) Once the package has been built, tagged and released, it will be
available as a package update from mirror.centos.org

For your scenario 2 and 3, the package will be available inside the
release's repositories so long as it is packaged and maintained.
If a customer upgrades from Ocata to Pike and wants to start using
your puppet module, he will be able to.

As far as installation and upgrade path, this is handled within the
installers (ex: Packstack, TripleO, Kolla), not within RDO itself.
RDO provides the packaging and the repositories, not the installation
or upgrade mechanisms.

[1]: https://github.com/rdo-packages/nova-distgit/commit/823152d9cf26768d1657881405a941dfdbcbba8e
[2]: https://github.com/redhat-openstack/rdoinfo/commit/b5bfbe4dea41e448179c342b5c6275a48a558bce

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Mon, Jul 17, 2017 at 11:02 AM, Dnyaneshwar Pawar
<Dnyaneshwar Pawar veritas com> wrote:
> Hi RDO Experts,
>
>
>
> I am trying to understand how does upgrades/hotfix scenarios work after
> integrating with RDO.
>
>
> Assuming that we will have single puppet-veritas_hyperscale for Pike, Queens
> etc...
> From IRC discussion (Thanks to amoralej.), I understand that we need to
> create branches for different releases as mentioned in branching document.
> Will also have to align our release schedule to that of RDO.
>
>
>
> Following points are not clear to me.
>
> Senario 1:
> Say, post Pike if we want to add bug fix to puppet-veritas_hyperscale, what
> should be the procedure to upgrade/apply fix where, customer has already
> configured veritas_hyperscale on top of Pike?
>
> Scenario 2:
> puppet-veritas_hyperscale is not supported on Ocata. If customer upgrades
> from Ocata to Pike, puppet-veritas_hyperscale should be available to
> customer.
> How does this gets handled?
>
> Senario 3:
> Customer upgrades from Pike to Queens. Would puppet-veritas_hypersclae be
> available to customer automatically?
>
>
>
> Thanks,
>
> Dnyaneshwar
>
>
> _______________________________________________
> rdo-list mailing list
> rdo-list redhat com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe redhat com


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]