*** chyka has quit IRC | 00:00 | |
*** d0ugal has joined #openstack-operators | 00:04 | |
*** rcernin has quit IRC | 00:09 | |
*** rcernin_ has joined #openstack-operators | 00:09 | |
*** VW_ has joined #openstack-operators | 00:15 | |
*** VW has quit IRC | 00:18 | |
*** VW_ has quit IRC | 00:19 | |
*** aojea has joined #openstack-operators | 00:23 | |
*** aojea has quit IRC | 00:28 | |
*** marst has quit IRC | 00:35 | |
*** tuanla____ has joined #openstack-operators | 00:38 | |
*** chito_ has quit IRC | 00:38 | |
*** d0ugal has quit IRC | 00:40 | |
*** rcernin_ has quit IRC | 00:50 | |
*** d0ugal has joined #openstack-operators | 00:51 | |
*** tuanla____ has quit IRC | 00:53 | |
*** tuanla____ has joined #openstack-operators | 00:54 | |
*** catintheroof has joined #openstack-operators | 00:56 | |
*** chyka has joined #openstack-operators | 01:01 | |
*** gyee has quit IRC | 01:01 | |
*** chyka has quit IRC | 01:06 | |
*** catintheroof has quit IRC | 01:21 | |
*** Apoorva_ has joined #openstack-operators | 01:32 | |
*** linkmark has quit IRC | 01:33 | |
*** Apoorva has quit IRC | 01:36 | |
*** Apoorva_ has quit IRC | 01:37 | |
*** trungnv has joined #openstack-operators | 01:52 | |
*** penick has quit IRC | 02:07 | |
*** rcernin has joined #openstack-operators | 02:11 | |
*** tuanla____ has quit IRC | 02:20 | |
*** tuanla____ has joined #openstack-operators | 02:21 | |
*** aojea has joined #openstack-operators | 02:25 | |
*** Apoorva has joined #openstack-operators | 02:29 | |
*** aojea has quit IRC | 02:29 | |
*** trungnv has quit IRC | 02:38 | |
*** AlexeyAbashkin has joined #openstack-operators | 02:38 | |
*** AlexeyAbashkin has quit IRC | 02:43 | |
*** mriedem has quit IRC | 02:56 | |
*** markvoelker has joined #openstack-operators | 03:24 | |
*** VW has joined #openstack-operators | 03:29 | |
*** khyr0n has joined #openstack-operators | 03:45 | |
*** VW has quit IRC | 03:48 | |
*** VW has joined #openstack-operators | 03:52 | |
*** markvoelker has quit IRC | 03:58 | |
*** Apoorva has quit IRC | 04:04 | |
*** VW has quit IRC | 04:07 | |
*** fragatina has quit IRC | 04:20 | |
*** fragatina has joined #openstack-operators | 04:20 | |
*** aojea has joined #openstack-operators | 04:25 | |
*** dmibrid_ has quit IRC | 04:28 | |
*** aojea has quit IRC | 04:30 | |
*** khyr0n has quit IRC | 04:37 | |
*** tuanla____ has quit IRC | 04:54 | |
*** tuanla____ has joined #openstack-operators | 04:55 | |
*** markvoelker has joined #openstack-operators | 04:55 | |
*** khyr0n has joined #openstack-operators | 04:58 | |
*** markvoelker has quit IRC | 05:28 | |
*** penick has joined #openstack-operators | 05:32 | |
*** tuanla____ has quit IRC | 05:33 | |
*** penick_ has joined #openstack-operators | 05:36 | |
*** penick has quit IRC | 05:36 | |
*** chyka has joined #openstack-operators | 05:50 | |
*** chyka has quit IRC | 05:51 | |
*** tuanla____ has joined #openstack-operators | 05:58 | |
*** penick_ has quit IRC | 06:12 | |
*** chyka has joined #openstack-operators | 06:15 | |
*** aojea has joined #openstack-operators | 06:17 | |
*** chyka has quit IRC | 06:20 | |
*** markvoelker has joined #openstack-operators | 06:25 | |
*** aojea has quit IRC | 06:28 | |
*** gkadam has joined #openstack-operators | 06:38 | |
*** trungnv has joined #openstack-operators | 06:43 | |
*** aojea has joined #openstack-operators | 06:50 | |
*** aojea has quit IRC | 06:50 | |
*** aojea has joined #openstack-operators | 06:50 | |
*** aojea has quit IRC | 06:52 | |
*** yprokule has joined #openstack-operators | 06:53 | |
*** markvoelker has quit IRC | 06:59 | |
*** aojea has joined #openstack-operators | 07:02 | |
*** aojea has quit IRC | 07:06 | |
*** chyka has joined #openstack-operators | 07:08 | |
*** chyka has quit IRC | 07:13 | |
*** lvdombrkr has quit IRC | 07:22 | |
*** rcernin has quit IRC | 07:31 | |
*** ircuser-1 has joined #openstack-operators | 07:39 | |
*** lvdombrkr has joined #openstack-operators | 07:42 | |
*** AlexeyAbashkin has joined #openstack-operators | 07:52 | |
*** rcernin has joined #openstack-operators | 08:02 | |
*** d0ugal has quit IRC | 08:03 | |
*** v12aml has quit IRC | 08:03 | |
*** d0ugal has joined #openstack-operators | 08:07 | |
*** tuanla____ has quit IRC | 08:10 | |
*** tuanla____ has joined #openstack-operators | 08:11 | |
*** v12aml has joined #openstack-operators | 08:27 | |
*** khyr0n has quit IRC | 08:37 | |
*** racedo has joined #openstack-operators | 08:37 | |
*** aojea has joined #openstack-operators | 08:45 | |
*** trungnv has quit IRC | 08:52 | |
*** markvoelker has joined #openstack-operators | 08:56 | |
*** chyka has joined #openstack-operators | 08:58 | |
*** chyka has quit IRC | 09:02 | |
*** aojea has quit IRC | 09:05 | |
*** aojea_ has joined #openstack-operators | 09:08 | |
*** jsheeren has joined #openstack-operators | 09:13 | |
*** treiz has quit IRC | 09:17 | |
*** treiz has joined #openstack-operators | 09:18 | |
*** markvoelker has quit IRC | 09:29 | |
*** derekh has joined #openstack-operators | 09:36 | |
*** treiz has quit IRC | 09:52 | |
*** treiz has joined #openstack-operators | 09:53 | |
*** treiz has quit IRC | 09:57 | |
*** treiz has joined #openstack-operators | 10:00 | |
*** yprokule has quit IRC | 10:15 | |
*** gfa has quit IRC | 10:15 | |
*** yprokule has joined #openstack-operators | 10:18 | |
*** fragatin_ has joined #openstack-operators | 10:22 | |
*** fragatina has quit IRC | 10:22 | |
*** markvoelker has joined #openstack-operators | 10:26 | |
*** gfa has joined #openstack-operators | 10:42 | |
*** electrofelix has joined #openstack-operators | 10:46 | |
*** fragatina has joined #openstack-operators | 10:57 | |
*** fragatin_ has quit IRC | 10:57 | |
*** markvoelker has quit IRC | 11:00 | |
*** AlexeyAbashkin has quit IRC | 11:22 | |
*** AlexeyAbashkin has joined #openstack-operators | 11:38 | |
*** markvoelker has joined #openstack-operators | 11:57 | |
*** aojea_ has quit IRC | 12:24 | |
*** markvoelker has quit IRC | 12:29 | |
*** tuanla____ has quit IRC | 12:39 | |
*** catintheroof has joined #openstack-operators | 13:11 | |
*** catintheroof has quit IRC | 13:12 | |
*** catintheroof has joined #openstack-operators | 13:12 | |
*** d0ugal has quit IRC | 13:14 | |
*** rcernin has quit IRC | 13:20 | |
*** d0ugal has joined #openstack-operators | 13:22 | |
*** aojea has joined #openstack-operators | 13:25 | |
*** markvoelker has joined #openstack-operators | 13:27 | |
*** markvoelker has quit IRC | 13:28 | |
*** markvoelker has joined #openstack-operators | 13:29 | |
*** d0ugal has quit IRC | 13:37 | |
*** aojea has quit IRC | 13:38 | |
*** d0ugal has joined #openstack-operators | 13:39 | |
*** liverpooler has joined #openstack-operators | 13:40 | |
*** jsheeren has quit IRC | 13:44 | |
*** mihalis68 has joined #openstack-operators | 13:48 | |
*** makowals has joined #openstack-operators | 13:53 | |
*** yprokule has quit IRC | 13:56 | |
*** mriedem has joined #openstack-operators | 13:58 | |
mihalis68 | it is time for the openstack operators weekly meeting but i don't see anyone. I will give it some time in case there aren't enough attendees | 14:01 |
---|---|---|
*** shintaro has joined #openstack-operators | 14:01 | |
mihalis68 | hi! | 14:02 |
shintaro | hi | 14:03 |
mrhillsman | o/ | 14:03 |
mihalis68 | o/ | 14:03 |
mihalis68 | #startmeeting Ops Meetup Team | 14:03 |
openstack | Meeting started Tue Dec 19 14:03:45 2017 UTC and is due to finish in 60 minutes. The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:03 |
*** openstack changes topic to " (Meeting topic: Ops Meetup Team)" | 14:03 | |
openstack | The meeting name has been set to 'ops_meetup_team' | 14:03 |
mihalis68 | #link https://etherpad.openstack.org/p/ops-meetups-team | 14:03 |
mihalis68 | #topic actions | 14:04 |
*** openstack changes topic to "actions (Meeting topic: Ops Meetup Team)" | 14:04 | |
mihalis68 | I have requested that we (Bloomberg) sponsor breakfast/coffee for the Tokyo meetup | 14:04 |
mihalis68 | that completes my actions | 14:04 |
shintaro | not much update from me this week | 14:04 |
mihalis68 | anyone else have pending past actions (I'm going to go on the honor system for this) | 14:04 |
mihalis68 | breakfast/coffee was $2k, which although not that much is a bit higher than at other meetups if I recall correctly | 14:05 |
mihalis68 | is that just because prices are high in Tokyo? | 14:05 |
*** emccormick has joined #openstack-operators | 14:05 | |
mihalis68 | hey! | 14:05 |
emccormick | o/ | 14:05 |
mihalis68 | welcome back | 14:05 |
mihalis68 | we are just in the reviewing past actions | 14:05 |
emccormick | thanks! Sorry for being so absent | 14:05 |
mihalis68 | part of the meeting | 14:05 |
mihalis68 | it's the time of year, lots of people have a lot going on | 14:06 |
emccormick | my action item was to get here. Done! :D | 14:06 |
mihalis68 | no other action updates | 14:06 |
mihalis68 | #topic Tokyo meetup, march 2018 | 14:06 |
*** openstack changes topic to "Tokyo meetup, march 2018 (Meeting topic: Ops Meetup Team)" | 14:06 | |
shintaro | I don't remember the past price for breakfast, but thats what I got from the venue and my contractor | 14:06 |
mihalis68 | I've requested that we sponsor breakfast, but it's not my call | 14:07 |
mihalis68 | I don't think it's a bad price, but I might get asked about it, so thought I'd try and be prepared | 14:07 |
mihalis68 | I think it's a good opportunity since we get to be a co-sponsor for a lot less than NTT :) | 14:07 |
mihalis68 | NTT is also doing the evening event I think you said last week? | 14:08 |
shintaro | yes we will | 14:08 |
mihalis68 | the only things left to do then are (possibly) schwag and the technical agenda | 14:08 |
mihalis68 | I haven't looked at the agenda for a while, how is it going? | 14:09 |
shintaro | I've asked the foundation to provide T-shirts | 14:09 |
shintaro | I've added popular topics from the past events. | 14:09 |
shintaro | #link https://etherpad.openstack.org/p/TYO-ops-meetup-2018 | 14:10 |
shintaro | not much update | 14:10 |
mihalis68 | I think we can pick up the technical agenda in the new year. I'll email the list asking for input on that after this meeting and we can maybe review when there's more of us available | 14:12 |
mihalis68 | #action mihalis68 to remind the operators mailing list to look at the technical agenda for tokyo | 14:12 |
shintaro | ok | 14:12 |
mihalis68 | #topic meetup #2 august 2018 | 14:12 |
*** openstack changes topic to "meetup #2 august 2018 (Meeting topic: Ops Meetup Team)" | 14:12 | |
mihalis68 | I mentioned last week or the week before: Bloomberg may offer to host in NYC again August | 14:13 |
shintaro | +1 | 14:13 |
mihalis68 | #action mihalis68 to push for a firm decision on hosting in august 2018 | 14:15 |
mihalis68 | anyone else have a gut feel on whether they'd attend? | 14:15 |
emccormick | Well that'd be nice. Maybe I could actually make this one! | 14:15 |
emccormick | I would definitely be there | 14:15 |
mihalis68 | Cool | 14:15 |
mrhillsman | amrith mentioned verizon may be willing to host something | 14:16 |
emccormick | last time I just got offered a boat load of money to fly to mexico and do some work and couldn't say no ;) | 14:16 |
mrhillsman | i think if bloomberg offers, verizon can help or vice versa | 14:16 |
mrhillsman | prefer the former since NY last time was pretty good | 14:16 |
mihalis68 | it would be good to get a contact at verizon we could talk to | 14:16 |
shintaro | We have OpenStack days Tokyo on 2nd-3rd Aug so I hope it wont overlap. | 14:16 |
mrhillsman | amrith | 14:16 |
mihalis68 | that's a good point | 14:16 |
mrhillsman | amrith kumar | 14:16 |
mrhillsman | i do not have his email, but he is quite active | 14:17 |
emccormick | where is Amrith at? | 14:17 |
mrhillsman | let me try to find contact info | 14:17 |
mihalis68 | ironically my wife works for verizon, however she's in their advertising part, no contact with the likely openstack-interested parts | 14:18 |
mrhillsman | maybe she can get in touch or someone who can | 14:18 |
mihalis68 | I'll look for amrith first | 14:19 |
mrhillsman | he is a fellow there so should be easy to find him | 14:19 |
mihalis68 | ok cool | 14:19 |
mihalis68 | #topic new logo | 14:19 |
*** openstack changes topic to "new logo (Meeting topic: Ops Meetup Team)" | 14:19 | |
mihalis68 | there are two new logo proposals from the foundation in an email on the operators mailing list | 14:20 |
mihalis68 | I'm not sure everyone who is here today has seen and responded | 14:20 |
mihalis68 | I'd encourage everyone to do so | 14:20 |
mihalis68 | there's a shield-shaped one that I like and I think others did, and then a round one that's less popular so far | 14:20 |
shintaro | we haven't got response from Clair, but it was clear everyone liked the first one | 14:20 |
emccormick | Feedback so far seemed pretty universally in one camp. | 14:21 |
emccormick | *nod* | 14:21 |
mihalis68 | I have a feeling the shield already won, but I did want everyone to get a chance to speak up | 14:21 |
shintaro | I will confirm Clair for update | 14:21 |
mihalis68 | #action shintaro to check on new logo status with Clair from the foundation | 14:21 |
mihalis68 | #topic opsguide | 14:22 |
*** openstack changes topic to "opsguide (Meeting topic: Ops Meetup Team)" | 14:22 | |
mihalis68 | #link https://wiki.openstack.org/wiki/OpsGuide | 14:22 |
mihalis68 | this is the new conversion of the OpenStack Operators Guide which was ejected from the core docs maintained with code and given to the community | 14:22 |
mihalis68 | I still haven't had meaningful feedback on this | 14:23 |
emccormick | I think it looks great. | 14:24 |
emccormick | I still have on my list to go through and start reviewing content | 14:24 |
emccormick | I have gotten as far as opening it in its own browser window ... | 14:24 |
mihalis68 | the reason I keep asking is that right now it's as converted from the source | 14:24 |
mihalis68 | systematic changes could be made efficiently throughout the document via code changes | 14:25 |
mihalis68 | once it starts being edited by the wiki process, however, it is forever after a bunch of wiki pages | 14:25 |
mihalis68 | one idea I just had... | 14:25 |
mihalis68 | check me on this, may be premature, but... | 14:26 |
mihalis68 | we could logo-ify it with our "shield" ! | 14:26 |
shintaro | +1 | 14:27 |
emccormick | +1 | 14:27 |
mihalis68 | ok | 14:27 |
emccormick | if we gotta own it, let's own it | 14:27 |
shintaro | what was the process to give feedback on wiki? I will spread it around in Japanese community | 14:27 |
mihalis68 | I'll get my guy to do that and maybe we can "approve" this via email amongst us first and then unleash to operators community via the mailing list? | 14:27 |
mihalis68 | For now I am de facto the owner, so email to me | 14:28 |
mihalis68 | Bloomberg tasked a contractor of ours to do the conversipon | 14:28 |
shintaro | ok thanks | 14:28 |
mihalis68 | with the aim of giving it back to the community in a high quality form | 14:28 |
mihalis68 | I could just say "ok good to go, have at it" | 14:28 |
emccormick | Just be I don't see any reason you need to go for wider approval on a logo. Just let anyone with a problem complain. We can always take it off | 14:29 |
emccormick | nothing objectionable though. Let's ping the list to get people looking at it. | 14:29 |
mihalis68 | however feedback from, say mccormick, shintaro etc would make me feel more confident that it's a good start | 14:29 |
emccormick | I sent a link to a sample wiki before for tracking bugs and what people have reviewed... | 14:29 |
emccormick | could be a google doc also. | 14:29 |
mihalis68 | well this is kind of what I'm asking. By default a wiki is just open to anyone with edit privileges to do whatever | 14:30 |
mihalis68 | but if we launch with defined owners, we get to define a better process | 14:30 |
mihalis68 | I am happy to continue to be AN owner but there needs to be several or it's not at all a community thing | 14:31 |
emccormick | Yeah we need lots of people to dip in | 14:31 |
shintaro | right | 14:31 |
mihalis68 | let's discuss amongst ourselves for now via email until we have consensus to broaden the scope. The hesitancy is just around having a good launch with enough process that it takes on some life of its own and is not just an abandonware doc that moved from docs to wiki | 14:32 |
emccormick | here | 14:32 |
emccormick | https://wiki.openstack.org/wiki/Documentation/QueensDocTesting | 14:32 |
emccormick | that's just a sample tracking doc | 14:33 |
mihalis68 | is your proposal we make a document similar to that for launch and then maintenance of OpsGuide? | 14:33 |
mihalis68 | by the way med_ also planned to take a look and provide feedback | 14:34 |
mihalis68 | haven't heard yet | 14:34 |
mihalis68 | #topic any other business | 14:35 |
*** openstack changes topic to "any other business (Meeting topic: Ops Meetup Team)" | 14:35 | |
mihalis68 | we are few in number today, so may as well zip through the agenda and give everyone some time back | 14:35 |
mihalis68 | any final comments? | 14:35 |
mihalis68 | I propose we officially NOT try to meet next week | 14:35 |
shintaro | +1 | 14:36 |
mihalis68 | any other response? That would make next meeting Jan 2nd 14:00 UTC | 14:36 |
shintaro | and the week after, I will not be available | 14:36 |
mihalis68 | unless that is seen as a bad time too? | 14:36 |
emccormick | +1 | 14:37 |
shintaro | I will be on vacation until Jan 8 so I will be back on 9th | 14:37 |
emccormick | I can be here on the 2nd | 14:37 |
emccormick | kida back to school *snoopy dance* | 14:37 |
mihalis68 | but will it be worthwhile to try on 2nd? | 14:38 |
mihalis68 | I guess we can meet and wrap-up quickly if not much business? | 14:38 |
mihalis68 | I don't know if I'll be at work or out but a quick meeting is likely fine either way | 14:38 |
mihalis68 | anyone else? | 14:38 |
mihalis68 | ok, we seem to have almost no opinion but it's slightly in favor of Jan 2nd | 14:40 |
mihalis68 | #agreed next meeting jan 2nd normal time | 14:40 |
mihalis68 | last call for any other business | 14:40 |
mihalis68 | #endmeeting | 14:41 |
*** 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/" | 14:41 | |
openstack | Meeting ended Tue Dec 19 14:41:19 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:41 |
openstack | Minutes: http://eavesdrop01.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-12-19-14.03.html | 14:41 |
openstack | Minutes (text): http://eavesdrop01.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-12-19-14.03.txt | 14:41 |
openstack | Log: http://eavesdrop01.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-12-19-14.03.log.html | 14:41 |
mihalis68 | thanks everyone | 14:41 |
shintaro | thank you | 14:41 |
*** shintaro has quit IRC | 14:41 | |
emccormick | o/ | 14:41 |
emccormick | happy holidays all of you | 14:42 |
emccormick | see you next year! | 14:42 |
*** VW has joined #openstack-operators | 14:43 | |
mihalis68 | hey VW we already finished | 14:45 |
*** smcginnis has joined #openstack-operators | 14:45 | |
mihalis68 | there was very little to this meeting | 14:45 |
VW | ok - mihalis68 - sorry | 14:45 |
mihalis68 | hey sean, just telling vw we already finished | 14:45 |
mihalis68 | you did not miss much, don't worry | 14:45 |
smcginnis | Bah, missed it again! :/ | 14:45 |
mihalis68 | next meeting attempt Jan 2nd | 14:45 |
VW | had to drop all three kids off this morning | 14:45 |
VW | took extra time | 14:45 |
smcginnis | mihalis68: Thanks, will try to get my phone to stop giving me calendar updates an hour off. :) | 14:45 |
mihalis68 | I did an email reminder this time, but very late | 14:46 |
mihalis68 | can do better | 14:46 |
mihalis68 | we didn't even discuss the openstack release cadence this time, | 14:46 |
mihalis68 | still trying to comprehend all that discussion | 14:46 |
smcginnis | mihalis68: I think enough downsides have been pointed out that it isn't going to happen. At least any time soon. | 14:47 |
smcginnis | But might be good to have an opinion on some of the issues it raises and how that might impact operators. | 14:47 |
mihalis68 | somehow every suggestion is eventually converted into a plan that would require more effort, and so is obviously unworkable | 14:48 |
emccormick | Huh. I thought it was somewhat well received. Perhaps I missed a new bit of flames on -dev | 14:48 |
mihalis68 | do fewer releases! More work :( | 14:48 |
mihalis68 | do more releases! More work :( | 14:48 |
smcginnis | emccormick: I think the initial responses were well recieved, but then more issues were raised with it. | 14:49 |
emccormick | I'll finish and respond on list. | 14:49 |
smcginnis | Thierry posted a nice recap of the dicussion on the openstack-dev list. | 14:49 |
smcginnis | If it would help, I can forward that to the openstack-operators list. | 14:49 |
smcginnis | Or just give a link here. | 14:50 |
emccormick | I'll get caught up. | 14:50 |
emccormick | I was generally in favor of it, but if we can get fast-forward upgrades going then I care much less | 14:50 |
emccormick | and LTS | 14:50 |
mihalis68 | I think it would be good to xpost to -operators | 14:50 |
mihalis68 | although I now do follow -dev | 14:50 |
smcginnis | OK, will do. Just for convenience, here's a link to the original post: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125688.html | 14:51 |
mihalis68 | somehow I missed every previous subscription confirmation email | 14:51 |
smcginnis | mihalis68: Spam filter? | 14:51 |
mihalis68 | *mutter* spam filters *mutter* | 14:51 |
mihalis68 | yeah | 14:51 |
smcginnis | :) | 14:51 |
mihalis68 | not too hard to avoid if I try | 14:51 |
mihalis68 | but failed numerous times | 14:51 |
mihalis68 | finally did it | 14:51 |
mihalis68 | hey I can put Tokyo breakfast/coffee on my corporate Amex, just got approval | 14:51 |
smcginnis | Mmmm, coffee. | 14:53 |
mihalis68 | Bloomberg believes strongly in coffee | 14:53 |
*** sxc731 has joined #openstack-operators | 14:53 | |
smcginnis | A sign of a good company. :D | 14:54 |
mihalis68 | the kitchen coffee here is just good enough to prevent external coffee shop outings, it's uncanny | 14:54 |
mihalis68 | like it's not *great* but every time I think I'll go get something better I decide ok free coffee and save 10-15 minutes wins | 14:54 |
smcginnis | Haha, sneaky. | 14:54 |
smcginnis | Now that I work from home, one of the few things I miss about going in to an office was access to unlimited free coffee. Even though it wasn't great, it was right there. ;) | 14:55 |
mihalis68 | I guess release cadence is well and truly in discussion across the community so no need for the meetups team specifically to worry about any more | 14:55 |
VW | some days you get what you pay for smcginnis ;) | 14:55 |
mihalis68 | I have never worked from home by default | 14:55 |
mihalis68 | I'm like a fossil | 14:55 |
smcginnis | VW: True! | 14:55 |
VW | it's a bit like Russian roulette around here sometimes when it comes to coffee pots | 14:56 |
smcginnis | mihalis68: I never did extensively until this job. Gotta say, I kind of like it. | 14:56 |
mihalis68 | I'd try it | 14:56 |
*** sxc731 has quit IRC | 14:56 | |
mihalis68 | but then I run a team of 9-12 now (depending on how you count it) | 14:56 |
mihalis68 | I feel like I should be here | 14:56 |
VW | mihalis68: I have made thursdays work from home day for about two years | 14:56 |
smcginnis | VW: Yeah, you would think making coffee was straight forward enough, but it's amazing how folks can mess it up. | 14:56 |
VW | it's a nice way to get away from the desk and the walk-ups and get caught up | 14:57 |
amrith | oink | 14:57 |
amrith | just saw my name here | 14:57 |
smcginnis | VW: ++ I feel like I get a lot more done without the random distractions. | 14:57 |
mihalis68 | oh yeah, the interruptions here ... | 14:57 |
mihalis68 | hey amrith | 14:57 |
*** emccormick has quit IRC | 14:57 | |
amrith | hello hello | 14:57 |
smcginnis | amrith: o/ | 14:57 |
mihalis68 | is verizon potentially interested in co-hosting openstack operators meet up in august 2018 in NYC? | 14:57 |
amrith | oh, damn. smcginnis is here | 14:57 |
amrith | see you all later | 14:57 |
amrith | ;) | 14:57 |
mihalis68 | harsh | 14:57 |
smcginnis | :) | 14:58 |
mihalis68 | Bloomberg is considering hosting again | 14:58 |
mrhillsman | hey amrith i mentioned discussing with you possibly verizon hosting/co-hosting meetup in fall next year | 14:58 |
amrith | mihalis68 potentially yes | 14:58 |
mihalis68 | would be 2 years since last time we hosted | 14:58 |
mihalis68 | ok cool | 14:58 |
amrith | yes, discussed it with amitry and a couple of others | 14:58 |
amrith | but the timing didn't work | 14:58 |
mihalis68 | yeah it's all mrhillsman's fault | 14:58 |
mrhillsman | :) | 14:58 |
mrhillsman | welp, now that you two know each other hehe | 14:58 |
mrhillsman | my job is done | 14:59 |
mrhillsman | know of each other rather | 14:59 |
mihalis68 | can I email you direct amrith? I'm cmorgan2@bloomberg.net | 14:59 |
amrith | mrhillsman I've known smcginnis for some time now | 14:59 |
mihalis68 | where are you located? | 14:59 |
amrith | mihalis68 email on its way | 14:59 |
amrith | near boston | 14:59 |
mihalis68 | ok so NYC is reasonable but not actually home | 14:59 |
amrith | we have a big team in Warren, NJ and VZ's hq is very nearby | 15:00 |
mihalis68 | seems we have local, boston and then DC/Reston area folks interested as a minimum, and then at least one +1 from japan | 15:00 |
amrith | so I'm a remote employee | 15:00 |
mihalis68 | yeah my wife works for VZ in west street and goes to basking ridge occasionally | 15:00 |
mihalis68 | in advertising | 15:00 |
amrith | ah, cool. so yes, hosting in that area is something we're interested in. | 15:00 |
mihalis68 | very good | 15:01 |
amrith | email on the way | 15:01 |
amrith | and sorry for yanking your chain smcginnis | 15:01 |
mihalis68 | don't scare off the developers from this meeting slot | 15:01 |
smcginnis | amrith: Haha, it's only fair. | 15:01 |
mihalis68 | sean brings news from the scene of the crime | 15:01 |
mihalis68 | I mean from the developers | 15:01 |
mrhillsman | amrith are you participating in the edge meetings/discussions? | 15:02 |
mrhillsman | gotta run peeps | 15:02 |
mrhillsman | thx mihalis68 for chairing | 15:02 |
mrhillsman | ttyl | 15:02 |
* amrith wonders whether smcginnis proximity to crime scenes may be more than correlation :) | 15:02 | |
mihalis68 | most welcome | 15:02 |
amrith | mrhillsman I was hoping to | 15:02 |
amrith | but got tied up in something else | 15:02 |
amrith | should dial in now, | 15:02 |
smcginnis | Hah! | 15:03 |
amrith | mrhillsman thanks for the reminder, now dialed in | 15:05 |
mrhillsman | ;) | 15:05 |
*** aojea has joined #openstack-operators | 15:07 | |
amrith | amitry ... would you please pm me an email address which I can use for the operators meetup scheduling | 15:08 |
*** aojea has quit IRC | 15:09 | |
*** aojea has joined #openstack-operators | 15:09 | |
*** marst has joined #openstack-operators | 15:10 | |
*** smcginnis has left #openstack-operators | 15:12 | |
*** chyka has joined #openstack-operators | 15:20 | |
*** aojea has quit IRC | 15:25 | |
*** chyka has quit IRC | 15:26 | |
*** chyka has joined #openstack-operators | 15:26 | |
*** chyka has quit IRC | 15:31 | |
*** liverpooler has quit IRC | 15:38 | |
*** aojea has joined #openstack-operators | 15:41 | |
*** liverpooler has joined #openstack-operators | 15:48 | |
*** gyee has joined #openstack-operators | 16:42 | |
*** penick has joined #openstack-operators | 16:42 | |
*** aojea has quit IRC | 16:42 | |
*** AlexeyAbashkin has quit IRC | 17:01 | |
mnaser | (posted in nova but reposting here): Spec-ing out new compute and in the interest of deployers and doing things in open we’re planning to publish the document ... I wanted to gather some feedback at what sort of cpu overcommit you’ve ran/seen people run? | 17:14 |
*** gkadam has quit IRC | 17:22 | |
*** Apoorva has joined #openstack-operators | 17:43 | |
*** Apoorva has quit IRC | 17:43 | |
*** Apoorva has joined #openstack-operators | 17:44 | |
*** derekh has quit IRC | 17:47 | |
*** catintheroof has quit IRC | 17:50 | |
*** catintheroof has joined #openstack-operators | 17:51 | |
penick | mnaser: at Oath we've done from 16:1 in user sandbox environments to 2:1/3:1 in production | 17:53 |
mnaser | penick: sweet, thanks for that info.. what about ratios of memory / cpu to be able to right size compute nodes? | 17:54 |
penick | mnaser: Unfortunately the answer for that is "It depends". What size VMs are you going to run? If you're going to offer your customers a selection of flavors, you can pretty much count on them only wanting the largest flavor. Humans are dependable like that ;) | 17:57 |
mnaser | penick: the idea is to have some sort of document to say "hey, this is what we've experienced, this is what others have experienced, let that help you decide" | 17:58 |
*** chito_ has joined #openstack-operators | 17:58 | |
mnaser | the idea is to have a general amount of information so that potential deployers can make an informed decision | 17:58 |
mnaser | because i think a lot of us tend to do this sort of 'architecting' behind our doors and i think we can all benefit from this information | 17:59 |
penick | Sure. Right sizing depends on workload. So I suggest you provide a formula and some strawman examples. | 17:59 |
penick | let's say you have 2 flavors, Flavor foo has 2 cpu cores and 4gb of ram; flavor bar has 8 cores and 16gb of ram. | 18:00 |
mnaser | penick: yeah i agree that usually we have to do a ratio of gb/cpu | 18:01 |
mnaser | so usually that ratio obviously depends on your workloads | 18:01 |
penick | (abandoning the strawman) | 18:02 |
penick | Our hypervisors range from 12 cores and 64gb of ram to 24 cores and 512gb of ram. Depending on network security zone type (corp vs prod, for example) and region. | 18:03 |
penick | Another factor to consider is the level of resiliency you'd like to offer your users, in some cases it makes sense to use more and smaller hypervisors rather than fewer deeper hypervisors. Build wide vs deep. | 18:05 |
penick | Our largest datacenters are in the US, so we build bigger hypervisors there. However in, say, ireland we have lower instance counts overall so we use smaller hypervisors (more likely to see 96-128gb) to ensure instances have rooms to spread around. | 18:06 |
penick | In the US we have much higher instance counts, so building deeper hypervisors makes sense, since we'll still have many hypervisors to meet demands | 18:07 |
*** catintheroof has quit IRC | 18:07 | |
*** catintheroof has joined #openstack-operators | 18:08 | |
penick | So, yeah. We do our hypervisor selection based on intended usage(network security zone type), geographical region, Overcommit SLA, power constraints, availability requirements, and cost. | 18:09 |
*** harlowja has joined #openstack-operators | 18:15 | |
mnaser | penick: some really good information to write up | 18:18 |
*** chyka has joined #openstack-operators | 18:18 | |
*** racedo has quit IRC | 18:20 | |
*** AlexeyAbashkin has joined #openstack-operators | 18:22 | |
penick | mnaser hope it helps | 18:24 |
*** AlexeyAbashkin has quit IRC | 18:27 | |
*** racedo has joined #openstack-operators | 18:28 | |
*** racedo has quit IRC | 18:37 | |
cloudnull | mnaser: re: osic -- we did a very similar thing as penick. The over commit was setup as 2:1 and we didn't really mess with the memory over commit ratios. | 18:38 |
cloudnull | The networking was the same throughout the cloud so we did partition on networking capability. All hypervisors were using bonded intel x710 nics, had 48 cores (with hyperthreading enabled) and 256G of ram. | 18:38 |
cloudnull | We had however have three different storage profiles so we created host aggregates and flavor meta-data so that we could offer a "good", "better", "best" option in terms of storage performance. | 18:39 |
cloudnull | The "good" option used rotational media and had the most storage, The "better" option was on s3500 ssd's and had a fair amount of storage. The "best" option was on s3700 ssd's and had the least storage. | 18:39 |
cloudnull | each flavor profile had varying amounts of ram | 18:39 |
mnaser | cloudnull: so there wasn't a relationship of the amount of memory / vcpus to try and maximize resources? | 18:40 |
cloudnull | the most use flavor was the medium of each size which had 8G | 18:40 |
cloudnull | nope, we prioratized instance performance over density. | 18:41 |
mnaser | cloudnull: so you could have scenarios where you had a hypervisor that had free memory but all vcpus used up, alright | 18:41 |
cloudnull | yup | 18:41 |
mnaser | i'm gathering all this information to build up a nice interesting article for sizing physical infrastructure | 18:41 |
cloudnull | very cool! | 18:42 |
mnaser | i feel like this is a common thing we all work to figure out | 18:42 |
cloudnull | sorry, i missed this pings earlier, technically im not here right now :) | 18:42 |
mnaser | (also side note i started poking around the ansible nspawn+ssh connection stuff you worked on!) | 18:42 |
mnaser | no worries, thanks for the info! | 18:42 |
cloudnull | cool! | 18:42 |
cloudnull | I have that all running in the lab now | 18:43 |
mnaser | we've had nspawn in prod for a while now, pretty much what OSA does but nspawn containers per service that are managed via puppet | 18:43 |
cloudnull | nice! | 18:43 |
cloudnull | nspawn has been great in test. | 18:44 |
mnaser | it's very reliable and good at what it does | 18:44 |
cloudnull | I really like it with macvlan | 18:44 |
mnaser | really, i havent experimented that far | 18:44 |
cloudnull | it seems bulletproof that way | 18:44 |
mnaser | host networking to avoid weird shenanigans | 18:44 |
mnaser | (is what we've done so far) | 18:44 |
mnaser | and make things a lot more sane in terms of addressing etc | 18:45 |
*** chyka has quit IRC | 18:45 | |
cloudnull | agreed | 18:45 |
mnaser | (also, this is all control plane, i dont really want to run openvswitch or neutron-*-agent or cinder-volume in containers yet) | 18:45 |
cloudnull | macvlan is similar to what osa does already however it gets rid of the bridge and veth. | 18:45 |
cloudnull | yea we do the same in osa | 18:45 |
mnaser | why didnt osa just use host networking? | 18:45 |
cloudnull | any service that interacts with a physical device really didn't make sense in a container for us | 18:46 |
*** AlexeyAbashkin has joined #openstack-operators | 18:46 | |
mnaser | ++ | 18:46 |
cloudnull | we didn't do host networking because we wanted to isolate network traffic a particular container could have access to | 18:46 |
mnaser | valid, i guess you work with the assumption of not knowing what type of network you're sitting in | 18:47 |
cloudnull | hind sight being 20/20 it probably would have been a good idea and would have saved us quite a bit of growing pains. | 18:47 |
cloudnull | however now, it i think we've got a handle on it all. | 18:47 |
mnaser | yeah its always a pain at the start | 18:47 |
cloudnull | so it's kinda "meh" to go back . | 18:48 |
mnaser | (if only OSA did binary packaging .. but i guess "contributions welcome" :p) | 18:48 |
cloudnull | yea. its been kicked around a bunch. | 18:48 |
*** chyka_ has joined #openstack-operators | 18:49 | |
cloudnull | but the from source thing has been working well for us, for now. | 18:49 |
mnaser | there's a lot of work to be done but i think the harder part is seeing how to architecturally make a shift to select one or another | 18:49 |
cloudnull | we use distro packages for all the OS bits. | 18:49 |
cloudnull | just the openstack parts are source base.d | 18:49 |
*** chyka_ has quit IRC | 18:49 | |
cloudnull | yea, it would be nice to give deployers that choice | 18:50 |
mnaser | its easy to say "use rpms" for 1 role but harder to architect a global change so that methodology can be used across | 18:50 |
*** chyka_ has joined #openstack-operators | 18:50 | |
mnaser | well, its that and also.. the fact that as much as the roles are nice, they are pretty OSA biased (venv/etc) | 18:50 |
cloudnull | yea. | 18:50 |
mnaser | but if there hasn't been much role-only consumers then i guess its probably best to get the flexibility of doing your own thing | 18:51 |
cloudnull | this is very true. I mean we could make some of that conditional, but we'd still have a pretty biased OSA pov even if we did. | 18:51 |
mnaser | i think one of the problems right now of ansible is it is very hard to make service specific unbiased roles | 18:52 |
cloudnull | it is a pain. | 18:52 |
mnaser | with puppet you add the resources you need, with ansible you have to use variables to control the flow and skip/run things that are needed/not needed | 18:52 |
*** chyka_ has quit IRC | 18:54 | |
cloudnull | yea some of the mechanics could be a lot better in ansible and a lot has improved since 2.0 but like everything they all have their pros and cons. | 18:54 |
cloudnull | all of todays problems will be solved tomorrow :) | 18:54 |
cloudnull | ok, mnaser gotta run, | 18:55 |
* cloudnull going back to not being here. | 18:55 | |
mnaser | its been fun chatting, enjoy your holidays cloudnull | 18:55 |
cloudnull | let me know if i can help or review things as you create your doc | 18:55 |
mnaser | will do! | 18:56 |
cloudnull | I think that'd be super helpful for a lot of folks | 18:56 |
mnaser | ++ | 18:56 |
cloudnull | take care! | 18:56 |
mnaser | later! | 18:56 |
*** catintheroof has quit IRC | 18:56 | |
*** AlexeyAbashkin has quit IRC | 18:58 | |
*** gkadam has joined #openstack-operators | 19:03 | |
*** chyka has joined #openstack-operators | 19:12 | |
*** chito_ has quit IRC | 19:13 | |
*** alanmeadows has quit IRC | 19:15 | |
*** alanmeadows has joined #openstack-operators | 19:15 | |
*** chyka has quit IRC | 19:17 | |
*** catintheroof has joined #openstack-operators | 19:29 | |
*** openstack has joined #openstack-operators | 19:42 | |
*** ChanServ sets mode: +o openstack | 19:42 | |
*** tdasilva has quit IRC | 19:47 | |
*** tdasilva has joined #openstack-operators | 19:47 | |
*** electrofelix has quit IRC | 19:48 | |
*** dmibrid_ has joined #openstack-operators | 19:50 | |
*** fragatina has quit IRC | 19:56 | |
*** drewn3ss has quit IRC | 20:01 | |
*** VW_ has joined #openstack-operators | 20:11 | |
*** VW has quit IRC | 20:14 | |
*** drewn3ss has joined #openstack-operators | 20:15 | |
*** gkadam has quit IRC | 20:18 | |
*** VW_ has quit IRC | 20:35 | |
*** AlexeyAbashkin has joined #openstack-operators | 20:37 | |
*** AlexeyAbashkin has quit IRC | 20:41 | |
*** Apoorva has quit IRC | 20:51 | |
*** penick has quit IRC | 20:53 | |
*** emccormick has joined #openstack-operators | 20:59 | |
*** chyka has joined #openstack-operators | 21:02 | |
*** catintheroof has quit IRC | 21:02 | |
*** catintheroof has joined #openstack-operators | 21:03 | |
*** chyka has quit IRC | 21:06 | |
*** catintheroof has quit IRC | 21:07 | |
*** Apoorva has joined #openstack-operators | 21:20 | |
*** penick has joined #openstack-operators | 21:20 | |
*** penick has quit IRC | 22:19 | |
*** penick has joined #openstack-operators | 22:25 | |
*** rcernin has joined #openstack-operators | 22:28 | |
*** penick has quit IRC | 22:40 | |
*** marst has quit IRC | 22:41 | |
*** penick has joined #openstack-operators | 22:43 | |
*** penick has quit IRC | 23:39 | |
*** catinthe_ has joined #openstack-operators | 23:43 | |
*** catintheroof has joined #openstack-operators | 23:52 | |
*** catintheroof has quit IRC | 23:52 | |
*** catintheroof has joined #openstack-operators | 23:53 | |
*** catinthe_ has quit IRC | 23:55 | |
*** catintheroof has quit IRC | 23:58 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!