Changing virt-type is unsupported, config-changed should block and advise via status

[Ryan Beisner]

Changing virt-type is unsupported, config-changed should block and advise via status.

Example:

nova-compute is deployed with virt-type=kvm.

User then sets virt-type to something different, such as lxd.

Juju get shows virt-type: lxd, but the charm has otherwise not reacted, and virt-type remains kvm (as it should).

Extended status should advise that the compute node type cannot be changed after deployment.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/409423

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/409423
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=ca8dcdeaa88818d9de5814c4953986f74fb035e8
Submitter: Jenkins
Branch: master

commit ca8dcdeaa88818d9de5814c4953986f74fb035e8
Author: Sandor Zeestraten <email address hidden>
Date: Sat Dec 10 08:51:18 2016 +0100

    Update config description for virt-type

    The charm allows changing of the virt-type configuration option after
    deployment, however this is not supported as noted in LP #1623679.

    This updates the description for virt-type to include a note that changing
    after deployment is not supported.

    Change-Id: I91f5e814e65f3cc622a1001adb9bf7850b74d6fd
    Related-Bug: #1623679
    Related-Bug: #1539489
    Related-Bug: #1626416