July 2017 - cloud - Fedora mailing-lists

[atomic-wg] Issue #299: Concerns related to enabling Atomic Host CloudImages compose in Rawhide for multi-arches
by Sinny Kumari 19 Jul '17

19 Jul '17

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` I am working on enabling Atomic Host CloudImages in Fedora 27 onward for multi-arches which includes aarch64 and ppc64le. Required changes has been made in Fedora config to enable qcow2 and raw images [Link - https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_361] . It seems making above changes is not sufficient because we are seeing all related builds failing for both arches. One of the failed koji build link - https://koji.fedoraproject.org/koji/taskinfo?taskID=20304853 After debugging cause of failure (started with ppc64le), I see following two issues: 1. kickstart file used for building Atomic CloudImage has arch specific content at line https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_35 . Possible solution ----------------------- We can remove x86_64 mention with something generic like: basearch=$(uname -i) and replacing x86_64 with $basearch should fix this. 2. I see that in kickstart fedora-atomic.ks [ https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_27 ], we don't use autopart (used by all other variants' kickstart) to create partition. Instead of autopart, we create partitions manually by using part. This leads to anaconda text based installation failure with error message "storage configuration failed: failed to find a suitable stage1 device." on ppc64le [ https://kojipkgs.fedoraproject.org//work/tasks/4883/20304883/screenshot.ppm ] It seems required PReP partition is not getting created for ppc64le arch. If I add into kickstart file "part prepboot --fstype "PPC PReP Boot" --size=10" to create PReP partition on ppc64le, I get successful running AH CloudImage on ppc64le (tried locally) . But, this would again add-up arch-specific changes in kickstart file. I would like to know your thoughts on getting them fixed in proper way. Note: Debugging issue on aarch64 is still pending which might bring-up some additional concern. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/299

3 12

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by dusty＠dustymabe.com 17 Jul '17

17 Jul '17

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2017-07-19 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/

1 0

[atomic-wg] Issue #303: Do at least 1-2 more 25 releases, or just switch to /updates
by Colin Walters 16 Jul '17

16 Jul '17

walters reported a new issue against the project: `atomic-wg` that you are following: `` In https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/ and https://pagure.io/atomic-wg/issue/228 we did some handwaving about releases that IMO was very vague :smile: Now that 26 is out, every 25 AH will simply stop receiving updates without admin intervention (either https://fedoraproject.org/wiki/Atomic_Host_upgrade or `rpm-ostree rebase fedora-atomic/25/x86_64/updates/docker-host`). I really think we need at least some grace period here. Also I'd like some time to polish off end-of-life notification better. So I propose we add infrastructure to continue promotion of /updates -> stable for the 25 ref for at least 2-3 releases. However, we wouldn't release new media (cloud images, ISO) for 25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/303

2 1

[atomic-wg] Issue #271: support ENA for fedimg upload
by Dusty Mabe 16 Jul '17

16 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` https://aws.amazon.com/blogs/aws/elastic-network-adapter-high-performance-n… we support this in our kernel so we should probably enable it. We need to: 1 - enable it in fedimg and underlying tools if needed 2 - see if having it enabled on all AMIs affects being able to launch on certain instance types (we would like to be able to enable it on all AMIs and just have it be a no-op on instances that don't support it. cc @sayanchowdhury `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/271

1 4

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage
by Dusty Mabe 16 Jul '17

