[atomic-wg] Issue #290: Make fedora-minimal base image generally available
mattdm added a new comment to an issue you are following: `` That's less than I expected, really. :) (And some of it really random. From coreutils, we loose `pinky` but not `base32` (which isn't in EL7 and I'd never heard of... but that's another story.) I'd really love to see a bug associated with each one of those `rm`s in `%post`. It seems like we could solve most of it with better packaging over time, and then get to the point where we _could_ do the additive thing. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #290: Make fedora-minimal base image generally available
dustymabe added a new comment to an issue you are following: `` theoretically yes, but we do some stuff to the minimal image to reduce the image size that we'd then have to undo. I don't think it really makes sense. You can see for yourself: [minimal kickstart](https://pagure.io/fedora-kickstarts/blob/f26/f/fedora-docker-base-minimal.ks) [non-minimal kickstart](https://pagure.io/fedora-kickstarts/blob/f26/f/fedora-docker-base.ks). Note that both of these *include* [docker-common.ks](https://pagure.io/fedora-kickstarts/blob/f26/f/fedora-docker-common.ks). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #290: Make fedora-minimal base image generally available
jberkus added a new comment to an issue you are following: `` Theoretically, yes. I'd let @maxamillion comment on whether that's practical. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #290: Make fedora-minimal base image generally available
mattdm added a new comment to an issue you are following: `` Is it possible to make the minimal image the base of the regular image? That seems ideal from a testing perspective (not to mention explosion of streams). I've had in the back of my mind for a while the idea of fedora-minimal and fedora (regular) like that, and then maybe a fedora-batteries image above that, which includes packages not in the fedora image but common to some threshold of our official layered images. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #290: Make fedora-minimal base image generally available
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` A "minimal" build of the base container image exists, but isn't official or generally available from the repository. We need this minimal image for a few reasons: * users care about container size from some use-cases (think super-micro-services and serverless) * arguably a more minimal container is easier to secure * other linux distros offer some kind of small base image * buildah, now in alpha, *really* benefits from a minimal base image For this to succeed, we'd want the following base images as part of registry.fedoraproject.org: * fedora-minimal:25 * fedora-minimal:26 * fedora-minima:latest Given that the minimal image will differ less per release version (since it has less plubming), it would be perfectly acceptable to have a very short expiration window on older release versions, or only supporting the current Fedora release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #283: please include documentation for run label inside Fedora container guidelines
jberkus added a new comment to an issue you are following: `` The guidelines link to the official Atomic CLI documentation. Is there a specific link to in-depth RUN docs we can use? This needs to be a web link, not a man page. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/283 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Atomic WG Meeting Minutes 2017-06-28
summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic_wg.2017-06-28-17.01.html full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic_wg.2017-06-28-17.01.log.html === #fedora-meeting-1: fedora_atomic_wg === Meeting started by dustymabe at 17:01:17 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic_wg.2017-06-28-17.01.log.html . Meeting summary --- * roll call (dustymabe, 17:01:23) * list of people to ping for meetings (dustymabe, 17:07:04) * LINK: https://pagure.io/atomic-wg/pull-request/288# (dustymabe, 17:07:13) * previous meeting action items (dustymabe, 17:10:51) * ACTION: dustymabe to propose a VFAD for wiki and docs discussion (dustymabe, 17:11:39) * LINK: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2017-06-21-17.03.log.html (dustymabe, 17:14:22) * ACTION: maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:14:52) * PRD has been approved (gholms, 17:16:04) * Matching Fedora Server's PRD format was helpful (gholms, 17:16:39) * LINK: https://pagure.io/atomic-wg/issues?status=Open=meeting (dustymabe, 17:17:12) * ACTION: jberkus to create new issues, specs for docs.projectatomic.io publication (dustymabe, 17:18:55) * clarify policy on atomic host support for older Fedora "number" releases (dustymabe, 17:20:07) * https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:20:11) * the fedora magazine post has landed https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/ (dustymabe, 17:20:31) * fedimg: don't use 'builder' instance for uploading AMIs (dustymabe, 17:22:54) * LINK: https://pagure.io/atomic-wg/issue/269 (dustymabe, 17:23:00) * this will most likely wait until after fedora 26 release because we are now in freeze (dustymabe, 17:23:29) * Set architecture label in the base container image (dustymabe, 17:26:28) * LINK: https://pagure.io/atomic-wg/issue/276 (dustymabe, 17:26:35) * Figure out comprehensive strategy for atomic host container storage (dustymabe, 17:28:45) * LINK: https://pagure.io/atomic-wg/issue/281 (dustymabe, 17:29:07) * AGREED: changing fedora 27 and beyond to default to overlayfs on the root partition will help us simplify our storage setup and align better with other fedora variants. This seems like a reasonable change to make assuming that overlayfs proves stable for the f26 cycle. (dustymabe, 17:41:27) * Atomic Host images omit many common locales that all other flavors include (dustymabe, 17:41:38) * LINK: https://pagure.io/atomic-wg/issue/282 (dustymabe, 17:41:45) * ACTION: maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group (dustymabe, 17:44:14) * Identify group of people interested in maintaining kubernetes (dustymabe, 17:44:56) * LINK: https://pagure.io/atomic-wg/issue/287 (dustymabe, 17:45:14) * open floor (dustymabe, 17:49:50) * Work continues on fixing EC2 image visibility, as copied images need their permissions changed (gholms, 17:53:06) * if you haven't yet tried out minishift, you should check it out https://www.openshift.org/minishift/ (dustymabe, 17:54:15) Meeting ended at 17:58:46 UTC. Action Items * dustymabe to propose a VFAD for wiki and docs discussion * maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 * jberkus to create new issues, specs for docs.projectatomic.io publication * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group Action Items, by person --- * dustymabe * dustymabe to propose a VFAD for wiki and docs discussion * jberkus * jberkus to create new issues, specs for docs.projectatomic.io publication * maxamillion * maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * roshi * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * **UNASSIGNED** * (none) People Present (lines said) --- * dustymabe (156) * roshi (24) * maxamillion (24) * gholms (22) * zodbot (20) * jberkus (18) * kushal (13) * yzhang (12) * sayan (11) * gbraad_ (9) * suiwenfeng (7) * DimGR (7) * walters (2) * miabbott (1) * rubao (1) * nzwulfin (1) * jzb (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ cloud mailing list --
Atomic WG Meeting Minutes 2017-06-21
summary: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2017-06-21-17.03.html full log: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2017-06-21-17.03.log.html === #fedora-meeting-1: fedora_atomic_wg === Meeting started by dustymabe at 17:03:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-21/fedora_atomic_wg.2017-06-21-17.03.log.html . Meeting summary --- * roll call (dustymabe, 17:03:28) * Fedora OSBS RFE: install go-md2man to buildroot image (dustymabe, 17:06:20) * LINK: https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:06:28) * LINK: https://pagure.io/atomic-wg/issue/256 (dustymabe, 17:10:56) * LINK: https://pagure.io/atomic-wg/issue/256#comment-436537 (dustymabe, 17:11:31) * ACTION: maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:17:11) * action items from last meeting (dustymabe, 17:17:28) * ACTION: dustymabe to propose a VFAD for wiki and docs discussion (dustymabe, 17:18:18) * ACTION: jberkus to update wg on final approval of PRD (dustymabe, 17:18:38) * ACTION: jberkus to create new issues, specs for docs.projectatomic.io publication (dustymabe, 17:18:48) * dustymabe did create the SIG page for the wiki https://fedoraproject.org/wiki/Atomic_WG (dustymabe, 17:19:39) * maxamillion updated the container guidelines to enforce ENV and label for https://pagure.io/atomic-wg/issue/277 (dustymabe, 17:19:57) * Atomic Host images omit many common locales that all other flavors include (dustymabe, 17:21:12) * LINK: https://pagure.io/atomic-wg/issue/282 (dustymabe, 17:21:20) * talk/workshop proposals for Flock (dustymabe, 17:23:36) * LINK: https://pagure.io/atomic-wg/issue/279 (dustymabe, 17:23:40) * Set architecture label in the base container image (dustymabe, 17:25:34) * LINK: https://pagure.io/atomic-wg/issue/276 (dustymabe, 17:25:42) * fedimg: don't use 'builder' instance for uploading AMIs (dustymabe, 17:37:29) * LINK: https://pagure.io/atomic-wg/issue/269 (dustymabe, 17:37:34) * clarify policy on atomic host support for older Fedora "number" releases (dustymabe, 17:38:39) * LINK: https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:38:53) * open floor (dustymabe, 17:40:34) * testday went well, no notable issues found. Good work! (roshi, 17:43:28) Meeting ended at 17:50:02 UTC. Action Items * maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 * dustymabe to propose a VFAD for wiki and docs discussion * jberkus to update wg on final approval of PRD * jberkus to create new issues, specs for docs.projectatomic.io publication Action Items, by person --- * dustymabe * dustymabe to propose a VFAD for wiki and docs discussion * maxamillion * maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 * **UNASSIGNED** * jberkus to update wg on final approval of PRD * jberkus to create new issues, specs for docs.projectatomic.io publication People Present (lines said) --- * dustymabe (112) * maxamillion (34) * roshi (22) * zodbot (16) * jbrooks (6) * jds2001 (5) * sayan (2) * dgilmore (2) * miabbott (1) * nirik (1) * mnguyen (1) * rubao (1) * ksinny (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #289: Investigating the possibility to have an Atomic Host LiveCD
gbraad reported a new issue against the project: `atomic-wg` that you are following: `` At the moment we run a CentOS-based livecd to run our VM environment, but we would really like to target an Atomic Host. I have been looking into generating an image using the kickstart at https://github.com/gbraad/minishift-atomic-iso/. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/289 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage
dustymabe added a new comment to an issue you are following: `` Discussed in the atomic working group meeting today: *changing fedora 27 and beyond to default to overlayfs on the root partition will help us simplify our storage setup and align better with other fedora variants. This seems like a reasonable change to make assuming that overlayfs proves stable for the f26 cycle.* `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #228: clarify policy on atomic host support for older Fedora "number" releases
The status of the issue: `clarify policy on atomic host support for older Fedora "number" releases` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/228 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #266: rpmostree_compose Ansible module
gbraad added a new comment to an issue you are following: `` Still in dev? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/266 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #228: clarify policy on atomic host support for older Fedora "number" releases
dustymabe added a new comment to an issue you are following: `` fed mag post here: https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/228 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #287: Identify group of people interested in maintaining kubernetes
jberkus added a new comment to an issue you are following: `` @sjenning well, we have to repackage based on Fedora or centOS base images with each Kubeadm release, so that's some ongoing work. There's also a bunch of other config stuff which doesn't currently work "out of the box" and would be nice to make work. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/287 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #287: Identify group of people interested in maintaining kubernetes
suiwenfeng added a new comment to an issue you are following: `` I am interested in kubernetes, please let me in. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/287 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
