[06:10] <stub> Tribaal: Could be. I'm noticing that bootstrap now seems a lot slower, with a CPU core nearly pegged and 60% iowait for over half a minute.
[09:32] <d4rkn3t> hello everyone, I've a question for you about JUJU environments and the deploy of services. I'v e created on a virtual environment with 3 VM (1 Region and 2 Cluster), added 1 node to RC and installed JUJU on RC, made the bootstrap of node the ubuntu's installer starts and install the OS. Now I'd like to deploy the services seeing the guides on web I saw that for each charms installed it creates a machine...my question is these machines
[09:32] <d4rkn3t> are a clone of the node or it's a name to identify just the charm installed on the node?
[09:58] <d4rkn3t> anyone can answer me?please
[10:32] <noodles775> d4rkn3t: I think that the name you are referring to is the "service name" (which defaults to the charm name if you don't provide one - see `juju help deploy`).
[10:33] <noodles775> hazmat, lazyPower: updates to the elasticsearch README if you've time: https://code.launchpad.net/~michael.nelson/charms/trusty/elasticsearch/update-readme/+merge/225802
[10:34] <noodles775> lazyPower: So I don't ping you in the future, what's the process to get updates to charms in the review queue - do I need to create a bug for each?
[10:34] <lazyPower> noodles775: yeah, if you've got a MP, make sure charmers is the reviewer
[10:34] <lazyPower> sorry just now waking up
[10:34] <lazyPower> its still pretty early here - give me a few to get moving and i'll take a look
[10:35] <noodles775> lazyPower: hah, sorry? You just replied within the minute! No rush, enjoy your breakfast!
[10:35] <lazyPower> :)
[10:38] <d4rkn3t> noodles775: thanks for your support it's a bit clear but I don't understand ia think f I've 4 nodes installed on MaaS and  I try to deploy a service, for example wordpress, this one will be installed on machine 0 by default?
[10:40] <noodles775> d4rkn3t: Ah - I'm not sure - I've not used MaaS. gmb or allenap might be able to answer your original question then? ^^
[10:41] <d4rkn3t> noodles775: and in case we want to add another node to MaaS , I've to run again the Juju bootstrap to allow to Juju to know there is a new node?
[10:42] <d4rkn3t> noodles775: thanks again for your first answer..
[10:42] <noodles775> No, you only need to bootstrap the juju environment once, but I'll defer to someone with experience with MaaS for the rest of your question :)
[10:43] <noodles775> no problem.
[10:43] <allenap> d4rkn3t: Juju asks MAAS for a machine, and MAAS chooses one in no special order (that satisfies any criteria that Juju has specified), so your first service deployment won’t always go to your first machine.
[10:43] <d4rkn3t> ok, I'll contact gmb or allenap
[10:43] <d4rkn3t> for the rest
[10:44] <allenap> d4rkn3t: When you add a machine to MAAS Juju can immediately make use of it, because Juju just asks MAAS for machines as it needs them.
[10:44] <d4rkn3t> so, one service one node????
[10:46] <d4rkn3t> each service will be installed on a node?
[10:46] <allenap> d4rkn3t: Yes, by default, but Juju can put multiple services onto a single machine if you ask it.
[10:46] <d4rkn3t> ok
[10:46] <d4rkn3t> now it's more clear!!!
[10:48] <d4rkn3t> and if I'd want to specify more environments  for example maas1, maas2.... how do juju assign the node to environment? it's the last q. I make :-))
[10:51] <lazyPower> d4rkn3t: each environment is its own isolated configuration, and your driving workstation will have that configuration
[10:52] <lazyPower> you can use the same maas cluster for different environments, and you would switch between them as 'juju switch maas1' - they keep the machines allocated isolated to that environment
[10:52] <lazyPower> i'd caution you against using the same user/apikey though, and isntead make a different user per environment so its apparent in teh maas GUI which machines are allocated to which environment
[10:59] <d4rkn3t> lazyPower: let's me know....at the begin i've an environment (maas1), i make the bootstrap juju see the node created on MaaS and deploy the service on that nodes. Then i decide to create new environment (maas2) with new nodes,  how can I assign the new nodes to the second environment?
[11:00] <lazyPower> d4rkn3t: you need to create the maas2 environment in $HOME/.juju/environments.yaml - and follow the same process as you would with mass1 but in the context of maas2 by issuing 'juju switch maas2'
[11:00] <d4rkn3t> ok
[11:01] <d4rkn3t> and the new context i can decide which node to use for that environment
[11:02] <lazyPower> just like maas1 - juju is only asking maas for a node
[11:02] <lazyPower> maas will randomly return a node for juju to use.
[11:02] <d4rkn3t> ops ....in the new context...
[11:03] <d4rkn3t> and using juju-gui, can i see these different environment and the node used for that one?
[11:21] <lazyPower> You'll need to deploy a second instance of the juju-gui
[11:22] <lazyPower> at the moment you cant manage multiple environments with a single juju-gui - rick_h__ may have more information on the subject as he's the GUI project guru.
[12:31] <d4rkn3t> lazyPower: thanks a lot for your support I'll try to make that on my infrastructure
[12:31] <lazyPower> No Problem d4rkn3t
[13:02] <d4rkn3t> lazyPower: I've tried to add 1 more node on MaaS but Juju don't see that when I run juju status
[13:03] <d4rkn3t> why?
[13:03] <lazyPower> d4rkn3t: which environment are you in? still in maas1?
[13:03] <d4rkn3t> the default, maas
[13:04] <lazyPower> and how are you trying to add a machine?
[13:04] <adeuring> d4rkn3t: Juju knows only about machines that are already deployed. By adding a machine to Maas you just make the number of machines offered by Maas larger
[13:04] <lazyPower> (relative) morning adeuring
[13:04] <d4rkn3t> how can i make that?
[13:04] <adeuring> morning lazyPower
[13:05] <d4rkn3t> the node is in ready status
[13:05] <adeuring> d4rkn3t: just run "juju deploy some-new-service" of "juju add-unit"
[13:07] <d4rkn3t> it should see the new node added on MaaS?
[13:07] <adeuring> yes
[13:07] <d4rkn3t> I don't see it
[13:08] <d4rkn3t> if i run juju status I see just "0" machines ( the first node I added before)
[13:08] <adeuring> d4rkn3t: whoich commands did you try?
[13:08] <lazyPower> i think its prudent to start a few steps back. How many machines do you have allocated in your MAAS pool d4rkn3t?
[13:10] <d4rkn3t> lazyPower:  at moment I've 2 node
[13:10] <lazyPower> d4rkn3t: ok, so when you view your MAAS gui, you have the region-controller and the cluster controller on teh same machine, with 2 additional nodes enlisted in maas?
[13:10] <d4rkn3t> one node has been bootstrapped with juju
[13:11] <d4rkn3t> now I've added another node to MaaS,
[13:11] <lazyPower> http://i.imgur.com/k0jvVIT.png
[13:11] <lazyPower> similar to the following, but showing 2 nodes, correct?
[13:11] <d4rkn3t> Ive RC + 2 CC ( offer DHCP service) with 2 node
[13:12] <lazyPower> when you issue juju deploy 'myservice' - its going to take a moment to go through the fastpath installer (assuming thats how you have your nodes setup) before it'll show as enlisted in juju
[13:12] <lazyPower> this can take up to 5 minutes depending on network speed, machine specs, etc.
[13:12] <lazyPower> however, in juju you should see it as pending
[13:12] <d4rkn3t> ok
[13:13] <d4rkn3t> until here everything are ok!
[13:13] <lazyPower> I'm bootstrapping my maas cluster atm so i can pull example output for you
[13:14] <d4rkn3t> lazyPower: thanks
[13:19] <lazyPower> d4rkn3t: http://paste.ubuntu.com/7760128/
[13:19] <lazyPower> thats directly after running juju quickstart, and juju deploy ubuntu
[13:20] <d4rkn3t> you're using 2 node, isn't it?
[13:21] <d4rkn3t> "0" and "1"
[13:21] <d4rkn3t> and on "1" you've deployed juju-gui!
[13:27] <lazyPower> yep, there's 3 total here, the bootstrap teh gui and a pending ubuntu node
[13:29] <d4rkn3t> lazyPower: sorry why 3 machines?
[13:29] <lazyPower> d4rkn3t: boostrap is machine 1 - i didn't co-locate juju gui, so thats machine 2 - the ubuntu service is node 3. by default juju assumes 1 service per node
[13:34] <d4rkn3t> I've just deployed juju-gui and make the status http://paste.ubuntu.com/7760176/, now i see also the second node
[13:35] <d4rkn3t> now also the second node is in allocated
[13:36] <lazyPower> sounds like things are progressing as they should
[13:36] <lazyPower> you can save yourself a node by deploying the juju-gui with '--to 0' to make it deploy on the bootstrap node
[13:36] <lazyPower> i just accepted teh juju quickstart defaults for simplicity sake
[13:37] <d4rkn3t> I've loose something why before the deploy I saw only 1 machines and after the deploy i see also the second one????
[13:38] <lazyPower> noodles775: Merged, thanks for the Readme update
[13:39] <d4rkn3t> i've tried to run the command juju deploy juju-gui --to 0 but receive this error "ERROR cannot add service "juju-gui": service already exists"
[13:39] <lazyPower> d4rkn3t: because juju is completely unaware of the maas pool, it just sends messages to maas requesting a machine.
[13:39] <d4rkn3t> lazyPower: ok, it's clear
[13:39] <lazyPower> d4rkn3t: you will have to juju destroy-service juju-gui, or deploy it with a different name (if you want 2 juju-gui's) deployed.
[13:40] <noodles775> lazyPower: great, txs.
[13:41] <d4rkn3t> i've destroyed it and the status now is  http://paste.ubuntu.com/7760210/""
[13:41] <lazyPower> noodles775: suggestion for the next update: use juju-run instead of juju ssh
[13:42] <lazyPower> juju-run is brilliantly handy
[13:43] <lazyPower> d4rkn3t: looks like agent 1 hasn't finished setting up. are you using the fastpath installer in maas?
[13:43] <d4rkn3t> yes
[13:43] <d4rkn3t> I'm seeing just now
[13:43] <d4rkn3t> ops!!!!
[13:43] <d4rkn3t> I've to wait
[13:44] <lazyPower> you can't be impatient :) We're orchestrating several layers of complexity here.
[13:44] <d4rkn3t> you right!!!!!
[13:44] <noodles775> lazyPower: I do use juju run for other things, not sure why I used ssh here. I'll switch it in the branch I'm working on :)
[13:44] <lazyPower> noodles775: its not a big thing, i just like promoting juju-run
[13:45] <lazyPower> noodles775: your juju-ssh line works ootb, and is just as brilliant. However i'm pushing the -run agenda here :P
[13:46] <noodles775> lazyPower: Yeah, we're using it to implement generic "actions" (like actions/reindex) so we can do `juju run --unit foo/0 actions/reindex` (until there's proper support for actions, I haven't checked recently).
[13:47] <lazyPower> noodles775: its coming but isn't here yet. we're taking similar actions against a few charms. cory_fu has done similar in the apache allura charm
[13:48] <noodles775> Cool, I'll try to check it out to compare and learn.
[13:48] <Caguax> juju switch maas
[13:48] <Caguax> ERROR couldn't read the environment
[13:48] <Caguax> Just install juju 1.20.0 and ran 'juju generate-config'. Edit the corresponding areas for maas but get the following after running 'juju switch maas' ;
[13:48] <Caguax> juju switch maas
[13:48] <Caguax> ERROR couldn't read the environment
[13:48] <lazyPower> Caguax: you have an error in your YAML
[13:49] <lazyPower> typically this is because you used a tab character instead of 4 spaces, but could be a number of things.
[13:49] <Caguax> lazyPower: hmm any log that help pih-point them ?
[13:49] <lazyPower> suggest to run it through a YAML linter
[13:50] <lazyPower> http://stackoverflow.com/questions/287346/yaml-validation  Caguax
[13:50] <Caguax> lazyPower: thanks...let me check that out
[13:50] <lazyPower> i would caution against using online yAML validators as you dont know what they are doing with the data. there's a few ruby/node.js listed linters in there
[13:54] <d4rkn3t> lazyPower: is there a way for juju to see the nodes added in the second time and start it in allocated status?
[13:55] <lazyPower> d4rkn3t: sounds to me like you want to allocate machiens to juju before you deploy. That emulates the manual behavior of juju - and will become cumbersome once you scale to gt 10 nodes.
[13:55] <lazyPower> i would advise against that
[13:56] <lazyPower> buti f you really want to go that route, by running juju add-machine, it will alloate the machine in juju
[13:56] <d4rkn3t> lazyPower: yes I'd like to make that, before to make the deploy of service
[13:56] <lazyPower> then you *have* to use juju deploy --to nodenumber   in order to deploy services, otherwise it will request another machine from MAAS
[13:57] <d4rkn3t> I've to use juju add-machine to inform juju I've added 1 more node to MaaS?
[13:57] <lazyPower> juju has no concept of maas other than it sends messages requesting a machine
[13:58] <lazyPower> juju add-machine will request the machine from maas, install the agent and leave it in an idle state, waiting for a service to be deployed to it.
[14:00] <d4rkn3t> perfect, but if I run the juju status I'd see the nodes available in my infrastructure!!!!!
[14:00] <lazyPower> d4rkn3t: there's maas-cli for that https://maas.ubuntu.com/docs/maascli.html
[14:00] <lazyPower> and the maas gui
[14:00] <lazyPower> but if thats what you want - i'm happy to say you've achieved that
[14:00] <lazyPower> :)
[14:01] <Caguax> lazyPower: Thanks...it was some space/tab thingie
[14:01] <lazyPower> Caguax: no problem - it gets me too.
[14:01] <lazyPower> Caguax: i find that when i edit in vim, if i show hidden characters while editing yaml, i'm about 90% more effective at not placing tabs vs spaces.
[14:02] <Caguax> lazyPower: Cool, will try that. thnks
[14:17] <d4rkn3t> lazyPower: I'd like to avoid to use always MaaS to see how many nodes I've available if I'm working with juju....
[14:21] <lazyPower> sinzui: grats on landing 1.20.0!
[14:22] <adeuring> d4rkn3t: the problem is that juju works also on public clouds (amazon/hp,azure/joyent etc). And these companies don't always want to say "we have a present 5000 machine idling and waiting for customers"
[14:23] <sinzui> thank you lazyPower
[14:24] <d4rkn3t> it's also true that!!!
[14:27] <d4rkn3t> but this is aspect that who works with juju should know, it's just my opinion!!!!! :-)
[14:27] <d4rkn3t> ops "but this is an aspect ..."
[14:30] <d4rkn3t> there should be  a way to see the available nodes presented on MaaS before to make the deploy of a service.....
[14:50] <d4rkn3t> lazyPower: thanks a lot for your technical support!!!
[14:51] <lazyPower> No problem d4rkn3t
[14:53] <d4rkn3t> allenap & noodles 755: thanks to you!! see y next time
[15:01] <d4rkn3t> hello again guys!but during the juju status I've seen this "agent-state-info: 'hook failed: "install"'" you can see all of that here "http://paste.ubuntu.com/7760515/" what does it mean?
[15:04] <lazyPower> d4rkn3t: something happened during the install hook that caused teh charm to fail. its now in a state that you need to resolve manually before it can proceed
[15:04] <lazyPower> you can either juju debug-hooks service/unit-number or you can juju resolved --retry service/unit-number to attempt retrying the hook to see if its temporary.
[15:05] <lazyPower> d4rkn3t: https://juju.ubuntu.com/docs/authors-hook-debug.html - see that for using debug-hooks
[15:06] <d4rkn3t> i've run "juju resolved --retry juju-gui/0" but i've receive any answer"""
[15:10] <lazyPower> d4rkn3t: you're either going to have to look through juju debug-log to see why it failed, or enter debug-hooks, run the install hook manually and find out why its failing
[15:10] <lazyPower> in either case, its going to require manual intervention if its not resolving itself when being retried
[15:12] <d4rkn3t> while the command "juju debug-hooks juju-gui/0" it' opened the terminal node! seeing in the machine-0.log there is this "ERROR juju runner.go:220 worker: exited "api": websocket.Dial wss://localhost:17070/: dial tcp 127.0.0.1:17070: connection refused"
[15:16] <d4rkn3t> after that now it's in started (http://paste.ubuntu.com/7760573/)
[15:16] <d4rkn3t> ?????
[15:19] <lazyPower> d4rkn3t: not sure why you got the API connection refused - but if its in started, you should be able to visit the GUI now.
[15:19] <lazyPower> can you try it and see if its pulling up for you or if it resolved without fixing the error?
[15:19] <d4rkn3t> the url to use it "MaaSCCSvr1Node1.maas"
[15:21] <d4rkn3t> the answer is "The page you are looking for is temporarily unavailable.
[15:21] <d4rkn3t> Please try again later." and the url is changed in "http://cdn.spotflux.com/50x.html"
[15:22] <lazyPower> ok, not sure whats going on. I would recommend to destroy the service and machine, and start over on the GUI deployment - so we can troubleshoot from step 1
[15:22] <lazyPower> if it fails install a second time, instead of trying resolved -r, issue a juju debug-hooks and re-run the install hook
[15:23] <d4rkn3t> ok
[15:38] <Caguax> I this a timeout issue ?
[15:38] <Caguax> ERROR juju.cmd supercommand.go:323 cannot initiate replica set: Closed explicitly
[15:39] <Caguax> https://gist.github.com/luflores/11fa3c6b4af78b6bd503
[15:49] <d4rkn3t> lazyPower: I've destroyed the service, I'm trying to destroy also the environment to re-start from the begin but I can't make this step. juju gives me this error "ERROR failed to destroy environment "maas"
[15:49] <d4rkn3t>         
[15:49] <d4rkn3t> If the environment is unusable, then you may run
[15:49] <d4rkn3t>     juju destroy-environment --force"
[15:50] <d4rkn3t> i made also the --force but nothing
[15:56] <lazyPower> if juju destroy-environment maas --force isn't working for you then there are larger problems manifesting here that are outside my realm of knowledge
[15:56] <lazyPower> that should forcibly destroy your juju environment with a large hammer with great predjudice.
[15:59] <Delair> I deployed neutron-gateway in kvm and and rest of the services including nova-compute on another server just for testing. Everything is deployed but i cant see the neutron service running when i login to openstack dashboard
[15:59] <Delair> do i need a relation from neutron-gateway to keystone
[16:22] <adeuring> utlemming: Today's Juju/Vagrant images don't work after a reboot: ISTM that the call of /root/redirect.py is missing again, so that port 8001 of the virtualbox is not forwared to 80 of the LXC instance of the GUI
[16:23] <utlemming> aduering: do you have a paste of the Juju output?
[16:23] <utlemming> adeuring: er, I mean the console of "vagrant up"?
[16:24] <adeuring> utlemming: http://paste.ubuntu.com/7760876/
[16:28] <utlemming> adeuring: looking...slow download today
[16:50] <jrwren> anyone else getting much rsyslog messages to /var/log/syslog on machines?  http://paste.ubuntu.com/7760981/
[17:43] <sebas5384> hey lazyPower! o/
[17:55] <Caguax> I am trying to run 'juju quickstart' to test my installation but it is failing with a 'DEBUG juju.mongo open.go:87 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused' Anyone have seeing this ?
[18:01] <lazyPower> o/ hey sebas5384
[18:03] <sebas5384> lazyPower: when you can, please take a look at this drupal charm? https://github.com/sebas5384/charm-drupal
[18:03] <sebas5384> :)
[18:06] <sebas5384> I release a 0.5 version, and now I'm going to do some other relations, like varnish, etc...
[18:07] <Caguax> I most be doing some obvious thing wrong but juju quickstart does not work on 1.20
[18:11] <lazyPower> sebas5384: I don't see it in the review queue. https://juju.ubuntu.com/docs/authors-charm-store.html
[18:13] <sebas5384> lazyPower: yeah, for that i have to use bzr ?
[18:13] <sebas5384> launchpad
[18:13] <lazyPower> Thats the officially supported method.
[18:15] <sebas5384> hmmm
[18:16] <sebas5384> lazyPower: ok then ¬¬
[18:16] <lazyPower> Sorry sebas5384. Everybody else does it - its easy to lose track of things if it's not in the queue.
[18:16] <lazyPower> in the future github will be a supported source and ease the process.
[18:17] <sebas5384> yeah I can imagine that! ;)
[18:24] <hasues> Does anyone have a working juju after deploying from github?  I can't seem to execute generate-config or anything else without errors?
[18:45] <lazyPower> hasues: if you're working on -HEAD of juju-core, you want want to ask in juju-dev
[18:49] <hasues> lazyPower: Well, I merely used "go get -d -v github.com/juju/juju/...", does that pull -HEAD?
[18:52] <lazyPower> hasues: i would think so, but i dont know.
[19:18] <sebas5384> ok now, that was easy https://code.launchpad.net/~sebas5384/charms/precise/drupal/trunk
[19:18] <sebas5384> :)
[19:57] <jrwren> juju-charm getall  # might not have been a good idea for me
[19:58] <lazyPower> jrwren: mirroring the charm store, one charm at a time :)
[19:59] <jrwren> Grabbing 164 charms from Charm Store
[20:00] <rick_h__> jrwren: how goes?
[20:00] <jrwren> rick_h__: I'm squashing bugs.
[20:00] <jrwren> rick_h__: I'm enjoying it :)
[20:01] <jrwren> rick_h__: learning a lot too. e.g. first time with debug-hooks
[20:01] <jrwren> rick_h__: welcome back :)
[20:01] <rick_h__> jrwren: heh, just got in the door in time for a meeting
[20:01] <rick_h__> jrwren: cool on bug squashing
[20:20] <michelp> sebas5384, cool!  ansible integration :)
[20:20] <sebas5384> thanks michelp !!
[20:20] <sebas5384> :)
[20:20] <sebas5384> ansible rocks! \o/
[20:42] <jrwren> i read https://juju.ubuntu.com/docs/authors-relations-in-depth.html and https://juju.ubuntu.com/docs/authors-charm-interfaces.html and I'm left with the question about optional or default value interface fields. Is that a comming thing?
[20:51] <jrwren> common thing?
[21:23] <jrwren> because: https://bugs.launchpad.net/charms/+source/mysql/+bug/965094
[21:23] <_mup_> Bug #965094: Provide config option to specify database encoding <mysql (Juju Charms Collection):Confirmed> <https://launchpad.net/bugs/965094>
[21:25] <sebas5384> [!] question: the charm icon only appears if the charm is recommended?
[21:26] <lazyPower> sebas5384: correct
[21:26] <sebas5384> damn it ¬¬
[21:26] <sebas5384> hehe
[21:31] <jose> cory_fu: ping
[21:58] <cory_fu> jose: Hey, what's up?
[21:58] <jose> cory_fu: hey, I got to reproduce the error with allura, if you want I can give you ssh access to the machiens
[21:59] <cory_fu> jose: My public ssh key is up on Launchpad
[21:59] <jose> awesome! give me just a minute
[22:52] <cory_fu> jose: Thanks again for helping me figure out the issue with the Allura charm.  You're the man.  :)
[22:52] <jose> not a prob :) glad I could give a hand!