[ec2] Ubuntu-ec2 Digest, Vol 14, Issue 4

[kishore pulivarthi]

UN SUBSCRIBE ME  DON'T SENT MAIL TO ME

On 2/25/10, ubuntu-ec2-request at lists.ubuntu.com
<ubuntu-ec2-request at lists.ubuntu.com> wrote:
> Send Ubuntu-ec2 mailing list submissions to
> 	ubuntu-ec2 at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.ubuntu.com/mailman/listinfo/ubuntu-ec2
> or, via email, send a message with subject or body 'help' to
> 	ubuntu-ec2-request at lists.ubuntu.com
>
> You can reach the person managing the list at
> 	ubuntu-ec2-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ubuntu-ec2 digest..."
>
>
> Today's Topics:
>
>    1.  Upgrading Intrepid AMIs (Simon Detheridge)
>    2. Re:  Upgrading Intrepid AMIs (Eric Hammond)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Feb 2010 14:26:29 +0000 (GMT)
> From: Simon Detheridge <simon at widgit.com>
> Subject: [ec2] Upgrading Intrepid AMIs
> To: ubuntu-ec2 at lists.ubuntu.com
> Message-ID: <127172800.21571267021589882.JavaMail.root at ken>
> Content-Type: text/plain; charset=utf-8
>
> Hi all,
>
> I've been running some fairly well used AMIs based on the original 8.10 that
> first appeared. I couldn't use 8.04 at the time, because I needed some newer
> kernel features. I'm aware that support for 8.10 ends in a couple of months
> (I'm assuming this means no more security updates?) so I'll need to upgrade.
>
> Any issues surrounding upgrading? Is it safe to upgrade in-place, the same
> as I would my physical server?
>
> Thanks,
> Simon
>
> --
> Simon Detheridge - CTO, Widgit Software
> 26 Queen Street, Cubbington, CV32 7NA - Tel: +44 (0)1926 333680
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Feb 2010 11:22:28 -0800
> From: Eric Hammond <esh at ubuntu.com>
> Subject: Re: [ec2] Upgrading Intrepid AMIs
> To: Simon Detheridge <simon at widgit.com>
> Cc: ubuntu-ec2 at lists.ubuntu.com
> Message-ID: <4B857C74.70404 at ubuntu.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Simon:
>
> Assuming you're not running EBS boot instances, you cannot upgrade the
> kernel in place.  Even if you are running EBS boot instances, upgrading
> in place can be a bit messy and probably should not be tested first on
> your live systems.
>
> If possible, I recommend you start with the latest 9.10 AMIs and build
> your systems on new instances.
>
> If you have built extensively customized private AMIs, and you did not
> automate or document the software installation and customization, and
> you really want to try upgrading without starting from scratch, here is
> an approach which could let you test this without risking your currently
> running instances, but it gets complicated:
>
> - download the custom AMI bundle from S3
> - unbundle the image
> - create an EBS volume
> - copy image file system to the EBS volume
> - snapshot the EBS volume
> - register the snapshot as a new EBS boot AMI with the old aki+ari
> - run a new instance of the EBS boot AMI
> - upgrade the system in place
> - snapshot that instance's EBS volume
> - register that EBS snapshot as a new new AMI with the newer aki+ari
> - run a new instanced of the new new AMI and test
> - clean up the temporary instances, EBS volumes, and EBS snapshot
>
> You could also save the image as an S3 based AMI if that's what you want
> to run.
>
> I'm not sure if solicitation is allowed on this list, but if needed, I
> could help with this kind of small task.
>
> My standard recommendation, however, is to always start with fresh
> public AMIs and document/automate the installation of your
> customizations so that you can switch to new public AMIs whenever they
> come out.  Whether you run the installation scripts at boot time or run
> them to create private AMIs depends on how long they take and how
> quickly you need new instances to start.
>
> --
> Eric Hammond
>
>
>
> Simon Detheridge wrote:
>> Hi all,
>>
>> I've been running some fairly well used AMIs based on the original 8.10
>> that first appeared. I couldn't use 8.04 at the time, because I needed
>> some newer kernel features. I'm aware that support for 8.10 ends in a
>> couple of months (I'm assuming this means no more security updates?) so
>> I'll need to upgrade.
>>
>> Any issues surrounding upgrading? Is it safe to upgrade in-place, the same
>> as I would my physical server?
>>
>> Thanks,
>> Simon
>>
>
>
>
> ------------------------------
>
> --
> Ubuntu-ec2 mailing list
> Ubuntu-ec2 at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ec2
>
>
> End of Ubuntu-ec2 Digest, Vol 14, Issue 4
> *****************************************
>