I like Gavin's solution of reconciling Cobbler and MAAS view using the Provisioning API. Turning this into a specific command that is run as part of vdenv is probably the direction to take. I say specific because I don't think we want to support general reconciliation where people starts adding stuff to Cobbler and expects to be able to sync MAAS with it. But as part of the vdenv setup, that should be fine.
Looking at both Gavin's diff and yours, I have big concerns about the status change. This seems to implied that there is currently no way for nodes to go from DECLARED to READY. How is that supposed to work in the normal case? Maybe that points to the fact that were aren't doing any commissioning yet? -- https://code.launchpad.net/~julian-edwards/maas/vdenv-enlistment/+merge/98393 Your team Launchpad code reviewers is requested to review the proposed merge of lp:~julian-edwards/maas/vdenv-enlistment into lp:maas. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
