Open Stack

On Wed, Nov 16, 2016 at 4:05 PM, Christopher Aedo <doc at aedo.net> wrote:
> On Fri, Nov 11, 2016 at 9:17 AM, Christopher Aedo <doc at aedo.net> wrote:
>> On 11/11/16, Tong Li <litong01 at us.ibm.com> wrote:
>>>
>>> Chris,
>>>    Thanks so much for doing this important work. Please let me know what I
>>> can do to help. If we do have a new repository, I will be very happy to
>>> move all the stuff we have in contrib repository over to the new one. We
>>> can also structure the entire directory a bit better. We can talk about all
>>> these things on coming Wednesday meeting. Chris, can you come to the
>>> Wednesday meeting UTC 1500 at
>>> http://webchat.freenode.net/?channels=openstack-meeting-cp
>>
>> I'm glad to hear there's support for this :)  I should be able to make
>> that meeting next week, look forward to coordinating next steps.
>
> In this mornings Interop Challenge meeting[1] we agreed to call the
> repository "interop-workloads".  I threw together a PR to request the
> repo[2] and at this point it looks good so will just need the Infra
> cores to review and merge.
>
> Along the way I also created a launchpad project[3] for this.  This
> will allow you to create blueprints for all the different efforts
> you're planning (and any PRs can reference blueprints or bugs).
>
> [1]: https://etherpad.openstack.org/p/interop-challenge-postmortem
> [2]: https://review.openstack.org/398533
> [3]: https://launchpad.net/interop-workloads

The repository has been created[1] and the gerrit group[2] has also
been created.  I was not able to find all the IDs specified in the
etherpad to add as initial cores, but many of the accounts have been
added.  At this time Brad or anyone else on that list can add the
others as needed.

Let me know if I can be of any further help here!

[1]: https://git.openstack.org/cgit/openstack/interop-workloads
[2]: https://review.openstack.org/#/admin/groups/1651,members

-Christopher


>
>
>> -Christopher
>>
>>>
>>> Thanks.
>>>
>>> Tong Li
>>> IBM Open Technology
>>> Building 501/B205
>>> litong01 at us.ibm.com
>>>
>>>
>>>
>>> From: Rochelle Grober <rochelle.grober at huawei.com>
>>> To:   Christopher Aedo <doc at aedo.net>, Caleb Boylan
>>>             <caleb.boylan at dreamhost.com>
>>> Cc:   defcore-committee <defcore-committee at lists.openstack.org>
>>> Date: 11/10/2016 08:17 PM
>>> Subject:      Re: [OpenStack-DefCore] [Interop] New Repository
>>>
>>>
>>>
>>> Sounds like a plan to me :-)
>>>
>>> Tong Li is critical for Core for this repo at the moment.  But it would be
>>> good to have someone else who could also actively track and review
>>> additions/changes, etc.
>>>
>>> I also think we might consider planning a "third party CI" type account or
>>> something so that when changes go in, all the interop vendors can
>>> automatically verify they haven't been broken.
>>>
>>> I'd love to see this happen.
>>>
>>> Might be able to put a cycle or two into it.
>>>
>>> --Rocky
>>>
>>> -----Original Message-----
>>> From: Christopher Aedo [mailto:doc at aedo.net]
>>> Sent: Thursday, November 10, 2016 10:18 AM
>>> To: Caleb Boylan
>>> Cc: defcore-committee
>>> Subject: Re: [OpenStack-DefCore] [Interop] New Repository
>>>
>>> On Wed, Nov 9, 2016 at 9:08 AM, Caleb Boylan <caleb.boylan at dreamhost.com>
>>> wrote:
>>>> Hi everyone,
>>>>
>>>> Great to see you all in Barcelona, the demo during the keynotes was
>>>> great! I think it would be great to get the playbooks and scripts into
>>>> the hand of end users that are using OpenStack clouds. There has been
>>>> talk of moving the Interop stuff into a separate repository (from the
>>>> osops-tools-contrib repository). I think this would be beneficial as
>>>> it is less confusing than having it in the same repository as other
>>>> scripts that are for operators instead of end users. What should this
>>>> repository be named and under what project should the repository
>>>> exist?
>>>
>>> I've heard some of the conversations around this as well, and I do
>>> agree a different repository seems reasonable.
>>>
>>> The question of who the reviewers will be is a pretty important one in
>>> my opinion and that also that impacts which project it would be best
>>> to sit under.  I'm inclined to suggest we make it part of the
>>> Community App Catalog project because it's related, and longer term we
>>> would like to play a big role in building a community of application
>>> reviewers.
>>>
>>> I guess that means I'm volunteering to help with this and will be
>>> happy if this repo is associated with the Community App Catalog
>>> project.
>>>
>>> -Christopher
>>>
>>>
>>>
>>>> Thanks,
>>>> Caleb
>>>>
>>>> _______________________________________________
>>>> Defcore-committee mailing list
>>>> Defcore-committee at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>
>>> _______________________________________________
>>> Defcore-committee mailing list
>>> Defcore-committee at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>
>>> _______________________________________________
>>> Defcore-committee mailing list
>>> Defcore-committee at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>
>>>
>>>
>>>