Onap supports multi tenant deployment as well as multisite. That is the onap franework can be installed in one tenant or site while the vnfs are deployed on another. We also have the ability to have regions and/or tenants for vnf deployement. This is defined by something call lcp in mso and there is a clouds.yaml that holds all these combinations. The heat template we put out for the demo does not however have the full capabilities exposed as its meant to be a simple tutorial
On May 29, 2017, at 2:19 PM, Viswa KSP <kspviswa.git...@gmail.com<mailto:kspviswa.git...@gmail.com>> wrote: Hello, I would like to know if ONAP supports multi-tenant deployment model. If yes, please point me to configuration guide accordingly. More details: If you look at other ETSI compliant NFV-Os like OSM, OpenBaton, there is a specific configuration step, where-in we will have to specify a VIM account with tenant name, keystone URL. mgmt IP etc. This space will be used by the orchestra tor during deployment. While instantiating a NSD, we can dynamically at run-time specify which VIM account to use. While I understand that ONAP currently not multi-vim complaint ( only supported with Openstack ), I would like to know if multi-tenant model is supported. Assume I have 2 tenant spaces ( in 2 different openstack sites - to complicate the problem statement further ) and I would like to instantiate service 1 in tenant 1 and service 2 in tenant 2, how should I go about in realising this requirement? BR, Viswa _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=8aOVDebX_cac4i_WaD2VI1ZaKYZWTLkLffNt5I5HUgo&s=MSoC0S256pAGmVajoRWmhow6Wr-4B4vNBOr0W_ffXgE&e=
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
