Code review comment for lp:~jtv/maas/bug-1373103
Revision history for this message
| Scott Moser (smoser) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I'd not bother carrying the hack much further than we have it already.
the goal is for maas to declarel networking information to the installer (curtin), and that to handle figuring out what to do with that network information.
i wouldn't bother wan an "OS registry" and scripts. we want maas to be stupid and images it installs to be smart. The image it installs provides a /opt/curtin/hook that has access to the network config that maas provided, and has to render that to in-operating system networking.
that way, maas is stupid, and the information about the OS is in the OS.
the change you have here is fine, but to me it seems like the wrong direction to "integrate with the OS registry", whatever that means.