Hi all,
I will be skipping tonight's meeting. Will have to sleep early with
some medicines on .
Open Floor note: F22 cloud image boots fine but is not getting any ip.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
FYI - if anyone is interested in mentoring a student for a project
related to the Cloud Working Group...
-------- Forwarded Message --------
Subject: Fedora Proposals for Google Summer of Code 2015 due *TOMORROW*
Date: Wed, 18 Feb 2015 10:16:17 -0500
From: Stephen Gallagher <sgallagh(a)redhat.com>
Reply-To: users(a)lists.fedoraproject.org
To: announce(a)lists.fedoraproject.org
Sorry for the obscenely short-notice folks. This year's GSoC application
was left unintentionally untended. I've started putting together a
Proposal page at
https://fedoraproject.org/wiki/Summer_coding_ideas_for_2015
If you are interested in mentoring a student this summer on your
project, please add your name and a description of the project no later
than tomorrow so I can submit the proposal on Friday.
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
FYI
-------- Forwarded Message --------
Subject: Fedora 22 Changes Completion deadline in one week - 2015-02-24
Date: Tue, 17 Feb 2015 08:39:28 -0500 (EST)
From: Jaroslav Reznik <jreznik(a)redhat.com>
Reply-To: devel(a)lists.fedoraproject.org
To: devel-announce(a)lists.fedoraproject.org
Greetings!
Fedora 22 Change Checkpoint: Completion deadline (testable) is in
one week - 2015-02-24 [1] and we're getting closer to this date.
Other important milestones are scheduled for this date:
* Alpha Freeze
* Software String Freeze
* Bodhi activation point
At this point, all accepted changes should be substantially complete,
and testable. Additionally, if a change is to be enabled by default,
it must be so enabled at Change Completion deadline.
Change tracking bug should be set to the MODIFIED state to indicate
it achieved completeness.
Fedora 22 is strictly time based release and we want to adhere to the
schedule. Incomplete and non testable Changes will be reported to
FESCo for 2015-02-25 meeting. Contingency plan for System Wide Changes,
if planned for Alpha (or in case of serious doubts regarding Change
completion), will be activated.
[1] https://fedoraproject.org/wiki/Releases/22/Schedule
Jaroslav
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
Hi,
are there non-intel cloud images available?
I am mainly interested in PPC64 qcow images of Fedora.
What is standard way of generating those images? I only find:
http://worknotes.readthedocs.org/en/latest/cloudimages.html
And I'm not sure how much official it is.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2015-02-18 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/
# F22 Blocker Review meeting
# Date: 2015-02-16
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net
It's Blocker Review time again! While we don't yet have an Alpha TC to
test, testing against rawhide has continued. The results have yielded a
couple proposed blockers: 3 Alpha and 2 Final. 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
Have a good weekend and see you Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
#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
Hey all,
Have been in the FOSDEM/DevConf.cz bubble for the past two weeks, returning home today. Will not be at the meeting this afternoon.
The Dockerfile social media/article stuff is high-priority for me next week, so I should have it ready to go Monday or Tuesday.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2015-02-11 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/
DAY
Reply-To:
In-Reply-To: <20150206155432.GI27640(a)redwood.ruck.lan>
On Fri, Feb 06, 2015 at 08:54:32AM -0700, Mike Ruckman wrote:
> # F22 Blocker Review meeting
> # Date: 2015-02-08
> # Time: 1700 UTC
> # Location: #fedora-blocker-review on irc.freenode.net
>
> So far this week we've found 1 proposed Alpha blocker as well as 5
> proposed for Final. 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
>
> Have a good weekend and see you Monday!
>
> [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
>
> --
> // Mike
> --
> Fedora QA
> freenode: roshi
> http://roshi.fedorapeople.org
> _______________________________________________
> cloud mailing list
> cloud(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
So, I can't read calendars, I guess. This meeting is for Monday, the 9th
and not Sunday the 8th.
Sorry for the noise!
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
Hello, cloud friends.
I've attached a signed list of fresh AMIs for the images we provide through [1]. If no one sees any problems here, we could ask someone from the web team to update that page with these new AMIs.
Notables:
- These AMIs were registered on the *official* Fedora AWS account, to which few people (to my knowledge) have access
- The AMIs currently listed on [1] were registered with the less-locked-down community cloud account
- AMI volume sizes are now "tailored to fit", to reduce AWS costs
- Base images use 3 GB volumes (our minimum)
- Atomic images use 7 GB volumes (uncompressed Atomic images are about 6.1 GB)
- Fedimg jobs were triggered on the fedimg01 machine, so there's a trail of fedmsgs like [2]
[1]: https://getfedora.org/en/cloud/download/
[2]: https://apps.fedoraproject.org/datagrepper/id?id=2015-d218ae58-ce79-46d8-9c…
-- David
Another testing cycle is finally upon us, and it's about time we got
some Test Days scheduled for the F22 cycle. The Anaconda team has
already requested a test day [0] and there are several other changes
coming to F22 that could use some testing love - a full list can be
found here:
http://fedoraproject.org/wiki/Releases/22/ChangeSet
F22 also has several self-contained changes that could use some testing.
So my thought was, if there were things people would like to get tested,
but didn't think it warranted an entire day - then we could group these
together and run a test day to poke at several different things at the
same time. Thoughts on this?
For those of you not familiar with test days, a test day is an
online event aimed at testing a specific feature of an upcoming Fedora
Release. By utilizing IRC for organization/coordination and a Wiki
page for instructions and results, test days are easy to organize.
Anyone can request to host a test day or request that the QA team help
you out with the organization of the test day. A test day can be ran
for any feature or area of a distribution that focused testing would be
useful for. More information on test days can be found here:
https://fedoraproject.org/wiki/QA/Test_Days .
To propose a test day, file a ticket on the QA Trac. A full
explanation can be found here:
https://fedoraproject.org/wiki/QA/Test_Days/Create . The SOP for
hosting a test day is here:
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
Traditionally test days have been held on Thursdays, but if you'd prefer
to have it on another day that's fine too. We're pretty flexible, but
having plenty of lead time helps to get the word out. Just put in your
ticket the date or time-frame you'd like, and we'll figure it out from
there.
If you have any questions about test days or the process, please don't
hesitate to contact me or any other QA Team member in #fedora-qa on
Freenode or respond on the test list.
Thanks and happy testing!
[0] https://fedorahosted.org/fedora-qa/ticket/457
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2015-02-04 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/
# F22 Blocker Review meeting
# Date: 2015-02-02
# Time: 1700 UTC
# Location: #fedora-blocker-review on irc.freenode.net
It's that time of week again, time for some Blocker Review! Currently we
have 1 Alpha and 1 Beta blocker proposed - so it should be a short
meeting. We'll be sticking with the new trend of going through all the
milestones during this meeting.
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 Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org