Standing SRU for new MAAS releases.

[Andres Rodriguez]

Hi Martin,




On Tue, Aug 19, 2014 at 12:29 PM, Martin Pitt <martin.pitt at ubuntu.com>
wrote:

> Hello Andres,
>
> thanks for the updates. (Also, I was on holiday, sorry for late reply)
>
> Andres Rodriguez [2014-08-13 19:58 -0400]:
> > > >    testing.
> > > >    We will provide an upgrade path that "just works".
> > >
> > > Can you please expand that? I. e. how do you make sure that existing
> > > MAAS deployments that were done with earlier versions continue to work
> > > with proposed new versions? How much do protocol changes affect
> > > particular hardware, i. e. up to which degree can this be tested
> > > automatically with e. g. a bunch of commodity hardware or even QEMU,
> > > and which parts would need the actual supported set of hardware,
> > > things like ppc64el or ARM servers, or other hardware which is hard to
> > > get into a CI environment?
> > >
> >
> > We currently maintain backwards compatibility with all of the components,
> > so every upgrade will yield a working MAAS that continues to work as
> > expected. We currently do manual testing for upgrades, but we are in the
> > process of adding automated upgrade testing to our CI.
>
> How do you do the manual upgrade testing, and what's the rough
> structure of testing this automatically then? The "what" is quite
> clear now, I'm still interested in the "How" for regression-testing
> newer versions against existing deployments.
>

The manual upgrade testing is done as follows:

1. Install, configure MAAS
2. We register machines
3. Commission machines
4. Perform deployments

This allow us to test the current released version.

5. Upgrade
6. Perform deployments
7. Register machines
8. Perform deployments.

This allow us to test the new version, and check for any regressions.

In one of hour labs we have 100+ systems, and we test trunk version of MAAS:

1. Stop machine deployments.
2. Perform upgrade
3. Resume deployments
4. Register / Re-Commission some machines to check for regressions
5. Perform new deployments.

Automated Testing

The automated testing we are in the process of adding will allow us to do
two things:

1. Fresh install of trunk
2. Register hardware
3. Commission hardware

At this point, we are able to identify any regressions.

4. Perform deployments

At this point, we are also able to identify regressions.

What's currently being added to the CI:

1. Install released MAAS version.
2. Register hardware
3. Commission hardware
4. Deploy hardware.
5. Upgrade hardware

At this point we are able to identify regressions.

6. Perform deployments

At this point we will be able to identify regressions.

Thanks





>
> Thanks!
>
> Martin
>
> --
> Martin Pitt                        | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
>



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