https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-681 transportpce <p>The developer guide docs indicates that it is possible to use path-computation-request as an external REST API in order to invoke the PCE module for checking connectivity:</p> <p><a href="https://docs.opendaylight.org/projects/transportpce/en/latest/developer-guide.html#invoking-pce-module" class="external-link" target="_blank" rel="nofollow noopener">https://docs.opendaylight.org/projects/transportpce/en/latest/developer-guide.html#invoking-pce-module</a></p> <p>However, this does not work in practice. The problem is that the servicehandler sets an input variable in the pce listener when receiving and processing a service request. If a path-computation-request is then sent through the external REST API, the pce listener will get a notification when path computation is finished and continue processing with the old input and new computed path. If the old input corresponds e.g. to a service creation, this will result in the service being re-created with the new path.</p> <p>Since invoking the PCE module as described in the docs would be a useful feature, maybe this could be solved by resetting the input variable in pce listener after finishing processing a request.</p> TRNSPRTPCE-681

Invoking PCE module

Bug Medium Open Unresolved Unassigned Jonas Mårtensson Mon, 8 Aug 2022 06:50:25 +0000 Thu, 15 Sep 2022 18:50:45 +0000 0 2 <p>Thanks Jonas for having reported this point.<br/> Actually, I don't read that the developer guide evokes the internal/external aspect of the PCE API.<br/> Anyway, the PCE API works fine since it is used in the PCE functional tests (see <a href="https://git.opendaylight.org/gerrit/gitweb?p=transportpce.git;a=blob;f=tests/transportpce_tests/pce/test01_pce.py;h=cdfe103aa0791aa210d4ea66da4530f9d94508c7;hb=refs/heads/master" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=transportpce.git;a=blob;f=tests/transportpce_tests/pce/test01_pce.py;h=cdfe103aa0791aa210d4ea66da4530f9d94508c7;hb=refs/heads/master</a>).<br/> The description you give corresponds to the case where PCE is invoked through the ServiceHandler, so when it is integrated in the global end-to-end process. The documentation mentions a specific case where PCE is used rather like a standalone feature.</p> <p>Hi Gilles, maybe I read too much into it but the guide does specify the RESTCONF API for invoking the PCE, and to me, in the context of ODL, RESTCONF is an external API. Sure the API works fine in the functional tests where it is not mixed with service requests through the service handler. In our application we are using TPCE both for service requests and for standalone path computation, and mixing these does not work without modifying the code, as I explained in the issue description.</p> Development Rank 0|i042sf: