Suraj We found that we needed to do a fair bit more than just create a subscriber in order to launch our VNF, so we haven?t yet distilled it all down to Python scripts yet. We have created a couple of bash scripts and instructions for the process that worked for us. The scripts are attached and the process is as follows.
1. Run the first step from the https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model tutorial (running the demo.sh init script) 2. Create a service, subscriber and service subscription with the create_subscriber.sh script, eg. ./create_subscriber.sh <AAI VM IP address> Demo2 Clearwater Rackspace IAD 1234567 3. Run the next two steps from the https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model tutorial, creating a service instance and a VNF. When creating the service instance you should find that the subscriber name you supplied to create_subscriber.sh (Demo2 in the example above) is a choice in the ?Subscriber Name? drop-down, and the service type (Clearwater in the above example) is a choice in the ?Service Type? drop-down. Click the Add VF Module button and at this point you should have a screen that looks a bit like this (obviously your values will differ). [cid:image001.jpg at 01D2BDBA.71AEE620] 4. Sign up to the SDNC GUI at http://<SDNC_VM_IP>:8843/signup<http://%3cSDNC_VM_IP%3e:8843/signup>, then log in at http://<SDNC_VM_IP>:8843/login<http://%3cSDNC_VM_IP%3e:8843/login> with those credentials (it doesn?t matter what user name or password you use). 5. Select Profiles, VNF Profile from the drop-down menu. Click on the Add VNF Profile, fill in the pop-up form and press Submit. The VNF Type field in the form must be set to the text from the button that appears when you press the Add VF Module button in the VID GUI (this will be of the form ?47d2b046866b421eA9d6..base_vfw..module-0? or ?Clearwater..base_clearwater..module-0? depending on how you onboarded your VNF). Set availability zone count to 999 and equipment role to robot-ete-t. 6. Create a VNF topology JSON document for your VNF from the skeleton used for the VFW demo, as follows. { 'input': { 'request-information': { 'notification-url': 'openecomp.org', 'order-number': '1', 'order-version': '1', 'request-action': 'PreloadVNFRequest', 'request-id': 'robot12' }, 'sdnc-request-header': { 'svc-action': 'reserve', 'svc-notification-url': 'http://openecomp.org:8080/adapters/rest/SDNCNotify', 'svc-request-id': 'robot12' }, 'vnf-topology-information': { 'vnf-assignments': { 'availability-zones': [], 'vnf-networks': [], 'vnf-vms': [] }, 'vnf-parameters': [ {'vnf-parameter-name': 'repo_url_blob', 'vnf-parameter-value': 'https://nexus.onap.org/content/repositories/raw'}, {'vnf-parameter-name': 'repo_url_artifacts', 'vnf-parameter-value': 'https://nexus.onap.org/content/groups/staging'}, {'vnf-parameter-name': 'demo_artifacts_version', 'vnf-parameter-value': '1.0.0'}, {'vnf-parameter-name': 'ecomp_private_net_id', 'vnf-parameter-value': 'oam_ecomp_urc0'}, {'vnf-parameter-name': 'ecomp_private_subnet_id', 'vnf-parameter-value': 'oam_ecomp_urc0'}, {'vnf-parameter-name': 'ecomp_private_net_cidr', 'vnf-parameter-value': '10.0.0.0/8'}, {'vnf-parameter-name': 'unprotected_private_net_id', 'vnf-parameter-value': 'demofwl_unprotected'}, {'vnf-parameter-name': 'protected_private_net_id', 'vnf-parameter-value': 'demofwl_protected'}, {'vnf-parameter-name': 'protected_private_net_cidr', 'vnf-parameter-value': '192.168.120.0/24'}, {'vnf-parameter-name': 'unprotected_private_net_cidr', 'vnf-parameter-value': '192.168.110.0/24'}, {'vnf-parameter-name': 'vfw_private_ip_0', 'vnf-parameter-value': '192.168.110.100'}, {'vnf-parameter-name': 'vfw_private_ip_1', 'vnf-parameter-value': '192.168.120.100'}, {'vnf-parameter-name': 'vfw_private_ip_2', 'vnf-parameter-value': '10.1.0.11'}, {'vnf-parameter-name': 'vpg_private_ip_0', 'vnf-parameter-value': '192.168.110.200'}, {'vnf-parameter-name': 'vpg_private_ip_1', 'vnf-parameter-value': '10.1.0.12'}, {'vnf-parameter-name': 'vsn_private_ip_0', 'vnf-parameter-value': '192.168.120.250'}, {'vnf-parameter-name': 'vsn_private_ip_1', 'vnf-parameter-value': '10.1.0.13'}, {'vnf-parameter-name': 'vfw_name_0', 'vnf-parameter-value': 'demofwl01fwl'}, {'vnf-parameter-name': 'vpg_name_0', 'vnf-parameter-value': 'demofwl01pgn'}, {'vnf-parameter-name': 'vsn_name_0', 'vnf-parameter-value': 'demofwl01snk'}, {'vnf-parameter-name': 'dcae_collector_ip', 'vnf-parameter-value': '10.0.4.102'}, {'vnf-parameter-name': 'dcae_collector_port', 'vnf-parameter-value': '8080'}, {'vnf-parameter-name': 'key_name', 'vnf-parameter-value': 'vfw_keydemo'}, {'vnf-parameter-name': 'pub_key', 'vnf-parameter-value': 'ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAqqnA9BAiMLtjOPSYBfhzLu4CiBolWoskDg4KVwhTJVTTeB6CqrQNcadlGXxOHhCYuNCKkUmIVF4WTOisVOJ75Z1c4OMoZLL85xVPKSIeH63kgVugwgPYQu55NbbWX+rsbUha3LnElDhNviMM3iTPbD5nnhKixNERAJMTLKXvZZZGqxW94bREknYPQTT2qrk3YRqwldncopp6Nkgv3AnSJz2gc9tjxnWF0poTQnQm/3D6hiJICrzKfAV0EaPN0KdtYjPhKrYoy6Qb/tKOVaaqsvwfKBJGrT9LfcA7D7M/yj292RT1XN63hI84WC383LsaPJ6eWdDTE6zUP1eGTWCoOw== rsa-key-20161026'} ], 'vnf-topology-identifier': { 'generic-vnf-name': 'DemoVNF', 'generic-vnf-type': 'demoVFW/47d2b046-866b-421e-a9d6 1', 'service-type': '85b65e3e-fb8e-4276-bdd5-53e4445cfef0', 'vnf-name': 'DemoModule', 'vnf-type': '47d2b046866b421eA9d6..base_vfw..module-0' } } } } The bits of this you will need to change are the vnf-parameters and vnf-topology-identifier sections. * The vnf-parameters are based on the environment file you supplied when you onboarded your VSP. I?m not 100% sure which parameters must appear in this section, what worked for us was to supply a value for every parameter in our environment file except for any image_name and flavour_name parameters. * The vnf-topology-identifier fields should be set as follows. * generic-vnf-name is the name you supplied when you created the VNF instance, which should be displayed in the VNF line when you look at your service instance in VID (for example DemoVNF in the above screenshot) * generic-vnf-type is the type displayed in the VNF line in VID ('demoVFW/47d2b046-866b-421e-a9d6 1? in the screenshot) * service-type is the service instance ID from the VID GUI * vnf-name can be set to any suitable name for the VF Module instance * vnf-type is the VNF Type you specified when you created the VNF profile in the SDNC admin GUI. 7. Upload the VNF topology to SDNC with the upload_vnf_topology.sh script, eg. ./upload_vnf_topology <SDNC VM IP address> vnf_topology.json 8. You should now be able to launch your VF Module from the VID GUI. We found that the request timed out in the GUI (VID polls 7 times at 10 second intervals), but the underlying openstack stack create command continued to run and our VF Module launched successfully. I hope this helps ? let me know if you have any questions. Regards, Mike From: Suraj Bisht [mailto:surajbi...@gmail.com] Sent: 25 April 2017 04:28 To: Mike Evans <mike at metaswitch.com> Cc: ROSE, DANIEL V <DR695H at att.com>; onap-discuss at lists.onap.org Subject: Re: [onap-discuss] Creating ONAP subscribers Hi Mike, We are facing same issue during creating subscriber, can you share python script for subscriber creation? Is there any procedure for creating subscriber through Portal/SDC GUI? Thanks, Suraj On Wed, Apr 19, 2017 at 8:23 AM, Mike Evans via onap-discuss <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> wrote: Daniel I?ve made good progress today reading through the robot scripts and infrastructure, to the point where I?ve been able to add a test subscriber for Clearwater using a hand-crafted curl command. I?m currently blocked on the MSO bug, so launching my Clearwater IMS core fails in the same way as trying to launch vFW or vLB, so I should be able to test it once the MSO fix is available (hopefully later today). I?m in the process of writing a small Python command line app to manage subscribers and their services based on what I?ve learnt, and I?m happy to share this when it?s working. Mike From: ROSE, DANIEL V [mailto:DR695H at att.com<mailto:dr6...@att.com>] Sent: 19 April 2017 14:17 To: Mike Evans <mike at metaswitch.com<mailto:mike at metaswitch.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: RE: [onap-discuss] Creating ONAP subscribers Under the hood this uses python. I will try and take a look at the Clearwater ims and see if I can onboard it and give you an example of what is needed. I think we may also enhance the demo script to split out some steps so that people who want to use their own vnfs can use them. Also for release 2 we are looking to reduce some of the extra stuff needed Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308<tel:(732)%20420-7308> From: Mike Evans [mailto:m...@metaswitch.com] Sent: Wednesday, April 19, 2017 3:14 AM To: ROSE, DANIEL V <DR695H at att.com<mailto:DR695H at att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: RE: [onap-discuss] Creating ONAP subscribers I was afraid you would say that ? I?d looked at the robot scripts in the robot VM and didn?t find them very readable. I?m in the process of creating some simple Python tools to configure subscribers and services ? I?ll post them back here when I have them working. Mike -- Mike Evans VP Systems Architecture +44 208 366 1177<tel:+44%2020%208366%201177> Metaswitch www.metaswitch.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.metaswitch.com_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=JvzECEiSGvQJBykYO2_sriGo0jUFr4DSxx2Dr4pgHWM&s=0C-8Ug_c72pkCkSq4fp4BfSn5olVjurYoyLgqqxeVtU&e=> From: ROSE, DANIEL V [mailto:dr6...@att.com] Sent: 18 April 2017 18:57 To: Mike Evans <mike at metaswitch.com<mailto:mike at metaswitch.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: [onap-discuss] Creating ONAP subscribers https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tutorial-253A-2BCreating-2Ba-2BService-2BInstance-2Bfrom-2Ba-2BDesign-2BModel&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=JvzECEiSGvQJBykYO2_sriGo0jUFr4DSxx2Dr4pgHWM&s=iVsMEdyMzbVjYZl7jkizeeLutQ349j6CkiCSTD2qVyU&e=> talks about the demo.sh init command, and that is what is doing that. Check out testsuite\robot\testsuites\demo.robot in the testsuite repo for what needs to be done, unfortunately its not very well documented at this point and we are looking at making it easier Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308<tel:(732)%20420-7308> From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mike Evans via onap-discuss Sent: Tuesday, April 18, 2017 12:44 PM To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: [onap-discuss] Creating ONAP subscribers I?m try to do a trial onboard of our Clearwater IMS core onto ONAP. I?ve got as far as onboarding the VNF and creating and distributing a service, but I can?t deploy it because I don?t have a subscriber set up for the service. Are there any instructions for how to do this? Mike -- Mike Evans VP Systems Architecture +44 208 366 1177<tel:+44%2020%208366%201177> Metaswitch www.metaswitch.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.metaswitch.com_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=ESAt66KL4o_bX10euIEeTPogc9q1NaC-QY_KFKvdrcs&s=VzGUrAsDvbovKb3Gu2BfRJ8lmwYQ6WvFV-c6XzZWvNo&e=> _______________________________________________ onap-discuss mailing list onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170425/130274c7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 62111 bytes Desc: image001.jpg URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170425/130274c7/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: create_subscriber.sh Type: application/octet-stream Size: 1332 bytes Desc: create_subscriber.sh URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170425/130274c7/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: upload-vnf-topology.sh Type: application/octet-stream Size: 405 bytes Desc: upload-vnf-topology.sh URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170425/130274c7/attachment-0001.obj>
