<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0);">Hey folks,</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">Sam had asked a reasonable set of questions regarding a patchset:</div>
<div style="color: rgb(0, 0, 0);"><a href="https://review.openstack.org/#/c/222893/">https://review.openstack.org/#/c/222893/</a></div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">The purpose of the patchset is to enable both RDO and RHOS as binary choices on RHEL platforms. I suspect over time, from-source deployments have the potential to become the norm, but the business logistics of such a change
are going to take some significant time to sort out.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">Red Hat has two distros of OpenStack neither of which are from source. One is free called RDO and the other is paid called RHOS. In order to obtain support for RHEL VMs running in an OpenStack cloud, you must be running on
RHOS RPM binaries. You must also be running on RHEL. It remains to be seen whether Red Hat will actively support Kolla deployments with a RHEL+RHOS set of packaging in containers, but my hunch says they will. It is in Kolla’s best interest to implement
this model and not make it hard on Operators since many of them do indeed want Red Hat’s support structure for their OpenStack deployments.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">Now to Sam’s questions:</div>
<div><span style="color: rgb(0, 0, 0); widows: 1; background-color: rgb(255, 255, 255);">"Where does 'binary' fit in if we have 'rdo' and 'rhos'? How many more do we add? What's our policy on adding a new type?</span>”</div>
<div style="color: rgb(0, 0, 0);"><span style="widows: 1; background-color: rgb(255, 255, 255);"><br>
</span></div>
<div style="widows: 1;">I’m not immediately clear on how binary fits in. We could make binary synonymous with the community supported version (RDO) while still implementing the binary RHOS version. Note Kolla does not “support” any distribution or deployment
of OpenStack – Operators will have to look to their vendors for support.</div>
<div style="widows: 1;"><br>
</div>
<div style="widows: 1;">As such the implied second question “How many more do we add?” sort of sounds like ‘how many do we support?”. The answer to the second question is none – again the Kolla community does not support any deployment of OpenStack. To the
question as posed, how many we add, the answer is it is really up to community members willing to implement and maintain the work. In this case, I have personally stepped up to implement RHOS and maintain it going forward.</div>
<div style="widows: 1;"><br>
</div>
<div style="widows: 1;">Our policy on adding a new type could be simple or onerous. I prefer simple. If someone is willing to write the code and maintain it so that is stays in good working order, I see no harm in it remaining in tree. I don’t suspect there
will be a lot of people interested in adding multiple distributions for a particular operating system. To my knowledge, and I could be incorrect, Red Hat is the only OpenStack company with a paid and community version available of OpenStack simultaneously
and the paid version is only available on RHEL. I think the risk of RPM based distributions plus their type count spiraling out of manageability is low. Even if the risk were high, I’d prefer to keep an open mind to facilitate an increase in diversity in
our community (which is already fantastically diverse, btw ;)</div>
<div style="widows: 1;"><br>
</div>
<div style="widows: 1;">I am open to questions, comments or concerns. Please feel free to voice them.</div>
<div style="widows: 1;"><br>
</div>
<div style="widows: 1;">Regards,</div>
<div style="widows: 1;">-steve</div>
<div style="widows: 1;"><br>
</div>
</body>
</html>