Tuesday, 2018-11-27

*** slaweq has joined #openstack-operators00:16
*** mriedem_away has quit IRC00:23
*** slaweq has quit IRC00:24
*** fresta has joined #openstack-operators00:49
*** jonher_ has joined #openstack-operators00:50
*** fresta_ has quit IRC00:53
*** jonher has quit IRC00:53
*** jonher_ is now known as jonher00:53
*** jamesmcarthur has joined #openstack-operators01:04
*** jamesmcarthur has quit IRC01:08
*** slaweq has joined #openstack-operators01:16
*** slaweq has quit IRC01:24
*** VW_ has quit IRC01:50
*** slaweq has joined #openstack-operators02:13
*** bzhao__ has joined #openstack-operators02:20
*** slaweq has quit IRC02:24
*** bzhao__ has quit IRC02:27
*** bzhao__ has joined #openstack-operators02:34
*** slaweq has joined #openstack-operators03:16
*** slaweq has quit IRC03:24
*** slaweq has joined #openstack-operators04:11
*** VW_ has joined #openstack-operators04:12
*** VW_ has quit IRC04:17
*** slaweq has quit IRC04:24
*** VW_ has joined #openstack-operators04:59
*** VW_ has quit IRC05:16
*** jamesmcarthur has joined #openstack-operators06:04
*** jamesmcarthur has quit IRC06:09
*** slaweq has joined #openstack-operators06:11
*** slaweq has quit IRC06:24
*** faizy98 has joined #openstack-operators06:51
*** rcernin has quit IRC06:58
*** ahosam has joined #openstack-operators07:02
*** ahosam has quit IRC07:16
*** aojea has joined #openstack-operators07:21
*** pcaruana has joined #openstack-operators07:23
*** slaweq has joined #openstack-operators07:42
*** simon-AS559 has joined #openstack-operators07:47
*** gkadam has joined #openstack-operators08:08
*** priteau has joined #openstack-operators08:23
*** ahosam has joined #openstack-operators09:15
*** jackivanov has joined #openstack-operators09:16
*** derekh has joined #openstack-operators09:40
*** faizy_ has joined #openstack-operators09:43
*** faizy98 has quit IRC09:46
openstackgerritMerged openstack/ha-guide master: Update openstackdocstheme, use Storyboard  https://review.openstack.org/61990410:49
*** simon-AS559 has quit IRC10:59
*** electrofelix has joined #openstack-operators11:17
*** ahosam has quit IRC11:31
*** ahosam has joined #openstack-operators11:41
*** faizy_ has quit IRC11:54
openstackgerritMerged openstack/operations-guide master: Update openstackdocstheme, use Storyboard  https://review.openstack.org/61990312:02
openstackgerritMerged openstack/operations-guide master: Remove doc/source/common/source/  https://review.openstack.org/61992112:04
*** ahosam has quit IRC12:05
*** ahosam has joined #openstack-operators12:05
openstackgerritMerged openstack/operations-guide master: Remove tools/glossary-sort.sh  https://review.openstack.org/61990512:09
*** ahosam has quit IRC12:20
*** ahosam has joined #openstack-operators12:20
openstackgerritAndreas Jaeger proposed openstack/operations-guide master: DNM: Test translated docs building  https://review.openstack.org/61990212:56
*** takamatsu has quit IRC12:58
*** aojeagarcia has joined #openstack-operators13:09
*** aojea has quit IRC13:09
*** ahosam has quit IRC13:17
*** takamatsu has joined #openstack-operators13:21
*** VW_ has joined #openstack-operators13:34
*** takamatsu has quit IRC13:37
*** takamatsu has joined #openstack-operators13:43
*** hughsaunders has quit IRC13:50
*** mriedem has joined #openstack-operators14:18
*** mihalis68_ has joined #openstack-operators14:19
mihalis68_I'm expecting we'll do an Ops Meetups team meeting in about 40 minutes from now (10am EST)14:19
smcginniso/14:21
mrhillsmano/14:21
mihalis68_I'll be back here then, meanwhile I made a start on the agenda : https://etherpad.openstack.org/p/ops-meetups-team14:22
*** gkadam has quit IRC14:52
mihalis68_I presume the IRC channels are not merging, unlike the email lists?14:53
mrhillsmanthey are not14:54
mrhillsmanno reduction in IRC channels are currently planned afaik14:55
mrhillsmans/are/is14:55
smcginnisYeah, just ML.14:55
mihalis68_#startmeeting ops-meetup-team15:00
openstackMeeting started Tue Nov 27 15:00:43 2018 UTC and is due to finish in 60 minutes.  The chair is mihalis68_. 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: ops-meetup-team)"15:00
openstackThe meeting name has been set to 'ops_meetup_team'15:00
smcginniso/15:00
mihalis68_o/15:00
smcginnisPunctual today. :)15:01
mihalis68_#link https://etherpad.openstack.org/p/ops-meetups-team15:01
mihalis68_#topic actions15:01
*** openstack changes topic to "actions (Meeting topic: ops-meetup-team)"15:01
mrhillsmano/15:01
mihalis68_the needed final prep steps for the forum sessions got done and those sessions went ahead15:01
*** shintaro has joined #openstack-operators15:01
mihalis68_any other actions to report?15:01
shintarohi15:01
mihalis68_good evening, Shintaro!15:01
shintarohi mihalis6815:02
mihalis68_we're just see if there are any actions to report on15:02
mihalis68_seems not15:02
mihalis68_#topic Berlin wrap-up15:02
*** openstack changes topic to "Berlin wrap-up (Meeting topic: ops-meetup-team)"15:02
mihalis68_I'd say it mostly went well, except ops docs was in the furthest possible room at an early time late on during the week, and as a result was thinly attended15:03
mihalis68_comments from those who attended?15:03
smcginnisThat was a long hike.15:03
mihalis68_yes, hit me more than I anticipated15:03
smcginnisOn the plus side, I think we did have a few key people in there, so it was at least somewhat productive.15:03
mihalis68_and you're further!15:03
shintarowe're having our local ops meetup next week. Does anyone have anything that I should ask the attendees?15:03
mihalis68_I agree that ops docs session worked15:03
*** emccormick has joined #openstack-operators15:03
emccormicko/15:04
mihalis68_howdy15:04
mihalis68_we are just discussing how Berlin went15:04
smcginnisshintaro: Great, I hope the event goes well.15:04
mihalis68_the ceph session I moderated was full15:04
mihalis68_although it veered towards presentation again15:04
shintaroI want to bring up some topics from the Forum session. Docs will be one of them for sure.15:05
mihalis68_Shintaro I guess I'd be interested to know if there would be interest in your community in attending anything in europe in first half of 2019, and/or NA in second half15:05
shintaroah yes. I should ask that.15:06
mihalis68_i'd also like to know if they will be subscribing to the merged mailing list15:06
mihalis68_i feel like we don't connect with the operators community in some parts, particularly not on the old openstack-operators dedicated list15:06
shintaroI agree about that15:06
mrhillsmanit is probably too late but if not i suggest throwing out a email to the discuss ML for any feedback folks would like from ops attendees they felt they did not get during the summit15:07
mihalis68_if there are suggestions on how news could be disseminated I'm sure we could adjust/extend how we share out updates, anouncements etc15:07
smcginnisI'd also love to hear if there's any tips out of the smaller event on format and content that we should incorporate into our larger events.15:07
shintaroyes I like to discuss how we can bring outputs from local discussions to wider community.15:08
mihalis68_So the "ops meetups team" produced 3 Forum sessions15:09
mihalis68_is there any feedback on how we did?15:09
mihalis68_good or bad?15:09
mihalis68_mhillsman, for example, any thoughts?15:09
mrhillsman3 was definitely well below the normal15:09
emccormickIt was our lightest contribution to the forum yet, but there was a much shorter schedule this time15:09
emccormickwhat with Keynotes for 2 / 3 days and all15:10
smcginnisYeah, that went fast.15:10
mihalis68_one thing that didn't happen was a dedicated ops social event. We simply stayed at the marketplace mixer for the duration15:10
emccormickThat would be my only negative comment on the forum from an Ops perspective15:10
shintarowe had quite a number of people for onboarding session.15:10
emccormickI previously spent almost my entire summit in forum sessions. Not so this time15:10
mrhillsmanwe have discussed in uc meeting how we can do better and the decision was to reach out to ML for etherpads where folks felt they wanted more ops input15:10
mrhillsmanuse that to create an etherpad to send to ML frequently for ops feedback15:11
emccormickThe ML has been really bad at garnering Ops feedback lately15:12
smcginnisHard to tell at this point how the Open Infrastructure Forum will shape up with a 3 day Summit followed by a 3 day PTG.15:12
emccormickthe past 3 cycles or so it's like pulling teeth15:12
mihalis68_My feeling is there's a communication disconnect somewhere15:13
emccormickagreed15:13
mihalis68_obviously you're allowed to be someone running openstack infra without being on the mailing list15:13
emccormickMight be helpful to talk to meetup organizers to encourage local attendees to subscribe15:13
mihalis68_that "works" much better than being an OS dev15:13
mrhillsmani think at least one of the issues is inconsistent comms15:13
shintaroMy understanding on mrhillsman's idea was to give local meetup groups a common place to gather their opinion/feedback15:13
emccormickmaybe some "getting involved" presentation at the smaller events15:14
mrhillsmanand not enough comms15:14
mrhillsmanat least from the uc discussions we think those two things are critical15:15
mihalis68_We do mostly mailing list updates with sprinkles of tweets here and there15:15
emccormickI wonder if a large chunk of the operators are coming from enterprise backgrounds where they're used to being siloed15:15
mihalis68_what else would you suggest?15:15
emccormickThey just reach out to vendors when they need support15:15
smcginnisYou're probably right emccormick15:15
emccormickbut now they're in an opensource community but continue to operate in that enterprise mode15:15
emccormickwhich doesn't work.15:15
emccormickThey just pop onto a mailing list or ask.openstack.org when things break15:16
mrhillsmani could see that15:16
mrhillsmanso i think there are two things and i am def ok with anyone wanting to help of course in any way15:16
emccormickThat doesn't solve the problem I realize, but perhaps working on the cultural issue will garner more participation15:16
mrhillsmanwe have the ops meetup team (i forget what you call a team's focus or what not) and then the broader community aspect15:17
emccormickI think we did well dragging T-Mobile into the mix this past summit :)15:17
mrhillsmanfor the ops meetup team, i just think we went through a tough time the last 6 months or so, but are back on a good track, and we just want to communicate earlier and more frequently15:17
emccormickwe need to do that with more of these big orgs15:17
mrhillsmanfor the community wide aspect, ...15:18
mihalis68_t-mobile? I thought it was deutsche telekom?15:18
emccormicksame same15:18
mihalis68_ah ok15:18
emccormickI"m lazy and didn't want to type Deutsche Telekom15:18
mrhillsmanlol15:18
emccormick:D15:18
smcginnisDT, even shorter. ;)15:19
mihalis68_mrhillsman did you have a following thought on connecting better with the wider community?15:19
mrhillsmanit is a difficult problem, but i think the current best solution is to simply start communicating with them more often and bubble up concerns15:20
emccormickI would love to see the UC reach out to more of the big orgs that send people to summits but we never hear from in between15:20
mihalis68_I'm thinking we may need to do a recruitement campaign15:21
mihalis68_https://imgflip.com/i/2njxb115:21
mrhillsmanmaybe we could float a 3 question email for a couple months15:21
emccormickor those that are both upstream contributors and ops15:21
mrhillsmanyeah, better wording mihalis68_15:21
mrhillsmanand grow from there15:21
emccormickAT&T, OVH, City Networks, Vexxhost, etc.15:21
mihalis68_there's an actual impediment in communicating with "them"15:22
mrhillsmanstart small because honestly i get overwhelmed with the fragmentation and trying to strategize on it from holistic viewpoint15:22
mihalis68_I don't know who they are, I don't have their email addresses15:22
emccormickThey like to contribute things but from an ops perspective they're invisible15:22
mihalis68_does my meme link work?15:22
mrhillsmanhehe, it does15:22
emccormickhehe nice15:22
shintaroHow about public cloud WG and scientific WG ? aren't they ops?15:22
mrhillsmani like it15:22
mrhillsmanyes shintaro they are15:23
emccormickshintaro Yes definitely15:23
emccormickThose guys should be part of Ops discussions too. Some are for sure, but others are invisible15:23
mrhillsmannot to beat a dead horse; cause it's just wrong15:23
shintaroI wonder if they are interested in having a session at the ops meetup15:23
smcginnisIt would be great if they did.15:24
mrhillsmanbut the reason we thought reaching out to folks regarding etherpads they would have liked more ops feedback on and then pushing that for some time is that it would hopefully a) create connection for ops (i am involved and have a voice) and b) with that create a thread from event to event to keep conversation going (event to event being all/any event types)15:25
emccormickI think it's a fine idea.15:25
emccormickI just fear that your response will be crickets as things stand right now15:26
emccormickbut give it a go and let's see what comes back.15:26
mihalis68_are you willing to try that out mrhillsman?15:27
mrhillsmanpersonally when i was sitting in ops role day to day i found interacting with community not as beneficial because a) discussions were just discussions and never really landed, and b) by landing i mean resolution beyond code (monitoring tools, deployment, etc)15:27
mrhillsmanVW_ actually initiated the discussion and took on that action item15:27
mrhillsmanhowever as a fellow uc member we all (uc) are participating when he initiates it15:28
mihalis68_Does anyone happen to know if SuperUser has written up the great email merger?15:28
shintaroHow about feedback for deployment tools which we discussed during the Forum session?15:28
smcginnisI don't believe so. (superuser)15:28
shintaroI think just email notification15:29
mihalis68_I think it's an opportunity to try and attract people into that list who maybe didn't feel like joining the previous highly specialized lists15:30
VW_hey folks - I'm here15:30
VW_working a couple of things at the same time15:30
shintarohi VW15:30
mihalis68_We've spent quite a bit of time discusssing several things which boil down to : participation is low and getting lower, yet there are clearly a lot of people out there running openstack, so the operators exist15:31
VW_I'll craft an email to the mailing list this week15:31
mihalis68_mrhillsman tells us you have an initiative to try and connect the community more15:31
mihalis68_well, I think there's a problem : the mailing list doesn't go to some of the people we want to connect with15:32
mrhillsmanVW_ as always let me know if you need me to help; i figured you were quite busy15:32
mrhillsmanagreed mihalis68_15:32
mrhillsmanit is first step15:32
mihalis68_I'm thinking there should be a bit of a splash around the merged mailing list, perhaps a SuperUser article and communication by the foundation15:32
smcginnisI wonder for the ops folks here that are involved and are getting value out of it, maybe it would be good to have a SuperUser article written about your experiences and the benefits you see from it.15:32
mrhillsmananother step for example is to hit up the meetup groups directly15:32
VW_no, I can get it out there.  The hard part is we need to know what things they may want more feedback on now, but have to wait till March to make the sessions at the Ops meetup15:32
VW_but I'll start the conversation15:33
mrhillsmanok cool15:33
mrhillsmani think once we get some momentum, which we have had a few times before, we should double down on keeping it15:33
mihalis68_can the UC request that superuser do some journalism and get the story of the mailing list out? or do they mostly just get topic suggestions from authors?15:34
mrhillsmani will ping jeremy and nicole about it after meeting mihalis68_15:34
mrhillsmani think it is a great suggestion15:34
mihalis68_I hope that doesn't sound negative, I'm asking about their remit, not criticizing15:34
mihalis68_ok cool15:34
mihalis68_jeremy is the admin, right?15:34
*** yevi has joined #openstack-operators15:35
mrhillsmani think so, i know he has the most information afaik about it15:35
mrhillsmanfrom reading emails15:35
mihalis68_ok can I action you on that?15:35
smcginnisHe at least helps a lot and can get in touch with the right person.15:35
mrhillsmanso i figured he would be best, nicole is SU editor-in-chief15:35
mrhillsmanyes sir15:35
mihalis68_yeah I worked with nicole on our article about docs15:35
mihalis68_#action mrhillsman to suggest to superuser editor and jeremy stanley an article about the mailing list merge15:36
mihalis68_*merger15:36
mrhillsmanthx15:36
mihalis68_#info VW is planning to pick up the conversation about ops feedback to rest of openstack community via email to mailing list15:36
mihalis68_I'd like to move the topic on because there's some news/progress15:37
mihalis68_#topic ops docs15:37
*** openstack changes topic to "ops docs (Meeting topic: ops-meetup-team)"15:37
mihalis68_the summary is in the etherpad, but I think we agreed that the arch guide is "worthy" and should be assimilated15:38
emccormickAnd needs less work than the rest.15:38
mrhillsman++15:38
mihalis68_smcginnis can you do that? Is it a lot of work? Just the move bit?15:38
smcginnisI haven't checked yet, but I assume that's under openstack-manuals.15:39
smcginnisYeah, I can get things moved over like I did for the other ones. Then others can focus on getting the content updated.15:39
mihalis68_great15:39
mihalis68_#action smcginnis will look into moving the arch guide to enable others to update it going forwards15:39
mihalis68_we also discussed and tentatively agreed to break out ops docs into a separate IRC meeting15:40
mihalis68_perhaps monthly15:40
mihalis68_I'd be up for that15:40
mihalis68_there's a way to formalise a new regular IRC meeting, so if we have support for the idea I'll put in that submission15:41
mihalis68_I think part of the motivation is Adam Speirs is deep into the HA Guide rewrite but doesn't attend the ops meetups team meetings15:41
smcginnisThat makes sense. We've discussed here, mostly because of interested folks. But really not part of "ops meetup".15:42
mihalis68_yeah15:42
mihalis68_ops docs is a SIG after all15:42
mihalis68_#action mihalis68_ to setup the monthly IRC meeting for the ops docs SIG15:42
shintaroSIG makes sence15:42
mihalis68_there's nothing like a meeting coming up to focus my attention on getting something actually done15:43
smcginnisHaha, true.15:43
mihalis68_I will update the mailing list when I've done that15:43
mrhillsmanhehe15:43
mihalis68_the other thing I wanted to mention, just for the humor aspect: Erik learned the tools and submitted a patch to the operators guide15:43
mihalis68_immediately turned down :P15:44
mihalis68_(ok ok I'm exaggerating, sean suggested an edit)15:44
mrhillsmanlol15:44
mihalis68_ok enough on that15:44
mihalis68_#topic meetups 201915:44
*** openstack changes topic to "meetups 2019 (Meeting topic: ops-meetup-team)"15:44
mihalis68_I just spotted that there's a proposal!15:44
mihalis68_https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin15:44
smcginnisWoot!15:45
mihalis68_February or March, Berlin.15:45
smcginnisIt's a great location and venue. Was there for another meeting before the Summit.15:45
mrhillsmanyeah, i read over it, nice to see it already up15:45
mrhillsmanagree with smcginnis15:45
mihalis68_It's been a while, but IIRC our procedure should be to share this proposal as widely as possible with the community and then see if there's any competing offer15:46
mrhillsman++15:46
mrhillsmanyep, spot on15:46
mihalis68_if not we just ask for feedback on the mailing list, and then finally if no objections agree to the proposal here and record it and then it's pretty much a done deal15:46
shintaro+115:46
mihalis68_(if competing offers, we do a poll, but I don't see that happening, quite franky)15:46
mihalis68_ok, this is exciting15:47
mrhillsmando we want to set a time for a) competing offers and b) feedback before a vote15:47
mihalis68_#action mihalis68 to share the proposal with the community15:47
smcginnisEnd of December? Would be great to give DT a final go ahead so they can do any prep they need on their end.15:47
mrhillsman^15:47
mihalis68_We do want to settle more quickly, to avoid the problems of last minute handling of the important stuff like technical agenda and moderators15:47
smcginnismihalis68_: Any update on potential Bloomberg hosting that you can talk about?15:48
smcginnisGiven the (lack of) activity, maybe we just make it a couple weeks before we finalize?15:48
smcginnisGet it done before the holidays.15:48
mrhillsmani also remember saying that i would shore up moderator wrangling if that is still something we want me to do15:48
mihalis68_There's an update that I don't understand where they seem to be asking for dates again15:48
emccormickDid we want to ask if they were planning on proposing Budapest still and if Berlin was their preference?15:49
mihalis68_I'll have to clarify what's going on there15:49
smcginnisThat would be great mrhillsman15:49
emccormickWe put a placeholder there since they mentioned it, but should we be sure they didn't just forget?15:49
mihalis68_#action mihalis68 to get clarity on bloomberg's potential for hostinv15:49
mihalis68_how about we pencil in end of december deadline subject to updates next week?15:50
spotzhey all sorry I'm so late got busy with other things15:50
mrhillsman++ mihalis68_15:50
mrhillsmano/ spotz15:50
emccormicko/15:50
mihalis68_hi spotz15:50
mihalis68_so really good news about meetup #1 201915:51
emccormickmihalis68_ Do you want to ping our DT friends and see if they want to put in a proposal for Budapest still or just roll with Berlin only?15:51
smcginnisYeah, great to have something on the table.15:51
mihalis68_we'll get the word out about it and see if it meets with approval from the community, particularly the european community15:52
mihalis68_I would think if they have a proposal for a time and place, that's their preference, no?15:52
*** dtrainor__ is now known as dtrainor15:52
emccormickWell they mentioned both at the forum session so *shrug*15:52
mihalis68_it seems to me that this proposal could be highlighted in a SuperUser article, if we can get one going15:53
mihalis68_it's great to have news in such things15:53
emccormickI have no objections at all to Berlin. I still have half the menu to get through at my favorite restaurant :D15:53
smcginnis:)15:53
mihalis68_"hey everyone, there's a merged mailing list now, and here's a meetup we'll be discussing there!"15:53
emccormickJust didn't want to leave it out if they wanted it considered15:53
smcginnisAnother pub crawl emccormick? :)15:53
mihalis68_I'd love to see Budapest but I'd just feel weird saying "waitaminit, berlin? I thought we were going to be invited to budapest!"15:54
emccormickI like my drinking to be stationary I think ;).15:54
emccormickmore drinky less walky15:54
smcginnisProbably safer that way.15:54
smcginnismihalis68_: Hah, true. If they only proposed Berlin, I'm perfectly fine with that.15:54
emccormickespecially given my issues stumbling around in the dark15:54
mihalis68_emccormick I'll see you safely back to base again15:55
emccormickokie doke15:55
emccormickBALLARD!15:55
mihalis68_I'm pretty excited by all this15:55
emccormickhehe15:55
spotzSweet so glad my idea for you to join the two events is working out!!!15:55
mihalis68_#topic any other business15:55
*** openstack changes topic to "any other business (Meeting topic: ops-meetup-team)"15:55
smcginnisNothing on my end.15:56
mihalis68_I'm interviewing someone in a couple of minutes so please speak up now with any further discussion items15:56
shintaronothing from me15:56
emccormickNothing further from me.15:56
mihalis68_last call15:56
smcginnisThanks everyone15:56
mihalis68_agreed. Good meeting15:56
mihalis68_#endmeeting15:56
*** openstack changes topic to "Discussion of topics related to operating Openstack infrastructures at scale | Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators | Logs: http://eavesdrop.openstack.org/irclogs/"15:56
openstackMeeting ended Tue Nov 27 15:56:56 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-11-27-15.00.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-11-27-15.00.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-11-27-15.00.log.html15:57
shintarothank you all15:57
*** shintaro has quit IRC15:57
mihalis68_I'll share these links to the new list in a bit after my interview15:57
smcginnisHope it goes well.15:57
*** VW_ has quit IRC15:59
*** dansmith has quit IRC16:02
*** dansmith has joined #openstack-operators16:02
openstackgerritErik McCormick proposed openstack/operations-guide master: Update Horizon Admin Guide URL  https://review.openstack.org/61734416:02
*** jamesmcarthur has joined #openstack-operators16:11
*** emccormick has quit IRC16:25
*** emccormick has joined #openstack-operators16:48
*** emccormick has joined #openstack-operators16:48
*** emccormick has quit IRC16:48
*** jamesmcarthur has quit IRC16:48
*** emccormick has joined #openstack-operators16:49
*** jamesmcarthur has joined #openstack-operators16:49
*** gyee has joined #openstack-operators16:59
*** derekh has quit IRC17:23
*** simon-AS559 has joined #openstack-operators17:32
*** emccormick has quit IRC17:37
*** emccormick has joined #openstack-operators17:37
*** simon-AS559 has quit IRC17:39
*** ahosam has joined #openstack-operators18:03
*** simon-AS559 has joined #openstack-operators18:28
*** simon-AS559 has quit IRC18:32
*** simon-AS559 has joined #openstack-operators18:32
*** emccormick has quit IRC18:39
*** simon-AS559 has quit IRC18:39
*** ahosam has quit IRC19:08
*** electrofelix has quit IRC19:25
*** hughsaunders has joined #openstack-operators19:35
*** aojeagarcia has quit IRC19:55
*** simon-AS559 has joined #openstack-operators20:02
*** simon-AS5591 has joined #openstack-operators20:04
*** simon-AS559 has quit IRC20:07
*** jamesmcarthur has quit IRC20:13
*** slaweq_ has joined #openstack-operators20:44
*** yevi has left #openstack-operators21:01
*** slaweq_ has quit IRC21:03
*** ahosam has joined #openstack-operators21:04
*** pcaruana has quit IRC21:46
*** priteau has quit IRC21:47
*** emccormick has joined #openstack-operators21:47
*** slaweq has quit IRC22:03
*** slaweq has joined #openstack-operators22:19
*** slaweq has quit IRC22:24
*** ahosam has quit IRC22:24
*** simon-AS5591 has quit IRC22:38
*** priteau has joined #openstack-operators22:54
*** rcernin has joined #openstack-operators22:57
*** priteau has quit IRC22:58
*** jamesmcarthur has joined #openstack-operators23:14
*** jamesmcarthur has quit IRC23:18
*** emccormick has quit IRC23:19
*** slaweq has joined #openstack-operators23:29
*** slaweq has quit IRC23:33
*** mriedem has quit IRC23:46

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