OSM Multi-tenancy: Difference between revisions
From OSM Public Wiki
(Created page with "new content coming soon") |
m (initial skeleton) |
||
| Line 1: | Line 1: | ||
new | This is an experimental feature which allows to use a single instance of OSM for a set of different projects and users. Full support will be available in Release FOUR. | ||
The required steps are: | |||
* Enable PAM authentication at SO, to support multiple users. | |||
* Create the required users and projects in SO, assigning the required privileges. | |||
* Map each SO project with a new RO tenant, with its corresponding VIMs. | |||
* [Optional] Create a separate Juju controller for each SO project. | |||
==Enabling PAM authentication== | |||
==Managing SO Projects== | |||
==Managing RO Tenants== | |||
==Working with multiple Juju controllers== | |||
[work in progress] | |||
Revision as of 18:16, 26 January 2018
This is an experimental feature which allows to use a single instance of OSM for a set of different projects and users. Full support will be available in Release FOUR.
The required steps are:
- Enable PAM authentication at SO, to support multiple users.
- Create the required users and projects in SO, assigning the required privileges.
- Map each SO project with a new RO tenant, with its corresponding VIMs.
- [Optional] Create a separate Juju controller for each SO project.
Enabling PAM authentication
Managing SO Projects
Managing RO Tenants
Working with multiple Juju controllers
[work in progress]