[00:58] <wesleymason> Tbf the really shouldn't directly pollute /var/www, as it would not be unreasonable for another service within the same host to use the standard path as well.
[00:58] <wesleymason> *the charm
[01:06] <marcoceppi> wesleymason: you should use a directory within /var/www
[01:06] <marcoceppi> wesleymason: like /var/www/service-name
[01:56] <Valduare> gah
[01:57] <Valduare> there needs to be more juju maintainers :P
[02:39] <Fishy__> you should apply
[02:44] <Valduare> im not good enough
[13:59] <mischief> hi, i'm running the latest juju-core tarball from launchpad.net
[14:00] <mischief> i followed the testing guide here but in the end, i can't contact the webserver running in the exposed wordpress charm https://juju.ubuntu.com/docs/getting-started.html#test
[14:02] <mischief> huh, finally worked
[14:02] <mischief> guess ec2 is just a bit slow :)
[14:33] <Valduare> how do I setup a second workstation to manage my stuff
[14:51] <Valduare> hi guys
[14:51] <Valduare> how do I connect a new workstation to my juju stuff
[14:51] <Fishy__> what do you have now
[14:51] <Fishy__> that you want to connect it to
[14:52] <Fishy__> a MAAS setup? openstack?
[14:52] <Valduare> no I mean, I setup juju on one workstation to manage my vm’s
[14:52] <Valduare> and now I am on a different workstation
[14:52] <Fishy__> so what type of environment did you use, local?
[14:52] <Valduare> manual provisioning
[14:53] <Valduare> have one bootstrap vm and a few other vm’s running some services now.
[14:53] <Fishy__> and you want to run juju commands on it?  or want it to be able to host stuff
[14:53] <Valduare> but I dualboot between ubuntu and mac so i’d like to be able to manage it from both OS - I have the same juju-core installed on mac and ubuntu 1.17.7
[14:54] <Fishy__> ok so to manage it, you just need the config file from ~/.juju
[14:54] <Fishy__> in both places
[14:54] <Fishy__> for manual maybe need a few other files
[14:55] <Valduare> I made the environments.yml the same on both installations
[14:55] <Fishy__> so that should let you do juju status in either place
[14:55] <Fishy__> and see the same stuff?
[14:55] <Valduare> so If I just copy the .juju dir over to mac it will be setup
[14:56] <Fishy__> thats my theory, but I have not tried it
[14:56] <Valduare> juju status tells me to create new environment
[14:56] <Valduare> new bootstrap environment
[14:56] <Fishy__> ya dont do that
[14:56] <Fishy__> juju generate-config    then    juju switch manual
[14:57] <Fishy__> then clobber your envionments over
[14:57] <Valduare> done that
[14:57] <Fishy__> so then juju status should see your "master node"
[14:57] <Fishy__> which knows about everyone
[14:57] <Valduare> how do multiple sysadmin manage something with a system like this??
[14:57] <Fishy__> 10 guys each have the same envionments.yaml
[14:57] <Fishy__> all point to the same master node
[14:57] <Fishy__> who knows about the cluster
[14:57] <Fishy__> maybe your master node is on the offline computer?
[14:58] <Fishy__> so you cant connect to it
[14:58] <Valduare> no its on an esxi host
[14:58] <Fishy__> and its running right now?
[14:58] <Valduare> I have juju-gui running on it
[14:58] <Valduare> cant login cause dont have the password from my ubuntu host workstation’s file heh
[14:58] <Valduare> but ya its running
[14:58] <Fishy__> and you can ping bootstrap-host
[14:58] <Fishy__> and it resolvs?
[14:58] <Valduare> yep
[14:58] <Valduare> can get to login screen fine for juju gui
[14:59] <Fishy__> hum
[14:59] <Fishy__> wonder if it is authentication issue
[15:00] <Fishy__> and "juju switch"  says manual ?
[15:00] <Valduare> aye
[15:00] <Fishy__> i blame authentication, but at my limits ;)
[15:12] <Valduare> marcoceppi: u around?
[15:12] <Valduare> marcoceppi: I got the juju set to 1.17.7 devel for homebrew :)
[15:15] <Valduare> Fishy__: just copied the entire .juju dir to mac and its working
[15:18] <Fishy__> there you go
[15:19] <Fishy__> wonder what file it needed
[15:24] <Valduare> not sure
[15:25] <Valduare> Fishy__: what all do you run with juju?
[15:26] <Fishy__> im attempting to switch my infastructure to juju
[15:26] <Fishy__> will be about 40 or 50 machines.. trying to use the MAAS approach
[15:27] <Fishy__> want to see how far I can go with juju to avoid having to use puppet
[15:27] <Fishy__> because I hate puppet that much
[15:34] <Valduare> i havnt tried puppet
[15:34] <Valduare> what all does it do
[15:34] <Fishy__> everything
[15:34] <Fishy__> runs ruby all over the place to do stuff
[15:34] <themonk> hello all
[15:35] <Fishy__> hi
[15:35] <themonk> i am facing a problem
[15:36] <themonk> in provider join i am setting some value like private ip and port using relation-set command
[15:38] <themonk> but i am not getting it in requirer relation changed
[15:38] <themonk> marcoceppi: hi
[16:04] <lazyPower> Valduare: Puppet is a configuration management solution, similar to chef
[16:05] <Valduare> morning lazyPower
[16:05] <lazyPower> o/
[16:05] <lazyPower> just stopping in to check on the community. So much to do
[16:05] <Valduare> I updated the homebrew juju.rb looks like it was accepted :)
[16:05] <Valduare> i got 1.17.7 running on my macbook
[16:05] <lazyPower> Yeah, they are pretty quick on accepting merge proposals.
[16:07] <Valduare> I tried the openerp-server charm last night
[16:07] <Valduare> but it setup the old 6.1 version not 7
[16:07] <lazyPower> yeah, there's an open bug ont hat
[16:07] <Valduare> they are almost out with 8 if not already.
[16:07] <Valduare> any idea who’s working on a fix?
[16:08] <lazyPower> I'm fairly certain its unmaintained at the moment. Patches are welcome if you want to try your hand at it
[16:08] <lazyPower> suggestion though: unless you want to handle the 6.1 deployments in the wild, target trusty.
[16:08] <Valduare> I havnt done a migration from 6.1 to 7 myself
[16:09] <Valduare> from what I read its a bain
[16:09] <Valduare> pain
[16:09] <lazyPower> yeah, and the logic for that is going to be hefty
[16:09] <lazyPower> since it requires database migrations
[16:09] <lazyPower> if I weren't under the gun for other projects i'd spend some cycles on upgrading the charm to 7
[16:10] <Valduare> I was reading in the charm files for it though it spoke of some sort of “choosing version to install”
[16:10] <Valduare> lp or something?
[16:10] <lazyPower> well, the idea is to actually extend the charm so the user can chose a version to install
[16:10] <Valduare> with openERP there is no maintained way to migrate between milestones
[16:10] <lazyPower> making charms more extensible through configuration. The charm handles all the nuances of each version.
[16:10] <Valduare> so the charms should reflect that and have a charm for 6.1 and charm for 7 and charm for 8 etc
[16:11] <lazyPower> interesting. How familiar are you with OpenERP?
[16:11] <Valduare> unless the charm can integrate the opensource upgrade tool project
[16:11] <Valduare> not extremely familiar
[16:11] <Valduare> just a good reader :P
[16:12] <lazyPower> well, those points would be extremely good points of interest as bugs against the charm for feature planning
[16:12] <Valduare> migration between versions is a paid support item with openERP
[16:12] <Valduare> but there is a community project for scripts to handle it
[16:12] <lazyPower> that, doesn't surprise me
[16:12] <Valduare> so what all do you do when you sit down to make a charm
[16:13] <Valduare> ie there’s an install guide for openerp 7, how does that get translated into a charm
[16:13] <lazyPower> Thats subjective to which charm i'm working on
[16:14] <lazyPower> but the first thing I do is get teh data integrity portion down. Write the backup routines and validate i have a recovery mechanism if the upgrade blows up
[16:14] <Valduare> I mean for a fresh install
[16:15] <lazyPower> ah, i start the install script with "return 1"
[16:15] <lazyPower> deploy it
[16:15] <lazyPower> debug-hooks into the server and start iterating
[16:15] <lazyPower> i "protoduction" the code. Aint nobody got time for deploy + scan logs
[16:16] <lazyPower> when i'm done, i tar up the charm, and scp it back to my desktop. Add comments, readme contents, clean up the code and open a MP
[16:19] <lazyPower> Valduare: i think i skipped a key part of your question. Yeah - if there is an upstream install guide. I follow that as closely as I can, unless i have security concerns with it.
[16:19] <lazyPower> then i add my own spin on those sections.
[16:19] <Valduare> so you launch a vm and follow the install guide there and then wrap it up some how?
[16:21] <lazyPower> no, i create a charm template using charm tools.    charm create boopdeep for example
[16:21] <lazyPower> i edit the metadata for relationships, add in whatever config options I think i'll need and add the return1 to the install hook
[16:22] <lazyPower> i deploy that service, the return1 ensures I enter the hook context at step 1 of the installs cript
[16:22] <lazyPower> i debug hooks into that machine, and set juju resolved -r on that unit so it re-runs the install hook
[16:22] <lazyPower> remove the return 1 and start coding out the installation. Fetching dependencies, setting up system users, etc.
[16:22] <lazyPower> from there, its subjective on what the charm's purpose is and what its providing.
[16:24] <lazyPower> make sense?
[16:25] <Valduare> the second to the last line you said did :P
[16:26] <lazyPower> Valduare: if you dont know about debug hooks, you need to start there. Deploy a charm and debug-hooks on the unit so you can see the glory of that tmux infused awesomeness
[16:28] <lazyPower> Valduare: https://juju.ubuntu.com/docs/authors-hook-debug.html
[16:31] <Valduare> have you used openerp?
[17:10] <lazyPower> Valduare: i have not. I was looking into it at one point
[17:10] <zrz> hi, i try to use juju on local environment with LXC but i get an error at bootstrap
[17:11] <zrz> ERROR juju.state open.go:93 TLS handshake failed: x509: certificate signed by unknown authority
[17:11] <zrz> I run ubuntu 13.04
[17:13] <zrz> It happens just after the connection to mongo
[17:14] <lazyPower> zrz: https://bugs.launchpad.net/juju-core/+bug/1178312
[17:14] <_mup_> Bug #1178312: ERROR state: TLS handshake failed: x509: certificate signed by unknown authority <config> <cts-cloud-review> <ui> <juju-core:Triaged> <https://launchpad.net/bugs/1178312>
[17:14] <lazyPower> its a known bug
[17:16] <zrz> I have only one machine
[17:17] <zrz> Already came accross the  launchpad link but don't really know if it applies
[17:18] <zrz> http://pastebin.com/cLP2UHry
[17:23] <lazyPower> hmm
[17:24] <lazyPower> zrz: i'm not sure, however if you're still around hwen I get back i'll take a look at it
[17:24] <lazyPower> off to run errands
[17:24] <zrz> thx
[17:24] <lazyPower> np tc o/
[17:30] <zrz> what should my .ssh/ folder look like ?
[17:42] <zrz> maybe do I have to regenerate a certificate
[19:12] <Valduare> we need someone to make an openerp 7 charm
[19:21] <Valduare> any volunteers?
[19:37] <Valduare> lazyPower: u around
[19:53] <Valduare> marcoceppi: u around?
[19:56] <lazyPower> Valduare: you rang?
[19:56] <Valduare> hi :)
[19:56] <Valduare> hows it going lurch
[19:56] <Valduare> :P
[19:56] <Valduare> found this in the install hook for openerp-server charm bzr checkout --lightweight lp:openobject-server${VERSION} openobject-server
[19:57] <Valduare> is there a way to pass the version variable when deploying a juju charm
[20:02] <lazyPower> whats it say at the top of the install hook?
[20:02] <lazyPower> surely its setting VERSION up there, with a helper like config-get
[20:02] <Valduare> isnt there something I can pass with the juju deploy —to  2 openerp-server    version=/7.0 or soemthing like that
[20:03] <lazyPower> Valduare: You can pass variables to a deployment. The available variables are defined in config.yaml of the charm. You set them with juju set <service> <variable>=<value>
[20:04] <lazyPower> Valduare: read: https://juju.ubuntu.com/docs/charms-config.html
[20:04] <Valduare> VERSION=$(config-get version) is in the file up top
[20:04] <lazyPower> Valduare: and https://juju.ubuntu.com/docs/authors-charm-config.html
[20:05] <lazyPower> its covered thoroughly in the docs
[20:07] <Valduare> ah so looks like it cant be passed through the command
[20:07] <Valduare> has to be put into a file for it to parse
[20:10] <Valduare> nope
[20:10] <Valduare> that dosnt work
[20:10] <Valduare> this documentation… ugh
[20:19] <lazyPower> Valduare: juju set openerp version=7
[20:20] <Valduare> when you run that it says service not found
[20:20] <Valduare> they need to specify in the documentation when to run that
[20:21] <lazyPower> Valduare: it can be run pretty much at any time
[20:22] <Valduare> if you run juju set before deploying service - service not found
[20:22] <lazyPower> charms are intended to be dynamic, and allow the user to dynamically reconfigure their services at any time during its lifecycle
[20:22] <Valduare> its not intuitive to new users that you can run the set imediately after deploying it (before it boots up - now I know lol)
[20:22] <lazyPower> Valduare: if you want to specify values at time of deployment, i suggest using the yaml approach and specifying it during the deployment with --config=configuration.yaml
[20:23] <Valduare> aye I tried that kept giving me errors
[20:23] <Valduare> examples on the docs provided no clues
[20:24] <Valduare> im speaking frankly - in order to help things along for new adopters like myself lol
[20:24] <lazyPower> The docs are up on GitHub
[20:24] <lazyPower> and pull requests are most certainly appreciated
[20:25] <lazyPower> if you've got ideas on how phrasing, or call outs would help - feel free to contribute. Otherwise, i understand your frustration :) Keep at it, i promise you that it's easier than it appears
[20:26] <Valduare> aye
[20:26] <Valduare> hmm hook failed : install
[20:27] <Valduare> ah there we go
[20:35] <Valduare> well this is nice, it didnt install the 7.0 version again
[20:39] <Valduare> lazyPower: is this correct? options:
[20:39] <Valduare>         version: "/7.0"
[20:40] <lazyPower> are you deploying the server or the web agent?
[20:40] <lazyPower> i'm looking up the charm
[20:42] <lazyPower> Valduare: that looks correct
[20:42] <Valduare> ok
[20:42] <Valduare> both onto same instance
[20:43] <lazyPower> Valduare: however that PPA only has 6.1
[20:43] <lazyPower> https://launchpad.net/openobject-server/+packages
[20:43] <lazyPower> so setting it to 7.0 is goign to fail
[20:43] <Valduare> ah crapola
[20:43] <Valduare> goot catch
[20:44] <lazyPower> Valduare: https://bugs.launchpad.net/charms/+source/openerp-server/+bug/1136952
[20:44] <_mup_> Bug #1136952: Charms deploy OpenERP 6.1.1 and not OpenERP 7.0 <audit> <openerp-server (Juju Charms Collection):New> <https://launchpad.net/bugs/1136952>
[20:45] <lazyPower> also this is a known problem against the charm
[20:46] <Valduare> so wonder if I can modify the charm
[20:47] <Valduare> wait, where did you get that link
[20:47] <Valduare> when I go to launchpad/openobject-server/7.0 it shows up fine
[20:48] <lazyPower> i went to launchpad/openobject-server
[20:48] <lazyPower> then clicked on the package resource at the bottom
[20:51] <Valduare> noticed that juju destroy-service openerp-server   leaves all the files?
[20:51] <lazyPower> I haven't deployed it, so no
[20:52] <lazyPower> bug would you be so kind as to file a bug about that?
[20:52] <lazyPower> s/bug/but/
[20:52] <Valduare> sure
[20:52] <Valduare> where at?
[20:52] <Valduare> the last link?
[20:52] <lazyPower> yep
[20:52] <lazyPower> it needsa fresh bug
[20:53] <lazyPower> not appended to that one - for clarification
[20:54] <Valduare> ok
[20:54] <Valduare> submitted
[20:55] <Valduare> any idea why its split into openerp-web and openerp-server ?
[20:55] <lazyPower> Scaling purposes
[20:55] <lazyPower> they are independent services
[20:55] <Valduare> ah
[20:56] <lazyPower> multiple front ends in different AZ's to keep latency down
[20:56] <lazyPower> single back end, or vice versa
[20:57] <Valduare> ok
[20:58] <Valduare> in these config.yaml files do they need to be in quotes?
[20:58] <Valduare> ie version: “/7.0”    or version: /7.0
[21:00] <Valduare> i get ERROR cannot parse settings data: YAML error: line 1: found character that cannot start any token
[21:01] <lazyPower> no quotes are not necessary
[21:01] <jose> hey guys, about bug #1299585, I think destroy-service never removes any files/programs/conf at all?
[21:01] <_mup_> Bug #1299585: juju destroy-service openerp-server fails to remove any files <openerp-server (Juju Charms Collection):New> <https://launchpad.net/bugs/1299585>
[21:02] <lazyPower> jose: the stop hook should clean up after the service
[21:02] <Valduare> any idea about the line 1 error>
[21:02] <jose> lazyPower: hmm, isn't the stop hook just supposed to stop the service?
[21:03] <lazyPower> Valduare: i cant read your yaml since i havent seen it so no
[21:03] <Valduare> i’ll pastebin
[21:03] <lazyPower> jose: stop is called when the service is being torn down
[21:03] <Valduare> but i coppied it in here
[21:03] <lazyPower> jose: so its supposed to stop teh service and perform any cleanup
[21:03] <Valduare> http://pastebin.com/jzxLTLhK
[21:04] <Valduare> i’ve tried header with   options:     openerp-web:    etc
[21:04] <lazyPower> Valduare: the format is service-name: <return><4 spaces> option: value
[21:04] <lazyPower> yaml doesn't read tabs. it has to be spaces.
[21:05] <Valduare> ah
[21:05] <Valduare> that should be added to the doc’s lol
[21:05] <lazyPower> or you should read up on how to write yaml ;)
[21:06] <Valduare> yes but the doc’s should have a pointer to let me know that I didnt know something lol
[21:06] <lazyPower> jose: ideally, your'e in a cloud environment where the machine is disposeable and each service is attached to its own machine. Thats why most stop hooks dont clean up the environment
[21:07] <lazyPower> because its wasted cycles as the service is getting trashed. However, users of the manual provider are going to see all of this as machines aren't getting wiped.
[21:07] <jose> lazyPower: so, before I do this push, should, let's say, the mailman charm, purge the installed packages on stop?
[21:07] <jose> otherwise, I can just uncommit
[21:08] <lazyPower> jose: that would be a good plan if you want to support users of the manual provider. Otherwise note the behavior in the readme and let the good times roll.
[21:08] <lazyPower> you as the charm author are ultimately responsible for the behavior of the charm, and its up to whatever you want to support
[21:08] <jose> I think it'd be nice, I'll add it :)
[21:08] <lazyPower> if a user deploys the charm without reading the readme first, thats their bad  for not expecting the behavior.
[21:09] <lazyPower> s/expecting/accepting
[21:09] <Valduare> wait wait this is is 2014 us consumers dont want any responsibility lazyPower :P
[21:10] <lazyPower> Valduare: i cant help it that people want genies. Juju is quite a bit of magic already - it doesn't grant 3 wishes on top of that.
[21:10] <Valduare> hehe
[21:11] <jose> :P
[21:11] <Valduare> ok now that i’ve gotten my syntax correct it does look like its not capable of doing openerp 7
[21:13] <Valduare> so that lp config option
[21:13] <Valduare> I may be able to point it to the right bzr repo eh?
[21:13] <lazyPower> give it a shot, if you get it working and submit a MP someone will review your owrk and you may make it into the charm store with that
[21:14] <lazyPower> i know quite a few users will be thanking you for the patch :)
[21:14] <Valduare> how can I download the charm and edit it and run locally
[21:15] <lazyPower> Do you have charm tools installed?
[21:16] <lazyPower> Valduare: brew install charm-tools && charm get openerp-server
[21:16] <lazyPower> https://juju.ubuntu.com/docs/howto-vagrant-workflow.html
[21:17] <Valduare> ty
[21:17] <lazyPower> I also made a video if the text is TLDR
[21:17] <lazyPower> https://www.youtube.com/watch?v=TSLJ22ntPQA
[21:50] <jose> lazyPower: hey, any idea of what a 'git add' error may mean? I haven't even ran git on my hook and it's giving me that error, http://paste.ubuntu.com/7176420/
[21:51] <lazyPower> i have not see that before :(
[21:53] <jose> weird
[21:57] <lazyPower> jose: actually it may be coming from juju itself, presently juju uses git for charm deployment versioning
[21:57] <lazyPower> which causes interesting errors when there are merge conflicts, and what not. You can see this behavior by editing a hook on the service, and then updating the same lines in your charm and redeploying
[21:58] <jose> will consider it, then
[22:47] <Valduare> hmm its been stuck at install failed
[22:47] <Valduare> cant destroy it to try again...
[22:48] <lazyPower> read up on resolving errors Valduare
[22:48] <lazyPower> if a machine is in an error state, it waits for user intervention
[22:49] <lazyPower> you cant destroy, or progress until its resolved.
[22:52] <Valduare> resolved openerp-web/0  says cant resolve cause its already resolved
[22:57] <Valduare> looks like I broke juju
[22:58] <lazyPower> its in a loop somewhere in a hook
[22:58] <lazyPower> i've done that by sending too many commands while it was in an error state
[22:58] <lazyPower> you can either wait for it to run its course and land on another error (or complete successfully)
[22:58] <lazyPower> or destroy the machine with --force (if you are on 1.17.x) and start over with it
[22:59] <lazyPower> by re-registering it in your machine pool
[22:59] <Valduare> ok
[23:03] <Valduare> now just says life dead in juju status for that machine heh
[23:03] <Valduare> can I re-add it yet?
[23:17] <marcoceppi> lazyPower: fyi, I'm about to start working in the queue. lmk if you're in it
[23:18] <lazyPower> marcoceppi: i am not. I'm trying to figure out vlan trunking so i can get to my maas nodes
[23:18] <lazyPower> nfs mounts are failing since its bidi communication :(
[23:18] <marcoceppi> that sucks
[23:18] <lazyPower> marcoceppi: WHY ARE YOU WORKING THE QUEUE ON YOUR BIRTHDAY?
[23:18] <lazyPower> get outta here
[23:31] <lemao> lazyPower: great video, thanks! Q: what is special about the custom JujuBox as opposed to a plain ubuntu-vagrant box plus a juju bootstrap?
[23:31] <lazyPower> lemao: lemao the juju box comes with all the juju bits included
[23:32] <lazyPower> you can do it manually but you'll need to write a provisioner statement to load the packages you need + bootstrap your environment. You get that all OOTB with the ubuntu-juju-precise vagrant box.
[23:33] <lemao> lazyPower: ok, I was interested in using trusty and I created a simple bootstrap.sh to provision vagrant. But LXC used precise instead of trusty for the containers
[23:34] <lazyPower> lemao: when we aren't so slammed with other things to do i'll be working on extending the vagrant story of juju, and producing some plugins for juju so you get all that goodness ootb
[23:35] <lazyPower> one of the big draws for me with vagrant is an isolated testing environment. That way i ensure all my dependencies are met for CI and what not in the 00-setup script from charm add tests
[23:37] <Valduare> hmm lazyPower I ran juju destroy-machine 2 —force and juju status shows it as dead, agent running
[23:37] <Valduare> wont remove?
[23:38] <lazyPower> interesting
[23:38] <lazyPower> not sure why thats happening. Sounds like a bug
[23:38] <weblife> wow hp small is cheaper then aws m1.small and better
[23:39] <weblife> plus 300 credit!! awesome, im in!!!
[23:40] <weblife> anyone know if they have similiar dns services though like route 53?
[23:42] <lemao> lazyPower: I am also looking for a full dev/testing environment that I could 'switch' to ec2, for instance.
[23:43] <lazyPower> lemao: meaning you test in EC2? or you test local and switch + deploy to ec2?
[23:43] <lemao> lazyPower: and I am stuck with OSX for now so vagrant+virtualbox is required
[23:43] <lemao> lazyPower: latter
[23:43] <lazyPower> then the juju vagrant image is your key to success
[23:43] <marcoceppi> weblife: yeah, they have a DNS server
[23:43] <marcoceppi> service*
[23:44] <lazyPower> lemao: that or join the jedi academy and run ubuntu native on your apple hardware :)
[23:45] <Valduare> so I may have to destroy entire environment to fix this?
[23:45] <lazyPower> Valduare: i wouldn't think so, no. have you tried rebooting the vm guest through your esxi VM Manager?
[23:45] <lemao> lazyPower: :-) I have been circling around that thought now for months ...
[23:45] <lazyPower> worst case scenario is you reprovision the vm and re-add it.
[23:46] <lazyPower> lemao: i have a MBA using reFind and it works extremely well. I recently picked up an XPS13 and have all but abandoned the apple hardware save for testing brew packaging and vagrant stuff
[23:49] <lazyPower> I'm actually considering selling it and picking up a mac mini to run on my network somewhere that i can remote into, keep it tucked away in a dark corner of my house
[23:51] <Valduare> ya I rebooted it
[23:51] <Valduare> havnt rebooted the juju bootstrap vm is that needed?
[23:51] <lazyPower> i dont think so
[23:51] <mischief> are there any juju developers here?
[23:52] <Valduare> ok i’ll try blowing the vm away and starting fresh
[23:52] <mischief> lazyPower maybe?
[23:52] <lazyPower> mischief: i'm not a core developer. I work on charms and community help/outreach
[23:52] <lemao> lazyPower: I will have to take the plunge at some point
[23:53] <lemao> lazyPower: is there a trusty JujuBox somewhere? Or where can I find the sources for the precise JujuBox?
[23:54] <lazyPower> lemao: unfortunately, the process to build those vagrant boxes remains full of mysticism and voodoo - i do however have some preliminary scripts using veewee to build your own basebox. The size was pretty hefty though (~800mb)
[23:55] <lazyPower> lemao: there are some baseline trusty boxes here: http://cloud-images.ubuntu.com/vagrant/trusty/
[23:55] <lazyPower> i dont think any of the juju boxes for trusty have been built yet.
[23:56] <lazyPower> and if you want to get started building your own baseboxes - you can build off my work here: https://github.com/chuckbutler/juju-vagrant-veewee-definitions