<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>There has been a lot of debate in the Kolla community about how to handle data containers but it has happened all over the place (irc, various reviews, etc). I’d like to have one record of the various tribal knowledge on this subject.</div>
<div><br>
</div>
<div>The latest proposal is to create one data container which is very small in nature and can be backed up with no VOLUME in the Dockerfile. Next start that container image with different names for all of the various data containers we operate. This should
provide a good backup solution for the data containers, and removes the current extra stuff hiding in the various API containers that we use as data containers now in the ansible deployment.</div>
<div><br>
</div>
<div>I have created a blueprint:</div>
<div><a href="https://blueprints.launchpad.net/kolla/+spec/one-data-container">https://blueprints.launchpad.net/kolla/+spec/one-data-container</a></div>
<div><br>
</div>
<div>It is in the discussion phase. If there is any <span style="font-weight: bold;">
technical</span> reason not to do this, lets get it out on the table now, otherwise I will approve the blueprint early next week and someone (perhaps me?) will begin the implementation. The goal is just to simplify the code base and get rid of the data container
bloat. ;)</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
</body>
</html>