| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Several people over the liberty cycle committed to maintaining
compose, but it was never completed. Rather than carry compose
in our repoistory until the end of time in a broken state I propose
removing it. If someone comes along and wants to resseruct the code
and make it functional in the future, I'd be 100% open to merge a
patch in the future which reintroduces this functionality. In the
meantime it is confusing to users which ask me on a daily basis if
compose is supported which I have to go into a 10 minute monologue
about why its in the repository.
Fortunately git contains full history so we can always revert this
change at a later time if someone wants to actually fixt his code
base up and make it useable in some way. I think the proper answer
is a seperate repoistory (kolla-compose) which contains any compose
related bits.
Please consider removing since nobody is using this code and its
dead.
TrivialFix
backport: liberty
Change-Id: I8b7c39b00d1967184d363af7db86d1ff8b5e725f
|
|
Remove all data containers from the repository except the one image
we intend to reuse for each data container. Adjust compose files to
remove all references to the unique data containers which serve no
purpose other then to take up extra resources.
Needs VOLUME in data containers exported in the compose files.
Change-Id: Id7746110946ef9836180cf57302aaf827e7e5405
Partially-Implements: blueprint one-data-container
|
|
Revert commit so that master will use the tag latest
Change-Id: If31c77cb288090dd5c780d684df41197df5b7fc2
|
|
Bump the tags for liberty2
Change-Id: Id8c22ea4db70dccdc66168fd0a953f8e2ca743e5
|
|
Container for Designate Sink, automatic domain creation for
enabled notification handlers (nova and/or neutron).
Change-Id: I41118cb149e7f39a17bff49123d82905b51b7939
Blueprint: designate-container
|
|
This is a complete DNS solution, with hidden master and bind9 slave.
It lacks the designate-sink service, because there is no true specification
to implement that. It listens for Nova/Neutron events and creates records
though adding those to just 1 domain isn't helping much in an environment
with multiple tenants.
Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a
Blueprint: designate-container
|
