User1: $JUJU_HOME/bin/juju bootstrap -v --debug --upload-tools would return 2014-02-13 00:35:41 ERROR juju.cmd supercommand.go:294 failed to enable bootstrap storage: failed to create storage dir: exit status 255 (Permission denied (publickey,password).)
User1: anyone knows reasons/solution for this ?
User1: ERROR juju.cmd supercommand.go:294 failed to enable bootstrap storage: failed to create storage dir: exit status 255 (Permission denied (publickey,password).) - how to workaround this?
User2: User1 sounsd like you're using the wrong public key?
User3: Can anyone point me to a charm which streams data (in my case, a log file) to another service? netcat would work but doesn't have the security I'd want.
User4: User3 there are rsyslog charms
User4: User3 http://manage.jujucharms.com/charms/precise/rsyslog
User3: Ta.
 * stub wonders about serializing his logs and using syslog as the transport
User5: User6 hi there, I'm trying to understand what https://pypi.python.org/pypi/amulet/1.2.1 is lp:amulet where there is no 1.2.1 tag, can you help ?
User3: Gah, I've got logging backwards
User3: My charm needs to 'require' syslog in order to emit log messages to a receiver that 'provides' syslog
User3: I think the rsyslog charm was written from the POV of syslog being a service, when I'm thinking of it as a protocol
User3: But I guess that way makes sense if we start running hooks in a better defined order, provider side hooks first
User6: User5 amulet is mirrored on launchpad, but hosted on github
User6: User5 https://github.com/marcoceppi/amulet/releases
User5: User6 but https://github.com/marcoceppi/amulet.git/ doesn't have the 1.2.1 tag either ... what am I doing wrong >-/
User6: User5 it's there, hard refresh?
User5: User6 that made it, glitch since yesterday evening I suppose... Anyway,
User5: User6 thsnks
User6: User5 np
User5: hehe, thanks (damn fingers)
User5: User6 I'm also trying to find where I can get an ubuntu packaged version for that, I'm using ppa:juju/devel but amulet is not there (and I need support for precise, saucy, trusty, /me sighs, life is complicated sometimes... ;)
User6: User5 tools are in juju:ppa/stable :)
User6: and it's built for precise, saucy and trusty
User5: \o/
User5: User6 can I mix ppa/stable with juju 1.17.2 ?
User6: User5 yes, so if you have devel ppa, you'll always get the lastest juju as juju 1.17.2 > 1.16.6
User6: but when the next stable release comes out, 1.18.0 it'll get installed over 1.17.2
User6: since we do devel and stable releases differently
User6: evens are stable, odds are devel
User5: User6 cool, thanks for the tip about juju/stable, I could find it on lp from lp:amulet :-/
User6: as such, having both ppa won't break anything
User6: User5 I'll update the project page, thanks for the feedback!
User5: User6 oh, ok, good to know (I hope I will remember that odd/even in this context...)
User7: when joining the db-admin relation with postgres, the user does not get the right to create new databases?
User6: User7 uh, the user /should/
User7: when I do "SELECT rolcreatedb from pg_roles where rolname like 'db_admin%';", all are flase
User7: *false
User6: User7 give me a few mins to spin up the latest postgres charm and check
User7: sure, mine says 'cs:precise/postgresql-61'
User7: just in case it matters
User6: User7 that appears to be the latest
User7: ok, that's interesting, it might be the pg_hba.conf interaction with the local environment again, as trying to create it in psql works now
User7: and he does have rolsuper, that should give the user right to do anything?
User6: User7 yeah, db-admin gives you superuser permissions
User6: so you should be able to romp around and create a database, etc
User7: User6 thanks, and sorry for the false alarm, it was caused by postgresql restoring my changes to pg_hba.conf after a while
User7: if doing deployment from local: and I've fixed bugs in the charm, how do I get them to be picked up? do I have to update revision? just removing the service and redeploying it again still uses the old version and there is nothing in .juju/charmcache
User6: User7 yeah, from local, run juju deploy -u --repository... local:...
User6: the -u will update the cache
User8: User6 doc your way with working dual local lxc environments
User6: User8 \o/
User8: now that I've got this I want cross env relations :P
User7: User6 so the proper way is changing the revision, thanks
User6: User8 dont' we all :)
User7: when generating default passwords, is there a way to communicate them to the user?
User6: User7 no, we strongly recommend you not auto-generate passwords and have users set it via config.yaml
User6: User7 you can juju-log it, or place it in a file on the server and tell the user to ssh + cat that file though, again not recommended
User7: but what if they do not set it?
User6: User7 you can have the config-changed hook exit 1, to alert the user of an error, or have it exit 0 while it waits for the user to change/set the password
User9: marcoceppi, so at the sprint people were making fun of me because I had to keep blowing away .jenv files
User9: http://joshstrobl.blogspot.com/2014/02/developing-ubuntu-juju-charm.html
User9: I feel vindicated knowing I wasn't the only one with broken local provider
User10: Thanks jcastro_, I'll go ahead and sign up in the juju mailing list and take part in the discussion!
User6: User10 its not local either
User6: err jcastro_^
User9: we should name this script thumper.sh: http://pastebin.com/UMeZdH0Y
User6: User9 ha!
User9: JoshStrobl, this is sweet feedback dude
User6: User9 HOLY CRAP DUDE
User11: niceeee
User10: User9 Just figured I'd share my experience writing a charm =)
User6: User9 please don't recommend that script
User6: User9 great way to loose your entire environments.yaml
User11: its pretty destructive without any kind of warning
User10: But yea, it was a bit of a pain setting up the environment, destroying it, etc.
User10: marcoceppi and lazyPower_ that is the point
User12: User10 oh i'm aware of that, but some people just run scripts blindly
User6: User10 some of us have more than one environment in environments.yaml :)
User12: ^
User10: I did it because whenever my charm failed to be installed properly and I went to kill the service, it would just put the state as "dying" the entire time, I couldn't kill it without destroying the environment.
User9: my point was mostly "we suck at cleanup so badly someone had to write a script."
User6: User9 yeah, I agree
User9: lazyPower, actually, weren't you writing a "nuke it from orbit" plugin?
 * marcoceppi makes a cleanup plugin
