Tuesday, 2019-06-18

*** georgk has quit IRC00:31
*** fdegir has quit IRC00:31
*** fdegir has joined #openstack-meeting-400:32
*** georgk has joined #openstack-meeting-400:32
*** diablo_rojo has quit IRC00:35
*** lemko has quit IRC00:35
*** michael-beaver has quit IRC00:35
*** markvoelker has joined #openstack-meeting-400:45
*** yamamoto has joined #openstack-meeting-400:45
*** markvoelker has quit IRC00:50
*** hongbin has joined #openstack-meeting-401:32
*** yamamoto has quit IRC01:42
*** yamamoto has joined #openstack-meeting-401:42
*** markvoelker has joined #openstack-meeting-401:46
*** iyamahat__ has joined #openstack-meeting-401:46
*** yamahata has quit IRC01:49
*** iyamahat_ has quit IRC01:49
*** iyamahat_ has joined #openstack-meeting-401:50
*** markvoelker has quit IRC01:50
*** iyamahat__ has quit IRC01:53
*** iyamahat_ has quit IRC01:56
*** markvoelker has joined #openstack-meeting-402:46
*** markvoelker has quit IRC02:51
*** markvoelker has joined #openstack-meeting-403:47
*** hongbin has quit IRC03:47
*** psachin has joined #openstack-meeting-403:50
*** markvoelker has quit IRC03:52
*** yboaron_ has joined #openstack-meeting-404:21
*** yboaron_ has quit IRC04:25
*** iyamahat has joined #openstack-meeting-404:30
*** janki has joined #openstack-meeting-404:35
*** markvoelker has joined #openstack-meeting-404:48
*** markvoelker has quit IRC04:52
*** pcaruana has joined #openstack-meeting-404:56
*** yamahata has joined #openstack-meeting-405:09
*** johnsom has quit IRC05:36
*** csatari has quit IRC05:36
*** hogepodge has quit IRC05:36
*** csatari has joined #openstack-meeting-405:38
*** hogepodge has joined #openstack-meeting-405:38
*** johnsom has joined #openstack-meeting-405:38
*** e0ne has joined #openstack-meeting-405:44
*** Luzi has joined #openstack-meeting-405:44
*** markvoelker has joined #openstack-meeting-405:49
*** markvoelker has quit IRC05:54
*** slaweq has joined #openstack-meeting-406:09
*** janki has quit IRC06:15
*** e0ne has quit IRC06:26
*** igordc has quit IRC06:32
*** e0ne has joined #openstack-meeting-406:36
*** gcheresh has joined #openstack-meeting-406:47
*** lemko has joined #openstack-meeting-406:49
*** markvoelker has joined #openstack-meeting-406:50
*** markvoelker has quit IRC06:54
*** trident has quit IRC06:57
*** trident has joined #openstack-meeting-406:59
*** e0ne has quit IRC07:13
*** ralonsoh has joined #openstack-meeting-407:50
*** markvoelker has joined #openstack-meeting-407:50
*** markvoelker has quit IRC07:55
*** ktibi has joined #openstack-meeting-408:01
*** spsurya has joined #openstack-meeting-408:01
*** ltomasbo has quit IRC08:12
*** e0ne has joined #openstack-meeting-408:23
*** psachin has quit IRC08:24
*** gcheresh has quit IRC08:29
*** gcheresh has joined #openstack-meeting-408:30
*** ltomasbo has joined #openstack-meeting-408:33
*** dklyle has quit IRC08:35
*** david-lyle has joined #openstack-meeting-408:35
*** markvoelker has joined #openstack-meeting-408:51
*** markvoelker has quit IRC08:56
*** k_mouza has joined #openstack-meeting-408:59
*** yamamoto has quit IRC09:23
*** yamamoto has joined #openstack-meeting-409:24
*** Adri2000 has quit IRC09:26
*** yamamoto has quit IRC09:29
*** maysams has quit IRC09:32
*** yboaron_ has joined #openstack-meeting-409:43
*** iyamahat has quit IRC09:52
*** ktibi has quit IRC10:18
*** k_mouza has quit IRC10:39
*** yamamoto has joined #openstack-meeting-410:41
*** psachin has joined #openstack-meeting-410:48
*** yamamoto has quit IRC10:50
*** yamamoto has joined #openstack-meeting-410:59
*** gcheresh has quit IRC11:09
*** mjturek has quit IRC11:23
*** bobmel has joined #openstack-meeting-411:23
*** mjturek has joined #openstack-meeting-411:23
*** ktibi has joined #openstack-meeting-411:34
*** dave-mccowan has joined #openstack-meeting-411:35
*** Adri2000 has joined #openstack-meeting-411:46
*** yamamoto has quit IRC11:48
*** yamamoto has joined #openstack-meeting-411:49
*** yamamoto has quit IRC11:53
*** seajay has joined #openstack-meeting-412:01
*** lpetrut has joined #openstack-meeting-412:05
*** k_mouza has joined #openstack-meeting-412:29
*** yamamoto has joined #openstack-meeting-412:35
*** lpetrut has quit IRC12:39
*** markvoelker has joined #openstack-meeting-412:55
*** bh526r has joined #openstack-meeting-412:56
*** markvoelker has quit IRC13:00
*** roman_g has quit IRC13:08
*** howell has joined #openstack-meeting-413:11
*** roman_g has joined #openstack-meeting-413:20
*** bobmel has quit IRC13:33
*** bobmel has joined #openstack-meeting-413:33
*** pcaruana has quit IRC13:37
*** seajay has quit IRC13:38
*** yamamoto has quit IRC13:41
*** yamamoto has joined #openstack-meeting-413:42
*** seajay has joined #openstack-meeting-413:42
*** yamamoto has quit IRC13:42
*** yamamoto has joined #openstack-meeting-413:43
*** psachin has quit IRC13:46
*** seajay has quit IRC13:52
*** liuyulong has joined #openstack-meeting-413:53
*** pcaruana has joined #openstack-meeting-413:54
*** markvoelker has joined #openstack-meeting-413:56
*** michael-beaver has joined #openstack-meeting-413:56
*** k_mouza has quit IRC13:59
*** k_mouza has joined #openstack-meeting-414:04
*** liuyulong has quit IRC14:07
*** Luzi has quit IRC14:12
*** liuyulong has joined #openstack-meeting-414:15
*** markvoelker has quit IRC14:15
*** gagehugo has joined #openstack-meeting-414:20
*** e0ne has quit IRC14:28
*** arunkant has joined #openstack-meeting-414:40
*** JamesBenson has joined #openstack-meeting-414:40
*** rihbb has joined #openstack-meeting-414:41
*** e0ne has joined #openstack-meeting-414:52
*** itxaka has joined #openstack-meeting-414:57
*** mattmceuen has joined #openstack-meeting-414:59
evrardjpo/15:00
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Jun 18 15:00:21 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. 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
georgkhi15:00
mattmceuen#topic Rollcall15:00
*** openstack changes topic to "Rollcall (Meeting topic: openstack-helm)"15:00
mattmceuenhttps://etherpad.openstack.org/p/osh-meeting-2019-06-1815:00
mattmceuenHey everybody - here is our agenda ^15:00
rhahi15:00
itxakao/15:00
rihbbhi15:00
mattmceuenwe'll give it a minute before getting started15:01
mattmceuenPlease add anything you'd like to discuss today to the agenda15:01
*** mbuil has joined #openstack-meeting-415:01
*** spsurya has quit IRC15:01
cheng1o/15:02
*** diablo_rojo has joined #openstack-meeting-415:02
mattmceuenAlright -- let's get started15:03
mattmceuen#topic Meeting Time Voting15:03
*** openstack changes topic to "Meeting Time Voting (Meeting topic: openstack-helm)"15:03
mattmceuenI sent out an email on this just a bit ago15:03
mattmceuenSlightly overdue, thanks for your patience :)15:03
mattmceuenportdirect and I sent out an etherpad with options and instructions15:04
mattmceueninstructions are in the etherpad and the email, so need to dig up the email: https://etherpad.openstack.org/p/osh-meeting-vote-201915:04
mattmceuenI'm asking anyone (who cares) to please vote thusly:15:05
mattmceuenPick your top five preferred Meeting Time + Meeting Approach combinations, and fill in one of the templates15:05
mattmceuenI think it's self-explanatory, but please let me know if there are any questions15:06
mattmceuenWe'll run this voting till EOD next Tuesday, so we get one more shot at reminding folks next team meeting15:06
mattmceuenAny questions?15:06
* portdirect slides in through the back door, trips over a chair, looks around then slides awkwardly into a seat.15:07
*** bobmel has joined #openstack-meeting-415:07
mattmceueno/ portdirect :D15:07
mattmceuenalright - moving on!15:07
* evrardjp notices portdirect has dropped the archeological vase everyone was watching at the center of the room15:08
* portdirect slides lower in his chair15:08
mattmceuen#topic openstack-helm-images release tagging/naming/tracking?15:08
*** openstack changes topic to "openstack-helm-images release tagging/naming/tracking? (Meeting topic: openstack-helm)"15:08
itxakathats me15:08
* mattmceuen is glad portdirect got released briefly from the mines!15:08
mattmceuentake it away itxaka15:09
itxakawondering how we should track releases under the openstack-helm-images repo as we do on the openstack-helm repo15:09
itxakawe been having some issues with this lately, openvswitch for example15:09
itxakatempest is also not synced with any release and its hardcoded15:09
evrardjpwhat do you mean by "having issues" ?15:09
evrardjptempest need some love15:09
itxakasomeone was complaining on irc about having an X version of openvswitch which was not compatible with something15:10
evrardjpIs freezing images with a date good enough?15:10
itxakadoesnt seem like we have the capability to have distinct images pinned to versions15:10
evrardjpitxaka: yes, we discussed this last week I think15:10
itxakaahh did I miss it?15:10
itxakayes, I miss it then15:10
evrardjpbut yeah, we don't "release"15:10
evrardjpwe are currently doing just master15:11
itxakayeah, tempest is terrible in this example becuase using master for it can backfire big time15:11
evrardjpI am not sure what's the proposal here15:11
evrardjpto understand*15:11
itxakano proposal yet, just a heads up that its something that we migth want to tackle sooner than later15:12
itxakaespecially with the upgrade gates incoming15:12
*** markvoelker has joined #openstack-meeting-415:12
itxakawe might start hitting issues with versions out of sync and no way of using a newer/older version from osh-images15:12
itxakaI did not have had time to investigate deeply enough to propose anything15:13
mattmceuenyeah, we discussed the openvswitch example specifically last week, but we should validate that our general approach fits what we need as well15:13
evrardjpso for me that raises two questions.15:13
mbuilitxaka: you mean the OS version or the openstack version? or both?15:13
evrardjp1) should we branch the whole repo with openstack branches? Does that make sense?15:13
itxakaboth should be including when discussing this IMO15:13
evrardjpOr do we branch with our OSH "releases"15:13
itxakathats a great question15:14
evrardjp2) If we do not branch, how do you intend to do this?15:14
portdirectwe (I) need to formalize the response to this - as we have discussed at many ptgs15:14
portdirectwe ideally do not want to branch - but this needs written up15:14
evrardjpyup I think we need to improve documentation there indeed.15:15
itxakado we need to keep a matrix of openstack versions -> image versions then?15:15
evrardjpdo we need to?15:15
itxakaas I missed any convo about this Im just hitting in the dark here on how its supposed to work15:15
portdirectitxaka - we should be able to get that from the tag/image-overrides?15:15
evrardjpbecause we have rolling "openstack" images, and the rest sounds fine to just roll forward15:15
georgkitxaka: honestly, rihbb and I wanted to bring up that exact question today again15:16
itxakaportdirect, how is someone supposed to know that deploying ubuntu-queens from osh needs the osh.image openvsiwthc 20180524 image?15:16
evrardjpok so I think the action items are to clear that up then?15:16
georgkas part of the bionic image introduction15:16
evrardjpitxaka: I see what you mean15:17
itxakathere is no links between osh and osh-images versions written anywhere so it gets a bit confusing15:17
georgk+115:17
mattmceuenitxaka: the ubuntu-queens reference overrides would list out the recommended overrides, right?15:17
mattmceuenrecommended *image overrides15:17
itxakabut for some images we only build "latest" no?15:18
evrardjpbut at every point the "latest" should work, as long as its consistent15:18
itxakawill it? doesnt the openvswitch issue last week told us that it doesnt? or was that a different issue?15:19
mattmceuenlatest of "everything" should probably work together, but to your point evrardjp, if we tag images w/ date (or something) that should be what we use in the reference overrides for particular override sets I would think15:19
evrardjpmattmceuen: I think frozen images should be used for "stable" like branches, or for ensuring upgrades. This is why I said we should link that to OSH and start releasing OSH.15:20
evrardjpit's not an easy topic :)15:20
itxakatbh, from my point of view, if we dont sync with openstack release names it gets unmaintainable pretty soon, even with date-freezed images15:20
evrardjpI didn't say we need to branch per openstack branch in that last comment. But having a "stable" branch15:20
portdirecti agree with evrardjp, on the need for frozen images15:20
mattmceuenSo portdirect I think you were speaking to the famous "sugarcube spec" - should we include image freezing in that spec as a related point of discussion?15:21
evrardjpthe tooling itself doesn't need to be branched though.15:21
portdirecti think i see the need for us to tie these things together using the example over-rides, eg: https://github.com/openstack/openstack-helm/blob/master/neutron/values_overrides/rocky-opensuse_15.yaml15:21
portdirectwe should also do this for things like ovs15:21
itxakaagreed15:21
portdirectusing the same name format - so that we can tie things simplty together15:22
portdirectwhich i suppose is the matrix itxaka proposed, just presented slightly differently?15:22
itxakathe operators know that they are using the correct stuff, and that it should work with other RELEASE_BRANCH components15:22
portdirectyup15:22
*** ktibi has quit IRC15:23
itxakawell, the matrix I was talking assumed that we would only have date-freezed images, which would be a nightmare to maintain15:23
itxakaif we had named frozen images, then its easy peasy15:23
mattmceuenis RELEASE_BRANCH in this context openstack, osh release, OS, or some combo?15:24
itxakasame as osh I think15:24
evrardjpitxaka: I think we should not talk generally in here15:24
mattmceuenI thought we were trying to avoid branching for openstack release and OS release, and only branch for osh major versions15:24
evrardjpthe only problem I see is inconsistent for ovs for the bare ovs image and what's provided in neutron, correct?15:24
georgkevrardjp: yes, due to source build OVS image15:25
evrardjpin that case, can't we just have consistent images by making multiple ovs images (per openstack branch)15:25
portdirect^15:25
evrardjpgeorgk: I think there are multiple solutions to this problem15:25
itxakaand tempest15:25
*** ktibi has joined #openstack-meeting-415:25
evrardjpI would rather tackle those separately15:25
evrardjpthe tempest issue is different right?15:26
evrardjpBecause if you would branch you would not gain anything with tempest, because tempest is supposed to be following master anyway15:26
*** ktibi has quit IRC15:26
evrardjpisn't it?15:26
itxakaso one thing is the problem that we have currently, but this is something that can hit us later with all the other osh-images .... images15:26
evrardjpcan we do a summary of what is decided?15:27
evrardjpI am confused now :p15:27
evrardjpshould that be a spec?15:28
mattmceuen++15:28
evrardjpdocs?15:28
portdirecti think a spec would be great here15:28
evrardjpI propose we document what we do, why we do, and the limitations, and if necessary, a spec for changes?15:28
*** e0ne has quit IRC15:28
itxakaagreed15:28
evrardjpok15:28
itxakasounds like a better way15:28
mattmceuenWe need a spec to outline when OSH is branched, how OSH deals with multiple openstack releases and operating systems, and how image building / tagging / branching dovetails into that15:29
itxakaof discussing this and also getting some backstory on it for those of us that do not have it15:29
portdirectcould we start that in a spec - I think that that would be the best way to fully articulate it15:29
itxakaagreed15:29
portdirectI could take that on - as its been on my action item list for far to long15:29
itxaka+115:30
mattmceuenthat would be awesome portdirect, ty15:30
evrardjpportdirect: I am still waiting for the CI and/or the versioning/releasing of helm charts, don't you want me to draft something?15:30
portdirectI have get a stab at it evrardjp15:30
*** markvoelker has quit IRC15:31
evrardjpok I will let that to you then :)15:31
portdirectthough once its up - i think it would be gret to get multiple people on the ps15:31
portdirect:)15:31
evrardjpfine for me. I just don't want to you burn out due to the amount fo work :)15:31
evrardjplong story short: you have our support, dear leader!15:31
mattmceuen+115:32
mattmceuenIf you need any help dusting off ancient PTG discussions you know where to find me portdirect :D15:32
mattmceuenI'd even buy you new sugarcubes15:32
portdirectlol - I'll take the dear part - though the only leader thing about me is in the title PTL - I'm an admin bod15:32
portdirectmattmceuen: :D15:33
evrardjpmattmceuen: hahah15:33
mattmceuenAlright, anything else to discuss on this before we defer the conversation to the spec?15:33
mattmceuenIn that case, moving on:15:34
portdirectevrardjp: for context, the 1st versioning conversation re osh used many sugarcubes in dublin to work though15:34
mattmceuenThe spec needs sugarcube ascii art or I won't approve it15:34
evrardjpI heard about that, but I wasn't there. It just regularily comes back, it's a nice running joke :)15:34
mattmceuen#topic Idee of a new SIG interesting for OSH members15:35
evrardjp"Today we'll learn about releasing with the _latest_ sugarcubes. Amazing!"15:35
*** openstack changes topic to "Idee of a new SIG interesting for OSH members (Meeting topic: openstack-helm)"15:35
mattmceuenhttps://etherpad.openstack.org/p/containers-sig15:35
mattmceuenevrardjp want to walk us through this?  I haven't had a chance to take a look15:35
evrardjp yeah. That might interest you.15:35
evrardjpoh you expect more text?15:35
evrardjpI am eating a waffle!15:35
itxakalmao15:35
mattmceuenwell I wanted a description, but now I really just want a waffle15:36
evrardjphaha15:36
evrardjpI understand15:36
evrardjpso15:36
mattmceuenno the text in the etherpad looks good :)15:36
evrardjpwell, there were discussions in the past about how to work with different container image building projects. Let's say we didn't document the failures or the agreements.15:36
evrardjpI think in the past there has been a need and a willingness to work together.15:37
evrardjpI am just adding a scope here, and trying to group ppl together15:37
evrardjposh is technically independant of images, but it still builds some, and consumes some15:37
portdirectI think this is a great initiative to get moving15:37
*** hamzy_ has joined #openstack-meeting-415:38
evrardjphave a look at the etherpad, and add your name if you want to participate, actively or passively15:38
evrardjpthat would be nice to have some kind of support.15:38
portdirectI'd really like us to not be in the image building process (or at least have as small a surface area as possible) and this looks like a great step in that direction.15:38
*** yboaron_ has quit IRC15:38
mattmceuenthanks for getting traction on this evrardjp15:38
*** michael-beaver has quit IRC15:39
*** mgagne has quit IRC15:39
*** d34dh0r53 has quit IRC15:39
portdirectand having a common set of guidlines that Kolla/OSH/TrippleO(/OSA?) can use woudl really help15:39
portdirectalong with projects guiding the packaging requirements they have15:39
*** lemko has quit IRC15:39
*** kklimonda has quit IRC15:39
evrardjpOSA is not really part of the scope, as they are using machine containers, but the first action item of collaboration benefits them too15:39
evrardjpso yeah it touches things broadly15:40
*** hamzy has quit IRC15:40
*** d34dh0r53 has joined #openstack-meeting-415:40
portdirectyeah - and the healthchecks!15:40
mattmceuenhooray for healthchecks15:40
*** dave-mccowan has quit IRC15:40
portdirectadam did some great work in that space - it would be good to see it 'taken home'15:40
evrardjpthat would be a collaboration with self-healing I guess15:40
*** michael-beaver has joined #openstack-meeting-415:40
evrardjpyeah15:40
portdirectyeah15:40
*** lemko has joined #openstack-meeting-415:40
*** kklimonda has joined #openstack-meeting-415:41
mattmceuenevrardjp will you send out next steps on the ML, or ?15:41
evrardjpmattmceuen: correct. One will the mailing lists, two will be the patchset for governance-sigs which I already have opened.15:42
evrardjpI am continuing on that lever15:42
evrardjplevel*15:42
mattmceuenexcellent15:42
*** mgagne has joined #openstack-meeting-415:42
*** iyamahat has joined #openstack-meeting-415:42
mattmceuenAny other questions / thoughts on the SIG, team?15:42
mattmceuenThanks evrardjp -- moving on:15:44
mattmceuen#topic Roundtable15:44
*** openstack changes topic to "Roundtable (Meeting topic: openstack-helm)"15:44
mattmceuenWe have some patchsets needing review - and a handful at the top have been waiting for a while:15:44
mattmceuen    https://review.opendev.org/#/c/660572/ --> Rafactoring volume mount variables in db sync job15:44
mattmceuen    https://review.opendev.org/#/c/662992/ --> htk: provide default domain env and secrets15:44
mattmceuen    https://review.opendev.org/#/c/662993/ --> keystone: default domain fix15:44
mattmceuen    https://review.opendev.org/#/c/665102/ --> Add bionic based build jobs to Zuul build configuraton15:44
mattmceuen    https://review.opendev.org/#/c/665310/ --> ubuntu bionic based ovs image15:44
mattmceuenWould be great to get some eyes on all of them15:45
mattmceuenAny other patches we'd like to request extra review on?  Or other Roundtable topics?15:45
georgkfor the bionic images, we'd like to get input in terms of which OpenStack version we should go for15:46
georgkit ties into the discusion we just had15:46
georgkso, comments are welcome15:46
georgkon the patchset15:46
portdirectgeorgk: why move away from source build here?15:47
portdirecti get move from debian, though it does make it very hard to target a particular version of ovs15:47
georgkwe'd like to move away from building OVS from source15:47
portdirectwhy?15:48
georgkah, ok15:48
evrardjpportdirect: but it makes things very consistent to use packages in ovs and neutron image for example15:48
georgkmainly because of incosistencies between the OVS version in the nova and neutron images and the OVS image itself15:48
evrardjpas long as its from the same source, they should work together well :)15:48
*** hamzy_ is now known as hamzy15:48
georgkcurrently, nova and neutron ship with the xenial version of 2.5 which is older than the 2.8 source build15:49
evrardjpalso, why maintaining things where someone does it for you? :D15:49
georgkwe were wondering last week: was there a technical reason to go  for a 2.8 source build?15:49
evrardjp(disclaimer: I work for a distro, but that's not only because that reasoning pays my bills that I have it, it makes genuinely sense to me)15:50
portdirectthere were some bugs in 2.5 that effected operation15:50
portdirecti dont have the details to hand, but can dig them out15:50
evrardjpthat's valuable input15:50
georgkok, we noticed however that 2.5 in neutron-ovs-agent does not work with 2.8 and DPDK15:50
georgkso, we wanted to move to a common consistent version15:51
georgkhence the upgrade to bionic to get off of 2.515:51
portdirectok - lets look to fix that15:51
portdirectare you using the clients to perform operations, or native?15:51
georgkwell, we havent really touched any config on that part15:51
georgkthe default I'd say :)15:52
portdirectgeorgk: I'd look into ovsdb_interface, and check that its set to 'native'15:55
portdirectif so then much of the versioning issues should come down to the python lib used to talk to the ovsdb15:56
georgkok, I'll check that and come back to you15:56
mattmceuen3min left - any additional topics today?15:57
georgkstill, it would be great to use a newer version of OVS with DODK support15:57
portdirectagreed!15:57
mattmceuenAlright folks, that's a wrap - thanks for joining today & have a great week15:59
mattmceuen#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Jun 18 15:59:14 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-06-18-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-06-18-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-06-18-15.00.log.html15:59
georgkok, thank you! have a nice day15:59
*** pcaruana has quit IRC16:01
*** igordc has joined #openstack-meeting-416:03
*** liuyulong has quit IRC16:04
*** rihbb has left #openstack-meeting-416:12
*** gagehugo has left #openstack-meeting-416:13
*** k_mouza has quit IRC16:24
*** mattmceuen has left #openstack-meeting-416:26
*** markvoelker has joined #openstack-meeting-416:28
*** pcaruana has joined #openstack-meeting-416:45
*** markvoelker has quit IRC16:46
*** igordc has quit IRC16:49
*** e0ne has joined #openstack-meeting-416:51
*** altlogbot_1 has quit IRC17:00
*** altlogbot_0 has joined #openstack-meeting-417:01
*** irclogbot_0 has quit IRC17:02
*** irclogbot_3 has joined #openstack-meeting-417:03
*** diablo_rojo has quit IRC17:04
*** yamahata has quit IRC17:06
*** iyamahat has quit IRC17:06
*** iyamahat has joined #openstack-meeting-417:20
*** yamahata has joined #openstack-meeting-417:21
*** slaweq has quit IRC17:34
*** igordc has joined #openstack-meeting-417:35
*** ralonsoh has quit IRC17:56
*** markmcclain has quit IRC18:00
*** gcheresh has joined #openstack-meeting-418:00
*** markmcclain has joined #openstack-meeting-418:02
*** e0ne has quit IRC18:13
*** lemko has quit IRC18:18
*** e0ne has joined #openstack-meeting-418:29
*** slaweq has joined #openstack-meeting-418:31
*** e0ne has quit IRC18:33
*** bh526r has quit IRC18:35
*** pcaruana has quit IRC18:45
*** slaweq has quit IRC18:54
*** pcaruana has joined #openstack-meeting-419:05
*** diablo_rojo has joined #openstack-meeting-419:13
*** JamesBenson has quit IRC19:26
*** ktibi has joined #openstack-meeting-419:26
*** JamesBenson has joined #openstack-meeting-419:27
*** ktibi has quit IRC19:31
*** JamesBenson has quit IRC19:34
*** gcheresh has quit IRC19:35
*** JamesBenson has joined #openstack-meeting-419:36
*** e0ne has joined #openstack-meeting-419:38
*** slaweq has joined #openstack-meeting-419:45
*** gcheresh has joined #openstack-meeting-420:14
*** jesusaur has quit IRC20:30
*** gcheresh has quit IRC20:35
*** e0ne has quit IRC20:36
*** itxaka has quit IRC21:37
*** JamesBenson has quit IRC21:46
*** markvoelker has joined #openstack-meeting-421:48
*** markvoelker has quit IRC22:00
*** slaweq has quit IRC22:08
*** slaweq has joined #openstack-meeting-422:11
*** evgenyl has quit IRC22:12
*** seungkyua has quit IRC22:15
*** slaweq has quit IRC22:16
*** evgenyl has joined #openstack-meeting-422:19
*** seungkyua has joined #openstack-meeting-422:20
*** howell has quit IRC22:44
*** diablo_rojo has quit IRC22:44
*** JamesBenson has joined #openstack-meeting-422:59
*** JamesBenson has quit IRC23:04
*** shachar has quit IRC23:22
*** shachar has joined #openstack-meeting-423:23
*** michael-beaver has quit IRC23:59

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