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 : 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:<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 - 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]> 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]> on behalf of Kanagaraj > Manickam <[email protected]> > *Date: *Thursday, June 8, 2017 at 12:13 AM > *To: *bharath thiruveedula <[email protected]>, "ROSE, DANIEL V" < > [email protected]>, "[email protected]" < > [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 entity whose address is > listed above. Any use of the information contained herein in any way > (including, but not limited to, total or partial disclosure, > reproduction, or dissemination) by persons other than the intended > recipient(s) is prohibited. If you receive this e-mail in error, please > notify the sender by phone or email immediately and delete it! > ************************************************************ > *************************** > > > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org] *On Behalf Of *bharath thiruveedula > *Sent:* 08 June 2017 00:39 > *To:* ROSE, DANIEL V; [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]> > *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] > <[email protected]>] > *Sent:* Tuesday, June 06, 2017 2:46 PM > *To:* ROSE, DANIEL V <[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]> > *Sent:* Wednesday, June 7, 2017 12:04 AM > *To:* bharath thiruveedula; [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:onap-discuss-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *bharath > thiruveedula > *Sent:* Tuesday, June 06, 2017 2:28 PM > *To:* [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] > https://lists.onap.org/mailman/listinfo/onap-discuss > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
