Re: 32 bit AMI registration boot problem: explaination and possible solutions
On 11/03/2014 11:51 PM, Mike Ruckman wrote: On Mon, Nov 03, 2014 at 07:25:28PM -0500, Dusty Mabe wrote: I would love to get rid of the 32bit AMIs. That being said, is this a knee jerk reaction? Typically it's best to make changes like this with planning involved and sufficient notice of the change so the community can prepare. Again, I'm all for getting rid of them. Just want to make sure we think about everything. Dusty I wasn't meaning it to come across as a knee jerk reaction - I was just curious after thinking about who *uses* a 32bit image when a 64bit is available? Especially for cloud where 64bit is supported everywhere someone might be launching our image from. Indeed. Given the way things work in Fedora, I didn't imagine that saying yes, we should get rid of these if there's not a reason to keep them meant they'd disappear immediately. (If only things happened that quickly...) The thing I thought about was perhaps there's some package people run on a regular basis that was only available in 32bit - but then again, if it was a commonly used package it's likely (if not for certain) there is a x86_64 version of it in the repos already. All that being said, I just figured I'd ask if we still need a 32bit AMI. I was counting on everyone else having more background knowledge into this than I have :) Do we have any way of seeing how many people actually use the 32-bit AMI on AWS? Best, jzb -- Joe Brockmeier | Principal Cloud Storage Analyst j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital signature ___ 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: 32 bit AMI registration boot problem: explaination and possible solutions
On Tue, Nov 04, 2014 at 07:41:27AM -0600, Joe Brockmeier wrote: Do we have any way of seeing how many people actually use the 32-bit AMI on AWS? Unfortunately, not really. -- 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
Re: final mirrorlist location for Atomic
On Mon, Nov 3, 2014, at 11:24 AM, Luke Macken wrote: I'm not sure exactly where the final bits will live, or what the URL will be, but the fedmsg-atomic-composer is up and running on the composer.stg box and successfully spitting out rawhide f21 trees. Nice. Maybe we can deprecate atomic01.qa.fp.org in favor of this? You could change it to take over the rawhide sync to dl.fedoraproject.org at least? Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. Who owns that decision/how do we move forward? ___ 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 Tue, Nov 04, 2014 at 10:28:02AM -0500, Colin Walters wrote: Assuming that this is correct, what needs to change? Is this a kickstart line? We should make the appropriate change _today_. That's not a globally replicated location, it means we're not taking advantage of mirrorlists. Particularly for cloud, I think we really Right, we decided a long time ago to defer worrying about mirroring until F22. want content replicated in each provider's AZ to avoid transit costs. Not sure if Fedora does this now. We had this set up several releases ago but it was dropped due to lack of popularity, if I recall. Now that we're scaling up our efforts we should revisit. ^ Kushal that's one for the todo list. :) Also: 1) That data comes from the atomic01.qa box that was provisioned as a testbed for Atomic work, with the idea that official composes would be done in rel-eng I thought that's what Luke was working on? 2) It's only composing rawhide right now :-/ And also note that until I get a chance to push some changes to spin-kickstarts, we're not going to have optimized LVM, which is 36% of the point of Atomic. Since beta is out the door, let's make those changes right now and get to testing them. The most realistic option to me seems to be to deliver Atomic 21 asynchronously from Fedora 21 final. Ideally within a few weeks? Welcome to other ideas though. We _really_ don't have a mechanism for that, although we have previously shipped updated images in emergencies. We've got people on this -- let's get it done with the actual release — there's still a month to go. (Two weeks of unfrozen, two where we can request exceptions but hopefully won't need to.) -- 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
Re: final mirrorlist location for Atomic
On Tue, Nov 04, 2014 at 10:34:30AM -0500, Colin Walters wrote: Pushing this out to a production releng box will be simple once we determine where the trees will live on /pub. Who owns that decision/how do we move forward? Ticket at https://fedorahosted.org/rel-eng/ — I think the existing alt location is good enough for now and just using that might save wrangling. -- 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
Re: Meeting On Wednesday at 19:00 UTC
One slight problem I just realized is that Daylight Savings ends on November 2nd so this may change some member's availability. Bit late on this one, but that time works fine for me regardless of the DST change. :) -- oddshocks ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Both atomic and base F21 beta AMIs available
Good news, everyone! Both base and atomic AMIs seem to be working properly (x86_64). As per our previous discussion, the 32 bit cloud base image needs to be rebuilt due to a PAE kernel problem, so that won't be available for now. robyduck has said that he'll be able to add the AMI IDs to the official page in a couple hours, but for now, you can find them on my FedoraPeople page: https://oddshocks.fedorapeople.org/ They're public and good to go, so you should be able to boot them and SSH in with the username 'fedora'. Let me know if there are any problems! -- oddshocks ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[cloud] #83: participation in OpenShift Commons
#83: participation in OpenShift Commons +- Reporter: mattdm | Owner: Type: task| Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting +- Take a look at http://origin.openshift.com/commons I brought up joining this to the board, and got the reasonable response of have you gotten the Cloud SIG committed to actually doing the participation asked for? I've talked to a couple of people and I think there's sufficient interest, but it seemed reasonable to ask formally if this is something we're interested in. The actual formal requirements seem to be low: OpenShift Commons is open to anyone. We have no Contributor License Agreement (CLA) or required donation to join. Instead we take each organization at their word to be active participants in forums, Special Interest Groups (SIGs), mailing lists and events. and I think it'd be _great_ to have Fedora officially involved in that way. What do you all think? -- Ticket URL: https://fedorahosted.org/cloud/ticket/83 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ 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: [cloud] #83: participation in OpenShift Commons
#83: participation in OpenShift Commons -+- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | -+- Comment (by hguemar): That's something I'm willing to consider but I need more informations on what is expected from us. Get to talk to pythondj before. -- Ticket URL: https://fedorahosted.org/cloud/ticket/83#comment:1 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ 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: [cloud] #83: participation in OpenShift Commons
#83: participation in OpenShift Commons -+- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | -+- Comment (by jzb): Yeah, I'd be interested, both on the Fedora and Atomic fronts. I've sent a note to pythondj about Atomic as well. -- Ticket URL: https://fedorahosted.org/cloud/ticket/83#comment:2 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ 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: Both atomic and base F21 beta AMIs available
On 11/04/2014 10:41 AM, David Gay wrote: Good news, everyone! Woot! They're public and good to go, so you should be able to boot them and SSH in with the username 'fedora'. Let me know if there are any problems! Just started one up on AWS, minimal testing: * Boots * rpm-ostree is present, status works * Docker is present * docker pull works * docker run works Missing Cockpit + Kubernetes, still, but I think that's a small issue. Need to put some storage instructions together as well, as the 3GB size issue is a problem... Best, jzb -- Joe Brockmeier | Principal Cloud Storage Analyst j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital signature ___ 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: help wanted -- test/karma docker-storage-setup
I backported some changes from fedora-atomic master to f21: https://git.fedorahosted.org/cgit/fedora-atomic.git/log/?h=f21 Here are 4 patches for spin-kickstarts master for fedora-cloud-atomic.ks. I tried to actually test them against rawhide but hit https://bugzilla.redhat.com/show_bug.cgi?id=290 So I backported them to f21 and then I hit a different (presumably anaconda, but maybe dracut) bug where it loops forever at shutdown (haven't searched for/filed a bug yet). However if I terminated the VM in imagefactory, the resulting qcow2 works. To save you all the pain of testing this until we get patches landed, please try: https://alt.fedoraproject.org/pub/alt/fedora-atomic/testing/f21/20141104.0/fedora-atomic-cloud-direct-lvm-walters-20141104.qcow2.gz From c314ed756cc3579d305867a7da13127fa6ceeb98 Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Tue, 4 Nov 2014 08:30:28 -0500 Subject: [PATCH 1/4] cloud-atomic: Use LVM by default in combination with docker-storage-setup This will allow flexible expansion of direct Docker LVM. --- fedora-cloud-atomic.ks | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks index 2f94492..5b75865 100644 --- a/fedora-cloud-atomic.ks +++ b/fedora-cloud-atomic.ks @@ -24,7 +24,10 @@ services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config zerombr clearpart --all # Atomic differs from cloud - we want LVM -autopart +part /boot --size=300 --fstype=xfs +part pv.01 --grow +volgroup atomicos pv.01 +logvol / --size=3000 --fstype=xfs --name=root --vgname=atomicos # Equivalent of %include fedora-repo.ks ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://kojipkgs.fedoraproject.org/mash/atomic/ --ref=fedora-atomic/rawhide/x86_64/docker-host -- 1.8.3.1 From 4fbf117c9819bb618c9a3e0d01a24f53b1ad3241 Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Tue, 4 Nov 2014 08:30:58 -0500 Subject: [PATCH 2/4] cloud-atomic: Point to dl.fedoraproject.org Since this is the repository that's actually getting updates. --- fedora-cloud-atomic.ks | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks index 5b75865..5ec2dcf 100644 --- a/fedora-cloud-atomic.ks +++ b/fedora-cloud-atomic.ks @@ -30,7 +30,7 @@ volgroup atomicos pv.01 logvol / --size=3000 --fstype=xfs --name=root --vgname=atomicos # Equivalent of %include fedora-repo.ks -ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://kojipkgs.fedoraproject.org/mash/atomic/ --ref=fedora-atomic/rawhide/x86_64/docker-host +ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://dl.fedoraproject.org/pub/alt/fedora-atomic/repo --ref=fedora-atomic/rawhide/x86_64/docker-host reboot -- 1.8.3.1 From d6b0df5916914921a67b74dcaf0433f8089fb9ec Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Tue, 4 Nov 2014 09:07:27 -0500 Subject: [PATCH 3/4] cloud-atomic: We use GRUB2 now instead of extlinux In order to have one bootloader per architecture for rpmostreepayload. --- fedora-cloud-atomic.ks | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks index 5ec2dcf..b077712 100644 --- a/fedora-cloud-atomic.ks +++ b/fedora-cloud-atomic.ks @@ -16,7 +16,7 @@ user --name=none firewall --disabled -bootloader --timeout=1 --append=no_timer_check console=tty1 console=ttyS0,115200n8 --extlinux +bootloader --timeout=1 --append=no_timer_check console=tty1 console=ttyS0,115200n8 network --bootproto=dhcp --device=eth0 --activate --onboot=on services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final @@ -42,10 +42,6 @@ passwd -l root # remove the user anaconda forces us to make userdel -r none -# Kickstart specifies timeout in seconds; syslinux uses 10ths. -# 0 means wait forever, so instead we'll go with 1. -sed -i 's/^timeout 10/timeout 1/' /boot/extlinux/extlinux.conf - # If you want to remove rsyslog and just use journald, remove this! echo -n Disabling persistent journal rmdir /var/log/journal/ @@ -125,15 +121,6 @@ echo --- # Note that running rpm recreates the rpm db files which aren't needed/wanted rm -f /var/lib/rpm/__db* - -# This is a temporary workaround for -# https://bugzilla.redhat.com/show_bug.cgi?id=1147998 -# where sfdisk seems to be messing up the mbr. -# Long-term fix is to address this in anaconda directly and remove this. -# https://bugzilla.redhat.com/show_bug.cgi?id=1015931 -dd if=/usr/share/syslinux/mbr.bin of=/dev/vda - - echo Zeroing out empty space with fstrim. /usr/sbin/fstrim / -- 1.8.3.1 From cdf0383c05c35d714b6439e2f7a6fa19d856901f Mon Sep 17 00:00:00 2001 From: Colin Walters walt...@verbum.org Date: Tue, 4 Nov 2014 09:09:45
Re: help wanted -- test/karma docker-storage-setup
On Tue, Nov 04, 2014 at 08:53:04PM -0500, Colin Walters wrote: Here are 4 patches for spin-kickstarts master for fedora-cloud-atomic.ks. I tried to actually test them against rawhide but hit https://bugzilla.redhat.com/show_bug.cgi?id=290 Applied to master -- I had to update the one about extlinux because an unrelated change you hadn't pulled. Can you rebase for f21? They don't apply cleanly -- I think just for minor things but I'll need more focus than I have right now to do it right. (Will look again tomorrow.) -- 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
