Cloud SIG news - week 29
by Haïkel
Hi folks !
we had to cancel this week's meeting due to the lack of quorum.
Let me remind you that Joe (jzb) announced earlier this week a new
meeting time after a vote:
Fridays @ 17:00 UTC / 13:00 Eastern / 12:00 Central / 10:00 Pacific
To find the next meeting time in your local time: date -d "Friday 17:00 UTC"
By the way, the Cloud WG had to replace one of its voting member: Andy
Grimm -agrimm) had been nominated by the existing members (including
Sando Mathys -red_trela- whom he replaces) +7
Welcome Andy and thank you Sandro for your dedication ! :)
In place of the weekly meeting, we had an informal meeting in
#fedora-cloud, few highlights:
* Due to the current poor shape of the hadoop ecosystem packages, the
Big Data Image will be delayed, the priority being fixing the packages
I suggested that we make it a spin for F21 and the official
deliverable rescheduled to F22
* imcleod is moving forward with Rackspace's nova agent, few packaging
issues might arises for requirements, but imcleod plans to provide a
copr repository anyway and the resulting cloud image will be
semi-official
* roshi thinks that the tests validation matrix is good enough for
testing the upcoming alpha release
If you have any news to share with us, feel free ;)
Best regards,
H.
9 years, 9 months
[PATCH] Don't enable by default
by Colin Walters
[ Posting here for increased visibility ]
Right now, cloud-init is only installed in the cloud images, so it's OK
if it enables itself by default.
However, for future Atomic work, we'll likely only have one tree
that's also running on bare metal, and that will include cloud-init.
This change should be safe because the Fedora Cloud kickstart in
spin-kickstarts uses services --enabled=cloud-init.
---
cloud-init.spec | 22 ++--------------------
1 file changed, 2 insertions(+), 20 deletions(-)
9 years, 9 months
Proposed generic release criterion: service manipulation
by Adam Williamson
Still working on Fedora 21 release criteria. It seems to me that there's
one area currently lacking in the criteria which all the Products would
probably like us to have, hence I'm proposing it as a new 'generic'
criterion, not Product-specific. We still haven't figured out exactly
how to present the criteria, so for now I'm proposing this one be added
as a new Fedora 21 Alpha criterion, i.e. it goes to
https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria (under
"Post-install requirements"). Here's the proposed criterion:
System service manipulation
It must be possible to start, stop, enable and disable system services
using the initialization framework's standard commands.
I don't think it needs any footnotes beyond standard 'References'.
Does this seem reasonable to everyone? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 9 months
New Cloud WG member approval: Andy Grimm
by Haïkel
Hello,
Since Sandro Mathys (red_trela) stepped down from the Working Group,
we're missing a member.
During last week meeting, Andy Grimm (agrimm, fas: arg) candidated to
replace him and taking ownership of Sandro's tasks.
According our Governance document: "When a position in the group
becomes available, that position will be filled by unanimous consent
of the existing members."
http://fedoraproject.org/wiki/Cloud/Governance
So we need to get consent from the remaining Cloud WG voting members
to get Andy onboard.
I suggest we use Apache lazy consensus rule: +1 (approve) +0 (no
opinion, but okay) -1 (disapprove)
and if there's no -1 before the next meeting, and we reached quorum by
then, Andy will be joining us.
Let's start voting !
+1 from myself.
best regards,
H.
9 years, 9 months