[01:18] I am trying to deploy my charms and I find that the machine creation itself has not succeeded [01:18] it is showing the 'pending' state [01:18] How do I debug this problem? [01:19] What can be the issue? [01:19] MAAS2.0 UI shows that the status of the machine is 'Deployed' [01:20] MACHINE STATE DNS INS-ID SERIES AZ 0 pending 192.168.1.252 4y3hkh trusty default [01:21] The above state is there for hours [01:21] Any help to debug this is much appreciated [01:38] hey I'm having an issue with conjure-up on xenial. I have 5 machines allocated for MAAS (1) and Openstack (4). Maas works great and I can conjure-openstack, but im having an issue with it wanting another host and there isnt one for neutron. Do I need 5 openstack machines, instead of the 4 the previous one could work with? [01:42] http://pastebin.com/ZfDciFgM [01:42] bildz: so 1 machine is always created for the 'controller' or 'juju admin' node [01:42] so if the bundle requires 5 machines that means you need at least 6 [01:43] I'm assuming thats the bundle requirement [01:44] bildz: yea [01:45] stokachu: where would i have read that? [01:46] I can barely find install information for 2.0-rc1 [01:46] bildz: jujucharms.com [01:47] we use https://jujucharms.com/openstack-base/ for conjure-up [01:47] juju docs https://jujucharms.com/docs/stable/getting-started [01:47] thank you [01:48] thankfully, i have another to get me through the install, but i've been playing around with the cli commands and am getting familiar with managing the deployment [01:48] :) === thumper is now known as thumper-dogwalk === scuttlemonkey is now known as scuttle|afk === thumper-dogwalk is now known as thumper-coffee === thumper-coffee is now known as thumper === saibarspeis is now known as saibarAuei === saibarAuei is now known as saibarspeis === saibarspeis is now known as saibarAuei === aluria` is now known as aluria [07:07] can somebody help me with container stuck in error/pending state? [07:08] i have machine which hosting kvm container (this juju says) so i want to remove role from this server [07:08] how to do that? how to fix services on the host machine which is in broken state? [07:22] juju resolved, but if you want it retry the last hook use juju resolved -r then the name [07:22] KpuCko: ^^ [07:23] spaok http://pastebin.com/BBkFtA4D [07:23] i don't know anythink for this machine: 11 [07:23] how to recognize it? [07:25] so, typically that happens when you run a add or deploy command it didn't match one of the other nodes [07:25] it's trying to add a new one [07:25] you can juju remove-machine 11 --force [07:26] mhm, command runs fine, but result is the same [07:27] oh sorry, i have to wait some time after im running juju status again [07:27] ya [07:27] its a queue like system [07:27] thanks a lot [07:27] np, that happens a lot :) [07:28] if your testing stuff, using --to against one of your machine ID's will help [07:29] yeah, yeah im working with juju gui [07:30] but i'm trying to learn how to debug hooks [07:30] how to fix them, etc [07:30] many thanks for the help === Guest60664 is now known as cyberjacob [08:53] alrighty, signed off to talk Juju at Pentaho Community event this year.... better sort out some more travel [09:34] does anyone know a charm that uses the current python-basic template? trying to get a feel for writing a charm [09:38] there is a python basic template? [09:38] what you looking at spaok ? [09:39] Hi, I am very new to Juju. I was following https://www.stgraber.org/2016/06/06/lxd-2-0-lxd-and-juju-1012/ and I am getting an error when bootstrapping controller [09:39] test@lxd:~$ sudo apt install juju [09:39] [sudo] password for test: [09:39] Reading package lists... Done [09:39] Building dependency tree [09:39] Reading state information... Done [09:39] The following additional packages will be installed: [09:39] distro-info juju-2.0 [09:40] magicaltrout: its part of the charm create command [09:41] marosg: that should work, that's the error? [09:42] This post assumes that you already have LXD 2.0 installed [09:42] you got that? [09:42] yes, LXD is working [09:42] there's a bug with images, not sure if they fixed it [09:42] might be that [09:43] try sudo lxc image copy ubuntu:16.04 local: --alias ubuntu-xenial [09:44] ah just the default stuff spaok ? [09:44] most charms start with it [09:44] I've got some basic-ish stuff kicking around hold on [09:44] ya, just reading about the services framework [09:45] be nice to see a current example [09:45] https://github.com/buggtb/layer-mesos-master/blob/master/reactive/layer_mesos.py [09:45] thats a simple one [09:45] cool, thanks [09:46] https://github.com/buggtb/layer-drillbit/blob/master/reactive/drillbit.py [09:46] there's a slightly more complex or messy one [09:46] depending how you look at it ;) [09:48] spaok, thanks, looks like it did the trick [09:48] marosg: np, I ran into that one also, I just pull the image now as ubuntu-xenial as part of my deployments [10:10] spaok: you need to update your version of charm [10:10] python-basic isn't the best template, python-reactive is [10:11] ok [10:11] spaok: if you `sudo add-apt-repository ppa:juju/stable` and upgrade charm and charm-tools you'll get a better experience [10:12] ah that explains my confusion [10:12] * magicaltrout didn't use python pre reactive [10:13] I looked at https://jujucharms.com/docs/stable/tools-charm-tools [10:13] and http://pythonhosted.org/charmhelpers/getting-started.html [10:13] read 2.0 docs [10:13] they are [10:13] fail [10:14] hah, ya, I've had a lot of problems with things in 2.0 docs [10:15] s/fail/in progress/ :P [10:15] fair enough [10:16] sorry i was referring to my comment [10:16] not the docs [10:16] as I said read 2.0 without clicking the link as I read stable :) [10:16] said/read [10:16] ya, the ones I was looking at don't really change between stable and dev [10:17] coffee clearly didn't have the desired effect this morning [10:17] heh, its 3am here [10:17] yeah i don't think charm build has changed much if at all [10:17] west coaster [10:17] yar [10:17] where abouts? [10:17] san jose [10:18] heart of silicon valley pretty much [10:18] ah very nice [10:18] took a drive up that way when I was out in Pasadena last week [10:18] nice [10:19] some nice beach roads [10:19] indeed [10:19] nice part of the world [10:20] this current? [10:20] charm 2.2.0-0ubuntu1~ubuntu16.04.1~ppa2 [10:20] charm-tools 2.1.4 [10:21] cause no template found for python-reactive [10:21] more current than mine [10:21] don't you just run "charm create"? [10:22] wasn't sure, I saw different things about using -t python, or -t python-basic [10:22] I can create it [10:22] na [10:22] s/create/try/ [10:22] charm create mycharm [10:22] then i see [10:22] INFO: Using default charm template (reactive-python). To select a different template, use the -t option. [10:22] which is what you want [10:23] kk, ya [10:23] ok, now to figure out how to populate it [10:23] before you build it [10:23] make sure you have the environment vars set [10:23] else you'll end up build stuff wonky [10:24] JUJU_REPOSITORY etc [10:24] for local repo? [10:24] yeah it'll stomp on your charm if you aren't careful [10:24] ok [10:24] you have to build before deploying or pushing to the charmstore [10:25] so JUJU_REPOSITORY INFERFACE_PATH and LAYER_PATH [10:25] need setting [10:25] cd [10:29] ok, I'm going to mess with this some more in the day light, thanks for the help magicaltrout and marcoceppi, gives me a good starting place [10:29] no problem [10:29] swing back round in the afternoon and more clued up people are around [12:30] hello [12:30] if I shutdown physical mahcines on which i have juju units as LXDs, when I boot up the machines again, the LXDs should come up themselves, right? [12:32] I don't believe that is the case although I've never tried [12:36] MrDan: they should [12:38] * marcoceppi powers off a node in maas to test [12:39] MrDan: yes, they should come back up [12:39] MrDan: I do it on my laptop all the time, but not tried it on a maas server [12:48] booo i'm 0 for 2 today [12:48] someone else the other day said theirs weren't coming back up [12:49] magicaltrout: it could be a bug [12:49] surely not? [12:49] but the agent should bring back not just the workload on the machine, but also the containers (if any) [12:50] +1, definitely it should [12:50] fair enough [12:50] sounds sensible ;) [12:51] i'm still waiting for my kickstarter stuff to finally have a way to test MAAS properly [12:51] looking forward to it [12:52] kickstarter stuff? [12:52] http://www.udoo.org/udoo-x86/ [12:52] bought a bunch of these [12:53] altough they now have 32GB ram not 8 [12:54] if they arrive before i'm due to demo Juju at the Pentaho meetup this year I'm gonna take them and do a "MAAS" big data deployment [12:54] ah nice [12:54] Cool stuff. Do they have some sort of management interface so they can be managed by MAAS? [12:55] you mean powerwise zeestrat ? [12:55] magicaltrout: Yes. [12:56] dunno, good question [12:56] Hi, testing now beta18 for the neutron-gateway issues [12:57] the maas docs are a bit of a black hole [12:57] MrDan: k, the team's landing that fix today for the rc2 tomorrow as well so please watch for that to help you get back to rc [12:59] looks like there might be ipmi support zeestrat [13:00] magicaltrout zeestrat if there's IMPI it'll work for sure with maas [13:00] magicaltrout: Then you are probably good to go. The MAAS docs aren't too bad. There's a list of power driver capabilities here: http://maas.io/docs/manage-power [13:00] yeah [13:00] magicaltrout: I know a guy who built a BMC with an arduino for raspberry pis. A lightweight restful api that would power on one of the GPIO pins to turn on or off an RPI [13:00] the problem with the docs is where they land on google [13:00] they don't seem to get indexed [13:01] magicaltrout: yeah, getting google juice has always been...a struggle for us on some of our properties [13:01] magicaltrout: I gave up googling and just go to the source, or use `site:jujucharms.com` or `site:maas.io` [13:02] maas.io is pretty new compared to maas.ubuntu.com [13:02] yeah but you google maas and you end up at maas.ubuntu.com but then maas.io is listed lower down but only the landing page [13:02] which is weird [13:03] anyway.... yeah these boards have an arduino built into them which is pretty crazy [13:03] interesting to see what you can do with an X86 board with an Arduino 101 on them [13:03] rick_h: it works, the neturon gateway services are installed [13:04] MrDan: cool, hope that unblocks you until rc2. [13:04] yep [13:04] tomorrow rc2 is out on ppa? [13:04] MrDan: yes, that's the plan [13:05] cool [13:24] Hi. We developed a "cinder storage driver" charm. In this charm we are using "subordinateconfigcontext" to pass configuration values to cinder.conf. [I mean to modify the cinder.conf charm]. we followed https://github.com/openstack/charm-cinder/blob/master/templates/mitaka/cinder.conf [13:26] marcoceppi: did we have the ability to list/etc plugins before? I don't see it in the command lists but curious how we missed this when doing the cli stuff [13:26] rick_h_: `juju-1.0 help plugins` [13:27] rick_h_: it was a help topic, but I don't see why it wouldn't be list-plugins today [13:28] Similary, Using the same charm we need to modify the nova.conf. We need to add use_multipath_option: true/false. [13:28] marcoceppi: gotcha, ok yea. I was trying to see why we didn't have any plugin based commands make it into the new cli planning [13:28] marcoceppi: but if it was under help we probably just missed it [13:29] rock: there is a way to do that without modifying the nova charm, but I don't remember what that is [13:29] rick_h_: I can build a `juju list-plugins` plugin, but it won't show up in help ;) [13:29] marcoceppi: lol yea [13:29] rick_h_: which brings up an interesting point [13:29] should `help commands` show plugins as well ;) [13:30] marcoceppi: yea, replying to your email thinking that through [13:30] rick_h_: cool, thanks [13:30] marcoceppi: if plugins is a noun in the juju-verse...what all does that mean. [13:30] you can list-plugins or `juju plugins` which are aliases [13:30] list, show, add/remove is done automatically via install. What's the command to get to a list of available plugins to install? [13:30] but I wonder about register-plugin [13:30] marcoceppi: that kind of stuff [13:30] where you whitelist the plugin so it shows up in commands [13:31] marcoceppi: hmm, not sure about that one [13:31] but that's a feature, listing plugins is parity [13:31] well, add-plugin, probably not register-plugin [13:31] fwiw, plugins still work [13:31] marcoceppi: yea, tbh as a whole this will have to fall into a 2.0.1 atm [13:31] pfft, PATCH RELEASE? [13:31] marcoceppi: exactly, we've got bugs of things that don't work that we need to get fixed for GA with it coming down to rc2 tomorrow and then a little gap for GA [13:31] jk, that sounds good [13:32] marcoceppi: so will file a bug and link it in my email reply [13:32] ta [13:32] rick_h_: I made sure to cc the -dev list ;) [13:32] marcoceppi: OK. I have a question. To modify nova.conf we are trying to use https://github.com/openstack/charm-nova-compute/blob/master/templates/mitaka/nova.conf. [13:33] rock: I imagine #openstack-charms would be a better room, a lot of good openstack charm knowledge there [13:33] marcoceppi: OK. Thank you. === rye is now known as ryebot [14:35] tvansteenburgh: I know I asked this recently, but wrt python-jujuclient, can we get a new release with the 2.0 rc1 support? A PPA won't work, in this case, because it's being run from fedora [14:36] aisrael: i'll do that now [14:36] tvansteenburgh: thanks! [14:41] aisrael: uploaded [14:41] (v0.53.3) [14:41] excellent, thanks! [15:04] hey rick_h_, if i add a user to my controller, and grant that person (let's call him tvansteenburgh) 'write' privileges to a model, should he be able to 'juju ssh X' into units of that model? [15:05] kwmonroe: you'll need to add his ssh key [15:05] kwmonroe: see juju add-ssh-key and such [15:05] kwmonroe: since he's not admin he can't manage keys and without a key, no access [15:06] add-ssh-key?!?!? rick_h_, you're the best. i didn't know of such sorcery. [15:06] kwmonroe: let me know how it goes === natefinch is now known as natefinch-afk [15:23] hi. Can I provide --resource foo=bar when deploying a bundle? how will it know what application it is for? [15:29] pascalmazon: sorry, bundles currently only support resources from the charmstore [15:29] pascalmazon: as you note, the bundle deployment scenario is a bit more complicated and was pushed past rev1 atm [15:31] rick_h: ok, thanks for the info! === natefinch-afk is now known as natefinch [16:18] hey beisner, suchvenu emailed mbruzek and i with some questions about the cinder charm (stuff like cinder for Z and cinder in lxd). who is the best contact for those? or would it be better to ask on the juju ML? [16:30] (stand down beisner ^^; we got the routing sorted) [17:33] woot thx kwmonroe === dpm is now known as dpm-afk [18:10] rick_h_: is there any way to tell `juju ssh` which key to offer? [18:12] tvansteenburgh: hmm, with juju scp you can specify args to the underlying scp functionality with a --, but I think we redid juju ssh in a OS agnostic way. [18:13] tvansteenburgh: so honestly not sure, will have to ask around/look and see if I can see anything in the code [18:14] rick_h_: ok. right now i'm in a situation where i have to rename my keys to get juju ssh to work [18:15] rick_h_: should i file a bug about that [18:15] ? [18:15] tvansteenburgh: yes please. Will see if there's a flag that's just not in help/etc [18:15] rick_h_: roger, thanks [18:16] mgz: around? you were just in ssh-key land recently. any ideas on ^ [18:23] tvansteenburgh: looking at https://goo.gl/0q2KWq [18:23] tvansteenburgh: looks like not supported :( [18:25] rick_h_: ack, thanks for looking [18:28] bdx_: heads up, comment/etc coming in on https://bugs.launchpad.net/juju/+bug/1627554 [18:28] Bug #1627554: juju binary broken on sierra [18:28] bdx_: let me know if you're up for seeing it through or want to punt. [18:50] Hi, i'm getting error 'ERROR unrecognized command:' for charm publish command. any idea? [18:51] charm * packages version: http://paste.ubuntu.com/23247897/ [18:59] junaidali: the command changed to charm release [19:00] thanks lazyPower. I missed the latest update [19:12] lazyPower junaidali I'm adding a silent plugin to the next charm snap, where charm publish is just an alias to charm release [19:29] wait what, is the next charm tools command for publishing changing? [19:31] we've got automation on that, will need to know when that will affect stable users (deb) [19:40] lazyPower, congrats on getting kubernetes enterprise support ready! [19:41] I had a question around it when you get a moment [19:41] firl: sure, i'm in/out but whats up? [19:42] I saw the kibana / es / filebeat configuration with kube, awesome! [19:42] is there a way to expose services yet like gce? [19:44] firl: we ship with an nginx reverse proxy, there's a demo action of microbots [19:44] it has limited support for sockets, i'm still working to make that easier [19:44] gotcha, I remember that being an issue [19:44] i want to add an action that will let you pick from pre-configured ingress LB's and specify a namespace and it "just works" after that [19:44] Gotcha, yes that would be wonderful [19:45] are there daily builds available for juju 1.25? [19:45] so we're 1/2 way there with whats in there :) [19:45] yeah, sounds awesome [19:45] gQuigs: not daily, 2.0 is what would be in daily [19:45] firl: i'm highly interested in your return feedback this go around, please capture it for us [19:45] yeah, I will try it out in Openstack [19:45] firl: if there's *anything* yinz need over there in the short term beta cycle, i want to get that captured. [19:45] I am considering if I need to try it on bare metal [19:45] well your networking will be pokey [19:46] lazyPower: right, but 1.25 is still maintained and I'd like to try a fix that's committed but not released [19:46] overlay in an overlay and all that [19:46] do I need juju 2 for it? [19:46] yeah the docker config would need to have 1404 mtu [19:46] firl: yeah, i def need that feedback of your network findings when deployed in openstack [19:46] i'm probably going to have to expose some of the guts of the container rumtime for configuration there [19:46] cool. I have a few nodes to test it in [19:47] whats the repo / guide again to get it going and I will try to test it this week [19:47] gQuigs: ah good point, try checking in #juju-dev [19:47] firl: the readme - jujucharms.com/canonical-kubernetes [19:47] will do, thanks [19:49] lazyPower perfect, I will try it with an openstack overlay. If it’s working enough I might put it on a couple bare metal machines. [19:50] does nodeport work through the juju overlay also? [19:50] or do i have to do a nginx reverse [19:52] lazyPower: hey there [19:52] if you want to do nodeport, you'll need to manually open the ports for now [19:52] any worker can perform as a reverse proxy for both nodeport and for ingress [19:52] thumper: yo [19:55] firl: but our recommendation is to use the ingress controller so its encapsulated. for the workdloads that demand nodeport, like a znc bouncer, we'll have to brianstorm and make that better [19:55] im just thinking through if i wanted to have socket support [19:55] but this is all awsome, nice job! [19:56] firl: https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx [19:56] its pretty extensive [19:56] i mean you can throw kubelego as a pod on the ingress and get free tls with letsencrypt [19:57] but thats the LB we shipped with for beta. it has the biggest portfolio of supported options without compromising support through advanced configuration. [19:57] yeah [19:57] currently I have an ssl secret with a single ssl proxy node that just acts as a termination point [19:57] just to get ssl so that might be a nice change of pace [19:58] lots of options [19:58] ya, I will have to get a juju 2.0 environment working and test it out [20:11] lazyPower: how often do you refresh your boot2docker/docker-machine? my charmbox is kernel panic'ing more frequently these days, and i realize i haven't updated since 1.11.2 [20:40] lazyPower: is it me, or does the demo button here not work? https://jujucharms.com/canonical-kubernetes/ [20:41] lazyPower: I presume it's supposed to bring up the demo page with canonical-kubernetes deploying/deployed, right? for me it just brings up an empty demo window [20:41] lazyPower: it says "fetching bundle data" but then... nothing [20:43] natefinch: known issue, gui team is updating the gui to make it work [20:47] rick_h_: ahh, good to know. Sucks that it happened after the announcement [20:48] natefinch: yea === natefinch is now known as natefinch-afk [21:52] Congratulations, and welcome to Apache: Big Data Europe! Your submission, "Highly Scalable Big Data Analytics with Apache Drill", has been accepted [21:52] Seville here I come [21:53] kwmonroe we have some interesting shit to work on [21:53] sorry stuff [21:53] not allowed to swear [21:56] right on magicaltrout! i've always wanted to do Highly Scalable Big Data Analytics with Apache Drill ;) [22:01] meh [22:01] i detect irony [22:01] well I can crack out the Big Top Stuff, Drill Stuff [22:01] at ApacheCon [22:02] I suspect it'll go down reasonably well and give me an excuse to have that upstream discussion [22:05] magicaltrout: do you know if there's any work behind https://issues.apache.org/jira/browse/BIGTOP-2001? it hasn't been updated in forever :/ [22:06] and from the drill side, even more foreverer: https://issues.apache.org/jira/browse/DRILL-114 [22:06] they both seem like odd requests [22:07] which is why they're probably both open [22:07] i'm guessing they're requests for bigtop to take over drill builds (or at least pin build versions for a particular bigtop release) [22:08] hmm, yeah but you can run Drill over anything in HDFS, Hive or HBase [22:08] its not vendor specific [22:10] at the summit, we talked about a hackathon with bigtop (c0s, specifically). when that happens, i'll see if there is any movement in bringing drill under the bigtop umbrella. [22:13] I don't see that happening [22:13] MapR have their claws in Drill [22:14] I also don't see the benifit but thats neither here nor there [22:14] especially as drill queries a bunch of non hadoop stuff [22:50] magicaltrout: is there a list of layers or interfaces you can use? [22:51] indeed spaok [22:51] interfaces.juju.solutions [22:52] interesting [22:52] thanks [22:56] magicaltrout: sorry to bug ya, just wondering, if I want to write an interface, do I just make something in charms/interfaces? not sure the difference between charms/interfaces and charms/deps/interface [23:00] no worries spaok i'm just trying to figure out where 150GB of non backedup science data has gone :) [23:00] yeah you just put it into charms/interfaces [23:00] no magic required there [23:06] spaok: https://jujucharms.com/docs/stable/developer-layers-interfaces [23:07] lazyPower: thanks [23:08] https://jujucharms.com/docs/devel/developer-layer-example [23:08] had a link to https://jujucharms.com/docs/devel/charms-layers-interfaces/ [23:08] which is 4040 [23:08] s/4040/404/ [23:15] spaok: thanks for reporting that https://github.com/juju/docs/pull/1411