March 2017 - cloud - Fedora mailing-lists

Atomic WG Meeting Minutes 2017-03-01
by Dusty Mabe 15 Mar '17

15 Mar '17

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-15/atomic_wg.201… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-15/atomic_wg.201… ============================ #fedora-meeting-1: atomic_wg ============================ Meeting started by dustymabe at 17:00:32 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-15/atomic_wg.201… . Meeting summary --------------- * action items from last meeting (dustymabe, 17:06:41) * LINK: https://public.etherpad-mozilla.org/p/atomic-host-docs (trishnag, 17:10:10) * ACTION: jberkus to schedule a meeting about support policy, rolling upgrades (dustymabe, 17:11:51) * ACTION: maxamillion to follow-up on fixing ami permissions, links with dgilmore (dustymabe, 17:12:25) * Label/comment for primary RPM? (dustymabe, 17:13:22) * LINK: https://pagure.io/atomic-wg/issue/254 (dustymabe, 17:13:30) * LINK: https://pagure.io/atomic-wg/issue/254#comment-431590 (maxamillion, 17:23:31) * lower case vs Initial Cap in Labels (dustymabe, 17:31:12) * LINK: https://pagure.io/atomic-wg/issue/253 (dustymabe, 17:31:20) * ACTION: maxamillion to verify if we can change case in koji etc., or fix it if we can't (jberkus, 17:38:22) * Container Guidelines: Layered Images used as a base for other Layered Builds (dustymabe, 17:51:43) * LINK: https://pagure.io/atomic-wg/issue/248 (dustymabe, 17:51:50) * clarify policy on atomic host support for older Fedora "number" releases (dustymabe, 17:55:07) * LINK: https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:55:13) * documentation (dustymabe, 17:59:30) * LINK: https://github.com/projectatomic/atomic-host-docs (jberkus, 18:00:17) Meeting ended at 18:07:03 UTC. Action Items ------------ * jberkus to schedule a meeting about support policy, rolling upgrades * maxamillion to follow-up on fixing ami permissions, links with dgilmore * maxamillion to verify if we can change case in koji etc., or fix it if we can't Action Items, by person ----------------------- * jberkus * jberkus to schedule a meeting about support policy, rolling upgrades * maxamillion * maxamillion to follow-up on fixing ami permissions, links with dgilmore * maxamillion to verify if we can change case in koji etc., or fix it if we can't * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (106) * jberkus (87) * maxamillion (34) * zodbot (18) * yzhang (16) * trishnag (15) * roshi (9) * jbrooks (9) * walters (3) * miabbott (3) * bowlofeggs (3) * jdoss (2) * jlebon (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 1

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dennis Gilmore 15 Mar '17

15 Mar '17

ausil merged a pull-request against the project: `fedora-atomic` that you are following. Merged pull-request: `` Updates for f26 repos. `` https://pagure.io/fedora-atomic/pull-request/56

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dusty Mabe 15 Mar '17

15 Mar '17

dustymabe commented on the pull-request: `Updates for f26 repos.` that you are following: `` fine, but i am going to hardcode the release because we it wouldn't make sense considering we are on the f26 branch `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dennis Gilmore 15 Mar '17

15 Mar '17

ausil commented on the pull-request: `Updates for f26 repos.` that you are following: `` lets not use hard coded arches anywhere please. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
by Josh Berkus 15 Mar '17

15 Mar '17

jberkus added a new comment to an issue you are following: `` For FLIBS labels: @maxamillion to verify that we can use lower-case labels in koji/osbs. If not, to add backwards-compatibility code so that we can. Rest of team to update Container Guidelines to use lower case. For Atomic CLI labels: Opening issue against Atomic CLI. For right now, do not change labels. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/253

1 0

[atomic-wg] Issue #251 `Advise users that updates/ ref should be deleted`
by Colin Walters 15 Mar '17

15 Mar '17

walters added a new comment to an issue you are following: `` I personally didn't like the idea of blogging this on projectatomic.io since it's kind of advertising an "oops". I can write up something for atomic(a)projectatomic.io though. Ideally someone would be able to find it via Google but that's hard. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/251

1 0

[atomic-wg] Issue #251 `Advise users that updates/ ref should be deleted`
by Dusty Mabe 15 Mar '17

