<div dir="ltr">Just to follow up, CI is passing for the three patches outstanding<br>and the last one has a release note for the overall feature. The trick to<br>getting CI to pass was to introduce a new variant Controller<br>role for when we actually deploy with CephNFS and the VIP for the<br>server on the StorageNFS network. Using the variant controller role and '-n'<br>with network_data_ganesha.yaml (1) enables the new feature to<br>work correctly while (2) making the new feature entirely optional so<br>that current CI runs without being affected by it.<br><br>I think the three outstanding patches here are ready to merge:<br><br><a href="https://review.openstack.org/#/q/status:open+topic:bp/nfs-ganesha">https://review.openstack.org/#/q/status:open+topic:bp/nfs-ganesha</a><br><br>I want to get them in so they'll show in downstream puddles for QE but<br>my full attention will immediately turn to upstream TripleO CI and doc for this<br>new functionality. In that regard I *think* we'll need Dan Sneddon's work here:<br><br><a href="https://review.openstack.org/#/c/523638">https://review.openstack.org/#/c/523638</a><br><br>so that actual deployment of the StorageNFS network doesn't have to<br>involve copying and editing<br><br>network/config/*/{ceph,compute,controller}/.yaml<br><br>as done in the DNM patch that I've used for testing actual integration of the<br>feature here:<br><br><a href="https://review.openstack.org/533767">https://review.openstack.org/533767</a><br><br>All said, this one seems to be a good poster child for composable roles +<br>composable networks!<br><br>-- Tom Barron<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 23, 2018 at 2:48 PM, Emilien Macchi <span dir="ltr"><<a href="mailto:emilien@redhat.com" target="_blank">emilien@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree this would be a great addition but I'm worried about the<br>
patches which right now don't pass the check pipeline.<br>
Also I don't see any release notes explaining the changes to our users<br>
and it's supposed to improve user experience...<br>
<br>
Please add release notes, make CI passing and we'll probably grant it for FFE.<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Jan 22, 2018 at 8:34 AM, Giulio Fidente <<a href="mailto:gfidente@redhat.com">gfidente@redhat.com</a>> wrote:<br>
> hi,<br>
><br>
> I would like to request an FFE for the integration of nfs_ganesha, which<br>
> will provide a better user experience to manila users<br>
><br>
> This work was slown down by a few factors:<br>
><br>
> - it depended on the migration of tripleo to the newer Ceph version<br>
> (luminous), which happened during the queens cycle<br>
><br>
> - it depended on some additional functionalities to be implemented in<br>
> ceph-ansible which were only recently been made available to tripleo/ci<br>
><br>
> - it proposes the addition of on an additional (and optional) network<br>
> (storagenfs) so that guests don't need connectivity to the ceph frontend<br>
> network to be able to use the cephfs shares<br>
><br>
> The submissions are on review and partially testable in CI [1]. If accepted,<br>
> I'd like to reassign the blueprint [2] back to the queens cycle, as it was<br>
> initially.<br>
><br>
> Thanks<br>
><br>
> 1. <a href="https://review.openstack.org/#/q/status:open+topic:bp/nfs-ganesha" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/q/status:open+topic:bp/nfs-<wbr>ganesha</a><br>
> 2. <a href="https://blueprints.launchpad.net/tripleo/+spec/nfs-ganesha" rel="noreferrer" target="_blank">https://blueprints.launchpad.<wbr>net/tripleo/+spec/nfs-ganesha</a><br>
> --<br>
> Giulio Fidente<br>
> GPG KEY: 08D733BA<br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Emilien Macchi<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div></blockquote></div><br></div>