[OpenStack-DefCore] [Interop] New Repository

Daniel Mellado dmellado at redhat.com
Fri Nov 11 08:20:45 UTC 2016


I did quite some work on the interop scripts for and wouldn't mind to
lend a hand on this by tracking ansible/tox reviews if you need some
other core.

Best!

Daniel

El 11/11/16 a las 02:16, Rochelle Grober escribió:
> 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
> 



More information about the Defcore-committee mailing list