15 Mar '17

dustymabe added a new comment to an issue you are following: `` @jlebon - do you think you could draft a statement? Some of the details aren't so clear to me. I know there is an extra ref laying around and that means things won't get cleaned up when they should --> out of space issues. Do you mind writing something up? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/251

1 0

I am on PTO today
by Kushal Das 15 Mar '17

15 Mar '17

Hi, I am on leave today. For the rest of the week, I will be attending FOSSASIA 2017 in Singapore. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

1 0

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`
by Jason Brooks 15 Mar '17

15 Mar '17

jasonbrooks added a new comment to an issue you are following: `` I made some edits (I made them in a google doc and sent you the link if you want that): === systemd-Based Containers === A systemd-based container runs systemd(/usr/bin/init) by default as its entrypoint. One or more services are configured using unit files, the say way they would be on a physical system or a virtual machine. systemd based containers have some advantages over running a service directly as the entrypoint (pid 1): Support for multi service containers. Support for unit file mechanism for starting the container. Ability to reap zombie processes. Population of /tmp with content needed to be run by a service Proper handling of syslog messages Proper handling of journalctl messages ==== Issues with systemd based containers ==== STDOUT/STDERR of the container does not come back though the container runtime logging system. systemd adds some requirements on the mechanism that containers are run: systemd requires that a tmpfs be mounted at /run. systemd requires that /sys/fs/cgroup be available inside of the container systemd requires that the signal to stop the container is SIGRTMIN+3 systemd likes if /tmp is a tmpfs. For more information on systemd in a container read this link. https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-priv… ==== LABELS ==== Run/Usage: Installing the oci-systemd-hook and oci-register-machine packages alongside the docker packaged shipped in Fedora takes care of most of the setup for running a systemd container. However, in order to provide compatibility with other container hosts, systemd-based containers should include a Run or Usage label that directs users to include the "--tmpfs /run", "--tmpfs /tmp", and "-v /sys/fs/cgroup:/sys/fs/cgroup" that systemd requires to run. For example: <pre> LABEL Usage="docker run -d -P --tmpfs /run --tmpfs /tmp -v /sys/fs/cgroup:/sys/fs/cgroup SYSTEMDIMAGE" </pre> Note: On a container host without oci-systemd-hook and oci-register-machine, log files will not appear on the host, since there’ll be no way to make the logs available outside of the container. ==== CMD/ENTRYPOINT ==== systemd-based containers must include "/sbin/init" as an ENTRYPOINT or CMD, which will start systemd inside the container at run time. systemd will start up and manage services enabled with the Dockerfile using the standard "systemctl enable foo" commands in RUN statements. For example: <pre> FROM fedora:25 ENV container=oci RUN dnf -y install httpd; dnf clean all; systemctl enable httpd STOPSIGNAL SIGRTMIN+3 EXPOSE 80 CMD [ "/sbin/init" ] </pre> Fedora now also provides a base-init container called fedora-init. This image is setup to running systemd containers by default. This means your Dockerfile could be as simple as <pre> FROM fedora-init:25 RUN dnf -y install httpd; dnf clean all; systemctl enable httpd EXPOSE 80 </pre> `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/233

1 0

notice about daylight savings: meeting at 17:00:00 UTC
by Dusty Mabe 15 Mar '17

15 Mar '17

For those that may be affected by daylight savings. We have elected in the past to keep our meeting at 17:00 UTC. Which means the meeting moves an hour for those who experience daylight savings. For example, I do experience dalight savings so the meeting will be one hour later for me today. Dusty

1 0

