Request from FESCo
by Garrett Holmstrom
Hi folks,
At Tuesday's meeting FESCo requested that we contact various VPS
providers that don't offer recent versions of Fedora with nicely-worded
emails that ask them to consider offering F12. Ideally they would like
some sort of "Contact VPS Provider" SOP, but for now perhaps we can come
up with a plan to gently nudge them toward using the images we provide
once we have them available. Any thoughts? Suggestions?
The relevant part of the FESCo meeting transcript follows.
--
(15:15:07) nirik: fes ticket 1 Investigate Fedora versions in VPS
providers - mmcgrath did this. The major providers do offer Fedora 12.
(15:15:16) notting: any ideas for how to promote this more?
(15:15:17) gholms: Amazon doesn't.
(15:15:21) dgilmore: people should only take tasks they are capable of
(15:15:32) nirik: gholms: yeah, noted. being worked on.
(15:15:50) nirik: fes ticket 2: SIGs roundup and pinging - jds2001 is
working on this.
(15:16:18) nirik: fes ticket 3: Fedora as Android Development platform -
mmcgrath was going to look at this.
(15:16:28) Kevin_Kofler: Linode has only F11. :-(
(15:16:53) nirik: Kevin_Kofler: yeah, at least it's a supported release
currently.
(15:16:54) Kevin_Kofler: You can upload any arbitrary VM image yourself,
but they don't have F12 as a premade offering.
(15:17:18) nirik: we could send them a nicely worded email asking them
to provide a f12 instance.
(15:17:46) nirik: and/or pass this info off to the cloud-sig to do so.
(15:17:54) gholms: Should I bring that up at the cloud-sig meeting?
(15:18:19) dgilmore: i thought we were working on creating ec2 images as
part of the f13 release process
(15:18:36) dgilmore: so while it sucks that there is not f12 images
(15:18:39) gholms: We are; it's still a work in progress.
(15:18:43) nirik: gholms: please do. Perhaps a "contact VPS provider"
SOP could come out of it?
(15:18:48) dgilmore: going forward we will upload official images
(15:19:17) gholms: I'm a bit concerned about the sheer number of VPSs
out there.
(15:19:28) gholms: Who do we contact, whose image formats do we supply, etc.
(15:19:38) ***nirik notes these are the kind of proactive things I would
like to see happen more rather than just us reacting to exising things.
(15:20:07) nirik: gholms: sure, it's a open question... but I think we
could open a dialog with them... and/or see what the cloud sig can do.
(15:20:38) gholms: How do we initiate such a dialog?
(15:20:46) nirik: so, do we add more tickets and advertise? who adds
tickets? anyone in fesco? anyone?
(15:21:11) gholms: (Sorry for straying off-topic; I'll wait for open floor)
(15:22:14) nirik: gholms: a nicely worded email to start with I would
say? "Dear VPS provider, we noticed you provide Fedora 10 and 9, those
releases are end of life. Would you consider offering F12? Would you
like assistance in making an image for your needs? we have a f12 image
in format X,Y,Z available. Please contact cloud-sig@ if you have questions"
(15:22:34) ajax: (i'm adding some ideas to the fes trac. typing is slow.)
14 years, 2 months
Meeting for tomorrow -- reschedule/postpone?
by Greg DeKoenigsberg
I will be travelling during our scheduled meeting for tomorrow.
I recommend that we postpone our meeting until next Thursday, and in the
meantime, take 10 minutes to send an email update of the current EC2
issues to the list.
Is this acceptable to everyone?
--g
--
Educational materials should be high-quality, collaborative, and free.
Visit http://opensource.com/education and join the conversation.
14 years, 2 months
Eucalyptus
by graziano obertelli
Hello,
as you may know (or know now :)), Eucalyptus is in freeze for a 1.6.2
release schedule by the end of the month, or the beginning of March, but
we would like to make an attempt to have packages for Fedora too for our
next release.
As mentioned before, we already have a spec file, which produces packages
not good enough to be integrated in Fedora, but this will give us a head
start to flushing out the installation procedure on Fedora as well as
finding how to configure it properly. I would love for comments on how to
make things better on Fedora, and in order to do that, we have a source
tree available on launchpad for 1.6.2. Problem is that, for now, I'll be
working on a private branch which I'll merge if our Q&A will give the
green light on the packages: if there is interests in seeing it, I'm more
than happy to publish it where is convenient for Fedora. Is there interest
for it? Is there a preference of where to put the code?
Also, if someone is working on axis2c, axis2 and/or rampartc, I'll be more
than happy to use those packages too.
The timeline is a bit tight for us, so forgive me if I will make stupid
question, which may be answereed but some directed google search. The
first one of which is this one: so far we used xen as the hypervisor of
choice on CentOS (and RHEL), but I know that now both are included in
Fedora. Which one is the preferred one? Which one should be the Eucalyputs
default?
cheers,
graziano
--
Graziano Obertelli
Eucalyptus Systems, Inc.
130 Castilian St. Goleta, CA 93117
Office: 805-845-8000
www.eucalyptus.com
14 years, 2 months
Today's meeting
by David Huff
unfortunately I will not be able to attend today's meeting, due to a
funeral.
-D
14 years, 2 months
IBM Cloud
by Mike McGrath
How are we going to get Fedora available as an option on
http://www.ibm.com/cloud/ Free guests for 30 days is pretty neat, I've
got one provisioning now.
-Mike
14 years, 2 months
Fedora-EC2-min.ks
by David Huff
Ok, as promised here is a first pass at a base ks file for the Fedora
EC2 image. I went with AOS as base and added a couple packages. Total
size is ~ 425M w/ 164 packages on a 650M disk image*.
http://github.com/huff/kickstart-stuff/blob/master/fedora-ec2-min.ks
The image has dhcp, selinux, yum, openssh, and couple other packages
necessary to launch an ec2 instance, log in remotely, and add additional
packages and configuration(a base usecase for testing an ec2 image).
This ks file writes a custom fstab compatible w/ the ec2 infrastructure,
adds the ssh key stuff to rc.local, and enables sshd for remote long in.
It also creates an initrd image and moves it plus the vmlinuz image
outside of the images to be bundled and uploaded separately after image
creation. I went this route so you build all three images at once for
consistency.
Workflow to build images....
1. download ks file
2. mkdir ./include
3. run appliance-creator** -c Fedora-EC2-min.ks -i ./include -p tar.gz
-o /out/put/dir
4. rm ./include
This will produce a tarball with three images, rawdisk image, vmlinuz,
and initrd.img.
Workflow for the whole process would be something like this......
1. run appliance-creator to build images(above)
a. bundle ramdisk + kernel
b. upload ramdisk + kernel
c. register ramdisk + kernel to get aki and ari numbers
2. bundle AMI
a. include aki and ari numbers form above
3. upload AMI
4. register AMI
5. make public
This has not be really tested, as the kernels are not available to
launch an image, comments/suggestions welcome
-D
* The stock image may get small as I am currently working with the
fedora spin guys on a smaller Fedroa-min.ks and hope to merge the aos.ks
with that.
** There are currently a couple bugs in AC which may throw errors in
F12, look for a new package in updates-testing soon!! or ping me for a
workaround.
14 years, 2 months
