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
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
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
holms (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
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
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
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
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 --
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 --
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
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
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
___
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 --
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 --
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
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
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
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
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
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
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.
``
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
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 --
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 --
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
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
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
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
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
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
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
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
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
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
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,
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
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
ket
> 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
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
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
(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
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
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
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
)
* 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
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
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
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 --
olic 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 pre
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 --
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 --
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
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
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,
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
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
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
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
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.
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
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
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
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
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
___
/ 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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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
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
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
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
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 --
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
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
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
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
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
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
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 unsub
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
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
://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
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
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,
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
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
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
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
1 - 100 of 223 matches
Mail list logo