[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
by Tomas Tomecek 15 Mar '17

15 Mar '17

ttomecek added a new comment to an issue you are following: `` Lower case, please: https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/mas… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/253

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dusty Mabe 14 Mar '17

14 Mar '17

dustymabe commented on the pull-request: `Updates for f26 repos.` that you are following: `` @ausil, updated to use metalinks `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dusty Mabe 14 Mar '17

14 Mar '17

dustymabe commented on the pull-request: `Updates for f26 repos.` that you are following: `` > rpm-ostree ➡ libdnf ➡ librepo, so it's going to work the same for every libdnf consumer. I thought so. Wasn't sure why it wasn't working for me :( > The bug is you need metalink= instead of baseurl=. In general, we should have a SOP to copy the git repo for fedora-repos. +1 fixed. and I also synced the entries in the file with their counterparts in fedora-repos. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Colin Walters 14 Mar '17

14 Mar '17

walters commented on the pull-request: `Updates for f26 repos.` that you are following: `` rpm-ostree :arrow_right: libdnf :arrow_right: librepo, so it's going to work the same for every libdnf consumer. The bug is you need `metalink=` instead of `baseurl=`. In general, we should have a SOP to copy [the git repo for fedora-repos](https://pagure.io/fedora-repos/blob/f26/f/fedora.repo). `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[fedora-atomic] PR #56 `Updates for f26 repos.`
by Dusty Mabe 14 Mar '17

14 Mar '17

dustymabe commented on the pull-request: `Updates for f26 repos.` that you are following: `` i'm not sure if rpm-ostree supports metalink - I just tried it with metalinks with this file: ``` [fedora-26] name=Fedora 26 - x86_64 failovermethod=priority baseurl=https://mirrors.fedoraproject.org/metalink?repo=fedora-26&arch=x86_… enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-$basearch skip_if_unavailable=False [fedora-26-updates] name=Fedora 26 updates - x86_64 failovermethod=priority baseurl=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f2… enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-$basearch skip_if_unavailable=False [fedora-26-updates-testing] name=Fedora 26 updates testing - x86_64 failovermethod=priority baseurl=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f26… enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-$basearch skip_if_unavailable=False ``` and I get this error: ``` [root@rpm-ostree ~]# rpm-ostree compose tree --repo=/root/repo --cachedir=/sharedfolder/cache/rpm-ostree /sharedfolder/code/pagure.io/fedora-atomic/fedora-atomic-docker-host.json No previous commit for fedora/26/x86_64/atomic-host error: cannot update repo 'fedora-26': repomd.xml parser error: Element <repomd> was not found - Bad repomd file ``` `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/56

1 0

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`
by Jason Brooks 14 Mar '17

14 Mar '17

jasonbrooks added a new comment to an issue you are following: `` How does this look? @dwalsh === systemd-Based Containers === A systemd-based container includes the systemd system and service manager as part of its image in order to run one or more systemd-managed services within a single container, to take advantage of systemd's zombie-reaping capabilities, or to better handle container logging. systemd-based containers' Dockerfiles have the following differences: ==== LABELS ==== Run/Usage: systemd-based containers should include a Run or Usage label that directs users to include "--tmpfs /run", "--tmpfs /tmp", and "-v /sys/fs/cgroup:/sys/fs/cgroup", which systemd requires to run. Container hosts running the default Fedora docker package and the oci-systemd-hook don't require these run options, but they should be included for compatibility with other container hosts. For example: <pre> LABEL Usage="docker run -d -P --tmpfs /run --tmpfs /tmp -v /sys/fs/cgroup:/sys/fs/cgroup -v owncloud-data:/var/lib/owncloud -v owncloud-config:/etc/owncloud owncloud" </pre> ==== CMD/ENTRYPOINT ==== systemd-based containers must include "/sbin/init" as an ENTRYPOINT or CMD, which will start systemd inside the container at run time. systemd will start up and manage services enabled with the Dockerfile using the standard "systemctl enable foo" commands in RUN statements. For example: <pre> FROM fedora:25 ENV container=oci RUN dnf -y install httpd; dnf clean all; systemctl enable httpd EXPOSE 80 CMD [ "/sbin/init" ] </pre> `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/233

1 0

2wk atomic release candidate: 20170314
by Dusty Mabe 14 Mar '17

14 Mar '17

We are going to attempt to release the 20170314 images. These images contain the following ostree version/commit: 25.80 24d4499420ffb2cc49681020bbe5aa6780d780d2b811eab1f5ffea6446b5a4c5 The atomic host VM images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2017031… The ISO image is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2017031… The AMIs are here: Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-northeast-1) ami-b5faa8d2 hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-southeast-1) ami-c8c270ab hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-southeast-2) ami-e0191483 hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (eu-central-1) ami-8401d6eb hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (eu-west-1) ami-42447324 hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (sa-east-1) ami-70e8891c hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-east-1) ami-89f55b9f hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-west-1) ami-30025a50 hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-west-2) ami-d225abb2 hvm standard Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-northeast-1) ami-bff7a5d8 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-southeast-1) ami-9bc270f8 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (ap-southeast-2) ami-11181572 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (eu-central-1) ami-100fd87f hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (eu-west-1) ami-c34473a5 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (sa-east-1) ami-eee98882 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-east-1) ami-44f75952 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-west-1) ami-a6025ac6 hvm gp2 Fedora-Atomic-25-20170314.0.x86_64 EC2 (us-west-2) ami-f029a790 hvm gp2 Cheers! Dusty P.S. The diff between this and the previous released version is: Upgraded: atomic-devmode 0.3.3-1.fc25 -> 0.3.6-1.fc25 bind99-libs 9.9.9-4.P5.fc25 -> 9.9.9-4.P6.fc25 bind99-license 9.9.9-4.P5.fc25 -> 9.9.9-4.P6.fc25 cockpit-bridge 131-1.fc25 -> 134-1.fc25 cockpit-docker 131-1.fc25 -> 134-1.fc25 cockpit-networkmanager 131-1.fc25 -> 134-1.fc25 cockpit-ostree 131-1.fc25 -> 134-1.fc25 cockpit-system 131-1.fc25 -> 134-1.fc25 container-selinux 2:2.6-1.fc25 -> 2:2.10-1.fc25 coreutils 8.25-15.fc25 -> 8.25-16.fc25 coreutils-common 8.25-15.fc25 -> 8.25-16.fc25 fedora-repos 25-2 -> 25-3 freetype 2.6.5-1.fc25 -> 2.6.5-3.fc25 gnutls 3.5.9-2.fc25 -> 3.5.10-1.fc25 gssproxy 0.6.1-2.fc25 -> 0.7.0-1.fc25 kernel 4.9.12-200.fc25 -> 4.9.13-201.fc25 kernel-core 4.9.12-200.fc25 -> 4.9.13-201.fc25 kernel-modules 4.9.12-200.fc25 -> 4.9.13-201.fc25 krb5-libs 1.14.4-4.fc25 -> 1.14.4-7.fc25 libseccomp 2.3.1-1.fc25 -> 2.3.2-1.fc25 libsss_idmap 1.14.2-2.fc25 -> 1.15.1-1.fc25 libsss_nss_idmap 1.14.2-2.fc25 -> 1.15.1-1.fc25 libsss_sudo 1.14.2-2.fc25 -> 1.15.1-1.fc25 nss 3.28.1-1.3.fc25 -> 3.28.3-1.0.fc25 nss-pem 1.0.2-2.fc25 -> 1.0.3-2.fc25 nss-softokn 3.28.1-1.0.fc25 -> 3.28.3-1.1.fc25 nss-softokn-freebl 3.28.1-1.0.fc25 -> 3.28.3-1.1.fc25 nss-sysinit 3.28.1-1.3.fc25 -> 3.28.3-1.0.fc25 nss-tools 3.28.1-1.3.fc25 -> 3.28.3-1.0.fc25 nss-util 3.28.1-1.0.fc25 -> 3.28.3-1.0.fc25 oci-systemd-hook 0.1.4-4.git15c2f48.fc25 -> 1:0.1.5-1.git16f7c8a.fc25 openssh 7.4p1-3.fc25 -> 7.4p1-4.fc25 openssh-clients 7.4p1-3.fc25 -> 7.4p1-4.fc25 openssh-server 7.4p1-3.fc25 -> 7.4p1-4.fc25 pcre 8.40-4.fc25 -> 8.40-5.fc25 python3-rpm 4.13.0-6.fc25 -> 4.13.0.1-1.fc25 python3-sssdconfig 1.14.2-2.fc25 -> 1.15.1-1.fc25 rpm 4.13.0-6.fc25 -> 4.13.0.1-1.fc25 rpm-build-libs 4.13.0-6.fc25 -> 4.13.0.1-1.fc25 rpm-libs 4.13.0-6.fc25 -> 4.13.0.1-1.fc25 rpm-plugin-selinux 4.13.0-6.fc25 -> 4.13.0.1-1.fc25 screen 4.5.0-1.fc25 -> 4.5.1-1.fc25 selinux-policy 3.13.1-225.10.fc25 -> 3.13.1-225.11.fc25 selinux-policy-targeted 3.13.1-225.10.fc25 -> 3.13.1-225.11.fc25 sssd-client 1.14.2-2.fc25 -> 1.15.1-1.fc25 vim-minimal 2:8.0.347-2.fc25 -> 2:8.0.425-1.fc25

