Tuesday, 2019-01-08

*** roman_g has quit IRC01:18
*** nzoueidi has quit IRC03:38
*** nzoueidi has joined #openstack-meeting-503:39
*** portdirect has joined #openstack-meeting-503:57
*** spsurya has joined #openstack-meeting-504:22
*** dims has quit IRC04:47
*** dims has joined #openstack-meeting-504:48
*** dims has quit IRC04:56
*** dims has joined #openstack-meeting-504:56
*** spsurya has quit IRC05:10
*** spsurya has joined #openstack-meeting-505:13
*** radeks has joined #openstack-meeting-505:48
*** radeks has quit IRC06:11
*** radeks has joined #openstack-meeting-506:20
*** slaweq has joined #openstack-meeting-507:50
*** slaweq has quit IRC07:53
*** slaweq has joined #openstack-meeting-507:55
*** ralonsoh has joined #openstack-meeting-508:23
*** evrardjp_ has joined #openstack-meeting-508:48
*** evrardjp__ has joined #openstack-meeting-508:49
*** evrardjp has quit IRC08:51
*** evrardjp_ has quit IRC08:52
*** evrardjp__ has quit IRC08:53
*** evrardjp has joined #openstack-meeting-509:03
*** derekh has joined #openstack-meeting-509:33
*** roman_g has joined #openstack-meeting-511:17
*** zigo has joined #openstack-meeting-513:29
*** trident has quit IRC13:41
*** trident has joined #openstack-meeting-513:42
*** sgrasley has joined #openstack-meeting-514:02
*** trident has quit IRC14:03
*** trident has joined #openstack-meeting-514:03
*** dimitris_ has joined #openstack-meeting-514:36
*** mjturek has joined #openstack-meeting-514:37
*** evgenyl has joined #openstack-meeting-514:54
portdirectlets give it a few for people to arrive, but its that time:15:00
portdirect#startmeeting openstack-helm15:00
openstackMeeting started Tue Jan  8 15:00:54 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
portdirect#topic rollcall15:01
srwilkerso/15:01
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:01
*** georgk has joined #openstack-meeting-515:01
*** nick_kar has joined #openstack-meeting-515:01
jayahno/15:01
*** howell has joined #openstack-meeting-515:02
alanmeadowso/15:02
mattmceueno/15:03
evrardjpo/15:03
howello/15:03
georgko/15:03
nick_karo/15:03
dimitris_o/15:03
evgenylo/15:03
portdirectok - lets begin15:04
portdirect1stly Happy New year everyone, I hope you all had a great break and have a fantastic year.15:05
portdirect#topic meeting-location15:05
*** openstack changes topic to "meeting-location (Meeting topic: openstack-helm)"15:05
portdirectmore of an announcement really, but the venue of this meeting will change to openstack-meeting-4 at some point: https://review.openstack.org/#/c/626182/2/meetings/openstack-helm-team-meeting.yaml15:05
srwilkerssounds good15:06
evrardjpshouldn't the startdate have changed in that patchset? :p15:06
evrardjpto express when the change happens?15:06
evrardjpjust saying ... : p15:06
srwilkers:p15:07
srwilkersmight as well change that, and change the chair as well since that's outdated too15:07
jayahn+1 on evrardjp15:07
evrardjpso when do we change, next week?15:07
portdirectevrardjp: i trust ttx to do the right thing ;)15:07
evrardjphe is french15:07
evrardjp:D15:07
srwilkersunless the start date is meant to reflect the project's start date for meetings overall15:07
mattmceuenlol15:07
srwilkersoh wow15:07
portdirectevrardjp: i believe once the ps merges, we will shift in sync15:07
portdirectso would expect to move next week, unless its nit picked to death..15:08
mattmceuensounds good to me15:08
evrardjpsrwilkers: the chair change should happen in a different patchset15:08
evrardjpbut yeah, we all agree then :)15:08
mattmceuenwhat all do we need to update - the wiki, the PS, anything else?15:08
evrardjpcool thanks for the notice!15:08
portdirectI'll get that done at some point, though i dont mind leaving mattmceuen on the hook ;P15:08
srwilkersevrardjp: that's fine.  i just think it needs to change in general, regardless of which changeset it's a part of15:09
srwilkersportdirect: dirty15:09
mattmceuenhappy to help, I'll do the wiki :p15:09
portdirectthe wiki certainly needs some love, though i *still* cannot log into it to make edits15:09
portdirectthat would be great mattmceuen15:09
portdirectcan you also remove the refeence to biweekly meetings in the wiki15:09
mattmceuenoh wow is that still there :)  willdo15:10
portdirectthx dude15:10
portdirectok to move on?15:10
srwilkersyup15:10
portdirect#topic "denver openstackpalloza"15:11
*** openstack changes topic to ""denver openstackpalloza" (Meeting topic: openstack-helm)"15:11
portdirectso - with the combined ptg and summit (almost like the good old days eh?) I'm hopeing we can have a much more lively/productive set of sessions in denver15:11
portdirectare people in here planning on attending all (or part) of the events there?15:12
georgkI am planning to be there15:12
srwilkersi'm anticipating being there for part of it15:12
jayahnworst time ever to have openstackpalloza. May 1 (holiday), May 6 (Holiday), between May 1~May3 my kid's short vacation15:13
jayahneither i cannot go or i go with family. :)15:13
portdirectbring them!15:14
portdirectI've put an etherpad up here: https://etherpad.openstack.org/p/openstack-helm-denver-201915:14
portdirectplease use it to add topics that you'd like to dicsuss at the event15:14
portdirectI'll also see if we can get telepresence set up for those that cannot attend15:15
evrardjpsrwilkers: woot15:15
srwilkers:)15:15
portdirectI've also added a section for `summit events`15:15
evrardjpI am curious , isn't it palooza, instead of palloza?15:16
portdirectI expect that I'll be submitting another workshop (or two) for the summit itself15:16
evrardjp<- english is not my native language15:16
portdirectevrardjp: being dyslexic i feel i can make my own rules.15:16
evrardjpportdirect: like for the workshop, prepare for failure!15:17
evrardjp:p15:17
evrardjpworkshops are a great idea15:17
evrardjpthough15:17
portdirectevrardjp: hopefully not, though spinning up 100 clouds is always fun.15:17
portdirectanyway - thats all I have on this15:18
portdirect#topic OVS-DPDK15:19
*** openstack changes topic to "OVS-DPDK (Meeting topic: openstack-helm)"15:19
georgkyeah15:19
portdirectgeorgk: do you want to continue the convo from the airship meeting?15:19
georgkso, noob trying to wrap his head around this and happy for reviews and advices15:20
georgkyes, please15:20
georgkBTW: please ignore that the list is on an Akraino wiki15:20
portdirectfor those that were not in the airship meeting15:20
portdirect:)15:20
portdirectgeorgk has done some great work outlineing the steps required for ovs-dpdk support in an openstack-helm cloud deployed with airship here: https://wiki.akraino.org/display/AK/Support+of+OVS-DPDK+in+Airship15:21
portdirectgeorgk: over to you15:21
hogepodge(hi, late arrival)15:21
georgkso, there was a comment that many of these things can be done by Airship today already, which is great15:21
srwilkershey hogepodge15:21
georgkso, if you can point me to how to get the configuration (e.g. for hugepages) done, that would be very appreciated15:22
georgkmoreover, I have pushed an initial patch with an ovs-dpdk helm chart15:22
georgk#link https://review.openstack.org/#/c/626894/15:22
portdirectgeorgk: re that ps - is there a reason that dpdk support cannot be added to the existing ovs chart?15:23
alanmeadowsbeat me to that one15:23
alanmeadowsjust scanning i only see image deltas15:23
alanmeadowsbut i must be missing something15:23
georgkmhh, probably not - we just need to parameterize the attributes related to hugepages15:23
*** markvoelker has joined #openstack-meeting-515:23
portdirectextra mounts in here: https://review.openstack.org/#/c/626894/1/ovs-dpdk/templates/daemonset-ovs-vswitchd.yaml15:24
georgkright15:24
portdirecti think if you wrapped those in {{ if .conf.dpdk.enabled }} or similar15:25
georgkyeah, ok, parameterizing this might make more sense, given the amount of common code15:25
georgkI agree15:25
portdirectthen you shoudl be able to reuse the exising chart15:25
portdirectnice15:25
evrardjp+1 on parametrization15:25
georgkok, ok.15:26
*** markvoelker has quit IRC15:26
georgkthen I was wondering on which tools to use to get  the hugepage configuration done on the host15:27
portdirecton the hugepage work - I'd recommend looking at libvirt for pointers15:27
*** markvoelker has joined #openstack-meeting-515:27
portdirectre getting them on the host - thats where i think airships drydock comes into play15:27
*** markvoelker has quit IRC15:27
georgkyes, that´s my understanding (again sanity check)15:28
georgkok, so I´ll update the chart as suggested and look into drydock15:29
portdirectnice - i think if you get the changes to ovs into the exising chart, then we can really start to help here15:29
georgkI am lacking a good dev environment at the moment, though15:29
portdirectit would also be great if you took the items you have in the akrano wiki and got them into launchpad15:29
georgkwill do15:29
portdirectthat we cant help with georgk :(15:29
mattmceuenI can :)15:30
mattmceuengeorgek let's take that one back to #airship15:30
mattmceuencatching up - can't help with dev env necessarily15:30
georgkmattmceuen: ok, great15:30
mattmceuenbut can help with with the drydock15:30
mattmceuen;-)15:30
georgksure ;-)15:31
georgkok, I think that´s it from my side for now15:31
georgkthanks15:31
portdirectnice - thanks georgk15:31
portdirectreally nice to see this start to come together, you've really championed it dude15:31
georgk:-)15:32
jayahnevrardjp: just quick check. are you suggesting this requires spec? https://review.openstack.org/#/c/603971/15:32
jayahnand frankly speaking, i don't know how to put it in release note. can somebody help me on that?15:33
portdirectpefect segway15:33
evrardjpnope, not a spec15:33
portdirect#topic reviews15:33
*** openstack changes topic to "reviews (Meeting topic: openstack-helm)"15:33
jayahnthen, cloud you be a bit more specific on documentation?15:34
jayahnwant to followup :)15:34
portdirectjayahn: I think the intent of that ps is pretty clear, and definatly solves a issue for many people15:34
evrardjpjayahn: IMO, now that we have release notes available in all the repos, we should give insights about what's changing in the repositories. Here you're bringing a new feature in, which IMO, deserves a few words in a release notes. A longer explanation can be given in a documentation page15:35
portdirecti think a note in the documetation on how to use it to say use an external mysql or keystone would be great15:35
jayahnportdirect: yeap, that we thought15:35
portdirectevrardjp: can you help jayahn though the process of writing a reno note?15:35
evrardjpthe purpose is for future you or any other person, to be able to see that feature and enable it on its deployments15:35
evrardjpportdirect: sure!15:36
jayahnokay. i can work on putting few words or a note in documentation.15:36
portdirectfrankly the commit message itself is almost whats required for the reno work15:36
portdirectjayahn: re https://review.openstack.org/#/c/625803/  (timezone work)15:37
evrardjpportdirect: I don't mean it should be different -- the commit message and the release notes are, for me, destined to two different audiences.15:37
portdirectagain i really like this - its been on my mental to do list for ages15:37
portdirectbut i need to double check the implementation15:37
portdirectkfox111 did some great work here ages ago15:37
evrardjpthe commit messages is for OSH developers, while the reno is meant for deployers which don't particularily need to git blame things15:37
portdirectand i think his method was a bit cleaner (though my memory is fuzzy)15:38
portdirectevrardjp: 'is almost' ;)15:38
jayahncan someone teach me how to add things in reno? :)15:38
*** georgk has quit IRC15:38
jayahnokay, got that from osh irc channel15:39
evrardjp(for the record in the OSH irc channel, we discussed how to create a release note using reno new <releasenotename>15:40
evrardjp)15:40
portdirectnice - thanks evrardjp15:40
portdirecton the docs work: https://review.openstack.org/#/c/625853/ I must hold my hands up here, work, and vaction got the better of me15:41
portdirecti also sent the cores email to the old ml addr :(15:41
evrardjpjayahn: https://docs.openstack.org/reno/latest/15:41
portdirectwill resend right after the meeting15:41
jayahnevrardjp: you are the best!15:41
evrardjpI think what's important to remember, is the focus of the release notes. IMO, the release notes should be focused on exposing features/bugs/gotchas/upgrade tips to deployers, the ones which won't git blame the code.15:42
evrardjpIt's a good quick intermediary before writing a fully featured documentation.15:43
portdirect++15:43
jayahn++15:43
portdirectevrardjp: while your here, could you pull the junk data out of the quay.io login for now in here: https://review.openstack.org/#/c/624713/15:43
portdirectand then i think we can merge15:43
evrardjpportdirect: still on my todolist, I wanted to do it yesterday/today, still didn't find the time yet.15:44
evrardjpportdirect: probably tomorrow.15:44
evrardjplatest15:44
*** MegHeisler has joined #openstack-meeting-515:44
*** nick_kar has left #openstack-meeting-515:44
evrardjpthanks for the reviews btw :)15:44
portdirectevrardjp: nah man, thanks for your work bootstrapping that repo, really helped lighten the load.15:45
portdirectok - lets open the floor15:47
portdirect#topic any other business?15:47
*** openstack changes topic to "any other business? (Meeting topic: openstack-helm)"15:47
evrardjpI hope you had nice holidays everyone15:48
evrardjpthat's it :)15:48
jayahnthanks!15:48
portdirectok - lets wrap up then15:49
portdirecttune in next time, same osh time, probably different osh channel15:50
portdirect#endmeeting15:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:50
openstackMeeting ended Tue Jan  8 15:50:28 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-08-15.00.html15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-08-15.00.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-08-15.00.log.html15:50
*** MegHeisler has quit IRC15:50
*** derekh has quit IRC18:00
*** ralonsoh has quit IRC18:07
*** georgk has joined #openstack-meeting-519:50
*** iyamahat_ has joined #openstack-meeting-520:01
*** iyamahat__ has quit IRC20:03
*** spsurya has quit IRC20:41
*** nzoueidi has quit IRC20:45
*** nzoueidi has joined #openstack-meeting-520:46
*** radeks has quit IRC21:02
*** slaweq has quit IRC21:28
*** hongbin has joined #openstack-meeting-522:01
*** mjturek has quit IRC22:03
*** georgk has quit IRC22:18
*** slaweq has joined #openstack-meeting-522:23
*** howell has quit IRC22:43

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