760963 - Clone community VM for Calendar from sea-vm-win32-2

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Justin Wood (:Callek)]

+++ This bug was initially created as a clone of Bug #760961 +++

Actions here:

IT:

  * Clone a new VM for NSS from sea-vm-win32-2.community.scl3.mozilla.com
    * Current Admin PW is the SeaMonkey password, and machine can go down at your leisure
  * Ensure IP/Hostname is proper for NSS here
  * Have someone [probably dustin] change PW's for :Fallen
    * Needs Administrator/cltbld pw changed
    * Needs Autologin pw changed in registry for cltbld user
  * Might not need 80 GB E:\ kaie should be able to tell you if you can shrink that.

:Fallen's TODO:
 * Tell IT what a sane E:\ drive space would be for you (E:\ is where your builds/source should live -- current is 80GB, I suggest 20 or 30 GB, likely)
 * Setup ssh keys, and do initial known_hosts connections
 * Sanity check the expected binaries/scripts are all installed (or easily installable by :Fallen)
 * Touch base with Callek/IT if there is any followup work needed.
 * Verify that the VM can reach all systems/services you need (ensuring that network flows are in place)
 * Setup buildbot.tac in /builds/slave
   * If you need to modify this directory naming, see :Callek on IRC for what else needs to change [not much, just a hardcode in a startup script]

Notes [for kaie]:
 * This machine is set to timesync with microsofts ntp timeserver, you can change this at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters if desired.
 * mozilla-build is in D:\mozilla-build, does have buildbot (0.8.4-pre-moz2) installed/etc. 
 * Python 2.5 and 2.7 are available
 * MSVC2010 is installed in d:\vs2010
 * You have ssh available (as cltbld, and dumps you into a MSDOS shell, not a unix-like bash/sh shell)
   * pro-tip: launch |D:\mozilla-build\bin\bash.exe --login| to get that functionality, but a slower response-time from this ssh session.
 * You have VNC available as cltbld as well.
 * RDP is preferred for maintenance, login as Administrator

-- It is possible that I missed something, but I don't believe so, and this should meet all your needs, feel free to contact/touch base with me if you need assistance/help/whatever.

Comment 1

[Philipp Kewisch [:Fallen][📱📆]]

(In reply to Justin Wood (:Callek) from comment #0)
> :Fallen's TODO:
>  * Tell IT what a sane E:\ drive space would be for you (E:\ is where your
> builds/source should live -- current is 80GB, I suggest 20 or 30 GB, likely)
The old VM had 30 gb, which was more than enough. Lets stick with 30 gb, unless IT wants to save space and rather expand later on, in which case I'd go with 20gb.

>  * Setup ssh keys, and do initial known_hosts connections
My ssh key can be found at attachment 256817 [details], but I can set this up myself if I have RDP access.


>  * Touch base with Callek/IT if there is any followup work needed.
Thanks for the offer, will do.


Looking forward to getting this set up, windows builds have been out for a month due to the merge aurora will be affected too starting tomorrow.

Comment 2

[Adrian J Fernandez [:Aj]]

nss-vm-win32-2.community.scl3.mozilla.com is online.
If you need the name changed, please let me know.

:dustin will update when logins changed.

:kaie if you need E:\ reduced or need anything else changed, please let me know.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

That will need to be named cal-vm-win32-1 - sorry if I didn't make that clear in IRC.

Password is changed to the calbld password (though note that the username is not calbld - Administrator or cltbld)

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

I fixed the name in DNS.  Aj, can you fix it in vcenter and inventory?

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

I reset the autologin password, too.

Comment 6

[Adrian J Fernandez [:Aj]]

Name has been updated in both inventory and vcenter.

Comment 7

[Justin Wood (:Callek)]

Additional TODO for (if dustin didn't), setup hostname properly on windows here. (Less important since we don't use DHCP for IP address, but still very very useful)

Comment 8

[Philipp Kewisch [:Fallen][📱📆]]

It seems this machine can't reach calendar-master.mozillalabs.com as a buildslave. Do you need a new bug for this, or do you want to take care here?

Comment 9

[Justin Wood (:Callek)]

BTW, you will want to perform the following command, from a windows cmd shell as administrator (sorry that I missed it):

move d:\mozilla-build\vim\vim72\install.exe d:\mozilla-build\vim\vim72\vim-install.exe

Comment 10

[Philipp Kewisch [:Fallen][📱📆]]

(In reply to Justin Wood (:Callek) from comment #0)
> :Fallen's TODO:
>  * Tell IT what a sane E:\ drive space would be for you (E:\ is where your
> builds/source should live -- current is 80GB, I suggest 20 or 30 GB, likely)
Done

>  * Setup ssh keys, and do initial known_hosts connections
Done

>  * Sanity check the expected binaries/scripts are all installed (or easily
> installable by :Fallen)
Looks good

>  * Touch base with Callek/IT if there is any followup work needed.
Done

>  * Verify that the VM can reach all systems/services you need (ensuring that
> network flows are in place)
Network flows are in place, all thats missing is bug 764537, but that issue has been there before this machine.

>  * Setup buildbot.tac in /builds/slave
>    * If you need to modify this directory naming, see :Callek on IRC for
> what else needs to change [not much, just a hardcode in a startup script]
Done, directory naming is fine.

(In reply to Justin Wood (:Callek) from comment #9)
> BTW, you will want to perform the following command, from a windows cmd
> shell as administrator (sorry that I missed it):
> 
> move d:\mozilla-build\vim\vim72\install.exe
> d:\mozilla-build\vim\vim72\vim-install.exe
Done


Everything is running, thank you everyone for your support.