Hi, In my app, I create a customer, then a service subscription, then a service instance.
After that I create the service elements, in my case x-connects traffic engineering tunnels, and I create the relation between each tunnel to its corresponding customer id, an service instance. You can find a tutorial here https://wiki.onap.org/pages/viewpage.action?pageId=10780854 and here https://wiki.onap.org/pages/viewpage.action?pageId=13599492. For your case, you might create pnfs (physical network funcations) to represent the routers, I show example from my app below: GET: https://aai.api.simpledemo.onap.org:8443/aai/v11/network/pnfs/pnf/PE1 AAI RESPONSE: <?xml version="1.0" encoding="UTF-8"?> <pnf xmlns="http://org.openecomp.aai.inventory/v11";> <pnf-name>PE1</pnf-name> <equip-type>router</equip-type> <equip-vendor>Juniper</equip-vendor> <equip-model>vMX</equip-model> <ipaddress-v4-oam>172.16.1.101</ipaddress-v4-oam> <sw-version>16.2R1</sw-version> <in-maint>false</in-maint> <resource-version>1509719242452</resource-version> </pnf> Abdelmuhaimen Seaudi Orange Labs Egypt Email: [email protected]<mailto:[email protected]> Mobile: +2012 84644 733 From: [email protected] [mailto:[email protected]] On Behalf Of Michael Still Sent: Monday, November 20, 2017 6:29 AM To: [email protected] Subject: [onap-discuss] [AAI] Modelling physical hardware in ONAP AAI Hi, I have a use case where we are managing a network of SDN switches. We would like to use ONAP AAI to handle the inventory management for ports on these switches, as well as modelling which switches are in what locations (and how they interconnect with each other). I haven't been able to find any examples of how I would do such a thing in AAI, although its entirely possible that I've missed something obvious. Does the team have any pointers on getting started? Thanks, Michael _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
