October 2014 - cloud - Fedora mailing-lists

[cloud] #35: External need: Automatic Image Upload
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#35: External need: Automatic Image Upload --------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: --- | Keywords: --------------------+------------------------------- '''Summary:''' Whenever an image is built, it is automatically uploaded to our cloud provider targets (EC2, etc.) and to the fedora ftp site (and possibly mirrors if we can convince mirror admins to drink from that firehose) '''Importance:''' vital (current process where rel eng does it by hand will not scale) '''Timeframe:''' whenever we can get it / this adds value whenever it happens '''Fedora Sub-Project/SIG:''' Release Engineering, possibly Infrastructure for resources '''Cloud SIG owner:''' TBD (note summer intern may help with that, if it is not too late) Possibly we file this as a change. Also see previous intern's initial work: https://git.fedorahosted.org/cgit/cloud-image-service.git/ We need someone to help drive this, and to assist rel-eng and infrastructure in whatever they need. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/35> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #15: migrate to GPT instead of old-style partitions
by Nobody 13 Oct '16

13 Oct '16

#15: migrate to GPT instead of old-style partitions ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- * What: use gpt with this spec http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ * Where: in the kickstart, and with support needed from build tools (which should be ticket #13) * Why: images could be launched as containers using new systemd hotness * When: nice for F21 alpha * Who: ??? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/15> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 3

[cloud] #14: Investigate systemd-networkd
by Nobody 13 Oct '16

13 Oct '16

#14: Investigate systemd-networkd ------------------------------+------------------------------- Reporter: mattdm | Owner: janeznemanic Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- * What: new service to do very basic network config * Where: remove the sysv network scripts, add config for this * Why: remove very kludgey shell scripts; try the new hotness * When: Before F21 alpha * Who: Janez Nemanic -- Ticket URL: <https://fedorahosted.org/cloud/ticket/14> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 53

[cloud] #56: tracking ticket for conversations around shipping ostree images
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#56: tracking ticket for conversations around shipping ostree images -------------------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 Component: Collaboration & Communication | (Branch) | Keywords: -------------------------------------------+------------------------------- We've decided to base the Fedora Docker host image on Project Atomic, and therefore rpm-ostree. This means several big conversations, including with QA, Rel Eng, and the mirror network. It will mean some new development and possibly extra resources. But first we need to figure out the questions to ask, and then we need to ask them, and then we need to find answers, or provide them where they don't already exist. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/56> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

[cloud] #13: Port Cloud Image Kickstart to anaconda/imagefactory
by Nobody 13 Oct '16

13 Oct '16

#13: Port Cloud Image Kickstart to anaconda/imagefactory ------------------------------+----------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Cloud Base Image | Keywords: ------------------------------+----------------------- Rel-Eng is updating to Koji 1.9, which will allow us to use Anaconda and ImageFactory for image creation instead of appliance-creator. * What: The current kickstart file is full of kludges for appliance- creator. Port to anaconda/imagefactory kludges * Where: same as ongoing maintenance of kickstart * Why: appliance-creator is being retired; anaconda-based installs are the way forward * When: As soon as this is available in Koji. Need a new ImageFactory release, then patches into Koji for support, then a new Koji release, then Koji needs to be updated in Fedora production * Who: Ian McLeod is working on ImageFactory; Jay Greguske on the Koji patches, Mike McLean is Koji maintainer, Dennis Gilmore in release engineering will do the Koji update. Need to work with them to get this in place, and then someone from cloud wg needs to do the updating. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/13> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 5