User12: User9 i dubbed it "The Atom Bomb"
User13: Are there best practices for accessing private bzr branches from LP from a service node?  The most obvious strategy seems to be to create a bot user and copy around a private ssh key but that thought alone I suspect makes kittens cry
User10: I couldn't even use destroy-machine because the charm was stuck as dying.
User12: and yeah - Its still in my slack task listing
User6: User10 there's a force flag for that
User6: User10 juju terminate-machine --force #
User10: User6 I'd trying that out, but thanks to you being so helpful (bad marcoceppi, bad!), my charm works.
User10: So I'll need to intentionally break the charm to test if that works :P
User10: marcoceppi and jcastro_ I'll update my blog with the update you provided, provide some warnings about the script, and join the juju mailing list. My fiancee and I are going to a dance however, so I'll be afk!
User10: *with the update, as in the quickstart stuff.
User6: JoshStrobl[afk]: enjoy!
User6: User9 here's pretty much all you need for a clean up: https://gist.github.com/marcoceppi/8977344
User12: User6 not sure about recent revisions of juju as i haven't had any issues, but with 1.17.0 i had to nuke ~/.juju/$env in the case of local as well. just removing the .jenv wasn't enough.
User6: User12 OHH, yeah, good point
User6: User12 https://gist.github.com/marcoceppi/8977344
User12: User6 and then there's the case where it wasn't destorying the lxc containers...
User6: User12 well, that's been fixed in 1.17
User12: you've basically just written the nuke plugin once you've done that. parse the env name out of the lxc-ls --fancy and bam.
User12: yeah, i agree, its no longer really required.
User12: someone was dilligent in getting that patched, and i send them all the <3 in the world for that.
User6: User12 probably thumper, at least that's who I always blame the lxc stuff on ;)
User6: So, I'm about to make a juju-plugin plugin which downloads...plugins
User6: much like npm, but for juju, because that seems the sanest way to package plugins
User12: +1
User12: Are you going to be hosting the API that powers this?
User12: or just parse launchpad data?
User6: User12 free for all
User6: User12 so you can host it on github, gist, lp, where ever
User6: User12 hosted
User12: brilliant
User6: open source, etc
User6: just going to have the plugin create a $JUJU_HOME/plugins directory, and have it added to the users path
User9: marcoceppi, do you know if we still support firing off a specific AMI for the AWS provider?
User9: we used to iirc.
User6: User9 I don't think we've supported that since the goland rewrite, let me check the source doe
User6: code*
User6: User9 so you /could/ if you created simplestream data and overwrote the canonical stream data
User6: then you could have it use another AMI
User14: marcoceppi, Are the machine logs for hp cloud stored on my local machine?
User6: User14 no, they're in the bootstrap node
User6: User14 the only reason machine logs are stored on your machine is if you're using the local provider because your laptop/desktop becomes the bootstrap node
User14: OK
User14: all-machines.log?
User15: hi, when i try to deploy a service on a machine with "juju deploy mysql --to lxc:0" it says "container creation template for juju-machine-0-lxc-0 failed"
User14: in /var/log/juju/ ?
User15: the output, of "juju status" in detail is: http://pastebin.ubuntu.com/6926247
User9: marcoceppi, excellent
User6: User9 haven't tested that, but it shoudl work
User6: User15 which provider?
User9: ok so not impossible
User6: User14 machine-# is where the machine logs are
User6: User15 nvm, I see you're on maas
User15: User6 what do you mean "which provider" please have a look at the output of "juju status":  http://pastebin.ubuntu.com/6926247
User6: User15 does this machine have outside network accecss?
User6: machine being cloud1.master
User15: User6 yes
User6: User15 well, the error states "failed to get https://cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt"
User15: User6 that should be fixed with help from #maas because the nodes were able to resolve all packages while booting after i executed a bash script to do some NAT
User6: User15 so, ssh in to that machine and try to wget that URL
User15: so i should enter this command on the bootstrap node?
User6: User15 yup
User15: or any other url?
User6: User15 that cloud-images url
User15: it answers with "password:"
User6: User15 that's...what?
User15: i have to type this command on the console of the juju bootstrap node, right?
User15: so, i typed this command in and the response of the console is "Password: "
User6: User15 so, you should just be able to type juju ssh 0 from wherever you ran juju bootstrap
User6: that should SSH you into the node
User6: then you should just type `wget  https://cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt`
User15: aha
User15: ok
User15: because i have the physcial node beside me, so i typed this command with node's keyboard ;)
User6: User15 right, and maas removes the passwords, so you can't just log in
User15: ok, i have tried ssh now it prints "shannoncoleman@example.com's password: " on maas-server console
User6: User15 did you add your ssh key to maas?
User15: yes
User15: so i have to add sth to "ssh cloud1.master" ?
User6: User15 well `juju ssh 0` should try to ssh shannoncoleman@example.com
User6: not sure why it says shannoncoleman@example.com
User15: it says master because i use DNS resolving
User15: provided by maas server
User6: User15 not sure why it says thomas instead of ubuntu
User15: OK
User6: it should be using the ubuntu user to ssh you in when you run `juju ssh 0`, could you run `juju ssh --show-log --debug 0` ?
User6: and paste the output
User15: kk
User15: k, i tried "juju ssh 0" it says "permission denied (publickey, password)
User6: User15 yeah, so it doesn't have your ssh keys on there
User15: i have followed the installation guide... i have created an ssh key
User15: andd added with "+ add ssh key" to preferences of root
User6: User15 can you run `ssh -vvv shannoncoleman@example.com` and pastebin the output
User6: User15 and the ssh key is on the machine you're running the juju command from, correct?
User15: yes, its on the maas-server-node
User6: User15 cool, so you're running these commands from the maas-master
User15: yes
User15: output: http://pastebin.ubuntu.com/6926349
User15: oh
User15: this id_rsa.pub... is this the ssh key which should come into maas-dashboard?
User15: because i have another ssh key created some time ago, and its file name is different and its location too...
User6: User15 so, yeah, the ssh id_rsa.pub file that's on this machine in the thomas user should be the one in the dashboard
User15: ok, s***
User6: add it, juju destroy-environment maas, rebootstrap, then try to deploy --to lxc:0 again
User6: User15 if it fails, again, then do the ssh and check to make sure you can get that url
User15: ok
User6: User15 no worries man! you would have hit this issue sooner or later ;)
User15: iam such an idiot, if this is the cause of the issue, i have wasted lots of hours. xP
User15: but Thank You so far !!!
User6: User15 np, feel free to ping me when you get going again. I don't think that's why the lxc container failed, but it's hard to troubleshoot if you can't get to the node
User15: User6 ok ty
User15: User6 hmm, i have changed that ssh, destroyed juju and rebootstrapped but there is still sth wrong: http://pastebin.ubuntu.com/6926519
User15: ok, last try for today, i have deleted all keys in .ssh and created a new one with the command "ssh-keygen -t rsa", rebootstraping now...
User15: User6 ok, i could login now to the node and i tried wget but i get "failed: no route ho host"
User6: User15 ah, I know this issue!
User6: User15 you need to configure your DNS server to foward requests
User6: quick fix, on the maas-master
User6: User15 open /etc/bind/named.conf.options on maas-master
User15: kk!
User6: and add the following bit
User6: http://paste.ubuntu.com/6926815/
User6: User15 you should see it commented out currently
User6: just uncomment and set the dns server to something, lik 91.69.162.6
User15: User6 no its not uncommented, its 91.69.162.6
User15: i told u from a bashscript to NAT right?
User15: i guess the NAT script has caused to set this IP as DNS
User6: User15 you're using the micro-cluster scripts?
User15: gimme a sec plz
User15: i have executed this script on maas-server: http://pastebin.ubuntu.com/6926827/
User15: there is a line: dnsserver="91.69.162.6"
User6: User15 yeah, that's from the micro-cluster scripts
User6: User15 can you actually dig @ that address?
User6: User15 ie, `dig @91.69.162.6 google.com` from the maas-master
User15: yes, i guess, "query time: 1022 msec"
User15: 1 server found
User15: but a question: is the dns-server of the node not simply the maas-dns-server?
User15: so 91.69.162.6 ?
User15: because i have set "manage dhcp + dns"
User15: instead of 91.69.162.6, which is dns-server from the maas-server
User6: User15 right, so basically the nodes will use your maas-master as DNS, but that DNS server needs to forward requests that it dosn't know about to an outside DNS server
User6: otherwise you'll get no route to host
User15: hmm ok , what does this mean? do i have to edit resolvconf on ssh node and add 91.69.162.6 (maas-server) as dns-nameserver=
User15: ?
User15: aaaahhh 91.69.162.6 is already written in resolv.conf of the node
User15: hmm
User15: this is, what my "interfaces" file on the maas-server looks like: http://pastebin.ubuntu.com/6926866
User15: dns-nameservers: 91.69.162.6 seems wrong, not?
User15: (eth0 connects the server to the nodes, eth1 connects the server to the i-net)
User6: User15 yeah, that dns-server should be the outward facing dns-server
User6: dns-nameserver*
User15: kk
User6: User15 then you'll have to restart networking
User15: k
User15: hmm still no route to host
User15: whe i start bootstrapping, i have to manually power on the node which is allocated in maas
User15: so, when i power off the node, and power on it again, does juju still work on that node?
User15: (i have also rebooted maas-server in meantime xP)
User6: User15 it should, unless the node has been set to stopped in maas
User15: kk
User15: but now, i see on the nodes console "cloud1 login:" but it seems it is not finishing...
User15: u know what i mean?
User15: normally, after this line, the node goes on and at the end it prints "cloud init" or sth like that
User6: User15 is this after a bootstrap or just a powercycle post bootstrap?
User15: just powerxycle
User6: User15 that's noraml
User15: ok, but when i hit "juju status" i get no answer in maas-server...
User15: it seems to stuck some way
User15: i cant even login too
User6: User15 so, you see cloudinit the first time because it's provisioning juju and installing a bunch of stuff, however, it's already done that so it just boots up and runs
User6: User15 can you ssh shannoncoleman@example.com ?
 * JoshStrobl thinks he may have been a bit overkill in the length of his response on the Juju mailing list :S
