AppSuite:File Storages per User - Revision history

Choeger: /* When is a user filestore enabled or when did a user has a own filestore? */

2022-04-14T11:26:34Z

When is a user filestore enabled or when did a user has a own filestore?

← Older revision		Revision as of 11:26, 14 April 2022
Line 210:		Line 210:
	== FAQs ==		== FAQs ==

	=== When is a user filestore enabled or when ~~did~~ a user ~~has a~~ own filestore? ===		=== When is a user filestore enabled or when does a user have an own filestore? ===

	A user filestore has an own filestore if a filestore is assigned to this user. This can either be done via the create and update clt's or via the movecontextfilestore2user clt.		A user filestore has an own filestore if a filestore is assigned to this user. This can either be done via the create and update clt's or via the movecontextfilestore2user clt.

Thorben: /* What happens in over quota scenarios by deleting users? */

2016-11-03T08:42:24Z

What happens in over quota scenarios by deleting users?

← Older revision		Revision as of 08:42, 3 November 2016
Line 238:		Line 238:
	=== What happens in over quota scenarios by deleting users? ===		=== What happens in over quota scenarios by deleting users? ===

	If the data is assigned to a different user the quota limit is ignored.		If the data is assigned to a different user the quota limit is ignored. But the user (inheriting deleted user's files) is supposed to clean existing files as any attempt to create a Drive file will fail due to over-quota

	=== How to deal with quota issues for the context admin caused by public files? ===		=== How to deal with quota issues for the context admin caused by public files? ===

Thorben: /* Useful command‐line tools */

2016-11-03T08:40:57Z

Useful command‐line tools

← Older revision		Revision as of 08:40, 3 November 2016
Line 207:		Line 207:
	* 'listuser' to get the quota limit specified per user or -1 if none		* 'listuser' to get the quota limit specified per user or -1 if none
	* 'listuserfilestores' to get a listing of users that use their own user file storage		* 'listuserfilestores' to get a listing of users that use their own user file storage

			== FAQs ==

			=== When is a user filestore enabled or when did a user has a own filestore? ===

			A user filestore has an own filestore if a filestore is assigned to this user. This can either be done via the create and update clt's or via the movecontextfilestore2user clt.

			=== When is which quota affected? ===

			In case the user has no own filestore the quota of the context filestore is affected. In case the user has an own filestore or in case the user is a slave user of another users filestore the quota of this user filestore is affected.

			=== How can a user check his quota usage? ===

			The 'Quota' portal widget shows quota and usage.

			=== How to change the filestore quota shown in the portal widget? ===

			To change the quota one just has to use the changeuser or changecontext CLT with the --quota (-q) argument. E.g.:

			changecontext -A adminmaster -P masterpassword -c -q 1024

			=== How does quota work for public files? ===

			The quota of the folder creator/owner is in charge for files other users put inside. This affects the quota for users having an own filestore

			=== What happens with ownership of public files and folders when the creator/owner gets deleted? ===

			This depends which argument is used during the delete operation. In the default case, the context admin is assigned as the owner. But it is also possible that the data is assigned to a different user or that the data is completed removed.

			=== What happens in over quota scenarios by deleting users? ===

			If the data is assigned to a different user the quota limit is ignored.

			=== How to deal with quota issues for the context admin caused by public files? ===

			If the quota is too limited for the context admin the data should be completely removed or assigned to a different user. E.g.:
			deleteuser -A ctxadmin -P password -c -i --no-reassign

Thorben: /* Useful command‐line tools */

2016-11-03T08:36:41Z

Useful command‐line tools

← Older revision		Revision as of 08:36, 3 November 2016
Line 203:		Line 203:
	The following command‐line tools might be useful to get an overview		The following command‐line tools might be useful to get an overview

	* listfilestore to list available file storages that can be assigned to contexts/users		* 'listfilestore' to list available file storages that can be assigned to contexts/users
	* listcontext to get the quota limit specified per context or -1 if none		* 'listcontext' to get the quota limit specified per context or -1 if none
	* listuser to get the quota limit specified per user or -1 if none		* 'listuser' to get the quota limit specified per user or -1 if none
	* listuserfilestores to get a listing of users that use their own user file storage		* 'listuserfilestores' to get a listing of users that use their own user file storage

Thorben: /* Extensions to provisioning command‐line tools */

2016-11-03T08:36:11Z

Extensions to provisioning command‐line tools

← Older revision		Revision as of 08:36, 3 November 2016
Line 190:		Line 190:
	Entries marked with an question mark (?) are mandatory depending on your configuration.		Entries marked with an question mark (?) are mandatory depending on your configuration.
	Entries marked with a pipe (\|) are mandatory for one another, which means that at least one of them, must be set.		Entries marked with a pipe (\|) are mandatory for one another, which means that at least one of them, must be set.

			=== Creating a user file storage ===

			Having the extensions to command-line tools a user-associated file storage can be enabled:

			* After using 'movecontextfilestore2user' command-line tool
			* Using 'changeuser' command-line tool with quota and filestore options or only quota options and "ALLOW_CHANGING_QUOTA_IF_NO_FILESTORE_SET" set to "true" in 'AdminUser.properties' file
			* By provisioning via 'createuser' command-line tool with quota and filestore options

	== Useful command‐line tools ==		== Useful command‐line tools ==

Thorben: /* Extensions to provisioning command‐line tools */

2016-11-03T08:31:51Z

Extensions to provisioning command‐line tools

← Older revision		Revision as of 08:31, 3 November 2016
Line 190:		Line 190:
	Entries marked with an question mark (?) are mandatory depending on your configuration.		Entries marked with an question mark (?) are mandatory depending on your configuration.
	Entries marked with a pipe (\|) are mandatory for one another, which means that at least one of them, must be set.		Entries marked with a pipe (\|) are mandatory for one another, which means that at least one of them, must be set.

			== Useful command‐line tools ==

			The following command‐line tools might be useful to get an overview

			* listfilestore to list available file storages that can be assigned to contexts/users
			* listcontext to get the quota limit specified per context or -1 if none
			* listuser to get the quota limit specified per user or -1 if none
			* listuserfilestores to get a listing of users that use their own user file storage

Thorben: /* changeuser */

2016-11-03T08:26:08Z

changeuser

← Older revision		Revision as of 08:26, 3 November 2016
Line 105:		Line 105:
	The existing changeuser CLI is enhanced by the following option		The existing changeuser CLI is enhanced by the following option
	‐q/‐‐quota The file storage quota in MB for associated user		‐q/‐‐quota The file storage quota in MB for associated user

			'''Note:''' Option ALLOW_CHANGING_QUOTA_IF_NO_FILESTORE_SET in file 'AdminUser.properties' controls if a user file storage is automatically enabled if the ‐q/‐‐quota option is given on a 'changeuser' invocation as an alternative to 'movecontextfilestore2user'. For users without a user file storage the 'changeuser' CLT needs to be called with a quota value different to unlimited (-1) and unlimited quota will only be enabled in case the user already has a user file storage.

	=== movecontextfilestore2user ===		=== movecontextfilestore2user ===

Thorben: /* Motivation */

2016-11-03T08:17:34Z

Motivation

← Older revision		Revision as of 08:17, 3 November 2016
Line 29:		Line 29:

	* All Drive files reside in the file storage associated with the context, which is either automatically determined or explicitly set (through -F,--destination-store-id option) when creating a context. All Drive files (from users of that context) and all other file resources (Snippets, PIM attachments, ...) share the same quota usage and limit settings. The file storage associated with the context is called '''context file storage'''.		* All Drive files reside in the file storage associated with the context, which is either automatically determined or explicitly set (through -F,--destination-store-id option) when creating a context. All Drive files (from users of that context) and all other file resources (Snippets, PIM attachments, ...) share the same quota usage and limit settings. The file storage associated with the context is called '''context file storage'''.
	* Certain users are supposed to store their Drive files in their own file storage with individual quota settings different from the context file storage. All files created in Drive folders owned by such a user are then accounted to that user-associated file storage having their own quota usage and limitation. The user-associated file storage may be set on user creation as it is for context creation. The file storage associated with a user is called '''user file storage'''.		* Certain users are supposed to store their Drive files in their own file storage with individual quota settings different from the context file storage. All files created in Drive folders owned by such a user are then accounted to that user-associated file storage having their own quota usage and limitation. The user-associated file storage may be set on user creation as it is for context creation. The file storage associated with a user is called '''user file storage'''. Introducing a user file storage is suitable when an administrator wants to have user-sensitive quota settings for Drive files and/or wants to assign a different type of storage for Drive files uploaded by users; e.g. let seldom used/accessed file resources reside in context file storage, but let frequently, highly accessed Drive files reside in a better storage sink
	* A certain user has his own (bigger) file storage for Drive files and other users of that context are supposed to use that file storage to share the quota usage and limitation specified for that file storage. A file storage owned by a user that is also used by other users is called '''master file storage'''.		* A certain user has his own (bigger) file storage for Drive files and other users of that context are supposed to use that file storage to share the quota usage and limitation specified for that file storage. A file storage owned by a user that is also used by other users is called '''master file storage'''.

Thorben: /* Motivation */

2016-11-03T08:11:57Z

Motivation

← Older revision		Revision as of 08:11, 3 November 2016
Line 28:		Line 28:
	That kind of separation allows different provisioning scenarios that an administrator possibly wants to achieve. With regard to Drive files it is now possible to define per context that:		That kind of separation allows different provisioning scenarios that an administrator possibly wants to achieve. With regard to Drive files it is now possible to define per context that:

	* All Drive files reside in the file storage associated with the context, which is either automatically determined or explicitly set (through -F,--destination-store-id option) when creating a context. The file storage associated with the context is called context file storage.		* All Drive files reside in the file storage associated with the context, which is either automatically determined or explicitly set (through -F,--destination-store-id option) when creating a context. All Drive files (from users of that context) and all other file resources (Snippets, PIM attachments, ...) share the same quota usage and limit settings. The file storage associated with the context is called '''context file storage'''.
	* Certain users are supposed to store their Drive files in their own file storage with individual quota settings different from the context file storage. All files created in Drive folders owned by such a user are then accounted to that user-associated file storage having their own quota usage and limitation. The user-associated file storage may be set on user creation as it is for context creation. The file storage associated with a user is called user file storage.		* Certain users are supposed to store their Drive files in their own file storage with individual quota settings different from the context file storage. All files created in Drive folders owned by such a user are then accounted to that user-associated file storage having their own quota usage and limitation. The user-associated file storage may be set on user creation as it is for context creation. The file storage associated with a user is called '''user file storage'''.
	* A certain user has his own (bigger) file storage for Drive files and other users of that context are supposed to use that file storage to share the quota usage and limitation specified for that file storage. A file storage owned by a user that is also used by other users is called master file storage.		* A certain user has his own (bigger) file storage for Drive files and other users of that context are supposed to use that file storage to share the quota usage and limitation specified for that file storage. A file storage owned by a user that is also used by other users is called '''master file storage'''.

	Having that possibilities of separation for quota usage and limitation it is possible to apply a certain use case scenario to contexts; e.g.		Having that possibilities of separation for quota usage and limitation it is possible to apply a certain use case scenario to contexts; e.g.

Thorben: /* Motivation */

2016-11-03T08:09:50Z

Motivation

← Older revision		Revision as of 08:09, 3 November 2016
Line 26:		Line 26:
	[[Image:file_storage_picture2.png\|Differentiate\|650px]]		[[Image:file_storage_picture2.png\|Differentiate\|650px]]

	That kind of separation allows different provisioning scenarios that an administrator possibly wants to achieve.		That kind of separation allows different provisioning scenarios that an administrator possibly wants to achieve. With regard to Drive files it is now possible to define per context that:

			* All Drive files reside in the file storage associated with the context, which is either automatically determined or explicitly set (through -F,--destination-store-id option) when creating a context. The file storage associated with the context is called context file storage.
			* Certain users are supposed to store their Drive files in their own file storage with individual quota settings different from the context file storage. All files created in Drive folders owned by such a user are then accounted to that user-associated file storage having their own quota usage and limitation. The user-associated file storage may be set on user creation as it is for context creation. The file storage associated with a user is called user file storage.
			* A certain user has his own (bigger) file storage for Drive files and other users of that context are supposed to use that file storage to share the quota usage and limitation specified for that file storage. A file storage owned by a user that is also used by other users is called master file storage.

			Having that possibilities of separation for quota usage and limitation it is possible to apply a certain use case scenario to contexts; e.g.

	* Slow mass storage vs. fast Drive storage setup		* Slow mass storage vs. fast Drive storage setup