kolla-mesos/tools
Angus Salkeld 1f95680a32 Use a new per-service format
Note: whilst this is a large patch, most of it is just moving stuff around.

This has a number of benefits now:
- generate the marathon/chronos files
- one file per running container (easier to manage changes)
- no need to redefine lots of marathon attributes
- to create special marathon attributes specify them under
  "service"/"task" or "container" depending on the attribute
  and it will override the value in services/default.marathon.j2
- render the command's files just before running the command
  (previously there was a risk of rendering the files too early)

We can benefit from the changes with a little more work:
- any update tasks can be easily separated from the service

Change-Id: I007c2859b9d4bf8e9b984cbeba93456a9ce06f29
2016-02-08 18:30:15 +10:00
..
__init__.py Fix tests and add bashate 2015-10-30 14:33:59 +09:00
bootstrap.sh Handle multiple network interfaces 2015-12-08 11:01:54 +01:00
generate_config_file_samples.sh Create own /etc/kolla-mesos config tree 2015-12-01 21:51:51 +01:00
kolla-mesos-ansible kolla-mesos-ansible script 2016-01-12 18:59:56 +01:00
run-bashate.sh Create a bashate script 2016-01-19 07:00:06 +01:00
validate-all-json.sh Use a new per-service format 2016-02-08 18:30:15 +10:00
validate-all-yaml.sh Use a new per-service format 2016-02-08 18:30:15 +10:00
validate-json.py Fix tests and add bashate 2015-10-30 14:33:59 +09:00
validate-service.py Use a new per-service format 2016-02-08 18:30:15 +10:00
validate-yaml.py Fix tests and add bashate 2015-10-30 14:33:59 +09:00