User15: no it says "could not resolve hostname cloud1.master: Name or service not known"
 * marcoceppi goes to review the overkill
User6: User15 so, can you run ssh -vvv shannoncoleman@example.com and pastebin the output?
User15: "interfaces" on master: http://pastebin.ubuntu.com/6927005
User15: maybe i have to add "master" in search line?
User15: ah...
User6: User10 fantastic feedback!
User10: Thanks
User6: thank you!
User15: it should spelled "dns-search" and "dns-nameservers" and not "search" and "nameserver" ... xP
User10: User6 In case you didn't get the notice on G+, I went ahead and updated the blog post to suggest your script as well. I described mine as an atom bomb to a problem that can be solved with a screwdriver :P
User6: User10 cool, I'm taking a few mins to work on making installing plugins for juju a lot easier too, as well as addressing some of the documentation concerns you brought up
User6: Unfortuantely our copywriter is out, so things like quickstart which are relatively new haven't been documented yet
User10: User6 That's understandable. Better to know now then never I suppose! :P
User15: User6 http://pastebin.ubuntu.com/6927050
User6: User15 what does dig cloud1.master present?
User15: User6 http://pastebin.ubuntu.com/6927064
User6: User15 what does /etc/resolve.conf look like on maas-master?
User15: User6 http://pastebin.ubuntu.com/6927078 and "interfaces": http://pastebin.ubuntu.com/6927082
User6: User15 move 91.69.162.6 to the first line
User6: also, which DNS server is the one you actually use?
User6: 140.21 or 176.16 ?
User15: dont know
User6: whichever it is, that's the one that needs to be in /etc/bind/named.local.options
User6: as it'll be the one that forwards requests, I'm guessing 91.69.162.6 considering the output of dig
User15: ok its 91.69.162.6 , i did "dig www.google.com | grep SERVER"
User15: can i simply edit resolv.conf?
User6: User15 you can, but it'll eventually get re-generated
User15: re-generated, but only after reboot?
User6: User15 and other certain times
User15: oh ok...
User6: User15 the best way is to edit /etc/resolvconf/...
User6: uh, I forget the file name, one second
User15: head?
User6: User15 yeah, /etc/resolvconf/resolv.conf.d/head
User6: that's a good one to start with
User15: and then reboot :-)
User15: yep
User15: working
User15: can login again :-)
User15: but no route to host :(
User6: User15 yeah, so you'll need to update the forwarders rule in the /etc/bind/named.local.optoins to the right dns server
User6: restart bind, then try again
User15: good point, but the ip is already correct
User15: 91.69.162.6
User6: well, something's messed up along the line there
User15: u meand named.conf.options?
User6: User15 for the sake of, something or another, from maas-master run `dig @91.69.162.6 google.com`
User15: btw, i have to run the bash script again it seems, because nat table iptables is empty ^^
User15: i always have to run it, if i reboot the maas-server tbh
User15: has sth to do with my old server version i guess
User15: when i execute this bash script, do i have to reboot, restart network service or sth like that?
User6: User15 nope, it should do all that for you
User15: kk
User6: User15 so, dig @91.69.162.6 google.com; did that work?
User15: "dig @91.69.162.6 google.com" > connection timed out; no servers could be reached
User6: darn, okay
User15: ?
User6: User15 well I was going to say you could just use another DNS server, but you can't because of your network location
User15: but i can connect to i-net on my maas-server
User6: User15 right, but some networks block exterior nameserver lookups
User6: which is happening in your case
User15: interesting: when i try "ping 91.69.162.6" on my node, it says "destination host unreachable"
User6: User15 it might not be listening to pings
User15: but "ping 91.69.162.6" works
User15: and "ping 91.69.162.6" works also from maas-server
User6: User15 right, because your bind instance isn't configured to not respond to pings
User6: OH, on your node
User15: yes, on the maas-server, i can ping 91.69.162.6 and 91.69.162.6
User15: from the juju-bootstrap-node, i can only ping 91.69.162.6
User15: so it seems there is some NAT problem?
User15: in the bash-script, eth0 and eth1 are not confused or sth like that? iam not that familiar with iptables-statements
User15: eth0 = connects the server to the nodes via switch, eth1 = connects the server with internet
User6: User15 oh, maybe that's what's up
User6: the script assumes something else
User15: kk
User15: so, i guess i need other NAT- and forwarding statements?
User6: User15 one sec, link the script you're using again?
User15: User6 kk, link is: http://pastebin.ubuntu.com/69227311
User15: User6 sorry, wrong address.... correct: http://pastebin.ubuntu.com/6927311
User6: User15 you should uncomment sysctl --system
User6: also, you should install iptables-persist
User6: and write the rules to it, so they survite restarts
User6: so, install iptables-persist, then run the nat script, then run `iptables-save > /etc/iptables/rules.v4`
User15: User6 but sysctl --system does not work with my ubuntu server edition
User6: User15 what...version are you running?
User15: ubuntu server 12.04.3 LTS
User16: User8 if I have an environment running, with a gui installed, will 'juju quickstart' just log me in to it?
User8: User16 yes
User16: ok
User8: User16 it's a much faster way thank finding your admin secret
User8: thank/than
User16: true that
User6: can we just make juju quickstart juju deploy?
User6: err boostrap
User8: not a fan, in this case it's not bootstrapping. It's using the existing env
User8: and it's used for: juju quickstart bundle:xxxx
User8: which can reuse an env, that's not 'bootstrap' really.
User6: User8 it will bootstrap if the env doesn't exist already
User6: atleast, I'm pretty sure it will
User15: User6 so, the content of the bash script is ok?
User6: User15 seems about right
User15: User6 but dns resolving works
User15: User6 see the output of the wget command: http://pastebin.ubuntu.com/6927432
User15: User6 so, do u have any other idea what the reason for the problem could be ? :(
User15: User6 ok, i have to go now. but i will be here next week, maybe there is a chance to get things work on another day ;)
User6: User15 cheers, sorry we couldnt' get this figured out today!
User15: User6 np! thank you for all your help and hints so far ;-) All these things helped me to get stepwise closer to openstack!
User15: gn8
User6: User17 https://github.com/juju/plugins
User17: I saw, I am subbed to the juju org
User17: <3
User6: I'll add more as I clean up plugins
User6: User17 could you test my install instructions when you get a chance?
User6: User12 you probably wrote a few plugins too ^^
User17: sure
User17: marcoceppi, git is in `git` now, not `git-core`
User12: User17 so git is no longer a metapackage?
User17: no it's a package package
User17: but it's git, not git-core
User17: marcoceppi, the rest of the instructions work
User6: User17 cool, thanks
User6: docs updated
User17: marcoceppi, http://paste.ubuntu.com/6927700/
User17: something is wrong with the backup one I think?
User6: User17 backup isn't a plugin in the plugin repo
User17: marcoceppi, also it's Verify not Veify
User6: User17 that's something in your path
User17: oh!
User12: User6 the only juju plugin i wrote you replaced with clean
User12: +1 on instructions working
User17: marcoceppi, all you need is an "updating" section and you should be good
User6: User17 something I just realized, it'd be nice if in () after the description juju showed you the path to the plugin
User17: just cd'ing in there and git pull should do it right?
User6: User17 ah, good catch
User6: User17 ack
User17: o/
User6: User16 you up?
User16: User6 yeah man
User16: pfft
User16: been up for hours
User6: User16 hey, how hard would it be to display the path of a plugin in the juju help plugins output?
User6: like `PLUGIN      --description output    PATH`
User17: man, I really want the docs on github
User16: you mean where we found th eplugin?
User17: but I don't want to go down that rabbit hole
User6: User17 oh, you mean with like markdown ;)
User16: User17 do it :-)
User6: +1 from me ;)
User17: marcoceppi, yeah, then you could inline edit docs ON THE FLY
User16: User17 ask for forgiveness
User6: User16 yeah, where the plugin is located
User17: thumper, yeah but we build the docs out of bzr, so like, we'd need to update cron jobs etc.
User6: like /usr/bin or is it ~/.juju-plugins, etc
User16: User6 pretty easy
User17: hmmmm
User6: User16 cool, I'll file a bug for it then try to hack it myself for the next 10 mins, then leave it to the experts
User17: hey rick_h_, how did you import the gui history into github and so on?
User16: User6 heh, ok
User16: User8 also, re: github, do you squash the commits when merging?
User17: https://github.com/kfish/git-bzr
User17: seems useful
User6: User17 there's like a million git-bzr plugins out there
User17: yeah I just want to know which one works
User6: they all kind of suck, are you talking about just moving the docs branch to github?
User6: I can do a one time export -> import to github
User6: #thingstodowhennickisaway
User17: yeah
User6: was that yeah do that, or...?
User6: I mean, we should make sure no other merges exist against the docs branch, then once we move it we'll need to basically not accept merges to the docs branch anymore on lp
User6: then setup lp to import from gh so that we don't break auto-doc generation
User17: I was thinking of filing to make the auto-doc scripts update to pull from gh instead
User17: marcoceppi, I don't see any active MPs for docs.
User6: User17 we could do that too, file to use gh, not sure how much IS will like that, but I can do an initial import to gh
User17: -core is moving to github
User17: let's go all in!
User6: User17 cool, will set up in a few seconds
User8: User16 notes, scripts, and docs in here: https://bazaar.launchpad.net/~rharding/juju-gui-lander/trunk/files
User8: User16 hazmat says that to squash commits from bzr over to the new git repo it's a one line change to bzr-fastimport
User6: User17 https://github.com/juju/docs
User17: marcoceppi, nice, I'll send the mail to nick
User8: User16 yes, we squash when marging currently. https://github.com/juju/juju-gui/blob/develop/HACKING.rst#typical-github-workflow is what we're doing atm with some warts
User12: User6 can i get an invite to the juju group?
User6: I don't think I'm an admin?
User8: User12 github username?
User12: User8 chuckbutler
User6: I do have the power
User8: User12 added as charmer like marco/jcastro
User12: ty rick_h_
User8: hmm, and did owners as well. looks like everyone is an owner
User6: User12 we should make sure that we don't ever push master, but use merge proposals instead
User6: psa
User12: User6 i'll follow the fork-repository pattern.
User6: User12 <3
User12: :)
User8: User6 lazyPower yea, we make everyone fork off of juju owned repo into their own space and use pull requests
User6: I guess it's about time I moved amulet from my namespace
User18: there might be a better way to do the merging so we don't need people to rebase before merging into the develop branch....but untested
User18: pr's accepted.....right rick_h_ ? :)
User8: User18 yea, hopefully I can hack at it some this weekend.
User18: oh that would be awesome
User8: User18 well I missed the no rebasing bit
User18: there is git merge --squash
User8: some of those ways just always end up as one commit which I'm not a fan of
User18: and git merge --squash --ff
 * marcoceppi stops pushing master to plugins now
