/srv/irclogs.ubuntu.com/2017/05/23/#juju.txt

lazyPowerthumper: what is the namenode charm?03:26
lazyPowerthumper: you're using big data terminology here...03:26
thumperlazyPower: oh hai03:26
thumperI was watching a deployment and noticed that it failed to install every time03:26
lazyPowerthumper: the kubernetes-master charm?03:27
thumperi think it was a custom bundle03:27
thumperused to scale testing03:27
thumperon aws03:27
lazyPowerhmm, ok03:27
lazyPoweri'm not sure what this namenode charm would be. it might be something kwmonroe has cooking up03:27
thumperthat's fine03:31
thumperI have enough issues to chase just now :)03:32
ZicoMattyw_, GM, thank you for your earlier reply. It works, I just added the layer.yaml containing (includes layer:metrics) and metrics.yaml containing (metrics: juju-units:) and upgraded the charms as "juju upgrade-charm <charm_id> --path <local/path/to/charm>" and after 5 minutes, juju metrics --all, Gives the number of units for all the charms like a CHARM :)07:22
=== frankban|afk is now known as frankban
mattywZico, glad it worked out, if you think there's improvements to be made with the docs I'd love to hear them.07:31
mattywZico, any any more questions feel free to ask - I'm here all the time, if I can't answer a question I'll be able to point you to someone who can07:32
ZicoMattyw, Great, thank you my friend, much appreciated :)07:32
ZicoMattyw, Concerning the docs improvement, yes, I think there is room for improvement, for example, compiling the steps that I mentioned to form a "HELLO_WORLD" Metric, I mean the unit count by enumerating the process as 1 , 2, 3, & 4 where 1. Layer.yaml, 2. metrics.yaml, 3. upgrade-charm, 4. After 5 minutes (Default), invoking the juju metrics command.07:35
ZicoThe Call for Upgrade-charm wasn't obvious unless you informed me to :)07:35
mattywZico, which pages did you read from the docs, was it just https://jujucharms.com/docs/stable/developer-metrics ?08:07
ZicoMattyw, yes, it was https://jujucharms.com/docs/stable/developer-metrics the starting page. But as you notice, there is no mention in it for " juju-units: " and no mention to trigger the "juju upgrade-charm"08:19
ZicoMattyw, Also, in the layer.yaml section, the word " includes " is not mentioned...08:20
ZicoPersonally, I added in the layer.yaml "     includes: ['layer:metrics']     "  as copied from a manually created TEST charm08:21
mattywZico, yeah, that page kind of assumes you know lots of stuff already, we probably need a better getting started page, how did you find out about charm metrics (just trying to understand where would be best for us to make a change in the docs)08:21
ZicoMattyw, Yes, Correct, in fact, I got frustrated at first :) because, I screened all the pages, and couldn't grasp a whole procedure. Starting point was: https://jujucharms.com/docs/stable/developer-metrics08:23
Zicothen went to https://jujucharms.com/docs/2.1/charms-metrics08:24
mattywZico, we have https://jujucharms.com/docs/stable/developer-getting-started. I guess that wasn't helpful?08:25
ZicoYes, Helpful of course, but doesn't read anything about the metrics. it would be nice to add a section to it to link to metrics08:27
mattywZico, understood, thanks very much for your feedback08:28
mattywZico, hopefully we'll make it easier for the next person :)08:28
ZicoMattyw, you are welcome, my friend, I hope so :) I am doing some research on Orchestration through JUJU and I need to get feedbacks (Metrics) to trigger optimization08:29
ZicoBTW, I have a problem that is: My Laptop is able to spin multiple machine and provision multiple services, however, when I run a large bundle , it arrives to a time that It dies (Sluggish responding), although free -h and top and iotop are reading low load! Any hint?08:31
mattywZico, sounds interesting, any questions or suggestions we're here to help/ listen08:32
mattywZic, you're running lxd I guess?08:32
mattywZico, ^^08:33
Zicoyes08:33
ZicoMattyw, 7 applications running on 4 machines (4 applications on 1 machine and remaining is 1 app per machine).08:33
ZicoMattyw, the 4 apps on 1 machines as 4 LXD08:34
kjackalGood morning Juju world!08:50
mattywkjackal, morning08:51
mattywZico, that means you'll probably have 5 lxd machines total including the controller08:51
mattywZico, doesn't suprise me that it might be a bit slow on your laptop08:52
ZicoMattyw, Correct.08:53
ZicoI have a new question please:08:53
ZicoI am struggling to make the PROXY SQUID_DEB_PROXY  HIT but all is miss :(08:54
ZicoI am following08:54
Zicohttps://askubuntu.com/questions/3503/best-way-to-cache-apt-downloads-on-a-lan08:54
Zicowritten by Jorje Castro08:54
ZicoAll I get is TCP_MISS not TCP_HIT :(08:56
ZicoAlthough, I remove the machine and recreate, so it's supposed to be cached08:56
ZiclazyPower: thanks for your reply (I just backlogged)09:37
Zic(hi Juju world)09:37
wpk /wind 1110:57
ZicoHi, how to purge (flush) historical logs, I mean JUJU debug-log --replay keeps tracks of several days back which are useless. Is it safe if I ssh the controller and empty the logsink.log by (ssh -m controller 0 and echo "" > /var/log/juju/logsink.log)?11:22
rick_hZico: since the logs are stored in the db that won't really work out.11:25
rick_hZico: there's tools in debug-log to help limit the time responded11:25
rick_hZico: check out https://jujucharms.com/docs/stable/troubleshooting-logs#the-debug-log-command11:26
ZicoRick_h, Yes, Right, thank you, I checked this, Much Helpful :)11:27
=== salmankhan1 is now known as salmankhan
ZicoHi, is there a way to forcibly remove a unit or an application without removing the underlying machine? (The "--force" is only application to remove-machine). This is the case when I get stuck with an app/unit with status ERROR and MESSAGE: *hook failed: "install"*12:13
Zicoapplication* shall read applicable :)12:14
ZicoBTW, removing it from the GUI (Destroy) says, this application is marked for destroy on next deploy. What's the catch?12:15
rick_hZico: no, there's not. If you force then there's no way for Juju to know what to remove as it doesn't track the files/installs/etc the charm does12:16
rick_hZico: is that you have to go down to the bottom-right and hit commit12:16
rick_hZico: where it'll try the same thing the cli does to remove an application, trigger the hooks, etc12:16
ZicoRick_h, yup, I commited of course :) and as result of commit, it says marked for destroy on next deploy12:17
rick_hZico: hmm, sounds like the GUI got confused?12:17
ZicoYup The exact wording is: (This application has been marked to be destroyed on next deployment.)12:18
Zicoand the status is (Status: error - hook failed: "install"  Agent Status: executing  Workload Status: error)12:19
ZicoSo, basically, I am stuck in infinite loop, neither the gui, nor the cli are able to remove the app/unit which is having status error (hook failed: install). The only way I could resort is by forcibly removing the underlying machine. My question is : Is there any other way to remove the app/unit without losing the machine?12:22
anrahZico: I think I have sometimes managed to resolve that by making dummy configuration change through cli and then say resolve to failed unit and after that remove-application12:26
ZicoAnrah, Good idea :), this is what I am thinking of. so, I go to $juju debug-hooks <app_name> and then what?12:28
anrahI just said juju config <app> <config-value>=foobar12:39
anrahthen juju resolve <unit>12:39
anrahjuju remove-application application12:39
anrahbut hmm, you have only one app per machine?12:40
ZicoAnrah, Yes Only one app, per machine currently.12:42
ZicoAnrah, I have done the trick (Y) , changed the config of passwd and then *resolved*, but again, hook failed: install and stuck at same position again and cannot remove the app.12:44
=== rvba` is now known as rvba
ZiclazyPower: can I deploy a specific bundle version through Juju GUI? because as I use manual-provisionning, I will need to redispatch charm to the "good" machine, and it's esasier with drag'n'drop if I need to demonstrate it to coworkers :)13:11
lazyPowerZic: yep just download teh bundle to your machine and drag/drop onto the gui13:12
Zichttps://localhost:8080/gui/u/admin/default/canonical-kubernetes/bundle/38 <= hmm, I thought to just edit that silly '38'13:12
Zicwill it work?13:12
Zicdrag'n'dropping from local is also good to know :)13:13
lazyPowerZic: you can view the specific revisin and choose deploy as well, sure13:15
lazyPower*revision13:15
Zicthanks, I'm impatient to upgrade this cluster in 1.7.2 to have the snap architecture13:16
Zic(the other one is already at latest revision)13:16
Zicmy next move will be to test if Juju and our Puppet orchestrator has some conflict on some files13:16
Zicwith snap, normally, all will be OK13:16
ZiclazyPower: before juju upgrade-charm, do you recommend upgrading the Juju client? we're not using the juju snap on the production cluster for now, I'm planning to switch to the snap version before/after the upgrade13:27
Zicdon't know if I choose before or after :>13:27
lazyPowerZic: as far as i know the snap package has very little to do with what you wind up with in your controller, as thats all packaged and maintained on the controller itself13:27
lazyPowerit'll only change how you receive your client package and client updates13:27
lazyPowerZic: but i would recommend the least-change method. introduce as few changes as possible, and slowly, so you can validate they haven't caused you any heartburn13:28
Zicyup13:28
ZiclazyPower: the kubernetes-master is stuck at "installing charm software" with no output at juju debug-log or in /var/log/juju of the kubernetes-master, where can I look to have more info? :(13:36
lazyPowerZic: thats the pre-dependency bootstrapping hook for reactive. the only thing i can think of would be to juju debug-hooks that unit, and kill the process executing the existing upgrade-charm hook13:37
lazyPowerthat way you can intercept it and run it manually13:37
Zicoh, did not know debug-hooks13:38
Zicpython3 /var/lib/juju/agents/unit-kubernetes-master-0/charm/hooks/install /var/lib/juju/agents/unit-kubernetes-master-0/charm/hooks/install13:38
Zickilling this one inside debug-hook ?13:38
Zicand relaunch it manually ?13:38
lazyPowerZic: yep, if you kill it, just wait a few seconds13:39
lazyPowerjuju will auto-retry the hook and trap it in that tmux session you have open13:39
Zicok13:39
Zickilled it 1min ago, it does not seem to respawn :(13:41
lazyPowerZic: juju resolved kubernetes-master/013:41
lazyPowerits likely on the backoff timer13:41
lazyPowerso resolving it will cause it to go ahead and retry13:41
ZicERROR unit "kubernetes-master/0" is not in an error state13:41
Zicit stuck at maintenance/executing in fact13:42
lazyPowerZic: systemctl restart jujud-unit-kubernetes-master-013:42
Zicon the juju controller machine right?13:42
lazyPowercycle the agent, that should kick it in the head13:42
lazyPowerno13:42
lazyPoweron the unit you're attached to for debug-hooks13:42
Zicah, on the kubernetes-master13:42
lazyPoweryep13:42
Zicoki13:42
lazyPowerjust to make things easier, if i dont explicity identify another unit, i'm referring to the unit you're attached to via debug-hooks.13:43
Zicit switched to error then back to maintenance/executing13:43
Zicok :)13:43
lazyPowerok, in your tmux session13:43
lazyPowerthere should be a new buffer open with the context listed13:43
lazyPower"upgrade-charm" for example13:43
Zicyep, I got the "This is a Juju debug-hooks tmux session."13:43
lazyPowerdo you see the hook listed in the tmux buffers?13:43
lazyPoweri forget if that message prints for every buffer or not13:44
lazyPoweri tend to just ignore that spam now :)13:44
lazyPowerok yeah, you're in the right context. i just trapped a hook to verify13:44
lazyPowerZic: from here, you can execute the hook manually, and attempt to gather more information. This buffer is loaded with all the juju env bits we set to make the agent operate13:45
Zicok, so I'm trying to launch the python3 script that I killed before, right?13:45
lazyPowerZic: so hooks/upgrade-charm if you're in the upgrade charm context. it may not give you an indicator as to whats actually happening, we scrape stdout from here to pipe to the logs.13:45
lazyPowerso if its just blank and hangs, time to start poking about to see if its network connectivity, or a locked apt daemon, or something similar13:46
Zicroot@mth-k8stestmaster-01:/var/lib/juju/agents/unit-kubernetes-master-0/charm# hooks/upgrade-charm <= I think I'm in the right context :)13:46
Zichttp://paste.ubuntu.com/24633743/13:47
Zicit does not output after that13:47
Zic(but does not return prompt either)13:48
lazyPowerZic: so it appears that its held up attempting to install the wheelhouse13:50
lazyPower:S i'm not sure what to recommend here, i haven't encountered reactive failing to bootstrap before13:51
lazyPowerand our resident reactive expert is out for Pycon13:51
Zicsame here :D it's the first time I encounter this issue13:51
lazyPowerZic: not an ideal solution, but can you bug this with the steps to reproduce and i can pass this along to cory when he's back from pycon?13:52
Zicif you weren't here, I would reboot the master with anger and expect it recaps the installation :D13:52
lazyPowerwell13:52
lazyPowerthats an option13:52
Zichuh :)13:52
Zictrying it \o/13:52
lazyPowerbut if its halting here, i dont necessarily think rebooting will help13:52
lazyPowerbut its worht a shot13:52
lazyPowergive it a go13:52
Zicin earlier time at my first try with Juju, I sometime rebooted the bad unit *and* the juju controller13:53
Zicsometime it recaps well13:53
Zicwas long time ago before joining here o/13:53
Zicoh, the upgrade-charm just gives me a traceback13:53
Zicmaybe because it receives the ACPI signal to reboot13:54
Zichttp://paste.ubuntu.com/24633780/13:54
Zicdon't know if it helps13:54
Zicunit-kubernetes-master-0: 13:56:02 INFO unit.kubernetes-master/0.juju-log Invoking reactive handler: reactive/kubernetes_master.py:88:install <= saw that at juju debug-log after reboot, so it restarted correctly but... no signs of life after that entry13:57
lazyPoweraha13:57
lazyPoweri have a couse of action for you now13:57
lazyPower  File "/usr/local/lib/python3.5/dist-packages/charmhelpers/core/hookenv.py", line 956, in resource_get <--13:57
lazyPowerit was locked up waiting on juju to resource_get a resource13:58
Zicnetwork issue? :o13:58
lazyPowerso, lets start with least invasive action13:58
lazyPowercan you re-attach to that unit and enter the debug-hook context again?13:58
Zicyup13:58
lazyPowersame process, attach to unit, if its locked up, restart the agent daemon13:58
Zichmm14:00
Zicthe debug-hooks does not let me in the right context this time14:00
Zicroot@mth-k8stestmaster-01:~# pwd14:00
Zic/home/ubuntu14:00
Zicthe tmux buffer is just "bash" instead of "install" like earlier14:01
lazyPowerright, when you first attach you only get a bash shell14:01
lazyPowerso, recycle the agent now14:01
lazyPowersystemctl restart jujud-unit-kubernetes-master-014:01
Zicah yup14:01
Zicforgot this step sorry14:01
Zicok, it's the right context now14:01
lazyPowernow, lets try this manually and see if we get any further detail14:01
lazyPowerresource-get kubernetes14:02
lazyPoweri suspect its going to just be hanging like it was when invoked with python, but you never know14:02
Zicfor now it's stucking yeah :)14:02
lazyPowerok, in another termina, lets attach to the controller and tail the controller logs14:02
lazyPowerif there's an issue we should see some serious spam in there while this resource-get is constantly polling attempting to grab the resource14:03
Zic2017-05-23 14:01:28 ERROR juju.rpc server.go:510 error writing response: write tcp 10.52.128.99:17070->10.52.128.24:59540: write: broken pipe14:04
Ziclike this?14:04
Zic(I have it repeatedly)14:05
lazyPowerthat may be it14:07
lazyPoweri would have expected something more descriptive14:07
lazyPowerZic: what version of the controller is this?14:07
Zic2.1.214:08
lazyPowerZic: looks like you're getting bit by this https://bugs.launchpad.net/juju/+bug/162712714:09
mupBug #1627127: resource-get gets hung on charm store <cdo-qa> <cdo-qa-blocker> <juju:Incomplete> <https://launchpad.net/bugs/1627127>14:09
ZicI feared that, as this test cluster is fully AWS (the production one is hybrid), I recreate the AWS SecurityGroup from scratch and mistaken somewhere, but normally it's openbar on private network14:10
lazyPowerZic: well there's also a defect in resource-get hanging like this14:10
lazyPowerit should have returned null or error by now14:10
lazyPowerinstead of hanging indef.14:10
Zicalways stuck with not returning the prompt :(14:10
lazyPowerclick the link at the top that this bug effects me, and add detail that you're able to reproduce deploying the bundle revision -23 (? i think?)14:11
lazyPowerthat'll help anastasiamac reproduce when it comes time to verify this bug again, as right now its incomplete and there's a good amount of back and forth about how to trigger this14:11
Zicneed to recover my Launchpad infos, wait :)14:12
lazyPowerZic: and you'll get an update when its fixed too :) becase ya know, you interacted with the bug <314:12
anastasiamaclazyPower: repro would be awesome \o/ midnight here now so m clocking off but will read backscroll :D14:12
lazyPoweranastasiamac: awe i didnt mean to ping you to bring you in here, my bad14:13
lazyPowercheers and will catch up with you tomorrow14:13
anastasiamaclazyPower: u did not ping ;) but i heard it all the way from there :D14:13
ZiclazyPower: added14:23
lazyPowerZic: fantastic, thanks for that. Now we're in a situation where we have to wait :S14:24
lazyPowerZic: correct me if i'm wrong, but this was just on the initial install of that older bundle rev yeah?14:24
Zicyup14:24
lazyPowerok14:24
lazyPoweri know how you can work around this14:24
lazyPowerso we dont have to wait but it wont be as clean as drag and drop14:25
Zicthe only special case is that I'm using manual provisionning14:25
lazyPowerin that bundle, it specifies individiual releases of charms... eg: kubernetes-master-1214:25
Zic(even if it's fully on AWS, because our Internal system manage AWS instance on its own...)14:25
lazyPowerif you go to http://jujucharms.com/u/containers/$charm  (including revno)14:25
lazyPoweryou can grab the resources for that charm on the right hand sidebar of that page14:25
lazyPowerthen once you juju deploy that bundle, you can juju attach $charm kubernetes=kubernetes.tar.gz as an example14:26
lazyPowerso you'll need to manually attach the resources, but it will get you unblocked14:26
lazyPower:( sorry that this isn't as smooth as it could be14:26
Zic https://jujucharms.com/u/containers/kubernetes-master-12/ is 404 :)14:27
lazyPowergah14:29
lazyPowers/-12/\/12/14:29
lazyPoweralso i dont know that thats the release you need14:30
lazyPoweri was using 12 as an example14:30
lazyPoweri think you're on rev 21 of master in that bundle...14:30
ZiclazyPower: just get the 12 from my juju status14:34
Zicit's the charm revision of kubernetes-master, right ?14:35
Zicor the revision of the charm-bundle?14:35
lazyPowerZic: the charm revision14:55
ZiclazyPower: do I need to restart the deploying of canonical-kubernetes from scratch ?14:57
lazyPowerZic: you should be able to attach those resources and recycle the agent and it should unstick the deployment14:57
Ziccool14:57
Zicfor attaching from CLI, what do I need? I think I'm mistaken "add-relation" and "attach" in my minds14:58
lazyPowerZic: juju attach --help (on your workstation)15:00
lazyPowerZic: and https://jujucharms.com/docs/2.0/developer-resources#adding-resources for reference15:01
ZiclazyPower: oh, it's what I thought, I'm mistaken attach vs. relation15:10
Zicthought it was relation to do manually :)15:10
ZicI'm OK with attach so :D15:10
ZiclazyPower | you can grab the resources for that charm on the right hand sidebar of that page15:26
Zickubernetes.gz is not clickable :D15:26
lazyPowerZic: from the revision specified in the bundle15:27
lazyPoweryeah15:27
lazyPowermake sure thats 1:1, i wouldn't recommend trying to use a different revision of the resource than what is published for the charm you're deploying15:27
lazyPowereg if you have kubernetes-master-12, then grab the resources off the right sidebar from https://jujucharms.com/u/containers/kubernetes-master/12/15:27
Zicyup but how can I *grab* it? you mean download locally right?15:28
ZiclazyPower: in https://jujucharms.com/u/containers/kubernetes-master/ (19th revision, the latest), ressources are clickable and downloadable, but for my revision 12th, ressources are not clickable either downloadable15:36
lazyPower:/ i'm not sure why that would be the case, resources are supposed to persist for the lifetime of the charm15:36
ZiclazyPower: https://jujucharms.com/u/containers/kubernetes-master/12/ can you get the kubernetes.gz ressource on this page?15:38
Zic(I'm using Firefox)15:38
lazyPowerrick_h: is there an API hack i can use to view this charm resource and determine why there's no downloadable resource?15:39
lazyPowerZic:  the only thing i can figure is somehow the charm got disassociated with a resource at this revision, and thats not going to be fun15:39
Zic:'(15:39
lazyPoweras i have no clue what resource would go with that revision, its quite old15:39
rick_hlazyPower: looking at what we're up to15:40
rick_hlazyPower: https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master/meta/resources ?15:41
rick_hlazyPower: e.g. https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master-12/meta/resources15:41
lazyPowerrick_h: https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master/12/meta/resources doesn't seem tow ork with a revision in the url15:41
lazyPoweroh15:41
lazyPowerofcourse :) the format changes15:41
rick_hlazyPower: yea, our bad for old vs new url format mixups15:41
ZiclazyPower: lurking a bit and found that https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master-12/resource/kubernetes/115:41
Zicis this good?15:42
lazyPoweryeah there's nothing there...15:42
lazyPowerits got no fingerprint on the listing15:42
lazyPowerwhoa15:42
lazyPowerwhat kind of wizardry is this15:42
Zic:>15:42
lazyPowerrick_h: your api skills surpass mine in every way, i have no clue how you found that15:42
lazyPoweroh snap and zic found it to boot15:43
lazyPoweri need new glasses15:43
rick_hlazyPower: https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master/meta goes to list all the bits available15:43
lazyPoweri think thats a sign i need to take my lunch before i head into a sig meeting15:43
rick_hlazyPower: so that lead to /meta/resources (and then the revision trick)15:43
rick_hlazyPower: :)15:43
ZiclazyPower: is this "1" file which seems to be a tar.gz archive containing kube-* binary is the kubernetes.gz you expect?15:45
Zicif yes, mv 1 kubernetes.tar.gz and I will continue your steps :)15:46
Zichmm, tried a ./kubectl --version of the binary inside15:46
Zicit's 1.4.0-beta.1015:47
Zicnot my version :(15:47
lazyPowerZic: time to walk through the revisions until you find the resource required. i hvae no clue whats going on in those older charm revs :| we were kind of a guinepig with resources15:48
lazyPowerZic:  you need 1.5.1 right?15:49
Zic1.5.315:50
Zichttp://paste.ubuntu.com/24634572/15:51
lazyPowerZic: try master rev 1915:51
lazyPowerthat should have 1.5.315:51
lazyPowermight be 18... but right around that range.15:51
Zicwhat I did not understand is why I have Rev 12 in the production cluster with kubernetes-master 1.5.315:52
Zicis the revision number is incorrect in this juju status?15:52
lazyPowerZic: did you attach a resource package post deployment?15:52
Zicnop :x15:53
lazyPoweri have no idea how this happened15:53
lazyPoweri'm just as baffled as you are :S15:53
Zicthis cluster in 1.5.3 is "one version" before 1.7.115:53
lazyPowerto my knowledge nobody on the k8s team has gone back and refreshed resource revisions attached to a charm rev15:53
Zicwe waited so long to upgrade it because 1.7.1 needs an outage maintenance (+ some test on our side)15:53
lazyPowerso what we published with is what should be attached to the charms15:54
lazyPowerwaiiit15:54
lazyPowerZic:15:54
lazyPoweri know why we're seeing the version mismatch now15:54
lazyPowerpromulgated version vs namespace version.  the promulgated charm is just a pointer to a charm rev in the namespace15:54
cmarstvansteenburgh, hi, i'm trying to get that zetcd snap to work in a charm, https://github.com/cmars/charm-zetcd15:55
lazyPowerlet me see if thats the case15:55
cmarstvansteenburgh, but, i can't seem to connect to zetcd with zkctl15:55
lazyPowercmars: he's afk for a bit headed to pickup his fam15:55
cmarslazyPower, ack, thanks15:56
tvansteenburghjust got back :)15:56
lazyPowerZic: thats not it - https://jujucharms.com/kubernetes-master/  is not a promulgated charm. so we only point at the namespace15:56
tvansteenburghcmars: does this help https://github.com/tvansteenburgh/zetcd-snaps15:56
lazyPowerZic: yeah i have no idea why thats the case :( i'm sorry i dont have better details.15:56
tvansteenburghcmars: i only tested with the example from the upstream zetcd readme15:56
cmarstvansteenburgh, ok. might be that i'm trying to connect it to cs:~containers/etcd15:57
ZicClient Version: version.Info{Major:"1", Minor:"4+", GitVersion:"v1.4.0-beta.11", GitCommit:"4b28af1232cc52da453eb4ebe3dc001314a1f99b", GitTreeState:"clean", BuildDate:"2016-09-23T22:53:01Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}15:58
Zicoops15:58
Zicbad pasting, let my try again...15:58
ZiclazyPower: Client Version: version.Info{Major:"1", Minor:"4+", GitVersion:"v1.4.0-beta.11", GitCommit:"4b28af1232cc52da453eb4ebe3dc001314a1f99b", GitTreeState:"clean", BuildDate:"2016-09-23T22:53:01Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}15:58
ZicRAH15:58
Zic:'(15:58
* Zic needs coffee15:59
Zicthird try, I can do it15:59
ZiclazyPower: https://api.jujucharms.com/charmstore/v5/~containers/kubernetes-master-19/resource/kubernetes/915:59
ZiclazyPower: found the 1.5.3 here15:59
Zicdon't ask me "why 9"15:59
Zicbut the /9 contains the 1.5.3 binary15:59
lazyPowerour api confuses me.15:59
lazyPoweri feel you16:00
Zic:}16:00
ZiclazyPower: does this mismatch displayed version can have significant problem when I will upgrade to the latest charms?16:00
Zicor it's just a displaying bug?16:01
lazyPowerZic: you'll be moving to snap packging16:01
lazyPowerwe can make more garantees there16:01
lazyPowerZic: you'll be in a track and always at tip of that track.16:01
Zicok16:02
ZicI think I will giving up the goal of building a "clone cluster" in 1.5.3 tho :(16:02
Zicwill directly test the upgrade in prod and *feared* :|16:03
lazyPowerZic: whats your scheduled time to do this upgrade?16:09
lazyPowerZic: i can spend some time either this evening or tomorrow morning running down the resources/revisions you have deployed and get something setup so we can test thsi without running a science experiment in prod16:09
lazyPowerZic: but i'm neck deep in trying to vet some code for a release today and i'm close to finishing. so i need the remainder of the day to finish this work up.16:10
ZiclazyPower: we can schedule that together, I don't want to impose you a date as it's for my work and you are just here as community help (my company decline the Canonical offers, sadly :/)16:11
lazyPowerZic: you're a valuable contributing member, you file bugs. i'm willing to help16:11
lazyPowerbut i appreciate you being respectful of my time as well16:11
lazyPowerso let me rund own the resources you need, and we'll go from there.16:12
lazyPowerZic: ill work off of http://paste.ubuntu.com/24634572/ and we can unwind from there16:12
Zicask me all you need, we are on different timezone (UTC+2 for info) and I'm on office from 10->19h, but I can lurk on IRC from home if needed16:14
ZiclazyPower: for http://paste.ubuntu.com/24634572/ for example, as displayed charm rev is maybe false, if I have a way of manually retrieving the good rev, tell me :)16:20
lazyPowerZic: /var/lib/juju/agents/unit-kubernetes-master/charm/revision16:23
lazyPoweri suspect it says "12" though16:23
Zicit said... "0"16:24
ZicxD16:24
Zic# cat /var/lib/juju/agents/unit-kubernetes-master-0/charm/revision16:24
Zic016:24
vlad_Hey guys anyone here to field a quick question?16:25
Ziccan I throw something violently on the wall? :)16:25
vlad_If you answer my question then yes for sure16:25
Zicvlad_: huhu, sorry, was not for you :)16:25
vlad_Zic: ahh ok no worries16:25
vlad_So I'm deploying a PoC juju/openstack cloud an want to deploy my juju controller to a specific node... is there a way to do this? (I looked but couldn't find anything obvious)16:26
vlad_Also I should clarify that I'm using maas as my machine provider16:27
lazyPowervlad_: you can specify a machine tag and tag that machine in maas16:28
Zicvlad_: I'm on manual provisionning so it's maybe incompatible with your case, but for me, it's like that: juju bootstrap manual/host.name.of.the.machine.which.host.the.controller cdk16:28
lazyPowervlad_: juju bootstrap --help   there's anotion of bootstrap constraints. and in that constraint list, you can specify the maas tag.16:28
vlad_lazyPower: thanks that's awesome didn't realize how deep constraints went.16:29
vlad_Zic: Thank you as well!16:29
Budgie^Smoreo/ Juju world16:34
hatcho/ Budgie^Smore16:35
lazyPower\o Budgie^Smore16:44
rick_hBudgie^Smore: are we chatting today?17:02
Budgie^Smoreyeah, was just pulling your number up... thought you were calling me for a min ;-)17:03
rick_hBudgie^Smore: hangout! link in the calendar invite17:03
rick_hBudgie^Smore: let me know if that doesn't work out17:03
=== frankban is now known as frankban|afk
jackjohnsmith^_^18:23
jackjohnsmithremove it18:23
jackjohnsmithremember felisha?18:23
jackjohnsmithsure canadian gov isnt looking for a smell is it?18:24
=== jackjohnsmith is now known as H0LYR3V3NG3
H0LYR3V3NG3rdy for a file top prevent visual18:28
H0LYR3V3NG3prison?18:28
H0LYR3V3NG3i know ur in csis body thats why im here18:28
=== H0LYR3V3NG3 is now known as jesse9
jesse9get it18:31
xModeMunxHi all. I'm new to juju, and just starting up a new cluster to test. This is an openstack "enterprise" local configuration.19:05
xModeMunxAm I able to provision the infrastructure via the online tool? Or am I not doing it right?19:05
xModeMunxI can't quite tell if this can be used as a "private" tool. I can register juju-cli as a cloud for my local maas configuration. So what are my limitations? :-/19:06
rick_hxModeMunx: so you can use the Juju CLI to bootstrap to a "private" openstack, or a local maas19:07
rick_hxModeMunx: from there you get a juju gui embedded into that Juju controller that you bootstrap so you get a bit of the online experience but self contained19:08
xModeMunxrick_h: I have got to that stage so far. So, i've bootstrapped and via the cli I can poll some basic things to test. So, onward to "configuring" my openstack deployment, how can I go about this?19:08
rick_hxModeMunx: oic, so you've used Juju to deploy openstack on top of MAAS?19:08
rick_hxModeMunx: to configure the openstack you can use Juju to provide some application level configuring for each OpenStack service or go to OpenStack (horizin dashboard for instance) to manage the OpenStack from there.19:09
xModeMunxrick_h: I haven't /yet/ deployed anything via juju. I have literally installed maas, added 2x "to-be" compute nodes, and 1x "to-be" controller node.19:09
rick_hbeisner: and others from the team that managed the openstack work would be able to help drop hints as to how to configure different bits you're interested in.19:09
rick_hxModeMunx: oic, so it might be useful to try the conjure-up to help do a sample/test install. It kind of guides/walks through the process a bit more than a manual deploy19:10
xModeMunxI have previously built OS from scratch, but having seen this tool, it seems I can alleviate mych of the efforts.19:10
xModeMunxrick_h: ah, awesome, i'll give that a go now :-)19:10
rick_hhttps://www.ubuntu.com/download/cloud/conjure-up check out https://docs.ubuntu.com/conjure-up/en/#getting-started19:11
stokachuand im here as well to help answer questions19:11
stokachuxModeMunx: ^19:11
xModeMunxstokachu: Waw, you guys are probably the friendliest irc people ever :-D19:12
rick_hxModeMunx: cool, yea hit up stokachu and others if you hit anything19:12
xModeMunxMuch appreciated guys. Let me go have a read, and see where it leads. Is this considered production ready btw? Cos it it proves useful, it may make its way into my next "real" work lab deployment.19:13
rick_hxModeMunx: yes, this is the same stack of tools we use to support our paying OpenStack customers.19:17
xModeMunxThanks Rick. Are you part of the canonical support guys?19:17
rick_hJust they get a nice phone number to call and some PDF files to go with it :)19:17
rick_hxModeMunx: no, we're more the dev engineer side.19:18
* rick_h has to run biab19:18
xModeMunxah, I see. The "real" men ;-)19:18
jesse9anywho i hacked all of you19:23
jesse9goodluck logging into anything19:23
xModeMunx```Set automatic aliases for snap "conjure-up" (cannot enable alias "juju" for "conjure-up", it conflicts with the command namespace of installed snap "juju")```19:23
xModeMunxSeems the first hurdle has presented itself.19:23
stokachuxModeMunx: sudo snap remove juju19:23
stokachuxModeMunx: conjure-up provides its own19:24
xModeMunxstokachu: Ahh. Even this snap stuff is new to me. I must be getting old :-(19:24
stokachuxModeMunx: im right there with you19:24
bdxSandbox2016!19:58
bdxwell19:59
xModeMunxAm I correct to view conjure as a terminal-based alternative to the online juju architect design tool?20:10
stokachuxModeMunx: to some extent, we go further and provide you with helpful guidance to configure your deployment20:11
stokachuwe can also make adjustments for deploying openstack and kubernetes on a single local machine20:11
xModeMunxstokachu: I see. Thanks for the clarity.20:11
stokachubdx: are you handing out passwords again?20:12
bdxthe problem with being overzealous to login to your pc before the screen turns on and you realize it wasn't sleeping and your irc window had the context20:14
* bdx weeping20:14
stokachulol20:16
stokachuive done that before too20:16
* lazyPower starts poke-checking known accounts for bdx20:17
* bdx wipes all reminisce of known string20:17
lazyPowergood plan :) I tease anyway ;)20:18
bdxlazyPower: its cool ... keep it up ... as long as you enlighten me to what this "CAAS" thing is while you are at it :)20:23
bdxcrickets20:26
bdx:)20:26
rick_hbdx: you causing trouble :P20:29
lazyPowerbdx: its a WIP, thats what it is :)20:35
lazyPoweror an experiment? i forget which20:35
lazyPowermaybe both20:35
xModeMunxif/when this conjure install finishes, and it works. I will consider it quite magical.20:41
xModeMunxI think it stalled. I crtl+c'd. Maybe I shouldn't have :-|21:09
stokachudepending on your hardware it could take up to an hour21:17

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