The status of the issue: `[VOTE] To mark recent failure on Atomic images as non blocking` of project: `atomic-wg` has been updated to: Closed by dustymabe.
https://pagure.io/atomic-wg/issue/171
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
It would be great if we can have some planned virtual meetings every few months to discuss the atomic working group and current issues that extend into discussions.
Should we meet every so often (not necessarily for an entire day) to sync up on issues and work through the backlog of items to clear out cruft and/or promote forgotten priorities?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/192
The status of the issue: `RFE : vagrant user with id=1000` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/166
dustymabe added a new comment to an issue you are following:
``
This is done now and in the fedora 26 artifacts that were just delivered.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/166
The status of the issue: `F26 Talking Points` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/262
dustymabe added a new comment to an issue you are following:
``
f26 is out - and I think this can be closed
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/262
adamwill reported a new issue against the project: `atomic-wg` that you are following:
``
Apparently, it was decided that Fedora Atomic Host images should include only the locales 'officially supported' by RHEL 7 - see https://bugzilla.redhat.com/show_bug.cgi?id=1430182 , jlebon says it was decided to apply the same choice to Fedora as to RHEL.
This is entirely out of step with all other Fedora flavors, though, I believe. These include far, far more locales. The 'RHEL supported' list doesn't include such obvious and widely-used locales as en_CA and en_AU. I'm not sure it makes sense to just decide the RHEL 'supported locales' list is an appropriate basis for the list of locales to include in Fedora images.
[Transferred from https://bugzilla.redhat.com/show_bug.cgi?id=1459341 as requested there].
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/282
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We want to have our users have the ability to use static deltas when moving from f25 to f26. We haven't yet moved to a unified repo but can give the users static deltas by simply pulling in the last f25 commit and then generating a static delta as described [here](https://pagure.io/releng/issue/6871#comment-446988).
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/291
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Example failed koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=20474689
We recently started having ostree re-use the local mirror of content from the ISO image if it existed. We have it look in `/ostree/repo` and `/run/install/repo` in [this line of code](https://github.com/rhinstaller/anaconda/pull/1119/files#diff-3e2b7e1a…. At least for fedora 25 (according to the [lorax template](https://pagure.io/fedora-lorax-templates/blob/f25/f/atomic-installer/lorax-configure-repo.tmpl#_8) the real location was `/run/install/repo/content/repo`. However `/run/install/repo/` is an actual directory on our media and has several things in there that anaconda uses. So `/run/install/repo` exists and is not an ostree repo.
This means that any ostree anaconda install that is initiated from a non-ostree install tree (like our atomic host qcows are in our pungi composes) will fail with this error:
```
The following error occurred while installing. This is a fatal error and
installation will be aborted.
Failed to pull from repository: g-io-error-quark: Opening objects/ directory:
openat: No such file or directory (1)
```
I'm thinking we should
1. fix the installer to look for the right location (PR [here](https://github.com/rhinstaller/anaconda/pull/1126))
2. possibly make ostree not fail if a provided reference repo is bogus.
Thoughts?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/301
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We're trying to balance the pros/cons of trying to have both kubernetes and origin in Fedora. We're trying to find a group of people interested in helping us maintain kubernetes within Fedora. This includes maintaining the rpm, fielding bug reports, making sure docs stay up to date, and trying to make sure upgrades work.
From our preliminary discussion i know a few people:
- @strigazi
- @dimtheo
- @jasonbrooks
- @jberkus
Can we get other people who are interested in helping out add their name to this issue?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/287
walters opened a new pull-request against the project: `fedora-atomic` that you are following:
``
Rename treefile to match ref
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/63
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
mostly a tracker ticket for getting bodhi to create ostrees by using pungi. This helps us by:
- only one way that Fedora Infra creates ostrees (through pungi)
- allows us to get ostree versions of the form `26.20170701.0`
- delete fedmsg-atomic-composer code
- handle multiarch for Atomic Host
related bodhi ticket: https://github.com/fedora-infra/bodhi/issues/1182
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/300
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
The way it is now:
Currently, the rootFS is sized at 3GB, fixed, and the Docker partition is 40% of the remaining space. This causes new users to run out of disk space if they do layering, ostree unlock, install a bunch of system containers, or even just run up the logs, even if they have plenty of physical disk space.
My suggestion for a new default is:
* RootFS: 25% of disk space, with a minimum of 3GB and a maximum of 16GB
* Docker Partition: 50% of total disk space (or 65% of remaining space), min 2GB
* Unallocated: 25% of disk space.
This would mean, for a new install:
Disk Root Docker Unallocated
8GB 3GB 4GB 1GB
32GB 8GB 16GB 8GB
200GB 16GB 100GB 84GB
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/197
The Fedora Atomic Working group has a proposed "Virtual" Fedora Activity
Day planned for the last week of July. Please consider joining us and or
brainstorming on details of the session in the ticket:
https://pagure.io/atomic-wg/issue/294
Dusty
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Target Date: Last week of July
Let's have a VFAD to help us find all of our docs that exist in the wiki and create an index of all of them. I suggest we actually have the index as our README for atomic-wg in pagure as well as our landing page on the wiki, but this may prove problematic. Really it would be great if we could have wiki support markdown formatting so we can just replicate the content between both places.
I suggest that we have a short 30minute video session and then a period of IRC collaboration as people go off to find docs (food break can be in here somewhere for breakfast/lunch/dinner depending on where you are). Then we can close with another 30 minutes video session to recap and possibly identify missing documentation and create tickets to get those docs created.
This will help us lead up to the Docs workshop at FLOCK.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/294
walters opened a new pull-request against the project: `fedora-atomic` that you are following:
``
manifest: Drop updates-testing by default
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/66
dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following:
``
Rename treefile to match ref
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/65
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
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
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Let's collect ideas for talk/workshop proposals at [Flock](https://flocktofedora.org/)
Due date for CFP submissions is June 15th
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/279
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-07-12 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/