lp:~caio1982/charms/trusty/system-image-server/productionizing-story-1332

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~caio1982/charms/trusty/system-image-server/trunk at revision 21

Caio Begotti: Pending requested 2015-05-04

Diff: 205 lines (+97/-18)

3 files modified

README (+5/-0)
config.yaml (+13/-1)
hooks/hooks.py (+79/-17)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

22. By Caio Begotti on 2015-05-04

add missing charm options that will help it to move a bit closer to production:

- cronjob can be used to set up a periodic run of image server stuff (like importing of new images)

- shell can be used to run a batch of commands in si-shell after, say, the deployment has been done but still requires some maintenance if an image needs to be promoted to a given channel manually and such

- make it possible to deploy the charm using production keys instead of those testing ones the image server code generates

21. By Caio Begotti on 2015-05-04

add a reminder as tests are starting to be very dearly missed in here...

20. By Caio Begotti on 2015-04-23

avoid duplicated entries errors when updating the config and calling hook config-changed multiple times

19. By Caio Begotti on 2015-04-23

make it so the config file is present during installation already otherwise we cant generate the keys

18. By Caio Begotti on 2015-04-23

make it so the keys generation only runs once as it is not needed everytime we change a config option

17. By Caio Begotti on 2015-04-23

fix the dictionary of options that is passed to the template render as the function object is not iterable

16. By Caio Begotti on 2015-04-23

reorganize the hooks methods to be next to each other

15. By Caio Begotti on 2015-04-23

fix missing import for exception handling when a hook is not found

14. By Caio Begotti on 2015-04-23

revamp how the hooks are called, thus simplifying a lot the charm config handling and how to tell juju which method is which hook

13. By Caio Begotti on 2015-04-23

move the calls that should actually have been config-changed to its particular hook block, which can then be executed by juju accordingly