[07:04] <kjackal> Good morning Juju World!
[09:43] <Naz> Hi, I am not able to deploy a service to an LXD directly?
[09:45] <Naz> In facts:     juju deploy ./mediawiki --series xenial --to lxd,  the following log is:  machine-34: 12:39:41 WARNING juju.provisioner incomplete DNS config found, discovering host's DNS config machine-34: 12:40:13 WARNING juju.provisioner failed to start instance (Failed to change ownership of: /var/lib/lxd/containers/juju-8aa58b-34-lxd-0/rootfs), retrying in 10s (2 more attempts) machine-34: 12:40:24 WARNING juju.provisioner incomplete DN
[09:49] <Naz> # cd /var/lib/lxd/containers/juju-8aa58b-34 (NOT -LXD-0, NO SUCH FOLDER) root@HP:/var/lib/lxd/containers/juju-8aa58b-34# ls -l ----> drwxr-xr-x 22 231072 231072   22 May 18 15:43 rootfs
[09:50] <Naz> Owner and group are 231072
[09:51] <Naz> JUJU STATUS ==> 34/lxd/0 STATE=  down                     INST ID pending         Series xenial
[10:04] <Naz> I want to deploy to LXD as I don't want to spin off more than 4 machine, I have 12 services currently. So, for example 3 LXD per machine to have the 12 over 4 machines
[10:06] <bloodearnest> hello folks. I just notices the 'Notes' column on juju status. How does one add notes?
[10:09] <bloodearnest> are they annotations? Or can I set them from the charm?
[10:38] <Naz> I see this is already reported as bug at : https://bugs.launchpad.net/juju/+bug/1614329
[10:38] <mup> Bug #1614329: Cannot deploy charm to new lxd container on machine: permissions error <lxd> <juju:Triaged> <https://launchpad.net/bugs/1614329>
[10:39] <Naz> WOW :)
[10:39] <Naz> at the same second, we posted this, My friend MUP :)
[12:36] <lazyPower> Naz: :) thats fun, but mup is a bot and just expands bug ids
[12:37] <lazyPower> bloodearnest: i dont think theres a way to set them from within a charm. I could be incorrect, but to my knowledge we dont have any support for that. you can set status messages via status_set() in the charmhelpers.core.hookenv package.
[12:39] <Naz> @LazyPower :) Really Interesting, I thought he is human :) How could he ties it to the bug? I used Google :)
[12:39] <lazyPower> Naz: you had a launchpad link with a launchpad id :) mup knows launchpad very intimately
[12:39] <bloodearnest> lazyPower, sure, we do that, and application_version_set(), but the Notes thing was new to me
[12:40] <lazyPower> bloodearnest: if we're missing a route to set data, lmk and i'll see about getting something pushed at charmhelpers
[12:42] <Naz> Ok, so, he just echo-ed the contents of the bug id that I pushed. Nice job anyway ...
[12:51] <Naz> @LazyPower, Anastasia (anastasia-macmood) wrote on 2017-02-17: 	#3  Removing 2.1 milestone as we will not be addressing this issue in 2.1. Changed in juju: milestone: 	2.1-rc2 → none . DOES THIS mean that it is postponed till 2.2?
[12:52] <lazyPower> Naz: that seems to be the case, possibly later depending on the roadmap. they will re-target the bug at which release should receive the fix.
[12:54] <Naz> Ok, Thanks for the clarification, In fact, Cheryl Jennings (cherylj) wrote on 2016-04-20: 	#1  There is an explicit check to determine whether or not a machine can host containers. When a machine agent starts up, it checks to see if the machine is running in a container, and if it is, that machine cannot host containers.
[13:59] <vlad_> Hey everyone I'm back for more questions. I've got a yaml bundle of my openstack config that I want to use. However, when I try to deploy the yaml config it errors out complaining about lxd containers that don't exist. Is there an easy way for me to add the creation of these containers to my config? (I started out by exporting this from a bundle in the gui)
[13:59] <admcleod> vlad_: can you pastebin your bundle?
[14:06] <vlad_> admcleod: I don't know for sure if I can due to it being for work. However, it's just a configured version of the openstack-base bundle. I.e. I've added IP information and some other secrets (via the UI), and then exported it for easier iterating and development. Does that help?
[14:15] <vlad_> Also if pastebin is necessary I can try to take time to remove sensitive information.
[14:17] <admcleod> vlad_: well, at the veyr least, it would be useful just to see the block where it tries to deploy one of these lxd containers its complaining about, and the specific error message
[14:26] <vlad_> admcleod: Yes I definitely think that makes sense. I actually just figured it out. I had to modify the bundle slightly, and that modification didn't make it into the export though other stuff did. Essentially it was referencing the creation of an lxd container on a machine that wasn't defined
[14:26] <vlad_> admcleod: Thanks for your time!
[14:27] <admcleod> vlad_: no worries, glad you got it working :)
[22:51] <Budgie^Smore> o/ juju world