[2.5] Pod console_logging should be the default (and needs a doc fix)

[Mike Pontillo]

When we run into issues with MAAS and pods in a production environment, it's often difficult to determine what went wrong due to the lack of console logging.

In MAAS 2.5, we introduced the ability to update console_logging=True for a pod. But there are two problems with that:

 * It is not the default option. Therefore, anyone who has problems in the field will need to recompose any VMs after setting this option, which makes pod VMs difficult to support.

 * There is a mistake in the documentation; it states "console_log" instead of "console_logging" as the name of the parameter to use.

Assumming we fix the first problem (lack of console_logging being the default option), the documentation will need to be updated anyway to reflect the new default. So we should fix both of these issues at the same time.

See also -

Original bug:
https://bugs.launchpad.net/maas/+bug/1713556

Original fix:
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053

Examples of difficult-to-debug issues to to the lack of this option being the default:
https://bugs.launchpad.net/maas/+bug/1794114
https://bugs.launchpad.net/maas/+bug/1810972

[Blake Rouse (blake-rouse)]

I think the default should be defined in a global option and not something that is just always on. I agree with the reason for it to be on, and with CI systems the global option can be set so the information can be gathered.

[Mike Pontillo (mpontillo)]

I feel that a global option would add unnecessary complexity. The only reason you want console logging to be turned off is if you're a developer who wants to see the console in virt-manager or similar. As a developer, I don't particularly care whether my pod console logging is turned off via a global option or via a setting on the pod. Either way it's just one line in my script to set up MAAS.