bin/doozer_init talks about "my_cal" (based on two digits at end of hostname) but /ctl/cal seems to be first come first serve

[tv42]

I don't see anything that would make it reliably "my" cal.

doozer_init happily deletes the cal entry, thus making whatever node had that CAL entry hang (it doesn't even realize it got kicked out; other nodes remove it from /ctl/node).

Even if this was enough to kick "others" out from using "my_cal" (which isn't, there's a huge risk of more and more nodes hanging), nothing guarantees the new doozerd started by doozer_init gets "my_cal". It's racy.

[mreiferson]

yea, the script relies on the sequential nature of how we deployed things at bitly, see #46 for some updates that I haven't finished (the script currently in master was prematurely merged)