[10:37] <Zic> hi here, all my kubernetes-worker are showed as "failed" in juju status since this morning, but everything is fine in practice... I ran a "juju debug-log" and saw a lot of "too many open files" of this kind : http://paste.ubuntu.com/25324995/
[10:37] <Zic> so I tried to modify the file.fs-max sysctl value & limits.conf, but nothing change
[10:37] <Zic> do you have clues ? :(
[11:32] <Ting_> hi there, I am deploying a application (postgresql in this case) on maas, it gets stuck at waiting for machine. Tried with print out log with "juju debug-log", but got no respond from that, anyone have idea about why juju debug-log doesn't work? How could this be fixed?
[11:42] <rick_h> Ting_: hmm, try the deploy with --debug in the command "juju deploy postgresql --debug" and see if that has some info
[11:44] <Ting_> yes, i deployed it with --debug, it showed some info and said command finished at the end.
[11:46] <rick_h> Ting_: ok, is there a machine in juju status with a number?
[11:46] <rick_h> Ting_: if so, try to do "juju show machine X" and see if there's any output about why it couldn't get the machine
[11:47] <Ting_> ok, i'll try it
[11:49] <Ting_> it shows some infor like juju-status: pending, machine-status:allocating
[11:54] <Ting_> rick_h: from maas gui, i can see the machine is deploying which takes very long time than expected.
[11:56] <rick_h> Ting_: ah ok. Assumed there was an error. Go Maas go!
[12:13] <Ting_> rick_h: sure, thanks!
[17:08] <stormmore> o/ juju world
[17:32] <rick_h> reminder juju show in 30 woot woot
[17:32] <rick_h> awesome 2.3 early feature demo coming
[17:33] <rick_h> well, future feature (probably not 2.3)
[17:53] <rick_h> Juju Show linkages: https://hangouts.google.com/hangouts/_/n4gmxnhlgrhkpibqzdn3gf7c2qe for joining in the conversation (tvansteenburgh, hml, kwmonroe, arosales, bdx, and anyone else)
[17:53] <rick_h> and for watching check out https://www.youtube.com/watch?v=NUx6kYE60Mc
[18:05] <arosales> rick_h: thanks, I'll be in read only mode today
[18:05] <tvansteenburgh> i'm on TV!
[18:05] <tvansteenburgh> i'm famous!
[18:06] <tvansteenburgh> https://lists.ubuntu.com/archives/juju/2017-August/009294.html
[19:41] <sfeole> i'm putting together some updates to a charm I use.  I'm curious , I have a function that I only want to run once, however I need it to wait until a specific condition is met. so can I stack 2 decorators like this: @when('condition_met') \n @only_once  \n def do_this_action()
[20:04] <blizzow1> So I have 3 decent servers that I used maas to wipe and put a default installation of ubuntu on them. I'd like to test openstack or kubernetes using these three servers and was contemplating using juju to do it. I keep running into issues with conjure-up. All the pages I see about deploying openstack or kubernetes suggest starting with maas+conjure-up+juju to get things up and running. Do I need conjure-up?
[20:09] <stokachu> Depends, is the problem conjure-up or your maas setup
[20:15] <blizzow1> stokachu: I don't think my maas is busted? but who knows.
[20:15] <blizzow1> wtf, why do I need lxd and zfsutils to run juju?
[20:16] <blizzow1> Why in the hell do I use snap? What happened to using apt??
[20:17] <stokachu> Well that's where most applications are heading coming from us
[20:17] <blizzow1> argh. yet another f'ing packaging/installation system.
[20:18] <blizzow1> what was the matter with apt? who knoooows?
[20:18] <stokachu> And I don't know what problems you are having as you haven't provided any additional information
[20:19] <stokachu> There is also a #maas channel
[20:20] <blizzow1> well, I'm over using conjure-up+snap to do stuff because it's always failing. So I'm trying to install juju on it's own VM and add the maas cloud. Then I'll get started on testing whatever I want...I see this page which seems to be how to install juju... https://jujucharms.com/docs/2.2/reference-install.  Where do I go from that page?
[20:21] <stokachu> Fair enough
[20:24] <stokachu> if you get bored and actually want to debug your maas+conjure-up then let me know
[20:28] <blizzow1> I guess my question was whether or not I even need to use conjure-up got get juju running? I'd prefer not to use lxd containers in a VM to provision bare metal that can provision more VMs. can I run a juju controller without LXD and adding some bridging to a VM that's already bridging?
[20:29] <stokachu> you dont need conjure-up to get juju running
[20:29] <stokachu> if you have maas you can just use this https://jujucharms.com/docs/stable/clouds-maas
[20:29] <stokachu> and juju deploy canonical-kubernetes
[20:30] <blizzow1> stokachu: thanks.
[20:35] <stokachu> blizzow1: you just want to make sure that maas is able to auto power on/off your nodes
[20:35] <stokachu> without you having to do anything
[20:36] <stokachu> blizzow1: also i usually create a VM on the maas server and register that as a node
[20:36] <stokachu> and do juju bootstrap --to vmhost.maas
[20:36] <stokachu> so you aren't using a whole machine for the bootstrap node
[20:39] <blizzow1> stokachu: maas is able to power up and power off these servers at will. I'm trying not to use a whole server to run maas or juju. I'm trying to use these servers to run openstack or kubernetes as a proof of concept, so my maas and juju servers are VMs on separate hypervisors.
[20:41] <blizzow1> So from my juju VM. I did an add-credential maas-cloud.  Then when I try an do a bootstrap, I get an error about failing because of constraints.
[20:42] <blizzow1> ERROR failed to bootstrap model: cannot start bootstrap instance: cannot run instances: cannot run instance: No available machine matches constraints: [('agent_name', ['cf1fbc63-9ad1-4556-8159-43a2f4f7aa32']), ('mem', ['3584']), ('name', ['maas01.mydomain.com'])] (resolved to "mem=3584.0 name=maas01.mydomain.com")
[22:34] <blizzow1> So if I already have a maas server running, how do I register that instead of bootstrapping another with juju?
[23:08] <thumper> blizzow1: so using maas with juju?
[23:08] <thumper> https://jujucharms.com/docs/2.2/clouds-maas