| lazypower|travel | firl yeah :( | 02:38 |
|---|---|---|
| firl | lazypower|travel: gotcha, is there a benefit to doing it this way over having k8s bootstrap the env itself? | 04:09 |
| lazypower|travel | The flannel networking is a bolt on for cross host communication. The charm itself does deliver a k8s bootstrapped cluster | 04:09 |
| lazypower|travel | we're leveraging hyperkube to standup the cluster, so we're closer in alignment with their reference arch | 04:10 |
| lazypower|travel | firl - unless i completely missed the questions intent.... | 04:11 |
| firl | http://kubernetes.io/v1.1/docs/getting-started-guides/juju.html | 04:11 |
| lazypower|travel | which is possible, its 5am | 04:11 |
| firl | hah yeah gotta love time zones | 04:11 |
| lazypower|travel | firl - ah yeah, dont trust that document :) thats in reference to our older charm work where we were delivering k8's entirely via CM | 04:12 |
| firl | hah kk | 04:12 |
| lazypower|travel | it was klunky to say the least, but it was an important evolutionary step in our understanding of their stack | 04:12 |
| lazypower|travel | thats actually a prime topic in my FOSDEM track today | 04:12 |
| firl | gotcha | 04:12 |
| firl | too bad I couldn’t come haha | 04:12 |
| firl | So I should wait until monday? will it get pushed to the charm store | 04:13 |
| lazypower|travel | it'll be recorded, and since we're buds, i'll do a special after-session for ya if you're interested :) | 04:13 |
| firl | or just fixed so I can deploy the bundle with charm build layer | 04:13 |
| firl | It’d be cool to get a better understanding | 04:13 |
| firl | I am going through bulletproofmeteor and they are recommending kubernetes | 04:13 |
| lazypower|travel | yeah, what I'll do is after FOSDEM lets out and I get settled in Gent i'll dive back into fixing that stilly bug. | 04:13 |
| firl | and since the meteor charm is broke, I figured why not | 04:13 |
| lazypower|travel | i can ping you here or via email once i've got a fix proposed, or you can star the layer-k8s repo | 04:14 |
| lazypower|travel | as I gate all that work through mbruzek | 04:14 |
| firl | celpa.firl@gmail.com | 04:14 |
| firl | ( I will star the github also ) | 04:14 |
| lazypower|travel | awesome. I'll reach out when i've got the fix in place for the flannel containers :) | 04:14 |
| firl | I have a build node all set aside for it | 04:14 |
| lazypower|travel | just for good measure | 04:14 |
| firl | I can at least smoke test it for ya | 04:15 |
| firl | since I replicated it | 04:15 |
| lazypower|travel | <3 really appreciate that | 04:15 |
| firl | so I should just do a single docker node for now | 04:15 |
| lazypower|travel | sure, actually if you remove 'layer:k8s' from the layer.yaml | 04:15 |
| lazypower|travel | rebuild and deploy with a single k8s node + single etcd service | 04:15 |
| lazypower|travel | you should be in like flynn | 04:16 |
| lazypower|travel | sorry, remove 'layer:flannel' | 04:16 |
| lazypower|travel | and you can even scale that, you just wont get distributed pods working. the scheduler is intelligent enough to know this in my testing | 04:16 |
| firl | lol gotcha I was like … yeah it’s not there | 04:16 |
| firl | ok | 04:16 |
| firl | I will do that for now and see how it goes | 04:16 |
| firl | then once it’s ready I can add the overlay networking | 04:16 |
| lazypower|travel | yep! | 04:16 |
| lazypower|travel | in-place upgrade should take care of that missing component | 04:17 |
| firl | any DTR charms you recommend | 04:17 |
| lazypower|travel | whats DTR stand for again? | 04:17 |
| firl | docker trusted registry | 04:17 |
| lazypower|travel | oh! | 04:17 |
| firl | ( to use outside of kuber ) | 04:17 |
| firl | for it to reference | 04:17 |
| lazypower|travel | I started on, but haven't finished it yet, we spiked on TLS support instead of the registry | 04:18 |
| firl | gotcha | 04:18 |
| lazypower|travel | with that being said, I can see hvaing a docker distribution charm in the next 30 days or so | 04:18 |
| lazypower|travel | if you're feeling spunky, i can get you early access there as well | 04:18 |
| firl | yeah, I don’t mind testing/contributing | 04:18 |
| firl | all of my charms currently are private only repo’s | 04:19 |
| firl | I also haven’t written anything for 1.25.3 | 04:19 |
| firl | so status/update/blocking is still a foreign concept | 04:19 |
| lazypower|travel | well, 2.0-alpha1 is coming really soon | 04:19 |
| firl | ( for dev that is ) | 04:19 |
| lazypower|travel | so be prepared for nomenclature changes, and even more awesome | 04:19 |
| firl | haha | 04:19 |
| firl | yeah running trusty-liberty now | 04:19 |
| lazypower|travel | as in single controller - many models (thats right, one state server for many environments) | 04:20 |
| firl | nice | 04:20 |
| lazypower|travel | and thats just the tip of the iceberg :D | 04:20 |
| firl | ya, i’m a fan of it | 04:21 |
| firl | have fun at the FOSDEM, I will try to deploy the bundle without flannel now | 04:21 |
| lazypower|travel | firl - thanks :) feel free to reach out if you encounter any further issues. I'm happy to lend a hand. And I really appreciate the testing/patience while we iron out our next major release of the charms | 04:22 |
| firl | hah yeah, it’s been a bumpy ride. It’s nice though to have configuration around the environments in a private cloud | 04:23 |
| nagyz | firl, so there was a maas 1.9 bonding + juju bug but it should be fixed in .3 | 09:45 |
| bdx_ghent | yoyoyo | 10:48 |
| bdx_ghent | ghent-charmers: what hotel are we in? | 10:48 |
| icey | is it possible to set a charm config from within an action? | 11:31 |
| firl | lazypower|travel: if you messaged me I missed it | 21:08 |
| firl | I saw a notification but the scroll history buffer is not big enough to show me what it was | 21:08 |
| lazypower|travel | firl - nope but here's a repost - nagyz firl, so there was a maas 1.9 bonding + juju bug but it should be fixed in .3 | 22:12 |
| firl | hah, k | 22:12 |
| firl | lazypower|travel: I am still on for tomorrow for setting up the cluster let me know when you want me to test it | 22:12 |
| firl | If I can get it, will deploy over maas and openstack | 22:13 |
| lazypower|travel | firl - will do. I'm still preoccupied with prep for the charmer summit, but for sure I'll be hacking on that regression | 22:13 |
| lazypower|travel | looking like its going to be first up tomorrow morning unless i get completely shanghaid | 22:14 |
| firl | no worries, I can do tuesday too if that’s easier. no worries on my end | 22:14 |
| lazypower|travel | Ok, lets shoot for that so i have some breathing room :) | 22:14 |
| * lazypower|travel adjusts the todo due-date | 22:14 | |
| firl | haha k | 22:15 |
| firl | just realized I was on the http://summit.juju.solutions/ website lol | 22:15 |
| lazypower|travel | :) Yep! | 22:17 |
| * lazypower|travel chants "one of us, one of us" | 22:17 | |
| firl | haha | 22:18 |
| nagyz | lazypower|travel, yeah but it's not :( | 22:29 |
| nagyz | lazypower|travel, I've been trying with .3 yesterday as well | 22:29 |
| firl | nagyz at least you have something to track though | 22:32 |
| nagyz | should I reopen the bug? | 22:32 |
| lazypower|travel | nagyz - link to the bug? | 22:34 |
| === lazypower|travel is now known as lazypower|summit | ||
| nagyz | I think this is the one that firl mentioned: https://bugs.launchpad.net/juju-core/+bug/1516891 | 22:52 |
| mup | Bug #1516891: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:Fix Released by frobware> <juju-core 1.25:Fix Released by frobware> <MAAS:Invalid> <https://launchpad.net/bugs/1516891> | 22:52 |
| nagyz | but my bug is that SOMETIMES it has some weird error. | 22:53 |
| nagyz | 50/50 :) | 22:53 |
| lazypower|summit | :-/ hrm | 22:55 |
| lazypower|summit | yeah, if you have logs/data to back up the hinky behavior, it'll go a long way to re-open the bug with logs | 22:55 |
| nagyz | I've posted the pastebin yesterday - do you have logs or shall I relink them? | 22:56 |
| lazypower|summit | nagyz - same output contained in comment #19? https://bugs.launchpad.net/juju-core/+bug/1516891/comments/19 | 23:01 |
| mup | Bug #1516891: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:Fix Released by frobware> <juju-core 1.25:Fix Released by frobware> <MAAS:Invalid> <https://launchpad.net/bugs/1516891> | 23:01 |
| nagyz | I don't run VLANs | 23:02 |
| lazypower|summit | ok, yeah - i would most def attach the logs and at bare minimum poke the bug | 23:05 |
| nagyz | the thing is it's not that it misconfigures the interface | 23:07 |
| nagyz | it's just.. something. I have no idea what. I can ssh to the node and whatnot. | 23:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!