<html><body><p>Chris, thanks so much! I will put up the new patch to reflect our decided new structure very soon. Really appreciate your help on doing this important work.<br><br>Tong Li<br>IBM Open Technology<br>Building 501/B205<br>litong01@us.ibm.com<br><br><img width="16" height="16" src="cid:1__=0ABB0AEEDFDF80598f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Christopher Aedo ---12/01/2016 10:47:01 PM---On Wed, Nov 16, 2016 at 4:05 PM, Christopher Aedo <doc@a"><font color="#424282">Christopher Aedo ---12/01/2016 10:47:01 PM---On Wed, Nov 16, 2016 at 4:05 PM, Christopher Aedo <doc@aedo.net> wrote: > On Fri, Nov 11, 2016 at 9:</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Christopher Aedo <doc@aedo.net></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">defcore-committee <defcore-committee@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/01/2016 10:47 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [OpenStack-DefCore] [Interop] New Repository</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>On Wed, Nov 16, 2016 at 4:05 PM, Christopher Aedo <doc@aedo.net> wrote:<br>> On Fri, Nov 11, 2016 at 9:17 AM, Christopher Aedo <doc@aedo.net> wrote:<br>>> On 11/11/16, Tong Li <litong01@us.ibm.com> wrote:<br>>>><br>>>> Chris,<br>>>> Thanks so much for doing this important work. Please let me know what I<br>>>> can do to help. If we do have a new repository, I will be very happy to<br>>>> move all the stuff we have in contrib repository over to the new one. We<br>>>> can also structure the entire directory a bit better. We can talk about all<br>>>> these things on coming Wednesday meeting. Chris, can you come to the<br>>>> Wednesday meeting UTC 1500 at<br>>>> </tt><tt><a href="http://webchat.freenode.net/?channels=openstack-meeting-cp">http://webchat.freenode.net/?channels=openstack-meeting-cp</a></tt><tt><br>>><br>>> I'm glad to hear there's support for this :) I should be able to make<br>>> that meeting next week, look forward to coordinating next steps.<br>><br>> In this mornings Interop Challenge meeting[1] we agreed to call the<br>> repository "interop-workloads". I threw together a PR to request the<br>> repo[2] and at this point it looks good so will just need the Infra<br>> cores to review and merge.<br>><br>> Along the way I also created a launchpad project[3] for this. This<br>> will allow you to create blueprints for all the different efforts<br>> you're planning (and any PRs can reference blueprints or bugs).<br>><br>> [1]: </tt><tt><a href="https://etherpad.openstack.org/p/interop-challenge-postmortem">https://etherpad.openstack.org/p/interop-challenge-postmortem</a></tt><tt><br>> [2]: </tt><tt><a href="https://review.openstack.org/398533">https://review.openstack.org/398533</a></tt><tt><br>> [3]: </tt><tt><a href="https://launchpad.net/interop-workloads">https://launchpad.net/interop-workloads</a></tt><tt><br><br>The repository has been created[1] and the gerrit group[2] has also<br>been created. I was not able to find all the IDs specified in the<br>etherpad to add as initial cores, but many of the accounts have been<br>added. At this time Brad or anyone else on that list can add the<br>others as needed.<br><br>Let me know if I can be of any further help here!<br><br>[1]: </tt><tt><a href="https://git.openstack.org/cgit/openstack/interop-workloads">https://git.openstack.org/cgit/openstack/interop-workloads</a></tt><tt><br>[2]: </tt><tt><a href="https://review.openstack.org/#/admin/groups/1651,members">https://review.openstack.org/#/admin/groups/1651,members</a></tt><tt><br><br>-Christopher<br><br><br>><br>><br>>> -Christopher<br>>><br>>>><br>>>> Thanks.<br>>>><br>>>> Tong Li<br>>>> IBM Open Technology<br>>>> Building 501/B205<br>>>> litong01@us.ibm.com<br>>>><br>>>><br>>>><br>>>> From: Rochelle Grober <rochelle.grober@huawei.com><br>>>> To: Christopher Aedo <doc@aedo.net>, Caleb Boylan<br>>>> <caleb.boylan@dreamhost.com><br>>>> Cc: defcore-committee <defcore-committee@lists.openstack.org><br>>>> Date: 11/10/2016 08:17 PM<br>>>> Subject: Re: [OpenStack-DefCore] [Interop] New Repository<br>>>><br>>>><br>>>><br>>>> Sounds like a plan to me :-)<br>>>><br>>>> Tong Li is critical for Core for this repo at the moment. But it would be<br>>>> good to have someone else who could also actively track and review<br>>>> additions/changes, etc.<br>>>><br>>>> I also think we might consider planning a "third party CI" type account or<br>>>> something so that when changes go in, all the interop vendors can<br>>>> automatically verify they haven't been broken.<br>>>><br>>>> I'd love to see this happen.<br>>>><br>>>> Might be able to put a cycle or two into it.<br>>>><br>>>> --Rocky<br>>>><br>>>> -----Original Message-----<br>>>> From: Christopher Aedo [</tt><tt><a href="mailto:doc@aedo.net">mailto:doc@aedo.net</a></tt><tt>]<br>>>> Sent: Thursday, November 10, 2016 10:18 AM<br>>>> To: Caleb Boylan<br>>>> Cc: defcore-committee<br>>>> Subject: Re: [OpenStack-DefCore] [Interop] New Repository<br>>>><br>>>> On Wed, Nov 9, 2016 at 9:08 AM, Caleb Boylan <caleb.boylan@dreamhost.com><br>>>> wrote:<br>>>>> Hi everyone,<br>>>>><br>>>>> Great to see you all in Barcelona, the demo during the keynotes was<br>>>>> great! I think it would be great to get the playbooks and scripts into<br>>>>> the hand of end users that are using OpenStack clouds. There has been<br>>>>> talk of moving the Interop stuff into a separate repository (from the<br>>>>> osops-tools-contrib repository). I think this would be beneficial as<br>>>>> it is less confusing than having it in the same repository as other<br>>>>> scripts that are for operators instead of end users. What should this<br>>>>> repository be named and under what project should the repository<br>>>>> exist?<br>>>><br>>>> I've heard some of the conversations around this as well, and I do<br>>>> agree a different repository seems reasonable.<br>>>><br>>>> The question of who the reviewers will be is a pretty important one in<br>>>> my opinion and that also that impacts which project it would be best<br>>>> to sit under. I'm inclined to suggest we make it part of the<br>>>> Community App Catalog project because it's related, and longer term we<br>>>> would like to play a big role in building a community of application<br>>>> reviewers.<br>>>><br>>>> I guess that means I'm volunteering to help with this and will be<br>>>> happy if this repo is associated with the Community App Catalog<br>>>> project.<br>>>><br>>>> -Christopher<br>>>><br>>>><br>>>><br>>>>> Thanks,<br>>>>> Caleb<br>>>>><br>>>>> _______________________________________________<br>>>>> Defcore-committee mailing list<br>>>>> Defcore-committee@lists.openstack.org<br>>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>><br>>>> _______________________________________________<br>>>> Defcore-committee mailing list<br>>>> Defcore-committee@lists.openstack.org<br>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>><br>>>> _______________________________________________<br>>>> Defcore-committee mailing list<br>>>> Defcore-committee@lists.openstack.org<br>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>><br>>>><br>>>><br>>>><br><br>_______________________________________________<br>Defcore-committee mailing list<br>Defcore-committee@lists.openstack.org<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br><br></tt><br><br><BR>
</body></html>