1 # Project/tenant support in the platform #
4 - Gerardo Garcia (Telefonica)
5 - Alfonso Tierno (Telefonica)
6 - Francisco Javier Ramon (Telefonica)
15 The NFV Orchestrator should be allowed to access all the datacenters and
16 services in a carrier network. However, from the perspective of the real
17 operation, it is often desirable to allow the partitioning of the telco cloud
18 space in different projects/tenants, following an equivalent approach to the
21 Thus, it would be desirable that an OSM project/tenant provided a separate
23 - A given set of accessible VNFs
24 - A given set of accessible NSs
26 - Optionally, a number of authorized datacenters (if more than one).
28 VNF descriptors and NS descriptors might be declared public (available for all
29 tenants) or available for a list of tenants. An NS instance will only run in
32 Users should belong at least to one tenant. By default, admin users should be
33 authorized in all tenants.
35 ## Demo or definition of done ##
36 - Create a 2 tenants (A and B) and add some users to them (user_a1, user_a2,
37 and user_b1). Assign different datacenters to them.
38 - Check that user_a1 can onboard a VNF and a NS in the tenant A successfully.
39 Check that it is not visible or accessible by user_b1.
40 - Check same operation as above but by user_b1 in tenant B.
41 - Check that user_a1 can deploy successfully its NS in the tenant A. Check that
42 the NS is not visible or accessible by user_b1.
43 - Check that user_a2 can access to the same VNFDs, NSDs, and the running NS
44 available it tenant A.
45 - Onboard an additional VNFD and a new NSD that uses the VNF and make them
46 public (e.g. from an admin user).
47 - Check that the public NSD and VNFD are accessible from both tenants and that
48 the NS can be successfully instantiated from any of them.
49 - Check that each tenant is deploying their NS instances in their corresponding