Re: Request for testing: Fedora 37 pre-Beta validation tests
On 8/29/22 17:22, Adam Williamson wrote: It would be really great if we can get the validation tests run now so we can find any remaining blocker bugs in good time to get them fixed. Right now the blocker list looks short, but there are definitely some tests that have not been run. Last I checked, flatpak was still broken. Will retest this week. -- -- Josh Berkus Kubernetes Community Architect OSPO, OCTO ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Atomic Host Docs VFAD on Friday information & preparation
Folks: As scheduled, we will be having a Virtual Fedora Activity Day focused on the Atomic Host documentation this Friday, July 28th. The day starts at 13:30 UTC (9:30 EDT, 19:00 IST), with a video conference before we split up for work. The rest of the program may be found on this etherpad: http://etherpad.osuosl.org/fedora_atomic_docs_vfad Before you come to the VFAD, please read that document. If you have a chance beforehand -- or if you cannot make it to the VFAD at all -- please comment on the proposed documentation content in the etherpad. Make sure and put your name in for your color so we know whose comments belong to whom. (note to folks on the cloud@ mailing list: we will soon stop using this mailing list for Atomic stuff. please sign up for atomic-devel) -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` @jlebon that was suggested, but @dustymabe really wanted a separate channel, and nobody argued against it. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Minutes for meeting
=== #fedora-meeting-1: fedora_atomic_wg === Meeting started by jberkus at 17:01:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-19/fedora_atomic_wg.2017-07-19-17.01.log.html . Meeting summary --- * Roll Call (jberkus, 17:01:49) * action items from last meeting (jberkus, 17:04:28) * open meeting tickets (jberkus, 17:05:47) * Ticket 295 Mailing lists and IRC (jberkus, 17:09:22) * LINK: https://pagure.io/atomic-wg/issue/295 (dustymabe, 17:09:50) * ACTION: : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra (jberkus, 17:22:27) * ACTION: : dustymabe to update IRC channel topics to reflect new scheme (jberkus, 17:23:15) * ACTION: ksinny to update wiki (jberkus, 17:23:29) * ACTION: dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings (dustymabe, 17:24:17) * ACTION: jberkus to write blog post for fedora magazine/pa.io on changes (jberkus, 17:24:22) * open floor (jberkus, 17:26:30) * LINK: https://pagure.io/atomic-wg/issue/303 (dustymabe, 17:27:33) * ACTION: dusty to put in place updating of last f25 ref automated via bodhi (dustymabe, 17:38:08) * ACTION: dustymabe to write blog post about last f25 updates (jberkus, 17:38:44) * ACTION: dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref (dustymabe, 17:38:52) * LINK: https://pagure.io/atomic-wg/issue/287 (strigazi, 17:39:21) * ACTION: dustymabe to create kubernetes-sig pagure repo and notify interested parties (dustymabe, 17:40:29) * ACTION: jberkus to re-create issues in new repo (jberkus, 17:41:44) * ACTION: kubernetes-sig to discuss version tagging for kube system containers (jberkus, 17:52:32) * LINK: https://pagure.io/atomic-wg/issue/294 (dustymabe, 17:53:52) * ACTION: dustymabe jberkus to write doc on docs vfad with all resources linked (jberkus, 17:59:10) Meeting ended at 18:00:56 UTC. Action Items * : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra * : dustymabe to update IRC channel topics to reflect new scheme * ksinny to update wiki * dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings * jberkus to write blog post for fedora magazine/pa.io on changes * dusty to put in place updating of last f25 ref automated via bodhi * dustymabe to write blog post about last f25 updates * dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref * dustymabe to create kubernetes-sig pagure repo and notify interested parties * jberkus to re-create issues in new repo * kubernetes-sig to discuss version tagging for kube system containers * dustymabe jberkus to write doc on docs vfad with all resources linked Action Items, by person --- * dustymabe * : dustymabe to update IRC channel topics to reflect new scheme * dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings * dustymabe to write blog post about last f25 updates * dustymabe to create kubernetes-sig pagure repo and notify interested parties * dustymabe jberkus to write doc on docs vfad with all resources linked * jberkus * : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra * jberkus to write blog post for fedora magazine/pa.io on changes * jberkus to re-create issues in new repo * dustymabe jberkus to write doc on docs vfad with all resources linked * ksinny * ksinny to update wiki * **UNASSIGNED** * dusty to put in place updating of last f25 ref automated via bodhi * dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref * kubernetes-sig to discuss version tagging for kube system containers People Present (lines said) --- * jberkus (106) * dustymabe (96) * jbrooks (36) * maxamillion (32) * roshi (23) * gholms (16) * strigazi (14) * ksinny (12) * walters (12) * zodbot (11) * bowlofeggs (1) * scollier (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Josh Berkus Project Atomic Red Hat OSAS ___ 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: `` Ah, limitations of pagure. So, two solutions: (1) we create an atomic_k8s repo (2) we ask folks to subscribe to the mailing list for automated notifications and filter by tags using their mail filters. I'm pretty sure I know the answer already, but @jchaloup @tstclair @dimtheo @sjenning @suiwenfeng can you comment on what you'd prefer? `` 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 #281: Figure out comprehensive strategy for atomic host container storage
jberkus added a new comment to an issue you are following: `` I'm saying that the XFS vs. BtrFS decision was made elsewhere for Fedora, and we can't change it *in this issue*. `` 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 #281: Figure out comprehensive strategy for atomic host container storage
jberkus added a new comment to an issue you are following: `` Anyway, I refuse to weigh into another XFS vs. BtrFS debate, and starting one here won't result in us having a storage plan. `` 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 #281: Figure out comprehensive strategy for atomic host container storage
jberkus added a new comment to an issue you are following: `` @chrismurphy ZFS is still out there, even if we can't touch it. `` 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 #281: Figure out comprehensive strategy for atomic host container storage
jberkus added a new comment to an issue you are following: `` "certain other filesystem"? Can you please be less opaque? `` 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 #287: Identify group of people interested in maintaining kubernetes
jberkus added a new comment to an issue you are following: `` I think we use atomic_wg pagure for issues, and tag stuff with [kube]? `` 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
jberkus added a new comment to an issue you are following: `` I think we use atomic_wg pagure for issues, and tag stuff with [kube]? `` 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 #281: Figure out comprehensive strategy for atomic host container storage
jberkus added a new comment to an issue you are following: `` Specifically, we want to be sure that the full disk is allocate on AWS instances. `` 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 #197: Change size of Root, Docker partitions in F26 Atomic Host storage setup
The status of the issue: `Change size of Root, Docker partitions in F26 Atomic Host storage setup` of project: `atomic-wg` has been updated to: Closed as Duplicate by jberkus. https://pagure.io/atomic-wg/issue/197 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #197: Change size of Root, Docker partitions in F26 Atomic Host storage setup
jberkus added a new comment to an issue you are following: `` Folding this issue into #281, which it's a subset of. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` Revised proposal based on discussion on #fedora-cloud: Mailing Lists: * ato...@lists.fedoraproject.org gets created. This list is for all automated messages and cc'd on announcements. It is not a discussion list; discussions on it will be either (a) cc'd to atomic-devel or (b) redirected to a pagure issue as appropriate. * atomic-de...@projectatomic.io will be used for all mailing list discussions. IRC: * all discussions of general topics around Fedora Atomic, including contents, containerized kube, container reviews, ostree changes, etc, etc. will be on #atomic. * discussions and troubleshooting Fedora build pipeline/releng (bodhi, punji, etc.) for Atomic will be on the new channel #fedora-atomic. Content discussions which start there will get re-directed to #atomic. Works for everyone? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` I'll also point out that https://getfedora.org/en/atomic/download/ already directs people to ato...@pa.io and #atomic. This isn't something I changed; it's how it was before I started working on Fedora Atomic. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` So for the last month, we have only two threads which were NOT automated messages (and in the meantime, over 100 automated messages). One was Stef's CI/CD question (which arguably should have been a Pagure issue, and could just as easily have been on atomic-devel@), and the other was one call for contianer review (which got no responses). So the reality is we have two media for communication in the project: IRC, and Pagure issues. The mailing list is NOT used for discussion, materially. So when we're talking about the list, we're really asking "where do automated messages go". And if that's the question, the answer *is* ato...@lists.fp.org. However, also based on that evidence, I assert that we should be telling people: discussion and support questions should go to atomic-devel@pa OR should be filed as issues on pagure, because that's where they'll get responses. Hence my proposal, above. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` @mattdm well, the contributors use email, so we need *something* for them to use. Or do we? I'm going to do an examination of traffic on cloud@. I'm willing to bet that I'll find out that 90% of the traffic is automated messages. Given that, we could have those messages go pretty much *anywhere*. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` Given the level of traffic on atomic@, those could be combined, frankly. And I think it would get questions on atomic@ answered faster. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` ... but what if their question is actually about rpm-ostree, or the Atomic CLI, once we get the details? Then we have to shunt them to another list. This is a bad experience for people new to the community. do you follow? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` @dustymabe, @mattdm One question is, "if a new participant/user/fedora packager wants to start a discussion about Fedora Atomic, where do we direct them?" If we can answer that, we can decide what to do with the mailing lists. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
jberkus added a new comment to an issue you are following: `` I am opposed to both having a new list and especially to having a new IRC channel. Let me explain the main reason for my opposition, followed by some detail on IRC vs. ML. A lot of the container audience is new developers and devops people. These folks generally prefer not to use "antiquated" media like email and IRC at all (mostly they use slack and github issues). We really want to reach this sector as users and potential contributors. It's bad enough that we're asking them to join a mailing list or an IRC channel at all; asking them to join *multiple* lists and channels is an automatic "Forget it, I'll use something else". Now, for the IRC channel, it's a fact today that #fedora-cloud and #atomic are used almost interchangeably by the contributors to Atomic Host and its underlying tech. I've seen CAH, CLI and rpm-ostree discussions on #fedora-cloud, and I've seen Fedora Atomic build discussions on #atomic. Given that, we should stop confusing new users and simply have One Big Channel with all things Atomic, which would be channel #atomic. The mailing list is more complicated. If you look at the traffic on cloud@lists.fedoraproject, you'll see that 80% of the traffic is automated notices of some kind. My proposal is that we: a. Move all *discussion* traffic to atomic-de...@projectatomic.io b. Create a new list, ato...@list.fp, which is exclusively for automated notices While this seems like a fine difference from Dusty's proposal, the distinction is important. Again, like #atomic, there is no clear distinction between what discussion belongs on atomic-devel vs. cloud@fedora, and as a result discussions end up getting crossed over or sent to both. This is very confusing to new community participants, especially if they're only subscribed to one of the lists. Second, by making the list split discussion vs. notices, we allow people to join in the discussion without requiring them to receive all of the automated notices. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release
The issue: `Cannot install to bare metal using kickstart due to ref name problems in f26 release` of project: `atomic-wg` has been assigned to `jberkus` by jberkus. https://pagure.io/atomic-wg/issue/296 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release
The issue: `Cannot install to bare metal using kickstart due to ref name problems in f26 release` of project: `atomic-wg` has been assigned to `dustymabe` by jberkus. https://pagure.io/atomic-wg/issue/296 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` I pave my bare metal cluster using a kickstart similar to the one here: http://www.projectatomic.io/blog/2016/10/install-with-kickstart/ However, as of f26 release, this no longer works. Which is surprising given that f26 alpha did work. The problem is this line in my updated kickstart: ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" --url="file:run/install/repo/content/repo" --ref="fedora/26/x86_64/atomic-host" --nogpg This should pull the ref from the local media (USB key). However, what I get now is "openat: no such file or directory" So somehow the ref is broken in the ISO. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/296 ___ 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: `` @fkluknav all of the buildah documentation so far has worked with base images, I assumed that a base image was required. Apparently, according to @dwalsh, a base image is NOT required? Or we already have a base image called "scratch" which has just glibc and nothing else? `` 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: `` @mattdm yah, and we're not going to get one, because Lennart hates containers. So probably wasting time here. `` 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: `` @jwboyer not yet, there's one currently being drafted, and one of the reasons we haven't published it is because fedora-minimal isn't usable in a Dockerfile. Let me sum up: Buildah builds containers in the LXC fashion, installing from the host system into an alternate rootdir. This means that containers can theoretically be much smaller than Docker Build, because build & install tools (gcc, git, dnf) don't need to be included in the image. However, if the base image is already 199MB, excluding 40MB of build tools doesn't really make a difference. Therefore, we want Fedora Minimal to be available for Buildah, where 40MB of not-needed tools would make a huge difference. `` 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: `` @fkluknav systemd is a big one, how many MB is that with dependencies? I thought we had a stub systemd which was kinda working ... it's particularly troubling to users to have systemd in the image when they don't want to use it (note that we're also going the opposite way with the fedora-init image). `` 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
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] 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
List of needed people for Flock sessions?
Bex, You've said that you want to use the list of accepted proposals to determine who needs to be at Flock this year (and thus who is funded). However, the application form doesn't have a field for "list of needed participants". Should we add everyone needed for a work session as co-presenters? Or something else? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #279: talk/workshop proposals for Flock
jberkus added a new comment to an issue you are following: `` Fedora Atomic Doc Work Fedora Atomic has all kinds of awesome first-in-the-industry capabilities, but isn't getting the attention it deserves because a minority of our features are documented. As of Flock, we have a brand-new, CI-and-container-driven documentation system, and this work session will help populate it. This session will include a brief introduction on setting up a local build & test environment for Atomic documentation and the practical basics of our tools and style sheets. We will then pick from a list of areas which urgently need documentation and participants will work in teams to start documentation for those sections. This Do session follows up on the Atomic Doc VFAD from late July, in order to get more Fedora community members helping with documentation. Attendees should bring Fedora laptops with git and Minishift installed. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/279 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include
jberkus added a new comment to an issue you are following: `` @jlebon given that we're currently trying to *shrink* the base image, I'm not keen on adding 137MB of storage if we can find another option. Currently the CoreOS ISO is half the size of Fedora Atomic, and that's an issue which folks bring up with me at container conferences, a lot. I'd be up for an "all-locales" branch. I'd prefer a locales system container, but I realize that's probably pie-in-the-sky right now. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/282 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include
jberkus added a new comment to an issue you are following: `` 1) Why do locales need to be installed into the tree? Isn't this just configuration? 2) Maybe we just need an all-locales option. 3) If Flatpak has a solution that works, can we emulate/copy it? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/282 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Question on adding new contributors
On 06/05/2017 01:55 PM, Dusty Mabe wrote: > > > On 06/05/2017 04:48 PM, Josh Boyer wrote: >> Hi Atomic group, >> >> The Atomic PRD (https://fedoraproject.org/wiki/Atomic/PRD) that was >> recently drafted says that other CPU architectures can be added as new >> community members join. A perfectly fair and reasonable statement! >> However, it now leads me to ask a question of you. Do you have formal >> ways for a new community member to join? Is there an on-boarding >> document in place? I ask because we already have community members >> willing to maintain other cpu architectures, particularly around ARM >> for IoT and ppc64le for containers. >> >> So aside from the work they have already done, such as request >> composes for these architectures and do testing, what else would you >> like to see in order for them to be official members? >> > > Hey Josh, > > We don't have anything official that I know of. For me it's all about > the following: > > 1 - do people hang out in IRC/mailing list and show up for meetings > 2 - do things get unbroken relatively quickly > 3 - does requested work get done in a timely manner > > If you want to formally be a member of the WG then doing those three > things and requesting to be a formal member will most likely get you > there. You can formally request to be a member by opening a ticket > against our pagure instance. > > Note that formal WG membership doesn't really buy you much. We really > take all of our community involvement seriously and I don't think > we've ever not considered someones vote for something because they > weren't an official member. We are glad to have everyone! > > I hope this helps answer your question Hey, we could put up a wiki page with all of the above, no? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #279: talk/workshop proposals for Flock
jberkus added a new comment to an issue you are following: `` So, one thing I *really* want to do is an end-to-end submit/review container images to FLIBS. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/279 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[fedora-atomic] PR #59: f26: add back in kube/storage clients for now
jberkus commented on the pull-request: `f26: add back in kube/storage clients for now` that you are following: `` The bigger point is that: a) we don't have *official* kube system containers yet. b) none of our users have tried the containers we do have, so we have no idea how they work in production `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/59 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Minutes for May 17 meeting
Follows: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-05-17/fedora_atomic_wg.2017-05-17-17.01.txt === #fedora-meeting-1: fedora_atomic_wg === Meeting started by jberkus at 17:01:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-17/fedora_atomic_wg.2017-05-17-17.01.log.html . Meeting summary --- * roll call (jberkus, 17:01:49) * meeting minutes (jberkus, 17:06:46) * action items from last meeting (jberkus, 17:10:30) * ACTION: : dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker (jberkus, 17:12:10) * LINK: https://pagure.io/atomic-wg/issue/262#comment-441102 (dustymabe, 17:13:20) * ACTION: : x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points (jberkus, 17:14:59) * issues flagged as meeting (jberkus, 17:15:33) * ACTION: jbrooks to write project atomic blog post re #228, and add info to fedora PRD (jbrooks, 17:21:45) * ACTION: jberkus to ask mattdm about how to get PRD approved (jberkus, 17:22:17) * open floor (jberkus, 17:24:37) * ACTION: : dustymabe to put bz query for containers pending review on wiki (jberkus, 17:33:50) * LINK: http://fedoraproject.org/PackageReviewStatus/ (dustymabe, 17:37:48) * ACTION: dustymabe to add a ticket to look into getting an easy-to-use container review link after F26 (jberkus, 17:40:20) Meeting ended at 17:53:46 UTC. Action Items * : dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker * : x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points * jbrooks to write project atomic blog post re #228, and add info to fedora PRD * jberkus to ask mattdm about how to get PRD approved * : dustymabe to put bz query for containers pending review on wiki * dustymabe to add a ticket to look into getting an easy-to-use container review link after F26 Action Items, by person --- * dustymabe * : dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker * : dustymabe to put bz query for containers pending review on wiki * dustymabe to add a ticket to look into getting an easy-to-use container review link after F26 * jberkus * : x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points * jberkus to ask mattdm about how to get PRD approved * jbrooks * jbrooks to write project atomic blog post re #228, and add info to fedora PRD * x3mboy * : x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points * **UNASSIGNED** * (none) People Present (lines said) --- * jberkus (81) * dustymabe (58) * maxamillion (21) * yzhang (20) * roshi (17) * zodbot (12) * sayan (11) * x3mboy (8) * jbrooks (6) * miabbott (2) * walters (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262: F26 Talking Points
jberkus added a new comment to an issue you are following: `` @x3mboy I thought we were supposed to have a meeting 20 min ago, but you haven't been on IRC. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ 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
jberkus added a new comment to an issue you are following: `` Suggested revision: * Due in part to this faster pace, the Fedora Atomic workgroup has always focused its testing and integration efforts most directly on the latest stable release, encouraging users of the older release to rebase to the newer tree, and dealing with support of the older release on a best-effort basis. Should be * Due in part to this faster pace, the Fedora Atomic workgroup has always focused its testing and integration efforts most directly on the latest stable release, encouraging users of the older release to rebase to the newer tree as soon as possible. Releases older than the current tree are supported only on a "best effort" basis, meaning that the ostree is updated, but there is no organized testing of it. `` 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
Re: will miss today's meeting
On 05/03/2017 08:34 AM, Dusty Mabe wrote: > > I'm attending Red Hat Summit this week and will most likely not > be able to attend the meeting today. We had one action item from > last week: Yah, I have the same issue. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Atomic WG Meeting Minutes April 19
... just for the record, since I forgot them last week. === #fedora-meeting-1: fedora_atomic_wg === Meeting started by jberkus at 17:02:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-19/fedora_atomic_wg.2017-04-19-17.02.log.html . Meeting summary --- * roll call (jberkus, 17:02:22) * previous meeting action items (dustymabe, 17:05:32) * LINK: https://pagure.io/atomic-wg/issue/268 that's mine (jbrooks, 17:06:45) * LINK: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/EKYELPBCKLLUMGTBOYWEC5BOERQBF634/ (dustymabe, 17:08:26) * Meeting Issues (jberkus, 17:14:59) * ACTION: jbrooks to lead writing up the new support policy and plan for rolling releases (jberkus, 17:26:28) * Open Floor (jberkus, 17:26:53) * LINK: https://github.com/moby/moby/pull/32691 (miabbott, 17:41:25) * LINK: http://www.navops.io/navops-roadshow.html (jberkus, 17:48:15) Meeting ended at 17:54:06 UTC. Action Items * jbrooks to lead writing up the new support policy and plan for rolling releases Action Items, by person --- * jbrooks * jbrooks to lead writing up the new support policy and plan for rolling releases * **UNASSIGNED** * (none) People Present (lines said) --- * dustymabe (91) * jberkus (82) * roshi (18) * zodbot (15) * sayan (11) * jbrooks (8) * miabbott (6) * dgilmore (6) * deuscapturus (5) * walters (3) * yzhang (2) * linuxmodder (1) * gholms (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #243: Require DESCRIPTION label for FLIBS containers
jberkus added a new comment to an issue you are following: `` Updated in Wiki. @jasonbrooks now yours for notifying the maintainers. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/243 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #256: atomic command changes: prefer file over label
The status of the issue: `atomic command changes: prefer file over label` of project: `atomic-wg` has been updated to: Closed as Wontfix by jberkus. https://pagure.io/atomic-wg/issue/256 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #256: atomic command changes: prefer file over label
jberkus added a new comment to an issue you are following: `` Closing, all changes have been made per discussion. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/256 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: [atomic-devel] Storage for system containers
On 04/25/2017 12:08 PM, Dusty Mabe wrote: > > > On 04/25/2017 08:25 AM, Daniel Walsh wrote: >> On 04/24/2017 01:56 PM, Dusty Mabe wrote: >> Perhaps we should just mount a partition at /var or move /var/lib/docker >> to /var/lib/containers/docker and make a symbolic link from >> /var/lib/docker-> /var/lib/containers/docker. >> > > I like the approach of /var/lib/docker -> /var/lib/containers/docker. > > Is this something we should pursue? Aren't we going to have to call it /var/lib/containers/moby pretty soon? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #225: Review Container Request for owncload (replacement of Fedora-Dockerfiles GitHub)
The issue: `Review Container Request for owncload (replacement of Fedora-Dockerfiles GitHub)` of project: `atomic-wg` has been assigned to `jberkus` by jberkus. https://pagure.io/atomic-wg/issue/225 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #258: Proposal: suggest ContainerApplicationGenericLabels as Optional labels for FLIBS
The status of the issue: `Proposal: suggest ContainerApplicationGenericLabels as Optional labels for FLIBS` of project: `atomic-wg` has been updated to: Closed by jberkus. https://pagure.io/atomic-wg/issue/258 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #258: Proposal: suggest ContainerApplicationGenericLabels as Optional labels for FLIBS
jberkus added a new comment to an issue you are following: `` Updated, closing issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/258 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262: F26 Talking Points
jberkus added a new comment to an issue you are following: `` Yes. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262: F26 Talking Points
jberkus added a new comment to an issue you are following: `` Looks good, we just need to supply some descriptions. I'd like to replace the OStree-related changes with: OSTree-Driven Releases The OSTree release dates now determine both the two-week release content and the media filenames, meaning that the OSTree update is the release. These OSTree releases are GPG-verified. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #242: Clarify requirements for INSTALL / UNINSTALL labels
jberkus added a new comment to an issue you are following: `` Doesn't contain the guidelines outlined above in this issue, or any examples. Needs more detail. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/242 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #244: require, supply guidelines for "run" label for container in FLIBS
jberkus added a new comment to an issue you are following: `` Container guidelines have been updated. Assigning to @jasonbrooks to track informing the maintainers. Jason, please close when they're informed. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/244 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Proposal: Release blocking for F27
On 04/11/2017 11:09 AM, Adam Miller wrote: > On Thu, Mar 23, 2017 at 10:14 AM, Colin Walters <walt...@verbum.org> wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1435310 >> raised the issue that apparently, Atomic Host isn't "release blocking". >> I think we have plenty of resources to match whatever criteria >> there are for that for Fedora 27. Thoughts? > > Does it make sense for Atomic Host to be "release blocking" when we > can just release every two weeks (or really whenever we want) where as > traditional release is bound to the standard cycle? It's loosely > coupled. > > I would like be clear that I'm not saying or suggesting it either is > or it isn't, but I'm not convinced either direction and I'm curious > what others think about the justification of not being tightly bound > to the release cycle. Also, once we go into rolling releases, how would this work? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262: F26 Talking Points
jberkus added a new comment to an issue you are following: `` Yeah, we should definitely add something about System Containers. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262: F26 Talking Points
jberkus added a new comment to an issue you are following: `` Here's what I have per Dusty: 1. Switch to OverlayFS for default Docker FS. (but not one-big-volume for backwards compat). 2. Containerized Kubernetes as an option. 3. Rename media files (ISO, etc.) to match OStree release date. @dusty, can you provide an example of a completed filename for this? 4. gpg verification of OSTree commits by default 5. two week releases and OSTree updates now synchronize `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: 2wk atomic release candidate: 20170327
On 03/27/2017 02:54 PM, Dusty Mabe wrote: > > We are going to attempt to release the 20170327 images. > These images contain the following ostree version/commit: > > 25.89 > 6a71adb06bc296c19839e951c38dc0b71ee5d7a82262fef9612f256f0c2a70da > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170327.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170327.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170327.0.iso Since I'm at Kubecon, I cannot test the ISO on bare metal this week. Can someone else? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262 `F26 Talking Points`
jberkus added a new comment to an issue you are following: `` @dustymabe well, the more important thing is to answer what we'll have; if we know that, I can do the talking points on the plane. Like, when are we going to decide about containerized kubernetes? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #262 `F26 Talking Points`
jberkus added a new comment to an issue you are following: `` So, will F26 Atomic have containerized Kubernetes? How about OverlayFS? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Meeting about rolling releases
On 03/17/2017 01:36 PM, Dusty Mabe wrote: > > > On 03/16/2017 04:28 PM, Josh Berkus wrote: >> Folks, >> >> For anyone who's interested, we'll be having a meeting about Rolling >> Releases (vs. versioned releases). This is just to get some face-time >> for the discussion of how rolling releases would work, what they mean, >> and when we'll be ready to deploy them (if ever). >> >> Friday, March 17th, 1pm EDT / 17:00 UTC. >> >> http://bluejeans.com/8169971214 >> > > We had the meeting today. I added a summary to the ticket. Please > carry out any discussion in the ticket. > > https://pagure.io/atomic-wg/issue/231 And recording link: https://bluejeans.com/s/wi5nw/ -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #254 `Label/comment for primary RPM?`
jberkus added a new comment to an issue you are following: `` Anything which doesn't involve a field populated by the maintainer is going to fail. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/254 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Meeting about rolling releases
Folks, For anyone who's interested, we'll be having a meeting about Rolling Releases (vs. versioned releases). This is just to get some face-time for the discussion of how rolling releases would work, what they mean, and when we'll be ready to deploy them (if ever). Friday, March 17th, 1pm EDT / 17:00 UTC. http://bluejeans.com/8169971214 Dial-in: +1 800 451 8679 +1 212 729 5016 meeting #8169971214 -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`
jberkus added a new comment to an issue you are following: `` We will be having a meeting on BlueJeans for this at: Friday, March 17th, 1pm EDT / 17:00 UTC. http://bluejeans.com/8169971214 Dial-in: +1 800 451 8679 +1 212 729 5016 meeting #8169971214 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/231 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #234 `Container guidelines for containers with volumes`
jberkus added a new comment to an issue you are following: `` @jhogarth I looked at your suggested guidelines. One I think we should add is: "Unless the image is intended for use as a system container intended for system administration, volumes must be defined so as to mount system directories which are exclusive to the container. For example, the container must mount /etc/application-name/ for config files, not /etc/." `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/234 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #245 `add DEPENDS label for FLIBS containers`
jberkus added a new comment to an issue you are following: `` Adding the Dependencies in the Help file instead. As such, removing this issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/245 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #243 `Require DESCRIPTION label for FLIBS containers`
jberkus added a new comment to an issue you are following: `` @jhogarth ok, I merged your text with mine in Container:Guidelines. Please take a look. Also, what we discussed during the meeting was requiring the help file (which could have any of three names) in the root of the image filesystem. No? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/243 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #258 `Proposal: suggest ContainerApplicationGenericLabels as Optional labels for FLIBS`
jberkus added a new comment to an issue you are following: `` @maxamillion @dustymabe @jasonbrooks etc. I will update the Container Guidelines if approved. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/258 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #248 `Container Guidelines: Layered Images used as a base for other Layered Builds`
jberkus added a new comment to an issue you are following: `` In general, the text seems fine, with a few fixes for labels we changed, etc. @maxamillion , what would the actual FROM line look like? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/248 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #258 `Proposal: suggest ContainerApplicationGenericLabels as Optional labels for FLIBS`
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` This page has a number of labels used by the RHCC which I think would be good to include as Optional labels for FLIBS: https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/vendor/redhat/labels.md The labels I think we should consider include: * url * summary * io.k8s.display-name * io.openshift.expose-services * io.openshift.tags Additionally, it would be good to automatically generate the `description` and `io.k8s.description` tags based on the contents of `help`.However, that is probably at task for a later date. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/258 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
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 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #254 `Label/comment for primary RPM?`
jberkus added a new comment to an issue you are following: `` I think the number of cases where the name of the container is a truncated, or extended, name of the package is going to be fairly large. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/254 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #255 `Consider creating redirection site for image Help Files`
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 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #254 `Label/comment for primary RPM?`
jberkus added a new comment to an issue you are following: `` @maxamillion @dustymabe `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/254 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #254 `Label/comment for primary RPM?`
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` In the 3/10/2017 VFAD, we decided that VERSION would be 0 pending updating FLIBS to support automatically pulling the version from the "primary RPM" in the container. However, we are not currently collecting information from maintainers about which RPM is the primary one. Should we have a label or structured comment, required, which contains this information? Ref #235 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/254 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
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 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #253 `lower case vs Initial Cap in Labels`
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 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #242 `Clarify requirements for INSTALL / UNINSTALL labels`
jberkus added a new comment to an issue you are following: `` Update from VFAD: The INSTALL and UNINSTALL labels are optional. They are only recommended if the container needs some kind of setup beyond "pull". System containers probably always need them. If an INSTALL is supplied, and UNINSTALL should be as well. Both of these labels should work, and should be tested using the Atomic CLI. Guidelines for Install/Uninstall will be included, but mostly point to the Atomic CLI docs. Clarification in Container Guidelines in progress. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/242 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #234 `Container guidelines for containers with volumes`
jberkus added a new comment to an issue you are following: `` Update from VFAD: Maintainers will be required to explicitly declare all required Volumes in the Dockerfile. RUN/USAGE should contain examples of mounting the volumes. HELP should contain a verbose description of each Volume and what its requirements are. Container guidelines being updated. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/234 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #244 `require, supply guidelines for "run" label for container in FLIBS`
jberkus added a new comment to an issue you are following: `` Decision from VFAD: Either USAGE or RUN is required. RUN is for the Atomic CLI, which submitters are not required to use. If they choose to submit using RUN, (a) it must actually work, and (b) USAGE is not required. If the maintainer does not use RUN, they must submit USAGE instead, which is a human-readable sample command. Updates to Container Guidelines to come. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/244 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #235 `Container guidelines for versioning of packages in the container`
jberkus added a new comment to an issue you are following: `` Update from VFAD: The VERSION label and tag will be populated with a "0" until such time as it can be automatically populated based on the "primary" RPM in the container. The RELEASE will be incremented both by the maintainer on any manual change to the package, and by the autobuilder on autobuild. More details in Container Guidelines: https://fedoraproject.org/wiki/Container:Guidelines#VERSIONING `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/235 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #235 `Container guidelines for versioning of packages in the container`
The status of the issue: `Container guidelines for versioning of packages in the container` of project: `atomic-wg` has been updated to: Closed as Fixed by jberkus. https://pagure.io/atomic-wg/issue/235 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
The status of the issue: `VFAD: Settle container policy open questions` of project: `atomic-wg` has been updated to: Closed as Fixed by jberkus. https://pagure.io/atomic-wg/issue/238 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
jberkus added a new comment to an issue you are following: `` VFAD has been held. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #235 `Container guidelines for versioning of packages in the container`
The issue: `Container guidelines for versioning of packages in the container` of project: `atomic-wg` has been assigned to `maxamillion` by jberkus. https://pagure.io/atomic-wg/issue/235 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #243 `Require DESCRIPTION label for FLIBS containers`
The issue: `Require DESCRIPTION label for FLIBS containers` of project: `atomic-wg` has been assigned to `jberkus` by jberkus. https://pagure.io/atomic-wg/issue/243 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #244 `require, supply guidelines for "run" label for container in FLIBS`
The issue: `require, supply guidelines for "run" label for container in FLIBS` of project: `atomic-wg` has been assigned to `jberkus` by jberkus. https://pagure.io/atomic-wg/issue/244 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #242 `Clarify requirements for INSTALL / UNINSTALL labels`
The issue: `Clarify requirements for INSTALL / UNINSTALL labels` of project: `atomic-wg` has been assigned to `dustymabe` by jberkus. https://pagure.io/atomic-wg/issue/242 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: Schedule for Container Policy VFAD
On 03/09/2017 07:50 AM, Daniel J Walsh wrote: > Sure I can help on this depending on the date. > Tommorrow. Can you dial in at 2pm? -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
jberkus added a new comment to an issue you are following: `` Link for VFAD issues is now here: https://pagure.io/atomic-wg/roadmap?status=Open_stones==2017-03-10+VFAD `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238 ___ 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`
jberkus added a new comment to an issue you are following: `` I'm going to schedule a meeting for next week to hash this out with the whole Atomic WG that can make it. `` 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
Fedora Atomic VFAD 2: Container Guidelines
We will be having a VFAD this Friday (March 10) to update and revise the Container Guidelines based on the reviews of the first containers submitted to FLIBs. The tentative schedule for this VFAD is: EST UTC 10:00-12:00 15:00-17:00 Part I 12:00-13:00 17:00-18:00 Break 13:00-15:00 18:00-20:00 Part II A specific agenda will be published Wednesday and a BlueJeans link on Thursday. If you can only attend part of the FAD because of your time zone, please update the Pagure issue with your availability and specific issues you care about so that we can adjust the agenda: https://pagure.io/atomic-wg/issue/238 This VFAD will consist of discussion of each issue followed by updating of the container guidelines. Some items may require follow-up, but the goal is to get all items settled during the VFAD. Issues covered by this VFAD are here: https://pagure.io/atomic-wg/issues?status=Open=VFAD If you have additional issues, please add them to Pagure, and make sure to tag them VFAD/containers. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
jberkus added a new comment to an issue you are following: `` The list of issues for this VFAD is here: https://pagure.io/atomic-wg/issues?status=Open=VFAD `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #244 `require, supply guidelines for "run" label for container in FLIBS`
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` For containers submitted to FLIBS, the "run" label should be REQUIRED in order to provide users with an example of how to use the container. In many cases, this would be a sample "docker run" command, ideally one which will work with the Atomic CLI. The problem with using the "run" label for containers which cannot work with the Atomic CLI is that Atomic will try to use that command anyway. It's possible that we want a second, "usage" label for those. Discuss. Earlier discussion on Mailing List: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/BJIWOVLORXWVLJHQOD2XW2T3YN333G4Q/#QH2SJK35GDX2UNHBLAFD5PLWPQY5IS6Q `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/244 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #243 `Require DESCRIPTION label for FLIBS containers`
jberkus added a new comment to an issue you are following: `` Link to discussion about this proposal: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/BJIWOVLORXWVLJHQOD2XW2T3YN333G4Q/#QH2SJK35GDX2UNHBLAFD5PLWPQY5IS6Q `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/243 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #243 `Require DESCRIPTION label for FLIBS containers`
jberkus reported a new issue against the project: `atomic-wg` that you are following: `` We should require a "description" label in FLIBS containers. This would contain a long, narrative description of the container and how it's supposed to be used, intended for human readability. This would include, for all containers: * what service/software the container provides It would also include all of the following which are applicable to the container: * what purpose it fulfills in a larger infrastructure * what each VOLUME in the container is for and what kinds of storage they need * any details about dependencies on other container images * links to documentation or software project pages * any special requirements the container has (like lots of RAM, or sound server access) * details on any required configuration, or links to documentation on configuration `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/243 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
jberkus added a new comment to an issue you are following: `` Waiting on @maxamillion to confirm, though, since he's required for this. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`
jberkus added a new comment to an issue you are following: `` What is people's schedule for the day? Presumaby if @goern and @ttomecek are in Westford for the day, they may have other meetings? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/238 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
