Re: [onap-discuss] Failure to create the demo vfirewall VNF
Hi, Please refer to https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack> for setting up OOM on Kubernetes, on Racnher, in OpenStack. Please discard the update wrt DCAE (I said it’s merge, but not just yet). And please refer to https://wiki.onap.org/display/DW/vFWCL+instantiation%2C+testing%2C+and+debuging <https://wiki.onap.org/display/DW/vFWCL+instantiation,+testing,+and+debuging> for running vFWCL use case. Of course, without DCAE, you won’t have close loop. Thanks, Alexis > On Jan 9, 2018, at 1:36 PM, Ramanarayanan, Karthick <krama...@ciena.com> > wrote: > > Yes. > I checked at sdnc pods, vnf pods, mso pods. > Found nothing pertaining to the error. > A sample sdnc pod check (apart from other pods) > kubectl -n onap-sdnc -c sdnc-controller-container logs sdnc-1395102659-w48gp > > Now I have to redo this test again as I am running out of memory here. > Note that this is a 14 core(28 threads for 56 total in cpuinfo), > 128 gig ram. (Intel Xeon E5-2683 v3) > Before I ran the OOM, I had /proc/sys/vm/drop_caches done to just start with > a free memory of over > 120 gigs. (After clearing the kernel buffer caches for a big head start for > ONAP :) > > Then the kubernetes setup to relaunch onap/rancher,etc. > > These have been up for over 3-4 days now and now my free memory is almost > down to 30 gig > on the caches side. Free memory minus caches is a meagre 800 megs. > > Now suddenly the portals are unresponsive. > > The sdc frontend has stopped responding with gateway timeouts though I am > fire a curl sdc2/rest/version to the backend. Frontend is dead! > > Its a cluster fuck now. > > I will restart the onap setup again before redoing the demo vfwcl instance > create. > (also with delete rollback set to false during vf create as Marco suggested) > > Hopefully you have tested a demo instance creation on a k8s setup with OOM on > amsterdam. > (not with ONAP running on openstack as the demo video shows) > > Thanks, > -Karthick > > From: FREEMAN, BRIAN D <bf1...@att.com> > Sent: Tuesday, January 9, 2018 5:41:48 AM > To: Ramanarayanan, Karthick; onap-discuss@lists.onap.org > Subject: [**EXTERNAL**] RE: Failure to create the demo vfirewall VNF > > You need to look at SO logs for the SdncAdapter and VnfAdapter and see what > error you are getting from SDNC or Openstack in SO. > > Usually a delete implies that SO talks to SDNC correctly but then the > interaction with Openstack fails or when SO goes to SDNC or AAI for data to > create the Openstack heat stack create that it is failing. > > Brian > > > From: onap-discuss-boun...@lists.onap.org > [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, > Karthick > Sent: Monday, January 08, 2018 6:33 PM > To: onap-discuss@lists.onap.org > Subject: [onap-discuss] Failure to create the demo vfirewall VNF > > Hi, > I am trying to instantiate the demo vfirewall-vsink service instance based > on the video here: > > > https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Running-2Bthe-2BONAP-2BDemos-3Fpreview-3D_1015891_16010290_vFW-5Fclosed-5Floop.mp4-23RunningtheONAPDemos-2DVNFOnboarding-2CInstantiation-2CandClosed-2DloopOperations=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=sHFlwt9oUg4ii_TV8umfzXphNLbVnoPEvv0hj8YTj7s=> > > While I am able to move ahead and reach till the vf create step, the add VF > step > for both vfirewall and packet gen instance results in failure and moves to > pending delete. > (sdnc preload checkbox enabled) > > The setup I have is OOM configured for kubernetes. > I am on amsterdam release branch for OOM. > So its not using openstack heat templates > to instantiate ONAP. Rather just a single node configured with k8s oneclick. > > The difference in the video pertains to running demo-k8s.sh init from > oom/kubernetes/robot > to instantiate the customer models and services after copying the demo/heat > to kubernetes robot /share directory for the distribute the work. > > The demo vfirewall closed loop service seems to be distributed as seen in > the ONAP portal. > ( I have also tried redistributing) > I am trying to instantiate the service for demo vFWCL. > > Logs indicate nothing in sdnc after the vF create failure. > I don't see any requests hitting Openstack logs either. >
Re: [onap-discuss] Failure to create the demo vfirewall VNF
Yes. I checked at sdnc pods, vnf pods, mso pods. Found nothing pertaining to the error. A sample sdnc pod check (apart from other pods) kubectl -n onap-sdnc -c sdnc-controller-container logs sdnc-1395102659-w48gp Now I have to redo this test again as I am running out of memory here. Note that this is a 14 core(28 threads for 56 total in cpuinfo), 128 gig ram. (Intel Xeon E5-2683 v3) Before I ran the OOM, I had /proc/sys/vm/drop_caches done to just start with a free memory of over 120 gigs. (After clearing the kernel buffer caches for a big head start for ONAP :) Then the kubernetes setup to relaunch onap/rancher,etc. These have been up for over 3-4 days now and now my free memory is almost down to 30 gig on the caches side. Free memory minus caches is a meagre 800 megs. Now suddenly the portals are unresponsive. The sdc frontend has stopped responding with gateway timeouts though I am fire a curl sdc2/rest/version to the backend. Frontend is dead! Its a cluster fuck now. I will restart the onap setup again before redoing the demo vfwcl instance create. (also with delete rollback set to false during vf create as Marco suggested) Hopefully you have tested a demo instance creation on a k8s setup with OOM on amsterdam. (not with ONAP running on openstack as the demo video shows) Thanks, -Karthick From: FREEMAN, BRIAN D <bf1...@att.com> Sent: Tuesday, January 9, 2018 5:41:48 AM To: Ramanarayanan, Karthick; onap-discuss@lists.onap.org Subject: [**EXTERNAL**] RE: Failure to create the demo vfirewall VNF You need to look at SO logs for the SdncAdapter and VnfAdapter and see what error you are getting from SDNC or Openstack in SO. Usually a delete implies that SO talks to SDNC correctly but then the interaction with Openstack fails or when SO goes to SDNC or AAI for data to create the Openstack heat stack create that it is failing. Brian From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, Karthick Sent: Monday, January 08, 2018 6:33 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] Failure to create the demo vfirewall VNF Hi, I am trying to instantiate the demo vfirewall-vsink service instance based on the video here: https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Running-2Bthe-2BONAP-2BDemos-3Fpreview-3D_1015891_16010290_vFW-5Fclosed-5Floop.mp4-23RunningtheONAPDemos-2DVNFOnboarding-2CInstantiation-2CandClosed-2DloopOperations=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=sHFlwt9oUg4ii_TV8umfzXphNLbVnoPEvv0hj8YTj7s=> While I am able to move ahead and reach till the vf create step, the add VF step for both vfirewall and packet gen instance results in failure and moves to pending delete. (sdnc preload checkbox enabled) The setup I have is OOM configured for kubernetes. I am on amsterdam release branch for OOM. So its not using openstack heat templates to instantiate ONAP. Rather just a single node configured with k8s oneclick. The difference in the video pertains to running demo-k8s.sh init from oom/kubernetes/robot to instantiate the customer models and services after copying the demo/heat to kubernetes robot /share directory for the distribute the work. The demo vfirewall closed loop service seems to be distributed as seen in the ONAP portal. ( I have also tried redistributing) I am trying to instantiate the service for demo vFWCL. Logs indicate nothing in sdnc after the vF create failure. I don't see any requests hitting Openstack logs either. The VNF preload operation seems to have succeeded for the firewall closed loop instances. The VNF profiles are also present in sdnc. I get back a http success (status code 200) with the request id as expected. A subsequent GET request for vnf topology information preloaded also works. Doing a POST using sdnc api (port 8282) works for the vnf topology preload step. But I see nothing in the logs for sdnc pods. (nothing relevant in sdc/mso pod either if that matters) Here is a snippet from curl to sdnc as well: curl -vX POST http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/operations/VNF-API:preload-vnf-topology-operation<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.43.172.252-3A8282_restconf_operations_VNF-2DAPI-3Apreload-2Dvnf-2Dtopology-2Doperation=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=Y3ruJ6Ym6EbR64sGaBOkI3m5Zw_Jgydl8PWX83NzX58=> -d @firewall.json --header "Content-Type: application/json"
Re: [onap-discuss] Failure to create the demo vfirewall VNF
You need to look at SO logs for the SdncAdapter and VnfAdapter and see what
error you are getting from SDNC or Openstack in SO.
Usually a delete implies that SO talks to SDNC correctly but then the
interaction with Openstack fails or when SO goes to SDNC or AAI for data to
create the Openstack heat stack create that it is failing.
Brian
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan,
Karthick
Sent: Monday, January 08, 2018 6:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Failure to create the demo vfirewall VNF
Hi,
I am trying to instantiate the demo vfirewall-vsink service instance based on
the video here:
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Running-2Bthe-2BONAP-2BDemos-3Fpreview-3D_1015891_16010290_vFW-5Fclosed-5Floop.mp4-23RunningtheONAPDemos-2DVNFOnboarding-2CInstantiation-2CandClosed-2DloopOperations=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=sHFlwt9oUg4ii_TV8umfzXphNLbVnoPEvv0hj8YTj7s=>
While I am able to move ahead and reach till the vf create step, the add VF
step
for both vfirewall and packet gen instance results in failure and moves to
pending delete.
(sdnc preload checkbox enabled)
The setup I have is OOM configured for kubernetes.
I am on amsterdam release branch for OOM.
So its not using openstack heat templates
to instantiate ONAP. Rather just a single node configured with k8s oneclick.
The difference in the video pertains to running demo-k8s.sh init from
oom/kubernetes/robot
to instantiate the customer models and services after copying the demo/heat
to kubernetes robot /share directory for the distribute the work.
The demo vfirewall closed loop service seems to be distributed as seen in the
ONAP portal.
( I have also tried redistributing)
I am trying to instantiate the service for demo vFWCL.
Logs indicate nothing in sdnc after the vF create failure.
I don't see any requests hitting Openstack logs either.
The VNF preload operation seems to have succeeded for the firewall closed loop
instances.
The VNF profiles are also present in sdnc.
I get back a http success (status code 200) with the request id as expected.
A subsequent GET request for vnf topology information preloaded also works.
Doing a POST using sdnc api (port 8282) works for the vnf topology preload
step.
But I see nothing in the logs for sdnc pods. (nothing relevant in sdc/mso pod
either if that matters)
Here is a snippet from curl to sdnc as well:
curl -vX POST
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/operations/VNF-API:preload-vnf-topology-operation<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.43.172.252-3A8282_restconf_operations_VNF-2DAPI-3Apreload-2Dvnf-2Dtopology-2Doperation=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=Y3ruJ6Ym6EbR64sGaBOkI3m5Zw_Jgydl8PWX83NzX58=>
-d @firewall.json --header "Content-Type: application/json"
Response status is http 200 as expected.
{
"output": {
"svc-request-id": "robot12",
"response-code": "200",
"ack-final-indicator": "Y"
}
}
Trying to do a get request for the vnf topology preload information POST
request above also returns expected information:
curl -sSL
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/config/VNF-API:preload-vnfs/vnf-preload-list/vfirewall-1/3d6f8762Fea8453fBd9a..base_vfw..module-0/preload-data/vnf-topology-information/vnf-topology-identifier<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.43.172.252-3A8282_restconf_config_VNF-2DAPI-3Apreload-2Dvnfs_vnf-2Dpreload-2Dlist_vfirewall-2D1_3d6f8762Fea8453fBd9a..base-5Fvfw..module-2D0_preload-2Ddata_vnf-2Dtopology-2Dinformation_vnf-2Dtopology-2Didentifier=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=VTydHcis8-MU0ztKmrS3--wrND4fGUtoupQgN4GyHZg=B-rVkAB1IjmgsV0NyrefoQR6XTfJmsEwekYrrdqmw-0=>
| jq .
{
"vnf-topology-identifier": {
"vnf-name": "vfirewall-1",
"generic-vnf-type": "3d6f8762-fea8-453f-bd9a 0",
"generic-vnf-name": "firewall-vnf",
"vnf-type": "3d6f8762Fea8453fBd9a..base_vfw..module-0",
"service-type": "5b5c134c-662e-407e-bc4c-4200b4b5cb02"
}
}
I am also attaching the firewall.json POST request for vnf toplogy preload to
sdnc portal.
The VNF profiles have all been added to sdnc portal
Re: [onap-discuss] Failure to create the demo vfirewall VNF
Karthick,
Make sure you set “delete on rollback” to false in vid. The exceeded number of
polls error is benign but it still deletes the VF module if the delete option
is set to true.
Marco
On Mon, Jan 8, 2018 at 9:36 PM -0500, "Ramanarayanan, Karthick"
<krama...@ciena.com<mailto:krama...@ciena.com>> wrote:
Hi Marco,
Thanks for the response.
Comments inline.
I have retried now with the changes to demo versions but doesn't change the
equation.
Same status as before.
More inline ...
>What error are you getting precisely?
I get maximum poll attempts exceeded.
I thought that's a benign error for the GUI waiting to refresh on request
status.
But after that, refreshing the service instance list, moves the VF to pending
delete.
(also unable to delete once in this state as mentioned earlier. No hint in
sdnc/mso/vid portal logs whatsoever)
Here's a snapshot for your perusal:
https://www.dropbox.com/s/z6b69aq40k6hw61/Screenshot%202018-01-08%2018.25.06.png?dl=<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_z6b69aq40k6hw61_Screenshot-25202018-2D01-2D08-252018.25.06.png-3Fdl-3D=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=-TKsKw1u370_qua5HDVvQ0303RXCgqk3oIGO5_ocicQ=rWZRrdvJWuQgfy0MF1xPCJsKhQGcpPRsqxfwEVYWv6M=>
> How did you set onap-parameters.yaml in OOM? The OpenStack parameters are
> used by SO to instantiate the VNFs.
Yes. I am aware about that. As without that, model init through demo-k8s robot
would have failed anyway.
Here's the onap-parameters.yaml for our k8s environment under
oom/kubernetes/config:
#cat onap-parameters.yaml
--
OPENSTACK_UBUNTU_14_IMAGE: "Ubuntu_14.04.5_LTS"
OPENSTACK_PUBLIC_NET_ID: "aff52391-359f-4264-9768-1948c83021bc"
OPENSTACK_OAM_NETWORK_ID: "abd45e55-bbac-4ec4-84cf-38479b1cf075"
OPENSTACK_OAM_SUBNET_ID: "28222064-0f44-4758-94c5-72eaaf726837"
OPENSTACK_OAM_NETWORK_CIDR: "10.0.0.0/26"
OPENSTACK_USERNAME: "onap"
OPENSTACK_API_KEY: "secret"
OPENSTACK_TENANT_NAME: "onap"
OPENSTACK_TENANT_ID: "45947f2541a34498b340eb93b56b5c24"
OPENSTACK_REGION: "RegionOne"
OPENSTACK_KEYSTONE_URL:
"http://192.168.42.240/identity;<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.42.240_identity-2522=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=-TKsKw1u370_qua5HDVvQ0303RXCgqk3oIGO5_ocicQ=eM8vOHX-aAqfl8OJCRiLbimCxELjrLH4QiNkrLWZL74=>
OPENSTACK_FLAVOUR_MEDIUM: "m1.small"
OPENSTACK_SERVICE_TENANT_NAME: "service"
DMAAP_TOPIC: "AUTO"
DEMO_ARTIFACTS_VERSION: "1.1.0-SNAPSHOT"
Maybe the DEMO artifacts version above needs to be 1.1.1 as I haven't changed
that yet.
Can try with that if you think that's the issue.
>Also, note that for Amsterdam release, the following parameters should be used:
Done. Posted the vnf preload topology operation with demo artifacts 1.1.1 and
install 1.1.1.
Confirmed with a GET as well to see the new posted data for the vnfs.
Same error as mentioned above.
Regards,
-Karthick
From: <onap-discuss-boun...@lists.onap.org> on behalf of "Ramanarayanan,
Karthick" <krama...@ciena.com>
Date: Monday, January 8, 2018 at 6:32 PM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] Failure to create the demo vfirewall VNF
{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.0"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.0-SNAPSHOT"
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
Re: [onap-discuss] Failure to create the demo vfirewall VNF
Hi Marco,
Thanks for the response.
Comments inline.
I have retried now with the changes to demo versions but doesn't change the
equation.
Same status as before.
More inline ...
>What error are you getting precisely?
I get maximum poll attempts exceeded.
I thought that's a benign error for the GUI waiting to refresh on request
status.
But after that, refreshing the service instance list, moves the VF to pending
delete.
(also unable to delete once in this state as mentioned earlier. No hint in
sdnc/mso/vid portal logs whatsoever)
Here's a snapshot for your perusal:
https://www.dropbox.com/s/z6b69aq40k6hw61/Screenshot%202018-01-08%2018.25.06.png?dl=
> How did you set onap-parameters.yaml in OOM? The OpenStack parameters are
> used by SO to instantiate the VNFs.
Yes. I am aware about that. As without that, model init through demo-k8s robot
would have failed anyway.
Here's the onap-parameters.yaml for our k8s environment under
oom/kubernetes/config:
#cat onap-parameters.yaml
--
OPENSTACK_UBUNTU_14_IMAGE: "Ubuntu_14.04.5_LTS"
OPENSTACK_PUBLIC_NET_ID: "aff52391-359f-4264-9768-1948c83021bc"
OPENSTACK_OAM_NETWORK_ID: "abd45e55-bbac-4ec4-84cf-38479b1cf075"
OPENSTACK_OAM_SUBNET_ID: "28222064-0f44-4758-94c5-72eaaf726837"
OPENSTACK_OAM_NETWORK_CIDR: "10.0.0.0/26"
OPENSTACK_USERNAME: "onap"
OPENSTACK_API_KEY: "secret"
OPENSTACK_TENANT_NAME: "onap"
OPENSTACK_TENANT_ID: "45947f2541a34498b340eb93b56b5c24"
OPENSTACK_REGION: "RegionOne"
OPENSTACK_KEYSTONE_URL: "http://192.168.42.240/identity;
OPENSTACK_FLAVOUR_MEDIUM: "m1.small"
OPENSTACK_SERVICE_TENANT_NAME: "service"
DMAAP_TOPIC: "AUTO"
DEMO_ARTIFACTS_VERSION: "1.1.0-SNAPSHOT"
Maybe the DEMO artifacts version above needs to be 1.1.1 as I haven't changed
that yet.
Can try with that if you think that's the issue.
>Also, note that for Amsterdam release, the following parameters should be used:
Done. Posted the vnf preload topology operation with demo artifacts 1.1.1 and
install 1.1.1.
Confirmed with a GET as well to see the new posted data for the vnfs.
Same error as mentioned above.
Regards,
-Karthick
From: <onap-discuss-boun...@lists.onap.org> on behalf of "Ramanarayanan,
Karthick" <krama...@ciena.com>
Date: Monday, January 8, 2018 at 6:32 PM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] Failure to create the demo vfirewall VNF
{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.0"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.0-SNAPSHOT"
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
Re: [onap-discuss] Failure to create the demo vfirewall VNF
Karthick,
What error are you getting precisely? How did you set onap-parameters.yaml in
OOM? The OpenStack parameters are used by SO to instantiate the VNFs. Also,
note that for Amsterdam release, the following parameters should be used:
{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.1"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.1"
}
When I shoot the video, the release wasn’t cut yet, so I had to use 1.1.0 and
1.1.0-SNAPSHOT respectively.
Marco
From: <onap-discuss-boun...@lists.onap.org> on behalf of "Ramanarayanan,
Karthick" <krama...@ciena.com>
Date: Monday, January 8, 2018 at 6:32 PM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] Failure to create the demo vfirewall VNF
{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.0"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.0-SNAPSHOT"
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
[onap-discuss] Failure to create the demo vfirewall VNF
Hi,
I am trying to instantiate the demo vfirewall-vsink service instance based on
the video here:
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations
While I am able to move ahead and reach till the vf create step, the add VF
step
for both vfirewall and packet gen instance results in failure and moves to
pending delete.
(sdnc preload checkbox enabled)
The setup I have is OOM configured for kubernetes.
I am on amsterdam release branch for OOM.
So its not using openstack heat templates
to instantiate ONAP. Rather just a single node configured with k8s oneclick.
The difference in the video pertains to running demo-k8s.sh init from
oom/kubernetes/robot
to instantiate the customer models and services after copying the demo/heat
to kubernetes robot /share directory for the distribute the work.
The demo vfirewall closed loop service seems to be distributed as seen in the
ONAP portal.
( I have also tried redistributing)
I am trying to instantiate the service for demo vFWCL.
Logs indicate nothing in sdnc after the vF create failure.
I don't see any requests hitting Openstack logs either.
The VNF preload operation seems to have succeeded for the firewall closed loop
instances.
The VNF profiles are also present in sdnc.
I get back a http success (status code 200) with the request id as expected.
A subsequent GET request for vnf topology information preloaded also works.
Doing a POST using sdnc api (port 8282) works for the vnf topology preload
step.
But I see nothing in the logs for sdnc pods. (nothing relevant in sdc/mso pod
either if that matters)
Here is a snippet from curl to sdnc as well:
curl -vX POST
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/operations/VNF-API:preload-vnf-topology-operation
-d @firewall.json --header "Content-Type: application/json"
Response status is http 200 as expected.
{
"output": {
"svc-request-id": "robot12",
"response-code": "200",
"ack-final-indicator": "Y"
}
}
Trying to do a get request for the vnf topology preload information POST
request above also returns expected information:
curl -sSL
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/config/VNF-API:preload-vnfs/vnf-preload-list/vfirewall-1/3d6f8762Fea8453fBd9a..base_vfw..module-0/preload-data/vnf-topology-information/vnf-topology-identifier
| jq .
{
"vnf-topology-identifier": {
"vnf-name": "vfirewall-1",
"generic-vnf-type": "3d6f8762-fea8-453f-bd9a 0",
"generic-vnf-name": "firewall-vnf",
"vnf-type": "3d6f8762Fea8453fBd9a..base_vfw..module-0",
"service-type": "5b5c134c-662e-407e-bc4c-4200b4b5cb02"
}
}
I am also attaching the firewall.json POST request for vnf toplogy preload to
sdnc portal.
The VNF profiles have all been added to sdnc portal for the 2 vfs.
But still VF create request (for both vfirewall sink and packetgen) results in
failure and moves transaction to pending delete.
No api request traces in Openstack as well and neither do I see any volume
creates for the vnf instance.
Also once in pending delete, I cannot delete the instance as well.
I am also enclosing the firewall POST json request for one of the vfirewall
vnfs that was preloaded to sdnc
vnf topology information as a POST. (mentioned above)
Attaching it inline to this mail --
{
"input": {
"vnf-topology-information": {
"vnf-topology-identifier": {
"service-type": "5b5c134c-662e-407e-bc4c-4200b4b5cb02",
"vnf-name": "vfirewall-1",
"vnf-type": "3d6f8762Fea8453fBd9a..base_vfw..module-0",
"generic-vnf-name": "firewall-vnf",
"generic-vnf-type": "3d6f8762-fea8-453f-bd9a 0"
},
"vnf-assignments": {
"availability-zones": [],
"vnf-networks": [],
"vnf-vms": []
},
"vnf-parameters":
[
{
"vnf-parameter-name": "image_name",
"vnf-parameter-value": "Ubuntu_14.04.5_LTS"
},
{
"vnf-parameter-name": "flavor_name",
"vnf-parameter-value": "m1.small"
},
{
"vnf-parameter-name": "public_net_id",
"vnf-parameter-value": "aff52391-359f-4264-9768-1948c83021bc"
},
{
"vnf-parameter-name": "unprotected_private_net_id",
"vnf-parameter-value": "zdfw1fwl01_unprotected"
},
{
"vnf-parameter-name": "unprotected_private_subnet_id",
"vnf-parameter-value": "zdfw1fwl01_unprotected_sub"
},
{
"vnf-parameter-name": "protected_private_net_id",
"vnf-parameter-value": "zdfw1fwl01_protected"
},
{
"vnf-parameter-name": "protected_private_subnet_id",
"vnf-parameter-value": "zdfw1fwl01_protected_sub"
},
{
"vnf-parameter-name": "onap_private_net_id",
"vnf-parameter-value": "private"
},
{
"vnf-parameter-name": "onap_private_subnet_id",
"vnf-parameter-value": "private"
},
{
"vnf-parameter-name":
