Comment 14 for bug 1109283

Hi Scott,

We are in the process of drafting the upgrade instructions, and we will communicate them through normal means, ML's, blog posts, etc, unless you believe a debconf message should also be showed.

I, however, feel the need to clarify this, since I fail to see how the MAAS SRU is causing a regression in MAAS in precise.

The reason why I fail to see a regression is that MAAS in precise does *not* really provide support for DNS/DHCP configuration. The MAAS SRU *does*. In Precise, MAAS uses a code copy of cobbler that generates a file to provide DNS/DHCP. However, this file is not configured by MAAS, nor generated by MAAS. The configuration requires manual intervention in order for it to work properly, which we believe is part of it being a broken implementation of cobbler. Since we rely on cobbler, MAAS in precise makes use of a dependency that can make an *attempt* to configure DNS/DHCP, which is in fact, not recommended by us. Most people will have manually configured DHCP/DHCP as an external service from MAAS, which is the implementation that we recommended from the beginning for Precise.

This is what the SRU *fixes* rather than *regresses*. This, however, requires proper configuration in the MAAS side after upgrade.

Now, as far as Quantal, it does not have this issue because MAAS in Quantal already has support for DNS/DHCP management and we no longer use the cobbler code copy.

Thank you for your input. Hope this information helps.