MAAS Next Steps

Registered by Andres Rodriguez on 2013-05-15

[RATIONALE]

MAAS will continue to evolve and continue to provide new features that will improve its capability and usability in hybrid environments.

[GOAL]

Provide the latests MAAS features in Saucy.

Blueprint information

Status:
Not started
Approver:
Dave Walker
Priority:
Undefined
Drafter:
Ubuntu Server Team
Direction:
Approved
Assignee:
Andres Rodriguez
Definition:
Approved
Series goal:
Proposed for saucy
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

[USER STORIES]
Ramon likes MAAS, however he wants to be able to obtain the latest MAAS with the new features. He also wants to make sure that the new release wont overwrite his changes in the PXE templates. This is why he needs newer MAAS.

[ASSUMPTIONS]
MariaDB/Percona will be packaged for Saucy

[RISKS]
MAAS features don't hit trunk before Feature Freeze, which would case a delay in releasing them or not releasing them at all.

[IN SCOPE]
PXE
Deployment

[OUT OF SCOPE]

[USER ACCEPTANCE]

[RELEASE NOTE/BLOG]

[SESSION NOTES]

(?)

Work Items

Work items for ubuntu-13.09:
[smoser] file FFE for things above. bug 1218526: DONE
[andreserl] Install templates in /etc/maas: DONE
[andreserl] maas-ipmi-autodetect should be shipped with MAAS: DONE
[tycho-s] Use simple streams to download the cloud images (5): INPROGRESS
[maas-maintainers] use curtin from inside maas (3): TODO
[maas-maintainers] add 'user-install-data' input to acquire/start call (2): TODO
expose FastPath installer {pre,post}_install scripts (2): TODO
[tycho-s] clean up obsolete ephemeral and fpi images (2): TODO
[andreserl] Allow installation of different kernel versions: BLOCKED
[maas-maintainers] define supported release combination matrix: TODO

Work items for ubuntu-13.10:
[smoser] raise installer-data up with juju-team: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.