[cloud] #69: Fedora Cloud image boot: Y U SO SLOW?
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#69: Fedora Cloud image boot: Y U SO SLOW? ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- In openstack using June 26th rawhide (http://koji.fedoraproject.org/koji/taskinfo?taskID=7078357) boot is really slow. It's about 25 seconds (as per the boot log) to a command prompt, but another 20 seconds until the root resize is done, and another 20 before cloud-init completes. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/69> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #40: rel-eng/image upload changes for f21
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#40: rel-eng/image upload changes for f21 -------------------------------------------------+------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Infrastructure & Release | (Alpha) Engineering | Keywords: -------------------------------------------------+------------------------- Some small updates to the cloud image upload process: * https://fedorahosted.org/rel-eng/ticket/5880 * https://fedorahosted.org/rel-eng/ticket/5881 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/40> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #70: cloud-init output not going to the openstack log
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#70: cloud-init output not going to the openstack log ---------------------+------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Beta) Component: --- | Keywords: ---------------------+------------------------------ Some combination of "got something wrong in the kernel parameters or where cloud-init is sending its output". -- Ticket URL: <https://fedorahosted.org/cloud/ticket/70> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #43: procedures and process for getting updated images onto mirrors
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#43: procedures and process for getting updated images onto mirrors ------------------------------+------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Beta) Component: Software Updates | Keywords: ------------------------------+------------------------------ Right now, cloud images only get mirrored at GA release time. We need to figure out how to ship updates. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/43> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #58: get vagrant-libvirt (and/pr vagrant-kvm) plugins into the distro
by Fedora Cloud Trac Tickets 08 May '15

08 May '15

#58: get vagrant-libvirt (and/pr vagrant-kvm) plugins into the distro --------------------+-------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- See http://ttboj.wordpress.com/2014/05/13/vagrant-on-fedora-with-libvirt- reprise/ and the call for help at the end. Also the discussion there, and also previous work at * https://bugzilla.redhat.com/show_bug.cgi?id=998503 * https://fedoraproject.org/wiki/Changes/Vagrant -- Ticket URL: <https://fedorahosted.org/cloud/ticket/58> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #68: support HVM instances in EC2
by Fedora Cloud Trac Tickets 11 Feb '15

11 Feb '15

#68: support HVM instances in EC2 ------------------------------+------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: ------------------------------+------------------------------- We currently only support Xen paravirtualized images (PV) in EC2. We need to support HVM as well. (This will require changes to our EC2 image production and upload process, and may require changes to our bootloader code as well. Particularly, it probably takes away our clever hack for providing different kernel parameters in EC2.) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/68> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #66: Create kickstart file
by Fedora Cloud Trac Tickets 13 Jan '15

13 Jan '15

#66: Create kickstart file -------------------------------+------------------------------ Reporter: pfrields | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 (Beta) Component: Docker Host Image | Keywords: -------------------------------+------------------------------ What: Based on the Base Image's kickstart file, write an extended kickstart file with the image-specifics. Where: kickstart file is at https://fedorahosted.org/spin-kickstarts/ Why: No kickstart file, no image. When: Before Fedora 21's first release candidates are built. Who: Someone in cloud working group in collaboration with the Spins SIG ''(ported from task list at https://fedoraproject.org/wiki/Cloud/Cloud_ToDo)'' -- Ticket URL: <https://fedorahosted.org/cloud/ticket/66> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

Short links to Fedora Cloud Images
by Matthew Miller 17 Dec '14

17 Dec '14

These links all work now: http://cloud.fedoraproject.org/fedora-19.x86_64.qcow2 http://cloud.fedoraproject.org/fedora-19.i386.qcow2 http://cloud.fedoraproject.org/fedora-latest.i386.qcow2 http://cloud.fedoraproject.org/fedora-latest.x86_64.qcow2 (They will redirect to a mirror link provided by mirrormanager.) -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

5 6

[cloud] #80: Public Uploaded Images Criteria
by Fedora Cloud Trac Tickets 12 Dec '14

12 Dec '14

#80: Public Uploaded Images Criteria --------------------+--------------------- Reporter: roshi | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- It came up in the blocker review meeting today [0] that there were no beta images available for EC2. A bug was filed (and voted a blocker) [1], but I think we need another criteria for when we add providers. I propose be added to the Alpha release criteria: Cloud images must be available in supported cloud service registries - AMI's uploaded for EC2 - docker image in docker registry - etc - etc [0] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-29/f21 -blocker-review.2014-10-29-16.05.log.html [1] https://bugzilla.redhat.com/show_bug.cgi?id=1158592 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/80> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

