cloud April 2014

cloud@lists.fedoraproject.org

31 participants
76 discussions

Re: Taskotron and Cloud Image tests
by Vitaly Kuznetsov 17 Apr '14

17 Apr '14

Tim Flink <tflink(a)redhat.com> writes: >> For RHEL cloud image checks we have special tool called 'valid': >> https://github.com/RedHatQE/valid , it can be reused for Fedora as >> well. The questions are: how do you see the integration and how can >> someone (me?) work on this (non-existent atm) part of Taskotron. > > For now, I think that the best place to start would be to figure out > what's missing from taskotron in order for the integration to happen. > - would the cloud image startup be done by valid or in taskotron? > - where would the cloud images be run? > - what other image work would be done in the task? Atm 'valid' gets EC2 AMI id as an input and produces test result (yaml file with all tests, their steps and results + logs). I think we can easily kick off such testing tasks from taskotron. The only missing piece in the picture is an 'image uploader': after image was built in koji someone needs to upload it as an AMI to EC2 (afaict Dennis does that manually now). 2mattdm: Matt, I remember you telling me that someone is working on such uploader. Can you please shed some light on what's the status now and what can be done in before f21? >> I can see two possible approaches: >> 1) 'Easy'. We create special type of task (sorry if I'm not that >> precise with terminology) which is being executed on static slave >> node which runs valid (in black-box mode) on newly uploaded image, >> grabs the result and returns it back. > > I suspect that this will be the best way to get started. The > ephemeral client work you mention below is going to be a lot of work > and there are a bunch of unknowns (use openstack or not, how isolated > should the clients be etc.). If we want to have a shot at having some > of the automated cloud tests done for f21, I think that starting with > the easiest route would likely be best Ok, I think that having something ready in f21 timeframe is really doable in case releng can automate AMIs uploading process. I'll take a look at the runner in libtaskotron and existing tasks examples. > > Apologies for the delayed response. Looking forward to working with you > on cloud image testing. > No prob) -- Vitaly Kuznetsov

3 5

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by jzb＠fedoraproject.org 15 Apr '14

15 Apr '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-04-17 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup. Source: https://apps.fedoraproject.org/calendar//meeting/309/

1 0

Announcing Dwarf: OpenStack API on top of libvirt/kvm
by Juerg Haefliger 15 Apr '14

15 Apr '14

In a nutshell, dwarf is OpenStack API on top of local libvirt/KVM. It supports a subset of the Keystone, Glance and Nova APIs to manage images and instances on the local machine. Source and some more information: https://github.com/juergh/dwarf/ Package for F20: https://copr.fedoraproject.org/coprs/juergh/dwarf/ I had some issues with SELinux when running Dwarf in a F20 VM (libvirtd fails to create temp directories when creating an instance). Not sure if that was a problem with the VM or what's going on. I don't have Fedora on a physical machine for testing so let me know if this is a problem for you. ...Juerg

6 12

Fedora Cloud images and Heartbleed
by Juerg Haefliger 11 Apr '14

11 Apr '14

Folks, Do the following cloud images contain fixes for the heartbleed bug? http://dl.fedoraproject.org/pub/fedora/linux/updates/19/Images/x86_64/Fedor… http://dl.fedoraproject.org/pub/fedora/linux/updates/20/Images/x86_64/Fedor… Thanks ...Juerg

2 2

[cloud] #18: File F21 change: (A)Periodic Updates to the Images
by Nobody 08 Apr '14

08 Apr '14

#18: File F21 change: (A)Periodic Updates to the Images ------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------------------ '''Summary:''' We want to be able to release updated images not just at release time. Hope for a one-month regular cadence, plus emergency updates if needed. '''Importance:''' vital (People don't like to yum update their images, and since we change so much, doing so is a significant launch delay. let's make it so they don't have to, but still get updates) '''Timeframe:''' F21 final + 1 month / Obviously better if we get things lined up earlier '''Scope:''' self-contained (but depends on bigger changes across the project) https://fedoraproject.org/wiki/Changes/(A)Periodic_Updates_to_Images '''Cloud SIG owner:''' TBD -- Ticket URL: <https://fedorahosted.org/cloud/ticket/18> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 3

