[09:17] <stub> I have banged out Python3 support for charm-helpers, https://code.launchpad.net/~stub/charm-helpers/py3/+merge/242460
[09:17] <stub> I've love a review ASAP since branches like this will grow conflicts with every landing
[11:51] <erkules> ahoi, what platforms are supported by juju?
[13:55] <tvansteenburgh> stub: thanks for the py3 charmhelpers branch! gonna review that now
[13:56] <stub> tvansteenburgh: ta.
[13:57] <darknet_> lazypower_: hi how are you?
[13:59] <darknet_> lazypower_: I've re-install everything using the guide published of Marco Ceppi (http://marcoceppi.com/2014/06/deploying-openstack-with-just-two-machines/). But the result is the always the same when I try to open the horizon I see just a white page!!!
[14:04] <darknet_> someone can help me, please?
[14:13] <darknet_> and from host machine a can ping that using either IP address or FQDN.
[14:22] <bloodearnest> hm, how does one use t2.micro instance-type on amazon?
[14:24] <bloodearnest> ah. https://bugs.launchpad.net/juju-core/+bug/1336473
[14:24] <mup> Bug #1336473: Support new t2 instance types on AWS <ec2-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1336473>
[14:24] <bloodearnest> bummer
[14:49] <darknet_> anyone can help me???
[14:58] <marcoceppi> darknet_: I'm about to follow my directions again to see if I can reproduce the issue
[15:01] <darknet_> marcoceppi_: hi Marco, thanks a lot for your reply. I also send y a private message about that issue.
[15:02] <darknet_>  marcoceppi_: I've re-install everything and I've the same issue...a white page
[15:06] <lazyPower> greetings darknet_
[15:06] <lazyPower> have you confirmed no further relationships are running in your environment? ran juju debug-log and saw no chatter amongst units reporting they are still doing anything?
[15:32] <lazyPower> can i get a quick pair of eyes on https://code.launchpad.net/~bigdata-dev/charms/trusty/hdp-hadoop/trunk/+merge/242414 ?  I need to get this landed for CTS today
[15:33] <dpb1> lazyPower: looking
[15:33] <lazyPower> thanks dpb1
[15:34] <marcoceppi> lazyPower: why are you removing usr/bin/env?
[15:34] <dpb1> lazyPower: what kind of testing have you done?
[15:34] <lazyPower> i didnt catch that marcoceppi - but a quick push will fix that
[15:35] <lazyPower> dpb1: deployed on canonistack, and hpcloud leveraging the tests in the charm suite - HDFS DFSADMIN report yields a good cluster, and terragen/sort smoke tests
[15:35] <marcoceppi> lazyPower: why do you have amir's branch in the bundle? wouldn't you want amulet to use the CWD charm?
[15:37] <lazyPower> marcoceppi: that was inhereted from amirs branch - when i ran the tests i pointed it at ~bigdata-dev
[15:38] <marcoceppi> lazyPower: just drop all that in general
[15:38] <lazyPower> when i push this from bigdata-dev i'll update to use the cs resource - however in bundles whats the proper format for calling CWD?
[15:38] <marcoceppi> and put charm: hdp-hadoop
[15:38] <lazyPower> marcoceppi: when i ran that it deployed cs:trusty/hdp-hadoop
[15:38] <marcoceppi> amulet will see that the charm its testing is that and use the directory the test is launched from
[15:38] <marcoceppi> how did you test?
[15:38] <lazyPower> with JUJU_REPOSITORY set, it didnt deploy that, it picked the CS resource over local
[15:38] <lazyPower> bundletester and executing the script directly
[15:39] <lazyPower> eg: tests/10_deploy
[15:39] <marcoceppi> idontbelieveyou.gif one second
[15:40] <marcoceppi> so, I don't know if bundletester sets JUJU_TEST_CHARM
[15:40] <marcoceppi> but if you set that to hdp-hadoop
[15:40] <marcoceppi> it will work
[15:41] <lazyPower> ok, so you want me to nuke the branch bits and export that env var and re-test?
[15:41] <marcoceppi> wait
[15:42] <marcoceppi> tvansteenburgh ^?
[15:42] <tvansteenburgh> ?
[15:43]  * tvansteenburgh reads scrollback
[15:45] <tvansteenburgh> if the the charm name matches the local dirname amulet will deploy the local charm
[15:46] <lazyPower> thats not consistent with what i saw lastnight but i'm running another test on it now
[15:46] <lazyPower> i know thats the case when the service is declared in the test itself - but the bundle was consistently picking cs:trusty/hdp-hadoop
[15:47] <tvansteenburgh> is the bundle file being loaded by amulet
[15:47] <tvansteenburgh> ?
[15:48] <tvansteenburgh> or just picked up implicitly by bundletester
[15:48] <lazyPower> its being loaded by amulet
[15:48] <lazyPower> self.d.load(yaml.safe_load(bun))
[15:49] <tvansteenburgh> ok
[15:49] <lazyPower> i see there's an open file descriptor in the test :S might as well fix that while i'm in here
[15:52] <darknet_> marcoceppi_: re-open the URL without /horizon I don't see neither the apache's page
[15:53] <lazyPower> darknet_: are you getting a no response or an empty reponse?
[15:59] <marcoceppi> tvansteenburgh: is it because the service naem doesn't match the charm name?
[15:59] <marcoceppi> as in the service is being aliased in the bundle file
[16:00] <darknet_> marcoceppi_: I tried to ping the node from host (my PC) using both IP add. and FQDN and it works correctly..
[16:00] <tvansteenburgh> marcoceppi: i haven't seen the bundle file
[16:01] <tvansteenburgh> is anything actually broken? i was waiting to hear the results of lazyPower's test run
[16:01] <lazyPower> tvansteenburgh: spinning up vagrant to run again - took me a minute to clean up and re-import the box.  I'm in the middle of another test on canonistack so my env is a bit occupied
[16:02] <tvansteenburgh> d.load() just calls d.add() for every service in the bundle, so it determine the charm-under-test in the same way
[16:02] <tvansteenburgh> *should*
[16:05] <lazyPower> i'll know as soon as the vm is booted - i'll ping ya with the results tvansteenburgh
[16:05] <tvansteenburgh> roger
[16:09] <dpb1> lazyPower: I'm progressively submitting diff comments
[16:13] <lazyPower> awesome. feedback much appreciated
[16:32] <dpb1> lazyPower: ok, I'm done, marked needs fixing
[16:33] <dpb1> caught one bug, most of the others are just really egregious style errors
[16:33] <lazyPower> dpb1: solid - i'll get these banged out and pushed within the hour. Cheers for the review
[16:40] <dpb1> np
[17:01] <lazyPower> marcoceppi tvansteenburgh whit: standup
[17:44] <themonk> jose, hi
[17:44] <themonk> jose, can we PM now?
[17:53] <themonk> lazyPower, hi
[17:53] <lazyPower> Hello themonk
[18:01] <themonk> lazyPower, sorry for late replay
[18:01] <lazyPower> no worries themonk
[18:02] <lazyPower> tvansteenburgh: appears nothings broken
[18:02] <tvansteenburgh> \o/
[18:02] <lazyPower> tvansteenburgh: i did however export the env var implicitly
[18:02] <lazyPower> that may or may not have been the magic sauce
[18:03] <tvansteenburgh> well yeah that'll work too
[18:03] <tvansteenburgh> although should work w/o it
[18:06] <lazyPower> yeah i had a variable in there i didnt think to isolate
[18:06] <lazyPower> next time around. but i'd say its safe to assume it was PEBKAC
[18:13] <themonk> lazyPower, i have a script.py which is not idempotent, i am passing properties values to config-change using juju set, and because setup.py is not reconfigurable i am setting a lock so that it(setup.py) can not run second time, and mention it in readme, my question is will it be a blocker in charm review?
[18:14] <lazyPower> themonk: its quite dependent on the context of the immutable configuration - in some scenarios it is neccessary to prevent dataloss for example.
[18:14] <lazyPower> Can you give some context as to why  the setting is immutable?
[18:22] <themonk> lazyPower, the context is it creates certs and insert it in jks and creates DS data which is immutable and many other things which i dont know all :)
[18:24] <themonk> lazyPower, may be it not complex to make it mutable, but right now its immutable.
[18:24] <lazyPower> themonk: that seems like a candidate for consideration - its going to be up to the reviewer that looks at the code
[18:25] <lazyPower> if there is a sane and viable way to make it mutable - we would perfer that be the case
[18:25] <lazyPower> themonk: i suggest you push it to a namespace branch and get a proper code review - otherwise its a bit too subjective to make a proper response.
[18:26] <themonk> lazyPower, hmm, agreed :) doing it, thanks
[18:27] <lazyPower> anytime themonk - good luck on the review
[18:27] <themonk> lazyPower, :)
[18:32] <jcastro> You can now configure 'apt-mirror' in environments.yaml to specify the
[18:32] <jcastro> mirror used by all the machines provisioned in the environment.
[18:32] <jcastro>     apt-mirror: http://my.archive.ubuntu.com
[18:32] <jcastro> \o/
[18:32] <jcastro> my fave feature so far
[18:38] <lazyPower> dpb1: fixes are up - running tests now
[19:43] <jcastro> jose, lazyPower, marcoceppi: let's fire it up in like 5 more minutes?
[19:43] <jose> sounds good to me
[19:43] <lazyPower> Sounds like a plan
[19:50] <jcastro> jose, ok let's do this!
[19:50] <jose> yep, it's starting
[19:51] <jcastro> jose, post the youtube link too for people who just want to listen
[19:51] <jose> got it
[20:01] <rick_h_> jcastro: jose marcoceppi mbruzek1 lazyPower working on an initial readme for hte bugs for jujucharms.com, please feel free to suggest updates. https://github.com/CanonicalLtd/jujucharms.com
[20:03] <jose> rick_h_: thanks! will take a look once we're done with the Charm School
[20:03] <rick_h_> jose: all good ty much
[20:06] <jcastro> wwitzel3, around?
[20:11] <jrwren> awe man, I'm missing charm school?
[20:13] <jcastro> yeah
[20:14] <jcastro> jose, youtube link pls
[20:14] <jose> ubuntuonair.com
[20:14] <jose> sec checking analytics
[20:16] <jose> or youtube.com/watch?v=NjERFuBs2S8
[20:20] <cory_fu> https://github.com/juju/plugins/
[20:22] <wwitzel3> jcastro: yepo
[20:23] <jcastro> https://plus.google.com/hangouts/_/g4roaheffd55jqc2tofvieb42ya?hl=en
[20:23] <jcastro> want to join our charm school to explain your new retry hotness?
[20:30] <cory_fu> https://github.com/nojhan/liquidprompt
[20:32] <sarnold> cory_fu: wow
[20:33] <lazyPower> sarnold: you following along at home on the charm school?
[20:34] <sarnold> lazyPower: no :/
[20:36] <lazyPower> sarnold: cory_fu wrote a pretty intense juju plugin
[20:36] <lazyPower> juju dhx
[20:36] <cory_fu> Oh, I thought you were impressed by my dhx plugin.  :)
[20:37] <cory_fu> wwitzel3: Please check out the middle / end of the Charm School video we just finished.  I'd like to get your feedback on my dhx plugin
[20:37] <sarnold> oh :) well, maybe I would be, let me go looking for it :)
[20:39] <sarnold> yup, looks pretty cool :)
[20:44] <cory_fu> wwitzel3: https://www.youtube.com/watch?v=NjERFuBs2S8#t=1059
[20:44] <wwitzel3> cory_fu: thank you
[20:45] <wwitzel3> jcastro: sorry, I didn't respond earlier, I'm neck deep in trying to get something reviewed and landed before I go on vacation for 2-weeks
[20:50] <cory_fu> wwitzel3: Oh, then the plugin review isn't urgent enough to block your vacation.  :)  Just was curious on your feedback vis what of those features might make sense in core down the road.
[21:14] <darknet_> Someone can help me? I've reported a problem with Openstack that was deployed by Juju.. All relations between charms are ok (green) but if I try to open horizon, I receive an error page like that " This webpage is not available".  I tried also to ping the vm node from my host using either its IP address or FQDN and it works!!. I followed this guide http://marcoceppi.com/2014/06/deploying-openstack-with-just-two-machines/. B.R.
[21:14] <darknet_> darknet
[21:19] <jrwren> I have an open bug on this, and I'm looking for ideas for work arounds. https://bugs.launchpad.net/juju-core/+bug/1392786
[21:19] <mup> Bug #1392786: charm has no way to report error state <charms> <feature> <hooks> <juju-core:Triaged> <https://launchpad.net/bugs/1392786>
[21:20] <jrwren> what to do when a charm has an error, if I'm actively avoiding error states?
[21:21] <jrwren> e.g. right now my charm takes a source PPA as config option. If you type that wrong then the isntall hook errors. I can catch the exception and let the hook complete without error. Question is, should I?
[21:24] <darknet_> anyone can help me?
[21:33] <cory_fu> darknet_: Is the openstack-dashboard service exposed?  (Does it say "exposed: true" in `juju status openstack-dashboard`?)
[21:34] <darknet_> cory_fu_: yes all services are exposed
[21:35] <cory_fu> darknet_: And port 80 is open (listed under ports)?
[21:36] <darknet_> cory_fu_: let me check
[21:37] <cory_fu> jrwren: There is a discussion underway for a feature to allow charms to report information, including more detailed statuses and messages, back to the user.  The semantics haven't been finalized yet, though, so it will be a while before it's available.  I'm definitely hoping it comes sooner rather than later.
[21:40] <cory_fu> jrwren: For the time being, how you handle it very much comes down to your specific needs.  I would lean toward failing into error state if the user enters an invalid value, since there isn't really a way to inform them that their selection is being ignored
[21:40] <cory_fu> But, depending on your specific scenario, it may be acceptable to fall back to a default value
[21:43] <darknet_> cory_fu_: i don't know what happened but not i see the openstack's dashboard....i don't have any idea why
[21:44] <cory_fu> E.g., something like an invalid PPA should probably be an error, because otherwise they'd be running the incorrect version / code without realizing it, but something like setting the domain to be used when generating URLs could be defaulted to a valid domain if you detect something completely wrong
[21:44] <jrwren> cory_fu: thanks. I'm going to go ahead and fail.
[21:45] <cory_fu> darknet_: It's possible the machine failed to provision.  Try looking through the full output of `juju status` to see if there are any errors that you missed
[21:45] <cory_fu> jrwren: Yeah, it's definitely not ideal, but we don't have a better option (yet!)
[21:45] <tvansteenburgh> lol, jrwren qotw
[21:46] <cory_fu> lol
[21:46] <jrwren> tvansteenburgh: tis my life motto.
[21:46] <sarnold> awesome :)
[21:48] <darknet_> cory_fu: this is a paste of juju status http://paste.ubuntu.com/9157090/
[21:49] <darknet_>  cory_fu_: I don't see any error!!!
[21:49] <marcoceppi> darknet_: is apache2 running on openstack-dashboard?
[21:50] <darknet_> yes
[21:51] <cory_fu> darknet_: And listening properly on 80 & 443 (netstate -tnl)?  If so, I guess check the Apache logs, unless marcoceppi has a better suggestion
[21:52]  * cory_fu tags out, because he just reached the end of his depth.
[22:05] <darknet_> cory_fu_: after to run the command "juju set keystone admin-password="test01" and try the login openstack gave me "Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator."
[22:31] <cory_fu> darknet_: Sorry, I stepped away.  Honestly, I haven't done anything with that openstack deployment.  You'd really need marcoceppi to help you, I'm afraid
[22:31] <darknet_> cory_fu:_ anyway thanks a lot for your support i'll try to ask that to marco
[22:32] <cory_fu> Good luck.
[23:07] <darknet_> cory_fu_: this is strange I've reboot all node and now I can open horizon, same error "This webpage is not available"....why?why?