[cloud] #74: Plan test days for Atomic image
by Fedora Cloud Trac Tickets 26 Nov '14

26 Nov '14

#74: Plan test days for Atomic image --------------------+------------------------------ Reporter: jzb | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Beta) Component: --- | Keywords: meeting --------------------+------------------------------ Once we have a viable image we need to go ahead and plan a test day around the image (or more). We're still delayed on alpha, but all signs are looking good for next week's go/no-go meeting. Will set a date or dates and start working on promoting that. Setting milestone as "beta" for this as it's something that should happen before the beta, but after alpha... -- Ticket URL: <https://fedorahosted.org/cloud/ticket/74> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

[cloud] #75: Article for Fedora Magazine on "state of cloud SIG/product" for alpha release
by Fedora Cloud Trac Tickets 26 Nov '14

26 Nov '14

#75: Article for Fedora Magazine on "state of cloud SIG/product" for alpha release ----------------------------+------------------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Website & Wiki | Keywords: meeting ----------------------------+------------------------------- What it says on the tin - putting in a tracker ticket to work on this and get it ready for the alpha release. Should go out simultaneously with the alpha or maybe staggered by a day or two to keep interest high. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/75> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

New Meeting Time
by Dusty Mabe 17 Nov '14

17 Nov '14

Hey All, Sorry this took so long. I was trying to get Dennis to vote so that we could accommodate his schedule if we ever needed him in any meetings. I never heard back from him so I'm moving forward. The results are here: http://whenisgood.net/recw7mb/results/wx5ep2c It looks like the best times are one of the following: Tuesday/Thursday at 16:00 UTC (12:00 EDT): See [1] Wednesday at 18:00 UTC (14:00 EDT): See [2] Wednesday at 19:00 UTC (15:00 EDT): See [3] What does everyone think about Thursday at 16:00 UTC? scollier, you are the only one that is listed as not available during that time. Can you somehow make it? Thanks, Dusty [1] - http://whenisgood.net/ResultsPopup?event=recw7mb&code=wx5ep2c&slot=14133024… [2] - http://whenisgood.net/ResultsPopup?event=recw7mb&code=wx5ep2c&slot=14133960… [3] - http://whenisgood.net/ResultsPopup?event=recw7mb&code=wx5ep2c&slot=14133996…

11 29

help wanted -- test/karma docker-storage-setup
by Matthew Miller 05 Nov '14

05 Nov '14

As Joe noted the other day, Fedora Atomic is intended to come with this service, which will create storage space for Docker images. As mentioned in the IRC meeting, at this point, the plan is to get this to stable after the beta (before the feature freeze, as soon as possible), to update the Atomic tree definition, and then to request a test candidate including it. But the first step is getting it to stable. So, testers wanted -- https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21 second priority after http://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test of course :) -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

5 17

Meeting On Wednesday at 19:00 UTC
by Dusty Mabe 05 Nov '14

05 Nov '14

I have updated fedlocal [1] to reflect the new meeting time. One slight problem I just realized is that Daylight Savings ends on November 2nd so this may change some member's availability. I guess we will cross that bridge when we get there. Dusty [1] - https://apps.fedoraproject.org/calendar/cloud/2014/10/27/

4 4

Reporting validation results with relval: please update python-mwclient to 0.7
by Adam Williamson 31 Oct '14

31 Oct '14

Hi, folks. Sorry for the cross-post, but wanted to try reach everyone I'd mentioned my little 'relval' tool to. If you have been using 'relval' to report validation results, or are thinking of trying it, please make sure you update python-mwclient to 0.7. Josef Skladanka submitted a few results using relval yesterday which messed up the Desktop page, and kindly fixed up the page and let me know about the problem (thanks, Josef!) On investigation I found the problem is that python-mwclient 0.6.5 is missing the ability to read in the text of a single page section (it looks like it has it, but it actually doesn't). Any time you submit a result to a multi-section page with python-mwclient 0.6.5, this will happen. With python-mwclient 0.7 it works fine. I'm going to send out a python-wikitcms update which requires python-mwclient 0.7 ASAP, and get the python-mwclient 0.7 update into stable for all releases also ASAP, but just in case anyone isn't updating regularly or anything, I thought I'd send a note. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Important: community cloud credentials
by Andy Grimm 31 Oct '14

