cloud January 2015

cloud@lists.stg.fedoraproject.org

23 participants
72 discussions

[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] #92: Need rootfiles package in fedora:latest Docker base image
by Fedora Cloud Trac Tickets 08 May '15

08 May '15

#92: Need rootfiles package in fedora:latest Docker base image -----------------------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: -----------------------------------+-------------------- We need the .bashrc in order to properly change the bash prompt once changed into the image. For example, here's the fedora:20 image: -bash-4.2# docker run -it fedora:20 bash [root@845950cd95f1 /]# cat /etc/fedora-release Fedora release 20 (Heisenbug) [root@845950cd95f1 /]# rpm -qf /root/.bashrc rootfiles-8.1-16.fc20.noarch For example, here's the fedora:latest image: -bash-4.2# docker run -it fedora:latest bash bash-4.3# rpm -qf /root/.bashrc error: file /root/.bashrc: No such file or directory -- Ticket URL: <https://fedorahosted.org/cloud/ticket/92> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

[cloud] #86: qcow2 images text is a bit obscure / OpenStack-only
by Fedora Cloud Trac Tickets 22 Apr '15

22 Apr '15

#86: qcow2 images text is a bit obscure / OpenStack-only ----------------------------+-------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Website & Wiki | Keywords: ----------------------------+-------------------- Lars Kellogg-Stedman sent a note to the Fedora Cloud list today noting, rightly, that the libvirt audience might miss the qcow2 images because it's labeled "OpenStack" (only) rather than being more expansive. We need to correct this and add instructions for using cloud-init with the image in Virt-Manager, etc. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/86> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #87: Fedora Magazine Post: How to Use Dockerfiles
by Fedora Cloud Trac Tickets 04 Mar '15

04 Mar '15

#87: Fedora Magazine Post: How to Use Dockerfiles -----------------------------------+--------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: meeting -----------------------------------+--------------------- Need to do a post on how to use Dockerfiles and maybe how to contribute patches to Dockerfiles. Should this also live on the wiki? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/87> 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

EC2 cloud image size
by Dmitry Makovey 30 Jan '15

30 Jan '15

I just tried to spin up "cloud" instance of F21 on EC2 only to discover it's requirements for 12G volume (???). Am I doing something wrong or did F21 jumped from moderate 2-3G (F20) over to 12G "overnight". I assumed "cloud image" would be a tiny set of packages with very little requirements to fit into all flavors offered by EC2 and alike. Was this done to accommodate Docker? -- Dmitry Makovey Web Systems Administrator Athabasca University (780) 675-6245 --- Confidence is what you have before you understand the problem Woody Allen When in trouble when in doubt run in circles scream and shout http://www.wordwizard.com/phpbb3/viewtopic.php?f=16&t=19330

5 15

2015-01-28 @ 1900 UTC ** Cloud SIG Meeting Minutes
by Mike Ruckman 28 Jan '15

28 Jan '15

============================ #fedora-meeting-1: cloud sig ============================ Meeting started by roshi at 19:00:42 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-01-28/fedora_cloud_s… . Meeting summary --------------- * Roll Call (roshi, 19:01:04) * Follow Up (roshi, 19:03:53) * LINK: https://fedorahosted.org/cloud/ticket/94 (dustymabe, 19:05:26) * LINK: https://fedorahosted.org/cloud/report/9 (roshi, 19:06:50) * HVM Instances (#68) (roshi, 19:07:16) * LINK: https://fedorahosted.org/cloud/ticket/68 (roshi, 19:07:24) * Open Floor (roshi, 19:23:21) * Meeting is going to end early due to not meeting quorum (roshi, 19:23:58) Meeting ended at 19:28:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * roshi (51) * dustymabe (28) * Corey84 (13) * zodbot (8) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

[cloud] #91: Update Timezone for the docker images
by Fedora Cloud Trac Tickets 28 Jan '15

28 Jan '15

#91: Update Timezone for the docker images -----------------------------------+----------------------- Reporter: kushal | Owner: kushal Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Docker Base Container | Keywords: meeting -----------------------------------+----------------------- In the kickstart currently it is configured as New York, it should be UTC. This issue was first mentioned by lsm5. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/91> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 26 Jan '15

26 Jan '15

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2015-01-28 from 19:00:00 to 20: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/1999/

1 0

2015-01-26 @ 1700 UTC ** F22 Blocker Review Meeting
by Mike Ruckman 25 Jan '15

25 Jan '15

# F22 Blocker Review meeting # Date: 2015-01-26 # Time: 1700 UTC # Location: #fedora-blocker-review on irc.freenode.net I seem to have forgotten how to use the "send" button on my mail client, so this annoucnement is getting out a bit late. Apologies for that! We've got another blocker review in a couple hours! We currently have several proposed blockers: 2 Alpha, 1 Beta and 2 Final. So if you're around after the QA meeting, come and join us for some blocker review goodness :) If you want to take a look at the proposed or accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/ Make sure to click through the milestones to see how many we have before the meeting! We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you soon! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud January 2015