[tripleo] move os-refresh-config, os-collect-config, tripleo-ipsec to 'release-management': none

Marios Andreou marios at redhat.com
Tue Jan 12 10:07:14 UTC 2021


On Mon, Jan 11, 2021 at 5:07 PM Herve Beraud <hberaud at redhat.com> wrote:

>
>
> Le lun. 11 janv. 2021 à 15:27, Alex Schultz <aschultz at redhat.com> a
> écrit :
>
>> On Mon, Jan 11, 2021 at 4:59 AM Marios Andreou <marios at redhat.com> wrote:
>> >
>> > Hi TripleO,
>> >
>> > you may have seen the thread started by Herve at [1] around the
>> deadline for making a victoria release for os-refresh-config,
>> os-collect-config and tripleo-ipsec.
>> >
>> > This message is to ask if anyone is still using these? In particular
>> would anyone mind if we stopped making tagged releases, as discussed at
>> [2]. Would someone mind if there was no stable/victoria branch for these
>> repos?
>> >
>> > For the os-refresh/collect-config I suspect the answer is NO - at
>> least, we aren't using these any more in the 'normal' tripleo deployment
>> for a good while now, since we switched to config download by default. We
>> haven't even created an ussuri branch for these [3] and no one has shouted
>> about that (or at least not loud enough I haven't heard anything).
>>
>> Maybe switch to independent?  That being said as James points out they
>> are still used by Heat so maybe the ownership should be moved.
>>
>
> I agree, moving them to the independent model could be a solution, in this
> case the patch could be adapted to reflect that choice and we could ignore
> these repos from victoria deadline point of view.
>
> Concerning the "ownership" side of the question this is more an internal
> discussion between teams and eventually the TC, I don't think that that
> will impact us from a release management POV.
>
>
ack yes this makes sense thanks James, Alex, Herve and Rabi for your
comments
First I'll refactor https://review.opendev.org/c/openstack/releases/+/769915
to instead move them to independent (and i'll also include
os-apply-config). Then I'll reach out to Heat PTL to see what they think
about the transfer of ownership,

thanks all



>
>> >
>> > For tripleo-ipsec it *looks* like we're still using it in the sense
>> that we carry the template and pass the parameters in
>> tripleo-heat-templates [4]. However we aren't running that in any CI job as
>> far as I can see, and we haven't created any branches there since Rocky. So
>> is anyone using tripleo-ipsec?
>> >
>>
>> I think tripleo-ipsec is no longer needed as we now have proper
>> tls-everywhere support. We might want to revisit this and
>> deprecate/remove it.
>>
>> > Depending on the answers here and as discussed at [2] I will move to
>> make these as unreleased (release-management: none in openstack/governance
>> reference/projects.yaml) and remove the release file altogether.
>> >
>> > For now however and given the deadline of this week for a victoria
>> release I am proposing that we move forward with [2] and cut the victoria
>> branch for these.
>> >
>> > thanks for reading and please speak up if any of the above are
>> important to you!
>> >
>> > thanks, marios
>> >
>> > [1]
>> http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019730.html
>> > [2]
>> https://review.opendev.org/c/openstack/releases/+/769915/1/deliverables/victoria/os-refresh-config.yaml
>> > [3] https://pastebin.com/raw/KJ0JxKPx
>> > [4]
>> https://opendev.org/openstack/tripleo-heat-templates/src/commit/9fd709019fdd36d4c4821b2486e7151abf84bc3f/deployment/ipsec/ipsec-baremetal-ansible.yaml#L101-L106
>> >
>>
>>
>
> --
> Hervé Beraud
> Senior Software Engineer at Red Hat
> irc: hberaud
> https://github.com/4383/
> https://twitter.com/4383hberaud
> -----BEGIN PGP SIGNATURE-----
>
> wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
> Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
> RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
> F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
> 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
> glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
> m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
> hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
> qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
> F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
> B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
> v6rDpkeNksZ9fFSyoY2o
> =ECSj
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210112/197f84ec/attachment-0001.html>


More information about the openstack-discuss mailing list