I have two machines in my MAAS environment
- First one is Juju bootstrap machine, while second one is normal node.
- Both of them are in running state.
- I deployed mysql with "juju deploy mysql" and issue "juju status" command to find that a new machine had been added with instance-id=pending and series=trusty.
- After few moments, that machine went into error state. Following is the output of my juju status command
machines: "0": agent-state: started agent-version: 1.20.11 dns-name: juju.maas instance-id: /MAAS/api/1.0/nodes/node-84c0dada-6aa0-11e4-8b62-52540059ce08/ series: trusty hardware: arch=amd64 cpu-cores=1 mem=1024M tags=virtual state-server-member-status: has-vote "3": agent-state: started agent-version: 1.20.11 dns-name: node0.maas instance-id: /MAAS/api/1.0/nodes/node-796b82da-6aea-11e4-860c-52540059ce08/ series: trusty hardware: arch=amd64 cpu-cores=2 mem=2048M tags=virtual "4": agent-state-info: 'cannot run instances: gomaasapi: got error back from server: 409 CONFLICT (No matching node is available.)' instance-id: pending series: trusty services: mysql: charm: cs:trusty/mysql-11 exposed: false relations: cluster: - mysql units: mysql/0: agent-state: pending machine: "4"
My question: Why Juju creates new "machine"? What is the defination of "machine" here? Is it an LXC container?
NOTE: I setup my MAAS with VMs.