Tuesday, 2018-06-26

*** yamamoto has quit IRC00:03
*** mjturek has quit IRC00:08
*** yamamoto has joined #openstack-meeting-500:59
*** yamamoto has quit IRC01:05
*** yamahata has quit IRC01:51
*** jgu has joined #openstack-meeting-502:07
*** jgu_ has joined #openstack-meeting-502:21
*** jgu_ has quit IRC02:23
*** iyamahat_ has quit IRC02:23
*** jgu has quit IRC02:25
*** roman_g has quit IRC02:26
*** ricolin has joined #openstack-meeting-502:42
*** yamamoto has joined #openstack-meeting-503:01
*** jgu has joined #openstack-meeting-503:05
*** yamamoto has quit IRC03:07
*** yamahata has joined #openstack-meeting-503:38
*** yamamoto has joined #openstack-meeting-504:04
*** yamamoto has quit IRC04:09
*** dims has quit IRC04:30
*** dims has joined #openstack-meeting-504:35
*** jgu has quit IRC04:38
*** yamamoto has joined #openstack-meeting-505:05
*** slaweq has joined #openstack-meeting-505:07
*** slaweq has quit IRC05:07
*** yamamoto has quit IRC05:12
*** yamamoto has joined #openstack-meeting-506:09
*** slaweq has joined #openstack-meeting-506:13
*** yamamoto has quit IRC06:14
*** yamamoto has joined #openstack-meeting-506:56
*** slaweq has quit IRC07:06
*** slaweq has joined #openstack-meeting-507:10
*** slaweq has quit IRC07:15
*** yamahata has quit IRC07:30
*** slaweq has joined #openstack-meeting-508:05
*** slaweq has quit IRC08:15
*** derekh has joined #openstack-meeting-508:49
*** iyamahat has joined #openstack-meeting-508:56
*** iyamahat has quit IRC08:59
*** roman_g has joined #openstack-meeting-509:02
*** ricolin has quit IRC09:07
*** slaweq has joined #openstack-meeting-509:15
*** slaweq has quit IRC09:23
*** slaweq has joined #openstack-meeting-510:48
*** yamamoto has quit IRC10:58
*** yamamoto has joined #openstack-meeting-511:07
*** slaweq has quit IRC11:23
*** yamamoto has quit IRC11:30
*** yamamoto has joined #openstack-meeting-511:33
*** derekh has quit IRC11:47
*** derekh has joined #openstack-meeting-511:49
*** MarkBaker has quit IRC12:17
*** slaweq has joined #openstack-meeting-512:25
*** slaweq has quit IRC12:29
*** yamamoto has quit IRC13:01
*** mjturek has joined #openstack-meeting-513:14
*** yamamoto has joined #openstack-meeting-513:29
*** MarkBaker has joined #openstack-meeting-513:33
*** hongbin has joined #openstack-meeting-513:42
*** jgu has joined #openstack-meeting-513:56
*** jgu_ has joined #openstack-meeting-513:57
*** jgu has quit IRC14:01
*** wxy| has joined #openstack-meeting-514:16
*** MarkBaker has quit IRC14:16
*** slaweq has joined #openstack-meeting-514:17
*** felipemonteiro has joined #openstack-meeting-514:26
*** felipemonteiro_ has joined #openstack-meeting-514:29
*** felipemonteiro has quit IRC14:33
*** piotrrr has joined #openstack-meeting-514:39
mattmceuen#startmeeting openstack-helm14:59
openstackMeeting started Tue Jun 26 14:59:55 2018 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: openstack-helm)"14:59
openstackThe meeting name has been set to 'openstack_helm'15:00
mattmceuen#topic rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
mattmceuenHi everyone -- here's the agenda for our OSH team meeting today: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-06-2615:00
rwellumo/15:00
mattmceuenI'll give a couple minutes for folks to update if they'd like to add to it15:01
*** vadym has joined #openstack-meeting-515:02
rwellumThanks for adding the production question mattmceuen15:02
mattmceuenFirst up:15:03
mattmceuen#topic Hooking up OSH to provider networks is not well documented15:03
*** openstack changes topic to "Hooking up OSH to provider networks is not well documented (Meeting topic: openstack-helm)"15:03
mattmceuenThanks for bringing this up piotrrr15:03
lamto/15:03
srwilkerso/15:03
mattmceuenThis is a fine line IMO for a couple reasons:15:03
portdirect\015:04
mattmceuen1. don't want to duplicate Neutron config in the OSH docs, but just the OSH-specific bits15:04
mattmceuen2. don't want to dictate how a specific deployment should configure things as that's very deployment-specific15:04
mattmceuenVery open to thoughts here.15:04
mattmceuen?15:04
portdirecthmm15:04
portdirectall points are valid15:04
portdirect0) our documentation is terrible in this regard15:05
mattmceuenBecuase obviously a cloud that can't connect its vms is not all that useful, so problems worth overcoming :D15:05
portdirect1) 100% agree15:05
piotrrrThanks. That's fair enough. Shouldn't we in that case have a dedicated section covering those networking aspects, and refer to it from various OSH deployemnt docs, wherever needed?15:05
vadymmaybe you could at least mention the need to set up bridges in the multinode manual?15:05
portdirect2) again agree, the reference to provider networks in the therpad is testiment to this15:05
mattmceuenvadym:  agree, that is a good minimal starting point -- that's basically making people aware of the documentation gap :)15:06
mattmceuen"this page left intentionally blank" kind of thing15:07
piotrrrindeed, that's another sub-item in that agenda point - the vm networking doesn't seem to work out of the box right now for multinode instrunctions.15:07
mattmceuenThere has to be some expectation of op-specific customization.  What would the right level of content be to include in OSH without duplicating ovs / neutron docs?  Obviously 1) calling out that it's a step that needs to happen, 2) linking to the appropriate neutron docs15:09
rwellumI think there's a compromise - the baseline you mentioned last week. It's reasonable that an OSH guide would explain how to get basic networking working to me.15:10
piotrrrat least having (1) would already be a good improvement over what's there now in multinode docs. but if applicable, might as well point to external sources. doesn't matter much. The important part is to communicate that op-specific customization is needed, and maybe some clues as to how to approach it.15:11
mattmceuenThat sounds like a reasonable approach.  I'll add a storyboard item to track the need and capture these thoughts there - we can always fine-tune once we have a PS15:12
portdirectrwellum, can you take this on, as part of your multinode guide work?15:12
rwellumSure happy too.15:13
rwellumAssign it to me if you want mattmceuen15:13
portdirectnice - thats awesome dude15:13
piotrrryup. the big picture I would say, it should be crystal clear what are the points where ops should, or must, plug in their logic to cover op-specific things.15:13
mattmceuencool will do - thanks rwellum15:14
mattmceuenyeah, agree piotrrr.  There's so much magic that you need to call out the places where there is no magic :)15:14
mattmceuenNext15:14
mattmceuen#topic     Loci/Kolla container images not production ready according to https://etherpad.openstack.org/p/openstack-helm-multinode-doc15:15
*** openstack changes topic to "Loci/Kolla container images not production ready according to https://etherpad.openstack.org/p/openstack-helm-multinode-doc (Meeting topic: openstack-helm)"15:15
mattmceuenTo paste in Pete:15:15
mattmceuen    As they are built in openstack-infra using unsigned packages15:15
mattmceuen    We dont want to advertise somthing as prodution ready unless we can support them with the respect `production ready` deserves15:15
mattmceuen    CVE tracking etc15:15
rwellumConfused, same images Kolla calls production ready?15:15
piotrrrOSH is using kolla/loci images. kolla/loci images are not production ready. OSH in 1.0.0 will continue using those images. Will that mean that OSH 1.0.0 will *not* be production ready?15:16
mattmceuenOSH will be production ready, and recommends that operators roll their own production ready images for prod use15:16
srwilkers^15:16
piotrrrperfect, that answers my question. Is there a plan to have any docs on how a op can start with creating those?15:17
portdirectrwellum: when did koll start calling the images to dockerhub production ready?15:17
mattmceuenOr at minimum, snapshot a tested, integrated set of images so that the operator can control their destiny15:17
mattmceuenThis is another instance where we should reference out to the kolla/loci build process, I think, piotrrr - I'll add it to the list15:18
rwellumIts their mission statement: "Kolla’s mission is to provide production-ready containers and deployment tools for operating OpenStack clouds."15:19
*** felipemonteiro_ has quit IRC15:19
rwellumSo they haven't accomplished their mission I guess? :)15:19
*** felipemonteiro_ has joined #openstack-meeting-515:19
portdirectthey provide the ability to build production ready containers15:20
rwellumAnd Kolla-Ansible is used in production in many places15:20
piotrrrdo Loci images aspire to be production ready at some point?15:20
portdirectthe ones to dockerhub are like us (unless thomthing radical has changed) for dev and evaluation only15:20
piotrrror do they plan to remain used primarly for dev purposes?15:20
portdirectboth Kolla and LOCI are production ready15:20
rwellumportdirect: you're contradicting yourself?15:21
portdirectno15:21
*** felipemonteiro has joined #openstack-meeting-515:22
portdirectyou can use kolla, and loci to build images for prodution15:22
srwilkershe's saying they provide the toolsets to build production ready images15:22
srwilkersnot that their default, publicly available images are production ready15:22
mattmceuenThe containers on github are "reference builds", right - not the images intended to be deployed in a true prod setting?15:22
portdirectboth publish images to dockerhub, but the images on dockerhub are not recommend for production15:22
mattmceuen*dockerhub15:22
rwellumEven the images that are built from stable OpenStack releases?15:22
portdirectyes15:23
mattmceuenIt's a subtle point, and I'll try to capture it in our doc to avoid misreading it as "Kolla and LOCI are not production ready"15:23
portdirectyou know the kolla images on dockerhub, were for a long time built from an insecure pc in my office?15:23
piotrrrAlright. Thanks, portdirect. I guess that explains it. All of the above should be made clear somewhere in the OSH docs I would say.15:24
*** felipemonteiro_ has quit IRC15:24
rwellumI knew it was in someone's office :). But I thought since the infrastructure moved to OpenStack, and the level of testing they go through - ensured a certain quality now.15:24
portdirectit does, but openstack infra does not sign packages etc15:24
portdirectgreat for dev15:25
portdirectnot for PCI compliance etc15:25
rwellumOk - I'm caught up.15:25
rwellumBe cool to ask this question on kolla irc15:26
mattmceuenAlright - next up:15:26
mattmceuen#topic Support multi versions of Rally - Let's have some time to think about it and discuss again next week.15:26
*** openstack changes topic to "Support multi versions of Rally - Let's have some time to think about it and discuss again next week. (Meeting topic: openstack-helm)"15:26
mattmceuenThere is some good discussion on this in the agenda, https://etherpad.openstack.org/p/openstack-helm-meeting-2018-06-26  if anyone wants to catch up15:26
mattmceuenSo the idea of tuning rally tests in `helm test` scenarios to be portable across different openstack versions resonates with me15:29
mattmceuenas it's straightforward, and `helm test` is not intended to be a thorough functional test, but rather a sanity test to ensure the deployment was successful15:29
mattmceuenThoughts?  This was copied from last time, so I'm not sure who brought it up to begin with15:31
portdirecti added a few inline15:32
*** felipemonteiro has quit IRC15:32
*** felipemonteiro has joined #openstack-meeting-515:32
*** felipemonteiro_ has joined #openstack-meeting-515:33
*** gagehugo has joined #openstack-meeting-515:34
*** felipemonteiro has quit IRC15:37
rwellumHow does this relate to the 'multiple versions' aspect?15:37
mattmceuenI think Jay brought up the topic from last time - portdirect's responses inline should be good to see, I'll shoot them to jayahn to catch up on15:39
mattmceuenrwellum in which sense?15:40
*** ricolin has joined #openstack-meeting-515:42
rwellumIs it multiple versions of rally or multiple versions of OpenStack - reading the etherpad and it's not clear15:42
portdirectwhich it are we talking about here?15:43
rwellumThe title is: "Support multi versions of Rally"15:43
rwellumI just don't see that in the discussion15:44
rwellumMaybe just missing the point?15:44
portdirectlines 31-35?15:45
mattmceuenThe point being that supporting multiple versions of openstack implies needing to support different variants of Rally (code and/or configuration)15:46
mattmceuenAnd how can we best approach that without having to go so far as to branch OSH per openstack release, and instead rely on thing like overrides or Rally tests that run across versions15:47
mattmceuenI shot it to Jay, we can bring it up again next time if he has any thoughts or concerns15:47
portdirecti think the point you raise though re helm test is critical here15:47
mattmceuenThen I'll add it into the etherpad :)15:48
portdirectin that for our purpose 0.8 is actually fine15:48
portdirectthough dont get me wrong, im not happy with that as an answer15:48
portdirectand we should strive to support rally/tempest ootb right up to master as well for helm test15:49
mattmceuenDefinitely15:49
mattmceuen#topic PS needing review15:49
*** openstack changes topic to "PS needing review (Meeting topic: openstack-helm)"15:49
mattmceuenOk folks - any languishing PS that you'd like to request eyes on?15:50
roman_gyours with docs update15:50
mattmceuen:)15:50
roman_go/15:50
mattmceuenI still need to push more changes to that, that's why I'm not pushing it hard - but I will get those done this week.  Thx roman_g15:51
mattmceuenHas been a week15:51
roman_gokok15:51
mattmceuen#topic Roundtable15:51
*** openstack changes topic to "Roundtable (Meeting topic: openstack-helm)"15:51
mattmceuenAnything else on y'alls minds?15:51
piotrrrAre you guys coming over to the berlin summit?15:53
mattmceuenThat is the plan, yes :)15:53
mattmceuenYou?15:53
piotrrryup, we will be there15:53
mattmceuenawesome15:53
mattmceuenAlright everyone, thanks for your time and your effort!15:55
mattmceuenHave a great day & week15:55
mattmceuen#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:55
openstackMeeting ended Tue Jun 26 15:55:36 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-26-14.59.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-26-14.59.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-26-14.59.log.html15:55
*** piotrrr has quit IRC15:55
*** gagehugo has left #openstack-meeting-516:04
*** ricolin has quit IRC16:33
*** yamahata has joined #openstack-meeting-516:57
*** derekh has quit IRC16:58
*** wxy| has quit IRC17:04
*** yamamoto has quit IRC17:12
*** felipemonteiro_ has quit IRC17:14
*** felipemonteiro_ has joined #openstack-meeting-517:14
*** yamamoto has joined #openstack-meeting-517:14
*** yamamoto has quit IRC17:20
*** slaweq has quit IRC17:40
*** felipemonteiro__ has joined #openstack-meeting-517:44
*** felipemonteiro_ has quit IRC17:48
*** felipemonteiro__ has quit IRC17:49
*** felipemonteiro__ has joined #openstack-meeting-517:49
*** felipemonteiro has joined #openstack-meeting-517:53
*** felipemonteiro__ has quit IRC17:54
*** felipemonteiro has quit IRC18:01
*** felipemonteiro has joined #openstack-meeting-518:01
*** felipemonteiro_ has joined #openstack-meeting-518:08
*** felipemonteiro has quit IRC18:11
*** yamamoto has joined #openstack-meeting-518:16
*** yamamoto has quit IRC18:20
*** yamamoto has joined #openstack-meeting-518:21
*** slaweq has joined #openstack-meeting-518:34
*** jgu_ has quit IRC18:46
*** jgu has joined #openstack-meeting-518:47
*** vadym has quit IRC18:54
*** felipemonteiro_ has quit IRC19:15
*** slaweq has quit IRC19:15
*** felipemonteiro has joined #openstack-meeting-519:19
*** slaweq has joined #openstack-meeting-519:24
*** slaweq has quit IRC19:52
*** jgu has quit IRC20:17
*** jgu has joined #openstack-meeting-521:03
*** felipemonteiro has quit IRC21:10
*** mjturek has quit IRC21:11
*** jgu has quit IRC21:29
*** felipemonteiro has joined #openstack-meeting-522:10
*** felipemonteiro_ has joined #openstack-meeting-522:12
*** felipemonteiro has quit IRC22:12
*** felipemonteiro__ has joined #openstack-meeting-522:13
*** felipemonteiro_ has quit IRC22:17
*** jgu has joined #openstack-meeting-522:21
*** hongbin has quit IRC22:36
*** felipemonteiro__ has quit IRC23:01
*** jgu has quit IRC23:03
*** jgu has joined #openstack-meeting-523:04
*** mjturek has joined #openstack-meeting-523:35
*** mjturek has quit IRC23:54
*** mjturek has joined #openstack-meeting-523:57

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