From dhuff at redhat.com Mon Dec 1 16:37:20 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 01 Dec 2008 11:37:20 -0500 Subject: [Thincrust-devel] [PATCH] Allow the appliance-creator to use remote urls with the new image tools In-Reply-To: <1227646365-31041-1-git-send-email-bkearney@redhat.com> References: <1227646365-31041-1-git-send-email-bkearney@redhat.com> Message-ID: <493412C0.4020200@redhat.com> Bryan Kearney wrote: > --- > tools/appliance-creator | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/tools/appliance-creator b/tools/appliance-creator > index c305ac7..c5f75f2 100755 > --- a/tools/appliance-creator > +++ b/tools/appliance-creator > @@ -86,7 +86,7 @@ def parse_options(args): > (options, args) = parser.parse_args() > > #check input > - if not options.kscfg or not os.path.isfile(options.kscfg): > + if not options.kscfg: > raise Usage("Kickstart config '%s' does not exist" %(options.kscfg,)) > > if options.include and not os.path.isfile(options.include) and not os.path.isdir(options.include): committed -D From dhuff at redhat.com Mon Dec 1 16:38:11 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 01 Dec 2008 11:38:11 -0500 Subject: [Thincrust-devel] [Fwd: Package: appliance-tools-004-1.fc11 Tag: dist-f11-python Status: complete Built by: huff] Message-ID: <493412F3.1060103@redhat.com> New build for f-11(rawhide) uses python 2.6 -D -------- Original Message -------- Return-Path: buildsys at fedoraproject.org Received: from zmta01.collab.prod.int.phx2.redhat.com (LHLO zmta01.collab.prod.int.phx2.redhat.com) (10.5.5.31) by mail02.corp.redhat.com with LMTP; Mon, 1 Dec 2008 11:37:05 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by zmta01.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 43DAA90249 for ; Mon, 1 Dec 2008 11:37:05 -0500 (EST) Received: from zmta01.collab.prod.int.phx2.redhat.com ([127.0.0.1]) by localhost (zmta01.collab.prod.int.phx2.redhat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rh4vqwtK0q8g for ; Mon, 1 Dec 2008 11:37:05 -0500 (EST) Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by zmta01.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 0C56A90224 for ; Mon, 1 Dec 2008 11:37:04 -0500 (EST) Received: from mx2.util.phx.redhat.com (mx2.util.phx.redhat.com [10.8.4.102]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mB1Gb3vr030693 for ; Mon, 1 Dec 2008 11:37:03 -0500 Received: from bastion.fedora.phx.redhat.com (bastion.fedora.phx.redhat.com [10.8.34.50]) by mx2.util.phx.redhat.com (8.13.1/8.13.1) with ESMTP id mB1Gb3MN022298 for ; Mon, 1 Dec 2008 11:37:03 -0500 Received: by bastion.fedora.phx.redhat.com (Postfix) id 3652E208D1B; Mon, 1 Dec 2008 16:37:03 +0000 (UTC) Delivered-To: huff at fedoraproject.org Received: by bastion.fedora.phx.redhat.com (Postfix, from userid 404) id 2FCA5208D5E; Mon, 1 Dec 2008 16:37:03 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on bastion.fedora.phx.redhat.com X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=no version=3.2.4 Received: from ppc3.fedora.phx.redhat.com (ppc3.fedora.phx.redhat.com [10.8.34.68]) by bastion.fedora.phx.redhat.com (Postfix) with ESMTP id 9035F208D1B; Mon, 1 Dec 2008 16:36:51 +0000 (UTC) From: Koji Build System Subject: Package: appliance-tools-004-1.fc11 Tag: dist-f11-python Status: complete Built by: huff To: katzj at fedoraproject.org, mikeb at fedoraproject.org, huff at fedoraproject.org, ivazquez at fedoraproject.org, kanarip at fedoraproject.org, jkeating at fedoraproject.org, notting at fedoraproject.org X-Koji-Tag: dist-f11-python X-Koji-Package: appliance-tools X-Koji-Builder: huff X-Koji-Status: complete Message-Id: <20081201163651.9035F208D1B at bastion.fedora.phx.redhat.com> Date: Mon, 1 Dec 2008 16:36:51 +0000 (UTC) X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 Package: appliance-tools-004-1.fc11 Tag: dist-f11-python Status: complete Built by: huff ID: 72610 Started: Mon, 01 Dec 2008 16:34:22 UTC Finished: Mon, 01 Dec 2008 16:36:23 UTC Changelog: * Mon Dec 01 2008 David Huff - 004 - bumped version for rebuild for Python 2.6 - Allow the user to pass in --version and --release command line paramneters (bkearney) - Patches to integrate ec2 conversion into the adk (bkeareny) - Allow the appliance-creator to use remote urls with the new image tools (bkearney) * Fri Nov 14 2008 David Huff - 003.9 - Fixed bug in globbing files under a directory (pmyers) * Fri Nov 14 2008 David Huff - 003.8 - Fixed bug that causes appliance-creator to stacktrace when -i is omitted (pmyers) SRPMS: appliance-tools-004-1.fc11.src.rpm Closed tasks: ------------- Task 967176 on xenbuilder2.fedora.redhat.com Task Type: buildArch (appliance-tools-004-1.fc11.src.rpm, noarch) logs: http://koji.fedoraproject.org/koji/getfile?taskID=967176&name=build.log http://koji.fedoraproject.org/koji/getfile?taskID=967176&name=root.log http://koji.fedoraproject.org/koji/getfile?taskID=967176&name=state.log rpms: http://kojipkgs.fedoraproject.org/packages/appliance-tools/004/1.fc11/noarch/appliance-tools-004-1.fc11.noarch.rpm Task 967193 on x86-3.fedora.phx.redhat.com Task Type: tagBuild (noarch) Task 967167 on x86-6.fedora.phx.redhat.com Task Type: buildSRPMFromSCM (/cvs/pkgs:rpms/appliance-tools/devel:appliance-tools-004-1_fc11) logs: http://koji.fedoraproject.org/koji/getfile?taskID=967167&name=srpm.log Task Info: http://koji.fedoraproject.org/koji/taskinfo?taskID=967164 Build Info: http://koji.fedoraproject.org/koji/buildinfo?buildID=72610 From bkearney at redhat.com Tue Dec 2 14:16:58 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 02 Dec 2008 09:16:58 -0500 Subject: [Thincrust-devel] spin-kickstarts Message-ID: <4935435A.4000602@redhat.com> Huff: With the new doco on the website, what is the purpose of spin-kickstartts? Will this contain the info which was going to be in the appliance-os rpm? -- bk From dhuff at redhat.com Tue Dec 2 17:03:41 2008 From: dhuff at redhat.com (David Huff) Date: Tue, 02 Dec 2008 12:03:41 -0500 Subject: [Thincrust-devel] spin-kickstarts In-Reply-To: <4935435A.4000602@redhat.com> References: <4935435A.4000602@redhat.com> Message-ID: <49356A6D.6050508@redhat.com> Bryan Kearney wrote: > Huff: > > With the new doco on the website, what is the purpose of > spin-kickstartts? Will this contain the info which was going to be in > the appliance-os rpm? > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel The appliance-os RPM got rejected for being included in fedora. To consume the AOS definition you must install the spin-kickstart package which contains the AOS definition. -D From bkearney at redhat.com Tue Dec 2 17:00:04 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 02 Dec 2008 12:00:04 -0500 Subject: [Thincrust-devel] spin-kickstarts In-Reply-To: <49356A6D.6050508@redhat.com> References: <4935435A.4000602@redhat.com> <49356A6D.6050508@redhat.com> Message-ID: <49356994.3060108@redhat.com> David Huff wrote: > Bryan Kearney wrote: >> Huff: >> >> With the new doco on the website, what is the purpose of >> spin-kickstartts? Will this contain the info which was going to be in >> the appliance-os rpm? >> >> -- bk >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > > The appliance-os RPM got rejected for being included in fedora. To > consume the AOS definition you must install the spin-kickstart package > which contains the AOS definition. I did not see the package list as a seperate entity. Is that in there? -- bk From dhuff at redhat.com Tue Dec 2 17:06:04 2008 From: dhuff at redhat.com (David Huff) Date: Tue, 02 Dec 2008 12:06:04 -0500 Subject: [Thincrust-devel] spin-kickstarts In-Reply-To: <49356994.3060108@redhat.com> References: <4935435A.4000602@redhat.com> <49356A6D.6050508@redhat.com> <49356994.3060108@redhat.com> Message-ID: <49356AFC.1090902@redhat.com> Bryan Kearney wrote: > David Huff wrote: >> Bryan Kearney wrote: >>> Huff: >>> >>> With the new doco on the website, what is the purpose of >>> spin-kickstartts? Will this contain the info which was going to be in >>> the appliance-os rpm? >>> >>> -- bk >>> >>> _______________________________________________ >>> Thincrust-devel mailing list >>> Thincrust-devel at redhat.com >>> https://www.redhat.com/mailman/listinfo/thincrust-devel >> >> The appliance-os RPM got rejected for being included in fedora. To >> consume the AOS definition you must install the spin-kickstart package >> which contains the AOS definition. > > I did not see the package list as a seperate entity. Is that in there? > > -- bk > I have submitted a patch for it to be included in future versions of the spin-kickstart rpm however it is not in the current version. -D From dhuff at redhat.com Tue Dec 2 18:46:13 2008 From: dhuff at redhat.com (David Huff) Date: Tue, 02 Dec 2008 13:46:13 -0500 Subject: [Thincrust-devel] appliance-tools update for F-10 Message-ID: <49358275.5070700@redhat.com> An appliance-tools update in updates repo and available for F-10 via yum, this newest package includes the latest features for the appliance-tools package including: - Added support for tar archives - Added support for both zip and zip64 functionality - Added md5/sha256 disk signature support - Added support for including extra file(s) in the appliance package - Added option for -o outdir, appliance package in a seprate dir under appliance name - Also includes several bug fixes F-10 appliance-tools.noarch 0:003.9-1.fc10 http://admin.fedoraproject.org/updates/appliance-tools-003.9-1.fc10 -D From dhuff at redhat.com Tue Dec 2 19:28:10 2008 From: dhuff at redhat.com (David Huff) Date: Tue, 02 Dec 2008 14:28:10 -0500 Subject: [Thincrust-devel] [Fwd: [Fedora Update] [new] appliance-tools-002.8-2.fc9] Message-ID: <49358C4A.6090401@redhat.com> New build submitted for F-9 updates-testing. This has the latest features and fixed the broken dep issue on ppc64. I will let y'all know when its in stable an d available in the updates repo. -D -------------- next part -------------- An embedded message was scrubbed... From: updates at fedoraproject.org Subject: [Fedora Update] [new] appliance-tools-002.8-2.fc9 Date: Tue, 02 Dec 2008 19:24:32 +0000 Size: 8318 URL: From dhuff at redhat.com Fri Dec 5 02:33:21 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 04 Dec 2008 21:33:21 -0500 Subject: [Thincrust-devel] [Fwd: appliance-tools-004-2.fc11 successfully tagged into dist-f11 by jkeating] Message-ID: <493892F1.7050106@redhat.com> -------------- next part -------------- An embedded message was scrubbed... From: Koji Build System Subject: appliance-tools-004-2.fc11 successfully tagged into dist-f11 by jkeating Date: Thu, 4 Dec 2008 22:46:36 +0000 (UTC) Size: 2887 URL: From jboggs at redhat.com Fri Dec 5 14:25:29 2008 From: jboggs at redhat.com (Joey Boggs) Date: Fri, 05 Dec 2008 09:25:29 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 Message-ID: <493939D9.8080307@redhat.com> This adds support to bundle ec2 images and upload to S3. EC2 ami/api tools are required to be installed -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ec2-bundle.patch URL: From bkearney at redhat.com Fri Dec 5 16:25:00 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 05 Dec 2008 11:25:00 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 In-Reply-To: <493939D9.8080307@redhat.com> References: <493939D9.8080307@redhat.com> Message-ID: <493955DC.7040108@redhat.com> Joey Boggs wrote: > This adds support to bundle ec2 images and upload to S3. EC2 ami/api > tools are required to be installed > Thanks.. I have added and pushed this. Do you recall where to get he ec2-register script from? Do you think it makes sense to break this up into bundle and upload packages? Also.. can you start to look at the vmware conversion as well. -- bk From dhuff at redhat.com Fri Dec 5 16:40:55 2008 From: dhuff at redhat.com (David Huff) Date: Fri, 05 Dec 2008 11:40:55 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 In-Reply-To: <493955DC.7040108@redhat.com> References: <493939D9.8080307@redhat.com> <493955DC.7040108@redhat.com> Message-ID: <49395997.7000207@redhat.com> Bryan Kearney wrote: > Joey Boggs wrote: >> This adds support to bundle ec2 images and upload to S3. EC2 ami/api >> tools are required to be installed >> > > Thanks.. I have added and pushed this. Do you recall where to get he > ec2-register script from? http://developer.amazonwebservices.com/connect/entry.jspa?externalID=368&categoryID=88 > > Do you think it makes sense to break this up into bundle and upload > packages? > > Also.. can you start to look at the vmware conversion as well. > I am also working on this as well. I think there are two things here: 1. a procedure for running the current AOS spin release, raw and virtimage.xml file, to run in VMware. 2. Need to add functionality to appliance-creator to spit out vmware meta data as we discussed. I haven't had alot of cycles to devote to this yet..... -D From jboggs at redhat.com Fri Dec 5 16:43:26 2008 From: jboggs at redhat.com (Joey Boggs) Date: Fri, 05 Dec 2008 11:43:26 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 In-Reply-To: <493955DC.7040108@redhat.com> References: <493939D9.8080307@redhat.com> <493955DC.7040108@redhat.com> Message-ID: <49395A2E.4080405@redhat.com> The ec2-register comes from the api tools which also requires a jre to work. We can break it apart, I like the way the adk is modularized with dependencies, makes it much easier to develop for. I'll start working on the vmware portion shortly. Hugh/Perry has me working on the bare metal installer script for oVirt. Shouldn't take too long to finish off. Bryan Kearney wrote: > Joey Boggs wrote: >> This adds support to bundle ec2 images and upload to S3. EC2 ami/api >> tools are required to be installed >> > > Thanks.. I have added and pushed this. Do you recall where to get he > ec2-register script from? > > Do you think it makes sense to break this up into bundle and upload > packages? > > Also.. can you start to look at the vmware conversion as well. > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Fri Dec 5 16:42:18 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 05 Dec 2008 11:42:18 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 In-Reply-To: <49395997.7000207@redhat.com> References: <493939D9.8080307@redhat.com> <493955DC.7040108@redhat.com> <49395997.7000207@redhat.com> Message-ID: <493959EA.7020705@redhat.com> David Huff wrote: > Bryan Kearney wrote: >> Joey Boggs wrote: >>> This adds support to bundle ec2 images and upload to S3. EC2 ami/api >>> tools are required to be installed >>> >> >> Thanks.. I have added and pushed this. Do you recall where to get he >> ec2-register script from? > > http://developer.amazonwebservices.com/connect/entry.jspa?externalID=368&categoryID=88 > everything but the ec2-register command > >> >> Do you think it makes sense to break this up into bundle and upload >> packages? >> >> Also.. can you start to look at the vmware conversion as well. >> > > I am also working on this as well. I think there are two things here: > > 1. a procedure for running the current AOS spin release, raw and > virtimage.xml file, to run in VMware. > > 2. Need to add functionality to appliance-creator to spit out vmware > meta data as we discussed. So.. I have been looking at the adk as a tool which drives off of the virt-image metadata. That way it can simplify the appliance-creator > > > I haven't had alot of cycles to devote to this yet..... > > -D > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From dhuff at redhat.com Fri Dec 5 16:50:40 2008 From: dhuff at redhat.com (David Huff) Date: Fri, 05 Dec 2008 11:50:40 -0500 Subject: [Thincrust-devel] [patch] add ec2 bundling/upload support to adk2 In-Reply-To: <493959EA.7020705@redhat.com> References: <493939D9.8080307@redhat.com> <493955DC.7040108@redhat.com> <49395997.7000207@redhat.com> <493959EA.7020705@redhat.com> Message-ID: <49395BE0.3030504@redhat.com> Bryan Kearney wrote: > David Huff wrote: >> Bryan Kearney wrote: >>> Joey Boggs wrote: >>>> This adds support to bundle ec2 images and upload to S3. EC2 ami/api >>>> tools are required to be installed >>>> >>> >>> Thanks.. I have added and pushed this. Do you recall where to get he >>> ec2-register script from? >> >> http://developer.amazonwebservices.com/connect/entry.jspa?externalID=368&categoryID=88 >> > > everything but the ec2-register command ahh yes... these are the api tools not the ami tools: http://developer.amazonwebservices.com/connect/entry.jspa?externalID=351&categoryID=88 No rpm for these.... > >> >>> >>> Do you think it makes sense to break this up into bundle and upload >>> packages? >>> >>> Also.. can you start to look at the vmware conversion as well. >>> >> >> I am also working on this as well. I think there are two things here: >> >> 1. a procedure for running the current AOS spin release, raw and >> virtimage.xml file, to run in VMware. Joey, do you know off the top of your head what the best procedure for converting the aos spin, raw disk image and lib virt xml filt to vmware with current f-10 tools. >> >> 2. Need to add functionality to appliance-creator to spit out vmware >> meta data as we discussed. > > So.. I have been looking at the adk as a tool which drives off of the > virt-image metadata. That way it can simplify the appliance-creator This makes sence however I thought the current thinking was that Appliance creator would spit out a raw disk image and both virt-image and vmware meta data? -D From jsteer at bitscout.com Mon Dec 8 02:22:52 2008 From: jsteer at bitscout.com (Jon Steer) Date: Sun, 7 Dec 2008 21:22:52 -0500 Subject: [Thincrust-devel] EBS Support on thincrust EC2 ami's not working.. Message-ID: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> I was pretty psyched when I tripped across the thincrust AMI's. I had been looking for stripped down appliance AMI's. Unfortunately, I discovered that neither the F8 or F9 AMI's will attach to a EBS volume. In the F8 case, the xfs filesystem is missing. In the F9 case, after attaching to the volume ok, the first operation on the device (something like df -h) causes an immediate crash. You cannot reboot the instance afterwards leaving me to think that the xfs filesystem doesn't match Amazons. Unfortunately, given time constraints, I can't learn and build a thincrust appliance in the schedule time allotted for this task. One other note, when building a thincrust appliance, it would be useful to leave at least 100MB on / so that you can at least download one or two apps to play around with it. I found given the constraints that I had to create a newer larger AMI to in order to play with it. thanks, jon -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkearney at redhat.com Tue Dec 9 13:14:35 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 09 Dec 2008 08:14:35 -0500 Subject: [Thincrust-devel] EBS Support on thincrust EC2 ami's not working.. In-Reply-To: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> References: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> Message-ID: <493E6F3B.6080702@redhat.com> See below: Jon Steer wrote: > I was pretty psyched when I tripped across the thincrust AMI's. I had > been looking for stripped down appliance AMI's. Unfortunately, I > discovered that neither the F8 or F9 AMI's will attach to a EBS volume. That is a good comment. I will look to adding that back in. Originally the intent was to expose folks to the Appliance Operating System. But, I think it makes sense to expose the other Amazon services as well. > > In the F8 case, the xfs filesystem is missing. In the F9 case, after > attaching to the volume ok, the first operation on the device > (something like df -h) causes an immediate crash. > You cannot reboot the instance afterwards leaving me to think that the > xfs filesystem doesn't match Amazons. > > Unfortunately, given time constraints, I can't learn and build a > thincrust appliance in the schedule time allotted for this task. > > One other note, when building a thincrust appliance, it would be useful > to leave at least 100MB on / so that you can at least download one or > two apps to play around with it. I found given the constraints that I > had to create a newer larger AMI to in order to play with it. I show about 83 megs free when I launch 9. What were you looking to install? -- bk From bkearney at redhat.com Tue Dec 9 14:02:46 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 09 Dec 2008 09:02:46 -0500 Subject: [Thincrust-devel] Re: Auto-discard notification In-Reply-To: References: Message-ID: <493E7A86.6040809@redhat.com> jsteer at redhat.com wrote: > > > After doing a "yum check-update" and updating a couple of packages. > there wasn't enough room to install (for example) Fedora Directory. I > don't know whether I would have fit some part of LAMP on there (like > mySQL).. > > So, perhaps my request of 100MB was a little short, maybe 200 :-).. ok.. We will look to bump up the amis a bit on the next build. > > I am a little curious about your comment of "adding it back in" since > the F9 AMI had XFS. Was there something else needed? I just figured that > it was an F9->Amazon issue not necessarily something in the AMI itself. I need to look into this today. I will play around and send back to the list. > > BTW, keep up the good work. > I wish I had time right now to dive into building an AMI from scratch > since I am very familiar with the livecd-creator technology, but perhaps > in a month or so when I have more time. Thanks! Any feedback (postivve/negative) is appreciated. > > thanks, > jon > > > > On Tue, Dec 9, 2008 at 8:14 AM, Bryan Kearney > wrote: > > See below: > > > Jon Steer wrote: > > I was pretty psyched when I tripped across the thincrust AMI's. > I had been looking for stripped down appliance AMI's. > Unfortunately, I discovered that neither the F8 or F9 AMI's > will attach to a EBS volume. > > > That is a good comment. I will look to adding that back in. > Originally the intent was to expose folks to the Appliance Operating > System. But, I think it makes sense to expose the other Amazon > services as well. > > > > In the F8 case, the xfs filesystem is missing. In the F9 case, > after attaching to the volume ok, the first operation on the > device (something like df -h) causes an immediate crash. > You cannot reboot the instance afterwards leaving me to think > that the xfs filesystem doesn't match Amazons. > > Unfortunately, given time constraints, I can't learn and build a > thincrust appliance in the schedule time allotted for this task. > > One other note, when building a thincrust appliance, it would be > useful to leave at least 100MB on / so that you can at least > download one or two apps to play around with it. I found given > the constraints that I had to create a newer larger AMI to in > order to play with it. > > > I show about 83 megs free when I launch 9. What were you looking to > install? > > > -- bk > > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel > > > > > -- > "Don't stand still, if you see me running down the road, 'cause there is > trouble right behind me". From bkearney at redhat.com Tue Dec 9 15:02:22 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 09 Dec 2008 10:02:22 -0500 Subject: [Thincrust-devel] EBS Support on thincrust EC2 ami's not working.. In-Reply-To: <493E6F3B.6080702@redhat.com> References: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> <493E6F3B.6080702@redhat.com> Message-ID: <493E887E.8060505@redhat.com> Bryan Kearney wrote: > See below: > > Jon Steer wrote: >> I was pretty psyched when I tripped across the thincrust AMI's. I had >> been looking for stripped down appliance AMI's. Unfortunately, I >> discovered that neither the F8 or F9 AMI's will attach to a EBS volume. Just following up. What steps did you use. I did the followng: - Created a volume from ElasticFox - Launched an Thincrust-F9 instance. - Attached it to a running instance on device /dev/sdb - did mkfs -t ext3 /dev/sdb - mount -f ext3 /dev/sdb /mnt2 And I could access it. from the images. i could then unmount it and re-mount it on another Thincrust-F9 and a Thincrust-F8 machine. -- bk From jsteer at bitscout.com Tue Dec 9 15:43:50 2008 From: jsteer at bitscout.com (Jon Steer) Date: Tue, 9 Dec 2008 10:43:50 -0500 Subject: [Thincrust-devel] EBS Support on thincrust EC2 ami's not working.. In-Reply-To: <493E887E.8060505@redhat.com> References: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> <493E6F3B.6080702@redhat.com> <493E887E.8060505@redhat.com> Message-ID: <74e6f65d0812090743x1cca2869uca1a664d33f5c89@mail.gmail.com> the difference I used xfs instead of ext3 following the Amazon directions http://developer.amazonwebservices.com/connect/entry.jspa?categoryID=100&externalID=1663 . create a 4GB volume in Elastic fox on /dev/sdl Launch the thincrust f9 ami from elasticfox on a minimal instance attach the ami to the voume with Elasticfox - yum check-update - yum -y update fedora-release - yum check-update - mkfs.xfs /dev/sdl - add sdl to fstab - mkdir /vol - mount /vol - df -h crashed the AMI after this, the ami won't reboot either. I had made an assumption (bad I guess) that Amazon required XFS.. jon On Tue, Dec 9, 2008 at 10:02 AM, Bryan Kearney wrote: > Bryan Kearney wrote: > >> See below: >> >> Jon Steer wrote: >> >>> I was pretty psyched when I tripped across the thincrust AMI's. I had >>> been looking for stripped down appliance AMI's. Unfortunately, I discovered >>> that neither the F8 or F9 AMI's will attach to a EBS volume. >>> >> > Just following up. What steps did you use. I did the followng: > > - Created a volume from ElasticFox > - Launched an Thincrust-F9 instance. > - Attached it to a running instance on device /dev/sdb > - did mkfs -t ext3 /dev/sdb > - mount -f ext3 /dev/sdb /mnt2 > > And I could access it. from the images. i could then unmount it and > re-mount it on another Thincrust-F9 and a Thincrust-F8 machine. > > > -- bk > > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel > -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From jboggs at redhat.com Tue Dec 9 19:47:08 2008 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 09 Dec 2008 14:47:08 -0500 Subject: [Thincrust-devel] EBS Support on thincrust EC2 ami's not working.. In-Reply-To: <74e6f65d0812090743x1cca2869uca1a664d33f5c89@mail.gmail.com> References: <74e6f65d0812071822w4f272b6frc6b22246bd940132@mail.gmail.com> <493E6F3B.6080702@redhat.com> <493E887E.8060505@redhat.com> <74e6f65d0812090743x1cca2869uca1a664d33f5c89@mail.gmail.com> Message-ID: <493ECB3C.2060809@redhat.com> Jon, I figured it out, in order for you to mount the xfs file system you will need to modprobe the xfs module prior to trying to mount it and it will work, so looks like a bug. The Thincrust ami's currently run a Fedora 8 kernel that is compatible with EC2 provided kernel modules, we will be updating that shortly. If you build a custom ami just create a file /etc/rc.modules and make it executable. Within that file add: modprobe xfs That will allow you to mount those file systems on boot without building a custom kernel. [root at domU-12-31-39-03-41-F3 ~]# mkfs.xfs /dev/sdb meta-data=/dev/sdb isize=256 agcount=4, agsize=65536 blks = sectsz=512 attr=2 data = bsize=4096 blocks=262144, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=4096 blocks=0, rtextents=0 [root at domU-12-31-39-03-41-F3 ~]# mkdir /vol [root at domU-12-31-39-03-41-F3 ~]# mount /dev/sdb /vol -t xfs [root at domU-12-31-39-03-41-F3 ~]# mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda2 on /mnt type ext3 (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/sdb on /vol type xfs (rw) [root at domU-12-31-39-03-41-F3 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 485M 444M 42M 92% / /dev/sda2 147G 188M 140G 1% /mnt none 854M 0 854M 0% /dev/shm /dev/sdb 1014M 160K 1014M 1% /vol [root at domU-12-31-39-03-41-F3 ~]# cd /vol [root at domU-12-31-39-03-41-F3 vol]# dd if=/dev/zero of=testfile bs=1M count=500 500+0 records in 500+0 records out 524288000 bytes (524 MB) copied, 9.47931 s, 55.3 MB/s [root at domU-12-31-39-03-41-F3 vol]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 485M 444M 42M 92% / /dev/sda2 147G 188M 140G 1% /mnt none 854M 0 854M 0% /dev/shm /dev/sdb 1014M 501M 514M 50% /vol Jon Steer wrote: > the difference I used xfs instead of ext3 following the Amazon directions > http://developer.amazonwebservices.com/connect/entry.jspa?categoryID=100&externalID=1663 > > . > create a 4GB volume in Elastic fox on /dev/sdl > Launch the thincrust f9 ami from elasticfox on a minimal instance > attach the ami to the voume with Elasticfox > - yum check-update > - yum -y update fedora-release > - yum check-update > - mkfs.xfs /dev/sdl > - add sdl to fstab > - mkdir /vol > - mount /vol > - df -h crashed the AMI > > after this, the ami won't reboot either. > > I had made an assumption (bad I guess) that Amazon required XFS.. > > jon > > > > On Tue, Dec 9, 2008 at 10:02 AM, Bryan Kearney > wrote: > > Bryan Kearney wrote: > > See below: > > Jon Steer wrote: > > I was pretty psyched when I tripped across the thincrust > AMI's. I had been looking for stripped down appliance > AMI's. Unfortunately, I discovered that neither the F8 or > F9 AMI's will attach to a EBS volume. > > > Just following up. What steps did you use. I did the followng: > > - Created a volume from ElasticFox > - Launched an Thincrust-F9 instance. > - Attached it to a running instance on device /dev/sdb > - did mkfs -t ext3 /dev/sdb > - mount -f ext3 /dev/sdb /mnt2 > > And I could access it. from the images. i could then unmount it > and re-mount it on another Thincrust-F9 and a Thincrust-F8 machine. > > > -- bk > > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel > > > > > -- > "Don't stand still, if you see me running down the road, 'cause there > is trouble right behind me". > ------------------------------------------------------------------------ > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From dhuff at redhat.com Thu Dec 11 16:04:07 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 11 Dec 2008 11:04:07 -0500 Subject: [Thincrust-devel] [Fwd: [Fedora Update] [comment] appliance-tools-002.8-2.fc9] Message-ID: <494139F7.3040704@redhat.com> An embedded message was scrubbed... From: updates at fedoraproject.org Subject: [Fedora Update] [comment] appliance-tools-002.8-2.fc9 Date: Thu, 11 Dec 2008 08:00:08 +0000 Size: 8961 URL: From dhuff at redhat.com Thu Dec 11 16:08:04 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 11 Dec 2008 11:08:04 -0500 Subject: [Thincrust-devel] appliance-tools update for F-10 In-Reply-To: <49358275.5070700@redhat.com> References: <49358275.5070700@redhat.com> Message-ID: <49413AE4.5040600@redhat.com> Update now available for F-9 via yum, appliance-tools-002.8-2.fc9. This build has the same features as the F-10 update below. More info: https://admin.fedoraproject.org/updates/appliance-tools-002.8-2.fc9 -D David Huff wrote: > An appliance-tools update in updates repo and available for F-10 via > yum, this newest package includes the latest features for the > appliance-tools package including: > > - Added support for tar archives > - Added support for both zip and zip64 functionality > - Added md5/sha256 disk signature support > - Added support for including extra file(s) in the appliance package > - Added option for -o outdir, appliance package in a seprate dir under > appliance name > - Also includes several bug fixes > > > F-10 > appliance-tools.noarch 0:003.9-1.fc10 > http://admin.fedoraproject.org/updates/appliance-tools-003.9-1.fc10 > > -D > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Thu Dec 11 21:36:04 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 11 Dec 2008 16:36:04 -0500 Subject: [Thincrust-devel] Passing a relative path to appliance-creator Message-ID: <494187C4.6080602@redhat.com> Huff: Can you take a look at passing a relative path to appliance creator: appliance-creator -t some/path It causes extra logs. Is there actually a side-effect going on? Bobmcw found this today. -- bk From dhuff at redhat.com Mon Dec 15 16:05:51 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 15 Dec 2008 11:05:51 -0500 Subject: [Thincrust-devel] Passing a relative path to appliance-creator In-Reply-To: <494187C4.6080602@redhat.com> References: <494187C4.6080602@redhat.com> Message-ID: <4946805F.3060909@redhat.com> Bryan Kearney wrote: > Huff: > > Can you take a look at passing a relative path to appliance creator: > > appliance-creator -t some/path > > It causes extra logs. Is there actually a side-effect going on? Bobmcw > found this today. > > -- bk Is this the error that you are getting? Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/python-2.6-2.fc11.x86_64.rpm ...OK Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/glibc-common-2.8.90-17.x86_64.rpm ...OK Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/kernel-2.6.28-0.127.rc8.git1.fc11.x86_64.rpm ...OK Unable to create appliance : Unable to install: [('installing package kernel-2.6.28-0.127.rc8.git1.fc11.x86_64 needs 46MB on the /tmp/appliance-creator/imgcreate-3Yr8OG/install_root filesystem', (9, '/tmp/appliance-creator/imgcreate-3Yr8OG/install_root', 47747072L)), ('installing package system-config-firewall-tui-1.2.13-3.fc11.noarch needs 48MB on the /tmp/appliance-creator/imgcreate-3Yr8OG/install_root filesystem', (9, '/tmp/appliance-creator/imgcreate-3Yr8OG/install_root', 50057216L))] -D From bmcwhirt at redhat.com Mon Dec 15 20:23:24 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Mon, 15 Dec 2008 15:23:24 -0500 Subject: [Thincrust-devel] Passing a relative path to appliance-creator In-Reply-To: <4946805F.3060909@redhat.com> References: <494187C4.6080602@redhat.com> <4946805F.3060909@redhat.com> Message-ID: The error I was getting when using a relative path was something along the lines of "XXX v1.0-3 already installed and latest version" or somesuch odd. -Bob On Dec 15, 2008, at 11:05 AM, David Huff wrote: > Bryan Kearney wrote: >> Huff: >> Can you take a look at passing a relative path to appliance creator: >> appliance-creator -t some/path >> It causes extra logs. Is there actually a side-effect going on? >> Bobmcw found this today. >> -- bk > > > Is this the error that you are getting? > > Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/python-2.6-2.fc11.x86_64.rpm > ...OK > Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/glibc-common-2.8.90-17.x86_64.rpm > ...OK > Retrieving http://download.fedora.devel.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/kernel-2.6.28-0.127.rc8.git1.fc11.x86_64.rpm > ...OK > Unable to create appliance : Unable to install: [('installing > package kernel-2.6.28-0.127.rc8.git1.fc11.x86_64 needs 46MB on the / > tmp/appliance-creator/imgcreate-3Yr8OG/install_root filesystem', (9, > '/tmp/appliance-creator/imgcreate-3Yr8OG/install_root', 47747072L)), > ('installing package system-config-firewall-tui-1.2.13-3.fc11.noarch > needs 48MB on the /tmp/appliance-creator/imgcreate-3Yr8OG/ > install_root filesystem', (9, '/tmp/appliance-creator/ > imgcreate-3Yr8OG/install_root', 50057216L))] > > > -D > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From dhuff at redhat.com Mon Dec 15 21:45:55 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 15 Dec 2008 16:45:55 -0500 Subject: [Thincrust-devel] Passing a relative path to appliance-creator In-Reply-To: References: <494187C4.6080602@redhat.com> <4946805F.3060909@redhat.com> Message-ID: <4946D013.7020904@redhat.com> Bob McWhirter wrote: > The error I was getting when using a relative path was something along > the lines of "XXX v1.0-3 already installed and latest version" or > somesuch odd. > > -Bob yea it looks like its a bug with livecd-tools, if an relative path is passed it sets the instroot to "relative path" which it then passes to yum as the install root, which causes the oddies. I'll post a patch to livecd-tools. -D Fix: /imgcreate/creator.py line 385 self.__builddir = tempfile.mkdtemp(dir = os.path.abspath(self.tmpdir), prefix = "imgcreate-") From bmcwhirt at redhat.com Tue Dec 16 01:13:26 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Mon, 15 Dec 2008 20:13:26 -0500 Subject: [Thincrust-devel] Multiple appliances per image? Message-ID: <1694EDB6-68E0-40CB-80AF-9ACCCA229489@redhat.com> Howdy-- I've been working on fairly fine-grained appliances, with the "appliance" as my unit of division. But some of these appliances are small, and could cohabitate within the same image. Looking at lib/ace.rb, though, am I correct to assume that ACE really likes exactly 1 appliance on a machine at a time? Is there any particular strategy for merging multiple discrete appliances into a single image, and have ACE do nice things with it? If not, is it on the roadmap? Thanks, -Bob From bkearney at redhat.com Tue Dec 16 13:37:01 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 16 Dec 2008 08:37:01 -0500 Subject: [Thincrust-devel] Multiple appliances per image? In-Reply-To: <1694EDB6-68E0-40CB-80AF-9ACCCA229489@redhat.com> References: <1694EDB6-68E0-40CB-80AF-9ACCCA229489@redhat.com> Message-ID: <4947AEFD.5000004@redhat.com> Bob McWhirter wrote: > Howdy-- > > I've been working on fairly fine-grained appliances, with the > "appliance" as my unit of division. > > But some of these appliances are small, and could cohabitate within the > same image. Looking at lib/ace.rb, though, am I correct to assume that > ACE really likes exactly 1 appliance on a machine at a time? That was the thinking. It would be trivial to allow it to handle more then one appliance, run it serially. Would that be the desired behaviour? Another solution would be to combine the puppet files into a single file. Do you have a preference? If not, I can knock out the former and let you give it a try. -- bk From bmcwhirt at redhat.com Tue Dec 16 13:45:14 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Tue, 16 Dec 2008 08:45:14 -0500 Subject: [Thincrust-devel] Multiple appliances per image? In-Reply-To: <4947AEFD.5000004@redhat.com> References: <1694EDB6-68E0-40CB-80AF-9ACCCA229489@redhat.com> <4947AEFD.5000004@redhat.com> Message-ID: <4C5EED83-8B9E-45A7-BCFB-85BC2A9460F0@redhat.com> > That was the thinking. It would be trivial to allow it to handle > more then one appliance, run it serially. Would that be the desired > behaviour? Another solution would be to combine the puppet files > into a single file. > > Do you have a preference? If not, I can knock out the former and let > you give it a try. Yah, serially would be a-okay. Though, thinking I might still have to do some puppet combination, so things like banners don't get trampled by the last recipe to run, since it consumes $appliance_name:, etc. Or do you think there's some way to do a merge in the image itself to handle banners, the appliance- info file, etc? Thanks, -Bob From bkearney at redhat.com Tue Dec 16 16:16:53 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 16 Dec 2008 11:16:53 -0500 Subject: [Thincrust-devel] Multiple appliances per image? In-Reply-To: <4C5EED83-8B9E-45A7-BCFB-85BC2A9460F0@redhat.com> References: <1694EDB6-68E0-40CB-80AF-9ACCCA229489@redhat.com> <4947AEFD.5000004@redhat.com> <4C5EED83-8B9E-45A7-BCFB-85BC2A9460F0@redhat.com> Message-ID: <4947D475.402@redhat.com> Bob McWhirter wrote: >> That was the thinking. It would be trivial to allow it to handle more >> then one appliance, run it serially. Would that be the desired >> behaviour? Another solution would be to combine the puppet files into >> a single file. >> >> Do you have a preference? If not, I can knock out the former and let >> you give it a try. > > Yah, serially would be a-okay. Give this a whirl. If it works for you, I can push it upstream. http://bkearney.fedorapeople.org/ace-0.0.4-1.fc10.noarch.rpm > > Though, thinking I might still have to do some puppet combination, so > things like banners don't get trampled by the last recipe to run, since > it consumes $appliance_name:, etc. Or do you think there's some way to > do a merge in the image itself to handle banners, the appliance-info > file, etc? This would require either manual combination of the files (e.g put the real meat of the recipe into a class) or some automated combination with conflict resolution. > > Thanks, > > -Bob > > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bmcwhirt at redhat.com Wed Dec 17 02:26:23 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Tue, 16 Dec 2008 21:26:23 -0500 Subject: [Thincrust-devel] ace-console.rpm? Message-ID: Hiya-- It seems ace-console.rpm isn't in the thincrust repo. Did it use to live there? Has it moved? Or am I just confused? I can't seem to find it in any normal repo or thincrust's. -Bob From bkearney at redhat.com Wed Dec 17 13:08:34 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 17 Dec 2008 08:08:34 -0500 Subject: [Thincrust-devel] Updated the documentation on the Appliance Configuration Engine Message-ID: <4948F9D2.5030508@redhat.com> Now that the Appliance Configuration Engine (ace) is in F9 and F10 the docs around using it got alot simpler. I updated them at the thincrust website. The most interesting change is that the examples page: http://www.thincrust.net/ace-examples.html Now provides the kickstart files directory. So, lets say you want to build the media wiki appliance. The steps for that are now: # yum install appliance-tools python-virtinst # wget http://www.thincrust.net/kickstarts/mediaWikiAppliance-f10.ks # appliance-creator -n mediaWiki --config mediaWikiAppliance-f10.ks # virt-image mediaWiki Hopefully this will help with the usage of the tools. Lemme know if you guys have questions or comments. -- bk From jboggs at redhat.com Wed Dec 17 21:33:57 2008 From: jboggs at redhat.com (Joey Boggs) Date: Wed, 17 Dec 2008 16:33:57 -0500 Subject: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 Message-ID: <49497045.8060608@redhat.com> The Fedora 10 version of Thincrust AOS is now available on EC2 AMI: ami-9055b1f9 Manifest: Thincrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml From bkearney at redhat.com Wed Dec 17 21:47:50 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 17 Dec 2008 16:47:50 -0500 Subject: [Thincrust-devel] Multi appliance Message-ID: <49497386.4070407@redhat.com> Bob: Which version of the ace were you using for multi appliance? I jus submitted version 4 to fedora and it should be in there. -- bk From jboggs at redhat.com Thu Dec 18 00:53:06 2008 From: jboggs at redhat.com (Joey Boggs) Date: Wed, 17 Dec 2008 19:53:06 -0500 Subject: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 In-Reply-To: <49497045.8060608@redhat.com> References: <49497045.8060608@redhat.com> Message-ID: <49499EF2.4030208@redhat.com> Discovered a problem with the AMI missing some packages, corrected that and published a new one. AMI: ami-3e56b257 Manifest: Thuncrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml Joey Boggs wrote: > The Fedora 10 version of Thincrust AOS is now available on EC2 > > AMI: ami-9055b1f9 > Manifest: > Thincrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Thu Dec 18 14:56:41 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 18 Dec 2008 09:56:41 -0500 Subject: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 In-Reply-To: <49499EF2.4030208@redhat.com> References: <49497045.8060608@redhat.com> <49499EF2.4030208@redhat.com> Message-ID: <494A64A9.10408@redhat.com> Joey Boggs wrote: > Discovered a problem with the AMI missing some packages, corrected that > and published a new one. > > AMI: ami-3e56b257 > Manifest: > Thuncrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml > The complete list of Thincrust ami ids can be found here: http://www.thincrust.net/aos.html -- bk From dhuff at redhat.com Thu Dec 18 16:34:41 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 18 Dec 2008 11:34:41 -0500 Subject: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 In-Reply-To: <49499EF2.4030208@redhat.com> References: <49497045.8060608@redhat.com> <49499EF2.4030208@redhat.com> Message-ID: <494A7BA1.4070105@redhat.com> Joey Boggs wrote: > Discovered a problem with the AMI missing some packages, corrected that > and published a new one. > > AMI: ami-3e56b257 > Manifest: > Thuncrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml > > > Joey Boggs wrote: >> The Fedora 10 version of Thincrust AOS is now available on EC2 >> >> AMI: ami-9055b1f9 >> Manifest: >> Thincrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml >> Joey out of curiosity how did you build these? Did you use the ADK? I have been playing around with the newest ADk stuff this week looking at some kind of build process that we could hand to some one like rel-eng to build AOS CLOUD and perhaps ovirt. -D From bmcwhirt at redhat.com Thu Dec 18 16:48:58 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Thu, 18 Dec 2008 11:48:58 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <49497386.4070407@redhat.com> References: <49497386.4070407@redhat.com> Message-ID: <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> I rebuilt one overnight, with a fresh cache, and the appliance ended up with: [root at localhost ~]# yum list installed ace* Installed Packages ace.noarch 0.0.3-7.fc10 installed ace-banners.noarch 0.0.3-7.fc10 installed ace-console.noarch 0.0.4-1.fc10 installed ace-console-wui.noarch 0.0.4-1.fc10 installed ace-ssh.noarch 0.0.3-7.fc10 installed [root at localhost ~]# Looks like I've not gotten the latest, maybe? This one didn't initialize both appliances. -Bob On Dec 17, 2008, at 4:47 PM, Bryan Kearney wrote: > Bob: > > Which version of the ace were you using for multi appliance? > > I jus submitted version 4 to fedora and it should be in there. > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Thu Dec 18 16:50:43 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 18 Dec 2008 11:50:43 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> Message-ID: <494A7F63.4050307@redhat.com> Bob McWhirter wrote: > I rebuilt one overnight, with a fresh cache, and the appliance ended up > with: > > [root at localhost ~]# yum list installed ace* > Installed Packages > ace.noarch > 0.0.3-7.fc10 installed > ace-banners.noarch > 0.0.3-7.fc10 installed > ace-console.noarch > 0.0.4-1.fc10 installed > ace-console-wui.noarch > 0.0.4-1.fc10 installed > ace-ssh.noarch > 0.0.3-7.fc10 installed > [root at localhost ~]# Yeah.. that is a mixed-install. You want 4-1 for all the packages. -- bk From jboggs at redhat.com Thu Dec 18 17:28:57 2008 From: jboggs at redhat.com (Joseph Boggs) Date: Thu, 18 Dec 2008 12:28:57 -0500 (EST) Subject: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 In-Reply-To: <494A7BA1.4070105@redhat.com> Message-ID: <1500562483.1178271229621337214.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> I used the adk to build up to the point of the ec2-upload-bundle due to a ruby garbage collection bug it would fail in F10. So I scp'd the manifest and image files over and uploaded from an F9 machine. ----- Original Message ----- From: "David Huff" To: "Thincrust tooling devel list" Sent: Thursday, December 18, 2008 11:34:41 AM GMT -05:00 US/Canada Eastern Subject: Re: [Thincrust-devel] Fedora 10 Thincrust now available on EC2 Joey Boggs wrote: > Discovered a problem with the AMI missing some packages, corrected that > and published a new one. > > AMI: ami-3e56b257 > Manifest: > Thuncrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml > > > Joey Boggs wrote: >> The Fedora 10 version of Thincrust AOS is now available on EC2 >> >> AMI: ami-9055b1f9 >> Manifest: >> Thincrust_AOS_Fedora10/Thincrust_AOS_Fedora10-ec2.disk0.manifest.xml >> Joey out of curiosity how did you build these? Did you use the ADK? I have been playing around with the newest ADk stuff this week looking at some kind of build process that we could hand to some one like rel-eng to build AOS CLOUD and perhaps ovirt. -D _______________________________________________ Thincrust-devel mailing list Thincrust-devel at redhat.com https://www.redhat.com/mailman/listinfo/thincrust-devel From bmcwhirt at redhat.com Fri Dec 19 05:44:50 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Fri, 19 Dec 2008 00:44:50 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <494A7F63.4050307@redhat.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> <494A7F63.4050307@redhat.com> Message-ID: <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> w00t! Confirmed working multi-appliance with the following: ace.noarch 0.0.4-1.fc10 installed ace-banners.noarch 0.0.4-1.fc10 installed ace-console.noarch 0.0.4-1.fc10 installed ace-console-wui.noarch 0.0.4-1.fc10 installed ace-ssh.noarch 0.0.4-1.fc10 installed [root at localhost ~]# On Dec 18, 2008, at 11:50 AM, Bryan Kearney wrote: > Bob McWhirter wrote: >> I rebuilt one overnight, with a fresh cache, and the appliance >> ended up with: >> [root at localhost ~]# yum list installed ace* >> Installed Packages >> ace.noarch >> 0.0.3-7.fc10 installed >> ace-banners.noarch >> 0.0.3-7.fc10 installed >> ace-console.noarch >> 0.0.4-1.fc10 installed >> ace-console-wui.noarch >> 0.0.4-1.fc10 installed >> ace-ssh.noarch >> 0.0.3-7.fc10 installed >> [root at localhost ~]# > > > Yeah.. that is a mixed-install. You want 4-1 for all the packages. > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bmcwhirt at redhat.com Fri Dec 19 06:03:29 2008 From: bmcwhirt at redhat.com (Bob McWhirter) Date: Fri, 19 Dec 2008 01:03:29 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> <494A7F63.4050307@redhat.com> <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> Message-ID: <06426369-1F72-4A0A-93E0-6821FB0CF2DE@redhat.com> Now that I'm multi-appliance enabled... Could the init.d script add some detail to the output? I currently get: Installing appliance Installing appliance Installing appliance If it could list the entry it's processing from appliancename, that'd be super nice. (Same with the "refreshing" boot output, too, please). Thanks! -Bob On Dec 19, 2008, at 12:44 AM, Bob McWhirter wrote: > w00t! > > Confirmed working multi-appliance with the following: > > ace.noarch > 0.0.4-1.fc10 installed > ace-banners.noarch > 0.0.4-1.fc10 installed > ace-console.noarch > 0.0.4-1.fc10 installed > ace-console-wui.noarch > 0.0.4-1.fc10 installed > ace-ssh.noarch > 0.0.4-1.fc10 installed > [root at localhost ~]# > > > On Dec 18, 2008, at 11:50 AM, Bryan Kearney wrote: > >> Bob McWhirter wrote: >>> I rebuilt one overnight, with a fresh cache, and the appliance >>> ended up with: >>> [root at localhost ~]# yum list installed ace* >>> Installed Packages >>> ace.noarch >>> 0.0.3-7.fc10 installed >>> ace-banners.noarch >>> 0.0.3-7.fc10 installed >>> ace-console.noarch >>> 0.0.4-1.fc10 installed >>> ace-console-wui.noarch >>> 0.0.4-1.fc10 installed >>> ace-ssh.noarch >>> 0.0.3-7.fc10 installed >>> [root at localhost ~]# >> >> >> Yeah.. that is a mixed-install. You want 4-1 for all the packages. >> >> -- bk >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From apevec at gmail.com Fri Dec 19 07:48:23 2008 From: apevec at gmail.com (Alan Pevec) Date: Fri, 19 Dec 2008 08:48:23 +0100 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <06426369-1F72-4A0A-93E0-6821FB0CF2DE@redhat.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> <494A7F63.4050307@redhat.com> <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> <06426369-1F72-4A0A-93E0-6821FB0CF2DE@redhat.com> Message-ID: <2be7262f0812182348v4503096bo5b4015afbee44277@mail.gmail.com> On Fri, Dec 19, 2008 at 7:03 AM, Bob McWhirter wrote: > Now that I'm multi-appliance enabled... > > Could the init.d script add some detail to the output? > > I currently get: > > Installing appliance > Installing appliance > Installing appliance > > If it could list the entry it's processing from appliancename, that'd be > super nice. +1 and please print [ OK ] or done when successful. Printing dots for progress feedback would also be very nice, but not sure if puppet gives you that information during execution? e.g. Installing 'jboxx' appliance ........ done Installing 'ovirt' appliance ........ done. From bkearney at redhat.com Fri Dec 19 12:18:58 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 19 Dec 2008 07:18:58 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <2be7262f0812182348v4503096bo5b4015afbee44277@mail.gmail.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> <494A7F63.4050307@redhat.com> <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> <06426369-1F72-4A0A-93E0-6821FB0CF2DE@redhat.com> <2be7262f0812182348v4503096bo5b4015afbee44277@mail.gmail.com> Message-ID: <494B9132.7030108@redhat.com> Alan Pevec wrote: > On Fri, Dec 19, 2008 at 7:03 AM, Bob McWhirter wrote: >> Now that I'm multi-appliance enabled... >> >> Could the init.d script add some detail to the output? >> >> I currently get: >> >> Installing appliance >> Installing appliance >> Installing appliance >> >> If it could list the entry it's processing from appliancename, that'd be >> super nice. > > +1 and please print [ OK ] or done when successful. > Printing dots for progress feedback would also be very nice, but not > sure if puppet gives you that information during execution? > e.g. > > Installing 'jboxx' appliance ........ done > Installing 'ovirt' appliance ........ done. > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel I will look at adding these this morning. And figure out why 4-1 is stuck. -- bk From bkearney at redhat.com Mon Dec 22 12:10:06 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 22 Dec 2008 07:10:06 -0500 Subject: [Thincrust-devel] Thincrust AMIs Message-ID: <494F839E.7070408@redhat.com> This was bounced over the wekeend. I am posting it here. Joey or David, have you seen this: Attempted to extend and rebundle the thincrust F10 ami (ami-3e56b257) .. but it failed when doing ec2-bundle-vol. mount: could not find any free loop device ERROR: execution failed: "mount -o loop /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" losetup -a returned nothing. I modified modprobe.conf with options loop max_loop=8 which I don't think should be required. When doing modprobe loop got FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory So, I'm presuming I can't rebundle the F10 image due to either some issue with the F10 image or when Amazon is injecting the kernel and libraries. jon -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". From bkearney at redhat.com Mon Dec 22 12:48:28 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 22 Dec 2008 07:48:28 -0500 Subject: [Thincrust-devel] Multi appliance In-Reply-To: <494B9132.7030108@redhat.com> References: <49497386.4070407@redhat.com> <0319F4D4-D9F1-442F-AF44-7B02C087C77C@redhat.com> <494A7F63.4050307@redhat.com> <9D6EF494-60D1-4EA3-A43B-BC94500B8309@redhat.com> <06426369-1F72-4A0A-93E0-6821FB0CF2DE@redhat.com> <2be7262f0812182348v4503096bo5b4015afbee44277@mail.gmail.com> <494B9132.7030108@redhat.com> Message-ID: <494F8C9C.5090100@redhat.com> Bryan Kearney wrote: > Alan Pevec wrote: > I will look at adding these this morning. And figure out why 4-1 is stuck. > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel 4-1 hit stable this morning. So if you are carrying your own version you should be able to drop it. -- bk From jon.steer at gmail.com Mon Dec 22 14:21:09 2008 From: jon.steer at gmail.com (Jon Steer) Date: Mon, 22 Dec 2008 09:21:09 -0500 Subject: [Thincrust-devel] Fwd: Extending Thincrust F10 AMI fails In-Reply-To: <74e6f65d0812211414g71f9b655g2d1d1079c7f8582d@mail.gmail.com> References: <74e6f65d0812211414g71f9b655g2d1d1079c7f8582d@mail.gmail.com> Message-ID: <74e6f65d0812220621m4442a372rf04d2d45734c9707@mail.gmail.com> Attempted to extend and rebundle the thincrust F10 ami (ami-3e56b257) .. but it failed when doing ec2-bundle-vol. mount: could not find any free loop device ERROR: execution failed: "mount -o loop /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" losetup -a returned nothing. I modified modprobe.conf with options loop max_loop=8 which I don't think should be required. When doing modprobe loop got FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory So, I'm presuming I can't rebundle the F10 image due to either some issue with the F10 image or when Amazon is injecting the kernel and libraries. jon Postscript Some additional information.. after googling about, it appears that if I grab the f9 /lib/modules/2.6.16-xenU I might be able to make this work, but I haven't a moment yet. -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From jboggs at redhat.com Mon Dec 22 14:56:27 2008 From: jboggs at redhat.com (Joey Boggs) Date: Mon, 22 Dec 2008 09:56:27 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494F839E.7070408@redhat.com> References: <494F839E.7070408@redhat.com> Message-ID: <494FAA9B.7090106@redhat.com> This is due to a kernel/modules mismatch, we install the modules from the 2.6.18.7-2 kernel from Fedora 8 during the conversion process since it's the only available Fedora kernel. In order to do this when bundling you have to specify the matching aki/ari images. This was missed during bundling. Is there something in the adk configuration so far where we can specify these entries? It will need to be done on all appliances ran though it for them to work properly. I'm rebundling the image now and will send out another email when it's available. Bryan Kearney wrote: > This was bounced over the wekeend. I am posting it here. Joey or > David, have you seen this: > > > > > Attempted to extend and rebundle the thincrust F10 ami (ami-3e56b257) > .. but it failed when doing ec2-bundle-vol. > > mount: could not find any free loop device > ERROR: execution failed: "mount -o loop > /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" > > losetup -a > > returned nothing. > > I modified modprobe.conf with > options loop max_loop=8 > > which I don't think should be required. When doing > modprobe loop > > got > FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such > file or directory > > So, I'm presuming I can't rebundle the F10 image due to either some > issue with the F10 image or when Amazon is injecting the kernel and > libraries. > > jon > > From bkearney at redhat.com Mon Dec 22 14:54:02 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 22 Dec 2008 09:54:02 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FAA9B.7090106@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> Message-ID: <494FAA0A.6030308@redhat.com> Yes.. pull down the latest adk. You can specify an appliance as follows: test: kickstart: "test.ks" memory: "512" cpus: "1" version: "1" checksum: True s3bucket: mahBucket ec2kernel: testkernel ec2ramdisk: testrd The ex2kerle and ramdisk only effect the ec2bundle. Is there something else it should hit? -- bk Joey Boggs wrote: > This is due to a kernel/modules mismatch, we install the modules from > the 2.6.18.7-2 kernel from Fedora 8 during the conversion process since > it's the only available Fedora kernel. In order to do this when bundling > you have to specify the matching aki/ari images. This was missed during > bundling. Is there something in the adk configuration so far where we > can specify these entries? It will need to be done on all appliances ran > though it for them to work properly. I'm rebundling the image now and > will send out another email when it's available. > > > > Bryan Kearney wrote: >> This was bounced over the wekeend. I am posting it here. Joey or >> David, have you seen this: >> >> >> >> >> Attempted to extend and rebundle the thincrust F10 ami (ami-3e56b257) >> .. but it failed when doing ec2-bundle-vol. >> >> mount: could not find any free loop device >> ERROR: execution failed: "mount -o loop >> /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" >> >> losetup -a >> >> returned nothing. >> >> I modified modprobe.conf with >> options loop max_loop=8 >> >> which I don't think should be required. When doing >> modprobe loop >> >> got >> FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such >> file or directory >> >> So, I'm presuming I can't rebundle the F10 image due to either some >> issue with the F10 image or when Amazon is injecting the kernel and >> libraries. >> >> jon >> >> > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From jboggs at redhat.com Mon Dec 22 15:02:07 2008 From: jboggs at redhat.com (Joey Boggs) Date: Mon, 22 Dec 2008 10:02:07 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FAA0A.6030308@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FAA0A.6030308@redhat.com> Message-ID: <494FABEF.6040102@redhat.com> We may want to restructure that some, since the default kernel we install is installed on all the appliances coming through there. We should default to those aki/ari images unless specified otherwise. I'll work with it some and see what I can come up with. Bryan Kearney wrote: > Yes.. pull down the latest adk. You can specify an appliance as follows: > > test: > kickstart: "test.ks" > memory: "512" > cpus: "1" > version: "1" > checksum: True > s3bucket: mahBucket > ec2kernel: testkernel > ec2ramdisk: testrd > > The ex2kerle and ramdisk only effect the ec2bundle. Is there something > else it should hit? > > -- bk > > Joey Boggs wrote: >> This is due to a kernel/modules mismatch, we install the modules from >> the 2.6.18.7-2 kernel from Fedora 8 during the conversion process >> since it's the only available Fedora kernel. In order to do this when >> bundling you have to specify the matching aki/ari images. This was >> missed during bundling. Is there something in the adk configuration >> so far where we can specify these entries? It will need to be done on >> all appliances ran though it for them to work properly. I'm >> rebundling the image now and will send out another email when it's >> available. >> >> >> >> Bryan Kearney wrote: >>> This was bounced over the wekeend. I am posting it here. Joey or >>> David, have you seen this: >>> >>> >>> >>> >>> Attempted to extend and rebundle the thincrust F10 ami >>> (ami-3e56b257) .. but it failed when doing ec2-bundle-vol. >>> >>> mount: could not find any free loop device >>> ERROR: execution failed: "mount -o loop >>> /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" >>> >>> losetup -a >>> >>> returned nothing. >>> >>> I modified modprobe.conf with >>> options loop max_loop=8 >>> >>> which I don't think should be required. When doing >>> modprobe loop >>> >>> got >>> FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such >>> file or directory >>> >>> So, I'm presuming I can't rebundle the F10 image due to either some >>> issue with the F10 image or when Amazon is injecting the kernel and >>> libraries. >>> >>> jon >>> >>> >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From jboggs at redhat.com Mon Dec 22 19:57:32 2008 From: jboggs at redhat.com (Joey Boggs) Date: Mon, 22 Dec 2008 14:57:32 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FAA9B.7090106@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> Message-ID: <494FF12C.7030903@redhat.com> Updated the ami to fix the kernel module mismatch Here's the new ami and I've tested that you can modprobe kernel modules in without any issues ami-2a5db943 If you rebundle with the same issue make sure you have associated the following aki and ari images. aki-a71cf9ce ari-a51cf9cc Joey Boggs wrote: > This is due to a kernel/modules mismatch, we install the modules from > the 2.6.18.7-2 kernel from Fedora 8 during the conversion process > since it's the only available Fedora kernel. In order to do this when > bundling you have to specify the matching aki/ari images. This was > missed during bundling. Is there something in the adk configuration so > far where we can specify these entries? It will need to be done on all > appliances ran though it for them to work properly. I'm rebundling the > image now and will send out another email when it's available. > > > > Bryan Kearney wrote: >> This was bounced over the wekeend. I am posting it here. Joey or >> David, have you seen this: >> >> >> >> >> Attempted to extend and rebundle the thincrust F10 ami (ami-3e56b257) >> .. but it failed when doing ec2-bundle-vol. >> >> mount: could not find any free loop device >> ERROR: execution failed: "mount -o loop >> /mnt/my-thincrust-f10-base-20081221 /mnt/img-mnt" >> >> losetup -a >> >> returned nothing. >> >> I modified modprobe.conf with >> options loop max_loop=8 >> >> which I don't think should be required. When doing >> modprobe loop >> >> got >> FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such >> file or directory >> >> So, I'm presuming I can't rebundle the F10 image due to either some >> issue with the F10 image or when Amazon is injecting the kernel and >> libraries. >> >> jon >> >> > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Mon Dec 22 20:29:16 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 22 Dec 2008 15:29:16 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FF12C.7030903@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FF12C.7030903@redhat.com> Message-ID: <494FF89C.3060601@redhat.com> Joey Boggs wrote: > Updated the ami to fix the kernel module mismatch > > Here's the new ami and I've tested that you can modprobe kernel modules > in without any issues > > ami-2a5db943 > > If you rebundle with the same issue make sure you have associated the > following aki and ari images. > aki-a71cf9ce > ari-a51cf9cc Thanks Joey. Are there doc changes we should make to the site? -- bk From jboggs at redhat.com Mon Dec 22 20:47:37 2008 From: jboggs at redhat.com (Joey Boggs) Date: Mon, 22 Dec 2008 15:47:37 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FF89C.3060601@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FF12C.7030903@redhat.com> <494FF89C.3060601@redhat.com> Message-ID: <494FFCE9.4010908@redhat.com> Just the ami associated with Fedora 10 but that's already done. Whenever we get ready to update the site with the adk docs we should overhaul the EC2 section as well. Bryan Kearney wrote: > Joey Boggs wrote: >> Updated the ami to fix the kernel module mismatch >> >> Here's the new ami and I've tested that you can modprobe kernel >> modules in without any issues >> >> ami-2a5db943 >> >> If you rebundle with the same issue make sure you have associated the >> following aki and ari images. >> aki-a71cf9ce >> ari-a51cf9cc > > > Thanks Joey. Are there doc changes we should make to the site? > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Tue Dec 23 12:05:35 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 23 Dec 2008 07:05:35 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FABEF.6040102@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FAA0A.6030308@redhat.com> <494FABEF.6040102@redhat.com> Message-ID: <4950D40F.9030401@redhat.com> Joey Boggs wrote: > We may want to restructure that some, since the default kernel we > install is installed on all the appliances coming through there. We > should default to those aki/ari images unless specified otherwise. I'll > work with it some and see what I can come up with. If you can throw a patch together for what you want to that would be great. Ideally.. this tool would get us kickstart to running image int he cloud.. including custom kernels. -- bk From bkearney at redhat.com Tue Dec 23 12:11:27 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 23 Dec 2008 07:11:27 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <494FFCE9.4010908@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FF12C.7030903@redhat.com> <494FF89C.3060601@redhat.com> <494FFCE9.4010908@redhat.com> Message-ID: <4950D56F.7040404@redhat.com> Joey Boggs wrote: > Just the ami associated with Fedora 10 but that's already done. Whenever > we get ready to update the site with the adk docs we should overhaul the > EC2 section as well. Do you have commit access to it? If so.. can you check in some changes? -- bk > > > Bryan Kearney wrote: >> Joey Boggs wrote: >>> Updated the ami to fix the kernel module mismatch >>> >>> Here's the new ami and I've tested that you can modprobe kernel >>> modules in without any issues >>> >>> ami-2a5db943 >>> >>> If you rebundle with the same issue make sure you have associated the >>> following aki and ari images. >>> aki-a71cf9ce >>> ari-a51cf9cc >> >> >> Thanks Joey. Are there doc changes we should make to the site? >> >> -- bk >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel C From jboggs at redhat.com Tue Dec 23 14:07:56 2008 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 23 Dec 2008 09:07:56 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <4950D56F.7040404@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FF12C.7030903@redhat.com> <494FF89C.3060601@redhat.com> <494FFCE9.4010908@redhat.com> <4950D56F.7040404@redhat.com> Message-ID: <4950F0BC.5010709@redhat.com> yeah, I'll put something together and put it out there, you still have to perform the deploy to the web server though right? Bryan Kearney wrote: > Joey Boggs wrote: >> Just the ami associated with Fedora 10 but that's already done. >> Whenever we get ready to update the site with the adk docs we should >> overhaul the EC2 section as well. > > Do you have commit access to it? If so.. can you check in some changes? > > -- bk > >> >> >> Bryan Kearney wrote: >>> Joey Boggs wrote: >>>> Updated the ami to fix the kernel module mismatch >>>> >>>> Here's the new ami and I've tested that you can modprobe kernel >>>> modules in without any issues >>>> >>>> ami-2a5db943 >>>> >>>> If you rebundle with the same issue make sure you have associated >>>> the following aki and ari images. >>>> aki-a71cf9ce >>>> ari-a51cf9cc >>> >>> >>> Thanks Joey. Are there doc changes we should make to the site? >>> >>> -- bk >>> >>> _______________________________________________ >>> Thincrust-devel mailing list >>> Thincrust-devel at redhat.com >>> https://www.redhat.com/mailman/listinfo/thincrust-devel >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel > C > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel From bkearney at redhat.com Tue Dec 23 15:10:13 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 23 Dec 2008 10:10:13 -0500 Subject: [Thincrust-devel] Thincrust AMIs In-Reply-To: <4950F0BC.5010709@redhat.com> References: <494F839E.7070408@redhat.com> <494FAA9B.7090106@redhat.com> <494FF12C.7030903@redhat.com> <494FF89C.3060601@redhat.com> <494FFCE9.4010908@redhat.com> <4950D56F.7040404@redhat.com> <4950F0BC.5010709@redhat.com> Message-ID: <4950FF55.7070309@redhat.com> Joey Boggs wrote: > yeah, I'll put something together and put it out there, you still have > to perform the deploy to the web server though right? Probably. Gimme a buzz when it is in there. -- bk From jon.steer at gmail.com Sat Dec 27 00:16:15 2008 From: jon.steer at gmail.com (Jon Steer) Date: Fri, 26 Dec 2008 19:16:15 -0500 Subject: [Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI Message-ID: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> This is a stumper.. Last week I took the newly rev'ed F10 AMI, booted it, and made a few derivatives of it. They all worked, last week. Today, I tried to boot up the derivatives and they failed with the following information in the console. Bringing up interface eth0: Determining IP information for eth0...RTNETLINK answers: No such process done. RTNETLINK answers: Network is down [ OK ] Starting system logger: [ OK ] Starting system message bus: [ OK ] Mounting other filesystems: [ OK ] Starting sshd: [ OK ] curl: (7) Failed to connect to 169.254.169.254: Network is unreachable Updating ec2-ami-tools curl: (6) Couldn't resolve host 's3.amazonaws.com' Fedora release 10.90 (Rawhide) Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) I'm a little confused on how this could have worked previously (I created each AMI, and then booted it to make sure it worked) and now it doesn't? Obviously, the network driver isn't being loaded? jon -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkearney at redhat.com Mon Dec 29 16:24:23 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 29 Dec 2008 11:24:23 -0500 Subject: [Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI In-Reply-To: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> References: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> Message-ID: <4958F9B7.9060508@redhat.com> Jon Steer wrote: > This is a stumper.. > Last week I took the newly rev'ed F10 AMI, booted it, and made a few > derivatives of it. > They all worked, last week. > > Today, I tried to boot up the derivatives and they failed with the > following information in the console. > > Bringing up interface eth0: > Determining IP information for eth0...RTNETLINK answers: No such process > done. > RTNETLINK answers: Network is down > [ OK ] > Starting system logger: [ OK ] > Starting system message bus: [ OK ] > Mounting other filesystems: [ OK ] > Starting sshd: [ OK ] > curl: (7) Failed to connect to 169.254.169.254 : > Network is unreachable > Updating ec2-ami-tools > curl: (6) Couldn't resolve host 's3.amazonaws.com ' > Fedora release 10.90 (Rawhide) > Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) When you rebundled the ami, did you specify a specific kernel and ramdisk? -- bk From jon.steer at gmail.com Mon Dec 29 16:32:46 2008 From: jon.steer at gmail.com (Jon Steer) Date: Mon, 29 Dec 2008 11:32:46 -0500 Subject: [Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI In-Reply-To: <4958F9B7.9060508@redhat.com> References: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> <4958F9B7.9060508@redhat.com> Message-ID: <74e6f65d0812290832n3c9418deqa4e5d0a61e2a36dc@mail.gmail.com> re: specific specific ramdisk and kernel.. yes, I thought I did. I also checked that the AMI ran after I saved it.. Below is the console output. I suspect that this line is telling me something *"PCI: Fatal: No config space access function found"* I'll try rebundling again and see if I get a different result. Linux version 2.6.21.7-2.fc8xen (mockbuild at xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:39:36 EST 2008 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 000000006ac00000 end: 000000006ac00000 type: 1 Xen: 0000000000000000 - 000000006ac00000 (usable) 980MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 186366 Normal 186366 -> 186366 HighMem 186366 -> 437248 early_node_map[1] active PFN ranges 0: 0 -> 437248 ACPI in unprivileged domain disabled Detected 2600.002 MHz processor. Built 1 zonelists. Total pages: 433833 Kernel command line: root=/dev/sda1 ro 4 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 2599.998 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000 Memory: 1711020k/1748992k available (2071k kernel code, 28636k reserved, 1080k data, 188k init, 1003528k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xee000000 - 0xf4ffe000 ( 111 MB) lowmem : 0xc0000000 - 0xed7fe000 ( 727 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e6e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e6e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6502.34 BogoMIPS (lpj=13004684) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1572864 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 6775k freed audit: initializing netlink socket (disabled) audit(1230567692.331:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.102 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Linux version 2.6.21.7-2.fc8xen (mockbuild at xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:39:36 EST 2008 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 000000006ac00000 end: 000000006ac00000 type: 1 Xen: 0000000000000000 - 000000006ac00000 (usable) 980MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 186366 Normal 186366 -> 186366 HighMem 186366 -> 437248 early_node_map[1] active PFN ranges 0: 0 -> 437248 ACPI in unprivileged domain disabled Detected 2600.002 MHz processor. Built 1 zonelists. Total pages: 433833 Kernel command line: root=/dev/sda1 ro 4 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 2599.998 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000 Memory: 1711020k/1748992k available (2071k kernel code, 28636k reserved, 1080k data, 188k init, 1003528k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xee000000 - 0xf4ffe000 ( 111 MB) lowmem : 0xc0000000 - 0xed7fe000 ( 727 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e6e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e6e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6502.34 BogoMIPS (lpj=13004684) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1572864 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 6775k freed audit: initializing netlink socket (disabled) audit(1230567692.331:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.102 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 powernow-k8: Found 1 Dual-Core AMD Opteron(tm) Processor 2218 HE processors (version 2.00.00) powernow-k8: BIOS error - no PSB or ACPI _PSS objects Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vbd/2051 XENBUS: Device with no driver: device/vbd/2049 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Freeing unused kernel memory: 188k freed Write protecting the kernel read-only data: 795k Red Hat nash version 6.0.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading xennet.ko module netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. Loading xenblk.ko module xen-vbd: registered block device major 8 Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Creating root device. Mounting root filesystem. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: /sbin/start_udev: line 131: /sbin/restorecon: No such file or directory the program '/bin/bash' called '/sbin/udevsettle', it should use 'udevadm settle ', this will stop working in a future release udevadm[315]: the program '/bin/bash' called '/sbin/udevsettle', it should use 'udevadm settle ', this will stop working in a future release [ OK ] Setting hostname localhost.localdomain: [ OK ] Setting up Logical Volume Management: File descriptor 7 (/sys/kernel/hotplug) leaked on lvm invocation. Parent PID 223: /bin/bash [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 /dev/sda1: clean, 22324/655360 files, 230544/2621440 blocks [/sbin/fsck.ext3 (1) -- /mnt] fsck.ext3 -a /dev/sda2 /dev/sda2: Adding dirhash hint to filesystem. /dev/sda2 has gone 181 days without being checked, check forced. /dev/sda2: 11/19546112 files (0.0% non-contiguous), 661385/39088128 blocks [PASSED] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0...RTNETLINK answers: No such process done. RTNETLINK answers: Network is down [ OK ] Starting system logger: [ OK ] Starting system message bus: [ OK ] Mounting other filesystems: [ OK ] Starting sshd: [ OK ] curl: (7) Failed to connect to 169.254.169.254: Network is unreachable Updating ec2-ami-tools curl: (6) Couldn't resolve host 's3.amazonaws.com' Fedora release 10.90 (Rawhide) Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) ip-10-251-194-19 login: On Mon, Dec 29, 2008 at 11:24 AM, Bryan Kearney wrote: > Jon Steer wrote: > >> This is a stumper.. >> Last week I took the newly rev'ed F10 AMI, booted it, and made a few >> derivatives of it. >> They all worked, last week. >> >> Today, I tried to boot up the derivatives and they failed with the >> following information in the console. >> >> Bringing up interface eth0: Determining IP information for >> eth0...RTNETLINK answers: No such process >> done. >> RTNETLINK answers: Network is down >> [ OK ] >> Starting system logger: [ OK ] >> Starting system message bus: [ OK ] >> Mounting other filesystems: [ OK ] >> Starting sshd: [ OK ] >> curl: (7) Failed to connect to 169.254.169.254 : >> Network is unreachable >> Updating ec2-ami-tools >> curl: (6) Couldn't resolve host 's3.amazonaws.com < >> http://s3.amazonaws.com>' >> Fedora release 10.90 (Rawhide) >> Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) >> > > When you rebundled the ami, did you specify a specific kernel and ramdisk? > > -- bk > > _______________________________________________ > Thincrust-devel mailing list > Thincrust-devel at redhat.com > https://www.redhat.com/mailman/listinfo/thincrust-devel > -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon.steer at gmail.com Tue Dec 30 01:24:04 2008 From: jon.steer at gmail.com (Jon Steer) Date: Mon, 29 Dec 2008 20:24:04 -0500 Subject: [Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI In-Reply-To: <74e6f65d0812290832n3c9418deqa4e5d0a61e2a36dc@mail.gmail.com> References: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> <4958F9B7.9060508@redhat.com> <74e6f65d0812290832n3c9418deqa4e5d0a61e2a36dc@mail.gmail.com> Message-ID: <74e6f65d0812291724t127761b4h62221a144f58de08@mail.gmail.com> Sorry, guess it is my bad... rebuilding and then explicitly stating the AKI and ARI produces images that run. thanks, jon On Mon, Dec 29, 2008 at 11:32 AM, Jon Steer wrote: > re: specific specific ramdisk and kernel.. > > yes, I thought I did. I also checked that the AMI ran after I saved it.. > Below is the console output. > I suspect that this line is telling me something > *"PCI: Fatal: No config space access function found"* > > > I'll try rebundling again and see if I get a different result. > > Linux version 2.6.21.7-2.fc8xen (mockbuild at xenbuilder1.fedora.redhat.com) > (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:39:36 > EST 2008 > BIOS-provided physical RAM map: > sanitize start > sanitize bail 0 > copy_e820_map() start: 0000000000000000 size: 000000006ac00000 end: > 000000006ac00000 type: 1 > Xen: 0000000000000000 - 000000006ac00000 (usable) > 980MB HIGHMEM available. > 727MB LOWMEM available. > NX (Execute Disable) protection: active > Zone PFN ranges: > DMA 0 -> 186366 > Normal 186366 -> 186366 > HighMem 186366 -> 437248 > early_node_map[1] active PFN ranges > 0: 0 -> 437248 > ACPI in unprivileged domain disabled > Detected 2600.002 MHz processor. > Built 1 zonelists. Total pages: 433833 > Kernel command line: root=/dev/sda1 ro 4 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c136c000 soft=c134c000 > PID hash table entries: 4096 (order: 12, 16384 bytes) > Xen reported: 2599.998 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000 > Memory: 1711020k/1748992k available (2071k kernel code, 28636k reserved, > 1080k data, 188k init, 1003528k highmem) > virtual kernel memory layout: > fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) > pkmap : 0xf5000000 - 0xf5200000 (2048 kB) > vmalloc : 0xee000000 - 0xf4ffe000 ( 111 MB) > lowmem : 0xc0000000 - 0xed7fe000 ( 727 MB) > .init : 0xc1319000 - 0xc1348000 ( 188 kB) > .data : 0xc1205e6e - 0xc1313fd4 (1080 kB) > .text : 0xc1000000 - 0xc1205e6e (2071 kB) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 6502.34 BogoMIPS > (lpj=13004684) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 512 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 1024K (64 bytes/line) > Checking 'hlt' instruction... OK. > SMP alternatives: switching to UP code > Freeing SMP alternatives: 13k freed > Brought up 1 CPUs > NET: Registered protocol family 16 > Brought up 1 CPUs > PCI: Fatal: No config space access function found > PCI: setting up Xen PCI frontend stub > Setting up standard PCI resources > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > TCP established hash table entries: 131072 (order: 8, 1572864 bytes) > TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > checking if image is initramfs... it is > Freeing initrd memory: 6775k freed > audit: initializing netlink socket (disabled) > audit(1230567692.331:1): initialized > highmem bounce pool size: 64 pages > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > ksign: Installing public key data > Loading keyring > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.102 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > input: Macintosh mouse button emulation as /class/input/input0 > Xen virtual console successfully installed as xvc0 > Linux version 2.6.21.7-2.fc8xen (mockbuild at xenbuilder1.fedora.redhat.com) > (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:39:36 > EST 2008 > BIOS-provided physical RAM map: > sanitize start > sanitize bail 0 > copy_e820_map() start: 0000000000000000 size: 000000006ac00000 end: > 000000006ac00000 type: 1 > Xen: 0000000000000000 - 000000006ac00000 (usable) > 980MB HIGHMEM available. > 727MB LOWMEM available. > NX (Execute Disable) protection: active > Zone PFN ranges: > DMA 0 -> 186366 > Normal 186366 -> 186366 > HighMem 186366 -> 437248 > early_node_map[1] active PFN ranges > 0: 0 -> 437248 > ACPI in unprivileged domain disabled > Detected 2600.002 MHz processor. > Built 1 zonelists. Total pages: 433833 > Kernel command line: root=/dev/sda1 ro 4 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c136c000 soft=c134c000 > PID hash table entries: 4096 (order: 12, 16384 bytes) > Xen reported: 2599.998 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000 > Memory: 1711020k/1748992k available (2071k kernel code, 28636k reserved, > 1080k data, 188k init, 1003528k highmem) > virtual kernel memory layout: > fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) > pkmap : 0xf5000000 - 0xf5200000 (2048 kB) > vmalloc : 0xee000000 - 0xf4ffe000 ( 111 MB) > lowmem : 0xc0000000 - 0xed7fe000 ( 727 MB) > .init : 0xc1319000 - 0xc1348000 ( 188 kB) > .data : 0xc1205e6e - 0xc1313fd4 (1080 kB) > .text : 0xc1000000 - 0xc1205e6e (2071 kB) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 6502.34 BogoMIPS > (lpj=13004684) > Security Framework v1.0.0 initialized > SELinux: Initializing. > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 512 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 1024K (64 bytes/line) > Checking 'hlt' instruction... OK. > SMP alternatives: switching to UP code > Freeing SMP alternatives: 13k freed > Brought up 1 CPUs > NET: Registered protocol family 16 > Brought up 1 CPUs > PCI: Fatal: No config space access function found > PCI: setting up Xen PCI frontend stub > Setting up standard PCI resources > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > TCP established hash table entries: 131072 (order: 8, 1572864 bytes) > TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > checking if image is initramfs... it is > Freeing initrd memory: 6775k freed > audit: initializing netlink socket (disabled) > audit(1230567692.331:1): initialized > highmem bounce pool size: 64 pages > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > ksign: Installing public key data > Loading keyring > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.102 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > input: Macintosh mouse button emulation as /class/input/input0 > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > usbcore: registered new interface driver hiddev > usbcore: registered new interface driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > TCP bic registered > Initializing XFRM netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > powernow-k8: Found 1 Dual-Core AMD Opteron(tm) Processor 2218 HE processors > (version 2.00.00) > powernow-k8: BIOS error - no PSB or ACPI _PSS objects > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vbd/2051 > XENBUS: Device with no driver: device/vbd/2049 > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > Freeing unused kernel memory: 188k freed > Write protecting the kernel read-only data: 795k > Red Hat nash version 6.0.19 starting > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Loading xennet.ko module > netfront: Initialising virtual ethernet driver. > netfront: device eth0 has flipping receive path. > Loading xenblk.ko module > xen-vbd: registered block device major 8 > Loading ehci-hcd.ko module > Loading ohci-hcd.ko module > Loading uhci-hcd.ko module > USB Universal Host Controller Interface driver v3.0 > Loading mbcache.ko module > Loading jbd.ko module > Loading ext3.ko module > Creating root device. > Mounting root filesystem. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > Welcome to Fedora > Press 'I' to enter interactive startup. > Starting udev: /sbin/start_udev: line 131: /sbin/restorecon: No such file > or directory > the program '/bin/bash' called '/sbin/udevsettle', it should use 'udevadm > settle ', this will stop working in a future release > udevadm[315]: the program '/bin/bash' called '/sbin/udevsettle', it should > use 'udevadm settle ', this will stop working in a future release > [ OK ] > Setting hostname localhost.localdomain: [ OK ] > Setting up Logical Volume Management: File descriptor 7 > (/sys/kernel/hotplug) leaked on lvm invocation. Parent PID 223: /bin/bash > [ OK ] > Checking filesystems > Checking all file systems. > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 > /dev/sda1: clean, 22324/655360 files, 230544/2621440 blocks > [/sbin/fsck.ext3 (1) -- /mnt] fsck.ext3 -a /dev/sda2 > /dev/sda2: Adding dirhash hint to filesystem. > /dev/sda2 has gone 181 days without being checked, check forced. > /dev/sda2: 11/19546112 files (0.0% non-contiguous), 661385/39088128 blocks > [PASSED] > Remounting root filesystem in read-write mode: [ OK ] > Mounting local filesystems: [ OK ] > Enabling /etc/fstab swaps: [ OK ] > Entering non-interactive startup > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: > Determining IP information for eth0...RTNETLINK answers: No such process > done. > RTNETLINK answers: Network is down > [ OK ] > Starting system logger: [ OK ] > Starting system message bus: [ OK ] > Mounting other filesystems: [ OK ] > Starting sshd: [ OK ] > curl: (7) Failed to connect to 169.254.169.254: Network is unreachable > Updating ec2-ami-tools > curl: (6) Couldn't resolve host 's3.amazonaws.com' > Fedora release 10.90 (Rawhide) > Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) > ip-10-251-194-19 login: > > On Mon, Dec 29, 2008 at 11:24 AM, Bryan Kearney wrote: > >> Jon Steer wrote: >> >>> This is a stumper.. >>> Last week I took the newly rev'ed F10 AMI, booted it, and made a few >>> derivatives of it. >>> They all worked, last week. >>> >>> Today, I tried to boot up the derivatives and they failed with the >>> following information in the console. >>> >>> Bringing up interface eth0: Determining IP information for >>> eth0...RTNETLINK answers: No such process >>> done. >>> RTNETLINK answers: Network is down >>> [ OK ] >>> Starting system logger: [ OK ] >>> Starting system message bus: [ OK ] >>> Mounting other filesystems: [ OK ] >>> Starting sshd: [ OK ] >>> curl: (7) Failed to connect to 169.254.169.254 : >>> Network is unreachable >>> Updating ec2-ami-tools >>> curl: (6) Couldn't resolve host 's3.amazonaws.com < >>> http://s3.amazonaws.com>' >>> Fedora release 10.90 (Rawhide) >>> Kernel 2.6.21.7-2.fc8xen on an i686 (/dev/xvc0) >>> >> >> When you rebundled the ami, did you specify a specific kernel and ramdisk? >> >> -- bk >> >> _______________________________________________ >> Thincrust-devel mailing list >> Thincrust-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/thincrust-devel >> > > > > -- > "Don't stand still, if you see me running down the road, 'cause there is > trouble right behind me". > -- "Don't stand still, if you see me running down the road, 'cause there is trouble right behind me". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkearney at redhat.com Tue Dec 30 13:31:21 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 30 Dec 2008 08:31:21 -0500 Subject: [Thincrust-devel] eth0 interface doesn't come up on latest derived F10 AMI In-Reply-To: <74e6f65d0812291724t127761b4h62221a144f58de08@mail.gmail.com> References: <74e6f65d0812261616m2a3da389sc174e294db6651c9@mail.gmail.com> <4958F9B7.9060508@redhat.com> <74e6f65d0812290832n3c9418deqa4e5d0a61e2a36dc@mail.gmail.com> <74e6f65d0812291724t127761b4h62221a144f58de08@mail.gmail.com> Message-ID: <495A22A9.60708@redhat.com> Jon Steer wrote: > Sorry, guess it is my bad... rebuilding and then explicitly stating the > AKI and ARI produces images that run. > > thanks, > jon Jon: Thanks for looking into this. Most of us are on vacation this week. We will work on the docs and talk with the Amazon folks about making the default ami/aki be the one you are in. -- bk