<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 23, 2014 at 8:12 PM, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On Wed, Jul 23, 2014 at 7:28 AM, Denis Makogon <<a href="mailto:dmakogon@mirantis.com">dmakogon@mirantis.com</a>> wrote:<br>
> Hello, Stackers.<br>
><br>
><br>
><br>
> For those of you who’s interested in Trove just letting you know, that for<br>
> now Trove can work with Neutron (hooray!!)<br>
> instead of Nova-network, see [1] and [2]. It’s a huge step forward on the<br>
> road of advanced OpenStack integration.<br>
><br>
> But let’s admit it’s not the end, we should deal with:<br>
><br>
> Add Neutron-based configuration for DevStack to let folks try it (see [3]).<br>
><br>
</div>I have some comments on this patch which I've posted in the review.</blockquote><div><br></div><div>Thanks for keeping an eye on it. So, you've suggested to use <span style="color:rgb(0,0,0);font-family:sans-serif;line-height:14.44444465637207px;background-color:rgb(252,250,150)">PRIVATE_NETWORK_NAME and</span><span style="color:rgb(0,0,0);font-family:sans-serif;line-height:14.44444465637207px;background-color:rgb(252,250,150)"> </span><span style="color:rgb(0,0,0);font-family:sans-serif;line-height:14.44444465637207px;background-color:rgb(252,250,150)">PRIVATE_SUBNET_NAME.</span></div>
<div><br></div><div><font color="#000000">Correct me if i'm wrong. According to [1] and [2] when neutron get's deployed, it uses pre-defined network (defined at [1]) and sub-network name (defined at [2]).</font></div>
<div><font color="#000000"><br></font></div><div><font color="#000000">If that's it - i'm totally fine to update patchset with suggested changed.</font></div><div><br></div><div>[1] <a href="https://github.com/openstack-dev/devstack/blob/89a8a15ebe31f4b06e40ecadd4918e687087874c/stackrc#L418-L420">https://github.com/openstack-dev/devstack/blob/89a8a15ebe31f4b06e40ecadd4918e687087874c/stackrc#L418-L420</a></div>
<div>[2] <a href="https://github.com/openstack-dev/devstack/blob/1ecd43da5434b8ef7dafb49b9b30c9c1b18afffe/lib/neutron">https://github.com/openstack-dev/devstack/blob/1ecd43da5434b8ef7dafb49b9b30c9c1b18afffe/lib/neutron</a></div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
> Implementing/providing new type of testing job that will test on a regular<br>
> basis all Trove tests with enabled Neutron to verify that all our networking<br>
> preparations for instance are fine.<br>
><br>
><br>
> The last thing is the most interesting. And i’d like to discuss it with all<br>
> of you, folks.<br>
> So, i’ve wrote initial job template taking into account specific<br>
> configuration required by DevStack and Trove-integration, see [4], and i’d<br>
> like to receive all possible feedbacks as soon as possible.<br>
><br>
</div>This is great! I'd like to see this work land as well, thanks for<br>
taking this on. I'll add this to my backlog of items to review and<br>
provide some feedback as well.<br>
<br></blockquote><div>Sound amazing, thanks for keeping an eye on. The most interesting part for me is a job template, i'd like to hear feedback in it as weel.</div><div><br></div><div>P.S.: sorry about putting job template on a gist instead of sending on the review, but i thought it would be good enough to recieve a feedback.</div>
<div><br></div><div> Best regards,<br></div><div>Denis Makogon</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Thanks,<br>
Kyle<br>
<div class=""><br>
><br>
><br>
> [1] - Trove.<br>
> <a href="https://github.com/openstack/trove/commit/c68fef2b7a61f297b9fe7764dd430eefd4d4a767" target="_blank">https://github.com/openstack/trove/commit/c68fef2b7a61f297b9fe7764dd430eefd4d4a767</a><br>
><br>
> [2] - Trove integration.<br>
> <a href="https://github.com/openstack/trove-integration/commit/9f42f5c9b1a0d8844b3e527bcf2eb9474485d23a" target="_blank">https://github.com/openstack/trove-integration/commit/9f42f5c9b1a0d8844b3e527bcf2eb9474485d23a</a><br>
><br>
> [3] - DevStack patchset. <a href="https://review.openstack.org/108966" target="_blank">https://review.openstack.org/108966</a><br>
><br>
> [4] - POC. <a href="https://gist.github.com/denismakogon/76d9bd3181781097c39b" target="_blank">https://gist.github.com/denismakogon/76d9bd3181781097c39b</a><br>
><br>
><br>
><br>
> Best regards,<br>
><br>
> Denis Makogon<br>
><br>
><br>
><br>
</div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div>