Wednesday, 2016-11-16

*** lamt has quit IRC00:25
*** lamt has joined #openstack-meeting-cp00:30
*** tovin07_ has joined #openstack-meeting-cp01:14
*** zhurong has joined #openstack-meeting-cp01:30
*** lamt has quit IRC01:57
*** coolsvap has joined #openstack-meeting-cp02:19
*** ajr1 has joined #openstack-meeting-cp03:35
*** ajr1 has quit IRC04:40
*** ajr1 has joined #openstack-meeting-cp04:40
*** ajr1 has quit IRC04:54
*** dims has quit IRC05:20
*** prateek has joined #openstack-meeting-cp05:27
*** harlowja has quit IRC05:55
*** dims has joined #openstack-meeting-cp05:59
*** markvoelker has quit IRC06:28
*** tovin07 has quit IRC08:24
*** markvoelker has joined #openstack-meeting-cp08:29
*** markvoelker has quit IRC08:34
*** tovin07 has joined #openstack-meeting-cp08:57
*** gouthamr has joined #openstack-meeting-cp09:13
*** gouthamr has quit IRC09:17
*** gouthamr has joined #openstack-meeting-cp09:17
*** tovin07 has quit IRC09:23
*** gouthamr has quit IRC09:43
*** gouthamr has joined #openstack-meeting-cp09:50
*** tovin07_ has quit IRC09:57
*** zhurong has quit IRC10:02
*** markvoelker has joined #openstack-meeting-cp10:30
*** markvoelker has quit IRC10:35
*** gouthamr has quit IRC10:38
*** gouthamr has joined #openstack-meeting-cp10:39
*** brault has quit IRC10:41
*** skazi has joined #openstack-meeting-cp10:43
*** brault has joined #openstack-meeting-cp10:45
*** gouthamr has quit IRC11:07
*** gouthamr has joined #openstack-meeting-cp11:27
*** gouthamr has quit IRC11:51
*** gouthamr has joined #openstack-meeting-cp11:52
*** coolsvap is now known as coolsvap_12:09
*** gouthamr has quit IRC12:32
*** zhurong has joined #openstack-meeting-cp12:35
*** prateek has quit IRC13:10
*** brault has quit IRC13:17
*** brault has joined #openstack-meeting-cp13:18
*** lamt has joined #openstack-meeting-cp13:23
*** brault has quit IRC13:30
*** xyang1 has joined #openstack-meeting-cp13:32
*** brault has joined #openstack-meeting-cp13:35
*** markvoelker has joined #openstack-meeting-cp13:44
*** gouthamr has joined #openstack-meeting-cp13:50
*** gouthamr has quit IRC13:54
*** jason___ has joined #openstack-meeting-cp14:06
*** gouthamr has joined #openstack-meeting-cp14:11
*** prateek has joined #openstack-meeting-cp14:17
*** lamt has quit IRC14:23
*** uxdanielle has joined #openstack-meeting-cp14:26
*** gouthamr has quit IRC14:39
*** lamt has joined #openstack-meeting-cp14:41
*** tongli has joined #openstack-meeting-cp14:44
jason___Morning , litong14:48
tongli@jason__, morning.14:48
tongliglad that you are here for the interop meeting.14:49
*** zhurong has quit IRC14:51
*** danielaebert has joined #openstack-meeting-cp14:57
*** jamespage has joined #openstack-meeting-cp14:58
*** kgarloff has joined #openstack-meeting-cp14:58
*** coolsvap_ is now known as coolsvap14:59
docaedoHey :)14:59
danielaeberthi kurt :-)14:59
jason___HI, kurt15:00
topol#startmeeting interop_challenge15:00
openstackMeeting started Wed Nov 16 15:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is topol. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: interop_challenge)"15:00
openstackThe meeting name has been set to 'interop_challenge'15:00
markvoelkero/15:00
topolHi everyone, who is here for the interop challenge meeting today?15:00
topolThe agenda for today can be found at:15:00
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2016-11-1615:00
topolWe can use this same etherpad to take notes15:00
*** skazi_ has joined #openstack-meeting-cp15:00
docaedoo/15:00
jason___Jason from huawei15:00
tonglio/15:00
skazi_o/15:01
tongligood day everyone!15:01
kgarloffKurt (DT)15:01
skazi_tongli: good time this time :o)15:01
topol#topic review action items from previous meeting15:01
topol#link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-11-02-14.01.html15:01
*** openstack changes topic to "review action items from previous meeting (Meeting topic: interop_challenge)"15:01
GheRiveroo/15:01
*** gema has joined #openstack-meeting-cp15:02
topolSo the only real action item left from the last meeting was to CONGRATULATE EVERYONE FOR DOING A GREAT JOB IN BARCELONA!!!15:02
gemao/15:02
topolso CONGRATULATIONS EVERYONE!!!15:02
tonglithanks Brad.15:02
gemathanks indeed :D15:02
gemait was fun15:02
topolWe got a ton of great press. Press Links can be found in the last meeting.  And the OpenStack Foundation was very very very happy15:02
jason___thanks so lot15:03
danielaebertthank you!!15:03
tongliit was good to know how the show was made, I mean by being on the back stage and of course on the stage.15:03
topolAnd the fun continues :-)15:03
topolLet's see todays agenda15:03
topol    #topic Next Steps  -- What loose ends do we need to tie up?15:03
topolAs we sprinted toward a Barcelona demo, I asked everyone to focus on that and I'm sure we left some loose ends.  Anyone remember any that they feel are urgent?15:04
jamespageo/15:04
topolAnyone concerned they couldnt get docker swarm running? Or Submitting RefStack results?15:05
tongliI think we really need to have our own repository.15:05
markvoelkertopol: Well, we discussed formalizing some best practices and I'm not sure we ever really did that.  There was a (somewhat sparse) etherpad I think15:05
topolyes, tongli nd yes markvoelker15:05
tongliChristopher Aedo will help and I hope he is in the meeting.15:05
jason___Suggest k8S and mesos as well15:05
*** zhipeng has joined #openstack-meeting-cp15:05
markvoelkerBut it would be nice to write something more formal up.  Not sure one workload is quite grounds for a formal doc though, but cataloging what we learned so far is a good step.15:05
*** eeiden has joined #openstack-meeting-cp15:06
topolmarkvoelker I agree.  We should write somthing more formal up before we forget15:06
docaedoI'm here to talk about the repo stuff15:06
tongli@markvoelker, +1, we can do couple more this time to help with the doc.15:06
docaedo(but note it's last thing on the agenda)15:06
topoldocaedo, definitely want to talk about the repo.  can we make that the next topic/15:07
tongli@docaedo, yes, sir, we can wait few minutes more. :-)15:07
markvoelkertopol: One other loose end we might want to tackle: everyone ran refstack for the challenge.  Have we put pointers to those results somewhere?15:07
topolso on the formal doc will we make that an OpenStack wiki page/15:07
topoland gather content on an etherpad page?15:08
tongliI agree with mark that we can develop couple more work load to help with the doc as we will find more best practices.15:08
topoltongli, yes the doc will contninue to iterate and improve15:08
tonglithe formal doc can be a doc file as part of the repository.15:08
tongliwe can review and submit15:08
topolBut where do we start the strawman?15:08
tonglilike any other document of a project.15:08
topoltongli, makes sense to me :-015:09
topoltongli, I like how you pushed to topics together15:09
kgarloffWorkloads on one hand - tools (ansible+shade vs. Teraform vs. Heat vs. ...) is the other dimension I think15:09
topolNeed a repo and put a doc in the repo :-)15:09
tonglisuppose we have our own repo, then in docs directory, we can have tons of stuff, best practice can be one.15:09
markvoelkerStarting on a wiki or etherpad sounds fine...once we get the repo sorted out we can think about the best place for a formal thing to live (once we have decent content).15:09
tonglior best practice has its own directory.15:09
jason___@kgarloff +115:09
topolmarkvoelker are you willing to start an etherpad page for us?15:10
tongli@markvoelker, please. @topol +115:10
topoland then as soon as we get a repo we can migrate over.  Does that sound like a good plan?15:10
markvoelkertopol: I think we already had a pad, no?  Just need to dig up the link?15:11
markvoelkerAnd get people to add to it?15:11
tongli@kgarloff, yeah, we will have tool names as top directory to hold different type of work load.15:11
topolwe had a postmortem page15:11
tonglithinking about different platforms as well.15:11
topolwe can reprupose that15:11
markvoelker#link https://etherpad.openstack.org/p/interop-challenge-postmortem15:11
topolrepurpose that15:11
topolmarkvoelker, perfect15:11
topol#action all, please use #link  https://etherpad.openstack.org/p/interop-challenge-postmortem  for lessons learned doc15:12
tonglibest practices can have sections such as tooling, networking, provisioning, metadata, etc.15:13
topol#action all, please add all you can to it15:13
tonglithere can be a lot of things we find.15:13
topol#action  all, sections include  tooling, networking, provisioning, metadata, etc.15:13
topolok, wonderful. so lets jump to what excites us all... a new repo!!!15:14
topol#topic new repo15:14
*** openstack changes topic to "new repo (Meeting topic: interop_challenge)"15:14
topolSo I think we earned this :-). docaedo, how do we make this happen?15:14
docaedopretty easy for the new repo really, just have to agree on where it will live, and who initial core reviewers will be15:15
dmelladoo/15:15
dmelladohi guys, sorry being late ;)15:15
docaedoI think it's also important, from the start, to have a clear articulation of what the vision/intention is15:15
docaedoie not make it just a dumping ground of playbooks, but have an idea of what kind of reviewers we would need, how things should be tested, etc15:15
dmelladoas a part of that, I think that we should refactor the playbooks to run on several distributions too15:16
docaedobut I suspect you already have that sorted out since you've been doing this for a while under the osops repo?15:16
topoldocaedo, I believe the vision is the repo will hold the workloads and their automation and serve as examples of best practices and the lessons learned doc.15:16
dmelladoI did an initial patch for that for fedora, but it'd be great to have it cleaned up and add more distros ;)15:16
topolI would think everyone who participated in the Interop Challenge should be made core.  Getting up on stage with live demos. I say they earned it15:17
tongli@dmellado, yes, different tools may require different methods.15:17
docaedotopol: makes sense to me15:17
tongliadding a lot of conditional statement do not seem to be the best way to handle this.15:17
danielaebert@topol: great idea!15:17
kgarloffdmellado: you mean other distros as target VMs,  right? Ansible host really should not matter...15:17
gematopol: I dare us getting rid of shade for the next iteration and using directly the APIs15:18
dmelladokgarloff: exactly15:18
topolonce we get a repo. we can add  a mission statement and refine it.15:18
topolgema that is the long term goal.  But my guess is shade is hiding some uglies from us15:18
*** prateek has quit IRC15:18
docaedotopol: sure, though I'll need someone to supply a sort of "elevator pitch" for the repo (so I can put it in the "paperwork" of the new repo request)15:19
kgarloffgema: moving lower level and removing abstraction?15:19
gematopol: I'd like to know what those are15:19
gemathis would help interop WG as well15:19
topolgema we will find out together :-)15:19
gematopol: +115:19
topoldocaedo, I can provide an elevator pitch15:19
gemakgarloff: removing abstractions yes, so that we are actually using the APIs directly15:19
topoldocaedo should I put it on an etherpad? Or email?15:20
docaedotopol: etherpad would work fine for me15:20
topollets do an etherpad and everyone can iterate15:20
tongli@gema, that means in ansible we will be removing ansible os cloud module, not sure I like that.15:20
topolI'll add a section to the postmortem etherpad for this15:20
tongliwe can talk more on that.15:20
docaedogema: I know it's a dangerous rabbit hole but I can't help but ask - by "using the APIs directly" do you mean using heat for orchestration, or something else?15:20
kgarloffgema: Well removing a layer results in a better proof of (low-level) compat - I can see the point..15:20
topolso we can keep everthing in one place till we get a repo15:20
kgarloffBut is this what users do?15:21
dmelladotongli: +1 on the talk, also if we use the apis directly we'll need to agree on which level of support we'll be providing15:21
dmelladoeven if the api should be backwards-compatible15:21
gemadocaedo: I mean talking to keystone, nova, cinder apis directly, rather than by a translator15:21
dmelladogema: ^^15:21
topol#action topol to add an elevator pitch to #link https://etherpad.openstack.org/p/interop-challenge-postmortem15:21
docaedogema: do you have any example of a distributable application that works that way?15:21
gemadmellado: the openstack API is compatible as defined by the guidelines15:22
topolso gema is discussing what falls under the next topic:15:22
gematopol: sorry for getting ahead :D15:22
markvoelkerTBH, I think it's fine to have more than one type here.  In the real world, people often use Ansible (and thus Shade too). So there's appetite for that. Can have direct-to-API workloads too.  I think we just need to organize them somehow, or tag them or something.15:22
topol#topic Next Steps -- what new interop intiatives do we want to focus on15:22
*** openstack changes topic to "Next Steps -- what new interop intiatives do we want to focus on (Meeting topic: interop_challenge)"15:22
docaedotopol: could you also add list of initial reviewers to that etherpad?15:23
topolmarkvoelker, I agree15:23
gemamarkvoelker: agreed15:23
topoldocaedo, sure15:23
tonglican be messing. I see this.15:24
topolaction all, if you participated in the interop challenge and want to be added as core, add your name to the core list section of #link https://etherpad.openstack.org/p/interop-challenge-postmortem15:24
markvoelkertopol: for new interop initiatives, I think we actually already brainstormed a few that we didn't have time for before BCN. NFV, k8s were on that list I think.15:24
tongliansible/shade15:24
tongliansible/osapi15:24
topolmarkvoelker, yes you are correct15:24
topolHere is what I heard:15:24
tongliansible/shade/ubuntu15:25
* markvoelker notes it would be good to review the user survey for what people are interested in, and what they're running on top of OS today15:25
GheRiverogema: shade is very useful to handle differencies between clouds: api versions, floating ip vs public ip. Doing that using only osapi and we will redo shade again15:25
topolCloud Foundry, k8s, NFV, and reduced reliance in shade were all that I heard discussed in Barcelona15:25
topolerr reduced reliance on shade15:25
tongli@GheRivero, yes, yes, that is what will happen.15:25
jason___@markvoelker +115:25
tongli@topol, I think we should target one or at most two.15:26
topolso question is after we work on the lessons learned doc and get the repo up.  what do we want to proritize first15:26
topoltongli agreed :-)15:26
tonglilike cloud foundry and NFV as the option.15:26
GheRiveroBut I agree that shade existence is needed but a big openstack failure15:26
dmelladoone thing that I'd really like to see this time upfront is to have at least some tox env already available15:27
GheRiveroSorry for the offtopic15:27
markvoelkertopol: perhaps a formal poll is in order? Give people a week to add suggestions to an etherpad, then do a doodle poll or something to pick?15:27
dmelladoit was quite chaotic to tell people to go and use version==XX or YY15:27
dmelladoI wouldn't like it to happen in the new repo15:27
topolmarkvoelker, agreed.  lets do a doodle poll15:27
topolgreat suggestion markvoelker15:27
GheRiverodmellado: i can help you with that... and setting some cicd for gating15:28
tongli@topol, can you add the doodle pool as an action for next week or week after?15:28
dmelladoGheRivero: that'd be great, was also on my list15:28
gemaGheRivero: indeed, with my interop hat on I would like to help fix the need for shade15:28
topol#action, all add to etherpad suggestions for work items.  After one week. topol will create a doode poll and send out to defcore list15:28
markvoelkertopol: I'm adding a section to the bottom of https://etherpad.openstack.org/p/interop-challenge-meeting-2016-11-16 for folks to drop suggestions15:28
topolmarkvoelker, reading my mind again.  Must have been due to that twitter photo with those big antlers next to your head15:29
topolYeah I saw that :-015:29
gemalol15:29
* markvoelker finds that they improve reception and wears them frequently when wanting to watch TV15:30
topollol15:30
markvoelker#action Everyone add ideas for next workloads to today's etherpad by 11/2315:30
markvoelkertopol: you want to put together the doodle poll once we hit 11/23?  Note: that's the day before Thanksgiving in the US, so may want to leave the doodle open a while.15:31
topolok, and to be clear I will add the mission statement and list for cores to #link https://etherpad.openstack.org/p/interop-challenge-postmortem15:32
topolmarkvoelker, makes sense. we will be sensitive to turkey day :-015:32
markvoelker#action: topol to generate Doodle poll from suggestion list by 11/23, send it to ML, leave it open for a week or so to account for US holiday15:32
docaedotopol: great - when should I make the repo request?  (and when I do I'll send a note to the defcore list with a link to the review)15:33
tongli11/23 is right before Thanksgiving, a wednesday, people maybe out.15:33
tonglido you want to make that date the week later?15:33
topoldocaedo, I'm hoping we can do that as soon as possible. I can add the elevator pitch  today. how quickly can be add their names to be included on the core list?15:34
docaedoI can put in the request for the repo today, we can adjust the cores any time after15:34
markvoelkertongli: 11/23 is just the cutoff for getting ideas, so I think giving people a week from today to do that is ok.  We'll leave the doodle open for a week or so to give people time to respond even if they take some holiday PTO.15:34
tongli@markvoelker, ok,15:34
docaedoone other question - should there be a source for this repo, which could be the directory in existing osops repo (this would retain the git history and existing content)15:35
kgarloff@docaedo +115:35
tongli@docawdo, can we just have the repo created with a simple readme file?15:35
dmellado@docaedo, I guess picking only the ansible-related commits could be a pain15:36
tongliI think even the existing osop/contrib structure need some work.15:36
docaedotongli: that's an option too15:36
tonglireally like to get it right this time.15:36
tongliand allow us to support different tools and different platforms, etc15:36
gemalet's start clean, then15:36
tongliso that we do not have to dig and guess to find what they are.15:37
topoldocaedo, I just started the core list. Added my name and my id15:37
* kgarloff remembers that the only thing to learn from history is that you don't15:37
tongli@kgarloff, haha. I like that a lot. who does? who remembers?15:38
docaedoI would strongly suggest you work through the directory structure before throwing things in there then (since it will start clean)15:38
topoldocaedo, is that all you need15:38
topollet's defintely start clean :-)15:39
markvoelkerdocaedo: ++.  topol: Perhaps we should start brainstorming the repo structure on the etherpad as well?15:39
topolmarkvoelker, yes15:39
tongli@docaedo, once it is ready , we can start send patches to setup directories.15:39
gematopol: what is the user id? where did you get that from?15:39
tongliand move some stuff over.15:39
docaedotopol: yes I think that's sufficient :)  ..  OH and this is planned to be under app-catalog repo?  Or completely fresh repo?  We do also need to know what to call it (probalby just interop)15:39
gemadocaedo: that may be confusing with the interop working group15:40
topolI would like a completely fresh repo. Does that make sense?15:40
gemamarkvoelker: ^ what name do we have lined up for that?15:40
topolInterop Workload Repo?15:40
docaedoTo be clear, I can take on the "request a new sub-repo under app-catalog", but a COMPLETELY new repo also means basically new project, and that's more work that I can not volunteer for at this time15:40
topolok, docaedo, lets keep it easy then15:41
topolsub-repo works for me15:41
topolI dont want to make life difficult for folks15:41
topolsub-repo work for everyone else?15:41
jamespagedoes that limit in any way what we might place in the interop area?15:42
jamespage(for sub-repo)15:42
docaedojamespage: no limitations, it would basically be it's own repository, just "managed" underneath the app-catalog project15:42
topoljamespage Im not sure I understand your question15:42
topolso we get our own name for the repo and our own core list15:42
topolI think a sub-repo gives us all that we need15:43
jamespagedocaedo, topol: I missed the 'own repository' bit of that15:43
docaedoand actually, now that I'm thinking a little more clearly, it does not have to be app-catalog/<something> .. it could live at it's own root, the only consideration would be from the governance side15:43
topolwe used sub-repos in Keystone and they worked great for things like pycadf15:43
docaedoFor this effort it would be on it's own repository - sorry for misleading the conversation15:43
tonglifor the name, can we just call it interop?15:44
gematongli: I will bring this up in today's defcore meeting15:44
docaedoit would just be a repo that is considered to be part of the Community App Catalog project (but with it's own set of core reviewers)15:44
gemawe are also changing names15:44
gematongli: calling it interop may be confusing but I am not sure15:44
topolI think if we get our own repo and own core list we can survive as a sub-repo under app catalog. and it make sense to me that this be associated with the app catalog project15:44
topolI like that association15:45
docaedoI do too15:45
topoldoes that work for everyone?15:45
jason___OK15:45
dmellado+1 for me15:45
docaedoOnly other thing I need at this point is agreement on what to call it15:46
topol#action on todays etherpad, everyone start making suggestions about the repo structure15:46
topolanyone have a better name than Interop Challenge Workloads?15:46
kgarloffWhy not just interop challenge?15:46
markvoelkertopol: I suggest lowercase and no spaces (for ease of CLI git use)15:46
*** coolsvap is now known as coolsvap_15:46
topolinteropcchallenge works for me15:47
topolmarkvoelker is that what you were thinking?15:47
dmelladointerop_challenge15:47
dmellado?15:47
markvoelkerI think I like interop_workloads somewhat better, but either is fine.15:47
docaedosuggest - instead of underscore for git15:47
topolI think I like interop_workloads15:48
topolit seems like the most accurate description15:48
dmelladointerop_worloads works for me15:48
dmelladowith - instead of _ if needed15:48
topolif someone new came around and saw it.15:48
topolinterop-workloads15:48
gema+115:48
jamespage+115:48
topolis that the best option?15:48
* markvoelker is ok with either and won't try to pain the shed another color if either is chosen =)15:49
GheRivero+115:49
gemamarkvoelker: confess, you just want to change the name later :P15:49
topolK, lets go with interop-workloads15:49
tongliwanting a more grand name, come on guys.15:49
*** zhipeng has quit IRC15:49
markvoelkergema: well, that would be the traditional OpenStack way...but I digress. =p15:49
dmelladojust please tell me that we won't be having a discussion on the mascot now15:49
dmelladoxD15:49
jamespageI think we just inherited the app-catalog mascot right?15:50
skazi_tongli: grandmaster9000?15:50
gemadmellado: it's going to be a chameleon15:50
tongli@skazi_, haha15:50
topolI can believe its not butter workloads?15:50
docaedojamespage: haha you are right, you get a quokka!15:50
tongli@topol, haha15:50
topolbetter just stick with interop-workloads15:50
tongliI am working on "interop-workloads" project, so lame!15:51
topol#agree new subrepo will be called interop-workloads15:51
*** uxdanielle has quit IRC15:52
topoldocaedo, I will add a elevator pitch today15:52
gematongli: you are probably working on conquering the world one cloud at a time!15:52
tongli@gema, haha.15:52
topol#topic open discussion15:52
*** openstack changes topic to "open discussion (Meeting topic: interop_challenge)"15:52
gemawe already covered this topic15:52
jamespagedid we?15:52
docaedotongli: you can call it something much fancier on the wiki, and in conversation - this is just the thing where people will clone the repo (so the easier/shorter it is, the harder it will be for someone to get it wrong :D )15:52
topolLots of progress made today. An other topics?15:52
tongli@docaedo, not a problem, just giving topol hard time,15:53
docaedotopol: thanks, I'll circle back later today and should be able to submit the PR today15:53
topolIcantbelievethisreponameissolongbutnonethelessinteropworkloads  was my 2nd choice15:53
tongli@docaedo, thanks lot for helping out. regardless what we call it, it will be great.15:53
topolyes, THANKS doceado15:54
topolany other topics for today?15:54
skazi_topol: where is the cores list for this repo?15:54
docaedohappy to help out - hopefully I'll be able to get more involved in this over the next few months too, especially around review and CI goes15:55
topolI started the cores list on #link https://etherpad.openstack.org/p/interop-challenge-postmortem15:55
topolplease add today so we docaedo can move forward on the repo. we can always add folks later if we miss them15:55
dmelladohey guys, I pm'ed topol a min ago, but want to make sure that for userid we're referring to gerrit username15:56
docaedotopol: yep, I can do that15:56
dmelladodo you need any more info besides that, docaedo ?15:56
skazi_topol: ah, thx, I was looking at the end of this etherpad15:56
docaedodmellado: no I don't think so, gerrit username is the thing - but anyway, I don't need that for the initial request15:56
dmelladodocaedo: that's what I thought, thanks for clarifying it ;)15:57
docaedoso the reviewers for the repo can come after :)15:57
topolI went to https://review.openstack.org/#/settings/ and grabbed my userid15:57
topolis that what you need docaedo?15:57
topoleer I meant username15:58
topolsorry15:58
topolok folks so to be clear provide your gerrit username15:59
docaedotopol: yep - but I will make sure *you* have the ability to add people to the group after the repo is set up, so I realize we do not need to have the list to request the repo, just want to make sure the "why are you requesting this repo" sentence makes sense and I'll be good to go15:59
topolK, I will add the why are you requesting this repo as soon as this meeting is over15:59
docaedotopol: awesome, then I'll make the request after breakfast16:00
topolanything else for today?16:00
topolI think we are out of time.16:00
tongli@docaedo, thanks a lot.16:00
topolTHANKS EVERYONE!!!16:00
tongli@topol, thanks brad16:00
*** coolsvap_ is now known as coolsvap16:00
docaedono prob!16:00
topol#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov 16 16:00:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-11-16-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-11-16-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-11-16-15.00.log.html16:01
*** uxdanielle has joined #openstack-meeting-cp16:01
*** skazi_ has quit IRC16:03
*** danielaebert has quit IRC16:04
*** gouthamr has joined #openstack-meeting-cp16:09
*** ruan_02 has joined #openstack-meeting-cp16:12
*** ruan_03 has joined #openstack-meeting-cp16:14
*** ruan_02 has quit IRC16:14
*** gagehugo has joined #openstack-meeting-cp16:18
*** kgarloff has left #openstack-meeting-cp16:24
*** gagehugo has left #openstack-meeting-cp16:25
*** jason___ has quit IRC16:35
*** Rockyg has joined #openstack-meeting-cp17:04
*** Rockyg has quit IRC17:10
*** david-lyle has quit IRC17:48
*** david-lyle has joined #openstack-meeting-cp17:48
*** uxdanielle has quit IRC17:52
*** harlowja has joined #openstack-meeting-cp18:14
*** uxdanielle has joined #openstack-meeting-cp18:27
*** gouthamr has quit IRC18:57
*** gouthamr has joined #openstack-meeting-cp18:59
*** coolsvap has quit IRC19:07
*** tongli has quit IRC19:40
*** uxdanielle has quit IRC19:52
*** diablo_rojo_phon has joined #openstack-meeting-cp19:56
*** edtubill has joined #openstack-meeting-cp20:08
*** uxdanielle has joined #openstack-meeting-cp21:12
*** gouthamr has quit IRC21:37
*** uxdanielle has quit IRC21:52
*** lifeless has quit IRC22:11
*** lifeless has joined #openstack-meeting-cp22:12
*** edtubill has quit IRC22:53
*** xyang1 has quit IRC23:15
*** lamt has quit IRC23:33
*** david-lyle_ has joined #openstack-meeting-cp23:50
*** david-lyle has quit IRC23:51

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!