Tuesday, 2017-10-03

*** jbadiapa_ has quit IRC00:04
*** sticker has joined #openstack-operators00:16
*** jbadiapa_ has joined #openstack-operators00:19
*** mriedem has quit IRC00:21
*** chyka has quit IRC00:41
*** chyka has joined #openstack-operators00:42
*** chyka has quit IRC00:46
*** chyka has joined #openstack-operators00:49
*** chyka has quit IRC00:54
*** penick has joined #openstack-operators01:18
*** penick has quit IRC01:25
*** gyee has joined #openstack-operators03:37
*** gyee has quit IRC03:38
*** VW_ has joined #openstack-operators03:45
*** VW has quit IRC03:45
*** Dinesh_Bhor has joined #openstack-operators03:47
*** gkadam has joined #openstack-operators03:52
*** dbecker has quit IRC03:53
*** arnewiebalck_ has joined #openstack-operators04:05
*** dbecker has joined #openstack-operators04:09
*** dmibrid_ has quit IRC04:51
*** pcaruana has joined #openstack-operators05:01
*** markvoelker_ has joined #openstack-operators05:03
*** markvoelker has quit IRC05:05
*** masber has joined #openstack-operators05:12
*** arnewiebalck_ has quit IRC05:16
*** yprokule has joined #openstack-operators05:17
*** pcaruana has quit IRC05:23
*** markvoelker_ has quit IRC05:37
*** markvoelker has joined #openstack-operators05:37
*** markvoelker has quit IRC05:42
*** rcernin has joined #openstack-operators05:53
*** Oku_OS-away is now known as Oku_OS06:09
*** simon-AS559 has joined #openstack-operators06:21
*** Apoorva has joined #openstack-operators06:23
*** simon-AS5591 has joined #openstack-operators06:23
*** nikhil has quit IRC06:24
*** vijaykc4 has joined #openstack-operators06:25
*** simon-AS559 has quit IRC06:25
*** vijaykc4 has quit IRC06:28
*** simon-AS5591 has quit IRC06:28
*** Apoorva has quit IRC06:30
*** simon-AS559 has joined #openstack-operators06:44
*** pcaruana has joined #openstack-operators06:44
*** simon-AS5591 has joined #openstack-operators06:46
*** vijaykc4 has joined #openstack-operators06:48
*** simon-AS559 has quit IRC06:48
aaksoshewless, enabling rootwrapd will probably help somewhat. then make sure you are using native interface for both ovsdb and openflow. finally upgrading neutron might also help as they have been switching to native netlink interface versus running iproute2 commands07:13
aaksothere were also inefficient code in iproute2 so upgrading that can help if touching to neutron is not possible07:15
*** vijaykc4 has quit IRC07:15
*** tesseract has joined #openstack-operators07:17
aaksothe performance is a very much "it depends" -question07:20
*** aojea has joined #openstack-operators07:31
*** aojea has quit IRC07:33
*** markvoelker has joined #openstack-operators07:38
*** racedo has joined #openstack-operators07:49
*** sticker has quit IRC07:49
*** vijaykc4 has joined #openstack-operators08:00
*** markvoelker has quit IRC08:12
*** saybeano has joined #openstack-operators08:22
*** vijaykc4 has quit IRC08:37
*** vijaykc4 has joined #openstack-operators08:37
*** vijaykc4 has quit IRC08:39
*** vijaykc4 has joined #openstack-operators08:39
*** spectr has joined #openstack-operators08:41
*** vijaykc4 has quit IRC08:44
*** vijaykc4 has joined #openstack-operators08:44
*** derekh has joined #openstack-operators08:44
*** arif-ali has quit IRC08:47
*** arif-ali has joined #openstack-operators08:51
*** electrofelix has joined #openstack-operators09:04
*** vijaykc4 has quit IRC09:04
*** vijaykc4 has joined #openstack-operators09:08
*** markvoelker has joined #openstack-operators09:09
*** TuanLA has joined #openstack-operators09:28
*** belmoreira has joined #openstack-operators09:39
*** markvoelker has quit IRC09:42
*** rmart04 has joined #openstack-operators09:44
*** chyka has joined #openstack-operators10:00
*** chyka has quit IRC10:05
*** belmoreira has quit IRC10:16
*** vijaykc4 has quit IRC10:32
*** markvoelker has joined #openstack-operators10:39
*** verdurin has joined #openstack-operators10:45
*** spectr has quit IRC11:07
*** markvoelker has quit IRC11:12
*** chyka has joined #openstack-operators11:35
*** yprokule_ has joined #openstack-operators11:38
*** yprokule has quit IRC11:39
*** yprokule_ is now known as yprokule11:39
*** chyka has quit IRC11:40
*** racedo has quit IRC11:41
*** racedo has joined #openstack-operators11:41
*** racedo has quit IRC11:41
*** vijaykc4 has joined #openstack-operators11:53
*** racedo has joined #openstack-operators11:53
*** liverpooler has joined #openstack-operators12:00
*** liverpooler has quit IRC12:00
*** liverpooler has joined #openstack-operators12:01
*** chyka has joined #openstack-operators12:05
*** TuanLA has quit IRC12:07
*** markvoelker has joined #openstack-operators12:09
*** chyka has quit IRC12:10
*** markvoelker has quit IRC12:12
*** markvoelker has joined #openstack-operators12:12
*** spectr has joined #openstack-operators12:24
*** dminer has joined #openstack-operators12:28
*** vijaykc4 has quit IRC12:29
*** vijaykc4 has joined #openstack-operators12:31
*** aojea has joined #openstack-operators12:33
*** catintheroof has joined #openstack-operators12:36
*** catintheroof has quit IRC12:36
*** catintheroof has joined #openstack-operators12:36
*** vijaykc4 has quit IRC12:37
*** vijaykc4 has joined #openstack-operators12:37
*** aojea has quit IRC12:38
*** gkadam has quit IRC12:38
*** catintheroof has quit IRC12:41
shewlessaakso: can you recommend any good documentation on enabling rootwrapd for mitaka?  I see the options in nova.conf (enable_rootwrap_daemon) but I'm not sure if there is more to it than just enabling that option12:43
*** rmart04 has quit IRC12:44
*** chyka has joined #openstack-operators12:51
*** catintheroof has joined #openstack-operators12:54
*** chyka has quit IRC12:55
*** emccormick has joined #openstack-operators13:05
*** mriedem has joined #openstack-operators13:07
*** chlong has joined #openstack-operators13:10
*** chlong_ has joined #openstack-operators13:10
*** liverpooler has quit IRC13:19
*** vijaykc4 has quit IRC13:44
*** smcginnis has joined #openstack-operators13:46
*** liverpooler has joined #openstack-operators13:53
*** liverpooler has quit IRC13:53
*** mihalis68 has joined #openstack-operators13:53
*** liverpooler has joined #openstack-operators13:54
*** liverpooler has quit IRC13:54
*** liverpooler has joined #openstack-operators13:55
*** verdurin has quit IRC13:57
*** shintaro has joined #openstack-operators13:58
*** spectr has quit IRC13:58
mriedemif anyone cares about seeing flavors have a description field on them, there is debate happening in -nova right now13:59
*** spectr has joined #openstack-operators13:59
mriedemabout whether we should add a description field to flavor, or just allow flavor.name to be the description and be mutable13:59
mihalis68anyone around for the ops meetups team meeting?14:00
shintaroo/14:00
mihalis68o/14:01
*** verdurin has joined #openstack-operators14:02
mihalis68#startmeeting Ops Meetup Team14:02
openstackMeeting started Tue Oct  3 14:02:21 2017 UTC and is due to finish in 60 minutes.  The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: Ops Meetup Team)"14:02
openstackThe meeting name has been set to 'ops_meetup_team'14:02
mihalis68#link https://etherpad.openstack.org/p/ops-meetups-team14:02
mihalis68agenda and sign-in sheet. Please add your name to attendees if you're here for this meeting14:03
mihalis68#topic review last week's action14:03
*** openstack changes topic to "review last week's action (Meeting topic: Ops Meetup Team)"14:03
mihalis68actions14:03
mihalis68I had a few actions and failed on most.14:03
shintaromrhillsman started email thread about support from Foundation.14:04
mihalis68For the session on openstack LTS releases I did contact a person I know at redhat and they would attend14:04
mihalis68does anyone if that session was accepted?14:04
shintaroI will be there14:04
mihalis68for the openstack operators guide (being converted to the wiki) I received a trial conversion from my contractor but have not yet uploaded it14:05
mihalis68that is also a proposed session14:05
mihalis68or perhaps the voting process is not complete? i don't know how that works, sorry14:06
smcginnisI think it's still in process.14:06
mihalis68if the LTS session proceeds I can send a representative from Bloomberg, same for operators guide14:06
mihalis68thanks Sean14:06
smcginnismihalis68: Given how much the topic of an LTS has been coming up, I'm pretty sure that session has a high chance of acceptance.14:07
mihalis68I would definitely hope so!14:07
emccormickhey guys. Sorry for being tardy.14:07
mihalis68no worries14:08
mihalis68I was just recounting the poor progress I made on actions14:08
mihalis68well, on some.14:08
mihalis68forgot to remind everyone about this meeting!14:08
shintaroWiki says draft Forum schedule will be open on 9th Oct14:08
*** chyka has joined #openstack-operators14:08
emccormickre: the session, all are still unreviewed.14:08
*** dminer has quit IRC14:08
VW_hey folks - sorry I'm late14:09
*** dminer has joined #openstack-operators14:09
*** VW_ is now known as VW14:09
mihalis68erik for operators guide wiki I have a better conversion in my inbox awaiting for review. For the LTS thing I have a contact in redhead who says they would represent, shintaro will attend, I can send someone. I will try and drum up a canonical contact (jill rouleau maybe>)14:09
mihalis68hi VW thanks for being here!14:09
mihalis68redHAT, thanks autocorrect you dimwit!14:09
mihalis68I also didn't yet email _med to get an update on whether he will run for UC.14:10
emccormicknice14:10
mihalis68#action mihalis68 still to email _med re: UC14:10
mihalis68#action mihalis68 to get the operators guide wiki pages updated14:10
mihalis68#action mihalis68 to propose article on LTS to SuperUser14:11
mihalis68#action mihalis68 to get Canonical comment on LTS session/representing14:11
mihalis68Phew.14:11
emccormickHope they give that one a big room ;)14:11
mihalis68any other comments on actions from last week?14:11
emccormickI did lots of nagging as directed.14:11
mihalis68my boss's boss is backing the superuser article, so that's good14:11
emccormickgot someone to take on the Ceph session14:12
emccormickhave a body to help run the fast-forward upgrade session14:12
emccormickalthough it sounds like I'm still going to end up running it.14:12
emccormickSo we, as a group, have 5 session in the hopper.14:13
*** chyka has quit IRC14:13
*** nikhil_ has joined #openstack-operators14:13
emccormickNova team covered some of the things that we wanted so I let them propose them.14:13
*** nikhil_ is now known as Guest6184914:13
mihalis68ah very nice14:13
emccormickand there's 3 NFV sessions already so I left that to others14:13
*** Guest61849 is now known as nikhil_k14:14
mihalis68smcginnis is Huawei able to represent at that session? That was an action on you last week I believe14:15
mihalis68#topic planning for Sydney14:15
*** openstack changes topic to "planning for Sydney (Meeting topic: Ops Meetup Team)"14:15
mihalis68I guess we really discussed this pretty well already?14:16
shintaroyes14:16
VWlooks like it14:16
mihalis68One very important thing I alluded to last week... no plans for an operators social event?14:16
mihalis68I mean, folks? What?14:16
emccormickhmm14:16
mihalis68it's a short event, easy to lose your chance if people all accept random vendor invites14:17
mihalis68(assuming there are still such things by then)14:17
shintaroright14:17
smcginnismihalis68: Sorry, had to step away. Yes, I can make sure someone from Huawei is there. Even if that ends up being just me to relay back some things.14:17
mihalis68erik you credit me with always leading the charge here, well, can't this time :|14:17
emccormickI hadn't thought about it. Is there a community event this time?14:17
emccormickI know there was supposed to be14:17
mihalis68ok cool, thanks smcginnis14:17
shintaroBoothcrawl on Monday14:18
mihalis68I think that's up to you attendees14:18
mihalis68 wish I was going14:18
shintaroMelbourne cup on tuesday?14:18
emccormickthere was something about the Melbourne Cup or something14:18
smcginnis:)14:18
emccormickyeah is that happening?14:18
emccormickinfo is lacking ;)14:18
VWlast I heard there would probably be no Stack c14:18
VWStack City14:18
VWonly the booth thing Monday evening14:18
emccormickhrmph14:19
VWas far as summit-wide things14:19
mihalis68could make this a low-complexity idea by just having a Avengers Unite... operators meet up within booth crawl14:19
emccormickWell it's a little late to drum up a sponsor and pick up a venue, but I guess I can shop around and propose a happy hour somewhere.14:19
mihalis68social secretary volunteer who is attending?14:20
emccormickexpo hall is a zoo.14:20
smcginnisEven if it's not sponsored, might be nice to have a time to just join up for socializing somewhere outside the expo hall.14:20
mihalis68you can pull off to one side there's normally space somewhere14:20
mihalis68I was just thinking everyone could go score a nice cold beer from a booth and then after a few minutes head on over to a side area where there's space e.g. sometimes the theatre isn't busy during the crawl14:21
smcginnisNot a bad idea.14:21
shintaroWe don't have a booth so I will be free during the crawl14:21
emccormickseems fine to me.14:22
mihalis68I put this idea on the agenda14:23
mihalis68anything else for sydney?14:23
emccormickMaybe we could set up a SYD-Ops-booze etherpad and tell people to post if they're going to a place and want company ;)14:23
shintaro+114:23
emccormicksort of worked in MEX14:23
mihalis68#action emccormick to make an ether pad for social event planning for sydney for OS ops14:23
mihalis68well volunteered erik :)14:24
VWwe do have a session for this group right - that I'm going to moderate?14:24
emccormickwheee14:24
mihalis68a catch-up yes14:24
emccormickyes14:24
VWjust double checking what all I signed up for :)14:24
emccormickwell it's on the request list anyway14:24
mihalis68that's more laptops and ether pads, less beer14:24
VWcool14:24
mihalis68normally14:24
emccormickwell, the first one in Barcelona turned into me getting back to my hotel at 3am so...14:24
mihalis68#topic 2018 meetup #1 Tokyo14:25
*** openstack changes topic to "2018 meetup #1 Tokyo (Meeting topic: Ops Meetup Team)"14:25
mihalis68shintaro has provided some updates on the agenda already14:25
shintaroI wrote some update on etherpad14:25
mihalis68the dialog is underway between Ops Meetups team and the foundation14:25
mihalis68mrhillsman emphasized that he thinks themed events work better14:26
mihalis68I know we discussed a Telecom track for Tokyo14:26
mihalis68although I think that should be up to the hosting org each time, personally14:26
shintaroyes, I have updated the agenda planning etherpad too14:26
shintaroincluding themed track14:26
mihalis68oh great14:26
mihalis68perhaps we can ask the Foundation to highlight this event specifically with the track?14:27
mihalis68we don't have anyone from the foundation here at these meetings any more14:27
shintaromrhillsman was thinking OpenDevConf as an model for themed track14:28
mihalis68shintaro do you want to contact Lauren to discuss the foundation starting to publicize your meet up?14:28
emccormickThat seemed like a much bigger and better funded event than what we usually manage to pull off14:28
mihalis68did you go emc?14:28
shintaroyes I will.14:28
smcginnisI do know the foundation is concerned about getting overloaded with running too many conferences. But I think with the success if OpenDev, if they can piggy back on this event, that might help things.14:29
emccormickIF we get 50 or 60 people again it kind of nukes the whole multi-track idea. Hopefully that's not the case14:29
mihalis68#action shintaro to contact openstack foundation events staff (Lauren Sell) to start publicizing Tokyo meet up, especially Telecom track14:29
emccormickI did not14:29
emccormickI watched everyone's tweets jealously though.14:29
mihalis68Can someone who attended or knows about OpenDevConf explain what we're missing that they had? Or what they did well that we do not?14:29
smcginnisHype?14:30
emccormickI never heard about it until everyone was there. Not sure how I missed the hype.14:30
shintarothe theme was Edge computing and was kind of hype, but good thing was the Foundation managed to get people from different organizations and also had dev people there14:30
smcginnisWell, not hype about the event, but hype about this cool new things called "edge computing". :)14:30
emccormickah. A hook14:31
emccormick;)14:31
*** chlong has quit IRC14:31
*** chlong_ has quit IRC14:31
mihalis68mrhillsman did attend OpenDevConf but is sadly not here today14:32
shintaroMicheal Still from Nova lead the main architecture session which gave a kick to the whole event14:32
mihalis68I can hardly give him an action to explain that in hi absence14:32
smcginnisETSI did an NFV event in parallel in Denver. I wonder if we are going to have a telecom track if it would make sense to contact someone with that org and get something going with them too.14:32
smcginnisAnother community to reach out to14:32
*** chlong has joined #openstack-operators14:32
emccormickThey proposed a session for the forum14:32
smcginnisOK, good.14:32
mihalis68I think that' s a very good idea14:32
emccormickAction Shintaro to attend and prod them about Tokyo14:33
shintaroI will :)14:33
smcginnisThey were more dev focused in Denver, but I would think they could have some good operator subjects.14:33
mihalis68the Ops Meetups idea shouldn't be some kind of private community, we're ops, we do it all, we should partner up with groups that can make these events zing14:33
smcginnis++14:33
VWyep14:33
mihalis68#action shintaro to reach out to ETSI about partnering for Telecom Track in Tokyo mid-cycle14:33
mihalis68ok good14:34
mihalis68any more about Tokyo?14:34
mihalis68again at risk of repeating myself is there an Ops social event?14:34
mihalis68I find Tokyo intimidating14:34
mihalis68I'm not going to venture out very far solo14:34
smcginnismihalis68: It's a very safe place. But huge. :)14:35
mihalis68yeah, I'm apprehensive about getting totally lost, not dying!14:35
mihalis68I did go once, for the summit there a couple of years ago14:35
mihalis68I'll make myself the unelected social secretary here unless there is a volunteer?14:35
mihalis68Someone who you know speaks japanese?14:35
emccormickI spent a week wandering around before the summit. Once you get used to the trains it's a piece of cake ;)14:36
shintarosocial event in Tokyo? yes planning but may need a sponsor14:36
smcginnisemccormick: ++ Love the train system.14:36
mihalis68+114:36
emccormickI had a JR pass. Totally worth it14:36
mihalis68when we (the bloomberg attendees) were about to get the wrong train, station staff RAN to tell us14:36
shintaroif you have google with you, youre fine14:36
emccormickyeah they are super helpful. And yes google ftw.14:37
smcginnisshintaro: Love that Google Maps will tell you exactly how many stops to go.14:37
mihalis68shintaro if someone else plans the social with some lead time, I might try to persuade Bloomberg to contribute to sponsoring that14:37
smcginnisAnd people go way out of their way to help if needed.14:37
shintarosubway and train system is so complicated that we use google to finde the right path14:37
mihalis68I mean I will try, but I might be able to get that to happen14:37
mihalis68any more discussion for Tokyo for today?14:38
shintarothanks mihalis68 I will let you informed about the evening event14:38
mihalis68Cool, thanks14:38
mihalis68#topic Operators Guide14:38
*** openstack changes topic to "Operators Guide (Meeting topic: Ops Meetup Team)"14:38
mihalis68briefly some real work happened on this, I am due to review and then re-upload pages to the openstack wiki and then launch it with the community14:39
mihalis68who would like to get email when there's something to actually work on there?14:39
mihalis68for anyone who doesn't know, it's transitioning from part of the openstack official docs to a wiki but still on the openstack site14:40
mihalis68it was just complex to get the markdown out of the normal openstack documentation files14:40
mihalis68Was hoping for "beta testers" for it before I mail the operators mailing list14:40
emccormickoo just looked at the map. Didn't realize this was down near where the summit was. I found a decent brewery down there.14:41
emccormicko/14:41
emccormickloop me in of course :)14:41
mihalis68ok. brewery in Sydney? Tokyo?14:41
emccormickTYO14:41
mihalis68oh nice.14:41
emccormicknow all I have to do is check my Untappd to remember what it was14:42
shintaroremember the name of the place?14:42
mihalis68I messed up in tokyo, I went to dinner with the Astara folks (remember that project) and had a bad local curry around the corner from my hotel14:42
emccormicklooking now shintaro.14:42
shintaroemail me if you find it. I can include it to the list :)14:43
smcginnisemccormick: We had an outing here if it happens to be the same you're thinking of: https://goo.gl/maps/oLMoezAzmur14:44
zioprotohello all, there is a meeting going on ?14:44
mihalis68yes we are nearly done I think. Nice to see you here14:44
mihalis68#topic SuperUser articles14:44
*** openstack changes topic to "SuperUser articles (Meeting topic: Ops Meetup Team)"14:44
mihalis68last week we saw a nice one featuring NTT (link in agenda)14:44
mihalis68the mexico city one is on hold indefinitely, I haven't heard from Gloria since the second earthquake14:44
shintarosmcginnis that place is a nice place!14:45
mihalis68but I did propose bloomberg submitting a proposal about the docs and the LTS discussion (which we got into in Mexico)14:45
emccormickT.Y. Harbor Brewery14:45
mihalis68I'm due to throw this together this week. The aim is to publicize the LTS meeting in Sydney14:45
smcginnisshintaro: I enjoyed it. :)14:45
emccormickhttps://www.tysons.jp/tyharbor/14:46
emccormickyep14:46
shintaroah same place )14:46
mihalis68that looks perfect for an Operators social14:46
mihalis68I'm hoping to be able to say in the article that NTT, RedHat, Canonical, Huawei will attend the LTS discussion14:47
emccormickI sat out by the water and drank alone. It was rather peaceful. Boring but peaceful. ;)14:47
mihalis68kind of makes it a fairly big deal14:47
smcginnismihalis68: Good way to motivate them all to show up. ;)14:47
mihalis68emc not all operators events can have Flamenco, free beer and Boris!14:48
mihalis68if there is anyone else here today that thinks their org could agree to attend a meeting on the topic of OpenStack official support for LTS releases, please speak up or let me know?14:48
mihalis68meeting is a forum session in sydney14:49
emccormick*chirp chirp*14:50
emccormickAnyone know Suse people?14:51
mihalis68William V?14:51
emccormickI just know the MEX folks, and they have no power in dev.14:51
emccormickI can ask if he knows someone14:51
mriedemallison price is who you'd ask from suse14:51
mihalis68#emccormick to ask SuSe (William Vera) about SuSe representing at the LTS Forum session14:52
mihalis68ah ok14:52
mihalis68anyone know her?14:52
emccormickOo I thought she was 100% foundation. Neat14:52
mihalis68I've been introduced, but that's it14:52
emccormickonly by name14:52
mriedemformerly HPE, now suse14:52
mriedemworking on fast forward upgrades for suse14:52
mihalis68mriedem would you be able to reach out?14:52
mriedemi don't really have skin in this game14:53
mihalis68or do you just happen to know of her work but not know her?14:53
mriedemso you don't want me owning that14:53
mihalis68ok then14:53
mriedemwe're not pals14:53
emccormickShe ran registration for our Philly meetup14:53
mihalis68I guess I can reach out then14:53
emccormickaccording to my emails.14:53
shintaroI can reach out.14:53
mihalis68#action mihalis68 to reach out to Allison Price re: SuSe at LTS forum session14:53
mihalis68ah ok you take it14:54
shintaroAllison from the foundation, right?14:54
emccormickmriedem Thanks for the info!14:54
mriedemshe's not foundation,  she was on the board at one time14:54
emccormickwonder if her email still forwards.14:55
emccormickoh it must14:55
mihalis68linked still says marketing manager for openstack14:55
emccormickshe sent an email re: sydney14:55
mihalis68*LinkedIn14:55
mriedemha, guess what everyone,14:55
mriedemi screwed up the name,14:55
mriedemallison randal is suse :)14:55
mriedemallison price is foundation :)14:55
mriedemmarketing14:55
mriedemsorry!14:55
mihalis68oh boy14:55
mriedemundo all the things14:55
shintarook wrong person14:56
emccormickWould have been fun to confuse the heck out of Allison Price though ;)14:56
mihalis68#shintaro to reach out to Alison Randal (SuSe)14:56
smcginnismriedem: Thought that didn't seem right. :)14:56
mihalis68I mean A.P. in Vancouver14:56
mihalis68but we do mean to contact a SuSe person in this case14:56
mihalis684 minutes left14:56
mihalis68#topic future meetings14:56
*** openstack changes topic to "future meetings (Meeting topic: Ops Meetup Team)"14:56
emccormickhaha she has her own Wikipedia page14:56
emccormickhttps://en.wikipedia.org/wiki/Allison_Randal14:56
mihalis68did anyone find out why there's a rumor of a meet up in the NE USA before end of year?14:57
emccormickNow I want one14:57
mihalis68I did suggest it, but then someone said that it seems to be already being planned, possibly Verizon?14:57
mrhillsmanbtw, I am waiting to hear back from foundation on logistics14:57
mihalis68operators local meetup14:57
mihalis68hi mrhillsman14:57
mihalis68could you share (maybe next week) what OpenDevConf has or did that we need to learn from?14:58
mrhillsmanI can ask Amrith about that14:58
mrhillsmanSure14:58
mrhillsmanBasically our previous discussion about themes relevant to region14:58
mihalis68#action mrhillsman to share insight into strengths of OpenDevConf14:58
mrhillsmanBut I can prepare more sensible discussion14:59
mihalis68yeah I mentioned themed track earlier. Shintaro is doing one for Tokyo and will contact foundation to get that publicized early14:59
mihalis681 minute left14:59
mihalis68no news on regional operators meet up in NE before end of year?14:59
mrhillsmanCool, I discussed with him as well, sounds great14:59
mihalis68so weird14:59
mrhillsmanidk about that14:59
smcginnismihalis68: Wish I could remember who said that to me.14:59
mrhillsmanI heard next year14:59
mihalis68at one of these meetings someone said Bloomberg was involved!14:59
mrhillsmanIt was Amrith iirc15:00
mihalis68ok out of time15:00
mihalis68is he a colleague?15:00
mrhillsmanVerizon guy I believe15:00
mihalis68if someone can chase info on that, would be appreiated15:00
mrhillsmanI'll ping him15:00
mihalis68any more?15:00
mihalis68thanks mrhillsman15:00
mihalis68and thanks to you al15:00
mrhillsmanWelcome15:00
mihalis68all15:00
mihalis68see you next week15:00
shintarothank you15:00
mrhillsmanThanks for your diligence Chris15:00
mihalis68#endmeeting15:01
*** 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:01
openstackMeeting ended Tue Oct  3 15:01:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-03-14.02.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-03-14.02.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-03-14.02.log.html15:01
*** shintaro has quit IRC15:03
mihalis68I didn't want to burden the official meeting with this, but the reason I dropped half my actions is we just retired a VM type and I've been chasing hundreds of owners. We will soon be 100% ceph backed VMs on openstack, and soon should be able to live migrate any VM at will15:03
mihalis68pretty psyched15:04
smcginnismihalis68: Nice!15:05
mihalis68yeah right15:05
mihalis68we're moving CPU type to KVM64 so that we don't get bit by platform differences15:05
mihalis68(previously we had some xeon v4 capacity joined and then when it had a systematic processor fault could only move to like machines, oops!)15:06
*** Oku_OS is now known as Oku_OS-away15:06
mriedemi've got a question for some ops while people are here listening15:08
mihalis68any more followups on todays stuff, anything at all, feel free to email me folks15:08
mihalis68go ahead mriedem15:08
mriedemwhat is the majority config people usually do for cloud-init behavior with refreshing guest information on reboot?15:09
mriedemthere is this thread in the ML about updating keypairs within a nova instance15:09
mriedemand part of that depends on how cloud-init is configured, because if refreshes on guest reboot, we can just update the keyname in the instance and it will get updated on reboot of the guest, otherwise you have to rebuild the instance15:09
*** chyka has joined #openstack-operators15:10
mihalis68we manage keys separately from cloud-init. We put a script on a VM at launch that periodically goes and gets the users for the VM15:10
mihalis68actually we put that script in the image15:10
mihalis68we tell people to use our curated images, so we get to put stuff in each VM15:11
*** yprokule has quit IRC15:11
*** sdague has joined #openstack-operators15:11
mriedemalright, so you're not really the person i should be asking then :)15:12
*** rcernin has quit IRC15:12
mriedemso is your script pulling something out of openstack for keypairs for the guest, or some other key store?15:13
mihalis68we've got our own internal non-openstack key management solution. I figured maybe my answer wouldn't help. Oh well :|15:16
mriedemif only there were other operators in the operators channel15:17
mihalis68I imagine they're all firefighting production emergencies.15:18
zioprotomihalis68: I read now the meetings log15:20
mihalis68hope all well with you15:20
zioprotomihalis68: I will also be in Sydney, and I am really interested in the LTS topic15:20
mihalis68Ok. It is already a proposed session, which smcginnis thinks is almost bound to be approved15:20
*** pcaruana has quit IRC15:20
zioprotoemccormick: you are expert in running Cinder with different Volume types ?15:20
mihalis68all we need to do is get the word out so that it's representative group at the session and then maybe this can start moving for real15:21
*** smcginnis has left #openstack-operators15:25
zioprotomihalis68: ok !15:31
jproulxmriedem: not sure if I'm any more help on key pairs.  On the Openstack side we just do the "if you change keys you need to rebuild" thing but mostly we use our config management to keep the right keys in the right places (on OpenStack, physical systems and public cloud) so the cloud-init managed keys are only really used by packer for image building and occasionally for the occasional manual test environments15:32
mriedemi'm also hearing from infra users that they disable/delete cloud-init after first boot because they don't want to messing things up, like hostname, on reboot of the guest15:33
mriedemso that would be another case where you need to rebuild if you change the keypair that the instance is going to use15:34
sdagueyeh15:35
*** penick has joined #openstack-operators15:35
jproulxfor "pet" type systems (anything that gets booted from a cinder volume) we also recommend removing cloud-init, for ephemeral images we do keep it around15:36
*** chlong has quit IRC15:36
jproulxthough we don't recommend 'pets' we do still build a few :)15:37
sdagueright, so with all those axes being true, I guess rebuild only is probably fine, as long as the keyname gets persisted into the server object after it15:37
mriedemsdague: yeah we already store the instance.key_name so we can change that during rebuild if we went that route15:40
mriedemso now it sounds like we're leaning toward https://review.openstack.org/#/c/375221/15:40
* penick perks up15:45
penick@mriedem re updating keypairs.. I don't update them from outside nova. I use SSH CA to sign the keys, so that I never need to worry about them15:49
emccormickzioproto Hardly expert, but I have messed with some few different things.15:51
emccormickjproulx Wouldn't that make it also impossible to change an instance flavor? No cloud-init, No disk resize.15:53
emccormickalthough I guess if you know how to remove it, you can also put it back15:53
emccormickand mriedem I've run into the same issue a couple of times and definitely +1 the ability to change key on rebuild.15:55
mriedememccormick: i think we're all in favor of being able to update the key on rebuild, the main question is if we tie that just into the rebuild API, or update the key as part of updating the server, and then the user has to either reboot or rebuild15:56
mriedemwhat i'm hearing is a lot of people disable/delete cloud-init after initial create, so reboot won't refresh the new key15:57
mriedemso yo'ud have to rebuild anyway15:57
mriedemwe have two nova specs proposed for each one15:57
jproulxemccormick: cloud-init removal is on boot-from-volume instances so root volume is independent of instance type in this particular and limited case16:00
jproulxin the general case we keep cloud-init16:01
mnasermriedem ill jump in and say i feel like if you implement it without a rebuild, it will likely be largely unused because of the heavy dependency for tooling in the vm16:02
mnaseran example of this is set_admin_password and most images in my experience dont run qemu-guest-agent16:02
*** gyee has joined #openstack-operators16:02
mnaserin general i feel like we operate under the assumption that once nova hands you the vm, it doesn't touch the state of the os (obviously there's things like resize which do but nothing that touches configs/etc)16:03
mriedemmnaser: so you're advocating for just baking it into the rebuild action API itself, to optionally specify a new key_name during the rebuild16:05
mriedemright?16:05
mriedemand don't leave it to chance that reboot would work16:05
mnasermriedem yes, that was something which was actually a big issue for customers a while back.  they lose their private key and they have no choice than booting a new vm (which loses the ip, mac address, etc)16:05
mnaserso we'd teach them how to take down all neutron port info, delete the instance, create port manually,  attach to new vm .. just for that16:06
penickSo if a user decides to rebuild a vm, the flow would be: grab keypair off instance, define that keypair in nova, then issue rebuild and specify that key name?16:07
mriedempenick: just create new keypair with new name, and provide that new keyname during the rebuild action16:07
mriedemlike how you can specify a different image or personality files during rebuild16:07
penickWill every rebuild thereafter use that same keyname, without needing it specified?16:08
mriedemyes16:08
mriedemkeyname on rebuild is optional16:08
mriedemif not specified, it's whatever the instance is already using16:08
penickI'm gonna check on the keypair data model real quick.. I have a concern.16:09
mnaserwell keypairs have always been tricky16:10
mnaserin that they dont have id's16:10
mnaserthey are unique by name so thats a bit tricky16:10
penickThat's one of my concerns. If a keypair is unique by name and user, does that mean the instance keypair is locked to a single user? I tend to have dozens of users in a tenant managing instances. So that'd be a problem.16:11
emccormickFunny there was just an ML message about deprecating personality files16:12
penickif keypairs aren't locked down by tenant, then in theory I could boot an instance and pass the same keypair name as another instance in a different tenant, then log in and now I have a copy of the keypair. Perfect for MITM attacks.16:12
penickNearly all users in my environment would use the instance hostname for the keypair name, so it'd be easy to guess what keyname to pass during rebuild16:13
emccormickkeypairs are per-=user16:13
penickk, so it's the first problem.. they'd need to be per tenant to work in a multi user environment16:14
penick(thanks)16:14
*** racedo has quit IRC16:23
*** simon-AS5591 has quit IRC16:28
mriedemcorrect keypairs are per user, and quota'ed that way16:37
*** tesseract has quit IRC16:37
mriedemmicroversion 2.10 allows an admin to create a keypair for another user16:38
mriedembut they aren't shared across users in the same tenant16:38
mriedemschema.UniqueConstraint("user_id", "name", "deleted",16:38
penickI think that would seriously constrain the usefulness of this feature16:39
mriedememccormick: are you yay or nay on deprecating personality files?16:40
mriedembecause i hope it's yay16:40
*** racedo has joined #openstack-operators16:43
*** vijaykc4 has joined #openstack-operators16:46
*** slaweq_ has quit IRC16:51
*** derekh has quit IRC16:55
jproulxnot having per project keys is a pain ... my group works around with config management as mentioned earlier but most other users of our cloud aren't that sophisticated (I mean they're only MIT CS gradstudents and research scientists...)16:56
sdaguekeypairs are all kinds of wonky in the model16:58
jproulxso if there's a proposal to make key per project optionally shared to a project/projects I'll all for that.  AWS get this wrong too what I'd really like is to select multiple keys for the users who should have access16:58
sdaguejproulx: that's not on the table at this point16:58
jproulxThats' fine it's hardly top of my list.16:59
sdaguehonestly, I think if we were changing something around keypairs in that way it would be make it so key pair could reference a barbican artifact instead16:59
jproulx+116:59
sdagueand nova stops doing keypair management16:59
sdaguebut... that's not being really proposed by anyone either16:59
sdaguethe only real question: should we even bother with specify new keypair on rebuild17:00
sdagueor is the whole keypair management through nova so gorpy at this point, that it's not worth bothering as it doesn't make it really useful anyway17:00
jproulxwell cloud-init which is a bit out of our hands expects a public key (possibly keys) in meta-data or configdrive since nova is still doing that it would need some knowlege of how to get it17:00
* jproulx must run off...17:01
sdagueyeh, nova would still transfer it into metadata17:01
sdaguebut when we brought up the whole keypair update question, the infra team had a different concern, which was key rotation, where they wanted the same name to able to be referenced, but update the key contents so that new servers built get a new key17:02
sdaguewhich totally also seems useful17:02
sdaguebut, in thinking that through more, I'd really hesitate in making all the key rotation bits first class in nova directly17:02
sdaguevs. giving it a handle to some more polished keystore17:03
*** nikhil_k has quit IRC17:04
*** vijaykc4 has quit IRC17:20
*** kukacz has quit IRC17:20
*** slaweq_ has joined #openstack-operators17:24
*** kukacz has joined #openstack-operators17:27
*** slaweq_ has quit IRC17:28
emccormickmridem I don't care really17:28
*** slaweq_ has joined #openstack-operators17:28
emccormickI've never had a need to use them personally17:28
*** slaweq_ has quit IRC17:30
penicksdague: I agree that keypairs should be in barbican. Additional functionality like signing keys for sshca belong in barbican anyway.17:33
sdaguepenick: ok, so... melwitt originally said that the update keypair on rebuild use case would be helpful for yahoo/oath. Is that not actually true?17:34
sdaguetrying to sort through if enough folks would use this to make it worth changing anything17:34
penickIt would help many of my users right now, but i'm moving everything to signed host certificates over the next year17:36
melwittwhen I worked there, I was asked if we could pass new --userdata to rebuild (for the purpose of injecting new keys) as a feature they wanted. so maybe that's changed17:36
penickSo she's correct, but i'm trying to obviate the problem with SSHCA17:36
sdaguepenick: ok, so by the time you'd get the code where it was implemented, it wouldn't be particularly useful to you17:38
*** khyr0n has joined #openstack-operators17:38
*** arnewiebalck_ has joined #openstack-operators17:40
penickyep17:46
*** slaweq_ has joined #openstack-operators18:01
*** racedo has quit IRC18:10
*** electrofelix has quit IRC18:26
*** arnewiebalck_ has quit IRC18:32
*** aojea has joined #openstack-operators18:34
*** slaweq_ has quit IRC18:35
*** slaweq_ has joined #openstack-operators18:35
*** aojea has quit IRC18:38
*** slaweq_ has quit IRC18:42
*** simon-AS559 has joined #openstack-operators18:59
*** simon-AS5591 has joined #openstack-operators19:00
*** simon-AS559 has quit IRC19:03
mriedemwell,19:06
mriedemkeep in mind,19:06
mriedemanything nova adds today, penick is never getting on his juno cluster19:06
mriedem:)19:06
mriedemsdague: i think enough people have said that at least the new keypair on rebuild api is useful19:06
mriedemi know our customers are asking for that19:06
mriedemthe thing that came up at the ptg and threw a wrench in the works was making it more generic so you could try and just reboot, and from all the discussions this morning with ops and users, it sounds like that's not very useful19:07
*** arnewiebalck_ has joined #openstack-operators19:12
*** slaweq_ has joined #openstack-operators19:12
penickmriedem for the record SIR, I will totes be on Ocata any day now. Anyyyy day now.19:16
penickJust you wait.19:16
penickIn all seriousness, even though this feature wouldn't apply to me, keys would need to be scoped to tenants, and not just users.19:18
sdagueyeh, the keys scoped to users thing is a goofy part of the data model from the before times that no one has looked at fixing19:18
*** slaweq_ has quit IRC19:22
*** slaweq_ has joined #openstack-operators19:22
penickand if it's just blindly changed to being tenant scoped, then other users within a tenant could compromise someones user keys.19:23
penickIt'd be better if instance keys were tenant scoped, and user keys weren't. Which is why it'd be better if this was all stored in barbican. Let barbican deal with deciding who has access to what.19:23
*** arnewiebalck_ has quit IRC19:26
mriedemis barbican required yet?19:30
*** catintheroof has quit IRC19:32
*** catintheroof has joined #openstack-operators19:32
sdagueI don't think yet, but it's getting close to that cusp19:36
*** dmibrid_ has joined #openstack-operators19:39
*** chlong_ has joined #openstack-operators19:43
*** mihalis68 has quit IRC19:43
*** chlong has joined #openstack-operators19:44
*** chlong has quit IRC19:46
*** liverpooler has quit IRC20:08
*** catintheroof has quit IRC20:10
*** catintheroof has joined #openstack-operators20:11
*** emccormickva has joined #openstack-operators20:12
*** emccormick has quit IRC20:16
*** dminer has quit IRC20:37
*** catintheroof has quit IRC20:42
*** catintheroof has joined #openstack-operators20:42
*** AndyU has quit IRC20:51
*** jamemcc_ has joined #openstack-operators20:55
*** VW has quit IRC20:57
*** VW has joined #openstack-operators20:58
*** chlong_ has quit IRC21:03
*** cnf has quit IRC21:09
*** cnf has joined #openstack-operators21:10
*** slaweq_ has quit IRC21:27
catintheroofhi guys, quick question, i know i can share a network with a specific project using RBAC since liberty, that works amazing, but what about if i want that an external network (router:external = True) is being seen or used ONLY by a single project, is that supported ? if so, how can i do it ?21:33
*** gyee has quit IRC21:34
*** simon-AS5591 has quit IRC21:49
*** slaweq_ has joined #openstack-operators21:58
*** VW has quit IRC22:09
*** khyr0n has quit IRC22:21
*** khyr0n has joined #openstack-operators22:21
*** khyr0n has quit IRC22:22
*** khyr0n has joined #openstack-operators22:22
*** khyr0n has quit IRC22:24
*** khyr0n_ has joined #openstack-operators22:24
*** khyr0n_ has quit IRC22:26
*** khyr0n has joined #openstack-operators22:26
*** khyr0n has quit IRC22:28
*** khyr0n has joined #openstack-operators22:28
*** khyr0n_ has joined #openstack-operators22:29
*** khyr0n has quit IRC22:29
*** khyr0n_ has quit IRC22:30
*** slaweq_ has quit IRC22:31
*** penick has quit IRC22:31
*** slaweq_ has joined #openstack-operators22:40
*** sdague has quit IRC22:56
*** chaology has quit IRC22:57
*** chyka_ has joined #openstack-operators22:57
*** chyka has quit IRC23:00
*** catintheroof has quit IRC23:01
*** chyka_ has quit IRC23:01
*** chaology has joined #openstack-operators23:09
*** slaweq_ has quit IRC23:13
*** slaweq_ has joined #openstack-operators23:24
*** chyka has joined #openstack-operators23:26
*** VW_ has joined #openstack-operators23:26
*** VW_ has quit IRC23:27
*** VW has joined #openstack-operators23:28
*** chaology has quit IRC23:28
*** chyka has quit IRC23:30
*** mriedem has quit IRC23:39
*** chaology has joined #openstack-operators23:45
*** slaweq_ has quit IRC23:56
*** markvoelker has quit IRC23:59

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