| *** slaweq has joined #openstack-meeting-5 | 00:11 | |
| *** slaweq has quit IRC | 00:16 | |
| *** hongbin has quit IRC | 01:00 | |
| *** ianychoi has quit IRC | 01:20 | |
| *** yamahata has quit IRC | 03:23 | |
| *** iyamahat_ has joined #openstack-meeting-5 | 03:40 | |
| *** iyamahat has quit IRC | 03:44 | |
| *** iyamahat_ has quit IRC | 03:50 | |
| *** markvoelker has joined #openstack-meeting-5 | 03:57 | |
| *** markvoelker has quit IRC | 04:02 | |
| *** slaweq has joined #openstack-meeting-5 | 04:30 | |
| *** trident has quit IRC | 07:42 | |
| *** trident has joined #openstack-meeting-5 | 07:44 | |
| *** radeks has joined #openstack-meeting-5 | 07:53 | |
| *** yamahata has joined #openstack-meeting-5 | 08:19 | |
| *** ralonsoh has joined #openstack-meeting-5 | 08:29 | |
| *** lemko has joined #openstack-meeting-5 | 08:33 | |
| *** derekh has joined #openstack-meeting-5 | 09:36 | |
| *** iyamahat has joined #openstack-meeting-5 | 10:41 | |
| *** sgrasley has joined #openstack-meeting-5 | 13:59 | |
| *** howell has joined #openstack-meeting-5 | 14:41 | |
| srwilkers | #startmeeting openstack-helm | 15:00 |
|---|---|---|
| openstack | Meeting started Tue Dec 11 15:00:18 2018 UTC and is due to finish in 60 minutes. The chair is srwilkers. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: openstack-helm)" | 15:00 | |
| openstack | The meeting name has been set to 'openstack_helm' | 15:00 |
| srwilkers | heya -- portdirect is running a bit late, so i'm going to kick things off for him | 15:00 |
| srwilkers | #topic rollcall | 15:00 |
| *** openstack changes topic to "rollcall (Meeting topic: openstack-helm)" | 15:00 | |
| srwilkers | o/ | 15:00 |
| *** markvoelker has joined #openstack-meeting-5 | 15:00 | |
| evrardjp | o/ (because I can't really \o/) | 15:00 |
| mattmceuen | o/ | 15:01 |
| srwilkers | if you turn in a circle really quick evrardjp, a o/ can become a \o/ | 15:01 |
| srwilkers | but you have to be really quick | 15:01 |
| srwilkers | lets give it a few minutes to let people trickle in -- also, here's the etherpad for today: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-12-11 | 15:01 |
| srwilkers | seeing some good stuff on here | 15:01 |
| evrardjp | srwilkers: :) | 15:02 |
| howell | o/ | 15:03 |
| jayahn | o/ | 15:04 |
| srwilkers | alright, let's get started | 15:05 |
| srwilkers | #topic gate refactor | 15:05 |
| *** openstack changes topic to "gate refactor (Meeting topic: openstack-helm)" | 15:05 | |
| srwilkers | first thing -- we've talked about getting periodic gates going in the past. we're at the point we should get that started | 15:05 |
| srwilkers | i've admittedly not set one up before, and i think evrardjp had some great ideas about what these would look like back in Denver | 15:06 |
| srwilkers | have any thoughts here evrardjp? | 15:06 |
| evrardjp | well it's quite simple, dailies are a simple job that runs on a specific pipeline | 15:06 |
| evrardjp | named "periodic" | 15:07 |
| evrardjp | those jobs can be extended in terms of length. | 15:07 |
| evrardjp | (I mean runtime) | 15:07 |
| evrardjp | There two things to figure out there: | 15:07 |
| evrardjp | 1) What will be the content of those (extending the current job to increase coverage is good!) | 15:08 |
| evrardjp | 2) Who will be monitoring those | 15:08 |
| evrardjp | The second point is by far more important: | 15:08 |
| evrardjp | If we have jobs that nobody monitors, there is almost 0 point of doing so. | 15:08 |
| evrardjp | it's easy for people to forget those periodics. | 15:09 |
| srwilkers | yeah, that's what i was thinking as well. ive typically got zuul.openstack.org up on my screen at all times (at home and at work), but that's just me. we'd certainly need to treat these as first class and not ignore them | 15:09 |
| *** jamesgu_ has joined #openstack-meeting-5 | 15:10 | |
| evrardjp | There is no pipeline yet for weeklies. We could have a job that skips when not on the week-end for example. But I will work with infra to see if it's possible to create a week periodic pipeline. | 15:10 |
| srwilkers | that'd be awesome | 15:10 |
| evrardjp | However, I don't think we should make use of such pipeline, as daily seems enough for OSH cases | 15:10 |
| evrardjp | srwilkers: do you have a specific idea of things that should run every week but not every day? | 15:11 |
| srwilkers | yeah -- i was thinking weekly would probably be good for something like the old armada job we ran | 15:11 |
| srwilkers | or some other sort of big bang integration run | 15:11 |
| evrardjp | k | 15:12 |
| srwilkers | but daily should really be enough for what we need | 15:12 |
| srwilkers | and i think pete's comment about the "big and fat" old jobs could possibly be a good start there | 15:12 |
| srwilkers | or some subset of those | 15:12 |
| jayahn | +1 on armada job - probably good candidate for it | 15:13 |
| evrardjp | srwilkers: could you clarify what those are? | 15:14 |
| evrardjp | Is that the regular folder's jobs? (running everything in multinode for example) | 15:14 |
| srwilkers | the old multinode jobs we ran previously (the five node jobs) | 15:14 |
| srwilkers | yeah | 15:15 |
| evrardjp | I see. | 15:15 |
| srwilkers | that could at least get us started, and we could modify those as needed/required moving forward | 15:16 |
| evrardjp | I have to check what was done/merged recently though, to ensure I am not re-inventing the wheel. | 15:17 |
| srwilkers | evrardjp: of course :) | 15:17 |
| evrardjp | (when implementing those new jobs) | 15:17 |
| evrardjp | I will probably dropped my old efforts then :'( | 15:17 |
| evrardjp | I don't have anything to add | 15:18 |
| evrardjp | srwilkers: do you plan to talk about the refactor and its potential issues, if I am not mistaken? | 15:19 |
| srwilkers | another item possibly related to the refactor is a failure in part of the script we used to exercise the stack | 15:19 |
| srwilkers | evrardjp: took the words out of my mouth | 15:19 |
| srwilkers | ie: https://review.openstack.org/#/c/623218/ | 15:19 |
| srwilkers | the latest failure for the compute-kit gate ran fine, up until we attempted to ssh into the vm we launch and curl the keystone endpoint | 15:20 |
| srwilkers | http://logs.openstack.org/18/623218/6/check/openstack-helm-compute-kit/f1143fa/job-output.txt.gz#_2018-12-07_17_42_36_020311 | 15:20 |
| srwilkers | i had planned to do some digging here today, but that's the only issue i've noticed bubble up so far | 15:20 |
| evrardjp | thanks srwilkers for the work, the debugging, and the fix ! :) | 15:22 |
| srwilkers | evrardjp: don't thank me. this was just a by-product of the conversations you helped drive in Denver :) | 15:23 |
| srwilkers | that's all i had to talk about wrt the gates. anybody else have anything? | 15:23 |
| mattmceuen | Not I! | 15:25 |
| evrardjp | I have nothing | 15:25 |
| srwilkers | #topic image builds | 15:26 |
| *** openstack changes topic to "image builds (Meeting topic: openstack-helm)" | 15:26 | |
| srwilkers | i'll just quickly touch on the point portdirect left here, then let jayahn and evrardjp chime in | 15:26 |
| evrardjp | I guess two big things need to happen there | 15:27 |
| srwilkers | there was some chat in the openstack-helm channel today about portdirect getting things squared away for us to be able to push images, so there's a path forward there | 15:27 |
| srwilkers | evrardjp: yep :) take it away | 15:27 |
| evrardjp | 1) Work on the new repos -- 2) Clean the old ones | 15:28 |
| evrardjp | I put numbers there, because I'd hope we start 2) only after 1) is fully done | 15:28 |
| evrardjp | To talk about 1) -- A few elements need happening | 15:28 |
| evrardjp | Include LOCI's image building into this new repo (WIP, only a few minor details are remaining) | 15:29 |
| evrardjp | Include proper logging of the building | 15:29 |
| evrardjp | Publish images | 15:29 |
| evrardjp | Be able to release images (so in other words... be able to "version" images in a nicely fashion, for 1.0 for example) | 15:30 |
| evrardjp | Then last step would be be able to consume said images into the other repos' charts. | 15:31 |
| evrardjp | Does that sound correct? | 15:31 |
| srwilkers | that seems sane to me | 15:32 |
| evrardjp | A stretch goal would be to be able to test images separately. | 15:32 |
| evrardjp | For all those above I am looking for help, and I hope a few SUSE people will step in the process :) | 15:32 |
| evrardjp | The last one (test images separately) is the trickiest for me, as I have no idea on where to start. | 15:33 |
| srwilkers | evrardjp: i'll be happy to jump in and help there. i'll take a look to see where i can start getting my hands dirty | 15:33 |
| evrardjp | Call for help is made, I leave the mic to other people now :) | 15:33 |
| evrardjp | srwilkers: we have docs :) | 15:33 |
| srwilkers | jayahn: i see you've got quite a few items here. floors yours | 15:33 |
| evrardjp | I think all of those patches should be into the same topic (I don't have the topic name yet, but will think about it) | 15:34 |
| jayahn | situation #1. skt has been deveoping charts to enable lbaas and fwaas, with kolla image. To upstream these charts, skt knows charts should pass gates using loci images. That loci part has been a big blocker for us. | 15:35 |
| jayahn | situation #2. skt ci pipeline currently detects any changes in values (regarding images, any tag changes or new image). skt has been replacing loci-based image values to kolla-based image values. | 15:35 |
| jayahn | Additionally, skt knows osh proejct will have loci-based gates only. that is totally understandable. | 15:35 |
| jayahn | based on situation #1, situation #2, skt need osh cores guide, opinion, or discussion,. | 15:35 |
| jayahn | skt can provide information on how to make osh charts work with kolla-image for anyone who wants to use kolla-images. it won't have gates, but we can always provides "any type of documents" for reference information. >> will it be valuable for osh project? | 15:35 |
| jayahn | in contrary, skt really needs help on loci image. how we can properly set / build loci image so that we can uptream our charts. can anyone help us to set up loci images? | 15:36 |
| srwilkers | i'll admit, i'm by no means an expert with the LOCI build process. but we've added added required packages to the LOCI images before (things like the fluent handler for oslo.log come to mind) | 15:37 |
| jayahn | or we can even publish kolla-images we are building internally. >> will it provide any value for osh project? | 15:37 |
| evrardjp | I am no core but please allow me to give my opinion | 15:39 |
| srwilkers | evrardjp: of course | 15:39 |
| jayahn | sure | 15:39 |
| srwilkers | jayahn: for what its worth though, we've got other charts that use kolla images currently (ceilometer comes to mind) | 15:39 |
| evrardjp | I don't think it's a good idea to extend too much the amount of different image build process that will be included in osh repositories. So I'd say, do not focus on adding more images if there are any existing images that match your purpose | 15:40 |
| evrardjp | Second, I'd say -- if you want to upstream a chart based on image x, you should be able to allow any deployer to use image y. | 15:41 |
| evrardjp | should (s)he want to be alone, let him/her/it be :) | 15:41 |
| evrardjp | portdirect: should talk about the necessity of building with LOCI to get an upstream chart in, but I don't believe it must be a necessity | 15:42 |
| evrardjp | myself | 15:42 |
| evrardjp | (that's for situation 1) | 15:42 |
| evrardjp | for situation 2: I would strongly hope that changes in values would be documented throught the help of anything (including release notes). This is now the "API" of the project, according to me | 15:43 |
| evrardjp | point 3) Documenting what needs to be done for using kolla images vs LOCI images is good -- I think that's a valid "user story" | 15:44 |
| evrardjp | should someone want to run with its own images, he could, by following the documentation | 15:44 |
| jayahn | FYI, replacing loci base images into kolla-based one is not 1:1 mapping. (as you probably knows). for loci, it is neutron, for kolla, it will be multiple images, neutron-api, neutron-server, .... sometimes can be tricky. :) | 15:45 |
| evrardjp | and last point -- I am sure the people in #openstack-loci can help you with the building of the images :D | 15:45 |
| jayahn | evrardjp: #openstack-loci it is. :) | 15:45 |
| srwilkers | i think engaging individuals in LOCI would be the best path forward | 15:46 |
| jayahn | for us, any effort we are putting on loci, is purely for upstream contribution. we are willing to do it, but really needs some help to shorten our trial and errors. :) | 15:47 |
| evrardjp | I think the OSH should keep its DNA of being "image independant", but still provide "reference" images that help do the things with minimum value overrides basically | 15:47 |
| evrardjp | there is already an octavia image btw :) | 15:48 |
| jayahn | so one additional document entry: reference information when you want to use kolla images. | 15:48 |
| jayahn | evrardjp: we found out that, we are currently testing with octavia loci image. :) | 15:48 |
| evrardjp | if you don't mind I would prefer a different title | 15:48 |
| evrardjp | "How to bring your own images" | 15:48 |
| jayahn | that can work. | 15:48 |
| evrardjp | assuming you're not using kolla, how would you do? (for example you build your own with Dockerfiles, or ansible, or dib...) | 15:49 |
| evrardjp | I think a practical example with Kolla would be great though, as you have the content | 15:49 |
| jayahn | evrardjp: you need to completely modify "images section in value.yaml" to meet with your images. | 15:50 |
| jayahn | currently, images keys are compatible with kolla-images, that is why, it is easy for us to set kolla-based images. | 15:50 |
| jayahn | if you build your own stuff, you need to changes everything, not only values, but also keys | 15:51 |
| evrardjp | all of it is worth documenting, IMO :) | 15:51 |
| jayahn | yeap. | 15:51 |
| srwilkers | agreed | 15:52 |
| srwilkers | anything else on this topic? we've got about 7 minutes left | 15:52 |
| evrardjp | none | 15:52 |
| srwilkers | jayahn? | 15:53 |
| evrardjp | "help needed" | 15:53 |
| jayahn | one additional question, if we would like to build loci images for osh chart, would we contribute it to osh-images-repo? | 15:53 |
| evrardjp | yes | 15:53 |
| portdirect | jayahn: yup | 15:53 |
| srwilkers | jayahn: yeah, that makes sense | 15:53 |
| jayahn | okay | 15:53 |
| evrardjp | seems portdirect srwilkers and I are aligned -- doomsday is near | 15:54 |
| srwilkers | :o | 15:54 |
| srwilkers | #topic storyboard | 15:54 |
| *** openstack changes topic to "storyboard (Meeting topic: openstack-helm)" | 15:54 | |
| jayahn | only three aligned, no doomsday yet | 15:54 |
| evrardjp | :) | 15:55 |
| srwilkers | just a quick touch here -- i know portdirect is still working on reviewing whats in storyboard | 15:55 |
| portdirect | but whats there to date - should be good to get going on as its leading towards the 1.0.0 release | 15:55 |
| *** markvoelker has quit IRC | 15:55 | |
| evrardjp | great! | 15:56 |
| portdirect | in particular we really need to get the docs and helm driven tests in shape | 15:56 |
| *** markvoelker has joined #openstack-meeting-5 | 15:56 | |
| portdirect | (sorry ive not caught up on scrollback - so may be rehashing things) | 15:56 |
| evrardjp | (maybe worth giving a link for the record?) | 15:56 |
| srwilkers | https://storyboard.openstack.org/#!/worklist/341 | 15:56 |
| portdirect | I'd say for people looking to get invovled this would be a great place to start | 15:57 |
| portdirect | evrardjp: it would be great to see some helm tests for services that dont have coverage atm | 15:57 |
| portdirect | as it would really help validate multi distro support amongst other things | 15:58 |
| portdirect | jayahn: i know that we need to give more attention to docs than we have recently | 15:58 |
| portdirect | do you have the bandwidth to enage there atm? | 15:59 |
| portdirect | *engage | 15:59 |
| evrardjp | portdirect: agreed on the helm tests. | 15:59 |
| srwilkers | we've got less than a minute | 15:59 |
| srwilkers | let's take this to #openstack-helm | 15:59 |
| evrardjp | I will although focus on the image building steps to get all of this out of the door. Maybe I should all of those into storyboard too? | 15:59 |
| srwilkers | thanks for coming everyone | 15:59 |
| evrardjp | thanks srwilkers ! | 15:59 |
| srwilkers | #endmeeting | 15:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:59 | |
| openstack | Meeting ended Tue Dec 11 15:59:58 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-12-11-15.00.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-12-11-15.00.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-12-11-15.00.log.html | 16:00 |
| jayahn | portdirect: yeah, jaesang has been actively looking into it from this week, i will get that as the first priority for the last of this year. | 16:00 |
| portdirect | jayahn: aweseome, i know its been party season over in sk ;D | 16:00 |
| *** markvoelker has quit IRC | 16:01 | |
| *** nzoueidi has quit IRC | 16:02 | |
| *** nzoueidi has joined #openstack-meeting-5 | 16:04 | |
| *** howell has quit IRC | 16:09 | |
| *** jamesgu_ has quit IRC | 16:15 | |
| *** hongbin has joined #openstack-meeting-5 | 16:19 | |
| *** jamesgu_ has joined #openstack-meeting-5 | 16:19 | |
| *** jamesgu__ has joined #openstack-meeting-5 | 17:35 | |
| *** jamesgu_ has quit IRC | 17:39 | |
| *** ralonsoh has quit IRC | 17:46 | |
| *** yamahata has quit IRC | 18:00 | |
| *** derekh has quit IRC | 18:00 | |
| *** iyamahat has quit IRC | 18:01 | |
| *** iyamahat has joined #openstack-meeting-5 | 18:17 | |
| *** iyamahat has quit IRC | 18:33 | |
| *** yamahata has joined #openstack-meeting-5 | 18:36 | |
| *** iyamahat has joined #openstack-meeting-5 | 18:43 | |
| *** mjturek has joined #openstack-meeting-5 | 18:46 | |
| *** lemko has quit IRC | 19:50 | |
| *** markvoelker has joined #openstack-meeting-5 | 21:45 | |
| *** markvoelker has quit IRC | 21:49 | |
| *** radeks has quit IRC | 22:18 | |
| *** markvoelker has joined #openstack-meeting-5 | 22:24 | |
| *** slaweq has quit IRC | 22:26 | |
| *** slaweq has joined #openstack-meeting-5 | 22:43 | |
| *** slaweq has quit IRC | 22:48 | |
| *** mjturek has quit IRC | 22:51 | |
| *** mjturek has joined #openstack-meeting-5 | 23:10 | |
| *** slaweq has joined #openstack-meeting-5 | 23:14 | |
| *** slaweq has quit IRC | 23:19 | |
| *** jamesgu_ has joined #openstack-meeting-5 | 23:29 | |
| *** jamesgu__ has quit IRC | 23:32 | |
| *** hongbin has quit IRC | 23:34 | |
| *** hongbin has joined #openstack-meeting-5 | 23:35 | |
| *** slaweq has joined #openstack-meeting-5 | 23:35 | |
| *** slaweq has quit IRC | 23:40 | |
| *** hongbin has quit IRC | 23:58 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!