March 2017 - cloud - Fedora Mailing-Lists

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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

2 years

3
5
0 / 0

[atomic-wg] Issue #210 `Move systemd-systemd container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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

2 years

2
1
0 / 0

[atomic-wg] Issue #218 `Move postgresql container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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

2 years

3
2
0 / 0

[atomic-wg] Issue #222 `Move systemd-apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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

2 years

3
2
0 / 0

[atomic-wg] Issue #203 `Move apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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 years

2
2
0 / 0

[atomic-wg] Issue #208 `Move mariadb container image from Fedora-Dockerfiles GitHub into DistGit`

by Adam Miller

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

2 years

4
4
0 / 0

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

by Dusty Mabe

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

2 years

6
16
0 / 0

[atomic-wg] Issue #237 `Migrate fedimg EC2Service from libcloud to boto`

by Sayan Chowdhury

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 years

2
2
0 / 0

[atomic-wg] Issue #232 `ssh issue on libvirt based images`

by Kushal Das

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.o... 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

2 years

6
9
0 / 0

[atomic-wg] Issue #246 `Period of fedimg downtime`

by Dusty Mabe

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

2 years

1
3
0 / 0

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud March 2017