initramfs on F21 beta image is corrupt?
by Lars Kellogg-Stedman
I just grabbed the F21 beta cloud image from:
http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/...
It looks like the initramfs on this image is corrupt; it appears to be
an uncompressed CPIO archive with truncated content:
# zcat initramfs-3.17.1-302.fc21.x86_64.img | cpio -it
gzip: initramfs-3.17.1-302.fc21.x86_64.img: not in gzip format
cpio: premature end of archive
# cpio -it < initramfs-3.17.1-302.fc21.x86_64.img
.
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/AuthenticAMD.bin
early_cpio
44 blocks
If I generate a new image with 'dracut -f', I get something that looks
a lot more sane...
# dracut -f
# zcat initramfs-3.17.1-302.fc21.x86_64.img | cpio -it
[...671 lines of output...]
The image still boots correctly in my OpenStack environment but I
suspect this will cause problems for someone.
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
9 years, 5 months
Re: Content for getfedora.org, meeting recap
by Joe Brockmeier
On 11/10/2014 02:50 PM, Paul W. Frields wrote:
> Minutes: http://meetbot.fedoraproject.org/fedora-mktg/2014-11-10/website-content.2...
> Minutes (text): http://meetbot.fedoraproject.org/fedora-mktg/2014-11-10/website-content.2...
> Log: http://meetbot.fedoraproject.org/fedora-mktg/2014-11-10/website-content.2...
One thing I have noticed - we don't have a "place" for Fedora Docker
images. Since they were taken on by the base WG, they have sort of been
orphaned under products. Do they belong under Server? Cloud? Spins?
> Notable -- Once a draft of strings are finished for the getfedora.org
> site, we'll pass to Working Groups through their liaisons for
> feedback. We're aiming to have those in the next 24 hours or so.
Hmmm. So I produced a patch against the getfedora branch. (Attached)
Here's the strings for the cloud pages:
main page:
Fedora Cloud:
Fedora Cloud provides a minimal Fedora cloud image for use in public and
private cloud environments. It includes just the bare essentials so you
get enough to run your cloud application -- and nothing more.
Get Cloud page:
Top:
Fedora Cloud has the tools
for public and private clouds,
traditional workloads, or Docker containers.
Middle:
The Fedora Cloud Working Group offers two variants for different use
cases. The Base image is suitable for anyone who wants to run Fedora in
the AWS public cloud, or on a private cloud like OpenStack.
The Fedora Atomic Host is generated using rpm-ostree to allow true
"atomic" updates, and is optimized to run Docker containers.
Both are available in formats suitable for public or private clouds.
[[We need a quote or something for the middle - who could we get
something from? Think testimonial.]]
Bottom:
Fedora Cloud images provide leading edge software for development and
deployment in public cloud environments.
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 5 months
urgent(ish): heat-cfntools -> python-boto -> python3 -> sad
by Matthew Miller
hey all. heat-cfntools requires python-boto, which requires python3,
which shouldn't happen before we're ready to transition to python3
overall.
This has a _significant_ impact on image size now that the python-boto
dep is gone from cloud init. Having _one_ python requirement is bad
enough but it's egregious to pull in both 2 and 3.
Options:
1. does heat-cfntools hard-require python-boto?
2. can we use a python-boto that isn't python3 before we're ready?
(there was supposed to be a coherent plan for this!)
3. should we drop heat-cfntools for f21?
Agents are a pain. :(
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 5 months
final mirrorlist location for Atomic
by Colin Walters
Currently, the Atomic cloud image still tries to contact the compose server internal mirror for updates.
Do we know what the final mirrorlist URL will be? Where are we on getting content sync'd out?
9 years, 5 months
[PATCH] cloud-atomic: Re-shrink rootfs partitions
by Colin Walters
mattdm changed these previously because we hit an ENOSPC error during
qcow2 image creation, but that *really* happened because the Fedora
rel-eng create-cloud-images script hardcoded 3GB.
Now that we've shrunk the content down to ~850MB, drop the defaults:
- rootfs down to 2GB. This is enough space for a replacement of
all content, plus a bit of spare room for logging
- /boot to 200MB. At present, kernel+initramfs is just 30MB,
so this is still very conservative.
---
fedora-cloud-atomic.ks | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
9 years, 5 months
fedora-productimg-cloud package
by Matthew Miller
We have a new package which contains the differentiated branding for
the installer -- fedora-productimg-cloud. This can also be used to
choose different defaults, and we could even move some of our ugly
kickstart hacks there (although that's a bit dubious).
We're deemphasizing this for F21, but for F22 and beyond, this will
help with what Jared and others suggested a little while ago -- people
who want to use the installer to generate a first-pass at a custom
cloud image interactively.
So anyway, the question: who wants to own or co-own this package?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 5 months
