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

Guest20118@tavansteenburgh, thanks00:05
=== scuttlemonkey is now known as scuttle|afk
=== menn0 is now known as menn0-afk
kklimondawhen is 2.1.2 being released? launchpad suggests last friday, but there are no packages I can find06:11
kklimondazeestrat:  looks like I can't reference variables in other variables? I guess that would be cheating ;)06:42
kjackalGood morning Juju world!07:27
zeestratkklimonda: Yeah, I tried that too ;)08:22
cnfcan you register multiple users on one machine with juju?09:56
cnfand switch between them?09:57
kjackalcnf you can register multiple users on the same controller09:59
cnfkjackal: yes, but can I log in to different users on the same local machine10:01
cnfusing the juju command10:01
cnfi don't want to be admin all the time10:01
kjackalcnf: I have never seen that10:02
cnfhmm10:02
cnfand no ACL's either, it seems10:02
kjackalyou mean do a "juju ssh myapplication/0" and you get a shell that is not a sudoer user10:03
kjackalThat is an interesting feature. What is the use case you want to serve with this?10:03
cnfno, i mean juju register10:05
cnfmultiple users10:05
cnfright now, everything i do with the juju command is as admin10:06
cnfhave to pick up some guests at reception, brb10:07
cnfback10:13
cnfkjackal: i basically want to restrict myself when i don't need to be admin10:14
kjackalcnf: your juju client can be a non-priviliged user10:14
kklimondaI just had juju fail to bring a couple of containers on two machines, with error cannot start instance for machine "0/lxd/15": unable to setup network: no obvious space for container "0/lxd/15", host machine has spaces: "management", "two-ceph-private", "two-ceph-public"10:15
kklimondabut that actually worked fine for other units of the same application, and for other containers on the same machine10:15
kklimonda(I'm testing 2.1.2 from git right now)10:15
cnfkjackal: right, but do i need to delete the admin credentials?10:16
cnfor can i swap between them?10:16
kjackalcnf: what kind of credentials?10:17
cnfkjackal: the admin user you are authenticated with10:26
cnfkjackal: now, my juju command is registered as full admin, right?10:27
cnfi can destroy models, delete users, etc etc10:27
kjackalyou can create a juju user (juju add-user) and then grant permissions (eg juju grant myuser add-model)10:28
cnfright, i did that10:28
cnfbut when i want to register it, it says i can't because i am already registered10:28
cnfso is the only way to unregister the admin user, and register the new user10:29
cnfand when i need admin the other way around?10:29
kjackalI ahven't tried to register a juju user with a local user that is already registered10:31
kjackalI guess it is expected for juju to complain10:31
kjackalcan you have a second local user to register with the controller with limited permissions?10:32
cnfyou mean add a new local user?10:32
cnfthat's a lot of extra work for this :P10:33
cnfmaybe i'll set up a docker container or something10:35
hoenircan anyone recommand me a charm that supports adding storage?11:32
kklimondaceph and ceph-osd11:34
tvansteenburghhoenir: the postgres charm does11:44
kklimondawhen juju is deploying containers on MAAS, what is responsible for assigning IPs? I have a reservation for IP range, but Juju still deployed LXD containers with IPs from this range12:33
cnfkklimonda: did you have free ip's?13:10
kklimondacnf: I should have 100+ free IPs in that netwokr13:34
kklimonda(based on quick math and what MAAS tells me)13:34
cnfk13:37
cnfi had all ip's in either dynamic or static pool13:37
=== scuttle|afk is now known as scuttlemonkey
skayskayresources question. I have a snap charm and made a bad assumption about resources as optional things. I thought I could remove a resource. The charm is for a public snap, so I want to grab it from the store.14:04
skayskaybut when I want to test a change in a fully deployed environment, I'd like to attach a snap resource14:04
skayskaythat is a bad assumption since I can't remove a resource.14:05
skayskayso, how do people normally test things in that situation? I'd rather not push a candidate snap if I'm doing something like adding debugging code to get more info, etc etc etc14:05
stubskayskay: If you are using the snap layer, attaching a 0 byte resource is effectively the same as removing the resource.14:14
stubskayskay: You should be able to have your edge charms with a snap attached as a resource, and your stable channel charms with no snap or 0 byte resource.14:15
skayskaystub: thanks, I didn't think of attaching a new zero byte resource. I feel sheepish now.14:15
skayskay:)14:16
skayskay(I am using the snap layer)14:16
stubskayskay: Its a hack, but works until we can drop this resources-are-required nonsense.14:16
=== scuttlemonkey is now known as scuttle|afk
=== scuttle|afk is now known as scuttlemonkey
=== scuttlemonkey is now known as scuttle|afk
ZiclazyPwr: hey, long time since we didn't talk, I have a question for you (or for marcoceppi too), can I update the nginx-ingress-controller deployed by CDK manually?15:24
ZicI need this functionality recently merged: https://github.com/kubernetes/ingress/pull/246/commits/5cc5669938108ab7429bc7eee40c18a6ba18150a15:24
lazyPwrZic: hey, 1 sec let me see whats in teh link15:25
lazyPwrZic: so this looks like k8s golang bin code... do you know if this is landing in the addon container?15:26
lazyPwrZic: if so, you should be able to just update the image reference in /etcd/kubernetes/addons/ingress-*.yml15:26
lazyPwrZic: however, you might need to set it in the Template dir of the charm, so it doesn't get autogenerated right back out of the template before its re-scheduled15:26
lazyPwrstub: hey little bit of an update on that btw, i spoke to rick about optional resources @ the last sprint. It's now acknowledged that its a potential issue, but no resolution has been offered as of yet.15:27
ZiclazyPwr: the last message is what I feared :( can I do this simply without breaking future updates of the charm ?15:28
lazyPwrskayskay: also, one workflow tip that mbruzek and I have done is resource-revision 0 is always a zero byte resource (by convention, we touch and push) so you can always re-publish with a zero byte resource simply.15:28
ZiclazyPwr: or do you know if this PR is already in the image used by the kubernetes charm in 1.5.3? I'm always on 1.5.2 currently15:29
lazyPwrZic: certainly if you patch the template and toggle ingress=true it will get your update. on teh next charm-upgrade it will ovewrite the changes to that template and you should be back in alignment with our upstream releases15:29
lazyPwrZic: i'm not positive on if its in the 1.5.3 release, it depends on when it was cut and added.15:29
Zicyeah, I saw this PR have 26 days, but I don't know if it was merged for the 1.5.3 release15:30
lazyPwri'm going to err and say it wasn't15:30
Zichttps://github.com/kubernetes/ingress/pull/246 <= thr PR associated15:30
lazyPwrZic: the trouble here is the issue wasn't attached to a release https://github.com/kubernetes/ingress/issues/18015:31
lazyPwrso its hard to discern when it was actually pulled into a release or if its just sitting in trunk15:31
lazyPwrZic: i would probably ping one of the authors of this pr and ask when it was/will-be released.15:31
ZiclazyPwr: thanks, also, just seeing the tag "Coverage 46%" in the Issue, seems that it's sure that it's not released so :(15:35
ZicI will try to ping the author anyway15:36
mbruzekZic: I can get you a resource if you can examine the binary files to see if the fix is in there.15:39
mbruzekZic: Alternately if you check out the tag branch "v1.5.3"  You could check for the code in there15:40
Zicmbruzek: good idea, it seems to be this one: https://github.com/kubernetes/ingress/releases/tag/nginx-0.9.0-beta.215:42
ZicI will check15:42
Zicok so15:44
Zic1.5.2 and 1.5.3 of Kubernetes in CDK's charm both use 0.8.3 of this nginx-controller15:44
Zicthe proxy-set-headers I need appeared in 0.9.0-beta215:45
Zic(but it's beta as you can see...)15:45
Zicbut a later stable version is 0.9.215:45
Zicare you planning to switch to 0.9.2 in next release so? :D15:46
Zichttps://github.com/kubernetes/ingress/releases <= oh, I do a mistake, it's not Nginx which is in 0.9.2, it's GCE ingress...15:49
Zicthe latest version of nginx-ingress-controller is still 0.9.0-beta.2, which contains the feature I wanted15:49
ZiclazyPwr / marcoceppi : for waiting, as I really need to customize nginx header for the launch of this customer, can I simply "kubectl edit rc nginx-ingress-controller", swap the image to "gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.2" instead of "gcr.io/google_containers/nginx-ingress-controller:0.8.3" (which CDK deployed) ?15:55
Zicas I understand, nex-upgrade will overwrite this change15:55
Zicbut I just need to recall myself to re-put it, no?15:56
ZicI don't feel confident in hacking the CDK template and deploy it for a production cluster :/15:56
marcoceppiZic: good question, Cynerva ryebot ^ ?16:07
Cynervacatching up, gimme a minute :)16:08
Zic:)16:09
Zichaha, I just realize that I confused marcoceppi & mbruzek for my earlier highlight-ing of CDK's maintainers :)16:11
Zicsorry :]16:11
CynervaZic: it looks like kubernetes-worker won't override the ingress RC until the charm is upgraded16:13
Zicand do I need to rollback to the original version of CDK kubernetes-worker charm before the next upgrade ?16:15
CynervaZic: so I think as a temporary workaround that should work. but i'm not 100% sure16:15
CynervaZic: hmm good question. all the charm does is `kubectl apply -f ingress-replication-controller.yaml` so i would think you won't have to roll it back before charm upgrade16:17
Zicok thanks16:22
ZicI think I will upgrade from 1.5.2 to 1.5.3 before testing this16:22
Zicplanned for tomorrow, I will let you know if it works :)16:22
Zic(the ingress upgrade part, I'm confident for 1.5.3 upgrade part)16:23
Cynervacool :D16:24
* Zic fix lazyPwr's eyes for the second part of his message16:24
Zic:}16:24
lazyPwrO_o16:25
lazyPwro_O16:25
* Zic begins to search "juju rollback command"16:26
ZicxD16:26
lazyPwrwait for snaps my friend, it'll make your roll forward/backwords life a bit easier.16:26
lazyPwrZic: have you seen the etcd 3.x migration bits using snaps?16:26
Zicnop, the last time we talked about this, it was not publicly released16:27
Zics/publicly/officially/16:27
Zicdoes it now?16:27
stormmoreI still have the the thought about using snaps on switches / routers to load the maas and juju controllers onto them instead of servers16:28
lazyPwrstormmore: you're not alone in that thought :)16:33
lazyPwrstormmore: however storage on a switch is going to be hairy at best... you'll likely want to run your rack controller on a unit with some storage16:34
lazyPwrZic: its pending a merge against layer-etcd, i have it published in my namespace though16:34
Zicoh, I can test it in the lab so :)16:34
lazyPwrZic: it supports moving between channels, and if you dont attach external storage (read: ebs/gce volumes) it'll version your data16:34
lazyPwrso say you upgrade to 3.0/stable channel and things get funky, NO PROBLEM!16:35
Ziccurrently, we have deployed our 2nd CDK cluster, full-AWS this time16:35
lazyPwrrevert back to 2.3/stable16:35
lazyPwrand it'll reload your data from the version of the snap that was installed using 2.3, you may incur some minor data loss, but this is expected with a rollback no?16:35
Zicand I convert the LXD labs into a real lab16:35
lazyPwryeah?16:35
stormmorelazyPwr, yeah I realize that but storage is only a problem when you are a boot strapping the data center. once the servers are up, the db, etc. can be moved into the cluster16:35
lazyPwrnice man :) You're getting your hands all kinds of dirty with cdk16:35
ZiclazyPwr: yeah, I'm just using NFS & ISCSI volume16:36
stormmorelazyPwr, that just leaves the core services running on the switches / routers, i.e. pxe, etc. from maas and the juju controller agent16:37
Zic(for the first CDK cluster actually)16:37
lazyPwrZic: i was talking to cholcombe and it appears that gluster+heketi is going to be problematic moving forward16:37
lazyPwrsome mailing list drama popped up about this :/16:37
Zicfor the second one, we're using AWS-EBS16:37
lazyPwri read into it a bit, and they are wanting to not support existing glusterfs deployments, which baffles me16:37
cholcombei find it odd also16:38
Zic(the first-one is the one I gave you the Architecture Plan, hybrid between baremetal servers / on-premise VMs & EC2@AWS)16:38
Zic(the second-one is full-AWS)16:38
lazyPwrcholcombe: <3 can we send them a gentle reminder to not stab their users in the face with a hot branding iron?16:38
cholcombei tried on the irc channel and they shot me down16:38
lazyPwrbecause $reasons again?16:38
cholcombeyeah because deploying onto an existing server that they didn't setup is hard16:39
cholcombei get it but at least try16:39
lazyPwrso what if we dont support existing clusters and instead make it a charm deployed glusterfs endpoint the only one we support in cdk?16:39
lazyPwror am i missing something16:39
lazyPwri dont think its out of the question to have a storage admin provision some bricks and enlist them in a gluster charm deployment, then xmodel relate them to cdk workers16:40
magicaltroutlazyPwr: http://pastebin.com/E4ZrqzNN16:40
magicaltrouthttp://pastebin.com/ewUELFwT16:40
magicaltroutgot any suggestions?16:40
cholcombelazyPwr: suggesting we just take over for heketi?16:40
lazyPwrmagicaltrout: how did you deploy this?16:41
magicaltroutmaual16:41
magicaltroutmanual16:41
ZiclazyPwr: basic question, does the "juju upgradecharm <app>" have a special order recommended? because between the insights.ubuntu.com news and https://kubernetes.io/docs/getting-started-guides/ubuntu/upgrades/, it's not the same16:41
lazyPwrZic: follow the kubernetes.io docs16:41
Zicupgrade-charm*16:41
magicaltroutjust walked through the bundle16:41
Zicok :)16:41
lazyPwrwe've kept that up to date16:41
lazyPwrmagicaltrout: are these local copies of the charms?16:41
magicaltroutnope16:41
magicaltrouti've got 2 running workers and 2 stalled16:41
lazyPwrmagicaltrout: well at the end of teh day it appears the resources didn't make it out of the charm store. You'll want to fetch the resources from jujucharms.com/u/containers/kubernetes-worker and juju attach them16:42
ZicAt this time rolling back etcd is unsupported. / At this time rolling back Kubernetes is unsupported. <= you already prepare this section about snap :D16:42
lazyPwrZic: not until it lands as GA16:42
lazyPwrbut yeah, i'll be adding subsections there about rollbacks using the snaps and what to expect16:42
Zicthe only snap-in-production that I used today is Rocketchat16:43
lazyPwrZic: i'm expected to have this fully landed and r2g by the time we cut the 1.6.x release16:43
lazyPwri've got some really good early tests in, i'm hacking on fixing the whole "i killed the master and my cluster just pooped the bed" bug16:43
Zic:}16:43
lazyPwrwhich is really obnoxious if you're not paying attention to what you're doing... juju remove-unit etcd-master, and suddenly things brick16:43
lazyPwr*sadtrombone.wav*16:43
ZicI need to switch to multimaster again some day also16:43
ZicI'm also on monomaster in production for now16:43
Zicthe lab is in multimaster with your patch for token16:44
lazyPwrZic: we have incoming work rn to hack in place an haproxy load balancer instead of that nginx based one16:44
lazyPwrmy colleague is hacking on that rn16:44
lazyPwrmagicaltrout: lmk if that doesn't resolve it, and i'm going to point a finger at a juju bug that i hvaen't found yet, but it seems like it just bailed during grabbing the resource, which is unfortunate :( i've seen this once before but it was back in the 2.0 beta days16:44
lazyPwrmagicaltrout: actually, are you still using a beta or did you finally upgrade to GA?16:45
magicaltroutthanks lazyPwr testing16:47
magicaltroutthis is a new deploy for the  JPL folks so nothing beta here :)16:48
* lazyPwr snaps16:48
magicaltrout2.0.216:48
lazyPwri was kind of hoping you would say beta-18 again, so i could easily point to why it happened16:48
magicaltroutit might have been connectivity betwen the openstack units and the charm store, but it would be nice for juju to recover if that were actually =the case16:49
ybaumyhuhu juju16:59
ybaumycan somebody tell me how to filter hosts to use for a cloud by zones in maas17:00
ybaumyi tried adding zone = foobar to the yaml file for the cloud17:00
ybaumybut that didnt work17:00
andrew-iiIf a MAAS node is released while it is a Juju controller... can I get that controller removed? It seems hung on `juju destroy-controller someController`17:17
ybaumyhave you tried unregister17:19
andrew-iiNot yet... one moment17:19
andrew-iioh17:19
andrew-iiWell, that was fast.17:20
ybaumydid it work17:20
andrew-iiThanks! I think I can rebootstrap it now17:20
ybaumyyes you can17:20
ybaumyhad a similar problem and that helped me too17:20
ybaumydo you happen to know how to filter maas nodes for a cloud by zones?17:21
ybaumyi need to know if that is possible17:22
andrew-iioh man, I am barely getting this thing to download images from ubuntu's cloud repo17:22
andrew-iiI vaguely remember that... one sec17:22
andrew-iiNuts, that's next on my list of things to try17:23
andrew-iiThat's what works with the HA zones, right?17:23
ybaumywell i want to create nodes for customers and add them to zones. then create a cloud for that particular zone17:24
ZiclazyPwr: I have a lot of apt updates also on the 1.5.2 cluster I'm planning to upgrade tomorrow, do you advice me to firstly run juju upgrade-charp <app> *before* apt update/upgrade ?17:24
Zic(to bypass some problem like the time apt upgrade etcd without the charms :/)17:24
andrew-iiybaumy: I was going about that upsidedown and was going to use Openstack to partition customers. But you make an interesting point; if I had my old pile of blade servers that sounds pretty good17:25
magicaltroutokay i think we can safely say Juju doesn't like deploying stuff to low power vms17:25
=== hml_ is now known as hml
ybaumyandrew-ii: a customer should be able to create his own cloud by a webinterface with vmware and maas. that the target.17:26
andrew-iiI don't have vmware, but my customers really only need containerization, so I probably have a different use case17:27
ybaumyandrew-ii: true. thats different. i have thought about that too. and will look into it once i am able to do that ..17:28
ybaumyim creating POC's for my company17:28
ybaumyso its just try and play at the moment17:29
andrew-iiybaumy: I get the feeling it's jumping right into the deep end to go straight-up containerization. But I only have a few machines for maas, so I can't afford to dedicate to each customer. But man, that sounds like a nice idea.17:29
andrew-iiybaumy: same here; if I can get the cloud bootstrapped and somehow lock it down _and_ get it to be usable, then it'll be a nice playground.17:30
ybaumyandrew-ii: we have vsphere vrealize scripted to create the vm templates and distribute them across the esx farms. then i use maas to commission them and juju to create the cloud17:31
ybaumybut now i need something to filter those vm's17:31
andrew-iiybaumy: slick. It does sound like zones are exactly what you'd want (if I understand why they were added).17:32
ybaumyandrew-ii: yes its really working now. its one last piece to put it together and close the POC17:33
andrew-iiBest I can figure is the `juju deploy someCharm --to zone=maasZone1`, but I bet you're not really looking to use the --to command17:33
ybaumyandrew-ii: does that work?17:33
ybaumyi have to try17:33
andrew-ii(For my setup I'm using maas tags to filter machines, sadly, so I may be a terrible example)17:34
andrew-iiybaumy: note that I just sorta stole that command and assumed it worked! It may be aws specific (or maybe maas emulates that too) - sorry if it fails utterly17:35
ybaumyandrew-ii: great this seems to work. at least it used now for bootstraping the foobar zone i specified17:36
andrew-iiybaumy: holy mackeral, whelp, I'm more optimistic now (I actually thought it'd fail...).17:37
ybaumymaybe its luck but i will try that a few times17:37
andrew-iiThat's the spirit!17:38
lazyPwrmagicaltrout: yeah it tends to yield a pretty crummy experience when you starve the unit resources17:56
lazyPwrZic: probably do the upgrade charm then run the apt update/upgrades17:57
lazyPwrZic: keep your change set to the least viable change in order to validate things are functional after making the change17:57
ybaumyandrew-ii: sadly this --to zone= seems to be ignored. i bootstrapt it then i wanted to enable-ha --to zone=foobar and one node was created in default one in foobar18:01
magicaltroutindeed lazyPwr i was hoping the units would at least start though :)18:01
ybaumyso i need something else18:01
andrew-iiybaumy: sorry - I was afraid it wouldn't work with maas yet18:01
ybaumyandrew-ii: thanks anyway .. better die trying then havent tried at all18:02
andrew-iiMight be worth checking if a newer version manages to use it (though I think I got that command from 2.1.1)18:02
ybaumyim using devel18:03
andrew-iiouch, nevermind then18:03
andrew-iiDid you try `--constraints zone=foobar` ?18:03
ybaumyhmm no :D18:03
ybaumywill do18:03
ybaumyhehe18:03
=== hml_ is now known as hml
andrew-iiI have some real goofy machines to play with, and some are only good at certain things (like one's basically a bank of hard drives), so I use `--constraits "tags=storage"` for that one18:05
ybaumywhat is your goal what are you trying to accomplish?18:05
andrew-iiThough just in case, make sure when boostrapping a controller you use `--boostrap-constraints` instead (otherwise the controller sets ALL nodes to use that constraint)18:06
ybaumyk18:06
andrew-iiI have a hodgepodge of random servers to play with, and I need a test rig that can simulate a network; plus host some in-house tools that will get replaced often18:06
andrew-iiLiterally random machines collected off craigslist for a few months18:07
ybaumyis that you homelab?18:07
ybaumyyour18:07
andrew-iiIt's my equipment, but it's hosted in the office for it's fancy 220V line, space, and dedicated network connection18:08
ybaumyi started also with some few blades but now the project has management attention18:10
ybaumyso i got everything i requested18:11
ybaumythat neat18:11
andrew-iihaha always the best when people with checkbooks take notice18:12
ybaumytrue18:14
ybaumy juju deploy --to zone=test cs:bundle/openstack-base-4918:28
ybaumyERROR Flags provided but not supported when deploying a bundle: --to.18:28
ybaumyalso something that should work18:28
andrew-iihmmm, yeah, that's what I thought to try18:29
ybaumyi will try single charms to see how that goes18:30
ybaumynope ignored as well18:36
ybaumyjuju deploy --to zone=test -n4 cs:ubuntu-1018:37
ybaumycreates random machines in all zones18:37
ybaumyi will try tags18:48
andrew-iiThat should work, though it's a pain to tag all the machines18:49
ybaumyyep18:49
ybaumyseems like that you cannot assign tags to all machines in a zone18:50
andrew-iiNuts. Need to do something complicated like a script to assign them all? (Overkill maybe?)18:50
ybaumyyou are right. i will have to script it but thats not the problem. it would be nice if something like that would be supported out of the box18:52
=== hml_ is now known as hml
andrew-iiI think there is a goal for it, it's just not added in yet?18:59
ybaumywe have to ask the devs19:00
ybaumyi signed up on the mailing list maybe i get an answer there19:00
andrew-iiybaumy: I don't know too much about navigating launchpad, but check https://launchpad.net/juju to see if that feature is slated for addition19:02
ybaumyjuju deploy --constraints tags=test  cs:bundle/openstack-base-4919:08
ybaumyERROR Flags provided but not supported when deploying a bundle: --constraints.19:08
ybaumy;)19:08
zeestratybaumy: 99% sure --constraints/--to don't work with bundles19:09
zeestratybaumy: same with --config19:10
ybaumyzeestrat: thats too bad. shouldnt they?19:10
zeestrat--config is on the roadmap19:10
ybaumysingle charms work now with contraints with tags thats nice so i have to script the whole bundle setup as single charms19:11
zeestratconstraints and to are (or at least can be) defined in the bundle so the idea is that you set them there19:11
ybaumyok so i can generate a yaml file with --contraints?19:12
ybaumythe format with all the : at the end is really hard to script19:13
ybaumyhmm19:13
ybaumyi will try and see19:13
zeestrathave you checked out https://jujucharms.com/docs/stable/charms-bundles ?19:13
ybaumybefore not. but i can just generate it one time and then use perl or sed to change the tags=test to tags=somethingelse19:16
ybaumynice19:17
ybaumy:)19:17
ybaumythanks zeestrat19:17
ybaumythat will do19:17
zeestratybaumy: glad to help :) There are no examples of using variables in the docs at the moment, but here's a openstack HA bundle you can look at: https://launchpadlibrarian.net/298175262/bundle.yaml19:18
ybaumyno need for variables. i just sed -i 's/tags=test/tags=somethingsomethign/g' in the file for each process before i start juju deploy bundle.yaml19:20
ybaumyand thanks for the HA link19:21
ybaumywill try tomorow. now football19:38
stormmorelazyPwr, trying to put together my budget ask, is there any conference, etc. that would be good for me to try and attend? any suggestions?19:48
magicaltroutall of them \o19:50
ybaumyzeestrat andrew-ii adding constraints to the bundle works. thanks for helping me.19:53
stormmoremagicaltrout, yeah I wish I could get the budget for that :-/ I have to be more realistic than that and target kubernetes, juju, maas related ones as well as the automotive ones since that is the industry we are actually in19:55
magicaltrouthmm wtaf, my deployment is green but the ingress proxy just gives me a 504 on  absolutely everything =/19:56
magicaltroutwhat country you in stormmore ?19:56
hatchcan a 'requires' relation be related to two 'provides' at the same time?19:57
lazyPwrstormmore: well, the charmer summit is great if you want facetime with us to hack on projects :)19:57
hatchex) kibana1 to elasticsearch1 and kibana1 to elasticsearch219:57
lazyPwrstormmore: however if you want k8s focus, you're more than likely going ot have success attending kubecon's but our presence there isn't very big. Mostly what I would call guerilla community ops, where we roam hallway tracks and find people to engage with19:58
lazyPwrhatch: depends on how the charm is coded to use those relationships, but yeah.19:58
hatchlazyPwr ok so there is no Juju restriction to that effect?19:58
lazyPwrinterfaces as the abstraction, you should be able to interface with both es clusters, but its up to the app to implement that, and up to the author to correctly implement the data coming from the interfaces.19:59
lazyPwrafaik, nope19:59
hatchthe GUI explicitly prohibits that interaction19:59
lazyPwrwhy?19:59
lazyPwrseems....arbitrary19:59
hatchmy guess, a limitation in Juju 1?19:59
lazyPwrkidna like not letting me unrelate a subordinate :P19:59
lazyPwryeah, you're probably right19:59
hatchor from PyJuju even?19:59
lazyPwrjuju1 had fun quirks like that19:59
hatchyeah19:59
hatchok thanks19:59
* hatch creates a model on jujucharms.com to test for sure20:00
stormmorelazyPwr, yeah I would love to go to a "charmer summit" but I don't see another one setup yet20:00
lazyPwrstormmore: i dont think we'll get it scheduled until mid spring.  jcastro might have more details as to when the next summit will be however20:01
jcastrowe haven't really talked about it20:02
magicaltroutsomewhere hot20:02
stormmoreand of course finance want to know like yesterday :-/20:05
stormmorelazyPwr, fyi I think the better question is whether you guys want to suffer the pain of meeting me ;-)20:11
magicaltroutany idea how to debug a 504 on the ingress router, no kubernetes dashboard etc lazyPwr ?20:12
stormmore@jcastro, I will look forward to hearing about when you do have those discussions20:22
jcastro\o/20:35
=== menn0-afk is now known as menn0
=== _thumper_ is now known as thumper
skayskayhey, trying to remove a unit that is in an error state for the config-changed hook doesn't work, as far as I can tell21:04
skayskaythere's ab ug about a failing upgrade state that already exists, maybe this is related21:05
skayskayoh, this may be something else. lp:1671476 is about destroying a model21:07
skayskayI'm unable to remove a unit or application21:09
magicaltroutyou need to mark the unit resolved first skayskay21:10
magicaltroutjuju resolved unit/0 --no-retry21:10
skayskaymagicaltrout: thanks! that's it. I didn't know about that --no-retry option. handy21:11
firlhello all; anyone have an example bundle of openstack using network spaces ?21:18
magicaltroutoooh shiugar21:22
magicaltroutsooo lazyPwr i'm not convinced that each k8s worker should be on its own flannel subnet, am I right?21:22
stormmorethis is really odd, having it hang during fetching juju agent21:25
stormmoreI suspect a network issue but I can't log into the instance using the key that I added to the MaaS user! hmmmm21:26
lazyPwrmagicaltrout: why not?21:28
magicaltroutokay in that case i'm just wrong :)21:29
magicaltrouti assumed they had to share a subnet21:29
* magicaltrout returns to wondering why they aren't working21:30
stormmoremagicaltrout, no each worker needs it's own subnet to manage it's containers with21:30
magicaltroutfair enough21:30
magicaltrouti'm spinning one up on aws for comparison, but i assumed they'd be on the same subnet. Obviously not :)21:30
stormmoreanyone have an idea where to look when I can enlist and commission nodes in maas but I can't bootstrap juju?21:33
rick_hstormmore: juju bootstrap --debug and then check the maas logs during bootstrap.21:42
stormmorerick_h, thanks, I keep forgetting about that. building a "clean" environment to try again21:44
zeestratfirl: The #openstack-charm people have a bundle in their dev repo: https://github.com/openstack-charmers/openstack-bundles/blob/master/development/openstack-base-spaces/bundle.yaml21:49
firlzeestrat thanks!21:49
zeestratfirl: There's a OpenStack HA bundle laying around using networks defined in config (not the new juju network bindings): https://launchpadlibrarian.net/298175262/bundle.yaml21:50
firlinteresting21:50
firlI am trying to figure out the best way to do the networking I need to, and I just finished configuring all of the physical net, so trying to make sure I have MAAS setup the way I Want to deploy the bundle21:51
firlit seems like “spaces” is where the bundles are going21:52
firlcharms rather21:52
zeestratfirl: I recommend checking out #openstack-charm channel as well. I'm working on a HA bundle with spaces if you're interested. Send me a pm and I can get back to you21:53
firlI will jump on that channel too21:53
firlhrmm no one in that one.21:54
zeestratfirl: sorry, #openstack-charms21:54
firlperfect21:54
zeestratthere are also some docs on https://docs.openstack.org/developer/charm-guide/ with release notes for the latest stable releases of the openstack charms21:55
zeestratI'm off for now, but pm me and I can get back to you21:56
firlthanks21:56
stormmorerick_h, http://paste.ubuntu.com/24179043/ shows the output from --debug, I am not seeing anything obvious in the regiond.log, rackd.log or the instance messages log to show why it isn't bootstrapping :-/22:07
stormmorerick_h, but this time I was able to log in, apparently I am missing a default gateway22:10
stormmorerick_h, which seem odd considering it did a apt update / apt dist-upgrade22:11
stormmoreone problem down, no telling how many to go :-/22:22
stormmoregotta love weird networking issues22:29

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