Cloud WG Trac: inform voting member of new tickets?
by Sandro "red" Mathys
Would it be possible (and desired) to have the Cloud WG Trac send an
email to all current voting members (and possible anyone else
interested) whenever a new ticket is opened? Just so people don't miss
them and know what to weigh in on in case they can't make a meeting,
etc.
Kindly let me know if everyone can set that up (for) himself and point
me to the option I'm not seeing :)
Thanks,
Sandro
10 years, 5 months
Meeting time going forward
by Sam Kottler
Hi,
Hope you all had a nice weekend!
I'd like to set a more permanent meeting time so we don't have to do a
whenisgood each week and handle coordination. Using the last two weeks
as a guide, it seems like an early evening time in UTC, somewhere
between 17:00 and 20:00, on Wednesday works well for people. Does anyone
have any conflict or objection to setting the meeting for 18:00 UTC each
week?
-Sam
10 years, 5 months
Fedora 20-Beta RC5 AMIs
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all,
Beta RC5 images have been uploaded to EC2 and are available at
ami-8b4219e2 : us-east-1 image for i386
ami-2f421946 : us-east-1 image for x86_64
additionally if your looking to the AMI's they have been added to files
in the release tree
http://dl.fedoraproject.org/pub/alt/stage/20-Beta-RC5/Images/i386/Fedora-...
http://dl.fedoraproject.org/pub/alt/stage/20-Beta-RC5/Images/x86_64/Fedor...
when we get to final Beta and the images are uploaded to all regions
they will all be listed and the file will be gpg signed in the final
tree
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJSevy8AAoJEH7ltONmPFDRBaQP/18Ugi6jB/q8Ej5s31xItFzZ
lQIzXZZDDOTHiRxWpzAKYAnu9Mo4N0QQk/OxjVPbuG9fwc1LaggauMWvYVbsy8sn
b3vzUSsJFWS6A1WdG817IICPHI/3GlGacdL+O2aGM3WZsr654R0p/9rxgUPo9a+A
KYBBP/mk+ur/y2larMaaIN+Sd3pwIl9ayG9k2uujkt9Up9combLPlBnzUQ/TM+Iy
abdmRmCG49KSeTNvRRUJkoZd5+r9cB8CzKQYnTLZjNviTouIoDeApV4SZa1tOwzg
Zu5ZQgs35rEr0+k4Z3vnXcZ5KDERQ2gvFDQJ5ng1LiLUJaOVkFG7D/JxR59/EbvX
Tm5Pr1M32FzmuIQg3hFxFNji7CbLGn/s3QQKHPd80tr7ba/yyEJqIrf4Y0ay9VTH
jtbppmThFhTWYP0lt1Sqgna8TwTXjwwK2bcuMpfsSrZuhQEuAPZpFf5HZA6Y+wCt
8wfjNPatbcktyANppbLQXq7dOwDZAUPwwgW2Bo7sk5k1OSvLKKmEwAWQPNdsmljF
VO9zUZWbtP5Arpg9dV1580p1lXBVGNHKNSqYjj59IhAgeQOKHrusi0jyjQXvyQKP
fnn7nRhQnj50QKjNvE2nRY74O4l9YMUxAoBaBnzb3Mff2hqSokgD419j9HSH0tIt
3pejUkTfj2POgdifZihE
=1VYS
-----END PGP SIGNATURE-----
10 years, 5 months
ZOMG WHAT ARE WE BUILDING?!
by Joe Brockmeier
Hi all,
(For those who weren't in today's IRC meeting, I sorta apologize for the
subject line. Sorta.)
As we were discussing today - we need to decide what we are building,
and (almost as importantly) what we're not building. We've agreed that
we want to be cooperating with the server SIG, but don't necessarily
plan to build a foundation for an IaaS ourselves.
Some of the questions that were raised during the meeting:
- Should we drop 32-bit?
- Should we be targeting ARM?
- Do we worry about supporting ALL THE METHODS of building the image, or
no? (I recommend we focus on One True Way so as not to confuse
everyone with 80 different ways they *could* do it.)
Other questions, thoughts, comments, flames?
I also want to recommend that we think hard about not just what we
build, but accompanying it with appropriate amounts of documentation for
the developers/users we expect to be consuming the image. I'm sure it
goes without saying that we would document what we do, but I would like
to see this thought about each step of the way so that when we get to a
finished product, it's dead easy to adopt.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
10 years, 5 months
Fedora Cloud WG weekly meeting minutes - 6 Nov 2013
by Sam Kottler
Thanks everyone who was able to make it to the meeting today! For those who weren't able to make it, here are few important links:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-06/fedora-meeti...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-06/fedora-meeti...
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-06/fedora-meeti...
Here's a summary of the meeting (link to the HTML version above):
==========================================
#fedora-meeting-1: Cloud WG weekly meeting
==========================================
Meeting started by samkottler at 17:00:29 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-06/fedora-meeti...
.
Meeting summary
---------------
* Roll call (samkottler, 17:04:35)
* Announcements (samkottler, 17:05:53)
* ACTION: frankieonuonga to bump his initial mail about roles +
responsibilities (samkottler, 17:09:30)
* rbergeron frankieonuonga stahnma samkottler to work on the PRD
(samkottler, 17:19:19)
* the goal for PRD completion is december 15th, the pace needed for
that will be determined on the list (samkottler, 17:23:54)
* AGREED: the goal for PRD completion is december 15th, the pace
needed for that will be determined on the list (+5) (samkottler,
17:25:13)
* pending tickets (samkottler, 17:25:55)
* LINK: https://fedorahosted.org/cloud/ticket/1 (samkottler,
17:26:26)
* LINK: https://git.fedorahosted.org/git/cloud-image-service.git
(samkottler, 17:32:38)
* frankieonuonga will work with dgilmore and others in rel-eng to
communicate about WG plans and help automate different processes
(samkottler, 17:33:49)
* LINK: https://fedorahosted.org/cloud/ticket/2 (samkottler,
17:40:46)
* ACTION: samkottler to do more research into the actual tools and
their licenses that are required to build GCE images (samkottler,
17:48:18)
* open floor (samkottler, 17:54:21)
* hguemar looking to package gcutil (number80, 17:54:34)
Meeting ended at 18:01:08 UTC.
Action Items
------------
* frankieonuonga to bump his initial mail about roles + responsibilities
* samkottler to do more research into the actual tools and their
licenses that are required to build GCE images
Action Items, by person
-----------------------
* frankieonuonga
* frankieonuonga to bump his initial mail about roles +
responsibilities
* samkottler
* samkottler to do more research into the actual tools and their
licenses that are required to build GCE images
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* samkottler (87)
* frankieonuonga (73)
* number80 (35)
* dgilmore (32)
* rbergeron (27)
* stahnma (20)
* nirik (5)
* zodbot (5)
* geppetto (5)
* sgallagh (3)
* mattdm (3)
10 years, 5 months
Re: Draft Product Description for Fedora Workstation
by Paul W. Frields
On Fri, Nov 01, 2013 at 10:24:20AM -0400, Christian Fredrik Kalager Schaller wrote:
> Hi everyone,
> Attached is the draft PRD for the Workstation working group. The
> proposal tries to be relatively high level and focus on goals and
> principles, but I have included some concrete examples at times to try
> to provide some clarity on how the goals and principles could play out
> in practice.
>
> I hope the community at large will take the time to read through it and
> provide feedback so that when the working group meet next we can use
> that feedback to start tuning in on the final form of the PRD.
Here's a statement we may need to better clarify on p. 3:
"The working group will also specify policies in terms of branding,
themeing and desktop graphics."
I think we should be clear that any branding efforts need to fit into
the overall branding framework of Fedora. We should be careful to
avoid having branding diverge between the products to an extent that
makes it harder for us to identify them as part of a family of Fedora
products.
In my time as an FPL, I worked extensively with Fedora folks on
trademark and brand guidelines. I suspect Robyn has done quite the
same wherever possible. It would be a step backward to make it harder
for people to readily identify any of the Fedora products with
Fedora.
This is really a suggestion for all the working groups, so I'm cc'ing
server@ and cloud@ lists too.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
10 years, 5 months
Cloud product kernel requirements
by Josh Boyer
Hi All,
I realize the WG is just forming up and you have a lot of other items
to cover for now, but I wanted to get this sent out and have people
start thinking about it sooner rather than later.
The kernel team has heard in the past that the Cloud group would like
to see something of a more minimal kernel for usage in cloud images.
We'd like to hear the requirements for what this smaller image would
need to cover.
Right now, a default x86_64 kernel package on f20 is ~134MB installed.
Most of that is device drivers installed in /lib/modules/`uname -r`/.
The vmlinux binary is about 5MB and the initramfs (which is created
at install time and can actually vary quite widely depending on
various things) is about 11MB. Drivers can be trimmed to a degree,
but please keep in mind that the kernel is already relatively small
for the functionality it provides. For example, it is not much bigger
than glibc-common (119MB).
So, some caveats to keep in mind while you're thinking about this:
1) We're mostly talking about packaging here, not building a separate
cloud kernel package or vmlinux. The kernel team really wants to have
a single vmlinux across the 3 products if at all possible. We can't
scale to much else.
2) What usecases is the cloud image going to cover? E.g. is it just
virtio stuff, or will it also fit PCI passthru (which then requires
drivers for those PCI devices)?
3) What are the common provisioning requirements that are driving the
size reduction? (See comment about glibc-common. I would think
change is needed in multiple packages, not just the kernel.)
4) Other "cloudy" stuff that I'm entirely unaware of that might be
relevant. Explain it to me like I'm a child.
Thanks!
josh
10 years, 5 months
Fedora 20-Beta RC4 AMIS
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all,
Beta RC2 images have been uploaded to EC2 and are available at
ami-c3e3bbaa : us-east-1 image for i386
ami-d3e2baba : us-east-1 image for x86_64
additionally if your looking to the AMI's they have been added to files
in the release tree
http://dl.fedoraproject.org/pub/alt/stage/20-Beta-RC4/Images/i386/Fedora-...
http://dl.fedoraproject.org/pub/alt/stage/20-Beta-RC4/Images/x86_64/Fedor...
when we get to final Beta and the images are uploaded to all regions
they will all be listed and the file will be gpg signed in the final
tree
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJSeaP8AAoJEH7ltONmPFDRk9IP/jnNhm8M088uIJw/4LQYfy7n
UtBF6NnEb1yUg2TSMuprVc4z1ZczG2t/UPZiQW5j6QnXLg+72XjYmr/9W/BhH1AR
rrzIOzQskrD1HK0yvkTt8P2KEgulCsUknx5PDgwY1pe3A55kHLiB/ePpUY0Sow8V
6bzHAaOdyX8RhumqkwB1GkVMavH89jgzmSntu0+qa/Yp8Y4H6gPr+6BpNtLUz9tu
fH15kqBayGzvNhoXzDtgiKF+eH/KITcdngNxjVIDSWYacYdhgbN3cYXI6z9D9Ylj
b5g11XfNwlB50hzQIldFyOdHVJtIqEA97uixPlHVBGfP1+vF5cbb40DK2qWNv87m
MmqGpXb3nvC9RKwQWbEHgAaIDAOFqFs+AD5AyDlBJRl9J0w4WvXEZpJwCWaaRJLf
1gEyr5m/K0GAyFPgtxsAvGjNzJUrA958++5QHy4Ogpq2dXd0ZcTedIz3Vu5FLvTG
tHsmSJet3wmfMsVXw5lqGdSKqsYMfxIe/eLSzhqkSn9ckbrLMBpUqSxqiFXel3Lt
qNvnyec8lDZcn1PsN6OhAvktpB5bvfy0xcOObikmGAEaQByNZ3sCxxOp8zJ7azrR
9E1MfpGgle1S1arOLoVCvG5S+Gp3HFxdI37BqFG6Qxwu2Cab9dYAN8T7whNzr68z
8yCKj2s2W3dctfNK4FYv
=5Nfl
-----END PGP SIGNATURE-----
10 years, 5 months
