Closed
Bug 720544
Opened 13 years ago
Closed 13 years ago
migrate cg-centos01 to scl3
Categories
(Infrastructure & Operations :: Virtualization, task)
Infrastructure & Operations
Virtualization
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
This VM is used for various things by various people. We'll plan to migrate it in early March.
That will require changing domain names and IPs, and some of the domains that will change are tied up in a registry change right now, hence the delay.
Reed would also like an IPv6 address for the host, as the sjc1 instance has one already.
| Assignee | ||
Comment 1•13 years ago
|
||
Actually, it will be easier to create a brand new VM in scl3 for this, and migrate the services on reed's timeline. So let's do that.
| Assignee | ||
Comment 2•13 years ago
|
||
new VM is in inventory: https://inventory.mozilla.org/en-US/systems/show/5206/
| Assignee | ||
Comment 3•13 years ago
|
||
Dan, over to you for this one. Specs should be identical to cg-centos01 in sjc1. CentOS 6 if possible. No puppet or anything. I can share the root pw with reed.
Assignee: dustin → server-ops
Component: Server Operations → Server Operations: Virtualization
QA Contact: cshields → dparsons
Updated•13 years ago
|
Assignee: server-ops → rbryce
Comment 4•13 years ago
|
||
CentOS 6 x86_64, please... The current one is CentOS 5 i386, which makes me regularly sad.
Comment 5•13 years ago
|
||
I created a Centos6.2_x86_64 template and deployed to esx cluster in SCL3. Need to figure out the community vlan net plumbing. Should be able to turn this over to dustin or reed shortly.
| Assignee | ||
Comment 6•13 years ago
|
||
rbryce, it looks from vc like this has been created with the wrong name - it should be reed1:
https://inventory.mozilla.org/en-US/systems/show/5206/
I changed this, put it on the community network, and booted it -- but I'm not sure what the root pw is. I'm also not sure what needs to change in inventory when the host is up -- MAC address? The IP should be 63.245.223.12. It's already in DNS. If we can set a random root password, I'll communicate that to reed and keep it in our password file.
I don't want to mess up the system that I'm not trained on by trying to finish this myself, so back to you :)
| Assignee | ||
Comment 7•13 years ago
|
||
rbryce finished this up. I'll find reed via IRC/GPG and get him the password.
| Assignee | ||
Comment 8•13 years ago
|
||
This still needs vmware tools (oops). I'll take care of that when I get the password gpg'd back from reed.
| Assignee | ||
Comment 9•13 years ago
|
||
vmware tools installed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 10•13 years ago
|
||
Reed, how comes the evacuation of the old VM?
Comment 11•13 years ago
|
||
I grabbed a backup of my home dir, and will restore as needed when the new box is ready.
| Assignee | ||
Comment 12•13 years ago
|
||
Nick, the new box is up - reed1.community.scl3.mozilla.com.
Comment 13•13 years ago
|
||
Ah, ok. Waiting on my logon and ssh to get configured then.
| Assignee | ||
Comment 14•13 years ago
|
||
Reed, when can we shut down the sjc1 host? We'll need to move the hardware on 5/14, so sometime before then!
| Assignee | ||
Comment 15•13 years ago
|
||
This wasn't supposed to, but just got unplugged and moved today.
Do you guys need anything on the old server, or can we call it dead?
Comment 16•13 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] from comment #15)
> This wasn't supposed to, but just got unplugged and moved today.
>
> Do you guys need anything on the old server, or can we call it dead?
Ugh, sorry, I didn't see your last comment. I do still need a few things, but if you can get me access for an hour or so, I can grab everything. I just need to rsync some stuff.
| Assignee | ||
Comment 17•13 years ago
|
||
Sounds like it is necessary -- we'll get you access to the data, but not in firedrill mode (so, tomorrow)
| Assignee | ||
Updated•13 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 18•13 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> Reed would also like an IPv6 address for the host, as the sjc1 instance has
> one already.
Also still missing an IPv6 address.
| Assignee | ||
Comment 19•13 years ago
|
||
IPv6 isn't up in scl3 yet, but hopefully will be by IPv6 day - XioNox is a good contact person in netops for that.
cg-centos01.community.scl3.mozilla.com is up now. Please get all of the info you need from it ASAP so we can shut it down, and comment here when that's done.
Comment 20•13 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] from comment #19)
> cg-centos01.community.scl3.mozilla.com is up now.
NXDOMAIN. Do you have the IP?
| Assignee | ||
Comment 21•13 years ago
|
||
(the NXDOMAIN got sorted in IRC. I forgot to commit the DNS change)
| Assignee | ||
Comment 22•13 years ago
|
||
OK to kill?
| Assignee | ||
Comment 23•13 years ago
|
||
Reed, I'm going to assume you've got the data off this host and destroy it once and for all. Please object here or in IRC in the next day if that's not the case!
Assignee: rbryce → dustin
| Assignee | ||
Comment 24•13 years ago
|
||
OK, halted, deleted from DNS.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•