/srv/irclogs.ubuntu.com/2017/12/14/#juju.txt

McL0v1nthedac: My juju version is 2.3.1-xenial-amd6402:00
McL0v1nthedac, maas version is 2.3.0-6434-gd354690-0ubuntu1~16.04.102:03
jac_cplaneis there anyway to completly wipe a juju controller/env?   I made the mistake of trying to upgrade juju version - which corrupted the env.   while trying to recover/remove/clean I just released the bootstrap node and uninstalled juju apt-get remove juju.    then tried to start from scratch - install juju,etc.   the problem is there are still remnants of the old system.   I just want to wipe and start from scratch.   juju03:38
jac_cplanekill-controller, destroy-controller all fail.03:38
jac_cplanefound this on the web - will this still work ?  "sudo apt-get purge --auto-remove juju"03:40
McL0v1njac_cplane that doesnt work, i tried03:42
jac_cplaneyep03:42
jac_cplaneI just tried.   btw- i guess there is no way to update juju03:42
McL0v1nops, i found the error with lxc's, This is in the logs:03:42
McL0v1nERROR juju.worker runner.go:392 exited "0-container-watcher": worker "0-container-watcher" exited: setting up container dependencies on host machine: could not find unused subnet03:43
McL0v1nthedac ^^03:44
pmatulisjac_cplane, can you open a doc issue on the wipe stuff please? https://github.com/juju/docs/issues/new03:45
jac_cplaneMcL0v1n - looks like i found the way.    juju unregister <controller-name>03:46
jac_cplanethen create a new one - same name overwrites the prev.  then you can bootstrap it03:46
McL0v1nahh, forgot about that03:48
McL0v1nalso juju kill-controller03:48
jac_cplanejuju kill-controller does not work in this case i mentioned.03:48
jac_cplaneI'll add to tghe docs03:48
McL0v1nany idea about why my lxcs are not provisioning? The error i posted above is in the host machine's logs03:50
pmatulisjac_cplane, see it, thanks03:59
McL0v1nI think it might have to be with: https://bugs.launchpad.net/juju/+bug/166564804:03
mupBug #1665648: Juju 2.0.3 fails to deploy LXD container lxdbr0 overlapping subnets <juju> <maas> <juju:Fix Released by hduran-8> <juju 2.1:Fix Released by jameinel> <https://launchpad.net/bugs/1665648>04:03
McL0v1nmup we posted at the same time04:03
McL0v1ni'm using a /8 10. subnet04:03
=== gsamfira_ is now known as gsamfira
mattywhey folks, can you have key names like "foo-bar" in config.yaml or do you need to use underscore (foo_bar) ?14:30
jammattyw: we do stuff like:14:33
jamstorage-default-block-source:14:33
jam  value: maas14:33
jam  source: model14:33
jamso foo-bar seems fine in yaml14:33
mattywjam, ok great thanks14:33
jammattyw: yamllint.com likes it fine, too14:34
mattywjam, I've seen lots of charms use _, even going so far as converting them back to - in the charm code14:34
mattywjam, so maybe it was a problem and not anymore?14:34
jammattyw: being ok in yaml != being ok in Mongo docs14:35
jamthough I think it is ok there, too.14:35
mattywjam, charm config docs?14:35
jamas we certainly use {"model-uuid": blah}14:35
mattywok great14:35
mattywI'll go with - for now thanks14:35
ybaumywhen i bootstrap a controller to eg vsphere/dc1 and want another one in vsphere/dc2. what do i have to do17:06
ybaumyi mean a failover controller17:07
ybaumyor do i have to add another controller and move it with vmotion17:09
=== frankban is now known as frankban|afk
hmlybaumy: here is some documention on juju high availablity: https://jujucharms.com/docs/2.3/controllers-ha17:22
hmlybaumy: the juju enable-ha help page has info on specifying already created machines to be controllers.  not sure if the vsphere dcs are part of constraints or not.17:22
hmlybaumy: you’d spin up a vsphere instance where you wanted it - then use juju add-machine ssh:…. to let juju know about it17:23
hmlybaumy: but the —to or —constaints flags would be better if possible17:24
ybaumyhml i did now a enable ha and moved one controller to dc217:27
ybaumyhml couldnt find anything that relates to creating it in dc2 in the first place17:27
ybaumyit also would make sense to distribute kubernetes etcd and master VM's to diffrent DC's17:30
ybaumybut appart from that and some dns problems im happy so far with it17:31
hmlybaumy: typically juju distributes between zones,17:34
hmlybaumy: looks like juju considers a vsphere dc as a region17:35
hmlybaumy: not sure if a region works with a placement directive or not.17:36
ybaumyhml so i have to create yaml to create masters in region dc1  and then dc2 ... with constraints?17:36
hmlybaumy: you don’t specify a region with a constraint: https://jujucharms.com/docs/2.3/reference-constraints#vsphere-provider:17:38
hmlrick_h: any ideas on how to do juju ha across regions (or vsphere dc)?17:44
rick_hhml: hmm, can you add-machine into the region and try to enable-ha --to ?17:47
rick_hhml: I think it'll be on your to make sure the controllers are reachable on a network level there17:47
hmlrick_h: that was my thought too, just wondering…17:47
rick_hhml: yea, not tried it but I think that should work17:47
hmlybaumy: ^^^17:47
hmlrick_h: regions don’t work with placement directives correct?17:48
rick_hhml: no, they're model level when you add-model and such17:48
rick_hhml: as all of the model is in the same region, otherwise there could be issue17:48
rick_hhml: region->region would need to be a CMR setup and controllers don't do that atm17:49
hmlrick_h: right17:49
ybaumyrick_h: hml thanks for clearing that up. but from a HA perspective its suboptimal18:00
rick_hybaumy: I'm sure there's ways to do it differently but my experience with clouds has been regions are for fallback and cross region coms can be slower/more $$ then inner region.18:01
rick_hhaving a controller in different regions raises all kinds of questions about the workloads in that region/etc.18:01
ybaumyrick_h: from your perspective its ok to handle it this way. from mine it doesnt since datacenters are only few kilometers away18:04
ybaumyrick_h: so HA is something im looking for18:05
rick_hybaumy: understand, it's an interesting perspective and if the networking/latency is good I can see that. It starts to feel like regions should be zones in that situation as far as spreading all units of workloads out across them as well.18:05
rick_hI mean if the region goes boom than any workloads the controller is managing goes with it18:06
ybaumyrick_h: well im talking on premise cloud though18:06
rick_hybaumy: right, do you have zones in each region?18:06
ybaumyrick_h: thats a different approach18:07
* rick_h is curious how it's setup 18:07
ybaumycurrently we spread masters and workers and etcd 's accross two datacenters. pods are also setup in a way to handle workloads if one DC is out18:08
ybaumykubernetes is what we are interessted in with juju18:08
rick_hybaumy: which on prem cloud is this? /me reads back18:08
rick_hoic, vsphere18:09
ybaumyrick_h: our companies vsphere18:09
ybaumyrick_h: we are using openshift atm from redhat but it costs .. though im looking into other directions18:09
rick_hyea, I'm not familiar with vsphere as much. I know in maas/openstack the we think of zones as you're doing dc's in vsphere. It's why we're hitting this mismatch as we obviously really care/want to have HA whereever possible in Juju and the workloads running.18:10
ybaumyrick_h: we would really like to see that18:10
ybaumyrick_h: first i made test with maas and vsphere and juju and then on top kubernetes but maas lets is also not what i want. 2.3 is really neat18:12
ybaumyjuju 2.318:12
ybaumyi like that its talking directly now with API18:12
rick_hybaumy: I'm glad you're finding Juju interesting. I wish I had better news on the cross zone HA setup. Like I was saying, you can work around it by manually adding machines I think, but then once you go deploy things they'll only go into the original region which isn't what you're going to want18:12
ybaumyrick_h: maybe in the future. tomorow our architects will get a presentation with juju setup from me. i hope they like it18:14
ybaumyas much as i do18:14
rick_hybaumy: in the long run it'd be interesting with 2.3 and cross model relations if the charms in k8s could treat relations across the models as a way to do its HA work and so you'd just deploy two k8s and relate them and they'd combine into a super k8s18:14
rick_hybaumy: cool, let us know if we can be of any help18:14
ybaumyrick_h: i will give a feedback18:14
rick_h<318:14
ybaumyim the canonical guy though .. most ppl think of canonical as desktop client OS and services18:15
ybaumyi hope i can change that18:15
rick_hybaumy: same here, we've put a lot of time and effort beyond the desktop :)18:19
ybaumyrick_h: in germany i tell you its really hard to find ppl who use ubuntu and other serivces professionaly18:22
rick_hybaumy: ah you're in germany? Yea, that's a tough nut there. Wasn't/isn't germany still very suse friendly as they were from there?18:23
ybaumyrick_h: we use suse for SAP of course cause there is no competition in this case. we use redhat and centos for everything else. but you are right SuSe is really popular18:24
ybaumyi tried their container platform lol18:25
ybaumyand ceph storage18:26
ybaumyits full of bugs18:26
ybaumyyou just cant use it18:26
ybaumySLES enterprise server is really stable for SAP and HANA18:26
ybaumyanyways i call it a day. beer is waiting. ttyl18:32
=== thumper is now known as thumper-away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!