dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Carried from this mailing list discussion: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-Jul…
We've had requests from users for btrfs support and we've had several bugs filed where users were trying to configure a system to use btrfs in the installer and it falling flat on it's face. The below list can be updated at any time to include a list of bugs that are releated to atomic ostree/rpm-ostree tech being able to boot on btrfs filesystems and having the installer support it:
- [BZ#1039124](https://bugzilla.redhat.com/show_bug.cgi?id=1039124) RFE: Allow /boot on BTRFS, tracker
- [BZ#1415846](https://bugzilla.redhat.com/show_bug.cgi?id=1415846) Atomic install boot loader fails with btrfs option
Some of these bugs aren't limited to rpm-ostree/ostree, but also to anaconda and enforced policy within anaconda.
Please add other bugs to this list.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/306
ttomecek reported a new issue against the project: `atomic-wg` that you are following:
``
@ignatenkobrain had an interesting idea this morning on IRC: what if all our docker base images had `--tsflags=nodocs` enabled on by default? This could be easily achieved by changing the configuration in `/etc/dnf/dnf.conf`.
I'm very much interested in your opinion. I personally like it and am all for it.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/308
dimtheo reported a new issue against the project: `atomic-wg` that you are following:
``
this is to let everyone know what cinder volumes will only attach but will not mount . I have been told that this is because of the kube version in atomic and this is fixed in kube 1.6.4 +
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/305
The status of the issue: `Do at least 1-2 more 25 releases, or just switch to /updates` of project: `atomic-wg` has been updated to: Open by dustymabe.
https://pagure.io/atomic-wg/issue/303
dustymabe added a new comment to an issue you are following:
``
will see if we can get that fixed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/303
walters added a new comment to an issue you are following:
``
Fixing the updates ref should literally just be:
`ln -sfr 25/refs/heads/fedora-atomic/25/x86_64/{docker-host,updates/docker-host}`
I'd like to not set precedent for abandoning refs.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/303
The status of the issue: `Do at least 1-2 more 25 releases, or just switch to /updates` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/303
dustymabe added a new comment to an issue you are following:
``
This is done - the f25 release ref will get updated every time bodhi runs now. One side effect is that the updates ref no longer gets updated.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/303
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
It was discovered today that the released qcow images from yesterday's release are following the updates ref (`fedora/26/x86_64/updates/atomic-host`) when they should be following the two week release ref (`fedora/26/x86_64/atomic-host`).
This has been resolved in https://pagure.io/fedora-kickstarts/pull-request/271
In order to resolve this please rebase your machines to the proper ref and reboot:
```
# rpm-ostree rebase fedora/26/x86_64/atomic-host
# reboot
```
If you have moved passed version `26.91` then you will notice packages get downgraded. This is expected.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/307
dustymabe added a new comment to an issue you are following:
``
VFAD complete - lots of documentation found! action items are:
Action Items:
- @jberkus: by EOD-USA Monday will update outline, create example of converting outline to issue title and doc name
* outline will be updated here:https://github.com/projectatomic/atomic-host-docs/blob/master/outline.…
- @dustymabe to creates issues in atomic-host-docs repo for beginning of TOC to Quickstart
- @drakonis to creates issues in atomic-host-docs repo for Quick Start to Using Ostree section
- @sayanchowdhury to create issues in atomic-host docs repo for Using Ostree Section to Docker
- @jasonbrooks to create issues in atomic-host-docs repo for Docker section to end of TOC
- @jberkus + @trishnag - create directory structure within the atomic-host docs site
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/294
ttomecek added a new comment to an issue you are following:
``
ping
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/284
FYI: The images from yesterday's release are not following the two week release
ref. Please follow the instructions in the following ticket if you use the cloud
images and want to follow the two week release ref:
https://pagure.io/atomic-wg/issue/307
Dusty
The status of the issue: `Kubernetes on system-containers in OpenStack Magnum` of project: `atomic-wg` has been updated to: Closed as Duplicate by jberkus.
https://pagure.io/atomic-wg/issue/292
jberkus added a new comment to an issue you are following:
``
Closed as duplicate
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/292
jberkus added a new comment to an issue you are following:
``
Closed as duplicate since it's moved to Kubernetes sig.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/304
The status of the issue: `Update to kubernetes 1.7.x` of project: `atomic-wg` has been updated to: Closed as Duplicate by jberkus.
https://pagure.io/atomic-wg/issue/304
full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-26/fedora_atomic…
#fedora-meeting-1: fedora_atomic_wg
Meeting started by jbrooks at 17:03:13 UTC (full logs).
Meeting summary
Roll Call (jbrooks, 17:03:19)
action items from last meeting (jbrooks, 17:05:10)
ACTION: jberkus strigazi to continue moving kube issues to new
kube-sig tracker (jbrooks, 17:10:03)
ACTION: jberkus to write blog post for fedora magazine/pa.io on
changes (jbrooks, 17:10:48)
atomic calendar created
https://apps.fedoraproject.org/calendar/atomic/ (dustymabe, 17:11:52)
patch sent to infra for f25 atomic ref
https://pagure.io/atomic-wg/issue/303#comment-450097 (dustymabe,
17:12:39)
kubernetes sig pagure repo created
https://pagure.io/atomic/kubernetes-sig (dustymabe, 17:13:21)
http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=39b719c
(puiterwijk, 17:13:40)
ACTION: dusty to write a comprehensive blog post on updating f25->f26
and will include update about f25 updates ref (dustymabe, 17:14:07)
ACTION: dustymabe jberkus to write doc on docs vfad with all resources
linked (dustymabe, 17:14:23)
ACTION: jbrooks to create kube-sig ticket about versions discussion
(jbrooks, 17:15:56)
open floor (jbrooks, 17:16:39)
atomic qcow/vagrant images from yesterday's release are set to update
from the wrong ref (the updates ref) - we are fixing this, but we need
to communicate this out to users (dustymabe, 17:18:21)
ACTION: dustymabe to communicate out issue with ref in atomic cloud
images (dustymabe, 17:21:48)
ACTION: dustymabe to create ticket to track RFE for rawhide based
containers to be made available from registry.fedoraproject.org
(dustymabe, 17:30:28)
http://pkgs.fedoraproject.org/cgit/container/container-engine.git/
(jbrooks, 17:31:21)
Meeting ended at 17:35:29 UTC (full logs).
Action items
jberkus strigazi to continue moving kube issues to new kube-sig tracker
jberkus to write blog post for fedora magazine/pa.io on changes
dusty to write a comprehensive blog post on updating f25->f26 and will
include update about f25 updates ref
dustymabe jberkus to write doc on docs vfad with all resources linked
jbrooks to create kube-sig ticket about versions discussion
dustymabe to communicate out issue with ref in atomic cloud images
dustymabe to create ticket to track RFE for rawhide based containers
to be made available from registry.fedoraproject.org
Action items, by person
dustymabe
dustymabe jberkus to write doc on docs vfad with all resources linked
dustymabe to communicate out issue with ref in atomic cloud images
dustymabe to create ticket to track RFE for rawhide based containers
to be made available from registry.fedoraproject.org
jberkus
jberkus strigazi to continue moving kube issues to new kube-sig tracker
jberkus to write blog post for fedora magazine/pa.io on changes
dustymabe jberkus to write doc on docs vfad with all resources linked
jbrooks
jbrooks to create kube-sig ticket about versions discussion
People present (lines said)
jbrooks (81)
dustymabe (53)
jberkus (30)
zodbot (16)
puiterwijk (11)
sayan (3)
kushal (1)
miabbott (1)
jzb (1)
walters (1)
strigazi added a new comment to an issue you are following:
``
>
> Let's do the simple solution first then :)
> stable in rawhide and stable-1 in fedora stable
>
> some sort of policy like this would be good to put in a readme over in https://pagure.io/atomic/kubernetes-sig
> Since 1.7 is now in rawhide and we have the above policy should we leave this issue open?
Good idea! We can close this and add a README in kubernetes-sig as you said.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/304
The issue: `Do at least 1-2 more 25 releases, or just switch to /updates` of project: `atomic-wg` has been assigned to `dustymabe` by dustymabe.
https://pagure.io/atomic-wg/issue/303
The status of the issue: `Start using new mailing list/IRC channel around f26 release time` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/295
dustymabe added a new comment to an issue you are following:
``
closing this as this has been decided and implemented.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
The status of the issue: `Cannot install to bare metal using kickstart due to ref name problems in f26 release` of project: `atomic-wg` has been updated to: Closed as Fixed by jberkus.
https://pagure.io/atomic-wg/issue/296
jberkus added a new comment to an issue you are following:
``
Blogged, closting.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/296
dustymabe added a new comment to an issue you are following:
``
> Let's do the simple solution first then :)
> stable in rawhide and stable-1 in fedora stable
some sort of policy like this would be good to put in a readme over in https://pagure.io/atomic/kubernetes-sig
Since 1.7 is now in rawhide and we have the above policy should we leave this issue open?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/304
The status of the issue: `Identify group of people interested in maintaining kubernetes` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/287
On 07/12/2017 12:56 PM, Dusty Mabe wrote:
>
> We recently changed the ref for atomic host in Fedora 26 to be
> `atomic-host` rather than `docker-host`.
>
> Similarly we'd like to change the name of the file within the repo [1]
> from fedora-atomic-docker-host.json to fedora-atomic-host.json.
>
> If anyone is pulling from this repo and building trees please update
> your files to use the new filename for the master and f26 branches.
>
> We have temporarily left a symlink for compatibility. I'll be removing
> that in a week or two and updating this mail when that happens.
>
> Dusty
>
> [1] https://pagure.io/fedora-atomic/blob/70e320ccb557ffd7f1bb14d6a6f0748843dc3d…
>
The symlink has been removed in the following PRs:
[1] https://pagure.io/fedora-atomic/pull-request/67
[2] https://pagure.io/fedora-atomic/pull-request/68
jflory7 added a new comment to an issue you are following:
``
Hey all, just thought I'd add that I'm interested in helping use and test k8s on Fedora. Still getting introduced to everything, but this is definitely something I'd be interested in helping with where possible! I'm subscribed to the kubernetes-sig repo now.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/287
sinnykumari added a new comment to an issue you are following:
``
>
> Does adding reqpart in fedora-atomic kickstart seem legit? If yes, I'd like to create a pull request for the same.
>
> Seems legit, although we may want to wait for the anaconda support for $basearch in ostreesetup line before we do this.
Sure.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/299
dustymabe added a new comment to an issue you are following:
``
> Does adding reqpart in fedora-atomic kickstart seem legit? If yes, I'd like to create a pull request for the same.
Seems legit, although we may want to wait for the anaconda support for $basearch in ostreesetup line before we do this. @walters is there an open issue for that against anaconda?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/299
sinnykumari added a new comment to an issue you are following:
``
>
> we need to experiment with reqpart and see if it does the right thing for atomic - are you able to run imagefactory locally and experiment?
> Haven't checked how reqpart works, will look into it.
>
> Yes, we can use reqpart in the fedora-atomic.ks to auto create architecture specific partitions. Image created and ran successfully with this change on ppc64le and x86_64 locally.
Does adding reqpart in fedora-atomic kickstart seem legit? If yes, I'd like to create a pull request for the same.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/299
jasonbrooks added a new comment to an issue you are following:
``
another test
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
Some of you have been subscribed by me because of your involvement
with the Fedora Atomic Working Group. Unsubscribe if you feel this
was in error.
Dusty
TL;DR There is a new fedora atomic mailing list [1] and IRC channel [2], but the mailing list
should only be used for automated messages and the IRC channel should be used only
when something extremely Fedora specific (like releng bits) is being discussed. Otherwise
please use the upstream project atomic mailing list [3] and IRC channel [4] for everything.
The cloud* list and IRC channel should be no longer used for atomic specific discussions.
In an attempt to minimize the confusion around the relationship between
the Fedora Atomic Working Group and the Fedora Cloud SIG we have decided [5]
to have a new mailing list [1] and irc channel [2] for Fedora Atomic.
Since there is an upstream project atomic mailing list [3] and irc channel [4] already
we have decided that the new fedora atomic mailing list and irc channels should
be narrow in focus and actually push discussion towards the upstream project
atomic mailing list and irc channel. This is mostly so we can get more people
talking about the same problems in one place and have some cross pollination.
The new communication model:
Mailing Lists:
* atomic(a)lists.fedoraproject.org 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-devel(a)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.
Please take this opportunity to subscribe to any new mailing lists and join any new irc
channels you find appropriate.
Dusty
[1] https://lists.fedoraproject.org/admin/lists/atomic.lists.fedoraproject.org/
[2] #fedora-atomic) on freenode
[3] https://lists.projectatomic.io/mailman/listinfo/atomic-devel
[4] #atomic on freenode
[5] https://pagure.io/atomic-wg/issue/295