cloud June 2014

cloud@lists.fedoraproject.org

29 participants
68 discussions

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

24 Jun '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-06-26 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

Re: Packaging Google-Daemon
by Renich Bon Ciric 24 Jun '14

24 Jun '14

On Tue, Jun 24, 2014 at 8:15 AM, Filipe Brandenburger <filbranden(a)google.com> wrote: > Hi Renich, > > I think you directed the message at me alone and not the mailing list... Whoops! Sorry! Let's keep it on the mailing list. > On Tue, Jun 24, 2014 at 6:03 AM, Renich Bon Ciric > <renich(a)woralelandia.com> wrote: >> Ok, here're the SRPM, RPM and SPEC files: >> >> http://23.251.155.37/fedora/ >> >> I'm trying it out on that same server and it works, so far. It seems >> to work at least. > > Nice! I'll check them out. > >> Anyone interested in reviewing? > > One minor nitpick... I think the name "google-daemon" is a bit too > generic and doesn't convey the idea that this is relevant for the > google *cloud* :-) > > The CentOS image calls it "google-compute-daemon": > > $ rpm -qa google\* > google-startup-scripts-1.1.3-1.noarch > google-compute-daemon-1.1.3-1.noarch > > Which is also what the release tarballs are called: > > https://github.com/GoogleCloudPlatform/compute-image-packages/releases I'll change the name then. > BTW, it seems that 1.1.4 is out, I believe that one will include the > systemd config, maybe you could update it to use the released 1.1.4 > instead of a git commit later than the tagged based as the initial > point for your package(s). > > Cheers! Ok, I'll update it. The reason for the latter commit is that it fixed some issue that was critical. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/

1 1

Metadata for cloud images
by Richard W.M. Jones 20 Jun '14

20 Jun '14

I would really like to add metadata for the Fedora cloud images. This serves two purposes: (1) It provides a way to describe the cloud images available, in a human- and machine-friendly way. (2) It means that virt-builder will just work with the existing Fedora cloud images. The metadata format is very simple. Here is an example: http://libguestfs.org/download/builder/index.asc It is also described formally: http://libguestfs.org/virt-builder.1.html#create-the-templates and there is a verification tool in Fedora [virt-index-validate]. My question is: What process creates/uploads the cloud images, and how do we get it to add the metadata file? Whatever currently creates the CHECKSUM file could be modified to create the metadata file too. https://fedorahosted.org/rel-eng/ticket/5805 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top

2 1

Re: [cloud] #4: new release criteria for post-f20 cloud image
by Fedora Cloud Trac Tickets 19 Jun '14

19 Jun '14

#4: new release criteria for post-f20 cloud image ------------------------------+-------------------------------- Reporter: mattdm | Owner: roshi Type: task | Status: assigned Priority: major | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords: | ------------------------------+-------------------------------- Comment (by roshi): I've created a wiki page with a list of things to test for. It still needs a lot of work, but it's a start. https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/what_to_test -- Ticket URL: <https://fedorahosted.org/cloud/ticket/4#comment:8> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 0

Re: [cloud] #4: new release criteria for post-f20 cloud image
by Fedora Cloud Trac Tickets 19 Jun '14

19 Jun '14

#4: new release criteria for post-f20 cloud image ------------------------------+-------------------------------- Reporter: mattdm | Owner: roshi Type: task | Status: assigned Priority: major | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords: | ------------------------------+-------------------------------- Comment (by mattdm): I'd like to add "libX11 not pulled in by some dep" as a warning flag, although not necessarily a blocker. (I'd like to test for that so we can react when it happens, which it seems to be inevitable in each release cycle.) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/4#comment:7> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 0

Re: [cloud] #5: tracker for GCE work
by Fedora Cloud Trac Tickets 18 Jun '14

18 Jun '14

#5: tracker for GCE work ------------------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Future Component: Cloud Base Image | Resolution: Keywords: | ------------------------------+--------------------- Changes (by filbranden): * cc: filbranden@… (added) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/5#comment:4> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 0

Make 'no_timer_check' Kernel parameter for Fedora cloud images
by Kashyap Chamarthy 18 Jun '14

18 Jun '14

Heya, This is a brief summary of discussions re `no_timer_check` Kernel parameter from different bug trackers (see references below for more details) What? ----- Make 'no_timer_check' Kernel parameter default for Fedora cloud images. Why? ---- It has been reported (recently and in the past) many times[1][2][3] that Kernel timer checks are not reliable/helpful in the context of virtualization and it's useful to disable This is also useful to elimiate false-positives in upstream OpenStack CI testing[1][2]. Notes ----- - 'no_timer_check' parameter is added implicitly when the kernel detects it is booting under KVM. However when booting under QEMU TCG (software emulation) you have to add this to the guest kernel command line explicitly. (Thanks Richard WM Jones.) - About 'no_timer_check', from Kernel documentation[4]: 'no_timer_check' [X86,APIC] Disables the code which tests for broken timer IRQ sources. References ---------- [1] https://bugs.launchpad.net/cirros/+bug/1312199 -- cirros 0.3.1 fails to boot - Relevant comments: #1, #2, and #4 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1102592 -- F20 could image affected by timing issues when using with soft-qemu [3] https://bugzilla.redhat.com/show_bug.cgi?id=502058#c15 -- qemu -no-kvm guest hangs at during timer setup; works with noapic [4] https://www.kernel.org/doc/Documentation/kernel-parameters.txt -- /kashyap

2 2

question about audit _by default_ in Fedora cloud images
by Matthew Miller 17 Jun '14

17 Jun '14

I was looking at https://fedorahosted.org/fesco/ticket/1311, and it occured to me that we don't ship the selinux troubleshooting tools by default in the minimal cloud image (add 'em if you need them). We do leave _audit_ there. What do people think about removing it? (As noted in the ticket, it's mostly useful with configuration, not in the default state.) -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

4 3

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

17 Jun '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-06-19 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

Prioritizing getting python-cheetah out of cloud-init
by Matthew Miller 17 Jun '14

17 Jun '14

cloud-init requires python-cheetah. This pulls in python-pygments. This pulls in python-pillow, which pulls in ghostscript. Then we get the whole X stack. Can we break this at the top? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud June 2014