Open Stack

Kris ++.

Kris' statement below is the exact reason why the Interop-Challenge team
thinks Operators repository is a good place to store the interop workload
deployment tool sets.  In addition, during today's Interop-Challenge IRC
meeting, we think that it would help if we can have a representative from
the the Operators team to join the Interop-Challenge IRC meeting
(Wednesdays at 1400 UTC,  IRC Channel (on freenode): #openstack-defcore )
if possible,

What is the IRC channel for the "OSOps Working Group" ?  As you indicated,
that would be a good place for us to ask questions.  Thanks!

Catherine Diep
RefStack Project PTL
IBM
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 08/31/2016 01:25 PM
-----

From:	"Kris G. Lindgren" <klindgren at godaddy.com>
To:	Joseph Bajin <josephbajin at gmail.com>, "Yih Leong, Sun."
            <yihleong at gmail.com>
Cc:	OpenStack Operators <openstack-operators at lists.openstack.org>,
            defcore-committee <defcore-committee at lists.openstack.org>
Date:	08/31/2016 12:52 PM
Subject:	Re: [OpenStack-DefCore] [Openstack-operators] [OSOps] Ansible
            work load test for interop patch set



I originally agreed with you, but then I thought about it more this way:
It’s a tool to test to see if clouds are interop compatible (atleast that
heat works the same on the two clouds).  While not technically a tool to
manage openstack.  But still something that some Operators could want to
know if they are looking at doing hybrid cloud.  Or they may want to ensure
that two of their own private clouds are interop compatible.

___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: Joseph Bajin <josephbajin at gmail.com>
Date: Wednesday, August 31, 2016 at 1:39 PM
To: "Yih Leong, Sun." <yihleong at gmail.com>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>,
defcore-committee <defcore-committee at lists.openstack.org>
Subject: Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work
load test for interop patch set

This looks like this was merged, but no one really answered my questions
about an "InterOp Challenge" code base going into the Operators repository.

--Joe

On Wed, Aug 31, 2016 at 12:23 PM, Yih Leong, Sun. <yihleong at gmail.com>
wrote:
 Can someone from ospos please review the following patch?
 https://review.openstack.org/#/c/351799/

 The patchset was last updated Aug 11th.
 Thanks!



 On Tue, Aug 16, 2016 at 7:17 PM, Joseph Bajin <josephbajin at gmail.com>
 wrote:
  Sorry about that. I've been a little busy as of late, and was able to get
  around to taking a look.

  I have a question about these.   What exactly is the Interop Challenge?
  The OSOps repos are usually for code that can help Operators maintain and
  run their cloud.   These don't necessarily look like what we normally see
  submitted.

  Can you expand on what the InterOp Challenge is and if it is something
  that Operators would use?

  Thanks

  Joe

  On Tue, Aug 16, 2016 at 3:02 PM, Shamail <itzshamail at gmail.com> wrote:


  > On Aug 16, 2016, at 1:44 PM, Christopher Aedo <doc at aedo.net> wrote:
  >
  > Tong Li, I think the best place to ask for a look would be the
  > Operators mailing list
  > (
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators).
  > I've cc'd that list here, though it looks like you've already got a +2
  > on it at least.
  +1

  I had contacted JJ earlier and he told me that the best person to contact
  would be Joseph Bajin (RaginBajin in IRC).  I've also added an OSOps tag
  to this message.
  >
  > -Christopher
  >
  >> On Tue, Aug 16, 2016 at 7:59 AM, Tong Li <litong01 at us.ibm.com> wrote:
  >> The patch set has been submitted to github for awhile, can some one
  please
  >> review the patch set here?
  >>
  >> https://review.openstack.org/#/c/354194/
  >>
  >> Thanks very much!
  >>
  >> Tong Li
  >> IBM Open Technology
  >> Building 501/B205
  >> litong01 at us.ibm.com
  >>
  >>
  >> _______________________________________________
  >> 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

  _______________________________________________
  OpenStack-operators mailing list
  OpenStack-operators at lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


  _______________________________________________
  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/20160831/85b87bbf/attachment.html>