User8: User18 oh hmm, well we just use the github api for the merge bit
User8: User18 so I don't have a way to tell it how to do it like that. I guess we could have the script try to do it and then close the pull request as a follow up step
User8: I want to see how we get into these merge conflict issues. I don't run into them but seems everyone else does so I must be missing something in my workflow.
User18: I don't....it only happens when you merge develop into your current workflow then modify it and another branch lands
User18: it's pretty rare
User18: but the conflicts make sense
User8: I think the trick is to fix the way we merge develop in mid-branch
User8: just git merge develop isn't good. I think a git rebase develop will work
User8: but need to setup branches in the right state and try it out this weekend
User6: User8 so is juju-core on gh or should I be using bzr still?
User8: User6 I'm not up on what core is up to. They're moving at some point but don't know timing/state of that.
User8: User6 I'm assuming since thumper asked for info they're still working on it
User6: makes sense, ta
User16: User6 core moving soon
User16: FSVO soon
User8: hah
User6: User17 are you going to announce plugins to the list or should I?
User17: I can if you'd like!
User17: I am at your service
User6: User17 you're more...wordsmity than I, I can't seem to get veify right ;)
User17: on it
User6: ta!
User17: marcoceppi, is juju clean the only one we have right now?
User6: it's the only one I've put in there, I'm trolling through my gists to find others
User17: ack
User6: I've created a ton of them, but they're pretty hyper specific
User17: wouldn't hurt to have them in there
User17: if anything as examples
User18: jcastro quickstart is a plugin..no?
User17: hatch, yessir it is!
User18: or is that leveled up too much? :)
User17: though tbh I think it should just be reimplemented in core
User17: that should just be the way to use juju IMO
User6: User18 well, is juju-quickstart just a single file? IMO plugins should graduate to packages, like deployer charm-tools and quickstart
User6: but a ton of them, like juju-clean, address gaps in juju released versions
User18: marcoceppi no it's quite a bit of work :)
User6: or one off simplifications, like juju-setall
User6: which just runs juju set key=val on all services wether it exists or not as a valid config
User18: https://code.launchpad.net/~juju-gui/juju-quickstart/trunk
User18: it seems like there should be a juju-plugins org and then each plugin has it's own repo
User18: else you have to pull down everything to patch one plugin
User18: but I mean, unless there are quite a few it's probably not a problem :)
User6: User18 that was my plan, but jorge was like "start small"
User18: I hate to say it.....but he is probably right ;)
User6: yeah, I registered jujuplugins.com but unless get a cascade of plugins I think this will suffice
User18: yup yup
 * marcoceppi shames jcastro for cowboying on the docs branch
