Initially I was also getting the same , to bypass this I did the mounting
manually
http://
{appc<http://%20%7bappc>-ip}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/clfwl01pgn6201
Body :
<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
<node-id>clfwl01pgn6201</node-id> <host
xmlns="urn:opendaylight:netconf-node-topology">10.247.83.123</host> <port
xmlns="urn:opendaylight:netconf-node-topology">2831</port> <username
xmlns="urn:opendaylight:netconf-node-topology">admin</username> <password
xmlns="urn:opendaylight:netconf-node-topology">admin</password> <tcp-only
xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only> <!--
non-mandatory fields with default values, you can safely remove these if you do
not wish to override any of these values--> <reconnect-on-changed-schema
xmlns="urn:opendaylight:netconf-node-topology">false</reconnect-on-changed-schema>
<connection-timeout-millis
xmlns="urn:opendaylight:netconf-node-topology">20000</connection-timeout-millis>
<max-connection-attempts
xmlns="urn:opendaylight:netconf-node-topology">0</max-connection-attempts>
<between-attempts-timeout-millis
xmlns="urn:opendaylight:netconf-node-topology">2000</between-attempts-timeout-millis>
<sleep-factor
xmlns="urn:opendaylight:netconf-node-topology">1.5</sleep-factor> <!--
keepalive-delay set to 0 turns off keepalives--> <keepalive-delay
xmlns="urn:opendaylight:netconf-node-topology">120</keepalive-delay> </node>
Changing the relevant parameters(node-id and host) and APPC started processing
the request.
Regards
Tapan M
From: [email protected]
[mailto:[email protected]] On Behalf Of MAHER, RANDA
Sent: Thursday, July 13, 2017 7:39 PM
To: Josef Reisinger <[email protected]>; onap-discuss
<[email protected]>
Subject: Re: [onap-discuss] VFW demo: APPC reports "Mount point does not exist"
when a policy to change the packer rate should be sent to pgn
Hi Josef,
Hector is looking into this. Looks like a step probably missed, investigating.
He will provide updates in Jira.
Thanks, Randa
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Josef Reisinger
Sent: Thursday, July 13, 2017 5:36 AM
To: onap-discuss
<[email protected]<mailto:[email protected]>>
Subject: [onap-discuss] VFW demo: APPC reports "Mount point does not exist"
when a policy to change the packer rate should be sent to pgn
Folks,
we got ONAP up on vanilla openstack and are "so close" to finish the vFW demo
scenario. We can see measurements being generated at the firewall node, trace
the message flow through DCAE components and policy to APPC where an action
should be triggered to increase/decrease the packet rate in the packet
generator. In the last step, we can see this error message
{ "errors":
{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount
point does not exist."}]}}appearing in karaf log.
The request in question looks like:
http://admin:[email protected]:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn/yang-ext:mount/sample-plugin:sample-plugin/pg-streams/<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.0.2.1-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_demofwl01pgn_yang-2Dext-3Amount_sample-2Dplugin-3Asample-2Dplugin_pg-2Dstreams_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=Re8u-N8fWloetxlcWy1lrD9dsPB2i6b8QVbNSc6ymS0&s=_DB7k_AIHfGt_2WDLovpakioqWxIEwudVKiqSI97KZo&e=>
I used to get node details if I shortened the url to
http://admin:[email protected]:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.0.2.1-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_demofwl01pgn&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=Re8u-N8fWloetxlcWy1lrD9dsPB2i6b8QVbNSc6ymS0&s=GIBolp10B3WgdR9v6Ko5P5gDdlC7EsZfz2Z_97CNNTc&e=>
Of course we did /opt/demo.sh APPC ... (often enough) on the robot VM, we could
even see this generating a message to APPC. We also rebooted/restarted some of
the components since the vFW stack was created - could this shave an impact on
the mounted state too?
More details are to be found in
https://jira.onap.org/browse/APPC-76<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_APPC-2D76&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=Re8u-N8fWloetxlcWy1lrD9dsPB2i6b8QVbNSc6ymS0&s=kT5SA7ul6XCoGdBpbedczSsZGamx2tuPSZY9pQ98Tvw&e=>
Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of
Nomadic Traits
IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius
IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel
Phone: +49 151 1426 4559
Mobile: +49-(0) 151 1426 4559
E-Mail: [email protected]<mailto:[email protected]>
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement, you may review at
https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
Amdocs Development Centre India Private Limited having CIN:
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A
limited liability partnership with LLP Identification Number: AAI-6901
effective 28th Feb 2017)
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
