Merge lp:~jtv/maas/cap-ipv6-deployment-ubuntu into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3004 |
Proposed branch: | lp:~jtv/maas/cap-ipv6-deployment-ubuntu |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
60 lines (+12/-2) 4 files modified
docs/capabilities.rst (+6/-0) docs/index.rst (+1/-1) docs/ipv6.rst (+3/-1) src/maasserver/api/version.py (+2/-0) |
To merge this branch: | bzr merge lp:~jtv/maas/cap-ipv6-deployment-ubuntu |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Newell Jensen (community) | Approve | ||
Review via email: mp+234904@code.launchpad.net |
Commit message
Define and document a new capability: ipv6-deployment
Also, move the link to the IPv6 documentation to a more appropriate place in the documentation index. Right below ‘networks’ is wrong because that document is about networks for placement-
Description of the change
It's tempting to call the capability just “ipv6,” but I think a capability of that name would make more sense for the point where the whole basic feature works. Instead I went with something more specific for what is now possible: deploy Ubuntu nodes with IPv6 enabled.
We may at some point support deploying over IPv6, which might create confusion with deployment of IPv6-capable nodes. A capability for exclusively IPv6-based deployment might be called something like pure-ipv6-
Jeroen
Looks good to me. Not sure if this is going to create more work for you or someone else later when the "whole basic feature works" if it would need to be changed to not be as specific as what you have here.