Standing SRU for new MAAS releases.

[Andres Rodriguez]

Hi Marc,

Sorry for a late reply, I missed your email.

It's still unclear to me how you are going to make sure a mi x of different
> major
> versions on controllers and nodes will be handled properly.
>
> How far back will you maintain backward and forward compatibility?


The MAAS API is fully backward and forward compatible. We have ensured that
all API calls have not changed with the new upstream changes. This ensures
that users of the MAAS API are not affected with the new features. We have
put this in practice on deployments that use the MAAS API.



How will you automate testing of all the different combinations of versions?

Are there any scenarios that will not be handled? For example, will there
> be any
> restrictions in mixing different versions where, for example, controllers
> need
> to be a higher version than the nodes, or that all controllers need to run
> the
> same version, etc?
>

MAAS deployments require the Region and Cluster controller to be the same
version. This is required for the communication between these components.
MAAS deployments by default include both the Region and the Cluster
controller in the same node.

This, however, does not affect nodes that have been deployed, given that we
maintain API compatibility. All of the nodes that MAAS manages, will
continue to work with newer MAAS versions without being affected. This
includes nodes that are in any state (Declared, Commissioning, Ready, and
Deployed).


>
> Marc.
>



-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
Systems Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/technical-board/attachments/20140925/c5c79119/attachment.html>