Oh right….
> On Jun 8, 2017, at 11:41 PM, bharath thiruveedula <[email protected]> > wrote: > > > Viswa, > > Tried that approach of using the module name we use for ./demo.sh preload > and while creating VF module in GUI as instance name too. We got the same > error. > > -Bharath T > > From: Viswa KSP <[email protected]> > Sent: Thursday, June 8, 2017 11:37 PM > To: bharath thiruveedula > Cc: Ahmad, Munir; Viswa KSP; Kanagaraj Manickam; ROSE, DANIEL V; > [email protected] > Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? > > Bharath, > > I think we missed the sequencing… Preload with some name and then use the > same name while create VF module via GUI. Lets try that Tom. > > BR, > Viswa > >> On Jun 8, 2017, at 11:31 PM, bharath thiruveedula <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Ahmad, >> >> Yes, we did preload in Robot VM, all tests were passed, I can see entry in >> SDNC portal. >> >> >>Module name is something you come up with and will be used when click Add >> >>VF-Module >> >> Even before running ./demo.sh preload, I can see module when we click on >> "Add VF module". Even after running ./demo.sh preload I can see the same VF >> module, what we see before running. >> >> We tried to check db of MSO, we couldn't see entries of newly added VNF in >> VID app in 'VNF_recipe and VNF_resource' tables. >> >> Regards >> Bharath T >> >> From: Ahmad, Munir <[email protected] <mailto:[email protected]>> >> Sent: Thursday, June 8, 2017 10:44 PM >> To: Viswa KSP >> Cc: Kanagaraj Manickam; bharath thiruveedula; ROSE, DANIEL V; >> [email protected] <mailto:[email protected]> >> Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> Just to confirm you created an instance called DemoNS >> Then you created a VNF called it kspviswa-ns-inst1-vnf-inst1 then you did >> you preload? >> >> Preload requires your VNF name and module name. >> TutorialFirewall..base_vfw..module-0 does not seem like a good name for >> module name. >> >> Module name is something you come up with and will be used when click Add >> VF-Module >> >> ./demo.sh preload kspviswa-ns-inst1-vnf-inst1 kspviswa-ns-inst1-module-inst1 >> >> Thanks >> Munir >> >> From: Viswa KSP <[email protected] >> <mailto:[email protected]>> >> Date: Thursday, June 8, 2017 at 11:42 AM >> To: "Ahmad, Munir" <[email protected] <mailto:[email protected]>> >> Cc: Kanagaraj Manickam <[email protected] >> <mailto:[email protected]>>, bharath thiruveedula >> <[email protected] <mailto:[email protected]>>, "ROSE, DANIEL V" >> <[email protected] <mailto:[email protected]>>, "[email protected] >> <mailto:[email protected]>" <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> Here you go. It is quite apparent that, something is missing in MSO DB >> schema... Could you please let us know what are we missing??? >> >> Below are the logs while deploying NS and VNF in VID >> 15:15:12,940 INFO [stdout] (default task-25) URL : >> http://mso:8080/mso/async/services/CreateServiceInstanceInfra >> <http://mso:8080/mso/async/services/CreateServiceInstanceInfra> >> 15:15:13,094 INFO [stdout] (pool-13-thread-3) createServiceInstanceIncoming >> - >> {"requestDetails":{"requestInfo":{"instanceName":"DemoNS","source":"VID","suppressRollback":false},"modelInfo":{"modelType":"service","modelInvariantId":"d11fbeb3-35c9-4a61-81c3-75d9873bd94d","modelNameVersionId":"789bb384-4837-4550-a6e3-c7526a738816","modelName":"ONAP-demo-network-service","modelVersion":"1.0"},"requestParameters":{"userParams":[],"subscriptionServiceType":"vFW"},"subscriberInfo":{"globalSubscriberId":"Demo102"}}} >> 15:15:13,350 INFO [stdout] (pool-13-thread-3) INSIDE --> Complete MSO >> Process Done SUCCESSFULLY >> 15:15:13,352 INFO [stdout] (pool-13-thread-3) CompleteMsoProcess Response >> --> >> 15:15:13,352 INFO [stdout] (pool-13-thread-3) >> 15:17:21,012 INFO [stdout] (default task-30) URL : >> http://mso:8080/mso/async/services/CreateVnfInfra >> <http://mso:8080/mso/async/services/CreateVnfInfra> >> 15:17:21,349 INFO [stdout] (pool-13-thread-1) INSIDE --> Complete MSO >> Process Done SUCCESSFULLY >> 15:17:21,352 INFO [stdout] (pool-13-thread-1) CompleteMsoProcess Response >> --> >> 15:17:21,352 INFO [stdout] (pool-13-thread-1) >> 15:21:21,525 INFO [stdout] (Camunda Metrics Reporter) 15:21:21.525 [Camunda >> Metrics Reporter] DEBUG o.a.i.t.managed.ManagedTransaction - Opening JDBC >> Connection >> 15:21:21,526 INFO [stdout] (Camunda Metrics Reporter) 15:21:21.525 [Camunda >> Metrics Reporter] DEBUG o.c.b.e.i.p.e.M.insertMeterLog - ==> Preparing: >> insert into ACT_RU_METER_LOG (ID_, NAME_, VALUE_, TIMESTAMP_) values ( ?, ?, >> ?, ? ) >> 15:21:21,526 INFO [stdout] (Camunda Metrics Reporter) 15:21:21.526 [Camunda >> Metrics Reporter] DEBUG o.c.b.e.i.p.e.M.insertMeterLog - ==> Parameters: >> 20934ac7-4c5e-11e7-9abf-0242ac110003(String), >> activity-instance-start(String), 0(Long), 2017-06-08 15:21:21.525(Timestamp) >> 15:21:21,541 INFO [stdout] (Camunda Metrics Reporter) 15:21:21.541 [Camunda >> Metrics Reporter] DEBUG o.c.b.e.i.p.e.M.insertMeterLog - <== Updates: 1 >> 15:21:21,542 INFO [stdout] (Camunda Metrics Reporter) 15:21:21.542 [Camunda >> Metrics Reporter] DEBUG o.a.i.t.managed.ManagedTransaction - Closing JDBC >> Connection [Transaction-aware proxy for target Connection >> [org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@11614a76]] >> >> >> The below logs are from ApiHandlers/error.log >> 2017-06-08T15:02:32.057Z|8efe1d7e-df4b-4ac8-880e-8a358a248156|default >> task-2|getVfModuleType|InfraPortalClient|VF Module Type||ERROR|DataError|No >> VfModuleType found in DB|MSO-APIH-3006E Attribute MSO_PROP_APIHANDLER_INFRA >> not found in DB >> 2017-06-08T15:09:29.635Z|025f6d38-b430-47a9-b99c-a971e87d3e9f|default >> task-3|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 025f6d38-b430-47a9-b99c-a971e87d3e9f >> 2017-06-08T15:09:51.608Z|45deab97-ac16-4db9-914a-53ff3ea1a6bc|default >> task-7|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 45deab97-ac16-4db9-914a-53ff3ea1a6bc >> 2017-06-08T15:10:09.783Z|cd798737-a7ef-4d38-9c19-ec13e5a4b3a1|default >> task-11|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned cd798737-a7ef-4d38-9c19-ec13e5a4b3a1 >> 2017-06-08T15:10:42.475Z|3bbd8915-5b93-4e14-825a-dbfcb1b679e5|default >> task-16|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 3bbd8915-5b93-4e14-825a-dbfcb1b679e5 >> 2017-06-08T15:10:58.516Z|b75df4e0-352c-4235-a3ee-3f6692a1a458|default >> task-20|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned b75df4e0-352c-4235-a3ee-3f6692a1a458 >> 2017-06-08T15:15:12.895Z|5f22ccc8-4ebb-4e4e-8a37-40558b1daf26|default >> task-25|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 5f22ccc8-4ebb-4e4e-8a37-40558b1daf26 >> 2017-06-08T15:17:20.973Z|093d4765-7471-4b05-bcad-8236f10590d1|default >> task-30|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 093d4765-7471-4b05-bcad-8236f10590d1 >> 2017-06-08T15:19:29.214Z|9ae1e0ba-06e0-4b37-9672-44284cd02371|default >> task-34|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned 9ae1e0ba-06e0-4b37-9672-44284cd02371 >> 2017-06-08T15:19:29.224Z|9ae1e0ba-06e0-4b37-9672-44284cd02371|default >> task-34|getVfModuleType|InfraPortalClient|VF Module Type||ERROR|DataError|No >> VfModuleType found in DB|MSO-APIH-3006E Attribute MSO_PROP_APIHANDLER_INFRA >> not found in DB >> 2017-06-08T15:23:34.029Z|d0b960d9-5be2-4630-b80d-7a5e7d0c6707|default >> task-35|generateUUID|InfraPortalClient|||INFO|null||MSO-APIH-5021I Missing >> requestID. Assigned d0b960d9-5be2-4630-b80d-7a5e7d0c6707 >> 2017-06-08T15:23:34.044Z|d0b960d9-5be2-4630-b80d-7a5e7d0c6707|default >> task-35|getVfModuleType|InfraPortalClient|VF Module Type||ERROR|DataError|No >> VfModuleType found in DB|MSO-APIH-3006E Attribute MSO_PROP_APIHANDLER_INFRA >> not found in DB >> >> BR, >> Viswa >> >> On Thu, Jun 8, 2017 at 8:35 PM, Ahmad, Munir <[email protected] >> <mailto:[email protected]>> wrote: >> Please send us MSO docker logs captured during the steps of deploying VNF >> from VID. >> >> From: Viswa KSP <[email protected] >> <mailto:[email protected]>> >> Date: Thursday, June 8, 2017 at 10:45 AM >> To: "Ahmad, Munir" <[email protected] <mailto:[email protected]>> >> Cc: Kanagaraj Manickam <[email protected] >> <mailto:[email protected]>>, bharath thiruveedula >> <[email protected] <mailto:[email protected]>>, "ROSE, DANIEL V" >> <[email protected] <mailto:[email protected]>>, "[email protected] >> <mailto:[email protected]>" <[email protected] >> <mailto:[email protected]>> >> >> Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> Dear All, >> >> We ( Myself & Bharath ) progressed a little bit by manually calling REST >> APIs for AAI to create entry for relationship between subscriber, network >> service & tenant . LCP region automatically got populated. >> >> Then we were able to create service, create VNF successfully. However when >> we proceed to create VF Module, we hit below error : >> >> <image001.png> >> >> We then did ./demo.sh preload kspviswa-ns-inst1-vnf-inst1 >> TutorialFirewall..base_vfw..module-0 , however situation didn't improve. >> Could you let us know what we are missing here? >> >> BTW we tried debugging using code and here is our understanding. >> >> Portal component is calling VID component @ >> http://vid.api.simpledemo.openecomp.org:8080/vid/mso/mso_get_orch_reqs/filter=serviceInstanceId:EQUALS >> >> <http://vid.api.simpledemo.openecomp.org:8080/vid/mso/mso_get_orch_reqs/filter=serviceInstanceId:EQUALS>:<SERVICE >> ID>?r=0.758821279377281 >> VID Component then serves this request @ >> /mso_create_vfmodule_instance/{serviceInstanceId}/vnfs/{vnfInstanceId} as >> per source MsoController.java. >> Here, VID is trying to contact MSO @ >> /serviceInstances/v2/<serviceInstanceId>/vnfs/<vnfInstanceId>/vfmodules >> endpoint. >> As per System.properties file, >> mso.server.url=https://mso.api.simpledemo.openecomp.org:8443/ecomp/mso/infra >> <https://mso.api.simpledemo.openecomp.org:8443/ecomp/mso/infra> >> So, complete URL would be >> http://mso.api.simpledemo.openecomp.org:8989/ecomp/mso/infra/serviceInstances/v3/de2d685a-48b5-4eb8-b83c-e2b36f1a4c02/vnfs/72d5ebc7-3b9a-4ebf-bcc6-e08ed9ef2471/vfModules/ >> >> <http://mso.api.simpledemo.openecomp.org:8989/ecomp/mso/infra/serviceInstances/v3/de2d685a-48b5-4eb8-b83c-e2b36f1a4c02/vnfs/72d5ebc7-3b9a-4ebf-bcc6-e08ed9ef2471/vfModules/> >> However when we try to see list of containers running in MSO VM, we don't >> see anything listening in 8443 port. >> But... If we try to create another instance of network service with same >> instance name, we are getting exception from MSO. So it is quite clear that, >> there is a communication b/w VID & MSO, but we are not sure about the >> target. Could you please shed some light here. >> BR, >> Viswa >> >> On Thu, Jun 8, 2017 at 6:08 PM, Ahmad, Munir <[email protected] >> <mailto:[email protected]>> wrote: >> You can update open stack info >> >> /opt/eteshare/config/integration_robot_properties.py >> /opt/eteshare/config/vm_properties.py >> >> I recommend you look into all the config files in /opt/eteshare/config/ and >> update where necessary. >> >> You will also need to update public_net_id, vfw_image_name, etc for the two >> use cases. Below is the directory where the two heat and env files can be >> found. >> >> /var/opt/OpenECOMP_ETE/robot/assets/asdc/ >> >> Example for vfw it would be >> /var/opt/OpenECOMP_ETE/robot/assets/asdc/base_vfw/base_vfw.env >> >> >> From: <[email protected] >> <mailto:[email protected]>> on behalf of Kanagaraj >> Manickam <[email protected] >> <mailto:[email protected]>> >> Date: Thursday, June 8, 2017 at 12:13 AM >> To: bharath thiruveedula <[email protected] >> <mailto:[email protected]>>, "ROSE, DANIEL V" <[email protected] >> <mailto:[email protected]>>, "[email protected] >> <mailto:[email protected]>" <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> I observed that robot is pre-configured with static IP and rackspace related >> settings. But I am trying on the OpenStack setup. So Do we have any >> guidelines on configuring the robot before running the demo.sh. >> >> Thanks >> Kanagaraj M >> >> *************************************************************************************** >> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** >> >> *************************************************************************************** >> This e-mail and its attachments contain confidential information from >> HUAWEI, which is intended only for the person or entitywhose address is >> listed above. Any use of the information contained herein in any way >> (including, but not limited to, total orpartial disclosure, reproduction, >> or dissemination) by persons other than the intended recipient(s) is >> prohibited. If you receive thise-mail in error, please notify the sender by >> phone or email immediately and delete it! >> *************************************************************************************** >> >> From: [email protected] >> <mailto:[email protected]> >> [mailto:[email protected] >> <mailto:[email protected]>] On Behalf Of bharath >> thiruveedula >> Sent: 08 June 2017 00:39 >> To: ROSE, DANIEL V; [email protected] >> <mailto:[email protected]> >> Subject: Re: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> Hi Daniel, >> >> Thanks for the info. >> >> I tried to manually create subscriber using the following ReST URLs >> sequentially >> >> 1)PUT >> /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id} >> 2)PUT >> /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id} >> 3)PUT / >> business/customers/customer/{customer-id} >> 4)PUT >> /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type} >> 5)PUT /service-design-and-creation/services/service/$UUID >> >> I could see the subscriber list while deploy service instance. But while >> adding VNF to the service instance, I couldn't LCP region and tenant >> populated. I have provided cloud-region-id and tenant created in step-1 and >> step-2 while creating customer, aren't those LCP and tenant? Any additional >> request do I need to perform for this? >> >> The other questions on these exercise I have are: >> >> 1)Do we use subscriber to be tied with openstack tenant logically? so that >> whenever we deploy network service it deploys in the openstack tenant space >> to which subscriber is linked to(I am assuming this from the context of ReST >> API-3 above) >> >> 2)While adding VNF, we have a textbox called "Product Family", what does it >> refers to? Is it the same as service type we created in step-4? >> >> P.S: Daniel, any plans for creating/encouraging more of direct chat tools >> like IRC/Slack, am aware of existing IRC channels though? >> >> Best Regards >> Bharath T >> From: ROSE, DANIEL V <[email protected] <mailto:[email protected]>> >> Sent: Wednesday, June 7, 2017 12:38 AM >> To: bharath thiruveedula >> Subject: RE: Can we skip openstack verification in Robot VM? >> >> It is just a customer basically. Subscriber, openstack tenant, openstack >> region all have to be loaded into aai and that’s done with a rest api >> >> Thanks, >> >> Daniel Rose >> ECOMP / ONAP >> com.att.ecomp >> 732-420-7308 >> >> From: bharath thiruveedula [mailto:[email protected] >> <mailto:[email protected]>] >> Sent: Tuesday, June 06, 2017 2:46 PM >> To: ROSE, DANIEL V <[email protected] <mailto:[email protected]>> >> Subject: Re: Can we skip openstack verification in Robot VM? >> >> ah okay, makes sense! >> Can you please let me the know context behind the subscriber. Is there a way >> to populate subscriber list? >> >> Regards >> Bharath T >> >> From: ROSE, DANIEL V <[email protected] <mailto:[email protected]>> >> Sent: Wednesday, June 7, 2017 12:04 AM >> To: bharath thiruveedula; [email protected] >> <mailto:[email protected]> >> Subject: RE: Can we skip openstack verification in Robot VM? >> >> Robot isn’t checking anything, robot is doing steps to load data from >> openstack into aai. But all it is oing is reading openstack and loading data >> into AAI so you can def do that yourself if you feel so inclined. >> >> Thanks, >> >> Daniel Rose >> ECOMP / ONAP >> com.att.ecomp >> 732-420-7308 >> >> From: [email protected] >> <mailto:[email protected]> >> [mailto:[email protected] >> <mailto:[email protected]>] On Behalf Of bharath >> thiruveedula >> Sent: Tuesday, June 06, 2017 2:28 PM >> To: [email protected] <mailto:[email protected]> >> Subject: [onap-discuss] Can we skip openstack verification in Robot VM? >> >> Hi, >> >> I came till distribution of network service. But the next task is to run >> robot scripts in Robot VM. Is there any way to skip openstack related checks >> and directly populate subscribers list? I want to try to deploy directly >> after distributing network service, with out going to robot's way. >> >> Any directions to achieve this would be much helpful >> >> Regards >> Bharath T >> >> _______________________________________________ >> onap-discuss mailing list >> [email protected] <mailto:[email protected]> >> https://lists.onap.org/mailman/listinfo/onap-discuss >> <https://lists.onap.org/mailman/listinfo/onap-discuss>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
