I just pushed the final (i.e. non-snapshot) version of cloud-init
0.7.0 to F18 and rawhide, which fixes a great deal of compatibility
bugs, makes most of the plugins work properly, and allows one to
configure the users on the system using instance user-data a lot
better than previous version. There is one fairly important change to
be aware of relative to F17's version: this version allows you to
change the user that it creates at startup time (and in fact add even
more), so it is recommended to *not* pre-create a user when you build
the image. What do we need to do to remove that from Fedora's cloud
image kickstart before we start building test images?
I'd like to push this to F16 and F17 as well to replace the horribly
broken versions that those operating systems shipped with. Any
How about EPEL? This update fixes so many issues that I believe it's worth it.
// Deploying fedora infrastructure (koji) across clouds
// As promised, steps to deploy kojihub to an openstack instance
communicating with builders on ec2
// Any provider supported by deltacloud will work
// (lots of em: http://deltacloud.apache.org/drivers.html)
// A short video of these steps in action can be seen here:
// install deltacloud & drivers
$ sudo yum install wget deltacloud-core deltacloud-core-openstack
// start it
$ deltacloudd -i mock
// small wrapper script around deltacloud:
$ wget https://raw.github.com/movitto/mycloud/master/mycloud.rb
$ chmod +x mycloud.rb
// template describing kojihub cloud deployment
// template describing kojibuild cloud deployment
// edit kojihub deployment to contain openstack credentials
$ vim koji_f17.xml
// startup an instance on openstack w/ kojihub setup togo
$ ./mycloud.rb koji_f17.xml
// grab public address from output, grab kojibuild ssl credentials from
$ scp -i ~/os.key ec2-user@kojihub:/etc/pki/koji/kojiadmin.pem .
$ scp -i ~/os.key ec2-user@kojihub:/etc/pki/koji/koji_ca_cert.crt .
// edit kojibuild deployment to deploy to ec2 w/ correct koji
credentials & hub address
$ vim koji_builder_f17.xml
// startup an instance on ec2 w/ kojibuild communicating w/ the hub
$ ./mycloud.rb koji_builder_f17.xml
// open up a webbrowser, navigating to http://kojihub/koji to use your
On 10/28/2012 08:00 AM, cloud-request(a)lists.fedoraproject.org wrote:
> Send cloud mailing list submissions to
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cloud digest..."
> Today's Topics:
> 1. Re: Please review / comment on / help with AWS Marketplace
> listing (Matthew Miller)
> Message: 1
> Date: Sat, 27 Oct 2012 12:16:12 -0400
> From: Matthew Miller <mattdm(a)fedoraproject.org>
> To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org>
> Subject: Re: Please review / comment on / help with AWS Marketplace
> Message-ID: <20121027161611.GA18788(a)disco.bu.edu>
> Content-Type: text/plain; charset=utf-8
> On Fri, Oct 26, 2012 at 04:41:47PM -0700, Garrett Holmstrom wrote:
>>>> NEED SOMETHING HERE
>>>> [Security? Fedora-ness? Values? Highlight some particlar awesomness?]
>>> Ideas, anyone?
>> We covered "freedom" with highlight 1. We covered "friends" with the
>> note about community support. "Features" is covered by highlight 2.
>> Guess what's left? ;-)
> Well, we need to start getting some firsts in place from a cloud point of
> view before we can highlight them. Since F17 is ancient in internet years
> already, maybe it doesn't matter so much, but what can we push as whiz-bang
> for F18?
Not even really "qualified" to answer this....since I'm just a
greenhorn, but what about "security"......"speed"......"ease of
use".....things that would appeal to the average admin......someone
who's NOT looking to pore over hours of material just to find out how to
do "ABC-123"?......just a suggestion....
Here's the details for the form I'm going to submit. Would appreciate your
input, especially on the Highlights. My comments in [brackets].
The Fedora Project is a worldwide community of people who love, use, and
build free software. We want to lead in the creation and spread of free
code and content by working together as a community. Fedora is sponsored
by Red Hat, the world's most trusted provider of open source technology.
Red Hat invests in Fedora to encourage collaboration and incubate
innovative new free software technologies.
Fedora 17 (Beefy Miracle) 2012.05.15
[Note: I put the date there because I'd like to leave open the option of
updated image spins. Open to suggestions on how best to do this.]
Official Fedora Cloud image.
Fedora is a Linux-based operating system built on our community's four
foundations: freedom, features, friends, and first. The Fedora Cloud image
in EC2 provides a functional core on top of which any of tens of thousands
of free and open source software packages can be easily added.
Free and Open Source: built by a collaborative community using entirely
Core Image Ready to Build Upon: use yum to add any of tens of thousands of
software packages, or drop in your own code.
[Avoid "minimal", because it isn't. Should I use a more precise count of
NEED SOMETHING HERE
[Security? Fedora-ness? Values? Highlight some particlar awesomness?]
[This is a boolean. We _do_ offer community support, of course. Should
maybe be true?]
Community supported. Visit Ask Fedora (http://ask.fedoraproject.org/), or
get involved by joining the Fedora Cloud SIG
(https://fedoraproject.org/wiki/Cloud_SIG). You can help us make Fedora in
the Cloud even more awesome for everyone.
open source, free, core
Resource1 Name & Resource1 URL:
Resource2 Name & Resource2 URL:
Fedora Cloud SIG
Resource3 Name & Resource3 URL:
Connect with SSH. No web services are installed or configured by default.
Fedora's EC2 images follow standard EC2 login conventions, meaning that
root login is disabled, but sudo access is granted. The default username
for the images is ec2-user.
End User License Agreement Text:
Refund and Cancelation Policy:
Fedora is available free of charge. Normal Amazon Web Services terms
Available in Regions....
True for all.
Endpoint URL Protocol:
[hopefully, I can get them to construct a ssh://ec2-user@.... URL]
[Blank for now]
Recommended Instance Type:
Available Instnace Types:
All except GPU. (Including Micro)
tcp, 80, 80, 0.0.0.0/0
tcp, 443, 443, 0.0.0.0/0
tcp, 22, 22, 0.0.0.0/0
[These are defaults for one-click launch]
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
As I understand it, there's no grub in the ec2 instances because grub2 was
not happy with the xen paravirtualized devices. And also it's not necessary.
Our instructions for OpenStack here
have a little script for injecting syslinux as a bootloader so the images
work with openstack.
A notable drawback is that kernel updates don't actually take effect without
manual intervention. Plus, of course, if we don't start doing this
ourselves, it means an extra annoying step for everyone.
It looks to me that more recent grub2 is patched to deal with the situation
-- see https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/623609 and code
in current grub-2.00/util/getroot.c.
Is there anything I'm missing here, and, what's the best way forward? (Grub
in everything? Grub in images on mirrors, skip it in ec2?)
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
At today's Fedora Cloud SIG meeting, we discussed something akin to this
 but for cloud instances. Deltacloud  could be used to manage
connections to different clouds and we can provide a simple gui dialog
to configure providers. This would simplify the Fedora desktop / cloud
integration experience and make deploying to the cloud from Fedora
Matt Miller suggested we add a feature but unfortunately I'm short on
cycles, though it was mentioned that if we can come up with a good story
/ proposal for Fedora 19, something might be able to be arraigned. We
also can see about pulling in the gnome design and implementation teams
to help us out with this story.
Thoughts? Unless there are any strong objections, I'll write up a formal
story / proposal for the Fedora wiki and we can take it from there.