Tuesday, 2019-05-21

*** markvoelker has joined #openstack-meeting-400:41
*** markvoelker has quit IRC00:45
*** roman_g has quit IRC01:38
*** lei-zh has joined #openstack-meeting-402:00
*** yamahata has quit IRC02:32
*** iyamahat has quit IRC02:32
*** lei-zh has quit IRC02:32
*** lei-zh has joined #openstack-meeting-402:33
*** dave-mccowan has quit IRC02:55
*** hongbin has joined #openstack-meeting-403:00
*** psachin has joined #openstack-meeting-403:29
*** gcheresh has joined #openstack-meeting-403:34
*** gcheresh has quit IRC03:41
*** zerick has quit IRC04:03
*** zerick has joined #openstack-meeting-404:04
*** lei-zh has quit IRC04:06
*** gcheresh has joined #openstack-meeting-404:06
*** hongbin has quit IRC04:21
*** gcheresh has quit IRC04:28
*** janki has joined #openstack-meeting-404:37
*** gcheresh has joined #openstack-meeting-404:43
*** slaweq has joined #openstack-meeting-404:49
*** yboaron_ has joined #openstack-meeting-404:57
*** slaweq has quit IRC04:59
*** pcaruana has joined #openstack-meeting-405:02
*** pcaruana has quit IRC05:11
*** slaweq has joined #openstack-meeting-405:16
*** gcheresh has quit IRC05:16
*** slaweq has quit IRC05:20
*** gcheresh has joined #openstack-meeting-405:21
*** e0ne has joined #openstack-meeting-405:23
*** e0ne has quit IRC05:24
*** lei-zh has joined #openstack-meeting-405:27
*** radeks_ has joined #openstack-meeting-405:36
*** Luzi has joined #openstack-meeting-405:43
*** gcheresh has quit IRC06:11
*** slaweq has joined #openstack-meeting-406:12
*** lpetrut has joined #openstack-meeting-406:15
*** yboaron_ has quit IRC06:23
*** markvoelker has joined #openstack-meeting-406:36
*** gcheresh_ has joined #openstack-meeting-406:52
*** trident has quit IRC07:03
*** trident has joined #openstack-meeting-407:05
*** markvoelker has quit IRC07:09
*** roman_g has joined #openstack-meeting-407:18
*** ralonsoh has joined #openstack-meeting-407:19
*** lemko has joined #openstack-meeting-407:20
*** pcaruana has joined #openstack-meeting-407:21
*** k_mouza has joined #openstack-meeting-407:25
*** k_mouza has quit IRC07:26
*** k_mouza has joined #openstack-meeting-407:26
*** k_mouza has quit IRC07:31
*** pcaruana has quit IRC07:39
*** k_mouza has joined #openstack-meeting-407:39
*** e0ne has joined #openstack-meeting-407:42
*** k_mouza has quit IRC07:43
*** e0ne has quit IRC07:57
*** happyhemant has joined #openstack-meeting-407:58
*** e0ne has joined #openstack-meeting-408:01
*** markvoelker has joined #openstack-meeting-408:06
*** k_mouza has joined #openstack-meeting-408:11
*** k_mouza has quit IRC08:15
*** diablo_rojo has joined #openstack-meeting-408:17
*** k_mouza has joined #openstack-meeting-408:21
*** k_mouza has quit IRC08:25
*** k_mouza has joined #openstack-meeting-408:26
*** k_mouza has quit IRC08:30
*** markvoelker has quit IRC08:39
*** k_mouza has joined #openstack-meeting-408:52
*** k_mouza_ has joined #openstack-meeting-408:54
*** k_mouza_ has quit IRC08:56
*** k_mouza has quit IRC08:56
*** k_mouza has joined #openstack-meeting-408:56
*** k_mouza has quit IRC08:57
*** k_mouza has joined #openstack-meeting-408:58
*** k_mouza_ has joined #openstack-meeting-409:01
*** k_mouza has quit IRC09:02
*** diablo_rojo has quit IRC09:03
*** k_mouza_ has quit IRC09:25
*** lei-zh has quit IRC09:35
*** k_mouza has joined #openstack-meeting-409:35
*** markvoelker has joined #openstack-meeting-409:35
*** diablo_rojo has joined #openstack-meeting-409:38
*** k_mouza has quit IRC09:39
*** k_mouza has joined #openstack-meeting-409:41
*** k_mouza_ has joined #openstack-meeting-409:43
*** k_mouza has quit IRC09:46
*** k_mouza has joined #openstack-meeting-409:46
*** k_mouza_ has quit IRC09:48
*** k_mouza has quit IRC09:51
*** k_mouza has joined #openstack-meeting-410:03
*** markvoelker has quit IRC10:09
*** k_mouza has quit IRC10:18
*** k_mouza has joined #openstack-meeting-410:32
*** k_mouza has quit IRC10:36
*** k_mouza has joined #openstack-meeting-410:39
*** k_mouza has quit IRC10:41
*** k_mouza_ has joined #openstack-meeting-410:41
*** k_mouza_ has quit IRC10:43
*** k_mouza has joined #openstack-meeting-410:43
*** k_mouza has quit IRC10:45
*** k_mouza has joined #openstack-meeting-410:49
*** k_mouza has quit IRC10:54
*** snapiri has quit IRC11:03
*** markvoelker has joined #openstack-meeting-411:06
*** k_mouza has joined #openstack-meeting-411:26
*** dave-mccowan has joined #openstack-meeting-411:27
*** k_mouza has quit IRC11:30
*** k_mouza_ has joined #openstack-meeting-411:30
*** k_mouza_ has quit IRC11:34
*** markvoelker has quit IRC11:39
*** bobh has joined #openstack-meeting-411:45
*** bobh has quit IRC11:46
*** janki has quit IRC11:54
*** k_mouza has joined #openstack-meeting-411:58
*** k_mouza_ has joined #openstack-meeting-412:00
*** k_mouza_ has quit IRC12:01
*** k_mouza__ has joined #openstack-meeting-412:01
*** k_mouza__ has quit IRC12:02
*** k_mouza_ has joined #openstack-meeting-412:02
*** k_mouza has quit IRC12:02
*** k_mouza_ has quit IRC12:07
*** markvoelker has joined #openstack-meeting-412:08
*** seajay has joined #openstack-meeting-412:10
*** k_mouza has joined #openstack-meeting-412:26
*** k_mouza_ has joined #openstack-meeting-412:30
*** k_mouza has quit IRC12:30
*** diablo_rojo has quit IRC12:33
*** psachin has quit IRC12:34
*** k_mouza_ has quit IRC12:37
*** k_mouza has joined #openstack-meeting-412:39
*** howell has joined #openstack-meeting-412:54
*** bh526r has joined #openstack-meeting-412:54
*** janki has joined #openstack-meeting-413:11
*** k_mouza has quit IRC13:27
*** k_mouza has joined #openstack-meeting-413:29
*** gcheresh_ has quit IRC13:29
*** k_mouza has quit IRC13:33
*** k_mouza has joined #openstack-meeting-413:35
*** k_mouza_ has joined #openstack-meeting-413:38
*** k_mouza_ has quit IRC13:39
*** k_mouza has quit IRC13:40
*** k_mouza has joined #openstack-meeting-413:42
*** sgrasley has joined #openstack-meeting-413:49
*** erolg has quit IRC13:53
*** jchhatbar has joined #openstack-meeting-413:57
*** spiette_ has joined #openstack-meeting-413:59
*** isq_ has joined #openstack-meeting-414:00
*** janki has quit IRC14:06
*** markmcclain has quit IRC14:06
*** dosaboy has quit IRC14:06
*** markvoelker has quit IRC14:06
*** ralonsoh has quit IRC14:06
*** yamahata__ has quit IRC14:06
*** spiette has quit IRC14:06
*** cheng1 has quit IRC14:06
*** aspiers has quit IRC14:06
*** mjturek has quit IRC14:06
*** Luzi has quit IRC14:09
*** kgz has quit IRC14:11
*** ralonsoh has joined #openstack-meeting-414:12
*** kgz has joined #openstack-meeting-414:15
*** kgz has quit IRC14:16
*** kragniz has joined #openstack-meeting-414:18
*** kragniz is now known as kgz14:20
*** aspiers has joined #openstack-meeting-414:24
*** lpetrut has quit IRC14:27
*** liuyulong has joined #openstack-meeting-414:39
*** k_mouza has quit IRC14:44
*** k_mouza has joined #openstack-meeting-414:46
*** k_mouza_ has joined #openstack-meeting-414:50
*** k_mouza has quit IRC14:51
*** k_mouza_ has quit IRC14:54
*** mfuller_ has joined #openstack-meeting-414:56
*** gagehugo has joined #openstack-meeting-415:00
portdirect#startmeeting openstack-helm15:00
*** k_mouza has joined #openstack-meeting-415:00
openstackMeeting started Tue May 21 15:00:17 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
evrardjpo/15:00
howello/15:00
*** itxaka has joined #openstack-meeting-415:00
megheisler\o15:00
portdirecthey all - the agenda is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-05-2115:00
itxakao/15:00
portdirectvery light this week15:00
mfuller_o/15:00
portdirectlets give it 5 mins for people to roll up15:00
gagehugoo/15:01
portdirectthough i expect this one may be quite light as many people are in bcn for kubecon15:01
georgkhi15:01
srwilkerso/15:01
*** mattmceuen has joined #openstack-meeting-415:01
mattmceueno/15:01
*** jchhatbar is now known as janki15:02
alanmeadowso/15:03
georgkquick question: who of you is at KubeCon - for a short chat15:03
evrardjpI am not15:04
georgkeverybody is hiding... :-)15:04
mattmceuenI am back at work as well :)15:05
*** cfriesen has joined #openstack-meeting-415:05
itxakame neither :(15:05
portdirectok lets go15:06
portdirect#topic tempest prerequisites from scripts to init containers15:06
*** openstack changes topic to "tempest prerequisites from scripts to init containers (Meeting topic: openstack-helm)"15:06
itxakatoday its all me :)15:07
*** cheng1__ has joined #openstack-meeting-415:07
*** hamzy has quit IRC15:07
itxakaso this was brougth up with our airship team, they find it quite a pain to do an automated airhship deployment that includes tempest because we are doing automated things in our deployment scripts to deploy a working tempest chart15:08
*** mbuil_ has joined #openstack-meeting-415:08
itxakaand the idea was brougth up to explore having those prerequisites be a part of the init containers of tempest to provide a full unmaned deployment of the tempest chart by passing just values15:08
portdirectwhat would the container do?15:09
evrardjpand how do you test the idempotency impact on said change on the chart?15:09
itxakacreate network+subnetwork basically15:10
itxakaand obtain the ids for the other needed components (only the image id I believe)15:10
itxaka*correction: and flavor id15:10
portdirectfor the 2nd point ++15:10
evrardjpwhat is the second point?15:11
portdirectfor the 1st, kinda ok with it - though with this not be better suited to being either in the boostrap job for the neutron chart15:11
evrardjphaving those at init containers?15:11
portdirector a generic heat driven 'openstack objects chart'15:11
itxakabasically whats in here: https://github.com/openstack/openstack-helm/blob/f9231d720c2299c5d85f614c2e1787599b069199/tools/deployment/multinode/900-tempest.sh15:11
portdirectevrardjp: point 1: `create network+subnetwork basically` point 2: `obtain the ids for...`15:12
itxakaso we can have a tempest deployment like the other charts, just passing values to the chart15:12
evrardjpok15:12
evrardjppoint 1 can be a part of the bootstrap neutron or tempest itself?15:12
itxakammmh using neutron to bootstrap any nets is also a good idea<15:12
portdirecti wonder if this: https://github.com/openstack/openstack-helm/blob/f9231d720c2299c5d85f614c2e1787599b069199/tools/deployment/multinode/900-tempest.sh#L22-L4315:12
portdirectshould become its own chart15:12
evrardjpthat's what I suggested15:13
evrardjpbut then you have to pass values around for next chart15:13
itxakanot really, you can store them in a shared configmap no?15:13
evrardjpwhich means introspection of the first chart values or things like that, which sounds not really clean15:14
portdirectid avoid that15:14
evrardjpitxaka: exactly15:14
itxakaand tempest can try to use those value if exists?15:14
portdirectitxaka: i'd avoid configmap deps across charts15:14
evrardjpit's still not great15:14
portdirectit gets super ugly15:14
evrardjpconvention over configuration can help here IMO15:14
* itxaka is thankful to not have experience there :D15:14
portdirectbut if you have the names, then you init container can get the ids..15:14
*** cheng1 has joined #openstack-meeting-415:15
portdirectso the info to pass as values becomes super simple15:15
itxakaI think that havin the neutron bootstrap creating networks is a really great and clean idea15:15
itxakaits useful in a lot of different scenarios15:15
itxakanot only for this15:15
itxakathen the init containers for tempest can just try to get the existing ids for those values only15:16
evrardjpI like the idea of automatically having not a bootstrap but another job to add some networks15:16
itxakaso its simpler to maintain15:16
evrardjpand those can indeed contain tempest networks15:16
evrardjpand with convention, re-use those in tempest helm chart15:16
portdirectthis is what we did for ironic15:16
portdirecteg: https://github.com/openstack/openstack-helm/blob/master/ironic/templates/bin/_retreive-cleaning-network.sh.tpl#L21-L2515:16
portdirectand a job to create if not already in existance15:17
portdirecthttps://github.com/openstack/openstack-helm/blob/master/ironic/templates/bin/_manage-cleaning-network.sh.tpl15:17
portdirectwhich could be transfered over to tempest pretty simply15:18
evrardjpso you mean a change in the tempest helm chart15:18
itxakaI dont even think we would need a job to create, that seems to fall out of a chart territory....15:18
itxakalike neutron chart should do network stuff, tempest should do tempest15:18
evrardjpI am fine with either neutron or tempest tbh15:18
portdirectitxaka: i agree15:18
evrardjpbut not as a separate chart which shares the data between with the help of configmaps15:19
evrardjpor others15:19
portdirectthough in some places the neutron boostrap job etc has limitations - eg with visibility15:19
evrardjpcould you clarify this?15:19
portdirecthence why im suggesting that perhaps we build a openstack-object cart that just drives a heat template15:19
portdirectevrardjp: yeah - people dont know to look for it :)15:20
portdirectand also inter service work is hard15:20
evrardjpportdirect: oh I misunderstood you -- you want to regroup ALL the activities under one roof?15:20
portdirectno15:20
evrardjpand conditionally trigger things?15:20
evrardjpok15:20
portdirectuse the boostrap job for boostrapping the service15:20
evrardjpI didn't quite catch what's your end state you desire then15:20
itxakabootstrap seems like a win win to me15:20
portdirectand have a chart that can creqte higher level objects15:20
itxakanow its me the one that got lost15:21
itxakaso no bootstrap jobs but a chart that creates all desired objects in teh deployment?15:22
portdirectboth - use boostrap where required15:22
portdirectbut a chart that can then be used above that to create deployed artifacts scross the cloud15:23
portdirecteg - boostrap can not create say a collection of glance images, neutron networks and nova vms sanely15:23
portdirectbut can prepare all those services to do so15:23
portdirectand a higher level chart then has value of orchestrating these 'primed' services15:24
itxakawhy cant bootstrap create a collection of objects related to its own chart?15:24
portdirectit can15:24
itxakait also sounds like reinventing heat :p15:24
portdirectno - its using heat ;)15:24
portdirect<portdirect> Pete Birley or a generic heat driven 'openstack objects chart'15:24
itxakashould chats be self contained? like everything from glance should eb done on the glance chart?15:25
itxakachats lmao15:25
itxaka*charts :D15:25
srwilkersyeah, i think that's the point being made here15:25
evrardjpI like the idea of being self-contained too15:25
itxakamaybe someone isnt deploying heat but still wants some images to be there15:25
portdirectcharts have to be self contained15:25
evrardjpsrwilkers: I think the message is not crossing the atlantic15:26
evrardjp:)15:26
evrardjpportdirect: I guess the question is where to put the line on "when/how" to use this chart leveraging heat cli15:26
portdirecti can boil it down to this i think:15:26
portdirect1) bootstrap script to boosstrap a service15:27
portdirect2) heat template in a chart to bootstrap a cloud15:27
portdirectwe have 1 today15:27
portdirectwe could do with 215:27
evrardjpok let me rephrase this15:27
evrardjpsee if I got it15:27
srwilkersultimately, the chart portdirect is talking about would be to do things that require creating objects that span the multiple services in our cloud (ie: i need to create some networks, some images, and whatever else for people/tempest/whatever to consume).  it doesn't make sense to have a job specific to tempest create things like networks and images that it needs to consume15:28
srwilkerswhich is why it'd be nice to have a chart that simply leverages heat to do this for us15:28
evrardjp1) bootstrap will only be used to "get started" with the service, and anything happening after service setup is delegated elsewhere.15:28
evrardjpI don't agree on the fact that "it doesn't make sense to have a job specific to tempest to create things tempest needs"15:28
evrardjpthat's exactly the point of the bootstrap jobs?15:29
portdirectre 1 - yes15:29
evrardjpok I understood the line/border15:29
evrardjpthe border makes sense to me15:29
evrardjpit's clear to explain to people and document15:29
portdirectre 2 - on the fence, i'd not block it - but here it would make more sens i think to seperate the concerns - as tempest is a test suite15:30
portdirect2 being `it doesn't make sense to have a job specific to tempest to create things tempest needs` in this case15:30
* srwilkers shrugs15:30
alanmeadowsThe other item worth mentioning15:31
itxakaok, so then its kind-of agreed that for creating objects in a cloud, an extra chart would be needed that leverages heat to create those objects15:31
itxakawith the only goal of that chart is bringing the deployed cloud to a user required state15:31
portdirectitxaka: that would be the best path i think15:31
evrardjpalanmeadows: yes?15:31
itxakanot just to use tempest but as a boostrap cloud kind of chart15:31
alanmeadowsis if you use bootstrap to actually "set up your cloud" rather than just do whats absolutely necessary to have that service up you'll end up with piecemeal data fed into dozens of different charts that will be hard to visualize/manage15:32
portdirecthence my visibility comment earlier15:32
alanmeadowsthat actually probably blongs in one place (e.g. how I setup openstack for my users)15:32
evrardjpI think we were in agreement to not set things to "set up your cloud" in bootstrap :)15:32
itxakaagreed15:32
portdirectjust to throw things off again - the one q i have is heat or shade?15:33
evrardjpthe focus point here was to setup the requirements for tempest. If we consider the setup the requirements part of the "set up your cloud" or if tempest chart itself would be setting up its requirements itself15:34
portdirecti think proabably heat, though it does depend in it - but a q worth asking15:34
evrardjpyou probably mean sdk15:34
evrardjpanything idempotent works for me15:34
itxakaheat I think althougth falling back to openstackclient in case of no heat may be worth discussing15:35
itxakabut who doesnt install heat!15:35
srwilkersthe same people who thought the game of thrones ending was good15:35
evrardjpthis is why SDK would not be a bad idea15:35
itxakaoh lmao15:35
gagehugohaha15:35
itxakashots fired15:35
mfuller_hahaha15:35
evrardjpsrwilkers: haha15:35
portdirectitxaka: here i dont think we want to offer a choice - if we go heat - inject raw heat as values.15:35
* itxaka adds srwilkers to good guys list15:35
*** hamzy has joined #openstack-meeting-415:35
srwilkerswhy do you think i came all this way itxaka?15:36
itxakaportdirect: sounds good!15:36
portdirectevrardjp: i ment shade here15:36
portdirectbut favor heat15:36
itxakaI think that making it clear that this requires heat would make the chart simpler15:36
portdirectevrardjp: actually i take that back - but still favor heat15:36
portdirect:)15:36
portdirectso shall we do it itxaka ?15:37
portdirectim down.15:37
alanmeadowsprobably the i-configure-openstack-chert should just support a few values? provide your uber heat stack here, openstackclient values here, shade values here?15:37
alanmeadowsthen the end user can do what they please?15:37
evrardjpI think the openstacksdk is more self contained and provide the same value, but it's up to the committer to decide15:37
alanmeadowsas long as, as evrardjp says, its idempotent15:37
portdirectalanmeadows: wfm15:38
evrardjpalanmeadows: you could have been belgian with your sense of the compromise there15:38
itxakalmao15:38
alanmeadowswell in this case, supporting "all the things" isn't that much work15:38
alanmeadows;-)15:38
itxakawfm15:38
evrardjpthings can also grow organically15:38
itxakaso heat first then openstackclient then shade?15:38
portdirectitxaka: sounds good15:39
itxakayaya15:39
portdirectheat > bash > python ;P15:39
evrardjpopenstackclient will be tedious to make idempotent, but up to you15:39
evrardjpportdirect: cannot compute that line15:39
portdirectno one can - its why its perfect15:39
evrardjpI cannot compute*15:39
* itxaka adds portdirect to the bad guys list15:39
* portdirect strokes white cat15:40
* evrardjp would like to see s/Arya/itxaka/ lists15:40
portdirectok to move on?15:40
evrardjpare the action points taken?15:40
evrardjpok for me to move on15:41
itxakalast item, if you have a good name for it please write it down15:41
itxakaIm bad at names15:41
itxakaso I will use alanmeadows one if there is no better suggestions :P15:41
srwilkersa chert has no name15:41
itxakai-configure-openstack-chert15:41
portdirectcloudstrap15:41
evrardjpsrwilkers: stop it! :p15:41
evrardjpportdirect: that's a trademark?15:42
evrardjpif not I should totally make taht a trademark15:42
portdirectmight be :(15:42
itxakaalready taken15:42
portdirectopenstack-objects may be the best, though most borning name15:42
evrardjpthe project name is openstack-helm15:43
evrardjpfor those who don't follow15:43
evrardjpshould we move on though?15:43
itxaka+115:43
itxakaoh wow that took a long time15:44
portdirect#topic meeting times ( http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006381.html )15:44
*** openstack changes topic to "meeting times ( http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006381.html ) (Meeting topic: openstack-helm)"15:44
itxakaso I put that in there but was just because the mail is on the list and I didnt see too many replies15:44
itxakamaily a heads up to people15:44
itxakamainly*15:44
itxaka+1 to move on15:44
evrardjpgood reminder15:45
*** k_mouza has quit IRC15:45
portdirectthx itxaka15:45
evrardjpjayahn: will thank you for it :)15:45
portdirect#topic versioning of helm charts -- spec status15:45
*** openstack changes topic to "versioning of helm charts -- spec status (Meeting topic: openstack-helm)"15:45
evrardjpjust wondering where we are there15:45
portdirectso im behind here - and need to get a draft of this up15:45
portdirectbut have something thats close to being push-able15:46
evrardjpppl can only start to work on things when the spec will be merged15:46
evrardjpit's just a reminder15:46
evrardjpnext topic15:46
evrardjp?15:46
portdirect#topic gates changes -- spec status15:47
*** openstack changes topic to "gates changes -- spec status (Meeting topic: openstack-helm)"15:47
portdirectevrardjp: you added this one i think15:47
evrardjpyes15:48
evrardjpI think we discussed some improvements in gates in the past. I had a series of patches long ago that always ended up in merge conflicts, so I dropped them all. IIRC, there was a spec that was supposed to be out, what's the status?15:48
portdirecttheres not been discussion of a spec that i can rememebr15:49
portdirectbut srwilkers and I were going to look at the gates prior to ptg - and have still to do so15:49
portdirecthttps://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-2315:49
portdirectso we should get back on that15:49
evrardjpok, I thought the result of that look was a spec15:49
evrardjpmy bad.15:50
portdirectno worries - a spec would certainly help this process15:50
portdirectso we should consider one following the poc15:50
itxakaportdirect: is the poc close or far away? maily to write it down on the etherpad15:50
portdirecti think its just a case of srwilkers and i finding 4 hours to do it15:51
evrardjpno need to really have specs for the purpose of having specs though, but documenting the reasons we decided to do that way, is useful15:51
*** cheng1__ has quit IRC15:51
portdirectevrardjp: exactly++15:51
evrardjpreviews? :D15:52
evrardjpovs-dpdk could deserve some love! :p15:52
portdirect#topic reviews15:53
evrardjpbut I am getting ahead of myself here15:53
*** openstack changes topic to "reviews (Meeting topic: openstack-helm)"15:53
portdirectas always a long list of things that could do with some love:15:53
portdirectReviews:15:53
portdirect    - https://pasted.tech/l/1701e85c296214b4 (or long url: https://review.opendev.org/#/q/project:%255Eopenstack/openstack-helm.*+owner:%22Jean-Philippe+Evrard+%253Cjean-philippe%2540evrard.me%253E%22++is:mergeable++is:open )15:53
portdirectOVS-DPDK15:53
portdirect- https://review.opendev.org/#/c/659581/ - workflow15:53
portdirect- https://review.opendev.org/#/c/626894/ - reviews from cores appreciated15:53
portdirect- https://review.opendev.org/#/c/643284/ - reviews from cores appreciated15:53
portdirect- https://review.opendev.org/#/c/651060/ - reviews from cores appreciated15:53
portdirect- https://review.opendev.org/#/c/659351/ - reviews from cores appreciated15:53
portdirect- https://review.opendev.org/#/c/659787/ - mysql: set hostpath for mysql-data (fixes zuul jobs)15:53
portdirect- https://review.opendev.org/#/c/659557/ - ceph: bump kubernetes version for ceph images15:53
portdirect- https://review.opendev.org/#/c/650523/ - Migrate ubuntu jobs from Xenial to Bionic (important for gating)15:53
*** k_mouza has joined #openstack-meeting-415:53
evrardjpthe first one is very important to us, but not as important as fixing the zuul jobs :D15:54
portdirectfor the dpdk work - it would be good to see this gated15:54
georgkyes, evrardjp mentioned this already15:54
*** k_mouza has quit IRC15:54
georgki need to see if I get DPDK working in the virtualized Openstack infra15:54
evrardjpportdirect: maybe not gated, but at least CI tested first? It still need some things to merfe first15:54
portdirectthat would be great georgk15:55
evrardjpmerge*15:55
*** e0ne has quit IRC15:55
georgkis that a prerequisite for gettting this merged?15:55
portdirectci tested would be15:55
*** k_mouza has joined #openstack-meeting-415:55
evrardjpportdirect: but this is very special15:55
*** janki has quit IRC15:55
evrardjp(if we don't have the hardware)15:55
*** macza has joined #openstack-meeting-415:55
portdirectevrardjp: we can get 3rd party ci i think for this15:56
*** macza has quit IRC15:56
evrardjp3rd party ci will never gate15:56
evrardjpit can vote but that's the max15:56
evrardjp(on purpose)15:56
*** k_mouza_ has joined #openstack-meeting-415:56
*** macza has joined #openstack-meeting-415:56
portdirectbut im not sure why we could not run in -infra?15:56
georgkas I said, I need to check15:57
evrardjplet me rephrase this -- we can have 3rd party CI voting, and I think that's an option we should follow if we can't do things in infra15:57
georgkI'll probably poke some of you who have better insight into this15:57
portdirectgeorgk: i think deepak would be great here15:58
evrardjpbut I also believe that this has value merged even without the testing yet. (Because there could be chicken and egg things)15:58
evrardjp(for example, the image building of dpdk should be merged before)15:58
*** k_mouza has quit IRC15:58
evrardjpbut that's my personal opinion, I am no one here :p15:58
*** cfriesen has left #openstack-meeting-415:59
georgkright, we need to address the images15:59
evrardjpout of time15:59
portdirectthanks everyone!16:00
portdirectsee you all in the channel16:00
portdirect#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue May 21 16:00:36 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-05-21-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-05-21-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-05-21-15.00.log.html16:00
*** gagehugo has left #openstack-meeting-416:00
*** k_mouza_ has quit IRC16:01
*** itxaka has quit IRC16:03
*** seajay has quit IRC16:05
*** itxaka has joined #openstack-meeting-416:05
*** aperevalov has quit IRC16:11
*** igordc has joined #openstack-meeting-416:20
*** seajay has joined #openstack-meeting-416:24
*** seajay has quit IRC17:07
*** seajay_ has joined #openstack-meeting-417:07
*** iyamahat has joined #openstack-meeting-417:12
*** igordc has quit IRC17:12
*** igordc has joined #openstack-meeting-417:13
*** iyamahat has quit IRC17:24
*** iyamahat has joined #openstack-meeting-417:27
*** yamahata has joined #openstack-meeting-417:27
*** ralonsoh has quit IRC17:37
*** igordc has quit IRC17:46
*** igordc has joined #openstack-meeting-418:18
*** mbuil_ has quit IRC18:18
*** itxaka has quit IRC18:59
*** itxaka has joined #openstack-meeting-418:59
*** radeks_ has quit IRC19:48
*** logan- has quit IRC19:55
*** lemko has quit IRC20:20
*** e0ne has joined #openstack-meeting-420:39
*** hamzy has quit IRC20:45
*** dave-mccowan has quit IRC20:50
*** dave-mccowan has joined #openstack-meeting-420:56
*** e0ne has quit IRC20:56
*** logan- has joined #openstack-meeting-421:15
*** diablo_rojo has joined #openstack-meeting-421:19
*** howell has quit IRC21:25
*** slaweq has quit IRC21:27
*** dave-mccowan has quit IRC21:40
*** seajay_ has quit IRC22:00
*** macza has quit IRC23:39
*** macza has joined #openstack-meeting-423:40
*** bh526r has quit IRC23:44
*** macza has quit IRC23:47

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