ejat | hi .. how could i juju deploy application into new lxd in specific machine ? | 03:19 |
---|---|---|
zeestrat | ejat: juju deploy <application> --to lxd:<machine-number>, so for example juju deploy keystone --to lxd:1. See also https://jujucharms.com/docs/stable/charms-deploying#deploying-to-specific-machines-and-containers | 08:38 |
ejat | zeestrat: thanks .... if i want to deploy into new lxd? | 09:53 |
ejat | i can do it using juju gui but doesn't know specific cli cmd | 09:54 |
ejat | manual placement in juju gui | 09:54 |
zeestrat | ejat: I'm not sure if I understand. The command I listed above is for deploying to a new lxd container on a specific machine. | 09:56 |
ejat | but need to define the machine number too right ? | 09:59 |
ejat | or no need ? | 10:00 |
ejat | btw, how to check the neutron-gateway error : Status: error - hook failed: "config-changed" | 10:01 |
ejat | deployed with maas | 10:01 |
ejat | and this bugs | 10:02 |
ejat | https://bugs.launchpad.net/mongodb-charm/+bug/1676730 | 10:02 |
mup | Bug #1676730: mongodb charm status unknown (needs application workload status and version) <sts> <uosci> <MongoDB Charm:In Progress by mariosplivalo> <https://launchpad.net/bugs/1676730> | 10:02 |
zeestrat | ejat: yes, you'll need the specific machine number. Don't know about the other bug. | 10:06 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!