AutomatedInstallation
NOTE: Gobby lost the group changes during the transition. If you attended this sprint please try to add your contributions here
Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: [https://blueprints.edge.launchpad.net/ubuntu/+spec/automated-installation-improvements Automated Installation]
Launchpad Team: [https://launchpad.net/~ubuntu-community-enterprise-project Ubuntu Community Enterprise]
Packages affected: debian installer
Wiki Page (this page): https://wiki.ubuntu.com/AutomatedInstallation
Mailing List: http://lists.ubuntu.com/mailman/listinfo/ubuntu-automated-installation
Summary
It would be beneficial for the debian-installer to facilitate automated installations / cloning similar to what the RH anaconda installer does with anaconda.ks. Better documentation for preseed and automated installation will be needed.
Release Note
This would effect enterprise / LTS deployments in facilitating automated installation for large deployments. Everything from classroom deployments to larger infrastructure that needs to "clone" and auto-deploy new Ubuntu installations.
Rationale
There is very little focus on a number of LTS / Enterprise focused topics, whereas this is used quite a lot around the community.
Use Cases
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.
This need not be added or completed until the specification is nearing beta.
Outstanding Issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.