welcome: please sign in

Diff for "Migration2009/Peer1"

Differences between revisions 2 and 3
Revision 2 as of 2009-09-26 06:40:37
Size: 1468
Editor: ClintonEbadi
Comment:
Revision 3 as of 2009-09-26 06:54:44
Size: 2387
Editor: ClintonEbadi
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
     * Deleuze has a BMC with IPMI 1.5 support
     * Can serve as a frontend to the IBM RSA2 and Mire's SP allowing us to take them off of the public Internet (lowering the chances of a breakin)
Line 36: Line 38:
== Space Change ==

 * Net 0U change
 * Free up 2 ports on the switch
   * Remove krunk
   * Remove ipkvm
   * Remove mire SP (attach to console server)
   * Remove hopper RSA (attach to console server)
   * Add new machine
   * Add console server
 * Console server would have no free switch ports (deleuze, hopper-sp, mire-sp, new machine)
 
Line 51: Line 65:
Net space savings of 0U (since the switch takes up space that could not be used for a server unless it were half depth) == Space Change ==

 * 0U
 * Free up 1 port on the switch
   * Remove mire
   * Remove hopper
   * Add new machine
 * Free up 1 port on the management console
   * Add new machine
   * Remove mire SP
   * Remove hopper RSA

We might want to keep the netgear switch to slave to the console server. A managed switch, however, would also offer vlan support and it looks like a port based management vlan could be used (as long as the vlan ID on the console and switch agreed).

If we were to remain at Peer1 we would still need new hardware. We could instead purchase a single machine and improve services in place.

1. Initial

1.1. New Hardware

  • 2U Server
    • PowerEdge 2970

    • OpenAFS file server, master KDC, databases initially
  • 1U Management console
    • IM4004-5
    • Smaller than the kvm (2U) and ipkvm (not racked, but using shared 1U with switch)
    • Full remote reboot and serial console on all machines

      • Deleuze has a BMC with IPMI 1.5 support
      • Can serve as a frontend to the IBM RSA2 and Mire's SP allowing us to take them off of the public Internet (lowering the chances of a breakin)
    • Net cost of $150 with only one server, -$150 with two
      • DRAC cards giving us remote reboot and a few other not so useful features cost $350

'Cost': ~$2700

1.2. Removed Harwdware

  • 1U Krunk
  • 2U Belkin KVM
  • 0U Startech IPKVM

Scrap krunk (does it have Ultra320 SCSI drives that could be reused in hopper?), and craigslist/ebay KVM and IPKVM.

1.3. Reassigned Hardware

  • Deleuze
    • Option One
      • Secondary KDC and AFS server
      • Maybe store mail volumes on Deleuze and user volumes on new machine
    • Option two
      • Database server (fast disks and decently fast cpus make it ideal for this)

1.4. Space Change

  • Net 0U change
  • Free up 2 ports on the switch
    • Remove krunk
    • Remove ipkvm
    • Remove mire SP (attach to console server)
    • Remove hopper RSA (attach to console server)
    • Add new machine
    • Add console server
  • Console server would have no free switch ports (deleuze, hopper-sp, mire-sp, new machine)

2. Six Months Later

2.1. New Hardware

  • 2U Server
    • PowerEdge 2970 or similar class machine

    • User accessible services
  • 1U managed switch

2.2. Removed Hardware

  • Mire
  • Hopper
  • Netgear switch

2.3. Space Change

  • 0U
  • Free up 1 port on the switch
    • Remove mire
    • Remove hopper
    • Add new machine
  • Free up 1 port on the management console
    • Add new machine
    • Remove mire SP
    • Remove hopper RSA

We might want to keep the netgear switch to slave to the console server. A managed switch, however, would also offer vlan support and it looks like a port based management vlan could be used (as long as the vlan ID on the console and switch agreed).

Migration2009/Peer1 (last edited 2011-04-22 22:58:15 by ClintonEbadi)