[cloud] #26: File F21 change: Docker Container Image
by Nobody 08 Apr '14

08 Apr '14

#26: File F21 change: Docker Container Image --------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 (Feature Deadline) Component: Docker Base | Keywords: Container | --------------------------------+------------------------------------------ '''Summary:''' This is Fedora running inside Docker. Currently, there are non-official images in the docker index, but we'd like them to really come out of release engineering. '''Importance:''' nice to have (The unofficial image situation is not ideal. Plus, this is an area where we can show leadership.) '''Timeframe:''' F21 alpha / If it's not ready for alpha, we have missed this release '''Scope:''' self-contained '''Cloud SIG owner:''' TBD (mattdm to kick things off) https://fedoraproject.org/wiki/Changes/Docker_Container_Image -- Ticket URL: <https://fedorahosted.org/cloud/ticket/26> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 5

[cloud] #17: File F21 change: Move to ImageFactory For image Creation
by Nobody 08 Apr '14

08 Apr '14

#17: File F21 change: Move to ImageFactory For image Creation ------------------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Feature Deadline) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------------------ '''Summary:''' Create images using Anaconda in Koji rather than appliance- creator. Allows fedmsg integration for upload service, and also could produce official Docker images. '''Importance:''' vital (basic image creation is nice-to-have, fedmsg integration is important to automation, and producing Docker images is strategically vital) '''Timeframe:''' at least a month lead time before F21 alpha / If we are going to release images made this way, we need them made that way for early testing, and there will be some porting work to the kickstart '''Scope:''' self-contained (work with Rel Eng) https://fedoraproject.org/wiki/Changes/ImageFactory_in_Koji '''Cloud SIG owner:''' mattdm Note that this relates to ticket #13 (that's a subset of the work necessary) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/17> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 7

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by jzb＠fedoraproject.org 08 Apr '14

08 Apr '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-04-10 from 14:00:00 to 15:00:00 UTC The meeting will be about: Standing meeting for the Fedora Cloud Workgroup. Source: https://apps.fedoraproject.org/calendar//meeting/309/

1 0

[cloud] #33: File F21 change: use %license for cloud image packages
by Fedora Cloud Trac Tickets 07 Apr '14

07 Apr '14

#33: File F21 change: use %license for cloud image packages --------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: --- | Keywords: --------------------+------------------------------------------ See https://fedorahosted.org/fpc/ticket/411 (the first part of which I am repeating here): Background: 1. Right now, license files are required to be marked as %doc files. 2. There has long been a "nodocs" parameter to RPM which skips all doc files. 3. In addition to the desired space-savings, this installs packages without their possibly-mandatory license files This interaction hasn't been problematic before, because generally using nodocs is an endpoint choice with no distribution after that. But now, we are looking at building some official cloud and container images with nodocs, so it suddenly becomes important. As a bonus, it's my understanding that this tag can automatically handle hardlinking identical license files. Specifically, I propose: 1. We change the guidelines 2. We start doing it for new packages 3. We file a F21 system-wide change for a proven packager to change all the packages that land in the cloud image for F21 (roughly, @core + dependencies plus a few extras) 4. We file a system-wide change for F22 to update all other packages which are part of the base design 5. Other packages updated on a as-time-permits/best-effort basis -- Ticket URL: <https://fedorahosted.org/cloud/ticket/33> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #20: File F21 change: Adopt-Your-Cattle
by Nobody 07 Apr '14

07 Apr '14

#20: File F21 change: Adopt-Your-Cattle -------------------------------------+------------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Feature Component: Collaboration & | Deadline) Communication | Keywords: -------------------------------------+------------------------------------- '''Summary:''' We want to provide a smooth path so a Cloud base image can be turned into Fedora Server '''Importance:''' moderate (Fits the lines we've drawn between the products while still giving people a simple path to running Fedora as a traditional server in a public or private cloud) '''Timeframe:''' F21 beta / This needs testing. '''Scope:''' self-contained (in collaboration with Server WG) '''Cloud SIG owner:''' TBD https://fedoraproject.org/wiki/Changes/Adopt-Your-Cattle -- Ticket URL: <https://fedorahosted.org/cloud/ticket/20> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud April 2014