• You'd reassign the disks the following way:
• (6080 node 2 still running in takeover mode)
• switch on new node1 (connected to disks already)
• environment variables will have to be set for the 'old' node2 to be recognized as partner!
  
• will be stuck on boot, since it doesn't find disks it owns. will tell you the new SYSID, though
• if in a reboot-loop (instead of waiting for keypress), shut it down again
  
• On node2 do
• 'partner' to switch to virtual partner
• 'disk reassign -d <new SYSID of new node1>
• 'partner' to switch back again
• Shut down Node2 cleanly
  
• Now new node1 will be able to boot successfully and since (by now) old node2 should have released he disks, not be 'waiting for giveback'...
• But how are you planning to take over the downed node2?
• In your case I could imagine 'cf forcetakeover -d'...  
  (That's where you need the partner-ID environment vars for...)
  
• ==> this is where I'm not sure if it works...
  
• Then the dry-run on new node2 to find the new SYSID and set the partner ID (on node2)
• Then the partner/disk reassign.../partner (on node1)
  
• I'm pretty sure a 'cf giveback' probably doesn't work yet... But maybe
  
• 'cf forcegiveback' on node1 to shut down virtual node2
• boot new node2, it should now recognize the disks...

Main thing is to get through this without a panic...   :-P

Sebastian

On 2013-4-15 16:39 , tmac wrote:

I completely understand. It is *not* a supported operation.

There are *still* NVRAM handshakes that happen and by changing the head you *WILL*
have major problems.

The NVRAM of the old and new systems would never be connected... but apparently I don't understand enough about this functionality, so I'll just study the upgrade guide.

Think about it, your downtime will be minimal. You are only taking down one head at a time.

Err, not really. If any service is unavailable, then our platform is down. Downtime would start when the first head goes down, and end when the last head goes up again. The nature of our system doesn't allow for a partial unavailability. In practice, that means a downtime of hours instead of minutes. If we cannot use takeover, we might as well replace both heads at the same time.

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters