Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose to allocate uids from the maximum down #21

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Propose to allocate uids from the maximum down #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions documents/wip/userNaming.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,13 +159,13 @@ penetration of NFSv4 may not be sufficiently high to eliminate this need. In
an HA fail over environment the potential change in UID of the user on one
machine and another UID on the fail over machine may not be tolerated. It is
therefore proposed that the created system users for the cloud frameworks
be assigned consistent user IDs across distributions start with 99 and working
down, the order is not of material interest.
be assigned consistent user IDs across distributions start with 4294967293 and
working down, the order is not of material interest.

_oneadmin -> 60001 (system user for openNebula)
_openstack -> 60002
_cloudstack -> 60003
_eucalyptus -> 60004
_oneadmin -> 4294967293 (system user for openNebula)
_openstack -> 4294967292
_cloudstack -> 4294967291
_eucalyptus -> 4294967290

Using the proposed "_" prefix for the proposed IDs for the cloud frameworks.

Expand Down