Tuesday, 2016-08-02

*** armax has quit IRC00:09
*** r-daneel has quit IRC00:11
*** cdelatte has quit IRC00:23
*** saneax is now known as saneax_AFK00:31
*** dminer has quit IRC00:44
*** Apoorva_ has joined #openstack-operators01:25
*** Apoorva has quit IRC01:29
*** Apoorva_ has quit IRC01:30
*** armax has joined #openstack-operators01:53
*** mriedem has quit IRC02:23
*** markvoelker has joined #openstack-operators02:25
*** amitkqed has quit IRC02:30
*** markvoelker_ has joined #openstack-operators02:30
*** amitkqed has joined #openstack-operators02:30
*** markvoelker has quit IRC02:30
*** dtrainor has quit IRC03:03
*** ducttape_ has joined #openstack-operators03:56
*** VW has joined #openstack-operators04:10
*** ducttape_ has quit IRC04:10
*** markvoelker_ has quit IRC04:15
*** julim has quit IRC04:19
*** armax has quit IRC04:21
*** VW has quit IRC04:26
*** saneax_AFK is now known as saneax04:28
*** crinkle has quit IRC04:35
*** crinkle has joined #openstack-operators04:35
*** elo has joined #openstack-operators04:52
*** eric_lopez has quit IRC04:55
*** markvoelker has joined #openstack-operators05:10
*** ducttape_ has joined #openstack-operators05:11
*** ducttape_ has quit IRC05:16
*** markvoelker has quit IRC05:16
*** jsheeren has joined #openstack-operators05:23
*** derekjhyang has quit IRC05:42
*** markvoelker has joined #openstack-operators06:06
*** ducttape_ has joined #openstack-operators06:12
*** markvoelker has quit IRC06:13
*** ducttape_ has quit IRC06:17
*** cartik has joined #openstack-operators06:18
*** cartik has quit IRC06:39
*** tesseract- has joined #openstack-operators06:43
*** liverpooler has joined #openstack-operators06:45
*** belmoreira has joined #openstack-operators06:50
*** markvoelker has joined #openstack-operators07:02
*** markvoelker has quit IRC07:08
*** zul has quit IRC07:09
*** ducttape_ has joined #openstack-operators07:13
*** ducttape_ has quit IRC07:18
*** zul has joined #openstack-operators07:24
*** markvoelker has joined #openstack-operators07:58
*** markvoelker has quit IRC08:04
*** vinsh has quit IRC08:14
*** vinsh has joined #openstack-operators08:15
*** mfisch has quit IRC08:17
*** DuncanT has quit IRC08:19
*** DuncanT has joined #openstack-operators08:20
*** mfisch has joined #openstack-operators08:22
*** mfisch has quit IRC08:22
*** mfisch has joined #openstack-operators08:22
*** admin0 has joined #openstack-operators08:44
*** markvoelker has joined #openstack-operators08:54
*** electrofelix has joined #openstack-operators08:56
*** markvoelker has quit IRC09:00
*** admin0_ has joined #openstack-operators09:10
*** admin0 has quit IRC09:12
*** admin0_ is now known as admin009:12
*** ducttape_ has joined #openstack-operators09:15
*** snecklifter has joined #openstack-operators09:16
*** ducttape_ has quit IRC09:19
*** paramite has joined #openstack-operators09:33
*** markvoelker has joined #openstack-operators09:49
*** markvoelker has quit IRC09:56
openstackgerritMatthias Runge proposed openstack/osops-tools-monitoring: Rename router to network  https://review.openstack.org/34991209:58
*** admin0 has quit IRC10:25
*** admin0 has joined #openstack-operators10:26
*** jsheeren has quit IRC10:30
*** jsheeren has joined #openstack-operators10:30
*** markvoelker has joined #openstack-operators10:45
*** markvoelker has quit IRC10:51
*** ducttape_ has joined #openstack-operators11:16
*** ducttape_ has quit IRC11:21
*** VW has joined #openstack-operators11:27
*** VW has quit IRC11:31
*** matrohon has joined #openstack-operators11:39
*** markvoelker has joined #openstack-operators11:39
*** paramite is now known as paramite|afk11:40
*** markvoelker_ has joined #openstack-operators11:44
*** markvoelker has quit IRC11:44
*** ducttape_ has joined #openstack-operators12:08
*** matrohon has quit IRC12:12
*** paramite|afk is now known as paramite12:13
*** ducttape_ has quit IRC12:26
*** zul has quit IRC12:32
*** zul has joined #openstack-operators12:32
*** dmsimard|afk is now known as dmsimard12:55
*** bvandenh has quit IRC13:03
*** saneax is now known as saneax_AFK13:09
*** ducttape_ has joined #openstack-operators13:12
*** markvoelker_ has quit IRC13:23
*** julim has joined #openstack-operators13:26
*** julim has quit IRC13:26
*** mriedem has joined #openstack-operators13:28
*** ducttape_ has quit IRC13:29
mrhillsmang'morning13:30
*** julim has joined #openstack-operators13:33
*** vinsh has quit IRC13:34
*** cdelatte has joined #openstack-operators13:43
fifieldthi13:47
*** VW has joined #openstack-operators13:49
mihalis68good morning, or other time of the day where you are! :)13:55
fifieldthi13:55
*** ducttape_ has joined #openstack-operators13:56
*** dminer has joined #openstack-operators13:57
*** sbezverk has joined #openstack-operators13:57
fifieldthi all13:59
fifieldtanyone here for the ops meetups team meeting?13:59
serverascodeyup13:59
s3an2o/13:59
*** kbringard has joined #openstack-operators13:59
mrhillsmano/13:59
*** saneax_AFK is now known as saneax13:59
fifieldteven VW is here13:59
VWo/13:59
daleeso/13:59
VWhey fifieldt!  I represent that statement...13:59
kbringardahoy hoy14:00
fifieldt#startmeeting Ops Meetups Team14:00
openstackMeeting started Tue Aug  2 14:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is fifieldt. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
openstackThe meeting name has been set to 'ops_meetups_team'14:00
fifieldtHello all, and welcome to season seven of the Ops Meetups Team meeting :)14:00
fifieldtNB: If you're new, or just idling in the channel, be sure to have read:14:00
fifieldt#link https://wiki.openstack.org/wiki/Ops_Meetups_Team14:00
fifieldtfor background.14:00
fifieldtCheck out our agenda items at:14:00
fifieldt# link https://etherpad.openstack.org/p/ops-meetups-team14:00
fifieldtAs always: please write your name down on the agenda etherpad as a way of introduction, since we're a new crew.14:00
fifieldtSecondly, if there's something else burning to put on the agenda, please add it to that same etherpad.14:00
fifieldt#topic Review of action items from the previous meeting14:00
fifieldtFirst up, a quick run-through of our action items from the previous meeting.14:00
fifieldt.. if I can find the right tab14:00
fifieldt#link     http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-07-26-13.59.html14:01
fifieldt1/    VW to pull group names off the wiki and arrange an ops 101 by inviting them to join a Q&A style session in Barcelona14:01
fifieldtVW, guessing ongoing? I have some news to announce ~soon about the schedule for barcelona anyway14:01
fifieldtat least edgar has the emails of the group organisers on the wiki now14:01
fifieldt2/ mrhillsman to write up some proposed steps on how to set up audio14:01
fifieldtI think this was done, right?14:01
mrhillsmanyes14:02
fifieldt3/     mihalis68 to ask Kathryn about hotel room blocks14:02
VWyes - I think enough time has past, so I'll ping the UC folks and see if the wiki is updated/final14:02
fifieldtanswer is:    Ask for the bloomberg rate at Fitzpatrick Hotel Lexington Avenue14:02
fifieldt4/     fifieldt to email mihalis68 a sample agenda brainstorming broadcast - DONE14:02
fifieldt5/     mihalis68 to send agenda brainstorming broadcast - DONE14:02
fifieldt#link     http://lists.openstack.org/pipermail/openstack-operators/2016-July/010951.html14:02
*** markvoelker has joined #openstack-operators14:02
fifieldtthanks to mihalis68, VW and mrhillsman14:02
fifieldton to our real agenda14:02
fifieldt#topic  August Meetup14:02
mrhillsmanlol14:02
mihalis68my full answer was we can't assist with hotel blocks and then that note about the standing discount for BB at Fitz, just to be clear14:02
mrhillsman"real" agenda...as if14:02
fifieldtSo, mihalis68, any updates?14:03
mihalis68again sorry14:03
fifieldtthanks for sending out the agenda brainstorming!14:03
fifieldt#link https://etherpad.openstack.org/p/NYC-ops-meetup14:03
mihalis68I started putting what appeared to be the most well supported topics onto the timetable14:03
fifieldtencourage everyone you can to get there14:03
fifieldt#link https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit#gid=104694415614:03
fifieldtthere's the grid14:03
fifieldtOther updates14:04
mihalis68one question I spotted just now, there is a thought that containerizing the control plane subsumes Kubernetes14:04
fifieldtyeah14:04
fifieldtthoughts on that?14:04
mihalis68which is apropos as they are both on the itinerary. For me, I think they can both stand14:05
VWI would agree14:05
mihalis68My own approach to containerization would be a lot more modest than jumping into Kubernetes first14:05
mrhillsmanshould kubernetes be done first however?14:05
mrhillsmanin terms of the talks14:05
mihalis68it is day 2 currently14:06
mrhillsmanbeing that if we are expecting it to be part of the containerizing conversation14:06
mihalis68I think containerization is broader than kubernetes14:06
mrhillsmandefinitely14:06
mihalis68for example Canonical's approach is LXD+ZFS14:06
mihalis68no kubernetes14:06
mihalis68I put it first because it is on our minds and got the most +1s14:06
mrhillsmani gotcha14:07
fifieldtok, seems reasonable14:07
fifieldtmaybe let's see how the brainstorming etherpad proceeds14:07
mihalis68I guess what I would like to hear is just is the itinerary going in the right direction?14:07
mrhillsmani was saying in reference to the question you spotted14:08
*** jsheeren has quit IRC14:08
fifieldtso, it normally takes up to 2 weeks to get people to give their feedbnack on the etherpad14:08
mihalis68kubernetes is ... gnarly. In texas we were told about openstack on K and vice versa14:08
mrhillsmani like the schedule thus far14:09
mihalis68I just felt it could have second day first session as it might well be a pretty lively debate and need not be merely one section of containerization14:09
mrhillsmanand the fact you put forth the effort to start framing it14:09
fifieldt+114:09
fifieldtok, so that's ongoing14:09
mrhillsman^14:09
fifieldtanother update is14:09
fifieldtwe have 86 registered so far14:09
mihalis68ok so I'll just move to filling more of the big spaces out this week and I will ping the ad-hoc mailing when there is something to see14:09
mihalis6886! Very nice14:09
fifieldtI'm going to get a dump of the registration list and take a look14:09
fifieldtmaybe poke some people who didn't register14:10
fifieldtand make sure there aren't any evil people on there14:10
mrhillsmanhehe14:10
mihalis68ad-hoc mailing list is me emailing the people who seem to be on this chat and willing to get email about progress on the itinerary in detail14:10
fifieldtAfter the agenda brainstorming, then we move to allocating moderators14:10
fifieldtwhich we need at least a couple weeks for14:10
mihalis68evil? I wasn't told that would be a problem *MWHAHAHA*14:10
fifieldt:D:D14:10
mihalis68yes the timetable is tight now14:10
mrhillsman^14:10
fifieldtso, anything else on NYC?14:11
mihalis68not to get too off topic, but I have wheels now so personal life all reverting to normal. Can find more time again14:11
fifieldtphew, glad to hear14:11
mrhillsmangreat to hear14:11
mihalis68I will take an action to follow up things with Kathryn to do with signs, banners. I expect nothing so far, hbut then again I feel operators don't really care? Is that fair?14:11
fifieldtI feel that it's important for the sponsorship14:12
fifieldtto have something with the company logo14:12
fifieldtthat looks a bit nice :)14:12
fifieldtso people respect the enormous effort of the underwriter14:12
fifieldtin terms of printing, agenda handouts go down well too14:12
mihalis68Yes I think at a minimum we'll make the itinerary handouts (as designed by our graphic designers, once we finalize) and a big poster thing. That could be done quickly14:12
fifieldtVW, s3an2, serverascode, kbringard - any other musings on NYC?14:13
mihalis68kathryn recommended I try to get the itinerary in by ... well now actually14:13
mihalis68one request from me: anyone not getting gmail last week from me about the itinerary who wants to I can add and of course can remove anyone who doesn't want to14:13
fifieldtmihalis68, I am in a US timezone next week - maybe we could aim to smash it out on the phone quickly then14:13
mihalis68sure14:13
VWI can't think of anything fifieldt14:13
serverascodenothing right now, other than you mentioned issues with lunch14:14
fifieldtright, Erin is on lunch14:14
serverascodenot sure if help from the foundation is taking care of that14:14
fifieldtshould know very soon14:14
fifieldtthanks for the reminder serverascode14:14
fifieldt#action fifield to followup with Erin about Lunch14:14
mihalis68bloomberg is getting it catered, the concern I remember is how much eating space there is14:14
fifieldtright14:14
mihalis68we're providing breakfast and lunch14:14
mihalis68not sure details14:14
fifieldtalso breakfast! that is awesome14:14
fifieldtoh!14:14
fifieldtone more!14:14
fifieldtimportant thing!14:14
fifieldtEvening event.14:14
emccormickmihalis68: Add me if you don't mind. emccormickva@gmail.com14:14
fifieldtSo, how do we go about organising one of those ?14:15
mihalis68ack14:15
fifieldtand getting one or more organisations to pay for it?14:15
mihalis68we (i.e. Kathryn) are all in after venue and breakfast+lunch so evenings are wide open14:15
*** shamail has joined #openstack-operators14:15
fifieldtyup, confirmed it needs to be non-bloomberg14:15
fifieldtnot asking anyone on this meeting to front up the cash14:16
fifieldtbut perhaps someone can send a blast email14:16
mihalis68perhaps that could be mentioned on the [openstack-operators] mailing list?14:16
fifieldtasking if any organisation is interested?14:16
fifieldtyeah14:16
fifieldtcan anyone take that action?14:16
mrhillsmani'll ask my org14:16
*** zioproto has joined #openstack-operators14:16
mihalis68I'm ducking that one, feels ... not right14:16
mihalis68(for me I mean)14:16
zioprotoSorry I arrived late for the meeting14:16
mrhillsmani can send an email14:17
fifieldtmrhillsman, yeah, if you could email ops ML that'd be great :)14:17
mihalis68I agree14:17
mrhillsmanwould we be asking the org to handle the entire process?14:17
fifieldtmrhillsman, it could just be cash, and we could find someone else to assess venues if that worked14:18
fifieldtdepends on org requirements14:18
mihalis68an evening event can be quite simple in a place like manhattan.14:18
fifieldtmihalis68's favourite bar, maybe :)14:18
mrhillsman^14:18
fifieldt#action mrhillsman to email ops ML asking if anyone is around to organise/sponsor an evening event14:18
fifieldtI'd recommend after Day 114:18
fifieldtsince people go home on day 2 :)14:18
mrhillsman+114:18
fifieldtok, that's all I've got for NYC14:18
s3an2I agree after day114:19
fifieldtthanks mrhillsman, mihalis68, zioproto :)14:19
mihalis68+114:19
*** vinsh has joined #openstack-operators14:19
fifieldtnext up, I have some news!14:19
fifieldt#topic Barcelona14:19
s3an2:D14:19
fifieldtI had the chance to chat today with colleagues about summit scheduling14:19
mihalis68I'll look and see what bars are near Civic Hall, but I may not know that neighborhood particularly14:19
mrhillsmanexcited now14:19
emccormickOoooo14:19
fifieldt#topic https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit#gid=80351347714:19
fifieldtinside our magic spreadsheet of doom14:19
fifieldtis the barcelona tab14:19
fifieldtin green and purple are the rooms we will probably get14:20
fifieldtTuesday is the day14:20
fifieldtand we need to cram in as much as possible as early as possible14:20
fifieldtso we have as little as possible conflicting with x-proj sessions14:20
fifieldt(NB: time slots may be +/- 15 minutes - need to update)14:21
fifieldtbut in general14:21
fifieldtsame size as Austin14:21
fifieldtwith the need to have a bit more going on at the same time14:21
fifieldtalso: important point:14:21
mihalis68same size is great.14:21
fifieldtLightning talks14:21
*** rockyg has joined #openstack-operators14:21
fifieldtI managed to get 2 slots reserved over in the conference track "Ops War Stories"14:22
fifieldtspecifically for the lightning talks normally at the ops summit14:22
fifieldtadvantages include: more audience, nicer rooms14:22
VWooh - nice14:22
zioproto+1 for the Ops War Stories" at the summit14:22
mrhillsmanpanel?14:23
fifieldtmrhillsman, normally 5-10min lightning talks14:23
fifieldthowever14:23
fifieldtif you like panels :)14:23
mihalis68is this a call for war .... stories?14:23
fifieldtI believe some submissions to the track include panels14:23
fifieldtso, standby for news on that14:23
fifieldtanyway, now we have approximate rooms for barcelona14:23
fifieldtas soon as we feel it's appropriate, we can start agenda brainstorming for that :)14:23
emccormickI think we might want to wait until the agenda for NYC is set14:24
mrhillsman^14:24
emccormickso as to not cause distraction from the task at hand14:24
fifieldtthat sounds sane emccormick14:24
fifieldtalso, I find that sometimes ops ML discussions happen in the lead up to the summit that make for good fishbowls14:24
emccormickbut put the call out right before NYC and then people can argue things at the meetup14:24
mihalis68put barcelona agenda on nyc agenda? :)14:25
emccormickyep14:25
zioprotowhat means 'to make for good fishbowls' ?14:25
emccormickwell it doesn't have to be a session, but it certainly could be ;)14:25
mihalis68I'll add it to the ether pad brainstorm and if it gets +1ed so be it14:26
fifieldtzioproto, Ops ML conversation becomes a conversation in a room at the summit14:26
shamailfifieldt: +114:26
zioprotook now I get it14:26
fifieldtso, we do need to think about how to manage that brainstorming14:26
fifieldtwhether it's a long-lived etherpad14:26
VWzioproto: and example from the past was packaging14:26
fifieldtor a short, highly-advertised thing14:26
VWlots of ML chatter let do a few sessions in Ops meetups at summits14:27
fifieldtso, we normally do get a few good session ideas at the "feedback session" at the midcycle14:27
fifieldtwe feed those into a later brainstorming etherpad14:27
fifieldtanyway, I feel like I'm not making much sense anymore :)14:27
fifieldtsomeone else talk about barcelona :)14:28
mrhillsmanlol14:28
zioprotoIt would be great to have James Page or somebody from Canonical to speak about the Ubuntu packaging on NYC. Is anyone in touch with him ?14:28
mihalis68I guess several of us can only comprehend NYC right now14:28
mrhillsmani did get a little lost14:28
mrhillsman:P14:28
s3an2zioproto, +114:28
emccormickBarcelona: Will there be wine at lunch? :D14:28
mihalis68but we are meeting weekly with extra email conversation around NYC, it should start to gel soon14:28
mihalis68and I have to read up about barcelona more before I have any mental framework14:29
emccormickanyway, did we manage to get feedback in on the unstructured room configuration?14:29
zioprotoI always beg him via email to get support on the Ubuntu packaging. I hope it does not hate me already because I write always to him for support :D He is very competent, I would love to meet him again in NYC at the ops event.14:29
mihalis68we have a support contract with Canonical. I will fwd a question as to is a Canonical person coming through that point of contact14:30
fifieldtemccormick, I will verify that ASAP14:30
fifieldt#action fifieldt to verify the room setup for Friday at barcelona isn't some weird square thing14:30
mihalis68twisted sentence... bloomberg will ask canonical if they are sending someone to NYC meetup14:30
emccormickBrilliant14:30
fifieldtexcellent14:31
zioprotomihalis68: thanks. It would be great to have a Canonical tech person at the packaging working group.14:31
*** saneax is now known as saneax_AFK14:31
fifieldtIs there anyone else we want to "invite" to NYC?14:31
zioprotoI guess we could need the same for Centos/Redhat14:31
fifieldtoh, apparently one of my amazing colleagues may be joining us to ask about promoting NYC14:32
mihalis68I have just done the email to my business sponsor who has the relationship with Canonical14:32
*** jamesdenton has joined #openstack-operators14:32
fifieldtto make sure we hit the cap that mihalis68 has nightmares about :)14:32
*** aprice_ has joined #openstack-operators14:32
fifieldtit's aprice_!14:32
mihalis68I asked for James Page14:32
VWI'd prefer to keep the mid-cycle as vendor free as possible14:32
aprice_hello everyone :)14:33
fifieldtEveryone, please welcome Allison Price (aprice_)14:33
mihalis68hello Allison!14:33
fifieldtshe organised quite a few of the past ops meetups14:33
emccormickHi Allison!14:33
shamailhi aprice_!!14:33
fifieldtand is also the editor in chief of superuser14:33
VWHowdy, Allison14:33
mrhillsmanhey aprice_ !14:33
mihalis68VW we said that vendors could attend with "operator hat" on right?14:33
fifieldtamoungst other things14:33
zioprotoVW: good point. I though of James as he is the main committer on the Ubuntu Cloud Archives package repo. Not as a Canonical representative.14:33
mrhillsmanmihalis68 yes iirc14:33
fifieldtaprice_, I think you were going to ask something about the NYC event?14:33
mihalis68I've seen james talk, he's not dry vendory14:33
mihalis68not very14:34
fifieldt+114:34
mnaserif this is not too far away from NYC, I'd like to drop by as well14:34
mnaser(I know I kindof just jumped in here)14:34
mnaseri'm @ vexxhost and we run a fairly large public cloud here with two az's14:34
fifieldtmnaser, would be amazing to have you14:35
fifieldtdetails at https://etherpad.openstack.org/p/NYC-ops-meetup14:35
aprice_yes, in previous versions of the ops midcycle we have done a lot of promotion to the ops community and now that it’s run by this committee, I wanted to get input on promotion of the NYC ops midcycle :)14:35
mnaserand i've worked on both writing openstack code side of things and running openstack, it's not too far out from here14:35
aprice_of course taking into account total capacity and getting the right folks there14:35
fifieldt#topic Ops meetup promotion14:36
mihalis68I'd say Tom has managed to make this one quite crowd-sourced14:36
fifieldtThat's a great topic aprice_14:36
mihalis68not that I am familiar with previous committee structures14:36
emccormickWe're about 95 short of max capacity at this point so shouldn't be an issue to advertise it a bit more14:36
mihalis68but as a crowd-sourced thing it's lacking in promotion14:36
mihalis68IMHO14:36
mrhillsmanhehe14:36
fifieldtaprice_, maybe it would help to talk about some of the things we've done in the past?14:37
fifieldt(eg official twitter account?)14:37
mihalis68we did tweet out the poll for location choice quite a bit14:37
aprice_what we have done previously is just emailing folks who have indicated that they are operators at the summit, folks who have attended past ops midcycles and reminding the ops mailing lists14:37
mihalis68I might not have tweeted the registration though14:37
mihalis68there had been concern about not getting oversubscribed and not getting too much attention from pure marketing folks14:38
aprice_we have also tweeted, but tried to make sure to keep it clear that this is for operators who are running an OpenStack cloud to make sure the intent of the event is clear and that it’s not for noobs.14:38
s3an2tweeting registration may target the 'wrong' people ;)14:38
mihalis68yes14:39
mihalis68I think we did get enough visibility on the poll itself14:39
aprice_yes, we try to make sure to get the _right_ folks there through the different avenues14:39
fifieldt(for reference, in emails to people and on reg we post: ***Note***: This event assumes OpenStack ops knowledge and is _not_ appropriate for beginners, or a place to learn about OpenStack. The event contains relatively few 'presentations' and is mostly a discussion-style event. To find other OpenStack events in your area, please visit www.openstack.org/events. )14:39
zioprotoIf there are local openstack groups on the meetup.com website, we should make sure they know about out NYC date. I think there are many places that are just 1 hour flight away and they have a local meetup.14:39
mihalis68and after that people who are actually operators hopefully stay in touch via the mailing list14:39
fifieldtright, that's another thing we do is normally contact local meetup groups14:39
mrhillsman+1 zioproto14:39
aprice_not tweeting is fine so that emails and other points of contact can have the disclaimer that fifieldt shared about14:39
aprice_above*14:39
mrhillsmanthere will be quite a few folks in NYC already because of OpenStack Days East as well14:40
fifieldtok, so questions then14:40
s3an2zioproto, The Manchester meetup did put out the dates last week for NYC14:40
mrhillsmannot sure if anyone knows the committee there, but could reach out14:40
fifieldt1/ For NYC and Ongoing, do we email the list of people who indicated they were "Ops" in their previous summit registration?14:40
mrhillsmannot the vendors of course, the committee is mostly made of meetup organizers from what i know14:41
fifieldt2/ For NYC and Ongoing, do we email folks who have attended past ops midcycles ?14:41
*** carolbarrett has joined #openstack-operators14:41
fifieldt3/ For NYC and Ongoing do we remind the Ops ML14:41
VWI say a good reminder email for each event is always a good thing14:41
fifieldtso that's a yes for #2, VW?14:41
VWcause Ops folks tend to get "distracted" - running clouds and all14:41
VWyep14:41
mihalis68Can it be one email for the union of 1,2&3 people?14:41
shamailfifieldt: Could we also possibly start with creating a list based on people who have committed to OSOps repo, answered questions on Ask OpenStack, etc?  I am wondering if there are activities in the community that we could use to identify “ops” to invite as well...14:42
fifieldtok, shamail, how about14:42
VWor start the list with all those who've earned the Ops tag14:42
fifieldt4/ for NYC and Ongoing, do we email the list of "Active User Contributors"?14:42
mnaserI wouldn't have known about this if I didn't randomly stumble upon a discussion under #openstack-operators .. contacting the people who are marked as ops would have gotten my attention14:42
VWand expand from there14:42
fifieldtso thqat's a vote for #1, mnaser?14:42
shamailfifieldt: that would cover this scope I gave but it also includes a lot of extra things that would attract vendors14:42
shamail(local user groups, WG members, etc)14:43
mnaserfifieldt, vote for #1, correct14:43
fifieldtwould the disclaimer posted above be sufficient for that case shamail14:43
fifieldtor do we really need a subset of AUC?14:43
shamailSubset would be ideal (we would already have the data organized by activities so it should be minimal additional effort)14:44
fifieldtok, that's good14:44
aprice_does this list already exist or does it need to be updated post Austin?14:44
shamailSo #1 + AUC subset14:44
fifieldt5/ For NYC and ongoing, do we email the subset of AUC more likely to be ops?14:44
aprice_shamail I know that you have been gathering info, but didn’t know how much else was needed14:44
shamailaprice_: This list is being updated at the moment… I can send you the current list… (we will refresh this list until feature freeze)14:45
aprice_shamail: thanks!14:45
fifieldtok, everyone14:45
shamailThe subset we would be interested in is already available14:45
fifieldtthe options here are numerous14:45
fifieldtcan I ask you all to go to https://etherpad.openstack.org/p/ops-meetups-team14:45
fifieldtat line 2814:45
fifieldtand put a +1 against things you support14:46
fifieldtalong with any comments under each14:46
mihalis68I have to apoligise to AUC people as I barely know what it is14:47
mihalis68and also can't spell14:47
fifieldtnot a problem mihalis68, it's quite new14:47
fifieldtbasically, it's an attempt to recognise people who've made contributions to OpenStack in areas other than code commits14:48
mihalis68so I +1ed the previous attendees and mailing list and summit self-identifiers14:48
mihalis68nothing against AUC I just don't know it14:48
fifieldtmihalis68, https://wiki.openstack.org/wiki/AUCRecognition14:48
mihalis68thanks14:49
fifieldtso, it looks like there's an open question about AUC14:49
fifieldtshamail, would you be able to followup, maybe with aprice_14:49
fifieldtto work out which bits are ops-centric that we could use?14:49
shamailfifieldt: +1, will do14:49
fifieldt#action shamail to followup with aprice_ on AUC bits for ops and report back14:50
aprice_thanks shamail14:50
fifieldtwe also need to communicate this discussion to the ML14:50
aprice_i have also added a part to the etherpad where folks can add which subsets they think should be included14:50
fifieldtexcellent14:50
*** saneax_AFK is now known as saneax14:50
fifieldtaprice_, (or anyone) are there any other promotion ideas for the ops events to discuss?14:51
aprice_that is what we have typically done, but I am always open for suggestions if anyone has anything they would like to add14:51
fifieldtanyone?14:51
mnaserWhat about contacting users who submitted data to the OpenStack survey within a certain scale14:52
mnaserex: folks who have mentioned they run clouds > N cores who would benefit from this14:52
mnaserI don't know about the legalities of being able to contact them but it's an idea14:52
openstackgerritMerged openstack/osops-tools-monitoring: Fixed oschecks-check_keystone_api  https://review.openstack.org/34685514:52
fifieldtsurvey filler-outerers, what do you think?14:53
fifieldt(5 minute warning)14:53
VWsurvey filler-outers sounds good14:54
fifieldt+1 I think contacting people who have a deployment in the survey is a good idea :)14:54
VWbecause it's just a "hey, come to the ops thing" email14:54
aprice_ok - I can add that to the list and email an update to the ops ML with a reminder about the event and what promotions we have discussed here.14:54
aprice_so that everyone is in the loop :)14:55
mnaserplus, the foundation puts so much effort into getting people to fill out the survey so it's a good list, imho.14:55
openstackgerritMerged openstack/osops-tools-monitoring: python-novaclient-3.1.0+ compatibility  https://review.openstack.org/34673014:55
fifieldtthat would be great aprice_!14:55
fifieldt#action aprice_ to send a summary of the promotion discussion to the list14:55
fifieldtok, anything else on promotioin?14:55
fifieldtguess we got it covered :)14:56
mihalis68yes14:56
mrhillsmannope covered14:56
aprice_I think that’s it - if anything else comes up, please reply on the ML email I send or ping me directly!14:56
aprice_thanks :)14:56
mihalis68we are half-full already after all14:56
fifieldtthanks Allison!!14:56
fifieldtso, with 3 minutes left14:56
mrhillsman^14:56
fifieldt#topic all other business14:56
mrhillsmanthanks aprice_14:56
mihalis68any more people wishing email updates when more of the itinerary is filled in?14:56
mihalis68I have emccormick to add14:56
shamail+1, yes please, mihalis6814:57
mihalis68will do14:57
mrhillsmani think i am already there14:57
mrhillsmanbut if not, please add me14:57
fifieldtack14:57
mihalis68you are14:57
zioprotoI also think I am already there14:57
mihalis68I want this itinerary full, it not final by this time next week14:57
mihalis68I'll verify zioproto14:57
zioprotosaverio.proto14:57
mihalis68just my own goal for myself14:57
mrhillsmanoh, just one more thing14:57
mrhillsmanthx fifieldt :)14:57
fifieldt#action mihalis68 (own goal) finish itinerary by next meeting14:57
fifieldtok, brilliant14:58
fifieldtwith 1 more minute to go14:58
mrhillsmanand mihalis68 (Bloomberg)14:58
mihalis68yes all hail tom14:58
fifieldtanyone want to sing us out?14:58
mihalis68bizarrely the meld to lang of hope and glory but with horrid soccer lyrics came to mind14:58
mihalis68melody14:58
mihalis68so will NOT be singing that14:58
fifieldt¯\_(ツ)_/¯ _/¯(ツ)¯\_ ¯\_(ツ)¯\_ _/¯(ツ)_/¯14:58
mrhillsmanhttps://www.youtube.com/watch?v=Xr37BJA3cLI14:58
mrhillsman^ song :)14:58
fifieldtoook14:59
fifieldtmany many thanks all!14:59
mihalis68tom types that 'supson so fast....14:59
fifieldtsee you next week!!14:59
mihalis68librarian ook?14:59
fifieldt#endmeeting14:59
openstackMeeting ended Tue Aug  2 14:59:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
mrhillsmanadios14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.log.html14:59
* fifieldt runs to the next meeting14:59
fifieldthave a great $TIMEOFDAY all14:59
mihalis68IRC+eavesdrop is impressive system, like it14:59
mihalis68you too!14:59
* mrhillsman runs to another meeting as well...will this running ever stop ;.;15:00
*** shamail has left #openstack-operators15:00
*** dtrainor has joined #openstack-operators15:02
*** zioproto has quit IRC15:03
*** dtrainor has quit IRC15:07
*** dtrainor has joined #openstack-operators15:15
*** zhangjn has quit IRC15:20
*** belmoreira has quit IRC15:21
*** armax has joined #openstack-operators15:26
*** zhangjn has joined #openstack-operators15:26
mihalis68if anyone is still on, a possible venue for a social event after day 1 of the meet up would be upstairs at the Old Town Bar. http://www.oldtownbar.com15:37
mihalis68pro: very old bar with original fitting, semi-famous, 0.2 miles away (5 minutes walk)15:37
mihalis68con: very standard basic pub food15:37
mihalis68I shall post this to the mailing list now also, seems quiet here :)15:38
*** dtrainor has quit IRC15:41
*** admin0 has quit IRC15:50
*** dtrainor has joined #openstack-operators15:55
*** liverpooler has quit IRC15:55
*** liverpooler has joined #openstack-operators15:58
*** aspiers has joined #openstack-operators16:14
aspiershi all, anyone know who is planning the schedule for the operator track in the Barcelona design summit?16:18
*** piet has joined #openstack-operators16:22
*** krotscheck is now known as krot_sickleave16:27
*** Apoorva has joined #openstack-operators16:42
*** saneax is now known as saneax_AFK16:49
*** egonzalez has joined #openstack-operators16:49
*** tesseract- has quit IRC16:51
*** chlong has quit IRC16:58
*** rockyg has quit IRC17:00
*** julim has quit IRC17:02
mihalis68aspiers that was discussed n todays meeting. It's early stage but there's a tab for barcelona in the itinerary planning google doc and I think there's an ether pad for brainstorming/crowdsourcing the itinerary. Tom Fifieldt shared the slots that operators will get in barcelona17:03
aspiersmihalis68: great, thanks! I looked at today's minutes but obviously skim-read too fast to notice that17:04
*** piet has quit IRC17:04
aspiersmihalis68: see also my mail to openstack-operators@ in the last hour17:04
mihalis68to be completely honest I am not prepared to work on barcelona at all yet, still trying to pull together the material for NYC in three weeks17:05
aspiersoh yeah, that's understandable :)17:05
aspierswish I could be there17:05
mihalis68I suggested barcelona itinerary be a session in NYC, let's see if that is well received17:05
mihalis68although it might get too self-referential and circular17:06
mihalis68a plan to meet and talk about a plan to meet and talk about a...17:06
*** julim has joined #openstack-operators17:06
*** paramite has quit IRC17:08
aspierslol :)17:09
*** chlong has joined #openstack-operators17:11
*** crinkle has quit IRC17:17
*** piet has joined #openstack-operators17:18
*** Apoorva has quit IRC17:21
*** Apoorva has joined #openstack-operators17:22
*** liverpooler has quit IRC17:25
*** aprice_ has quit IRC17:25
*** aprice has joined #openstack-operators17:42
*** electrofelix has quit IRC17:54
*** VW has quit IRC17:59
*** VW has joined #openstack-operators17:59
*** crinkle has joined #openstack-operators18:00
*** rockyg has joined #openstack-operators18:25
*** julim has quit IRC18:29
*** julim has joined #openstack-operators18:31
mgagnefyi, I found this slow MySQL query in my logs: http://paste.openstack.org/show/545715/ which takes ~1.2s with ~800k rows in instances table. I created a key for vm_state,deleted fields and it now takes ~0.01s. CREATE INDEX `instances_vm_state_deleted_idx` ON `instances` (`vm_state`, `deleted`);18:33
mgagneI'm running Kilo18:33
*** aprice has quit IRC18:39
*** aprice has joined #openstack-operators18:40
*** julim has quit IRC19:04
*** julim has joined #openstack-operators19:06
*** fifieldt has quit IRC19:07
mriedemopen question: how common is it for people to set resume_guests_state_on_host_boot=True in nova.conf?19:08
mriedemwe had a compute host go down and like 36 guests weren't restarted19:09
mriedemlooks like setting resume_guests_state_on_host_boot=True in nova.conf would have done a hard reboot on those guests to get them running again19:09
*** carolbarrett has quit IRC19:12
*** fifieldt has joined #openstack-operators19:18
*** kstev has quit IRC19:20
*** rarcea has joined #openstack-operators19:23
*** rarcea has quit IRC19:30
*** jamesdenton has quit IRC19:32
*** aprice has quit IRC19:37
*** _ducttape_ has joined #openstack-operators19:56
*** ducttape_ has quit IRC20:00
*** kstev has joined #openstack-operators20:01
*** aprice has joined #openstack-operators20:02
*** julim has quit IRC20:04
*** _ducttape_ has quit IRC20:09
*** ducttape_ has joined #openstack-operators20:09
*** rarcea has joined #openstack-operators20:18
*** rarcea has quit IRC20:18
*** hj-hp has joined #openstack-operators20:20
*** aprice has quit IRC20:22
*** hj-hp has quit IRC20:23
*** hj-hpe has joined #openstack-operators20:23
*** ducttape_ has quit IRC20:24
*** aprice_ has joined #openstack-operators20:25
*** egonzalez has quit IRC20:26
*** hj-hpe has quit IRC20:27
*** ducttape_ has joined #openstack-operators20:27
*** hj-hpe has joined #openstack-operators20:27
*** openstackgerrit_ has joined #openstack-operators20:35
*** openstackgerrit_ has quit IRC20:36
*** fragatina has joined #openstack-operators20:50
*** fragatina has quit IRC20:50
*** fragatina has joined #openstack-operators20:51
*** snecklifter has quit IRC20:52
*** notmyname has quit IRC20:55
*** elo has quit IRC20:59
*** rockyg has quit IRC21:25
*** mriedem has quit IRC21:36
*** fragatina has quit IRC21:38
*** rockyg has joined #openstack-operators21:43
*** hj-hpe has quit IRC21:50
*** VW has quit IRC21:53
*** rockyg has quit IRC21:53
*** markvoelker has quit IRC21:54
*** aprice_ has quit IRC22:02
*** VW has joined #openstack-operators22:05
*** Apoorva_ has joined #openstack-operators22:06
*** aprice_ has joined #openstack-operators22:06
*** aprice_ has quit IRC22:07
*** kbringard has quit IRC22:08
*** VW has quit IRC22:09
*** Apoorva has quit IRC22:09
*** VW has joined #openstack-operators22:10
*** VW_ has joined #openstack-operators22:13
*** VW has quit IRC22:17
*** VW_ has quit IRC22:17
*** elo has joined #openstack-operators22:22
*** Apoorva_ has quit IRC22:43
*** _ducttape_ has joined #openstack-operators22:44
*** Apoorva has joined #openstack-operators22:44
*** ducttape_ has quit IRC22:47
*** delattec has joined #openstack-operators22:48
*** _ducttape_ has quit IRC22:48
*** david-lyle has quit IRC22:50
*** cdelatte has quit IRC22:51
*** david-lyle has joined #openstack-operators22:51
*** mriedem has joined #openstack-operators23:00
*** saneax_AFK is now known as saneax23:00
*** julim has joined #openstack-operators23:03
*** dminer has quit IRC23:04
*** vinsh has quit IRC23:05
*** VW has joined #openstack-operators23:30
*** VW has quit IRC23:34

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