<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
Hi Eugene,</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
Just my take, but I assumed that we’d re-sequence the migrations at merge time, if needed. Feature branches aren’t meant to be optional add-on components (I think), nor are they meant to live that long. Just a place to collaborate and work on a large chunk
of code until it’s ready to merge. Though exactly what those merge criteria are is also yet to be determined.</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
I understand that you’re raising a general problem, but given lbaas v2’s state, I don’t expect this issue to cause many practical problems in this particular case.</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
This is also an issue for the incubator, whenever it rolls around.</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
Thanks,</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
doug</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_sign_1411522438470094080" class="bloop_sign"></div>
<br>
<p style="color:#000;">On September 23, 2014 at 6:59:44 PM, Eugene Nikanorov (<a href="mailto:enikanorov@mirantis.com">enikanorov@mirantis.com</a>) wrote:</p>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div></div>
<div>
<title></title>
<div dir="ltr">Hi neutron and lbaas folks.
<div><br>
</div>
<div>Recently I briefly looked at one of lbaas proposed into feature branch.</div>
<div>I see migration IDs there are lined into a general migration sequence.</div>
<div><br>
</div>
<div>I think something is definitely wrong with this approach as feature-branch components are optional, and also master branch can't depend on revision IDs in</div>
<div>feature-branch (as we moved to unconditional migrations)</div>
<div><br>
</div>
<div>So far the solution to this problem that I see is to have separate migration script, or in fact, separate revision sequence. The problem is that DB models in feature branch may depend on models of master branch, which means that each revision of feature-branch
should have a kind of "minimum required" revision of the master branch.</div>
<div>The problem that revision IDs don't form linear order, so we can't have 'minimum' unless that separate migration script may analyze master branch migration sequence and find minimum required migration ID.</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Eugene.</div>
</div>
_______________________________________________ <br>
OpenStack-dev mailing list <br>
OpenStack-dev@lists.openstack.org <br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <br>
</div>
</div>
</span></blockquote>
</body>
</html>