Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 77 Next »

This is the set of steps we will use to migrate to the new subnet at Carinet, the shared firewall with new IP addresses.

0%

Task List

  1. handler

    Carinet will provision the new IPs on the new sub-net

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  2. handler

    Obtain, confirm local DB backup

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  3. handler

    stop DB replication to SD PROD DB

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  4. handler

    halt all SD servers (in order web, geo, db)

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  5. handler

    stop web service on web server

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  6. handler

    sbin/shutdown -h now on web server

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  7. handler

    sudo dtomcat5 stop -force on geo

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  8. handler

    sbin/shutdown -h now on geo server

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  9. handler

    /usr/pgsql-9.0/bin/pg_ctl -D /data/9.0/data -m stop on db server

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  10. handler

    sbin/shutdown -h now on db server

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  11. handler

    SF will give the go-ahead to Carinet to proceed

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  12. handler

    CARI.net will ensure STD-ESXI/E3_1230-04-QCE server is shutdown and will transport hardware to proper chassis in order to fit the rack in C2 datacenter.

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  13. handler

    Once in C2 datacenter, CARI.net will re-ip server from 209.126.178.66 to NAT 10.224.211.12/66.240.211.12

    Priority MEDIUM
    jjohnson
    Mar 21, 2012
  14. handler

    Using the new IP, SF will connect to the STD-ESXI/E3_1230-04-QCE server as the ESXI host via the VSphere Client

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  15. handler

    Once connected, SF will power on the VMs in sequence: VCenter VM VCenter17870, Prod-DB, Prod-Geo, and Prod-Web

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  16. handler

    SF will then assign the new assigned IPs on the 10.224.211.x subnet to each of the 4 VMs, and make additional necessary configuration changes within the the VMs.

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  17. handler

    SF will then test VPN connectivity to the VMs using SSH Putty sessions.

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  18. handler

    confirm services db, geo, web

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  19. handler

    test SD application (read only)

    Priority MEDIUM
    jjohnson
    Feb 25, 2012
  20. handler

    resynch db replication

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  21. handler

    test SF application (confirm replication)

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  22. handler

    SD PROD WEB into standby

    Priority MEDIUM
    jjohnson
    Mar 22, 2012
  23. handler

    If connectivity is successful, then we are done; if not, then SF and Carinet will work together to ensure the VPN tunnel is working correctly on the new shared firewall.

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  24. handler

    decommission existing carinet firewall (carinet)

    Priority MEDIUM
    pmccullough
    Feb 25, 2012
  25. handler

    decommission additional storage server STD-CUSTOM/NEHALEM_EN_3440-04-QCE (sfgovstor01.aspadmin.net-209.126.178.126)

    Priority MEDIUM
    jjohnson
    Mar 28, 2012
  26. handler

    Decommission Private V-LAN

    Priority MEDIUM
    jjohnson
    Apr 11, 2012
  27. handler

    notify DBI "replication down"

    Priority MEDIUM
    pmccullough
    Apr 11, 2012
  • No labels