Open Stack

I think this is a great idea as well.   I am willing to be core on this new
repo as well.  This work will continue to be a significant focus area for
me.

Thanks,

Brad


Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet:  btopol at us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680



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>,
            "Sun, Yih Leong" <yih.leong.sun at intel.com>, Brad
            Topol/Raleigh/IBM at IBMUS
Date:	11/10/2016 08:16 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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20161111/79969e64/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20161111/79969e64/attachment-0001.gif>