jitsu environment import export

jitsu environment import export

Deployment automation for juju. We see lots of shell scripts for creating 
environments. Ideally we could just edit a json file or dump an existing 
environment to create a new one. These pair of commands (export and import) do
just that.

 you can dump an environment to json with

   jitsu export -e env_name > env.json

 it will capture services, unit counts, constraints, service config, relations, etc.

 That can in turn be imported to another environment with 

   jitsu import -e env_name env.json


R=negronil

https://code.launchpad.net/~hazmat/juju-jitsu/import-export/+merge/112819

(do not edit description out of merge proposal)

[hazmat, 2012-06-29 17:40:35]

Please take a look.

[negronjl, 2012-06-29 19:07:18]

Kapil:

Thanks for this. It is very useful.

Some thoughts about both export and import:
- They could both use more verbose help that details how to use the tools.

Some thoughts about import:
- It appears that import needs a local repository ( or I don't know how to tell
it to use cs: which could be alleviated by more verbose help )

I tried both export and import. They both work.

Thanks Kapil.

Thanks,

Juan

[hazmat, 2012-07-01 00:40:04]

*** Submitted:

jitsu environment import export

Deployment automation for juju. We see lots of shell scripts for creating 
environments. Ideally we could just edit a json file or dump an existing 
environment to create a new one. These pair of commands (export and import) do
just that.

 you can dump an environment to json with

   jitsu export -e env_name > env.json

 it will capture services, unit counts, constraints, service config, relations,
etc.

 That can in turn be imported to another environment with 

   jitsu import -e env_name env.json


R=negronil

R=negronjl
CC=
https://codereview.appspot.com/6350057