Community

Suppose I have a Nimbula system up and running, and then an update to the software is released. What will be the procedure to update all the servers?

Will it be automatic, or a matter of downloading the update, selecting the servers, and then clicking "Go!"?

(And thanks for offering a free version for small operations!)

--Matt B.

HI Matthe

Nimbula Director upgrades will be available as ISO's which should be run as seed VMs within the cluster. Newer seed ISOs can be can be used to upgrade an existing site. The upgrade utility should be launched from within this seed VM. When run, it will provide a Debian repository over HTTP and communicate with the site API endpoint to add this new repository as an available update location. Nodes will then retrieve the new packages and upgrade to these packages. Once this process has completed on all nodes, the site will issue a 'restart' command and will be temporarily inaccessible while the services restart.

Jacqui

Edited jacqui (March 11, 2011 11:44:33)

jacqui
HI Matthe

Once this process has completed on all nodes, the site will issue a 'restart' command and will be temporarily inaccessible while the services restart.

Jacqui

Does this mean that the VMs running on these nodes will be inaccessible or that the API itself won't be available until restart is complete?

aaron_dodd
[quote=jacqui]HI Matthe

Once this process has completed on all nodes, the site will issue a 'restart' command and will be temporarily inaccessible while the services restart.

Jacqui

Does this mean that the VMs running on these nodes will be inaccessible or that the API itself won't be available until restart is complete?[/quote]


The instances will continue to be accessible. It's only the ability to connect to the API that will be out for a short period.