1 0

[atomic-wg] Issue #235 `Container guidelines for versioning of packages in the container`
by James Hogarth 13 Mar '17

13 Mar '17

jhogarth reported a new issue against the project: `atomic-wg` that you are following: `` Since the container build process uses stable repos it's tricky to time a container update alongside an update of key components. It also leads to the question to the guidelines of "what does 'ENV NAME=myawesomecontainer VERSION=0.1 RELEASE=1 ARCH=x86_64' actually mean?" In the case of the owncloud container review one would think it refers to owncloud itself (presently at 9.1.4) but the container also has httpd and php which may be susceptible to security issues and knowing the version within may be important. There's also an issue of tying the version in the ENV to the actual package in place. We should have something in the guidelines to ensure this. The RUN dnf -y install owncloud (in this instance) should probably have dnf -y install owncloud-${VERSION}-${RELEASE} in order to prevent race conditions, although this would have an effect on the proposed fortnightly build process with the timing between an RPM maintainer updating the package and the container maintainer presenting a container update. We either need a way to attempt to automate this, accept failures and rebuilds or some other thing I haven't thought of. In addition we should allow building the container from at least the testing repos, if not the koji buildroot or similar setup, to prevent a significant lag between an update in fedora and being able to provide that update in a container based service. The worst case would be a package in updates-testing for a full week and a poorly timed move to stable with the next container build, as proposed elsewhere, two weeks away for a full three weeks for a potential vulnerability or major bug. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/235

