[01:34] <vmorris> is there something in particular that i need to do to pass http proxy settings into LXD containers?
[07:31] <junaidali> hey guys, can a peer relation only share private-address?
[07:32] <junaidali> I'm trying to share some data across peers, but the relation data that i get is always the private address
[07:33] <kjackal> Good morning Juju world!
[07:34] <kjackal> junaidali: yes peer relations are just like the rest of the relations, you can share any kind of data
[07:34] <kjackal> junaidali: You need to create an interface for that, let me find an example
[07:35] <kjackal> junaidali: https://github.com/juju-solutions/interface-spark-quorum
[07:35] <junaidali> Good morning kjackal, thanks.
[09:17] <vibol> Hello
[09:19] <vibol> when we run juju enable-ha --n 3 we will be avaible to run juju command on the second and third node like the first controller ?
[09:19] <vibol> i mean we will be able to run juju status on the 3 state server in ha mode ?
[10:48] <SimonKLB> how do you run the same charm with different configurations since units have the same?
[10:49] <SimonKLB> for example two mysql databases with different ports?
[10:53] <mgz> you name the services/applications differently
[10:54] <mgz> `juju deploy cs:mysql dba && juju deploy cs:mysql dbb`
[10:55] <SimonKLB> mgz: thanks
[10:56] <SimonKLB> mgz: can you get some kind of unique id from an application?
[10:57] <mgz> the service name is unique
[10:57] <SimonKLB> mgz: not if you remove it and then start a new one with the same name right?
[10:59] <mgz> well, how is that distunguishable from a newly deployed service? config isn't kept if you destroy a service
[11:00] <SimonKLB> mgz: right, ill create the id myself, probably best not to rely on something the user can specify if you want to ensure uniqueness anyway :)
[11:01] <vibol> in juju 2.0 do we need to bootstrap at lease 3 machine to enable ha with juju enable-ha -n 3 ?
[11:02] <mgz> you don't bootstrap three times. juju will take three machines if you want ha though.
[11:04] <vibol> i'm in manual environment did the ha work in manual environment ?
[11:05] <mgz> yes. you'll need to add-machine enough suitable things before calling enable-ha
[11:05] <vibol> i add 2 machine with juju add-machine ... and than juju enable-ha -n 3 --to 0,1 and i got machine 3 already a controller
[11:05] <vibol> i run juju status i see my new machine is add 0, 1
[11:05] <vibol> and 0, 1 is a new added machine
[11:05] <mgz> did you add-machine in the right model?
[11:05] <vibol> machine 0 already controller sory
[11:06] <vibol> why guidline from doc in manual provisioning juju add-machine ssh:xx.xx and machine showing correctly in juju status
[11:06] <vibol> i follow the doc in 2.0 version
[11:07] <mgz> and also, it's 'ensure-availability' in 2.0 so I hope that's the command you're using
[11:08] <vibol> this command is in 1.25 ? because in 2.0 i don't see this command instead of enable-ha
[11:08] <mgz> my bad, I got it backwards
[11:09] <vibol> in 2.0 it has a seperate between agent list controller list right ?
[11:09] <mgz> yeah, there are two models by default
[11:10] <mgz> one for the controllers, and one empty and ready to use for workloads
[11:10] <mgz> anyway, feel free to file a bug with your steps and what error message you get
[11:11] <vibol> i'm not good at a bug report.. but will try
[11:18] <SimonKLB> mgz: is it possible to have some kind of global configuration for every application deployment of a charm in the same config.yaml and then the specific options under the service namespace?
[11:19] <mgz> SimonKLB: I am somewhat confused about what you're trying to accomplish
[11:19] <SimonKLB> something like
[11:19] <SimonKLB> ssl-enabled: True
[11:19] <SimonKLB> service_1:
[11:19] <SimonKLB>   port: 8080
[11:19] <SimonKLB> service_2:
[11:19] <SimonKLB>   port: 9090
[11:19] <mgz> sure, but you split that
[11:19] <mgz> the config that generally applies goes in the charm
[11:20] <mgz> and the fact there is a port config option
[11:20] <mgz> the ports for specific services goes in the bundle
[11:20] <SimonKLB> hmm, this is two services of the same charm
[11:20] <mgz> sure
[11:20] <SimonKLB> im not using a bundle right now
[11:21] <mgz> you have a bundle that specifies all your services, and can include specific config for them
[11:21] <SimonKLB> so it's not possible to have global configurations without a bundle ?
[11:22] <mgz> you can do everything via command line as well
[11:22] <mgz> so, write a script that says deploy this service, set this config, and so on
[11:22] <mgz> skin the cat however you want
[11:23] <SimonKLB> yea thats what im looking to do right now, so in this example i deploy two services of the same charm, but i was thinking if it was possible to keep everything in the same config.yaml still
[11:23] <SimonKLB> but to not having to repeat stuff in the config.yaml file i was wondering if you could keep the general config options at the top?
[11:31] <vibol> when enable ha other machine is down and sad lost connection
[11:32] <vibol> but running juju ssh still working find
[11:32] <vibol> fine
[11:32] <mgz> vibol: down means the agent isn't talk back, so check /var/log/juju and such
[11:34] <vibol> juju mongo connection fail @@
[11:34] <vibol> it a strange problem
[11:34] <vibol> let see...
[11:35] <vibol> there 2 nic currently availble first primary one is private and has the static ip.. but why juju mongo try to connect the second nic instead because i set this nic to dhcp and get internet from my rounter
[11:36] <vibol> juju mongo shoud connect through the primary nic... but not sure
[12:23] <vibol> it seem like a bug ... because i can reproduce this problem anytime
[12:25] <mgz> vibol: please file one, I'm not sure how multiple nics and the manual provider are meant to play together
[12:25] <vibol> thank you.. i'm sorry to making u confuse
[12:25] <mgz> but there may be additional prerequisites on network setup before you can add-machine
[12:25] <vibol> juju seem to work not very well on manual provider
[12:26] <vibol> i can deploy a service as normal on my network setup for juju
[12:26] <vibol> the only problem os deploying ha only
[12:27] <mgz> yeah, it's likely that the state server requirements are stricter than for a normal service
[12:27] <mgz> as they need to do much more
[12:27] <vibol> i'm sorry before i file a bug
[12:27] <mgz> for instance, need to be on all networks that any other machine is on, and from your experience sounds like the local network setup also matters
[12:28] <vibol> i want to deploy all maas juju both in ha
[12:28] <vibol> and i want to deploy juju and deploy maas using juju
[12:29] <vibol> because the doc say it is possible to deploy maas using juju
[12:29] <mgz> er... you probably don't want to try that
[12:29] <vibol> -_- it really make me confusing
[12:29] <vibol> but why ? any problem ?
[12:29] <mgz> I'm aware of some very experimental maas charms
[12:30] <vibol> ohh
[12:30] <mgz> but the normal way is you just deploy maas, then can use juju for workloads on top
[12:30] <vibol> good
[12:30] <vibol> ...
[12:30] <mgz> juju drives maas quite happily
[12:30] <vibol> i though deploy maas in ha by hand is very hardwork
[12:30] <vibol> but it the same on juju with manual provisioning -_-
[12:31] <mgz> yeah, that is also true
[12:31] <mgz> well, it's easy with homogenous envs
[12:31] <vibol> i guess i should start maas in deploy juju on top of maas and see how it work first
[12:33] <vibol> and also can we install landscape with ha without using juju @mgz
[12:39] <mgz> vibol: I believe so, but you'll need poke landscape for that
[19:42] <vmorris> i have a question about charms running in a private maas deployment. i have configured http proxy in the model at bootstrap and things tend to come up fine so long as they are running inside lxd containers; however, whenever I try to deploy something directly to a maas machine, it tries to talk to the api server over ipv6. this normally woudn't be a problem but the requests are hitting my proxy server and are being rejected
[19:43] <vmorris> trying to formulate a question.. lol. How about: is there a way to force the charm deployment to only communicate over ipv4?
[19:47] <rick_h_> vmorris: juju allows using a contraint for deployment that might help there. You'd have to setup different spaces in maas for ipv4/6 subnets perhaps? and then get juju bootstrapped onto the ipv4 space and I would hope we'd use that to communicate vs the v6
[19:47] <rick_h_> vmorris: if that doesn't work I'd suggest mailing the list and I'll get some of our networking folks to formulate a more intelligent response vs a guess
[19:48] <lazyPower> rick_h_ - we used to have a prefer_ipv4  thing in the 1.24 era
[19:48] <rick_h_> lazyPower: right, that went away
[19:48] <lazyPower> rick_h_ - do you konw if that got scrubbed? i'm not finding it in teh docs anymore
[19:49] <lazyPower> ok, thats what i suspected.
[19:49] <lazyPower> thanks for confirming
[19:49] <rick_h_> lazyPower: yea, caused some issues as much as it solved and we need a better way to do that right
[19:49]  * lazyPower nods
[19:49] <vmorris> rick_h_: hmm, okay. i've been able to keep ipv6 subnets from showing up in MAAS by disabling the v6 stack on the maas controller
[19:49] <vmorris> but I keep ending up with messages like this in the juju debug log: ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: preparing operation "install cs:neutron-gateway-232": failed to download charm "cs:neutron-gateway-232" from API server: GET https://[fd55:faaf:e1ab:a4f:5054:ff:fea9:25aa]:17070/model/3a3a6a0e-e580-437c-8b25-211b188de393/charms?file=%2A&url=cs%3Aneutron-gateway-232: Get https://[fd55:faaf:e1ab:a4f:5054:ff:fea9:
[19:49] <vmorris> 25aa]:17070/model/3a3a6a0e-e580-437c-8b25-211b188de393/charms?file=%2A&url=cs%3Aneutron-gateway-232: Forbidden
[19:49] <vmorris> ew sorry
[19:50] <vmorris> these requests are hitting my http proxy server and are getting denied there
[19:50] <rick_h_> vmorris: hmm, but is something in the proxy path getting routed via ipv6? I mean if the ipv6 stack isn't on in maas not sure how juju would be initiating ipv6 traffic
[19:52] <vmorris> rick_h_: that's another thing i don't understand, this is the sort of message I see in the squid access log:
[19:52] <vmorris> 10.20.95.61 TCP_DENIED/403 3936 CONNECT [fd55:faaf:e1ab:a23:5054:ff:fe14:7dc2]:17070 - HIER_NONE/- text/htm
[19:52] <vmorris> wouldn't thins indicate that the request is coming in on ipv4?
[19:53] <rick_h_> vmorris: hmm, 17070 is the controller port. I'm not sure on the ipv4 part. Would have to try to match those ip addresses with your infrastructure and see what machines are doing what there
[19:54] <vmorris> rick_h_: these are all maas machines and lxd containers that came up as a result of a juju deploy
[19:55] <rick_h_> vmorris: right, but you're saying that the nodes don't have ipv6 enabled
[19:55] <rick_h_> vmorris: and so the ipv6 addresses must be coming from some dhcp/etc on the network?
[19:55] <vmorris> ah no.. the maas controller doesn't have ipv6 enabled
[19:55] <vmorris> i don't know if i can control ipv6 on the nodes
[19:56] <rick_h_> vmorris: so I'm curious how the deployed nodes/containers have ipv6 addresses
[19:58] <vmorris> rick_h_: ooh i see what you're saying
[19:58] <rick_h_> vmorris: right, the nodes and containers get their addresses either as hard coded or via the dhcp server maas runs.
[19:59] <rick_h_> vmorris: either way, the data comes from maas unless there's another thing in the mix there
[19:59] <vmorris> rich_h_: there's definitely not another dhcp server.. and i only enabled dhcp on the 10.20.95.0/24 subnet.. yes where are they getting these addresses?
[20:00] <vmorris> here i'll get on the juju controller node and dump out some information
[20:01] <vmorris> rick_h_: https://paste.ubuntu.com/23389877/
[20:05] <vmorris> rick_h_: v6 addressing looks like it's coming in through MAAS metadata, looking for confirmation
[20:11] <vmorris> rick_h_: lazyPower: perhaps i should've been more clear.. i've disabled ipv6 on the maas-controller itself, but there is a way to disable it in the region/rack settings as well?
[20:44] <vmorris> rick_h_: let me back up and ask a more pointed question.. if i have 3 interfaces on a maas machine, but only want to use 2 of them in my juju deployments, i can do this with spaces?
[20:45] <vmorris> or, even more to the point - if i have internet connectivity out of one interface, but want to run my juju applications on another, how is this configured?
[20:48] <vmorris> also, according to the docs, spaces are only supported on EC2
[21:46] <vmorris> question: when running juju deploy with --debug, i'm seeing some messages from httpbakery client.go GET to api.jujucharms.com -- are these requests coming from the juju controller machine?