[2.4, 2.5, enhacement] MAAS deployed Pods can be released

MAAS doesn’t know a pod was deployed, since this is manually sending user
data. That said, we will cover this if we get to “make this MAAS mode a pod”

On Tue, Jul 17, 2018 at 12:05 AM Lee Trager <email address hidden>
wrote:

> Public bug reported:
>
> The performance CI deploys Ubuntu to all physical machines and then
> creates a number of Pods on each machine. I accidentally released all
> machines during testing. MAAS did not warn me I was releasing a machine
> which drove Pods. When I tried to deploy to those Pods all MAAS gave me
> was a power error.
>
> MAAS should not allow machines which drove Pods to be released. The user
> should be forced to delete the Pod first.
>
> ** Affects: maas
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1782060
>
> Title:
> MAAS deployed Pods can be released
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1782060/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; status=New; importance=Undecided;
> assignee=None;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: ltrager
> Launchpad-Bug-Reporter: Lee Trager (ltrager)
> Launchpad-Bug-Modifier: Lee Trager (ltrager)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Before releasing a machine MAAS could check if any IP address or the hostname of the machine being released is set as the BMC address for any other machine. If so MAAS can raise an error that the machine being released is currently configured as a BMC for another machine.

1. On 'deploy' the machine should be automatically logged.
2. On 'release' (after being unlocked) the machine should be asked to confirm whether you want to continue because this machines is a KVM pod.
3. After 2, the machine should cascade and delete the pod (which would delete the vm's).

s/logged/locked