5 7

[atomic-wg] Issue #255 `Consider creating redirection site for image Help Files`
by Dusty Mabe 13 Mar '17

13 Mar '17

dustymabe added a new comment to an issue you are following: `` IMHO we are creating a problem before it exists. I ultimately don't have to manage infrastructure so I'm going to abstain from voting on this one. I do know that I really don't want to have to deal with this at all, so if we go this route, whoever pursues implementation needs to own it in the future as well. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/255

1 0

[atomic-wg] Issue #255 `Consider creating redirection site for image Help Files`
by Josh Berkus 13 Mar '17

13 Mar '17

jberkus added a new comment to an issue you are following: `` @dustymabe @maxamillion `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/255

1 0

[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
by Dusty Mabe 13 Mar '17

13 Mar '17

dustymabe added a new comment to an issue you are following: `` i'm +1 for all lower case - but realize this is an arbitrary discussion `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/253

1 0

[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
by Josh Berkus 13 Mar '17

13 Mar '17

The issue: `lower case vs Initial Cap in Labels` of project: `atomic-wg` has been assigned to `maxamillion` by jberkus. https://pagure.io/atomic-wg/issue/253

1 0

[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
by Josh Berkus 13 Mar '17

13 Mar '17

jberkus added a new comment to an issue you are following: `` @maxamillion @yzhang @dustymabe `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/253

1 0

[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
by Dusty Mabe 13 Mar '17

13 Mar '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We have identified quite a few policy decisions that need to be made surrounding containers before we can start reviewing these things in bulk. Some of the issues are below: - https://pagure.io/atomic-wg/issue/235 - https://pagure.io/atomic-wg/issue/234 - https://pagure.io/atomic-wg/issue/233 We need to have a group of people really get together and hash these issues out and publish the results so that we can start reviewing containers at a faster rate. I am giving the point on this to @jberkus as discussed in today's IRC meeting. A VFAD next week would probably be a great way to hash out some of this and get decisions back to users and reviewers fast. other interested parties that want to take part in the discussion are @gbraad, @kushal, @jhogarth. It's also required that @maxamillion be there and would probably be good to have @jbrooks there. I'll add more names as I find people. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238

4 14

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`
by Josh Berkus 13 Mar '17

13 Mar '17

The issue: `Container guidelines for systemd based containers` of project: `atomic-wg` has been assigned to `jasonbrooks` by jberkus. https://pagure.io/atomic-wg/issue/233

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud March 2017