July 2017 - cloud - Fedora Mailing-Lists

[atomic-wg] Issue #133: Hand off Atlas release process for vagrant boxes to releng

by Dusty Mabe

dustymabe added a new comment to an issue you are following: `` the docs for the vagrant cloud api are sparse. I found where someone created some scripts to access the API - maybe we can clean some information from there: https://github.com/concourse/vagrant-cloud-resource/blob/master/assets/out `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/133

6 years, 3 months

1
0
0 / 0

Fedora Atomic Host Two Week Release Announcement

by noreply＠fedoraproject.org

A new Fedora Atomic Host update is available via an OSTree commit: Commit: ce555fa89da934e6eef23764fb40e8333234b8b60b6f688222247c958e5ebd5b Version: 25.154 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

6 years, 3 months

2
1
0 / 0

Atomic WG Meeting Minutes 2017-07-05

by Jerry Zhang

Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-05/fedora_atom... 17-07-05-17.00.html =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by yzhang at 17:00:21 UTC. The full logs are available athttps://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-05/fedora_at... . Meeting summary --------------- * Roll Call (yzhang, 17:00:35) * Action items from last meeting (yzhang, 17:02:49) * ACTION: maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group (yzhang, 17:03:52) * ACTION: dustymabe to propose a VFAD for wiki and docs discussion (dustymabe, 17:04:09) * ACTION: maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 (yzhang, 17:05:29) * Make fedora-minimal base image generally available (yzhang, 17:06:25) * LINK: https://pagure.io/atomic-wg/issue/290 (yzhang, 17:06:31) * ACTION: maxamillion to release the fedora-minimal base image with next container release: https://pagure.io/atomic-wg/issue/290 (yzhang, 17:13:30) * Atomic Host images omit many common locales that all other flavors include (yzhang, 17:14:31) * LINK: https://pagure.io/atomic-wg/issue/282 (yzhang, 17:14:37) * Figure out comprehensive strategy for atomic host container storage (yzhang, 17:28:01) * LINK: https://pagure.io/atomic-wg/issue/281 (yzhang, 17:28:06) * fedimg: don't use 'builder' instance for uploading AMIs (yzhang, 17:28:57) * LINK: https://pagure.io/atomic-wg/issue/269 (yzhang, 17:29:03) * open floor (yzhang, 17:33:34) * kubernetes sig (dustymabe, 17:35:17) * LINK: https://pagure.io/atomic-wg/issue/287 (dustymabe, 17:35:48) * ACTION: dustymabe to update the kubernetes thread with tracking options: https://pagure.io/atomic-wg/issue/287 (yzhang, 17:42:01) * cloud/atomic confusion (dustymabe, 17:42:32) * ACTION: dustymabe to open a ticket for cloud/atomic confusion (yzhang, 17:44:49) * open floor (dustymabe, 17:46:43) * please update the ticket and say what talks were accepted for flock https://pagure.io/atomic-wg/issue/279 (dustymabe, 17:50:36) * LINK: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.o... (dustymabe, 17:52:58) * stef from the fedora CI efforts has a proposal for actually delivering atomic host from a CI pipeline: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.o... please review that - he's going to discuss it with us next week at this meeting (dustymabe, 17:53:40) Meeting ended at 17:56:46 UTC. Action Items ------------ * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * dustymabe to propose a VFAD for wiki and docs discussion * maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 * maxamillion to release the fedora-minimal base image with next container release: https://pagure.io/atomic-wg/issue/290 * dustymabe to update the kubernetes thread with tracking options: https://pagure.io/atomic-wg/issue/287 * dustymabe to open a ticket for cloud/atomic confusion Action Items, by person ----------------------- * dustymabe * dustymabe to propose a VFAD for wiki and docs discussion * dustymabe to update the kubernetes thread with tracking options: https://pagure.io/atomic-wg/issue/287 * dustymabe to open a ticket for cloud/atomic confusion * maxamillion * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 * maxamillion to release the fedora-minimal base image with next container release: https://pagure.io/atomic-wg/issue/290 * roshi * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * yzhang (103) * dustymabe (93) * maxamillion (34) * roshi (28) * zodbot (17) * kushal (12) * jbrooks (11) * sayan (6) * ksinny (5) * walters (5) * miabbott (2) * jlebon (2) * imcleod (1) * deuscapturus (1)

6 years, 3 months

1
0
0 / 0

[atomic-wg] Issue #269: fedimg: don't use 'builder' instance for uploading AMIs

by Dusty Mabe

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

6 years, 3 months

2
3
0 / 0

2wk atomic release candidate: 20170705

by Dusty Mabe

