Hi VM, The 409 CONFLICT error is the right error, and the error that MAAS provides through the API when no machines matching the criteria supplied are available. Juju doesn't directly query MAAS for how many machines are available it simply takes the criteria you supplied (or the default constraints) and requests MAAS provision a machine which has at least these characteristics. MAAS will either do so or report back an error, in this case the 409, since no machines are available that match that criteria (let alone there not being any machines available).
Since you're using MAAS with a low number of available machines, you may instead want to try deploying to containers on the single node you have available. By default juju will provision one machine per unit of service in it's topology, but you can help guide where Juju should place machines if that pattern doesn't suite your needs. There are two ways to achieve this. The first is using the `--to` flag, as you've alluded to, though this is seldom recommended as you run the risk of charms conflicting with each other over resources on a system. A better solution would be to use containers on these machines, for instance `juju deploy --to lxc:1` which would deploy that service to an LXC container on machine 1. You can find the machine numbers from the output of `juju status` in the machine section of the YAML output. https://jujucharms.com/docs/charms-deploying#deploying-to-specific-machines-and-containers For what it's worth, the MAAS experience is improved when you have more machines available in your pool. Thanks, Marco On Mon Dec 22 2014 at 5:54:41 PM Vahric Muhtaryan <vah...@doruk.net.tr> wrote: > Hello All , > > Im testing juju with MAAS and looks like somehow juju or MAAS do not > recognise that machine pool is over. > For example if I have just only one machine available for reservation and > install the mysql or wordpress > Juju get one machine from MAAS and install related software packages. > > Problem is when I would like to install second thing , in my example is > database, its try to catch one more machine but problem is there is no > available server , but its catching but because of serve is not available, > its mark it 409 CONFLICT no matching node is available . > > My idea is before provision something MAAS can check and confirm the > environment. > > My question is juju or MAAS somehow need to know servers are really > available or not ? If not can ask to admin for continue or not or try to > advise share or install on same machine which already other service is > runnung (like deploy —to 1 mysql) > > Regards > VM > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju