<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 15px; font-family: Calibri, sans-serif;">
<div>Please add me too to the list!</div>
<div><br>
</div>
<div>Regards,</div>
<div>Vikram Hosakote</div>
<div>IRC: vhosakot</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Michał Jastrzębski <<a href="mailto:inc007@gmail.com">inc007@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, April 30, 2016 at 9:58 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote<br>
</div>
<div><br>
</div>
<div>
<div>
<div>Add me too please Steven.</div>
<div><br>
</div>
<div>On 30 April 2016 at 09:50, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>> wrote:</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>Fellow core reviewers,</div>
<div><br>
</div>
<div>We had a fantastic turnout at our fishbowl kubernetes as an underlay for</div>
<div>Kolla session. The etherpad documents the folks interested and discussion</div>
<div>at summit[1].</div>
<div><br>
</div>
<div>This proposal is mostly based upon a combination of several discussions at</div>
<div>open design meetings coupled with the kubernetes underlay discussion.</div>
<div><br>
</div>
<div>The proposal (and what we are voting on) is as follows:</div>
<div><br>
</div>
<div>Folks in the following list will be added to a kolla-k8s-core group.</div>
<div><br>
</div>
<div> This kolla-k8s-core group will be responsible for code reviews and code</div>
<div>submissions to the kolla repository for the /kubernetes top level directory.</div>
<div>Individuals in kolla-k8s-core that consistently approve (+2) or disapprove</div>
<div>with a (-2) votes to TLD directories other then kubernetes will be handled</div>
<div>on a case by case basis with several "training warnings" followed by removal</div>
<div>of the kolla-k8s-core group. The kolla-k8s-core group will be added as a</div>
<div>subgroup of the kolla-core reviewer team, which means they in effect have</div>
<div>all of the ACL access as the existing kolla repository. I think it is</div>
<div>better in this case to trust these individuals to the right thing and only</div>
<div>approve changes for the kubernetes directory until proposed for the</div>
<div>kolla-core reviewer group where they can gate changes to any part of the</div>
<div>repository.</div>
<div><br>
</div>
<div>Britt Houser</div>
<div><br>
</div>
<div>mark casey</div>
<div><br>
</div>
<div>Steven Dake (delta-alpha-kilo-echo)</div>
<div><br>
</div>
<div>Michael Schmidt</div>
<div><br>
</div>
<div>Marian Schwarz</div>
<div><br>
</div>
<div>Andrew Battye</div>
<div><br>
</div>
<div>Kevin Fox (kfox1111)</div>
<div><br>
</div>
<div>Sidharth Surana (ssurana)</div>
<div><br>
</div>
<div> Michal Rostecki (mrostecki)</div>
<div><br>
</div>
<div> Swapnil Kulkarni (coolsvap)</div>
<div><br>
</div>
<div> MD NADEEM (mail2nadeem92)</div>
<div><br>
</div>
<div> Vikram Hosakote (vhosakot)</div>
<div><br>
</div>
<div> Jeff Peeler (jpeeler)</div>
<div><br>
</div>
<div> Martin Andre (mandre)</div>
<div><br>
</div>
<div> Ian Main (Slower)</div>
<div><br>
</div>
<div>Hui Kang (huikang)</div>
<div><br>
</div>
<div>Serguei Bezverkhi (sbezverk)</div>
<div><br>
</div>
<div>Alex Polvi (polvi)</div>
<div><br>
</div>
<div>Rob Mason</div>
<div><br>
</div>
<div>Alicja Kwasniewska</div>
<div><br>
</div>
<div>sean mooney (sean-k-mooney)</div>
<div><br>
</div>
<div>Keith Byrne (kbyrne)</div>
<div><br>
</div>
<div>Zdenek Janda (xdeu)</div>
<div><br>
</div>
<div>Brandon Jozsa (v1k0d3n)</div>
<div><br>
</div>
<div>Rajath Agasthya (rajathagasthya)</div>
<div><br>
</div>
<div><br>
</div>
<div>If you already are in the kolla-core review team, you won't be added to the</div>
<div>kolla-k8s-core team as you will already have the necessary ACLs to do the</div>
<div>job. If you feel you would like to join this initial bootstrapping process,</div>
<div>please add your name to the etherpad in [1].</div>
<div><br>
</div>
<div>After 8 weeks (July 15h), folks that have not been actively reviewing or</div>
<div>committing code will be removed from the kolla-k8s-core group. We will use</div>
<div>the governance repository metrics for team size [2] which is either 30</div>
<div>reviews over 6 months (in this case, 10 reviews), or 6 commits over 6 months</div>
<div>(in this case 2 commits) to the repository. Folks that don't meet the</div>
<div>qualifications are still welcome to commit to the repository and contribute</div>
<div>code or documentation but will lose approval rights on patches.</div>
<div><br>
</div>
<div>The kubernetes codebase will be maintained in the</div>
<div><a href="https://github.com/openstack/kolla">https://github.com/openstack/kolla</a> repository under the kubernees top level</div>
<div>directory. Contributors that become active in the kolla repository itself</div>
<div>will be proposed over time to the kolla-core group. Only core-kolla members</div>
<div>will be permitted to participate in policy decisions and voting thereof, so</div>
<div>there is some minimal extra responsibility involved in joining the</div>
<div>kolla-core ACL team for those folks wanting to move into the kolla core team</div>
<div>over time. The goal will be to over time entirely remove the kolla-k8s-core</div>
<div>team and make one core reviewer team in the kolla-core ACL.</div>
<div><br>
</div>
<div>Members in the kolla-k8s-core group will have the ability to +2 or –2 any</div>
<div>change to the main kolla repository via ACLs, however, I propose we trust</div>
<div>these folks to only +2/-2 changes related to the kubernetes directory in the</div>
<div>kolla repository and remove folks that consistently break this agreement.</div>
<div>Initial errors as folks learn the system will be tolerated and commits</div>
<div>reverted as makes sense.</div>
<div><br>
</div>
<div>I feel we made a couple errors with the creation of Kolla-mesos that I feel</div>
<div>needs correction. Our first error the kolla-mesos-core team made a lack of</div>
<div>a diversely affiliated team membership developing the code base. The above</div>
<div>list has significant diversity. The second error is that the repository was</div>
<div>split in the first place. This resulted in a separate ABI to the containers</div>
<div>being implemented which was a sore spot for me personally. We did our best</div>
<div>to build both sides of the bridge here, but this time I'd like the bridge</div>
<div>between these two interests and set of individuals to be fully built before</div>
<div>beginning. As such, I'd ask the existing kolla-core team to trust my</div>
<div>judgement on this point and roll with it. We can always change the</div>
<div>structure later if this model doesn't work out as I expect it will, but if</div>
<div>we started with split repos and a changed structure to begin with, we can't</div>
<div>go back to a non-split repo as the action is irreversible according to dims.</div>
<div><br>
</div>
<div>I know this proposal may seem uncomfortable for our existing kolla-core</div>
<div>team. I can assure you based upon twenty years of open source participation</div>
<div>this will result in a better outcome. We had talked about splitting the</div>
<div>repositories, and our plan around that is to punt until such action is</div>
<div>absolutely necessary. Keeping things in one repository can always be split</div>
<div>later, but a premature split can never be undone without losing git commit</div>
<div>history.</div>
<div><br>
</div>
<div>We will mark the kubernetes orchestration in Kolla as experimental until</div>
<div>existing feature parity is achieved in the kolla CLI tool. After the</div>
<div>initial implementation is ready, we will mark it as ready for evaluation.</div>
<div>At the conclusion of Newton, assuming the implementation works well, we will</div>
<div>mark the implementation as "production ready", just as our current Ansible</div>
<div>orchestrated implementation is recorded.</div>
<div><br>
</div>
<div>** All CLI features of the kolla-ansible shell script to be implemented for</div>
<div>"ready-for-evaluation" stage. **</div>
<div><br>
</div>
<div>This includes the following CLI operations where they make sense:</div>
<div><br>
</div>
<div>Prechecks</div>
<div>mariadb_recvoery</div>
<div>Deploy</div>
<div>Post-deploy</div>
<div>Pull</div>
<div>Upgrade</div>
<div>Reconfgiure</div>
<div>Certificates</div>
<div><br>
</div>
<div>As part of this change, I will be submitting a change to rename</div>
<div>kolla-ansible to kolla with appropriate documentation changes. This one</div>
<div>shell script will in the future will read from globals.yml a yaml variable</div>
<div>which is "orchestratoin_engine" which may be either ansible or kubernetes.</div>
<div>In this way, the terminology I strongly dislike "first class citizen" will</div>
<div>be removed from our lexicon in the Kolla repository. Instead of first</div>
<div>class/second class citizen, we will have all orchestration systems as "first</div>
<div>class citizens" with varying levels of maturity.</div>
<div><br>
</div>
<div>Please vote +1 if in favor, -1 if not in favor. 7 votes will trigger early</div>
<div>closing of the vote and the creation of the kubernetes directory with a</div>
<div>README.rst. The voting will remain open for 1 week until May 6th unless a</div>
<div>majority is reached prior to the voting window closing. I would appreciate</div>
<div>a quick turnaround on the voting so the work can begin rapidly. If you have</div>
<div>arguments with this approach I'd like to hear them. If they involve the</div>
<div>concept of trust, I'd ask you to keep in mind we are a community working</div>
<div>towards a common goal with common objectives, and to trust until given</div>
<div>reason otherwise.</div>
<div><br>
</div>
<div>[1]</div>
<div><a href="https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kubernetes-underlay">https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kubernetes-underlay</a></div>
<div>[2]</div>
<div><a href="https://github.com/openstack/governance/blob/master/tools/teamstats.py#L32">https://github.com/openstack/governance/blob/master/tools/teamstats.py#L32</a></div>
<div><br>
</div>
<div><br>
</div>
<div>__________________________________________________________________________</div>
<div>OpenStack Development Mailing List (not for usage questions)</div>
<div>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>__________________________________________________________________________</div>
<div>OpenStack Development Mailing List (not for usage questions)</div>
<div>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>