[Labs-l] Starting migration to new hardware today, expect some downtime on your instances

Ryan Lane rlane32 at gmail.com
Sun Jul 8 00:59:34 UTC 2012


>> i-00000105 <-- deployment-transcoding
>
> That one can be deleted
>

Deleted.

>> i-00000263 <-- deployment-cache-upload
> I might need /etc from that one.
>

Ok. Let's handle this Monday, if that's ok with you.

>> i-0000025a <-- deployment-imagescaler01
>> i-00000264 <-- deployment-cache-bits
>> i-0000028c <-- deployment-jobrunner05
>> i-000002d3 <-- deployment-apache30
>> i-000002d4 <-- deployment-apache31
>
> They are, AFAIK, fully puppetized. Will rebuild those boxes on monday
> and let you know if they can safely be deleted for good.
>

Great!

>> i-000000e1 <-- deployment-wmsearch
>> i-000000f8 <-- deployment-backup
>> i-00000118 <-- deployment-feed in deployment-prep project
>
> Petan would know what they were for. wmsearch I guess to setup a Lucene
> search backend.
>

Heh. Peten created all three of these. deployment-backup, AFAIK, was a
replica of the database in deployment-prep. deployment-feed was
running the IRC server, right?

>> i-000002bd <-- deployment-bastion in deployment-prep project
>
> It was stuck somehow, I never managed to log in. Petan would be able to
> tell more about it.  I guess it just uses some 'bastion' puppet class.
>

So, it can be deleted?

- Ryan



More information about the Labs-l mailing list