Re: cloud init update needs testing
On Fri, Nov 7, 2014, at 09:53 PM, Matthew Miller wrote:
Hi all! https://admin.fedoraproject.org/updates/cloud-init-0.7.5-8.fc21
needs testing — let's get this into F21 (and, more to the point, into
test candidates, so we can make sure it's thoroughly tested).
Hooray. So for Atomic, this gets us:
[root@icarus fedora-atomic.f21]# rpm-ostree rpm diff --repo=repo
fedora-atomic/f21/x86_64/docker-host{^,}
ostree diff commit old: fedora-atomic/f21/x86_64/docker-host^
(ce8a771db37c9ef6ec980f780d2aacf972bd4c37aae3663c762989d9c630dbab)
ostree diff commit new: fedora-atomic/f21/x86_64/docker-host
(08894c763108d2858bd9c75f557f8baf97e7367ec2f5ab4ab28e5af0bf94ec3c)
Upgraded:
cloud-init-0.7.5-8.fc21.x86_64
* Fri Nov 07 2014 Garrett Holmstrom gho...@fedoraproject.org - 0.7.5-8
- Dropped python-boto dependency [RH:1161257]
- Dropped rsyslog dependency [RH:986511]
Removed:
json-c-0.12-5.fc21.x86_64
libestr-0.1.9-4.fc21.x86_64
liblogging-stdlog-1.0.4-4.fc21.x86_64
logrotate-3.8.7-4.fc21.x86_64
python-boto-2.32.1-1.fc21.noarch
python3-3.4.1-15.fc21.x86_64
python3-libs-3.4.1-15.fc21.x86_64
python3-pip-1.5.6-2.fc21.noarch
python3-setuptools-2.0-8.fc21.noarch
rsyslog-7.4.10-5.fc21.x86_64
I also created a fresh qcow2 from it, booted it locally, and logged in fine
with my userdata. Ship it!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: final mirrorlist location for Atomic
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters walt...@verbum.org wrote:
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?
the metalink should be
https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64
Thanks, Dennis. The attached patch should implement this, once we:
1) Get https://admin.fedoraproject.org/updates/ostree-2014.11-1.fc21 through
2) Recompose the tree with it
3) Get a metalink generated pointing at that tree
4) Do some end-to-end testing of this
From e2317e1449749759d0a8895bca46f28b1739fa42 Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Fri, 7 Nov 2014 13:49:57 -0500
Subject: [PATCH] atomic: Rewrite origin to point to metalink
Basically Anaconda-in-ImageFactory is set up to pull from the
builder, so that's what ends up in the origin file. But that's
obviously not what we want to ship to users.
ostree/rpm-ostree do not yet have a convenient command to change this,
so brute force it with sed.
Implements https://lists.fedoraproject.org/pipermail/cloud/2014-November/004570.html
---
fedora-cloud-atomic.ks | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index be862c4..8861d1e 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -36,6 +36,9 @@ reboot
%post --erroronfail
+# See https://github.com/projectatomic/rpm-ostree/issues/42
+ostree remote add --set=gpg-verify=false fedora-atomic 'metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-atomic-21arch=x86_64'
+(origin_file=$(echo -n /ostree/deploy/fedora-atomic-host/deploy/*.origin); sed -e 's,installmedia:,fedora-atomic:,' ${origin_file} ${origin_file}.new mv ${origin_file}{.new,})
# older versions of livecd-tools do not follow rootpw --lock line above
# https://bugzilla.redhat.com/show_bug.cgi?id=964299
--
1.8.3.1
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
urgent(ish): heat-cfntools - python-boto - python3 - sad
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 mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[PATCH] cloud-atomic: Re-shrink rootfs partitions
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(-) From 8cae1be2139094c173cd0af86e515f363204b9af Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Sat, 8 Nov 2014 13:27:05 -0500 Subject: [PATCH] cloud-atomic: Re-shrink rootfs partitions 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(-) diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks index 3906b03..9290de4 100644 --- a/fedora-cloud-atomic.ks +++ b/fedora-cloud-atomic.ks @@ -24,10 +24,10 @@ services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config zerombr clearpart --all # Atomic differs from cloud - we want LVM -part /boot --size=500 --fstype=ext4 +part /boot --size=200 --fstype=ext4 part pv.01 --grow volgroup atomicos pv.01 -logvol / --size=5000 --fstype=xfs --name=root --vgname=atomicos +logvol / --size=2000 --fstype=xfs --name=root --vgname=atomicos ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://compose-x86-02.phx2.fedoraproject.org/compose/atomic/ --ref=fedora-atomic/f21/x86_64/docker-host -- 1.8.3.1 ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora Change for AtomicHost
Initial cut: https://fedoraproject.org/wiki/Changes/AtomicHost Notably, adding bare metal (already working) and vagrant boxes (have prototype code), and I'd like to do a diskless Live PXE image (code exists, need to put it together and polish). This is kept in the Cloud group, but I think the division between Cloud/Server here is going to become rather arbitrary and weird. Oh well. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
