decide whether the exogeni rack management switch should have a public IP, and implement accordingly

[chaos@bbn.com]

Each ExoGENI rack's management switch (the 8052) needs a temporary public IP when the rack is initially installed. At the moment, there are no specific provisions for removing that public IP, and e.g. at BBN, it is still in place.

Decide whether ExoGENI prefers to keep that public IP in place long-term and secure the switch appropriately for a publically-accessible device, or to remove the public IP from the configuration once the rack is installed. If the former, do some testing. If the latter, test removing the IP at BBN, and add it to the rack install process.

[ckh@renci.org]

The public IP address has been removed from the BBN 8052. It's not necessary to include it in future configurations within ExoGENI.

[jbs@bbn.com]

Has it been removed from the switch on the RENCI, UH, and FIU racks too?

[ckh@renci.org]

RENCI's 8052 hasn't had a public IP for a while now. There's no plan to assign one to UH and FIU.

[chaos@bbn.com]

Just to put it on this ticket for clarity: i had previously assumed that if we removed the public IP from bbn-8052, we would also remove the cable between bbn-8052 and our lab equipment. Chris mentioned that this isn't the case --- the cable (and the VLAN which is shared with the campus network) will remain to provide an alternate L2 path, and this is just a question of whether there's a public IP associated with that VLAN.

[chaos@bbn.com]

Another question: will the IP address 192.1.242.4 be reused for anything else (e.g. will it get prepended to the VM range or anything?), or will it be unused now?

[chaos@bbn.com]

Regardless, there's one last action item on this, which is to remove bbn-8052.exogeni.net from DNS. (I'm removing bbn-8052.exogeni.gpolab.bbn.com from our DNS, but y'all control the CNAMEs at exogeni.net.)

[ibaldin@renci.org]

bbn-8052.exogeni.net has been removed

[chaos@bbn.com]

Verified, closing.