Tuesday, 2018-03-27

*** chyka_ has joined #openstack-operators00:02
*** jamesmcarthur has joined #openstack-operators00:02
*** chyka has quit IRC00:05
*** jamesmcarthur has quit IRC00:07
*** rcernin has quit IRC00:19
*** rcernin has joined #openstack-operators00:19
*** liverpooler has joined #openstack-operators00:19
*** chyka_ has quit IRC00:27
*** fragatin_ has quit IRC00:40
*** fragatina has joined #openstack-operators00:41
*** fragatina has quit IRC00:41
*** fragatina has joined #openstack-operators00:41
*** fragatina has quit IRC00:41
*** fragatina has joined #openstack-operators00:43
*** fragatina has quit IRC00:48
*** harlowja has quit IRC00:53
*** mriedem has quit IRC00:55
*** liverpooler has quit IRC01:08
*** liverpooler has joined #openstack-operators01:48
*** germs has joined #openstack-operators01:52
*** germs has quit IRC01:52
*** germs has joined #openstack-operators01:52
*** germs has quit IRC01:57
*** gyee has quit IRC02:26
*** dmsimard|cave is now known as dmsimard02:29
*** liverpooler has quit IRC02:29
*** VW has joined #openstack-operators02:33
*** VW has quit IRC02:59
*** fragatina has joined #openstack-operators03:02
*** fragatina has quit IRC03:08
*** fragatina has joined #openstack-operators03:30
*** wvera has joined #openstack-operators03:39
*** fragatina has quit IRC03:51
*** germs has joined #openstack-operators03:53
*** germs has quit IRC03:53
*** germs has joined #openstack-operators03:53
*** wvera has quit IRC03:55
*** germs has quit IRC03:58
*** fragatina has joined #openstack-operators03:59
*** Tyrantelf has quit IRC04:22
*** Tyrantelf has joined #openstack-operators04:23
*** markvoelker has quit IRC04:27
*** AlexeyAbashkin has joined #openstack-operators04:33
*** chyka has joined #openstack-operators04:34
*** wvera has joined #openstack-operators04:36
*** wvera has quit IRC04:36
*** AlexeyAbashkin has quit IRC04:37
*** chyka has quit IRC04:39
*** dmibrid_ has quit IRC05:11
*** fragatina has quit IRC05:20
*** fragatina has joined #openstack-operators05:20
*** markvoelker has joined #openstack-operators05:28
*** germs has joined #openstack-operators05:54
*** germs has quit IRC05:54
*** germs has joined #openstack-operators05:54
*** germs has quit IRC05:59
*** chyka has joined #openstack-operators06:23
*** chyka has quit IRC06:27
*** aojea has joined #openstack-operators06:31
*** dbecker has quit IRC06:31
*** aojea has quit IRC06:40
*** dbecker has joined #openstack-operators06:46
*** tuanla____ has joined #openstack-operators06:47
*** pcaruana has joined #openstack-operators06:53
*** tesseract has joined #openstack-operators07:15
*** paken has joined #openstack-operators07:16
*** rcernin has quit IRC07:25
*** damien_r has joined #openstack-operators07:25
*** dims_ has joined #openstack-operators07:48
*** dims has quit IRC07:49
*** AlexeyAbashkin has joined #openstack-operators07:51
*** germs has joined #openstack-operators07:54
*** germs has quit IRC07:54
*** germs has joined #openstack-operators07:54
*** gkadam has joined #openstack-operators07:55
*** germs has quit IRC07:59
*** racedo has joined #openstack-operators08:09
*** derekh has joined #openstack-operators08:09
*** gkadam_ has joined #openstack-operators08:37
*** gkadam has quit IRC08:39
*** rmart04 has joined #openstack-operators08:42
*** gkadam_ has quit IRC08:42
*** gkadam_ has joined #openstack-operators08:42
*** rmart04 has quit IRC09:06
*** rmart04 has joined #openstack-operators09:06
*** germs has joined #openstack-operators09:55
*** chyka has joined #openstack-operators09:58
*** germs has quit IRC10:00
*** chyka has quit IRC10:02
*** gkadam__ has joined #openstack-operators10:03
*** gkadam has joined #openstack-operators10:06
*** gkadam_ has quit IRC10:07
*** gkadam__ has quit IRC10:08
*** derekh is now known as derekh_afk10:13
*** gkadam has quit IRC10:32
*** gkadam has joined #openstack-operators10:35
*** AlexeyAbashkin has quit IRC11:05
*** admin0 has joined #openstack-operators11:06
*** AlexeyAbashkin has joined #openstack-operators11:07
*** paken has quit IRC11:43
*** germs has joined #openstack-operators11:56
*** germs has quit IRC11:56
*** germs has joined #openstack-operators11:56
*** tuanla____ has quit IRC12:00
*** germs has quit IRC12:01
*** liverpooler has joined #openstack-operators12:12
*** markvoelker has quit IRC12:28
*** markvoelker has joined #openstack-operators12:28
*** chyka has joined #openstack-operators12:28
*** simon-AS559 has joined #openstack-operators12:29
*** chyka has quit IRC12:33
*** aojea has joined #openstack-operators12:38
*** derekh_afk is now known as derekh12:48
*** aojea has quit IRC12:54
*** VW has joined #openstack-operators13:06
*** paken has joined #openstack-operators13:17
*** mriedem has joined #openstack-operators13:18
*** annabelleB has joined #openstack-operators13:44
*** jamesmcarthur has joined #openstack-operators13:46
*** vijaykc4 has joined #openstack-operators13:57
*** germs has joined #openstack-operators13:57
*** shintaro has joined #openstack-operators14:01
*** germs has quit IRC14:02
smcginnisMeeting today?14:03
shintarohi14:04
smcginnisHey shintaro. o/14:04
shintarohi smcginnis!14:04
shintaroI guess it's just two of us here.14:05
smcginnisI guess so.14:06
smcginnisHmm, I vaguely remember some talk about maybe skipping since it was right after the last one and so long before the next, but I thought that was two weeks ago.14:08
smcginnisOh well, I didn't really have anything to talk about. :)14:08
shintaroMe neither. I will check the recent ML discussion on co-location.14:09
shintaroI haven't had a time to really follow the discussion14:09
mrhillsmanI'm here huckleberry14:09
smcginnisMorning mrhillsman.14:09
shintarohi mrhillsman14:10
smcginnisshintaro: Yeah, that could change a lot. I should catch up on the latest there too.14:10
smcginnisLast I read, it sounded pretty favourable to happening.14:10
mrhillsmanwe did discuss in yesterday's uc meeting to confirm with folks here about the ptg/midcycle change14:10
smcginnisI think my question last week was if the current folks that were stepping up to sponsor an independent event would be offended if we changed things. And if they would still be willing to participate.14:11
shintarorebranding and seek for a better collaboration seems good idea to me14:11
jamesmcarthurHi all. Apologies for my tardiness.14:11
*** mihalis68 has joined #openstack-operators14:12
shintaroI guess we need mihalis68 to answer that question, smcginnis14:12
mihalis68hello. Sorry I'm late14:12
mihalis68what's the question?14:13
mrhillsmani don't see Chris as he would be able to speak on ...14:13
shintarohi mihalis6814:13
mrhillsmano/ mihalis6814:13
smcginnismihalis68: Morning. We were just chatting about the combined PTG/Ops prospect.14:13
mihalis68dammit I don't have scrollback14:13
smcginnismihalis68: I just mentioned I was wondering if the current planned sponsors of the independent event would be OK with changing things on them.14:14
mihalis68was attending to a ceph cluster - that's my new life14:14
mrhillsmanit seems we have consensus on the ML14:14
mrhillsmansmcginnis' question14:14
mrhillsmanand any concerns other than what has previously been mentioned14:14
mihalis68the update on the planned event is that so far the old venue is gone and the people who run the new place that I though was suitable seem to be flaky. So far we don't have a venue after all (I thought this was practically a formality but it seems they don't actually do events of this size, and perhaps the bloomberg events people didn't know that)14:15
mrhillsmanjamesmcarthur correct me if i am wrong but yay nay needs to happen pretty soon?14:16
mihalis68so I need to talk to my contacts at verizon and walmart in any case as there's no current confirmed plan. I will definitely ask them to consider the proposal to merge it into a redefined PTG14:16
mrhillsmanis amrith the person still on verizon side?14:17
mihalis68I don't think operators can formally agree to it before we actually see a proposal though. So far there's no location and no actual modified event definition14:17
mihalis68I don;t think we could ask a sponsor to say yes to it just yet14:18
mihalis68like where actually is it?14:18
mrhillsmanlocation cannot be revealed until after 4/914:18
mihalis68the actual travel implications matter - people are in locations14:18
mrhillsmanbut it is central iirc14:18
mihalis68the sponsors are in NY/NJ/W.VA14:19
smcginnisThat is what I have heard - central14:19
jamesmcarthurWe need a decision no later than April 414:19
mihalis68"central" is definitely not as good for those firms14:19
mihalis68I don't quite understand how there's a firm deadline but not really a firm proposal14:19
jamesmcarthurWell, we're negotiating a contract for the event location. If we were to give it out ahead of time, we would lose the ability to properly negotiate.14:21
jamesmcarthurIt's in the Central US, as I mentioned previously.14:21
mrhillsmanimho that is probably not a blocker14:21
jamesmcarthurRe: a proposal, as I mentioned in the email, we're happy to work with the Ops/UC/TC to update the language in a way that makes all parties comfortable.14:22
mrhillsmanprobably safe to assume foundation can handle all logistics14:22
jamesmcarthurWe're not going to go through that exercise though unless we know that you'll be willing to colocate.14:22
mrhillsmanand make messaging changes14:22
mrhillsmansorry on phone, fingers slower :)14:23
jamesmcarthurThat said, perhaps we could ask this group to work with teh UC on defining the language they'd like to see?14:23
mrhillsmanand again, just my opinion, though central may not be ideal, should be a blockee14:24
jamesmcarthurUltimately, it's up to the community, not the Foundation :)  We're just trying to facilitate the event space and details.14:24
mrhillsmanshould not be a blocker14:24
jamesmcarthurRe: sponsor locations, Verizon and WalMart both have a presence all over teh US. I'd be happy to have our sponsor team reach out to them to discuss details on sponsorship.14:25
mrhillsmanis there any reason not to say yes that is a strong blocker?14:25
jamesmcarthurWe also don't have to have the sponsorships settled by April 4.14:26
mihalis68it's not verizon and walmart corporations, it's the openstack teams. they have much more specific locations14:26
jamesmcarthurJust an agreement to colocate so that we can finalize our negotiations with the venue.14:26
*** racedo has quit IRC14:27
mihalis68previously the way ops meetups work is a proposal is made and the community assesses it. If there are competing ones they are put to a vote, otherwise we just publicize it and then if there's nothing wrong with a (single proposal) move forward with it14:28
jamesmcarthurWe just did that on the mailing list and there seemed to be broad acceptance of colocating.14:28
mrhillsman^14:28
jamesmcarthurIf there is a competing proposal, then let's go ahead and put that out to the same lists.14:28
mihalis68so given the interest in this colocated event that could proceed. That is separate from can I convert the interest of three sponsors of a proposed event in NYC in August into supporting something somewhere else at a different time14:28
mihalis68is the offer to cater to an ops meet up in a modified PTG contingent on some assumption of bringing the sponsors over?14:30
jamesmcarthurNot at all.14:30
jamesmcarthurOur events team can try to work with those particular sponsors, and we would of course continue to seek additional sponsorship for the event.14:32
jamesmcarthurTo be clear mihalis68: we're not asking you to manage the sponsors for a co-located event.14:32
jamesmcarthurIf those sponsors would prefer to stay on the east coast, there are surely OpenStack Days or meetups that they could support.14:33
mihalis68Actually OpenStack Days east didn't happen - not enough sponsors around here. That's why finding people interested in sponsoring an ops meet up in particular was pretty exciting.14:34
*** paken has quit IRC14:34
apriceo/14:35
mihalis68I understand that not all details can be presented in a  proposal right now, but it seems like some guidelines could be - for example "central USA" and something about how the event will be extended to have a specific "track" for operators would make it something that could be approved by the community in my opinion14:35
*** gkadam_ has joined #openstack-operators14:36
apricesorry im late, but catching up here. our team is happy to coordinate with you mihalis68 on providing details to Verizon and Walmart so they understand the combined event.14:36
jamesmcarthurmihalis68, that's exactly what's been communicated AFAIK. A separate, co-located event in the Central US just for Ops.14:37
apriceit is exciting that they are interested in sponsoring, so we want to make sure they are fully in the loop on this event proposal.14:37
mihalis68I think that's important.14:37
apriceWith such great buy-in from the community, I imagine they will be onboard as they have sponsored the North America Summits that are not necessarily located on the East Coast.14:37
mihalis68maybe I seem to be being difficult, but Bloomberg, for example (my employer) likes sponsoring ops meetups and declined to sponsor PTG14:37
mihalis68so this combined event would need to be a credible replacement for the ops meet up in this slot for ops14:38
apricethis is what the modified event language will help, IMO14:38
mihalis68given that, I would expect us to enthusiastically join in and I'd have every hope that verizon and walmart (and maybe others in NE USA) would to14:38
mihalis68*too14:38
*** gkadam has quit IRC14:38
apriceper jamesmcarthur's comment earlier, could this group provide suggested language that is more welcoming? otherwise, we can definitely draft something and collect feedback if that's easier14:39
*** kendallwaters_ has joined #openstack-operators14:39
mihalis68if we could get a draft of the language together I could meet again with the people in verizon, walrmart plus my line management and advocate throwing our support behind this event14:39
apricei think that revised language may help both the sponsors and folks on the fence fully understand how the events will be combined14:39
mihalis68yes exactly14:40
jamesmcarthurmihalis68: Are we in agreement that we have community buy-in for a co-located event?14:42
mihalis68do you see the formerly-PTG-parts and the formerly-ops-meetups being entirely separate? Part of the impetus behind examining co-location had been comments e.g. from Sean M that the first 2 days of the event are really cross-community14:42
mihalis68no I don't think we have that yet14:42
jamesmcarthurmihalis68: yes, as outlined, they will be completely separate events, with opportunities for cross-collaboration in the evening14:42
jamesmcarthurmihalis68: I didn't see any objections on the ML14:42
jamesmcarthurSo I'm trying to understand how we don't have buy-in14:43
mrhillsman^14:43
mihalis68without some definition of the event, there's nothing to agree to14:43
mrhillsmanI was just reviewing it as well and it seems language changes can be extracted from it14:43
mihalis68and for example I am not sure that 100% separate events is what was being proposed14:43
apricemrhillsman: ++14:44
mihalis68Sean and others told me "Chris you should definitely come to PTG - days 1 and 2 anyway they are totally cross-community". Well if I'm at a "totally separate event" we seem to be missing a trick here14:44
*** kstev has joined #openstack-operators14:45
smcginnisThat was before the conversations about combining events, TGF.14:45
smcginnis*TBF14:45
jamesmcarthurmihalis68: I believe they were communicating about the PTG. What we have proposed on the Ops Mailing list is a co-located event and agreed that we would rename/rebrand the event so that it's clear its' for both Ops and Devs14:45
mihalis68seems to be two events, co-located14:46
jamesmcarthurThis proposal is not about asking the Ops to attend the PTG. It's about co-locating the Ops Meetup with the PTG and creating a new event.14:46
mihalis68if I attend with my ops hat on, I go to the ops meet up event?14:46
jamesmcarthurWhere both Ops and Devs attend14:47
jamesmcarthurHowever, there is separate space for both groups.14:47
mihalis68so how long is this event?14:47
kendallwaters_5 days14:47
mihalis68Yeah, not good for me. ops meetups are 214:47
jamesmcarthurThe Ops aren't obligated to be there for the full 5 days. Also, please keep in mind that this is a meetup for the entire Ops community.14:48
shintaroI'm getting confused, too. So the first 2 days are also separate event?14:48
jamesmcarthurIt depends on the need of the groups that are meeting.14:48
mihalis68We can't agree to support an event "details to be filled in later"14:48
jamesmcarthurAgain, my reading of the mailing list was that the community already agreed to the concept.14:49
mrhillsmani think the point is we decide on the details14:49
mihalis68those who saw and read one email thread, yes14:49
jamesmcarthurCorrect.14:49
jamesmcarthurmihalis68: we also have a survey where 90% of the survey takers agreed that they would like to co-locate with the PTG14:49
jamesmcarthurReasons cited: It would be easier to justify travel expenses14:50
mrhillsmanand we discussed previously again, we would like logistics help with autonomy re schedule/details14:50
jamesmcarthurRight, this is an event for Ops, so ultimately you define teh event. 2 days, 3 days, 5 days...14:51
jamesmcarthurIn fact, we'd love to know so we can reserve the right amount of space.14:51
jamesmcarthurAnd we're asking for your help in defining the language.14:51
jamesmcarthurPerhaps it would be helpful to jump on a Zoom so we can all discuss this face to face?14:52
smcginnisSo how about this strawman. Monday and Tuesday are cross-project days where ops are welcome to attend SIG and other discussions, and if not interested can be travel days or whatever for them. Then Wed-Thurs are the two tracks/events where the ops folks have what has traditionally been done for ops meetups. Then Friday is a travel day or ops can stick around to follow up with dev-side things14:52
smcginnisthat they weren't able to get to over the week or wanted to follow up on.14:52
jamesmcarthurPerfectly doable :)14:53
shintaro+1 to smcginnis much more clear14:53
mrhillsman+1 smcginnis14:53
* jproulx1 also likes smcginnis strawman fwiw 14:54
mihalis68that sounds good. I would want the "ops are welcome to attend" bit to be clearly stated14:54
mihalis68this brings back the possibility of getting more out of this, which I liked14:54
smcginnis++14:54
mrhillsmanmihalis68 i think we agreed to that ;) more than once hehe14:54
mihalis68the "strictly separate" but "further away" proposal didn't seem like it gave me anything14:54
mihalis68mrhillsman the details matter very much14:55
mihalis68if there's two days that I'm invited to that are cross-community then great14:55
mihalis68previously in todays meeting it was stated "completely separate" right?14:56
jamesmcarthurI was referring to meeting space reserved just for Ops meetings14:56
mihalis68that didn't include that "mixing" that people thought would be so good (dev, ops all talking about shared concerns)14:56
mrhillsmanI don't think that was in relation to messaging14:57
jproulx1I like the  "everyone is invited to everything but these 2 days are best if you only have 2 days to spend" which smcginnis proposal seems to imply14:57
jamesmcarthurJust so we're all clear, here's the proposal in teh email:14:57
mrhillsmanhence my what have we not addressed already comment earlier14:57
jamesmcarthurIn addition to those questions, we'd like to pitch an option for you for the next Ops Meetup.  The upcoming PTG is the week of September 10 in North America. We have an opportunity to co-locate the Ops Meetup at the PTG.14:57
jamesmcarthurIf the Ops community was interested in this, we would have separate space with your own sessions and separate branding for the Ops attendees. This would also involve updating the language on the OpenStack website and potentially renaming the PTG to something more inclusive to both groups.14:57
jamesmcarthurEvenings at a co-located event would allow for relationship building and problem sharing. We're pitching this as a way to bring these two groups together, while still allowing them to have distinct productive events.  That said, we're in no way trying to force the situation. If, as a group, you decide you'd prefer to continue managing these events on your own, we're happy to support that in wha14:57
jamesmcarthurtever way we can.14:57
jamesmcarthurThe format of the event is really up to you all. I think smcginnis' plan is quite good.14:58
jamesmcarthurBut it can be defined in whatever way suits the Ops community.14:58
mihalis68the above is fine. Earlier in todays chat I though you were confirming that the events were separate for the full duration. But I prefer the idea in Sean's proposal15:00
jamesmcarthurSo, it sounds like we are all in agreement that an Ops Meetup colocated in the Central US with the Project Teams is approved?15:00
smcginnisI am hoping this will result in some discussion in a SIG taking place on Monday, some talk about some of the plans on Wed, then while having beers Wednesday night someone from the "ops" side and someone from the "dev" side being able to say, "hey, that thing we talked about earlier, so and so brought up X today that I think would make that even better."15:01
mihalis68actually I think we should inform the mailing list that this is the direction one more time15:01
jamesmcarthurmihalis68: would you like to take that on and chime in on the thread?15:02
mihalis68You can't really take the discussion so far as definitive for the community IMO15:02
mihalis68yeah. I might say "object by end of week" if that is ok with everyone15:02
mihalis68normally id say next meeting however I'll be in iceland and not IRCing15:03
shintaro+115:03
mrhillsman++15:03
smcginnis+115:03
mihalis68ok I shall do so.15:03
mihalis68I'll probably talk to my contacts just before I do so. If they are strong yes that will make it more emphatic15:04
mihalis68Hmmm, did anyone make this an IRC meeting?15:04
mihalis68it's quite consequential and I forgot to do that15:04
mihalis68if not I'll find another way to share the transcript15:04
mihalis68hmmm, but I don't have the first 10 minutes15:05
mihalis68can someone else share this meeting text somehow?15:05
mrhillsmanyep, I can15:05
mrhillsmanwill post to ML?15:06
mihalis68great, thanks!15:06
shintaroit should be under #link http://eavesdrop.openstack.org/irclogs/%23openstack-operators/15:06
mihalis68even though we didn't hash start meeting?15:06
mihalis68did not know that15:06
mrhillsmanI think so15:06
shintaroeverything is recorded :)15:06
mihalis68cool15:06
mrhillsmanlol15:06
mrhillsmanbig brother openstack eh15:07
mihalis68recorded but open15:07
mihalis68quite a bit different15:07
smcginnisWe could ask infra to put part of it under the meeting logs I think.15:07
smcginnisIf it matters that much. Otherwise we can just point to the IRC channel logs.15:07
mihalis68hate to burden anyone, but for todays meeting feels important/worth it15:08
mihalis68I think it does15:08
mrhillsmanI can follow up with infra15:08
mihalis68for the record, I'm going to chime in on the thread, but I will also make a separate new post which tries to call attention to an important change in the ground rules of the meetups in general. Having links will be helpful for that in particular15:09
mihalis68big thanks to Sean for the strawman15:09
mihalis68it made the proposal concrete, something I could sell to my boss15:10
*** pcaruana has quit IRC15:10
smcginnisHeh, no problem.15:10
shintaroyeah thanks15:10
smcginnisGlad it helped to solidify things. :)15:10
mihalis68I actually was thinking of pinging you privately and asking for something like that believe it or not15:10
*** vijaykc4 has quit IRC15:10
mihalis68alright... see you all on the mailing list a bit later, and perhaps at a mystery location in Central USA in September!15:11
shintarothank you all15:11
jamesmcarthurthanks everyone15:11
smcginnismihalis68: Thanks for taking on the ML piece. Will be good to get things finalized one way or the other, but I'm hoping we can all meet up somewhere in September.15:11
*** simon-AS559 has quit IRC15:11
*** shintaro has quit IRC15:12
mihalis68my pleasure. Sorry if I seem to be difficult here15:12
smcginnisGood to make sure everyone is on the same page.15:13
smcginnisIf anyone needs it, here is the start of today's IRC logs - http://eavesdrop.openstack.org/irclogs/%23openstack-operators/%23openstack-operators.2018-03-27.log.html#t2018-03-27T14:03:4015:13
*** germs has joined #openstack-operators15:13
*** germs has quit IRC15:13
*** germs has joined #openstack-operators15:13
mrhillsmanyou're not being difficult, things were just not landing home from your perspective15:15
mrhillsmanvaluable indeed as we have strawman now :)15:16
*** germs has quit IRC15:18
*** damien_r has quit IRC15:27
*** immune2iocane has joined #openstack-operators15:38
*** derekh has quit IRC15:53
*** derekh has joined #openstack-operators15:53
*** fragatina has quit IRC15:58
*** gyee has joined #openstack-operators16:00
*** germs has joined #openstack-operators16:01
*** germs has quit IRC16:01
*** germs has joined #openstack-operators16:01
*** chyka has joined #openstack-operators16:01
*** germs_ has joined #openstack-operators16:08
*** germs has quit IRC16:10
*** germs_ has quit IRC16:11
*** germs has joined #openstack-operators16:12
*** germs has quit IRC16:12
*** germs has joined #openstack-operators16:12
*** vijaykc4 has joined #openstack-operators16:17
*** rmart04 has quit IRC16:17
*** derekh has quit IRC16:21
*** germs has quit IRC16:22
*** pcaruana has joined #openstack-operators16:25
*** derekh has joined #openstack-operators16:27
*** germs has joined #openstack-operators16:29
*** germs has quit IRC16:29
*** germs has joined #openstack-operators16:29
*** germs has quit IRC16:32
*** germs has joined #openstack-operators16:43
*** germs has quit IRC16:43
*** germs has joined #openstack-operators16:43
*** VW_ has joined #openstack-operators16:52
*** VW has quit IRC16:54
*** germs_ has joined #openstack-operators16:55
*** germs has quit IRC16:56
*** fragatina has joined #openstack-operators16:56
*** VW_ has quit IRC16:58
*** VW has joined #openstack-operators16:59
*** derekh has quit IRC16:59
*** gkadam_ has quit IRC17:00
*** fragatina has quit IRC17:09
*** ckonstanski has quit IRC17:19
*** AlexeyAbashkin has quit IRC17:21
*** jamesmcarthur has quit IRC17:25
*** fragatina has joined #openstack-operators17:30
*** tesseract has quit IRC17:40
*** jamesmcarthur has joined #openstack-operators17:49
*** pcaruana has quit IRC17:51
*** paken has joined #openstack-operators17:51
smcginnismihalis68: Good write up of the proposal.18:04
*** rmart04 has joined #openstack-operators18:16
*** rmart04 has quit IRC18:16
*** jamesmcarthur has quit IRC18:17
*** fragatina has quit IRC18:22
*** annabelleB has quit IRC18:25
*** jamesmcarthur has joined #openstack-operators18:33
*** AlexeyAbashkin has joined #openstack-operators18:35
*** AlexeyAbashkin has quit IRC18:39
*** fragatina has joined #openstack-operators18:46
*** immune2iocane has quit IRC18:58
*** germs_ has quit IRC19:00
*** jamesmcarthur has quit IRC19:13
*** jamesmcarthur has joined #openstack-operators19:14
*** jamesmcarthur has quit IRC19:14
*** jamesmcarthur has joined #openstack-operators19:14
*** VW has quit IRC19:15
*** immune2iocane has joined #openstack-operators19:21
*** VW has joined #openstack-operators19:23
*** vijaykc4 has quit IRC19:30
*** harlowja has joined #openstack-operators19:34
*** germs has joined #openstack-operators19:55
*** germs has quit IRC19:55
*** germs has joined #openstack-operators19:55
*** rmart04 has joined #openstack-operators19:55
*** dmibrid_ has joined #openstack-operators20:00
*** germs has quit IRC20:02
*** germs has joined #openstack-operators20:02
*** germs has quit IRC20:02
*** germs has joined #openstack-operators20:02
*** liverpooler has quit IRC20:08
*** jamesmca_ has joined #openstack-operators20:20
*** rmart04 has quit IRC20:21
*** jamesmcarthur has quit IRC20:24
*** germs has quit IRC20:30
*** aojea has joined #openstack-operators20:34
*** jamesmca_ has quit IRC20:41
*** VW_ has joined #openstack-operators20:57
*** VW has quit IRC21:00
*** jamesmcarthur has joined #openstack-operators21:04
*** jamesmcarthur has quit IRC21:09
*** thingee has quit IRC21:18
*** immune2iocane has quit IRC21:32
*** fragatina has quit IRC21:35
*** fragatina has joined #openstack-operators21:35
*** kendallwaters_ has quit IRC21:38
*** paken has quit IRC21:40
*** mriedem is now known as mriedem_afk21:47
*** Caterpillar has quit IRC21:50
*** lbragstad has quit IRC22:15
*** rcernin has joined #openstack-operators22:16
*** fragatina has quit IRC22:21
*** fragatina has joined #openstack-operators22:21
*** aojea has quit IRC22:24
*** kstev has quit IRC22:27
*** germs has joined #openstack-operators22:31
*** germs has quit IRC22:31
*** germs has joined #openstack-operators22:31
*** lbragstad has joined #openstack-operators22:32
*** lbragstad has quit IRC22:32
*** germs has quit IRC22:36
*** Caterpillar has joined #openstack-operators22:40
*** fragatina has quit IRC22:58
*** fragatina has joined #openstack-operators22:58
*** AlexeyAbashkin has joined #openstack-operators23:12
*** fragatina has quit IRC23:14
*** fragatina has joined #openstack-operators23:14
*** AlexeyAbashkin has quit IRC23:17
*** immune2iocane has joined #openstack-operators23:24
*** harlowja has quit IRC23:32
*** immune2iocane has quit IRC23:32
*** chyka has quit IRC23:35
*** germs has joined #openstack-operators23:35
*** germs has quit IRC23:35
*** germs has joined #openstack-operators23:35
*** chyka has joined #openstack-operators23:35
*** germs has quit IRC23:36
*** germs has joined #openstack-operators23:36
*** germs has quit IRC23:36
*** germs has joined #openstack-operators23:36
*** chyka has quit IRC23:39
*** jamesmcarthur has joined #openstack-operators23:43
*** mriedem_afk has quit IRC23:43
*** jamesmcarthur has quit IRC23:47
*** germs has quit IRC23:58
*** germs has joined #openstack-operators23:59
*** germs has quit IRC23:59
*** germs has joined #openstack-operators23:59

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