ExoGENI and OS Upgrade Plans - Documentation requirement

[lnevers@bbn.com]

The test case EG-ADM-7 checks for availability of ExoGENI rack documentation. This ticket captures the requirement to deliver a documented approach for ExoGENI components and OS upgrades.

At this time Administrative pages at ​https://wiki.exogeni.net/doku.php?id=private:start do not include any items relating to updating or upgrading any of the ExoGENI components or Operating Systems in use in the rack.

[lnevers@bbn.com]

A page is found which provides a diagram of the ​Software update process for the rack and states:

In general, because the rack software contains a lot of internal dependencies, the updates to elements of the rack need to be done in discussion with the ExoGENI team. 

I thought the ExoGENI team is responsible for upgrades? Should that be stated explicitly?

[lnevers@bbn.com]

Attaching full list of suggested "yum list all|egrep -i exogeni" from bbn-hn and bbn-w1.

[ibaldin@renci.org]

I have added the following sentence to the page

"Instructions for upgrades for specific software components will be made available to other rack operators at the time when those upgrades are deemed appropriate and necessary by the ExoGENI team."

This is as far as I'm willing to go with this ticket. As we have previously discussed on numerous occasions, there will never be a generic upgrade procedure due to the complexity of the software system.

[lnevers@bbn.com]

Sounds good, the set of updates to the ​Software Update process for the rack page does set exceptions for the rack operators.

Closing ticket and marking this item with "pass" state.