Tuesday, 2018-03-20

*** germs has joined #openstack-operators00:01
*** germs has quit IRC00:01
*** germs has joined #openstack-operators00:01
*** germs has quit IRC00:05
*** ircuser-1 has joined #openstack-operators00:13
*** sn0wmonster129 has joined #openstack-operators00:26
*** liverpooler has joined #openstack-operators00:30
*** TxGirlGeek has quit IRC00:36
*** annabelleB has quit IRC01:11
*** germs has joined #openstack-operators02:02
*** germs has quit IRC02:06
*** fragatina has quit IRC02:15
*** chyka_ has joined #openstack-operators02:15
*** fragatina has joined #openstack-operators02:15
*** fragatin_ has joined #openstack-operators02:18
*** chyka has quit IRC02:18
*** fragatina has quit IRC02:19
*** fragatin_ has quit IRC02:22
*** chyka_ has quit IRC02:22
*** jbadiapa has quit IRC02:29
*** jamesmcarthur has joined #openstack-operators03:13
*** zerick has quit IRC03:14
*** zerick has joined #openstack-operators03:18
*** zerick has quit IRC03:20
*** chyka has joined #openstack-operators03:23
*** chyka has quit IRC03:28
*** germs has joined #openstack-operators04:03
*** germs has quit IRC04:03
*** germs has joined #openstack-operators04:03
*** germs has quit IRC04:07
*** fragatina has joined #openstack-operators04:14
*** fragatina has quit IRC04:16
*** fragatina has joined #openstack-operators04:16
*** jamesmcarthur has quit IRC04:18
*** dmibrid_ has quit IRC04:51
*** lpetrut has joined #openstack-operators05:02
*** fragatina has quit IRC05:58
*** lpetrut has quit IRC06:00
*** germs has joined #openstack-operators06:04
*** germs has quit IRC06:08
*** lpetrut has joined #openstack-operators06:12
*** masber has quit IRC06:12
*** Jack_Iv has joined #openstack-operators06:22
*** Jack_Iv has quit IRC06:26
*** masber has joined #openstack-operators06:44
*** masber has quit IRC06:47
*** masber has joined #openstack-operators06:47
*** jbadiapa has joined #openstack-operators06:53
*** lpetrut has quit IRC06:57
*** chyka has joined #openstack-operators07:00
*** chyka has quit IRC07:04
*** d0ugal has joined #openstack-operators07:12
*** d0ugal has quit IRC07:12
*** d0ugal has joined #openstack-operators07:12
*** jamesmcarthur has joined #openstack-operators07:18
*** d0ugal has quit IRC07:21
*** jamesmcarthur has quit IRC07:23
*** rcernin has quit IRC07:23
*** rcernin has joined #openstack-operators07:24
*** rcernin has quit IRC07:24
*** aojea has joined #openstack-operators07:30
*** pcaruana has joined #openstack-operators07:34
*** d0ugal has joined #openstack-operators07:49
*** tesseract has joined #openstack-operators08:00
*** AlexeyAbashkin has joined #openstack-operators08:04
*** germs has joined #openstack-operators08:05
*** germs has quit IRC08:05
*** germs has joined #openstack-operators08:05
*** rmart04 has joined #openstack-operators08:07
*** germs has quit IRC08:08
*** damien_r has joined #openstack-operators08:10
*** gkadam has joined #openstack-operators08:22
*** admin0 has joined #openstack-operators08:23
*** electrofelix has joined #openstack-operators08:38
*** lpetrut has joined #openstack-operators08:49
*** lpetrut_ has joined #openstack-operators08:50
*** lpetrut has quit IRC08:50
*** dbecker has joined #openstack-operators08:56
*** d0ugal has quit IRC09:02
*** racedo has quit IRC09:08
*** racedo has joined #openstack-operators09:11
*** baffle has quit IRC09:13
*** baffle has joined #openstack-operators09:14
*** derekh has joined #openstack-operators09:40
*** liverpooler has quit IRC09:54
*** germs has joined #openstack-operators10:05
*** germs has quit IRC10:05
*** germs has joined #openstack-operators10:05
*** germs has quit IRC10:10
*** chyka has joined #openstack-operators10:13
*** chyka has quit IRC10:19
*** masber has quit IRC10:43
*** rcernin has joined #openstack-operators11:02
*** rcernin has quit IRC11:06
*** masber has joined #openstack-operators11:08
*** masuberu has joined #openstack-operators11:12
*** masber has quit IRC11:14
*** pcaruana has quit IRC11:23
*** chyka has joined #openstack-operators11:35
*** chyka has quit IRC11:39
*** pcaruana has joined #openstack-operators11:55
*** racedo_ has joined #openstack-operators11:58
*** racedo has quit IRC11:58
*** aojea has quit IRC12:02
*** germs has joined #openstack-operators12:06
*** germs has quit IRC12:06
*** germs has joined #openstack-operators12:06
*** germs has quit IRC12:10
*** aojea has joined #openstack-operators12:14
*** d0ugal has joined #openstack-operators12:41
*** d0ugal has quit IRC12:41
*** d0ugal has joined #openstack-operators12:41
*** VW has joined #openstack-operators12:43
*** AlexeyAbashkin has quit IRC12:48
*** vijaykc4 has joined #openstack-operators12:58
*** AlexeyAbashkin has joined #openstack-operators13:10
*** fragatina has joined #openstack-operators13:17
*** mriedem has joined #openstack-operators13:18
*** vijaykc4 has quit IRC13:41
*** annabelleB has joined #openstack-operators13:46
*** jamesmcarthur has joined #openstack-operators13:47
*** jamesmcarthur has quit IRC13:47
*** jamesmcarthur has joined #openstack-operators13:48
*** simon-AS559 has joined #openstack-operators13:48
*** mihalis68 has joined #openstack-operators13:52
mihalis68#startmeeting Ops Meetup Team14:00
openstackMeeting started Tue Mar 20 14:00:28 2018 UTC and is due to finish in 60 minutes.  The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Ops Meetup Team)"14:00
openstackThe meeting name has been set to 'ops_meetup_team'14:00
mihalis68#link https://etherpad.openstack.org/p/ops-meetups-team14:00
smcginniso/14:01
jamesmcarthuro/14:01
mrhillsmano/14:01
mihalis68o/14:02
*** shintaro has joined #openstack-operators14:02
mihalis68hello everyone!14:02
mihalis68#topic actions14:02
*** openstack changes topic to "actions (Meeting topic: Ops Meetup Team)"14:02
shintarohi14:02
mihalis68I ask people to self-report their actions14:02
mihalis68I have a few in my queue14:03
mihalis68work on the ops guide wiki  - no progress other than the discussion in tokyo14:03
shintaroDone Tokyo!14:03
mihalis68and very well done it was too!14:03
smcginnisThanks for the great work shintaro!14:03
mihalis68I'm also working on a proposal to host in august, but we don't have anything yet14:03
shintarothank you14:04
mihalis68any more actions to report?14:04
jamesmcarthurmihalis68: Not sure if this fits in on the actions side or not...14:05
mihalis68actually one update on the ops guide wiki from Anne - she looked into setting an approver for that wiki, but couldn't find a setting. It seems (according to her) she was remembering a setting available in the women of openstack wiki (only)14:05
jamesmcarthurBut I wanted to note that the Foundation staff really wants to help the Ops community have a successful event.14:05
mihalis68so we actually don't have much of  a plan for documents that come out of core openstack docs into community-edited wikis14:06
jamesmcarthurI've been working on a lengthly email with some thoughts and would like to solicit feedback from this group before sending it to the larger Ops mailing list.14:06
mihalis68sure14:06
jamesmcarthurGreat :) I'll send out after the meeting today.14:07
*** germs has joined #openstack-operators14:07
*** germs has quit IRC14:07
*** germs has joined #openstack-operators14:07
mihalis68#topic tokyo recap14:07
*** openstack changes topic to "tokyo recap (Meeting topic: Ops Meetup Team)"14:07
mihalis68I emailed the ops meetups team with some thoughts on how tokyo went. Shintaro responded, but we haven't shared that with the wider community just yet14:08
mihalis68should I cut and paste here?14:08
shintaroor on the etherpad?14:08
mrhillsman^14:09
mrhillsmani think i responded - albeit very short response :)14:09
mihalis68I just dumped them in todays agenda14:10
mihalis68the things we need to do better next time are:14:11
mihalis68verify moderators at the beginning of each14:11
mihalis68day14:11
mihalis68have a master of ceremonies for each room if more than one14:11
*** germs has quit IRC14:11
mihalis68e.g. shintaro was in the telecom track room quite a lot and the main room didn't have anyone in charge14:11
*** kstev has joined #openstack-operators14:12
mihalis68more consideration of language issues14:12
shintarolanguage issues are more likely in Asian countries14:13
mihalis68we ended up having to suggest having translator support for some people who tried to participate in english but struggled. Now of course my japanese is ... none ... so definitely not a criciticism14:13
mihalis68anyone else have suggestions for the future based on how it went in Tokyo?14:13
shintaroWe need more promotion on agenda creation. and if possible, ask the attendees to put in some contents before the meetup.14:14
mihalis68I also felt that the "working session" concept met with varying success, let's say14:14
mihalis68yes, the agenda and moderators are the heart of the event, and the biggest struggle14:15
mrhillsmani think the working session came from new york and milan14:15
mihalis68for example : I put ceph on the proposed topics list, it received several +1s, so I volunteered to moderate that session14:15
mihalis68however I ended up doing more of a ceph lecture14:15
mrhillsmanor were more successful there because there were folks from UC working groups / teams in attendance14:15
mihalis68it was definitely "working sessions" in my first ops event (Philadelphia/comcast)14:16
mrhillsmanmexico city was the only one for me that did not have14:17
mrhillsmannot even on the agenda i mean14:17
mihalis68mexico city was working sessions, not sure what you're saying14:17
mihalis68for example the first session was documentation. I moderated but it was a roundtable discussion style thing, definitely not a presentation14:18
shintaroGood balance of ops and devs/foundation seems to work better14:18
*** chyka has joined #openstack-operators14:18
mihalis68yeah, for those not there there was a very interesting discussion on the often-discussed idea of somehow merging ops meetups and ptg14:19
mrhillsmani think of working sessions as actually working on something vs discussion14:20
mrhillsmandiscussion could be presentation and/or going through an etherpad14:20
smcginnisMaybe we need to change it from "moderator" to something else. To me at least, my expectation was moderating would just involve asking leading questions and making sure everyone got a chance to speak. But it sounds like we are actually looking for moderators to be closer to be something more than that.14:20
mrhillsmanjust my perspective/definition difference14:21
*** pcaruana has quit IRC14:21
mrhillsmanbut i got you14:21
mihalis68moderating is meant to be what you say Sean, as I understand it, however when the room is unresponsive you have to adapt or it feels like failing14:21
mrhillsman^14:22
smcginnisIt seemed like there was an expectation of a lot more background preparation.14:22
mihalis68I mean, the tradition handed down by Tom has always been that the moderator is just a faciitator14:22
mihalis68for LTS in mexico, for example just a few comments were needed to light the room on fire (metaphorically speaking!)14:22
mihalis68we had ops with strong feelings, representatives of distros who want this to happen e.g. maria from redhat14:23
mihalis68that conversation was definitely "working together" not a presentation from the front (although there's no code involved)14:23
jamesmcarthurPerhaps a light agenda for each working session would help facilitate things?14:23
*** chyka has quit IRC14:23
*** fragatina has quit IRC14:23
jamesmcarthurI mean, come in with some goals and discussion points for the gropu.14:23
mrhillsman^ we have those14:23
mihalis68we did have that for most sessions, but for some of them the room was quite unresponsive14:24
jamesmcarthurgot it14:24
jamesmcarthurthat's frustrating14:24
mihalis68I suspect culture and language were more of an impediment that I had previously anticipated14:24
mrhillsmansounds like it14:24
jamesmcarthurOne of the ideas we've been discussing with the UC (and I discuss this a bit in my email) is to start putting Ops tracks in OpenStack Days.14:25
mihalis68one of the local attendees felt the need to tell his fellow attendees to speak up and not feel intimidated. He mentioned that a -1 on a code review can feel like personal rejection, for example14:25
mrhillsmanmaybe not so much of a problem but rather enlightening factor14:25
jamesmcarthurMaybe if we get some feedback from users at the OpenStack Days events, that would provide some more ammo to spark conversation.14:26
mihalis68yes, my goal in mentioning is to work out how to do even better in future evnts14:26
mrhillsmani think also jamesmcarthur that can help ^14:26
mrhillsmanto know beforehand culture/language nuances14:26
mihalis68One interesting bit of info, PTG may not continue as is. Without getting into too much detail, the next one is the last one guaranteed to happen14:27
mihalis68so any plan to merge ops meetups into those is already questionable14:27
jamesmcarthurmihalis68: that's not been decided yet14:27
mrhillsman^14:28
shintaroI think I need to train local ops on how to do working sessions since they have not attended PTG nor Forum before.14:28
mihalis68that's what Ann told me14:28
smcginnisWe should know after the board of directors meeting right before the Vancouver summit.14:28
*** pcaruana has joined #openstack-operators14:28
mihalis68I'm not saying they won't happen after then, only that they are not guaranteed to happen14:28
jamesmcarthurPerhaps a miscommunication, but it's definitely still on the table.14:28
mrhillsmanshintaro i think that is a good comment in general and to jamesmcarthur point may be helped via openstack days, local user groups having some format for facilitating ops meetup like sessions14:29
mihalis68I'm not betting the farm on openstack days - openstack days east simply didn't happen last year (the ones for this neck of the woods)14:30
smcginnisI wonder though if the ops meetup was linked to it, if that would make it more likely to always happen.14:31
mrhillsmanthat's fine no concern for those that do not happen :)14:31
mrhillsmanpretty sure there are some user groups that are listed that are not active14:31
apricemihalis68: there are several OpenStack Days around the world that have voiced interest in having this event as the users and operators and interested in that kind of opportunity, particularly in Europe and Asia where the events continue to grow.14:31
mrhillsmanbut for those that are there are probably some things that could be helped using those that are14:31
mihalis68Oh definitely. When openstack days happen, I think operators should attend! I was disappointed we didn't get one in NE USA last year14:32
mihalis68in the meanwhile, though, there seemed good interest in a traditional Ops Meetup in NYC in August this year14:32
mihalis68by the way, the nature of sessions at those events is described fairly clear here:14:33
mihalis68#link https://wiki.openstack.org/wiki/Operations/Meetups14:33
mihalis68we had "general sessions" which we hoped would require light moderation, but in the end needed quite strong, active leading by the moderator14:33
mihalis68Any more for Tokyo recap?14:35
mrhillsmantimecheck - 25 minues :)14:35
mihalis68#topic august 2018 meetup14:35
*** openstack changes topic to "august 2018 meetup (Meeting topic: Ops Meetup Team)"14:35
mihalis68as mentioned, Bloomberg is trying to obtain a venue and make a proposal for an Ops Meetup in NYC, August this year14:36
shintaroI will put up some statistics on the etherpad later.14:36
mihalis68unfortunately Civic Hall (the venue we provided in august 2016) has ditched that space14:36
mihalis68we are talking to another similar organization, but can't show any results yet14:36
mihalis68along with Bloomberg, Verizon and Walmart have strong interest in that event, since they have teams in the region14:37
jamesmcarthurSo, this is also in the email, but we are able to host at the PTG in North America, but we would need to know by April 4.14:37
mrhillsmanpersonally, just my .02 of course, i think we should really resolve concerns related to ^14:37
mihalis68When I read the definition of PTG, it is not for me.14:37
mrhillsmanlike ^14:37
jamesmcarthurIf it was hosted there, Ops Meetup would get its own space, branding, etc..14:37
mihalis68This was discussed quite a bit in Tokyo14:37
smcginnisI think that would be great to make sure there was still separate branding and space.14:38
jamesmcarthurmihalis68: up to this point, it's been for Project Teams. However, the event could certainly change to fit the OPs Meetup as well.14:38
smcginnisSame event, just happens to be at the same time and place as the PTG.14:38
jamesmcarthurWe'd even consider renaming it.14:38
smcginnisAllowing at least some cross-polination.14:38
*** d0ugal has quit IRC14:38
jamesmcarthurBut yeah... it would allow for evening conversations and such, which I think could be fruitful for the whole community.14:38
mihalis68yes, I contend it would have to change, and in which case many things become possible14:39
jamesmcarthurIf you all decided to hold the Ops Meetup there, it has already been agreed that the branding around the event and space would be adapted for your needs.14:39
mihalis68here's what it says currently14:39
mihalis68"Who Should Not Attend14:39
mihalis68The event is not optimized for non-contributors or people who can’t relate to a specific project team. Each team is given a single room and attendees are expected to spend all their time with their project team. Attendees who can’t pick a specific team to work with are encouraged to skip the event in favor of attending the OpenStack Summit, where a broader range of topics is discussed."14:39
jamesmcarthurRight. I'm saying that would change.14:40
mihalis68ok good14:40
mrhillsmanlike summit and opendev14:40
jamesmcarthurBecause now it would be both Ops and a Project Teams meeting.14:40
mrhillsmantwo different events same space14:40
mihalis68Ann put it very nicely "when two people move in together, it's important that they both make changes, move their stuff, etc"14:40
smcginnis:)14:40
jamesmcarthurI would think of it more like you rented an apartment next door and get to see each other in the halls ;)14:40
mrhillsman^14:40
mrhillsmani was trying to think of something with less holes lol14:41
smcginnisGreat analogy. :)14:41
mrhillsmansame complex different apartments14:41
mihalis68Sure. Her comment was very apt for some ideas that were proposed previously where the ops event was sort of like crashing the event and trying to snag people in the hallways14:41
mrhillsmanhrm, never got that from previous ideas14:42
mrhillsmanthat's unfortunate but good to know14:42
*** annabelleB has quit IRC14:42
mihalis68is the next PTG defined anywhere?14:42
jamesmcarthurmihalis68: not yet. It would largely be dependent on if the Ops Meetup were co-located there.14:43
jamesmcarthurIn which case we would update the language and branding to reflect that.14:43
jamesmcarthurIt's just a web page at the moment and can easily change :)14:43
*** liverpooler has joined #openstack-operators14:44
jamesmcarthurWe'd be happy to collaborate with you all to make sure the language reflects the event you want to put on,14:44
mihalis68do you have rough dates?14:44
mrhillsmanshould this be voted on? feels like we will just continue to discuss/philosophy without14:44
jamesmcarthurSo that the Dev and Ops communities are comfortable14:44
mrhillsmanwith traditional as fallback14:44
jamesmcarthurweek of September 1014:44
jamesmcarthurin North America14:45
smcginnis15 minutes14:45
mrhillsmanor just do it :)14:45
jamesmcarthur(all these details are in the email I'm sending over too ftr)14:45
smcginnisWith NY already in the works, that makes it a little trickier.14:45
mihalis68right now we look like having a viable event in august with three sponsors and other stated interest. I'm not sure that's a "fallback"14:45
smcginnisBut I think if we decided to do this, it might make it more likely that the PTG will continue to be around past September.14:45
jamesmcarthursmcginnis: I think it would certainly show the board that it's an important event for the whole community14:46
jamesmcarthurmihalis68: Would those sponsors consider sponsoring it at a different venue?14:46
mrhillsman"around past September" ?14:46
smcginnisOr if it's too late to stop the New York train (or undesired at this point) at least declaring the public intention of aligning with the PTG would be good stuff to bring to the BoD in May.14:47
mrhillsmanor just around Sept14:47
mrhillsmanasking because Berlin is Nov of course14:47
VWhey guys - sorry for being mia for most of this14:48
jamesmcarthurTo be clear, we already have a venue and space lined up for September.14:48
mrhillsmanok14:48
mrhillsmanhey VW14:48
mihalis68where's the venue?14:48
jamesmcarthurWe're going into contract with them, so we can't disclose until after April 9.14:48
smcginnisjamesmcarthur: And would that venue accomodate another 100+ people for a simultaneous event.14:48
jamesmcarthurBut it's in the US14:48
jamesmcarthurAnd the date is the week of September 1014:48
jamesmcarthursmcginnis: yes14:49
smcginnisjamesmcarthur: Can you share what general area of the US?14:49
smcginnisEast, west, central?14:49
jamesmcarthurWe just have to give them the word that we want the space by April 414:49
jamesmcarthurCentral14:49
smcginnisjamesmcarthur: There aren't any trains close by? :)14:49
mrhillsmanhehe14:49
*** annabelleB has joined #openstack-operators14:50
mrhillsmanget your hook out the water smcginnis14:50
VWsmcginnis, mihalis68 - I, myself am a convert to this idea of co-location, so I'm happy to discuss with either of you in more detail offline14:50
smcginnismrhillsman: hehe14:50
mihalis68sure14:50
VWbut I think we can structure the sessions to honor the intent of both of the original events14:50
smcginnisVW: I was originally against it when we spoke about it in the past, but I think I've come around to the benefits.14:50
VWbut also reap the bennifit of after hour social interactions, etc14:51
smcginnisVW: Totally agree.14:51
mihalis68to answer the question of would the sponsors consider sponsoring a different venue, I am not sure they would tbh14:51
mrhillsmansame here, just quicker to come around i guess :)14:51
smcginnisThe after hours part I think could be really beneficial for all.14:51
*** kendallwaters has joined #openstack-operators14:51
aprice++14:51
mrhillsman9 minutes ;)14:51
mihalis68but it depends on the details. the amounts we put into ops meetups are small and bloomberg is very happy with the cost/benefit14:51
mihalis68we declined to sponsor ptg, it was a lot more money14:52
smcginnisBut I feel like there are a few of us now for this that are dominating the discussion. I don't want to railroad the whole group. (pun intended)14:52
mihalis68neither do i and sorry if it seems that way14:52
mrhillsmanlol14:52
mrhillsmani was saying earlier to that i think we need to just write down the concerns and address them14:53
mrhillsmanif we can at all14:53
mrhillsmanand if it makes sense, move forward14:53
smcginnisMaybe a ML thread?14:53
mrhillsmanif not, move forward :)14:53
smcginnisjamesmcarthur: You were going to start one, first to just us, then the whole list, right?14:53
jamesmcarthurshould I just send my email to the Ops Mailing list and get the discussion started?14:53
mrhillsmanapril 4th is the deadline for foundation14:53
mihalis68I can't speak for verizon and walmart, except to say they are very much looking to send operators to a get-together. Could absolutely be appropriate for a redefined event, but not for the traditional PTG as currently defined14:53
mihalis68jamesmcarthur I think the ops mailing list would be the right place to start yes14:54
jamesmcarthuralrighty... I'll send and duck ;)14:54
smcginnis:)14:54
* VW braces for impact14:54
*** electrofelix has quit IRC14:54
mihalis68this team tries to "facilitate" ops meetups, is not "Ops Board of Directors" or any governance type thing!14:54
smcginnisAnd if anyone here is strongly against it - please don't feel like you should stay quiet just because there are some for it.14:55
mihalis68mailing list and voting is the true discussion and decision mechanism14:55
mrhillsman^14:55
mihalis68#topic any other business14:55
*** openstack changes topic to "any other business (Meeting topic: Ops Meetup Team)"14:55
mihalis68think we covered a lot today14:56
smcginnisGreat discussion.14:56
mihalis6810 am EST seems to be vastly more successful time slot than the previous one14:56
mrhillsman++14:56
mihalis68apologies to those for whom it moves around due to us lunatics doing DST14:56
mrhillsman:)14:57
shintaroand now its 1 hour earlier for me, too14:57
mrhillsmanyour summaries help14:57
mihalis68that's... good?14:57
shintarowhich is good14:57
mihalis68ah, good! :)14:57
mihalis68my favorite memory of tokyo is still how long it took for those at the table to work out payment arrangements at "Prime Meat" that was hilarious14:58
VWmath is hard14:58
smcginnisEspecially after a couple beers. :)14:58
shintarowe were too drunk to do the calculation :)_14:58
mihalis68especially after ... "socialising"14:58
VWnice14:59
mihalis68i will say if the event is redefined and welcomes operators, I'd be in favor of convergence and try to drag my companies sponsorship to it14:59
mihalis68last call for comments!14:59
mihalis68#endmeeting15:00
*** 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:00
openstackMeeting ended Tue Mar 20 15:00:02 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-03-20-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-03-20-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-03-20-14.00.log.html15:00
mihalis68thanks everyone!15:00
shintarothank you mihalis6815:00
smcginnisI would like to hear Bloomberg, Verizon, etc input on the idea since they are willing to sponsor a separate event.15:00
smcginnisThanks all.15:00
jamesmcarthurthanks everyone for the discussion!15:00
*** shintaro has quit IRC15:00
mihalis68I'll talk to them and report back (and even give myself an action to do so!)15:00
smcginnismihalis68: Excellent, thanks!15:00
VWcool - and I'll be more on time next week to try and elaborate some of my thoughts :D15:01
VWin the meantime, I'm sure I'll be chiming in on the thread that comes out of jamesmcarthur's email15:01
*** saybeane has quit IRC15:02
*** TxGirlGeek has joined #openstack-operators15:06
*** d0ugal has joined #openstack-operators15:10
*** aojea has quit IRC15:17
*** VW_ has joined #openstack-operators15:25
*** VW_ has quit IRC15:27
*** VW_ has joined #openstack-operators15:27
*** VW has quit IRC15:29
*** TxGirlGeek has quit IRC15:45
*** fragatina has joined #openstack-operators15:45
*** TxGirlGeek has joined #openstack-operators15:47
*** chyka has joined #openstack-operators15:49
*** saybeano has joined #openstack-operators15:51
*** TxGirlGeek has quit IRC15:53
*** yevi has joined #openstack-operators15:53
*** TxGirlGeek has joined #openstack-operators15:54
*** TxGirlGeek has quit IRC16:02
*** TxGirlGeek has joined #openstack-operators16:04
*** VW_ has quit IRC16:05
*** dtrainor has quit IRC16:05
*** VW has joined #openstack-operators16:06
*** TxGirlGeek has quit IRC16:06
*** TxGirlGeek has joined #openstack-operators16:10
*** TxGirlGeek has quit IRC16:15
*** masuberu has quit IRC16:18
*** chito_ has joined #openstack-operators16:22
*** TxGirlGeek has joined #openstack-operators16:23
*** gyee has joined #openstack-operators16:26
*** rmart04 has quit IRC16:42
*** bradm has quit IRC16:42
*** gkadam has quit IRC16:47
*** jamesmcarthur has quit IRC16:47
*** AlexeyAbashkin has quit IRC16:53
*** masuberu has joined #openstack-operators16:59
*** dtrainor has joined #openstack-operators17:04
*** simon-AS559 has quit IRC17:05
*** damien_r has quit IRC17:06
*** kendallwaters has quit IRC17:10
*** chito_ has quit IRC17:11
*** bkero- has quit IRC17:11
*** amrith_ has quit IRC17:12
*** amrith has joined #openstack-operators17:13
*** amrith is now known as Guest4626417:13
*** fragatina has quit IRC17:17
*** annabelleB has quit IRC17:18
*** annabelleB has joined #openstack-operators17:19
*** liverpooler has quit IRC17:27
*** lpetrut_ has quit IRC17:30
*** chito_ has joined #openstack-operators17:30
*** mihalis68 has quit IRC17:31
*** aojea has joined #openstack-operators17:32
*** masuberu has quit IRC17:33
*** bkero has quit IRC17:39
*** bkero has joined #openstack-operators17:41
*** chito_ has quit IRC17:46
*** derekh has quit IRC17:52
*** bkero has quit IRC18:01
*** bkero has joined #openstack-operators18:02
*** Guest46264 has quit IRC18:10
*** amrith has joined #openstack-operators18:11
*** amrith is now known as Guest5626218:11
*** jamesmcarthur has joined #openstack-operators18:12
*** lpetrut has joined #openstack-operators18:13
*** AlexeyAbashkin has joined #openstack-operators18:14
*** AlexeyAbashkin has quit IRC18:14
*** AlexeyAbashkin has joined #openstack-operators18:15
*** harlowja has joined #openstack-operators18:23
*** Guest56262 is now known as amrith18:30
*** gyee has quit IRC18:30
*** fragatina has joined #openstack-operators18:35
*** aojea has quit IRC18:36
*** AlexeyAbashkin has quit IRC18:44
*** AlexeyAbashkin has joined #openstack-operators19:03
*** jamesmcarthur has quit IRC19:11
*** jamesmcarthur has joined #openstack-operators19:13
*** rmart04 has joined #openstack-operators19:15
*** rmart04 has quit IRC19:20
*** VW_ has joined #openstack-operators19:21
*** VW has quit IRC19:25
*** VW_ has quit IRC19:25
*** VW has joined #openstack-operators19:31
*** AlexeyAbashkin has quit IRC19:51
*** liverpooler has joined #openstack-operators19:51
*** tesseract has quit IRC19:56
*** annabelleB has quit IRC19:58
*** TxGirlGeek has quit IRC20:01
*** masber has joined #openstack-operators20:02
*** TxGirlGeek has joined #openstack-operators20:03
*** germs has joined #openstack-operators20:10
*** germs has quit IRC20:10
*** germs has joined #openstack-operators20:10
*** germs has quit IRC20:13
*** dmibrid_ has joined #openstack-operators20:19
*** masber has quit IRC20:32
*** TxGirlGeek has quit IRC20:34
*** TxGirlGeek has joined #openstack-operators20:36
*** TxGirlGeek has quit IRC20:38
*** TxGirlGeek has joined #openstack-operators20:48
*** TxGirlGeek has quit IRC20:53
*** jamesmcarthur has quit IRC20:55
*** TxGirlGeek has joined #openstack-operators21:01
*** jamesmcarthur has joined #openstack-operators21:03
*** jamesmcarthur has quit IRC21:04
*** jamesmcarthur has joined #openstack-operators21:04
*** chito_ has joined #openstack-operators21:05
*** annabelleB has joined #openstack-operators21:15
*** VW has quit IRC21:16
*** AlexeyAbashkin has joined #openstack-operators21:19
*** TxGirlGeek has quit IRC21:20
*** TxGirlGeek has joined #openstack-operators21:21
*** AlexeyAbashkin has quit IRC21:23
*** TxGirlGeek has quit IRC21:32
*** TxGirlGeek has joined #openstack-operators21:35
*** TxGirlGeek has quit IRC21:36
*** bradm has joined #openstack-operators21:37
*** jamesmcarthur has quit IRC21:39
*** VW has joined #openstack-operators21:41
*** yevi has left #openstack-operators21:44
*** lpetrut has quit IRC21:44
*** kstev has quit IRC21:46
*** VW has quit IRC21:51
*** admin0 has quit IRC21:52
*** TxGirlGeek has joined #openstack-operators21:55
*** kstev has joined #openstack-operators21:59
*** simon-AS559 has joined #openstack-operators22:05
*** jbadiapa has quit IRC22:07
*** germs has joined #openstack-operators22:10
*** germs has quit IRC22:10
*** germs has joined #openstack-operators22:10
*** rcernin has joined #openstack-operators22:13
*** bollig has quit IRC22:13
*** bollig has joined #openstack-operators22:14
*** germs has quit IRC22:14
*** dmibrid_ has quit IRC22:16
*** dmibrid_ has joined #openstack-operators22:17
*** jamesmcarthur has joined #openstack-operators22:18
*** AlexeyAbashkin has joined #openstack-operators22:19
*** liverpooler has quit IRC22:23
*** AlexeyAbashkin has quit IRC22:23
*** simon-AS559 has quit IRC22:24
*** TxGirlGeek has quit IRC22:26
*** TxGirlGeek has joined #openstack-operators22:28
*** TxGirlGeek has quit IRC22:38
*** jamesmcarthur has quit IRC22:41
*** TxGirlGeek has joined #openstack-operators22:41
*** TxGirlGeek has quit IRC22:52
*** TxGirlGeek has joined #openstack-operators22:55
*** harlowja has quit IRC22:57
*** chyka has quit IRC23:00
*** chyka has joined #openstack-operators23:01
*** TxGirlGeek has quit IRC23:02
*** masber has joined #openstack-operators23:03
*** masuberu has joined #openstack-operators23:04
*** TxGirlGeek has joined #openstack-operators23:06
*** masber has quit IRC23:08
*** khyr0n has joined #openstack-operators23:16
*** kstev has quit IRC23:18
*** AlexeyAbashkin has joined #openstack-operators23:19
*** AlexeyAbashkin has quit IRC23:23
*** jamesmcarthur has joined #openstack-operators23:24
*** jamesmcarthur has quit IRC23:29
*** Anticime1 is now known as Anticimex23:29
*** mriedem has quit IRC23:34
*** chyka has quit IRC23:46
*** harlowja has joined #openstack-operators23:49
*** mriedem has joined #openstack-operators23:52

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