[07:46] <kjackal> Good morning Juju world!
[10:23] <surf> hii all, I am bootsraping juju on openstack cloud how much time it will take to complete bootstrap
[10:24] <surf> i am suspecting it is strucked at "Running apt-get upgrade"
[10:24] <surf> please someone help
[10:26] <sparkiegeek> surf: how long is a piece of string? It's impossible to say how long it will take, but if you're having problems you should paste debug logs from bootstrap (e.g. --debug)
[10:27] <sparkiegeek> surf: also, look at https://jujucharms.com/docs/2.0/models-config#apt-updates-and-upgrades-with-faster-machine-provisioning to turn off the apt step
[10:30] <surf> sparkiegeek: here is my bootstrap command and output http://paste.openstack.org/show/596012/
[10:34] <sparkiegeek> surf: is your OpenStack otherwise healthy? i.e. can you start an instance, assign a floating IP and SSH to that floating IP?
[10:35] <surf> sparkiegeek: yeah my openstack instance is in active state
[10:35] <sparkiegeek> surf: ah somehow I missed the last couple of lines - so it successfully reached the instance in the end
[10:35] <surf> yes
[10:35] <sparkiegeek> surf: so yeah - I think if you've got up to date images in Glance, then you can safely disable the apt update/upgrade steps
[10:37] <surf> sparkiegeek: Tell me the way to do this
[10:38] <sparkiegeek> surf: use the --config option of juju bootstrap and set enable-os-refresh-update and enable-os-upgrade to false
[10:40] <aisrael> Does any documentation for configuring Juju 2 under centos7 exist? The only page in the docs I can find is for 1.24
[10:41] <surf> sparkiegeek: could you provide a sample command
[14:59] <lazyPower> bdx - heyo, i know you're not in office yet, but I'll take a look at your Elasticsearch peering code before I leave office today. Thanks for being patient on that request.
[14:59] <lazyPower> magicaltrout - only a handfull of days left before we go sample the belgium microbrews :D
[16:32] <bdx> lazyPower: 10-4, thx
[16:38] <lazyPower> np np
[16:38] <lazyPower> happy to help where i can
[20:47] <bdx> lazyPower: is there a kubernetes bundle that includes the monitoring pieces?
[20:47] <lazyPower> bdx - looking specifically for the beats bits without manually relating?
[20:47] <lazyPower> ryebot - can you run a quick build and publish to your namespace w/ the monitoring segment? I know we didnt publish that as we haven't settled on naming schema for the addon bundles.
[20:48] <ryebot> lazyPower: yep, no problem
[20:49] <ryebot> lazyPower: cdk or core?
[20:49] <lazyPower> ty ryebot
[20:49] <lazyPower> bdx ^ preference on which base solution?
[20:51] <bdx> lazyPower: canonical-kubernetes?
[20:51] <lazyPower> ryebot ^
[20:51] <ryebot> ack
[20:55] <ryebot> lazyPower bdx: https://jujucharms.com/u/ryeterrell/cdk-flannel-elastic/
[20:55] <ryebot> ^ untested recently
[20:55] <lazyPower> ryebot - a gentleman and a scholar, ty ty ty
[20:56] <ryebot> anytime
[20:56] <bdx> lazyPower, ryebot: thanks!
[21:18] <CoderEurope> marcoceppi_: You good for Tuesday & getting discourse upto date with a Juju charm ?
[21:18] <petevg> kwmonroe: if I'm co-locating two services on the same machine, what's the bundle yaml syntax for putting them in lxd containers?
[21:20] <kwmonroe> petevg: it's "to: blah" to put multiple services on the same machine.. lemme see about lxd directives.
[21:20] <petevg> kwmonroe: I know about the "to" part. Couldn't find the directive bit in the docs ...
[21:20] <kwmonroe> petevg: looks like "to: lxd:n"... https://jujucharms.com/docs/2.0/charms-bundles#bundle-placement-directives
[21:21] <petevg> kwmonroe: sweet. Thank you :-)
[21:21] <kwmonroe> np
[21:21] <cholcombe> do we have any charms out there that manage ca certs?
[21:22] <kwmonroe> cholcombe: pretty sure lazyPower and mbruzek do that ^^ easyrsa maybe?
[21:22] <rick_h> cholcombe: and wasn't there some look at vault or something in the openstack team for some of that?
[21:22] <cholcombe> kwmonroe, thanks
[21:22] <cholcombe> rick_h, well vault encrypts things at rest
[21:23] <kwmonroe> cholcombe: https://jujucharms.com/u/containers/easyrsa/6 might be what you want
[21:23] <lazyPower> cholcombe it uses a single CA, non encrypted at rest, but easyrsa is our go-to for that atm
[21:23] <lazyPower> its just a bunch of bash wrappers around the openssl cli
[21:23] <cholcombe> lazyPower, that's exactly what i need.  a single ca
[21:23] <lazyPower> if you have an existing CA cert, you should be able to side-load that into the charm as well
[21:23] <lazyPower> consult the readme for specifics
[21:23] <lazyPower> if anythings funky, ping me or mbruzek  and we'll try to step you through it
[21:24] <cholcombe> lazyPower, much appreciated
[21:24] <lazyPower> np np
[21:24] <lazyPower> happy to help where we can
[21:26] <cholcombe> lazyPower, so is easyrsa by containers what i want?
[21:26] <lazyPower> cholcombe yep, thats the latest and greatest. i don't think its gotten a review to be promulgated yet
[21:26] <lazyPower> sof or now the namespace is the difinitive source
[21:26] <cholcombe> that's fine
[21:26] <marcoceppi_> CoderEurope: Yup!
[21:43] <CoderEurope> marcoceppi_: Cheers - see you (at what time UTC??) tomorrow ...
[21:44] <bdx> if I am deploying lxd containers via e.g. `juju deploy ubuntu --to lxd:N` is there anyway to have the production considerations for lxd applied to my juju deployed lxd hosts? does the lxd charm do this?
[21:45] <bdx> should I create a subordinate for this?
[21:45] <rick_h> "the production consideerations"?
[21:46] <bdx> rick_h: https://github.com/lxc/lxd/blob/master/doc/production-setup.md
[21:47] <lazyPower> host var tuning for open file pointers and what not
[21:48] <lazyPower> yeah, we've talked about this briefly too on the application container side of things
[21:50] <bdx> rick_h, lazyPower: I have a bundle that deploys 14 lxd to a host ... using the aws provider
[21:51] <bdx> rick_h, lazyPower: I'm thinking a subordinate that adds the production setup config for lxd might be the answer I need
[21:52] <lazyPower> bdx - seems like a good work-around until we can tweak/tune that from juju. However i'm not certain how much of that production-setup doc we've encapsulated in the lxd logic of the juju agent.
[21:52] <bdx> rick_h, lazyPower: I was hoping the lxd charm does this already, but it doesn't look like it
[21:52] <lazyPower> there's likely some overlap, but hard to say without investigation
[21:52] <bdx> lazyPower: I don't think any of it has been
[21:54] <CoderEurope> marcoceppi_: Cheers - see you (at what time UTC??) tomorrow ...
[22:20] <marcoceppi_> CoderEurope: 3PM EST / 8PM UTC
[22:21] <CoderEurope> marcoceppi_: gotcha - I shall be there :)
[23:54] <lazyPower> bdx - ok just finished up with piloting a large PR into the k8s repo. lets context switch to elastic questions and then i'm gonna EOD. Is the elastic-charmer doc updated with the most recent information I should be looking at?