Hi Jimmy,
Thanks for your reply, what I meant is l-interface needs to have a parent (all the options for the parent you listed below) and thus cannot exist on its own. For my use-case a BVI is really an l-interface which doesn't have any of the below mentioned parents, it has PNF as its parent. However no such association is currently defined in the schema and so I was looking for suggestions to model a BVI in the AAI schema. Bests, Rashmi ________________________________ From: FORSYTH, JAMES <jf2...@att.com> Sent: September 15, 2017 8:36 AM To: Pujar, Rashmi; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] Mapping a Bridged-virtual-interface (BVI) to AAI schema Hi, Pujar, l-interfaces is not bound to p-interface, that is just one of the options it has for a parent. From the schema, those options are... * FROM generic-vnf (is composed of l-interface) * FROM lag-interface (is composed of l-interface) * FROM newvce (is composed of l-interface) * FROM p-interface (is composed of l-interface) * FROM vserver (is composed of l-interface) * FROM l-interface (is composed of l-interface) Thanks, jimmy From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pujar, Rashmi Sent: Wednesday, September 13, 2017 1:58 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] Mapping a Bridged-virtual-interface (BVI) to AAI schema Hello AAI experts, I want to use the AAI schema to hold a network resource: Bridged Virtual Interface (BVI). See link for more explanation: https://www.cisco.com/c/en/us/support/docs/lan-switching/integrated-routing-bridging-irb/200650-Understanding-Bridge-Virtual-Interface.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cisco.com_c_en_us_support_docs_lan-2Dswitching_integrated-2Drouting-2Dbridging-2Dirb_200650-2DUnderstanding-2DBridge-2DVirtual-2DInterface.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=kdYzvSNbhHhBF64v1QCbOdl1bQ3ul7_TejEYezFIXmg&s=bISmhN50csvF-voAdzAcqSfsFXDBkfhPzk8vHWlNPVU&e=> BVI is really a routed virtual L3 interface (has an IP address) that allows traffic to get out of an EVI (L2 VLAN) --> a virtual interface that is not tied to any physical interface. It fits into the "l-interfaces" object defined in the AAI schema. However, "l-interfaces" is always bound to a "p-interface" object. I would like to understand why the "l-interfaces" was not exposed as an independent entity. Any ideas on how to retrofit a BVI interface in the schema would be very helpful. Thanks, Rashmi
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
