/srv/irclogs.ubuntu.com/2014/09/18/#juju.txt

bradmanyone about?  I'm having issues with getting a juju bootstrap to work, looking at the debug logs its in a loop around trying to ssh in, even though the ssh command it's trying to use it working when I do it manually00:19
sarnoldis there anything in the unit logs?00:20
bradmwell, no, because juju can't seem to talk to the unit00:21
bradmthere's no juju installed, no evidence that juju has done anything to it00:21
sarnoldbut you could ssh in manually and look, right?00:21
bradmthis is using juju+maas, so the instance is a physical machine00:21
bradmsure can00:21
bradmthere's no /var/lib/juju or /var/log/juju on the unit, there's no juju package installed00:22
bradmoh hang on, the bootstrap node has juju 1.20, but the unit can only see 1.18, that doesn't seem good00:23
sarnoldyou've rapidly gone beyond my experience :) but maybe the --upload-tools thing can help?00:23
bradmmaybe, and if I can add the juju stable ppa to the maas preseed as well, might help00:24
bradmif I create the /var/lib/juju/nonce.txt by hand, everything starts moving forward01:05
=== fuzzy is now known as Fuzai
=== Fuzai is now known as Ponyo
ayr-tonpanic: Unexpected <nil> in storage-port: <nil>. Expected float64 or int. When juju status. juju 1.21-alpha1-trusty-amd6402:18
ayr-tonSomeone knows how to fix it?02:19
josemarcoceppi: hey, I'm having this problem, "Failed to request test // Only charmers can initiate reviews"03:09
=== uru_ is now known as urulama
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
Xiaoqiannobuto: ping09:04
zaargydoes juju autoheal services? if so can someone point me to how it works? thanks09:23
=== fabrice is now known as fabrice|lunch
Odd_BlokeIs there a programmatic way of destroying a service without having to guess when to resolve errors?11:24
Odd_BlokeBy "programmatic" I mean "I'm writing a shell script using the Juju CLI".11:24
Odd_BlokeUse case is this: I want to spin up a service and if it fails to deploy, remove it completely.11:25
Odd_Bloke(Such that deploying again won't get an 'already deployed' error)11:26
Odd_Bloke(Side note: is there documentation of the possible agent states?)11:31
MmikeOdd_Bloke, can't you destroy your environment and try again?11:54
=== psivaa_ is now known as psivaa
Odd_BlokeMmike: These are ephemeral services which I would expect to be deployed in to an existing environment.12:08
MmikeOdd_Bloke, from what I can see you can only do 'destroy-machine' with --force option - that would remove all units deployed on that machine12:10
Odd_BlokeMmike: Cool, I'll give that a try. Thanks!12:14
MmikeOdd_Bloke, sure thing - let us know if that worked for you12:14
Odd_BlokeWill do.12:14
Odd_BlokeIf I change configuration options iwthin hooks, should I expect the changed values to show up in a 'juju get'?12:23
=== fabrice|lunch is now known as fabrice
rcjOdd_Bloke, in my experience, no.  If a unit changes a service config value, that change is not reflected to other units or to the juju CLI/GUI12:56
rcjI'm having that problem too.12:56
rcjIs there a way to surface arbitrary data/status from a charm back to the cli?12:57
Odd_Bloke"juju ssh cat ..."? ¬.¬12:58
Odd_BlokeMmike: A first test suggests that blowing away the machine works. :)13:11
lazyPower Odd_Blokejuju destroy-machine # --force13:31
lazyPowerthen juju destroy-service13:31
Odd_BlokeCool, that's working for me.13:34
=== kentb-out is now known as kentb
lazyPowermwenning: ping14:43
mwenninglazyPower, pong14:44
lazyPowerI know this is low priority atm, any updates on the dell cluster?14:44
mwenninglazyPower, dell cluster?14:52
lazyPowermwenning: apologies for being the master of no context. The Dell OpenManage server charm was pending tests when I left off.  I beleive kent handed this off to you?14:53
mwenninglazyPower, ah.   yes he did.  Looks like Adam Israel looked at it yesterday and said the charm tests pass cleanly.14:56
mwenningMy TODO list today says to contact you and ask what the next steps are :-)14:57
lazyPoweraisrael: i haven't looked at the charm since kent and I last spoke. the tests that passed cleanly were unit tests I'm assuming?14:57
aisraelNo. Charm proof passed cleanly, but I was unable to run the tests15:00
mwenningaisrael, why couldn't you run the tests?15:01
lazyPowermwenning: i'm one of the few people that has access to that lab, and even then i had a heck of a time getting in15:04
aisraelLooking back through my notes. I see: 2014-09-17 15:33:16 INFO config-changed Starting Systems Management Data Engine:15:04
aisrael2014-09-17 15:33:16 INFO config-changed Failed to start because system is not supported15:04
mwenninglazyPower, aisrael, I see.  OK let me play with it.  aisrael, what system were you using?15:05
aisraelmwenning: Testing using the local provider under vagrant15:06
lazyPoweraisrael: its not going to run there, as it depends on a specific dell package that gets installed to manage them that has access to control fans, etc.15:07
mwenningoh.  Don't think OMSA will work there, you probably need real dell hardware15:07
lazyPowerits a hardware level api15:07
lazyPoweryeah, i already went through all of this, which is what sparked the request for the lab15:07
mwenningMaybe I can log a clearer error message15:08
aisraelRight, that's what I figured. I meant to re-assign the ticket to you to review, but lp wouldn't let me15:09
lazyPoweraisrael: no worries. I've had this on my recurring todo list for a couple weeks now since we've had a bit of back and forth about it15:17
=== wedgwood1 is now known as wedgwood
=== fabrice is now known as fabrice|familyti
=== victorp_ is now known as victorp
mwenningkentb, good morning!16:07
kentbmwenning: mornin!16:07
mwenningThey are discussing your charm on the internal #juju -16:07
mwenning<lazyPower> mwenning: any insight on if this works for other servers or if its limited to an implicit series such as the M R and G (i think)16:08
mwenningI said it should work on any Dell server that supports OMSA, is this correct?16:08
kentbcorrect, so, PowerEdge C is the only line that doesn't work, but, Dell will tell customers that as well.16:09
mwenningkentb, cool, thx16:09
kentbmwenning: np.  my pleasure :)16:09
lazyPowerkentb: o/16:10
=== fabrice is now known as fabrice|family
kentbo/16:11
mwenningkentb, thx,  one more step closer...16:12
kentbyep...it's been a long road on this one.  Thanks for helping out with carrying it to the goal line.16:12
lazyPowerkentb: we're literally feet away from the finish line. I need to evaluate the tests being run and wrap up on teh quorem of implications this has on our CI and its a wrap.16:13
kentblazyPower: awesome.  Thanks for all your help and review.16:14
lazyPowerNo problem, thanks for being a responsive charm author :)16:15
lazyPowerand leaving me in good hands post-facto. mwenning deserves a beer.16:15
kentbyou are certainly welcome. mwenning does deserve a beer.  Fortunately, he's just down the road from me.16:15
=== kentb is now known as kentb-afk
=== CyberJacob|Away is now known as CyberJacob
=== kentb-afk is now known as kentb
=== kwmonroe is now known as kwmonroe_
=== kwmonroe_ is now known as kwmonroe
=== roadmr is now known as roadmr_afk
josejcastro: updating the Ubuntu on Air! calendar18:59
natefinchjcastro: got a minute to talk about feature flags?19:34
=== roadmr_afk is now known as roadmr
mbruzekDoes anyone in #juju know what charm can relate to couchdb's "db" relation?20:10
=== urulama is now known as urulama-afk
marcoceppinatefinch: I do20:20
* marcoceppi was off yesterday20:20
natefinchahh cool20:20
natefinchso we had a juju core team lead meeting this morning, and we talked about feature flags for a good proportion of our hour long meeting20:21
marcoceppifun!20:21
natefinchwhat we decided on was that having a flag per feature was just going to get too unwieldy and too confusing for everyone, so we should just mark charms very simply as "needs juju x.y or higher"20:21
natefinchand that perhaps this has some drawbacks compared to feature flags, but that they were worth the tradeoff just to make things easier for everyone to understand.20:22
marcoceppinatefinch: I'm a +1 with needs juju x.y and if the field is ommitted it's a safe to use charm20:23
natefinchyep20:23
natefinchcool20:23
marcoceppias that begins to land I'll make sure the review docs are cleared up to make sure people using newer features have this in metadata.yaml20:23
natefinchyep, I'll sync with you so that we make sure the docs and the feature land together20:24
marcoceppinatefinch: \o.20:24
lazyPowerthis is re: healthchecks/actions/etc?20:24
natefinchish, yes.  Basically, a way to use features that will be not be backwards compatible with older jujus without totally screwing the older jujus (i.e. deploy and nothing happens)20:24
natefinchit'll also mean that if you make a new version of a charm and mark it with a minimum juju version, older versions of juju will still use the old charm, and not try to deploy the new one that won't work20:26
natefinch..... where new version means one for a newer series20:26
lazyPowerawesome20:26
lazyPower+1 from me20:26
natefinchcool20:26
marcoceppinatefinch: given how much of a proponent jcastro was to this yesterday you may want to double check with him, but I think this should appease him20:27
natefinchmarcoceppi: cool. Yes, I wanted to talk with him about it. Hopefully this will be good enough.  I'll make sure to catch up with him next time he's avaialble.20:27
jcastroI AM APPEASED!20:27
natefinchhaha20:27
jcastronatefinch, sorry I didn't respond I just got back20:27
jcastroMin version seems like the best approach to me20:28
natefinchjcastro: how I viewed that last message: http://2.bp.blogspot.com/-FFpUo771xbc/UaNn0M9Ap3I/AAAAAAAAAWU/CBNxgExQRfg/s1600/51987-Are-You-Not-Entertained-1a5I.jpeg20:28
natefinchjcastro: cool20:29
jcastromin is nice and easy20:30
jcastrobecause we can easily search one field20:30
natefinchyep20:30
natefinchand there's no magic to figuring it out20:30
jcastroinstead of "ok search for charms which support feature X"20:30
jcastrothen we'd have to have a feature-to-version grid, etc.20:30
natefinchyup20:31
jcastrohey marcoceppi20:41
jcastroyou were going to generate a tarball of all the charms for the OBs right?20:41
marcoceppihey jcastro20:41
jcastroso we don't have to wait all day for charm get all iiirc20:41
marcoceppijcastro: I do do this, yes20:41
jcastrolink?20:41
marcoceppijcastro: http://people.canonical.com/~marco/mirror/juju/charmstore/20:41
marcoceppiit needs to be refreshed now that I look at it20:42
marcoceppiunmomento20:42
=== tdc_ is now known as tdc
=== kwmonroe_3tac is now known as kwmonroe
=== CyberJacob is now known as CyberJacob|Away

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