*NOTE* The next release of Fedora 25 Atomic Host will be our last Fedora 25 based release. We will start releasing Fedora 26 based Atomic Host's from this point forward. Tomorrow we will attempt to release the 20170705 images. These images contain the following ostree version/commit: 25.154 ce555fa89da934e6eef23764fb40e8333234b8b60b6f688222247c958e5ebd5b The atomic host VM images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... The ISO image is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... The AMIs are here: Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-northeast-1) ami-95cdd1f2 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-southeast-1) ami-193fb47a hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-southeast-2) ami-67372504 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (eu-central-1) ami-d9bb1bb6 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (eu-west-1) ami-db5fb9a2 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (sa-east-1) ami-791b6e15 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-east-1) ami-e54c76f3 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-west-1) ami-fb0d229b hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-west-2) ami-baa6b6c3 hvm gp2 Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-northeast-1) ami-b7d2ced0 hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-southeast-1) ami-893ab1ea hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (ap-southeast-2) ami-083b296b hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (eu-central-1) ami-90ba1aff hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (eu-west-1) ami-5a5abc23 hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (sa-east-1) ami-351a6f59 hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-east-1) ami-40437956 hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-west-1) ami-660d2206 hvm standard Fedora-Atomic-25-20170705.0.x86_64 EC2 (us-west-2) ami-9ca5b5e5 hvm standard The diff between this and the previous released version is: ostree diff commit old: f136ff5370c0f77d9c1f4fd3ecb8e1815650d8aaf834e41a5e995a13494407e9 ostree diff commit new: ce555fa89da934e6eef23764fb40e8333234b8b60b6f688222247c958e5ebd5b Upgraded: dbus 1:1.11.12-1.fc25.x86_64 -> 1:1.11.14-1.fc25.x86_64 dbus-libs 1:1.11.12-1.fc25.x86_64 -> 1:1.11.14-1.fc25.x86_64 hostname 3.15-7.fc24.x86_64 -> 3.15-8.fc25.x86_64 kernel 4.11.6-201.fc25.x86_64 -> 4.11.8-200.fc25.x86_64 kernel-core 4.11.6-201.fc25.x86_64 -> 4.11.8-200.fc25.x86_64 kernel-modules 4.11.6-201.fc25.x86_64 -> 4.11.8-200.fc25.x86_64 libgcrypt 1.6.6-1.fc25.x86_64 -> 1.7.8-1.fc25.x86_64 nfs-utils 1:2.1.1-5.rc3.fc25.x86_64 -> 1:2.1.1-5.rc4.fc25.x86_64 rsync 3.1.2-3.fc25.x86_64 -> 3.1.2-4.fc25.x86_64 skopeo 0.1.19-1.dev.git0224d8c.fc25.x86_64 -> 0.1.22-1.git5d24b67.fc25.x86_64 skopeo-containers 0.1.19-1.dev.git0224d8c.fc25.x86_64 -> 0.1.22-1.git5d24b67.fc25.x86_64 systemd 231-15.fc25.x86_64 -> 231-17.fc25.x86_64 systemd-container 231-15.fc25.x86_64 -> 231-17.fc25.x86_64 systemd-libs 231-15.fc25.x86_64 -> 231-17.fc25.x86_64 systemd-pam 231-15.fc25.x86_64 -> 231-17.fc25.x86_64 systemd-udev 231-15.fc25.x86_64 -> 231-17.fc25.x86_64 vim-minimal 2:8.0.642-1.fc25.x86_64 -> 2:8.0.679-1.fc25.x86_64 Most notable updates are the kernel, systemd, and skopeo. Dusty

6 years, 3 months

1
0
0 / 0

Delivering Atomic Host via CI/CD pipeline

by Stef Walter

Hey guys, A bunch of us (myself, Pingou, Ari, Dusty, Colin, and others) have been talking about the idea of delivering Atomic Host via a CI/CD pipeline. The plan would be to provide continuous integration testing feedback to folks working on packages in Atomic Host and bringing together its compose. In addition the composed QCow2, OSTree, and AMI artifacts that are integrated would be the same ones delivered to users, rather than being recomposed in a different way. I've written something up that explains things further: https://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Deli... I'd like to discuss this in the meeting today. Do we have time? Cheers, Stef

6 years, 3 months

2
3
0 / 0

[atomic-wg] Issue #292: Kubernetes on system-containers in OpenStack Magnum

by Spyros Trigazis

strigazi reported a new issue against the project: `atomic-wg` that you are following: `` In this issue we will try to track the work we are doing to modify our templates in openstack/magnum to deploy kubernetes (etcd, flannel) in system containers. At the moment, we run 1. etcd, flannel, kubelet and kube-apiserver from the binaries includes in fedora-atomic 2. kube-proxy, kube-scheduler, kube-controller-manager as static pods 3. core-dns, kubernetes-dashboard as deployments The goal is to run all components of 1. in system containers and be able to change version easily and get the newest faster. We will investigate if there are benefits to run 2. as system-containers too. We (magnum and atomic-wg) could leverage magnum to test the newest packages of kube/etcd/flannel. Magnum's CI will run soon on CICO [1]. Magnum's configuration scripts: http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common... [1] https://bugs.centos.org/view.php?id=13192 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/292

6 years, 3 months

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup

by dusty＠dustymabe.com

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

6 years, 3 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud July 2017