Showing content from https://github.com/vmware-archive/vsphere-storage-for-docker/issues/1032 below:
Implement multi-node ESX support in tenancy/auth code · Issue #1032 · vmware-archive/vsphere-storage-for-docker · GitHub
Implement per the following assumption/desired behavior
Assumption: Cross-ESX multi-tenancy works on shared datastores only
Approach: Centralized backend DB on shared storage, with symlinks from local (/etc/vmware)
Behavior changes:
Milestone 1
- Admin needs to run "config init" on each ESX: vmdkops_admin config init --datastore=<DS_NAME>
- DS_NAME must be a shared datastore to support cross-ESX multi tenancy. If a local datastore is provided, everything still works fine except that multi tenancy is limited on one single ESX only.
- All ESX drivers will share the same auth configuration persisted in one single database.
- If "config init" is not done, then there’s no authorization - any requests from any Docker Hosts will be executed with no restriction. To keep the backward compatibility, all the volumes should still be created under the dockvols/_DEFAULT folder.
Milestone 2
- Admin can run “config init” on any ESX: vmdkops_admin config init --datastore=<DS_NAME>
- All other ESXs that have access to the same shared datastore will discover the configuration automatically
- Admin can run "config rm" to switch to a different shared datastore (instead of doing "config rm" followed by a "config init")
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4