cloud July 2017

cloud@lists.fedoraproject.org

12 participants
88 discussions

[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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud July 2017