User19: he shalt be punished by eating only beans from a can and dark coffee for a week!
User20: Hi - I wonder who I should talk to about issues I'm having in juju-quickstart? Specifically: https://bugs.launchpad.net/juju-quickstart/+bug/1280005
User21: Bug #1280005: juju-quickstart cannot bootstrap local environemtn with sudo <juju-quickstart:New> <https://launchpad.net/bugs/1280005>
User6: User20 as of 1.17.2 you no longer need sudo to bootstrap (it'll instead prompt for password) so when 1.18.0 is released that bug won't be relevant anymore
User20: User6 in the mean time, what can I do?
User6: User20 run sudo juju quickstart ?
 * thomi tries
User8: User20 howdy, yea for now I cheat and bootstrap with juju and then run quickstart to get the Gui and bundles deployed
User20: User8 ok, I'll try that
User8: User20 we're in between releases. Right now it checks if the version is < 1.18 and if so it throws the message
User8: User20 once 1.18 hits it'll 'just work' and it's a pain point during the dev 1.17 cycle
User20: User8 perhaps on trusty it shouldn't install the PPA?
User20: User8  any idea when the 1.18 release is happening?
User8: User20 I think the aim is within 2wk?
User20: awesome, thanks
User8: User20 no promises, but soon so should get over this bump
User20: :)
User10: @marcoceppi - I don't think individual repositories are necessarily for juju plugins. I've contibuted to DefinitelyTyped (a repository of definitions and tests for Typescript stuff - https://github.com/borisyankov/DefinitelyTyped) and having each "definition" (in the case of Juju plugins it'd be a folder for each plugin) works out pretty well.
User6: User10 well, this is one repository, that has a file per plugin
User6: same concept
User6: User10 I'm about to add more, I just put the one in there, but others are welcome
User20: User8 probably a dumb question, but 'juju generate-config' does not set 'admin-secret' in the local environemnt config stanza, which then causes other things to fail. Any ideas what I'm missing?
User10: User6 Essentially, although you could easily divide each plugin into it's own folder and accompany each plugin with it's own Markdown page that'd be similar to man pages so people could easily understand (in a human readable fashion) the plugin's use-case, flags/ args, etc.
User6: User10 since plugins work by path, we'd have to add /each/ folder to path, which is tedious
User10: true
User6: User10 yeah, that's why I enforce all plugins accepting a --help flag
User6: since juju will automatically run the -help flag if you do `juju help <plugin>`
User6: much like the other juju help topics
User8: User20 I think they changed that it's in the jenv file now. The gui mentions it when you install it and load it now
User10: User6 Awesome.
User8: User20 so check the .juju/environments/xxxx.jenv
User20: User8 yes, I see it there, but after doing a manual bootstrap, 'juju-quickstart -e local' complains about it being missing from the environments.yaml file - should I copy it over, or is there a better way?
User8: User20 if you juju quickstart it should find it and load the gui and auto log you in
User8: User20 juju-quickstart --version
User20: juju-quickstart 1.0.0
User8: hmm, can you file a bug then that lists the error you get from quickstart with it complaining. Note that you generated the config via generate-config
User8: User20 ^
User20: User8 sure thing
User8: User20 for the moment yes, you can copy it over
User6: User12 you around?
User8: User20 but I thought it should *just work* in either location
User6: User12 could you review and merge this plz https://github.com/juju/plugins/pull/2
User20: User8 https://bugs.launchpad.net/juju-quickstart/+bug/1280019
User21: Bug #1280019: juju-quickstart does not find admin-secret <juju-quickstart:New> <https://launchpad.net/bugs/1280019>
User8: User20 thanks, will put this on the radar to check into
User8: User20 I'm wondering if this is another case where "juju < 1.18 look in environments.yaml" and otherwise look in .jenc
User8: .jenv
User20: sounds like it
User8: User20 I'll verify tomorrow and update the bug.
juju
Ubuntu IRC