Re: Packaging Google-Daemon
by Renich Bon Ciric
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/
9 years, 9 months
Re: [cloud] #4: new release criteria for post-f20 cloud image
by Fedora Cloud Trac Tickets
#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
9 years, 9 months
Make 'no_timer_check' Kernel parameter for Fedora cloud images
by Kashyap Chamarthy
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
9 years, 9 months
question about audit _by default_ in Fedora cloud images
by Matthew Miller
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
9 years, 9 months
Prioritizing getting python-cheetah out of cloud-init
by Matthew Miller
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
9 years, 9 months