13:01:09 #startmeeting Container SIG 13:01:09 Meeting started Mon Nov 19 13:01:09 2018 UTC. 13:01:09 This meeting is logged and archived in a public location. 13:01:09 The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:01:09 The meeting name has been set to 'container_sig' 13:01:25 #topic Roll Call 13:01:48 Anybody there for the Container SIG meeting :) ? 13:02:22 .hello2 13:02:23 bhavin192: bhavin192 'Bhavin Gandhi' 13:02:29 cverna, hello o/ 13:02:43 bhavin192: o/ 13:02:53 #chair bhavin192 13:02:53 Current chairs: bhavin192 cverna 13:03:01 .hello2 jcajka 13:03:02 jcajka: jcajka 'None' 13:03:10 #chair jcajka 13:03:10 Current chairs: bhavin192 cverna jcajka 13:03:33 ttomecek: jlanda Container SIG meeting in on if interested :) 13:04:07 .hello2 13:04:08 ttomecek: ttomecek 'Tomas Tomecek' 13:04:16 #chair ttomecek 13:04:16 Current chairs: bhavin192 cverna jcajka ttomecek 13:04:22 #topic Updates since last meeting 13:04:37 jcajka++ for running the last meeting 13:05:00 cverna: np 13:05:12 I don't have much update on my side, except that I am still working to get aarch64 cluster for OSBS 13:05:25 and we have bodhi updates available for contianers :) 13:05:38 * jcajka hopes it is going well 13:05:52 cverna: if you need any help let me know 13:06:40 jcajka: sure for now I am blocked by some firewall rules, hopefully that will be solved this week 13:07:15 Anybody else has some updates ? or should we look a tickets ? 13:07:21 cverna, so the contaainer updates via bodhi work fine? 13:07:55 ttomecek: yes, and a PR for fedpkg was merged this morning so next version of fedpkg will support it 13:08:14 awesome! 13:08:28 no updates for our sig devconf session yet 13:08:30 one remark was given on devel about the build nvr 13:08:48 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SRUFZNXNGRZHHTO6FSYGMR2ZVHQWEY6Z/ 13:09:32 If the container has the same name as the rpm we use the same nvr and OSBS will bump the release number, so that can mess up the rpm builds 13:10:22 I am not sure yet how to fix this, but I can open a ticket in our tracker and we can look at it there 13:11:18 cverna, the easiest solution is probably to rename the component, not sure if that's a good idea; +1 on opening the ticket 13:11:39 I ll create the ticket after this meeting 13:12:11 #topic Tickets 13:12:29 quick note from me, if anybody have spare time I will much appreciate a review of any on the https://tinyurl.com/yarw3y2g (now they all should build as latest origin update hit stable), i will be happy to review back(preferring containers and Go packages;)) 13:12:30 #topic Remove the $FGC from the container name https://pagure.io/ContainerSIG/container-sig/issue/2 13:12:52 jcajka: I ll give it a look 13:13:06 jcajka: oh man that's a big list :) 13:13:21 just a few containers ;D 13:13:54 so about issue 2 --> https://pagure.io/ContainerSIG/container-sig/issue/2 13:14:01 I have some news 13:14:18 I finally manage to build a container using OSBS custom tag feature 13:14:36 https://koji.stg.fedoraproject.org/koji/buildinfo?buildID=1157701 13:15:49 hum src.fp.o is odd in stg 13:16:50 so by using a container.yaml file in dist git we can set the tags used during the build 13:16:53 see https://paste.fedoraproject.org/paste/BVRSDBs2o2fUZekSH5DMFg 13:17:09 that was we will not have the latest tag applied to every build 13:18:43 cverna: awesome, and latest will set by bodhi or by the thing that pushes it in to the stable registry? 13:19:24 cverna: i'm on another meeting 13:19:25 jcajka: yes bodhi will first set a testing tag, then create a latest tag once the update is pushed to stable 13:19:34 jlanda: np enjoy :) 13:20:10 cverna, that's pretty good! that should also address the problem with automatic tagging on images based on RPM versions inside, to some extent 13:20:45 hopefully we should be able to move to quay.io early next year, so I think this will be a good opportunity to drop the namespacing 13:21:36 I ll add some info in the ticket and we can start working on updating the guidelines ( ie how to use the container.yaml file) 13:22:04 +1 13:22:11 So it would be like container-image:version-tag and we won't have this tied to a specific version of Fedora, right? 13:22:40 yes 13:23:16 or just container:latest which should use the latest fedora base image 13:24:53 Anything else on this ticket ? 13:26:30 Ok moving on to next ticket 13:26:58 #topic Bodhi Container Update Policy https://pagure.io/ContainerSIG/container-sig/issue/19 13:28:49 cverna, what's the intent? 13:29:49 so currently we have the same settings as for rpms on container updates, I think these policies are not well defined for containers 13:30:39 ie for a update to move from container-image:testing tag to container-image:latest we currently need either +3 karma or 7 days in testing 13:30:40 cverna, so you want container images to be more relaxed? 13:30:49 ttomecek: yes :) 13:31:08 I think we could ask for no karma and maybe 2-3 days in testing 13:31:31 keeping in mind that we will also have CI and gating for containers 13:31:34 cverna, what's the status of container testing? last time I checked, I saw some infra-related errors 13:31:52 cverna, +1, 2-3 days 13:31:58 cverna: IMO +3 karma for auto-push or 2-3days 13:32:10 and no negative karma 13:32:10 ttomecek: I have not checked in a while :( 13:32:43 ttomecek: jcajka can you add your proposal on the ticket, then we can find a consensus and make a fesco ticket 13:33:07 cvernaL sure 13:33:15 cverna 13:33:48 Also it is to be noted that for container depending on other layered image as base image, you should be able to use the testing tag during the OSBS build 13:34:58 I am not sure we want to recommend that, but that's a way for not having to wait 3 days before building the containers 13:36:17 cverna: it would be great to have some equivalent to buildroot override so we can create batched(multiple image) updates 13:37:21 jcajka: yes it is on bodhi roadmap, and Randy had some though about it already 13:37:29 but not sure when this will happen 13:38:09 ack, I will comment in to the thicket with that on my mind 13:38:11 * cverna thinks that we CI + automatic update we would already have a good solution 13:38:52 #topic Open Floor 13:39:17 Anything else to add ? 13:39:42 (not from me, good progress!) 13:40:02 nothing else from me 13:40:49 ok thanks all for coming :) 13:41:09 cverna++ thank you for organizing the meeting! and thank you all for updates 13:41:10 and talk to you in 2 weeks 13:41:21 #endmeeting