cloud May 2017

cloud@lists.fedoraproject.org

13 participants
84 discussions

[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 #184 `ISO file is missing`
by Pagure 14 Jul '17

14 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Try to download the ISO at this location, as supplied by GetFedora.org: https://download.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2… You'll find that there is no file there, and your download does not start. There is currently no way to download the Atomic ISO. In fact, it appears that none of the alternate downloads are available for 12/7: http://mirror.math.princeton.edu/pub/alt//atomic/stable/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/184

3 14

[atomic-wg] Issue #192 `atomic working group - periodic virtual FADs`
by Pagure 14 Jul '17

14 Jul '17

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

2 2

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`
by Pagure 13 Jul '17

13 Jul '17

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

4 17

[atomic-wg] Issue #279: talk/workshop proposals for Flock
by Dusty Mabe 11 Jul '17

11 Jul '17

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

5 14

[atomic-wg] Issue #261 `Issue Tracker for F26 release blockers`
by Dusty Mabe 10 Jul '17

10 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This ticket will be used throughout the f26 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on. **Blocker Bugs** - **Important Bugs** - none Over time only the description of this bug will be edited for updates. Please do not add comments to this issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261

3 7

[atomic-wg] Issue #269: fedimg: don't use 'builder' instance for uploading AMIs
by Dusty Mabe 05 Jul '17

05 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` we hit [an issue](https://pagure.io/releng/issue/6761) yesterday because fedimg failed upload all of our AMIs for that day's build of FAH. This is most likely due to the fact that we use a builder instance to pull the cloud disk image and then create the EBS. Bringing up the builder instance can fail (commodity hardware in EC2) and thus can lead to situations like this. It would be much better if we don't use a builder instance. This is being worked on in https://github.com/fedora-infra/fedimg/issues/42. This ticket will track that work that is 'two weeks away' from completion. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269

2 3

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud May 2017