16 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We have system containers storing things in /var/lib/containers/storage. We have docker/moby containers storing things in /var/lib/docker. We might move to overlay2 on a single big root partition in the future, we might not. We have discussed these topics in a few maililng list threads [[1](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-April/msg00031.html)] [[2]()] and also ran out of storage on atomic host before [[3](https://bugzilla.redhat.com/show_bug.cgi?id=1391725)] Let's put some thought into this and try to figure out a proper strategy going forward. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281

6 31

[atomic-wg] Issue #302: F26s will not provision on Azure
by Brent Baude 15 Jul '17

15 Jul '17

baude reported a new issue against the project: `atomic-wg` that you are following: `` The F26 AH and Cloud images will not provision on Azure due to a missing udf kernel module. The udf kernel module is in the kernel-modules-extra. As of cloud-init-0.7.9, the WALinuxAgent is not needed for provisioning on Azure. The F26 AH and Cloud images should theoretically be able to boot on Azure now. However, vm boot process with cloud-init, we have to load a cdrom device with the azure/cloud-init metadata on it. In Azure, that cdrom device uses a udf filesystem. Unfortunately the udf kernel driver is in the kernel-modules-extra package and is not available on the base images. The mount fails and therefore fails the attempt to use cloud-init's data source. I have filed a bugzilla to request that the udf driver be moved to main here -> https://bugzilla.redhat.com/show_bug.cgi?id=1471314 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/302

2 1

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/215

3 5

[atomic-wg] Issue #210 `Move systemd-systemd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/syst… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/210

2 1

[atomic-wg] Issue #217: Move python container image from Fedora-Dockerfiles GitHub into DistGit
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` assigned to @hhorak - any updates? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/217

1 0

[atomic-wg] Issue #217: Move python container image from Fedora-Dockerfiles GitHub into DistGit
by Dusty Mabe 14 Jul '17

14 Jul '17

The issue: `Move python container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been assigned to `hhorak` by dustymabe. https://pagure.io/atomic-wg/issue/217

1 0

[atomic-wg] Issue #218 `Move postgresql container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/postgresql `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/218

3 2

[atomic-wg] Issue #222 `Move systemd-apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/apac… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/222

3 2

[atomic-wg] Issue #203 `Move apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/203

2 2

[atomic-wg] Issue #208 `Move mariadb container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/mariadb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/208

4 4

[atomic-wg] Issue #216: Move nodejs container image from Fedora-Dockerfiles GitHub into DistGit
by Dusty Mabe 14 Jul '17

14 Jul '17

The status of the issue: `Move nodejs container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/216

1 0

[atomic-wg] Issue #216: Move nodejs container image from Fedora-Dockerfiles GitHub into DistGit
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` There is a nodejs container in the registry now https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/216

1 0

[atomic-wg] Issue #132: Fedora AMIs should use corresponding s3 mirrors
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` there are plans to mirror content in s3 again which should solve this issue: https://pagure.io/fedora-infrastructure/issue/6022 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/132

1 0

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We are now *releasing* OSTree content every two weeks rather than every night ([link](http://www.projectatomic.io/blog/2017/02/matching-fedora-ostree-released-content-with-each-2week-atomic-release/)). Next we would like to make the image names that get produced reflect in some way the OSTree content that is baked into the image. During recent development @jlebon actually suggested that we use date based versions for Fedora Atomic Host: something like `version: 20170130.0`, `version: 20170130.1`, `version: 20170215.0`, etc... Let's decide on what we want the versioning scheme to look like and also what the image names "could look like" as a result of this. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/229

6 16

[atomic-wg] Issue #237 `Migrate fedimg EC2Service from libcloud to boto`
by Sayan Chowdhury 14 Jul '17

14 Jul '17

sayanchowdhury reported a new issue against the project: `atomic-wg` that you are following: `` fedimg `EC2Service` right now uses libcloud to create the AMIs. Libcloud does not support a lot of features whereas boto has a better documentation and provides the missing bits. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/237

2 2

[atomic-wg] Issue #232 `ssh issue on libvirt based images`
by Kushal Das 14 Jul '17

14 Jul '17

kushal reported a new issue against the project: `atomic-wg` that you are following: `` During our Atomic tests, after disabling the chronyd service, we reboot the VM. After that the ssh serivce is not coming back on time. This VM has one vcpu in it. Sometimes we saw behaviour on Vagrant libvirt (which boots with 2 VCPU(s)), and at least once with Vagratnt Virtualbox before. One such example of failure: https://apps.fedoraproject.org/autocloud/jobs/2188/output#30 https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… is the thread in the mailing list on the same topic. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/232

6 9

[atomic-wg] Issue #246 `Period of fedimg downtime`
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` There appears to be a period of downtime where fedimg was not uploading AMIs Fedora-Atomic-25-20170226.0.x86_64 EC2 (us-west-2) ami-5051d230 hvm gp2 Fedora-Atomic-25-20170304.0.x86_64 EC2 (ap-northeast-1) ami-8cb2e5eb hvm gp2 Attached is a run of [get_ami.py](https://pagure.io/fedora-websites/blob/master/f/tools/get_ami.py) which shows a gap. Can someone investigate why this happened? <!!image> `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/246

1 3

[atomic-wg] Issue #260: work items to harmonize releng pungi/ostree artifact creation
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` OK. Some time later - an update on this ticket - Highlighting OSTree commits as the delivered artifact We will be setting an ostree version that corresponds to the pungi compose ID. See OSTREE_VERSION_FROM_LABEL_DATE_TYPE_RESPIN in https://pagure.io/pungi/pull-request/592. We are already using this for rawhide. - If we change the compose ID - what about Multi-Arch? We are not planning to change the compose ID any longer. Additionally with bodhi calling pungi we will be able to support multi-arch better. - pungi compose ids are inflexible Still using the same compose ID as in the past so no issues here - Getting rid of bodhi creation of ostrees planned and in progress: https://pagure.io/atomic-wg/issue/300 - Coupling ostree creation with image creation Since we are also planning to move mash to pungi we might as well add image/ISO creation to pungi and have it do everything all at the same time. This would mean we no longer have timing issues **Identified Action Items** 1. We can work on patches to pungi to accept an ostree version as input and know what to do with it. This would be a version that would be input for image creation, not necessarily for ostree tree compose creation. i.e. build a qcow image for ostree version 25.100 that is in the ostree repo. Assumes the ostree version already exists. Done. https://pagure.io/pungi/pull-request/592 2. We can work on patches to pungi to that can determine what the ostree version should be and set that during ostree tree compose time. See https://pagure.io/pungi/pull-request/575 Same as above 3. We need to provide to releng a script that can be run so they can "detect" what ostree version to specify as a compose id (I believe this assumes we keep ostree/image creation decoupled) No need. Just use OSTREE_VERSION_FROM_LABEL_DATE_TYPE_RESPIN 4. Determine priority of having bodhi call pungi to create ostrees high :) 5. We need to determine what we want the OSTree version to look like for Fedora 26 (right now the atomic WG proposal is `$majorversion.$year$month$day.$serial` `26.20170320.0`. Please comment in https://pagure.io/atomic-wg/issue/229 We will get 26.20170320.0 6. Figure out if a compose id like `Fedora-Atomic-26-26.20170220.0_0` is possible and if anything breaks as a result. No Need `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/260

1 0

[atomic-wg] Issue #125: Fedora-Dockerfiles examples for Kubernetes
by Dusty Mabe 14 Jul '17

14 Jul '17

The status of the issue: `Fedora-Dockerfiles examples for Kubernetes` of project: `atomic-wg` has been updated to: Closed by dustymabe. https://pagure.io/atomic-wg/issue/125

1 0

[atomic-wg] Issue #125: Fedora-Dockerfiles examples for Kubernetes
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` Fedora Dockerfiles is pretty much dead now that we have FLIBS. I'm going to close this. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/125

1 0

[atomic-wg] Issue #166: RFE : vagrant user with id=1000
by Langdon White 14 Jul '17

14 Jul '17

langdon added a new comment to an issue you are following: `` Woo! Saw this in my latest vagrant box! Thanks! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/166

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud July 2017