x/solar
Code Issues Proposed changes
solar/resources/keystone_service
History
Jedrzej Nowak e3b4fba8af Introduced Resource Repositories. 
Works but requires manual `import`.
Removed `id` from resources.

Change-Id: I36ef63a5003ea39eb88d9076afd61215584916d9
2015-12-18 17:13:56 +01:00
..
actions
Renamed all yml files to yaml
2015-09-15 12:20:12 +02:00
meta.yaml
Introduced Resource Repositories.
2015-12-18 17:13:56 +01:00
README.md
Add some README's to couple of resources
2015-07-16 09:04:59 +02:00
test.py
Remove '.value' from inputs in resource tests
2015-09-15 09:56:20 +02:00

README.md

keystone_service resource

This resource sets up a Docker container with Keystone code. It requires config to be provided by the keystone_config resource (mounted under /etc/keystone).

Basically, the philosophy behind containers in Solar is to have stateless containers with service code and mount stateful resources with config, volumes, etc. to that container. Upgrade of code then would be just about replacing the stateless container with new one and remounting state to that new container.