31 Oct '14

Hi, all. This week, the Cloud Working Group migrated from shared credentials to individual credentials in our AWS account. If you have previously used the shared credentials and would like to have a new individual account created, please file a ticket at https://fedorahosted.org/cloud/newticket . Please state your use case in the ticket, so we have some idea of how people use this resource, and whether additional permissions may be required beyond our defaults. Also, credentials will only be issued via PGP-encrypted email, so ensure that your FAS account lists your current public key. I sincerely apologize if this breaks any automated scripts. I asked members of various teams to ensure that we were safe to make this change, but as you can imagine, this is a security-sensitive issue, so asking the list publicly was not possible. --Andy

1 0

32bit AMI issues (unofficial AMI)
by Dusty Mabe 30 Oct '14

30 Oct '14

Last night I created some AMIs for roshi to test using the procedure at [1]. I then booted the x86_64 AMI (ami-145fdd7c) and it seemed fine. The i386 AMI (ami-de6be9b6) had issues booting (see [2] for full log). Has anyone else seen this before? [[32m OK [0m] Started System Logging Service. [[32m OK [0m] Started OpenSSH Server Key Generation. [ 17.320770] cloud-init[332]: Cloud-init v. 0.7.5 running 'init-local' at Thu, 30 Oct 2014 04:30:06 +0000. Up 17.22 seconds. [[32m OK [0m] Started Initial cloud-init job (pre-networking). [[1;31mFAILED[0m] Failed to start LSB: Bring up/down networking. See "systemctl status network.service" for details. Thanks, Dusty [1] - https://gist.github.com/dustymabe/3d53cfe6b9ae32c5e2fb [2] - http://ur1.ca/im3op

2 2

Fwd: [Test-Announce] Fedora 21 Beta Release Candidate 4 (RC4) Available Now!
by Adam Williamson 29 Oct '14

29 Oct '14

-------- Original Message -------- Subject: [Test-Announce] Fedora 21 Beta Release Candidate 4 (RC4) Available Now! Date: 2014-10-29 19:16 From: Andre Robatino <robatino(a)fedoraproject.org> To: test-announce(a)lists.fedoraproject.org Reply-To: test(a)lists.fedoraproject.org NOTE: The last compose was RC2. As per the Fedora 21 schedule [1], Fedora 21 Beta Release Candidate 4 (RC4) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/6010#comment:19 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Workstation and Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Server: https://fedoraproject.org/wiki/Test_Results:Current_Server_Test Cloud: https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test Summary: https://fedoraproject.org/wiki/Test_Results:Current_Summary Ideally, all Alpha and Beta priority test cases for each of these test pages [2] should pass in order to meet the Beta Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Create Fedora 21 Beta test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/6010 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://admin.fedoraproject.org/mailman/listinfo/test _______________________________________________ test-announce mailing list test-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

[cloud] #79: FAS Cloud Group
by Fedora Cloud Trac Tickets 29 Oct '14

29 Oct '14

#79: FAS Cloud Group -------------------------+--------------------- Reporter: roshi | Owner: roshi Type: enhancement | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -------------------------+--------------------- Would it make sense for us to have our own group in FAS for things such as editing the calendar? I don't know what other benefits it might bring us, but seems like there's a group for everything else. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/79> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

Announcing Fedora Outreach mailing list -- please subscribe if interested
by Matthew Miller 29 Oct '14

29 Oct '14

Because response to the Fedora Outreach Steering Committee proposal has been overwhelmingly positive, I created a new mailing list, initially to discuss the possible creation of such a group and to coordinate actually doing it, and then eventually to be a discussion list _for_ the group. If you are interested in this, please subscribe at <https://lists.fedoraproject.org/mailman/listinfo/outreach>. Thanks! [This message is massively multi-posted — please don't reply. Instead, discuss on the new list!] -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2014