[00:00] <zradmin> just created a test user and was able to authenticate to maas through the webpage
[00:06] <davecheney> zradmin: via juju
[00:24] <zradmin> ah ok so create another api user and stand up a second juju environment?
[00:39] <arosales> zradmin, that is how I read davecheney suggestion
[00:40] <zradmin> yeah, I'm setting it up currently
[00:41] <arosales> zradmin, cool
[01:06]  * arosales grabs some dinner
[06:15] <AskUbuntu> Creating a charm | http://askubuntu.com/q/380207
[08:16] <ankrj> Hello everyone!
[08:18] <ankrj> What kind of an environment do I need t osetup in order to start writing charms?
[08:43] <jaywink> ankrj, you will find everything you need here: https://juju.ubuntu.com/docs/authors-charm-writing.html
[11:46] <makara> hi. Juju sounds like a good idea, but I'm skeptical
[11:47] <makara> suppose I want to deploy a Wordpress instance
[11:48] <makara> what type of instance would I get? I just want a microinstance - the smallest, least powerful option
[11:49] <makara> but I've been having trouble with Wordpress because it keeps the siteurl in it's DB, and then when I associate the instance with a static IP, the DNS changes, and Wordpress breaks
[11:50] <makara> since juju is the to cloud what apt is to a system, changing an IP address would be like messing with the directories APT installs to
[11:51] <makara> what are your experiences?
[12:13] <makara> how can I deploy an EC2 t1.micro instance instead of an m1.small instance?
[12:15] <makara> terminal hangs after: juju deploy --to 0 wordpress
[12:15] <makara> ctrl+c
[12:15] <makara> juju status
[12:15] <makara> hangs
[12:44] <mthaddon> makara: you can specify whatever instance size you want - that's independent of the charms you're deploying (e.g. wordpress or mysql)
[12:45] <mthaddon> makara: see https://juju.ubuntu.com/docs/charms-constraints.html
[12:47] <makara> mthaddon, ok thanks, but I have another problem now
[12:48] <makara> juju is hanging
[12:48] <makara> so I go "juju status" and it doesn't give me anything
[12:49] <mthaddon> it may be that the instance is too small to run juju and wordpress - but I'm not sure of the best way to troubleshoot unless you already know the IP and can login to the instance to diagnose
[12:59] <makara> mthaddon, juju is running on my own machine
[12:59] <makara> i'm deploying an m1.small instance
[12:59] <makara> it deploys it, but then juju hangs
[13:00] <mthaddon> well, you're using the juju client from your own machine, but juju itself is running on the m1.small instance
[13:00] <mthaddon> so I'd try to login to that instance directly and troubleshoot - I assume this is EC2 and you can use other tools to figure out the IP of the instance, etc.
[13:44] <makara> mthaddon, ok, well if I have to do that then first impressions aren't going very far
[13:44] <makara> its why I would want to use Juju in the first place
[13:45] <mthaddon> fair enough - I'm not a juju developer, just a user like yourself, so others may have better troubleshooting advice
[13:57] <marcoceppi> makara: what version of juju are you using (juju version) ?
[14:00] <makara> marcoceppi, 1.16.3-raring-amd64
[14:01] <marcoceppi> makara: awesome, you've got the latest. You shouldn't expereince problems deploying to amazon, sorry you're having a poor first time experience
[14:01] <marcoceppi> makara: so what happens when you run `juju status --debug --show-log` ? Could you paste that to http://pastebin.ubuntu.com
[14:01] <marcoceppi> makara: it may help us debug what's going on
[14:03] <makara> marcoceppi, there's a bit too much revealed in this log for my liking
[14:04] <marcoceppi> makara: you can mask IP addresses or PM me if you want it outside of the channel
[14:05] <makara> marcoceppi, its private key data, security keys, etc
[14:05] <makara> marcoceppi, i've taken that out: http://pastebin.ubuntu.com/6453412/
[14:23] <ashipika> hello juju world..
[14:24] <ashipika> manual provisioning.. bootstrapped one host, added another.. both ubunu 12.04.. tried deploying tomcat7.. but it is stuck in pending state
[14:25] <ashipika> and for the second machine i added it says instance-state:missing
[14:27] <ashipika> any ideas?
[14:27] <marcoceppi> makara: is i-d3b6399c actually running on your account right now?
[14:34] <marcoceppi> ashipika: can you ssh in to that machine? the instance-state:missing?
[14:34] <marcoceppi> ashipika: also, manual provisioning is still very much under development
[14:35] <ashipika> i can ssh manually, yes.. but not via juju
[14:35] <ashipika> Permission denied (publickey,password).
[14:36] <marcoceppi> ashipika: that's fine, manually ssh for now
[14:36] <ashipika> but how come the state is missing?
[14:37] <marcoceppi> ashipika: that's what I'm trying to help you figure out
[14:37] <marcoceppi> ashipika: again, manual provisioning is not a stable juju feature yet
[14:37] <ashipika> i understand that.. how can i help decypher this problem?
[14:38] <marcoceppi> ashipika: again, ssh in to the server and I can help you troubleshoot the problem :)
[14:38] <ashipika> i'm in :)
[14:38] <marcoceppi> ashipika: run `initctl list | grep juju` what do you get?
[14:39] <ashipika> jujud-machine-4 start/running process 2869
[14:40] <marcoceppi> ashipika: can you install pastebinit then run `cat /var/log/juju/machine*.log | pastebinit`
[14:41] <ashipika> http://paste.ubuntu.com/6453560/
[14:42] <marcoceppi> ashipika: that's the problem
[14:42] <marcoceppi> ashipika: where is the bootstrap node?
[14:42] <ashipika> on another machine.
[14:42] <marcoceppi> ashipika: is that other machine your local machine?
[14:42] <ashipika> no
[14:43] <ashipika> the bootstrap machine is at 192.168.1.108, while this machine is 192.168.1.110
[14:43] <marcoceppi> ashipika: the address it's getting for the bootstrap node is ubuntu.; this leads me to believe that the bootstrap node doesn't have proper hostname setup for it
[14:43] <marcoceppi>  dialing "wss://ubuntu.:37017/"
[14:43] <ashipika> oh! it's trying to contact mongodb at ubuntu.?
[14:44] <marcoceppi> ashipika: well, it's trying to contact the bootstrap API at ubuntu.
[14:44] <ashipika> ok
[14:44] <marcoceppi> which connects to mongo, so essentially yes
[14:44] <ashipika> so i need to fix hostname at the bootstrap host?
[14:44] <marcoceppi> ashipika: it's got a bad address resolution. make sure the bootstrap machine has proper hostname that's mappable in the system
[14:44] <marcoceppi> yeah
[14:45] <ashipika> why not ip? why hostname?
[14:45] <marcoceppi> ashipika: what did you set as the bootstrap node for the manual provisioner?
[14:45] <marcoceppi> again, improvements to this feature are being made
[14:45] <marcoceppi> this isn't the final product for manual provisioning
[14:45] <ashipika>  maas-server: 'http://192.168.1.1/MAAS/'
[14:45] <ashipika> in the .yaml file
[14:46] <ashipika> sorry.. wrong file..
[14:46] <ashipika> but i set the ip for the boostrap-host: 192.168.1.108
[14:46] <marcoceppi> interesting
[14:46] <marcoceppi> ashipika: can you `cat /var/log/cloud-init/*.log | pastebinit`
[14:47] <ashipika> on the bootstrap server?
[14:47] <marcoceppi> ashipika: on the machine-4
[14:47] <ashipika> no cloud-init folder in the log folder..
[14:47] <marcoceppi> how about a cloud-init.log in /var/log?
[14:48] <ashipika> nope
[14:48] <marcoceppi> hum, cloud-init had to run somewhere on that machine
[14:49] <ashipika> i can't see any logs
[14:51] <marcoceppi> ashipika: apt-get install tree, `tree /var/log | pastebinit`
[14:52] <ashipika> http://paste.ubuntu.com/6453610/
[14:55] <makara> marcoceppi, no, I terminated it
[14:56] <marcoceppi> makara: okay, well run juju destroy-environment to clean up, then try bootstrapping again. This time use --debug and --show-log flags. If after a few moments you can't run juju status and get output, sanitize the log and paste it for me
[14:57] <marcoceppi> ashipika: interesting. No cloud-init log anywhere. Regardless, update the host of your bootstrap node, stop the juju-machine-4 upstart, delete /etc/init/juju-*, then try adding it again
[14:58] <ashipika> ok.. thank you very much
[14:59] <makara> marcoceppi, I'll post it tomorrow 6 UCT
[14:59] <marcoceppi> makara: I'm EST (UTC-5) so I won't get it for a few hours, but I'll look for it when I awake
[14:59] <makara> k
[15:49] <X-warrior> is anybody using elasticsearch/logstash with juju? I'm trying the elasticsearch charm but it is failling
[15:51] <marcoceppi> X-warrior: I know it's been deployed a few times, where is it failing?
[15:51] <X-warrior> on deploy, the hook start is failling ' HOOK WARNING: ElasticSearch may have failed to start.'
[15:54] <marcoceppi> thats not very helpful
[15:57] <X-warrior> I guess it is not juju faults, it is something related to ElasticSearch, let me dig into it
[15:57] <X-warrior> brb
[18:37] <x-warrior> What does this means? "ERROR no CA certificate in environment configuration" ?
[18:39] <x-warrior> I'm able to connect to one environment, but when I try to connect to otherone, I receive this error
[18:50] <marcoceppi> x-warrior: did you bootstrap from that machine or another machine?
[18:50] <x-warrior> marcoceppi, another machine
[18:51] <marcoceppi> x-warrior: yeah, that's why
[18:51] <marcoceppi> x-warrior: you need to copy the certs from that machine to this one
[18:51] <x-warrior> you mean .ssh certs?
[18:51] <x-warrior> because I'm able to ssh directly to the machine
[18:51] <x-warrior> without using juju
[18:57] <x-warrior> marcoceppi, have to go now, talk about this with u tomorrow, have a good one
[18:57] <x-warrior> ty
[20:15] <InformatiQ> i was searching for a directory server in the charm store, didn't find anything i know. anyone has an idea if there is one?
[20:16] <InformatiQ> i would tend to see that as an important part