Grid Configuration - Revision history

Qadmin: Add Modify Grid Network Settings and Modify Grid Time Zone Settings sections (QSTOR-12352)

2026-09-04T04:30:52Z

Add Modify Grid Network Settings and Modify Grid Time Zone Settings sections (QSTOR-12352)

Qadmin: /* Changing the Grid Master */

2026-09-03T23:33:55Z

Changing the Grid Master

← Older revision		Revision as of 23:33, 3 September 2026
Line 112:		Line 112:
	So the ordinary reason to reach for Force is the one that matters most: '''the current master is unreachable and you need to promote a surviving member to get grid management back.''' It is not a retry switch for an election that failed for some other reason.		So the ordinary reason to reach for Force is the one that matters most: '''the current master is unreachable and you need to promote a surviving member to get grid management back.''' It is not a retry switch for an election that failed for some other reason.

	Because a forced promotion skips coordination with the existing master, only use it when you are confident the old master is genuinely down. Forcing a promotion while the old master is still running and merely unreachable from this member leaves two systems believing they coordinate the grid.		Because a forced promotion skips coordination with the existing master, only use it when you are confident the old master is genuinely down. Forcing a promotion while the old master is still running and merely unreachable from this member leaves two systems believing they coordinate the grid and will take a minute or two for the nodes to sort.

	== Removing a System ==		== Removing a System ==

Qadmin at 23:31, 3 September 2026

2026-09-03T23:31:15Z

← Older revision		Revision as of 23:31, 3 September 2026
Line 50:		Line 50:
	You do not need to connect to the grid master to manage the grid -- any member gives you the whole grid. Management operations may feel more responsive when run against the master, because operations that need coordination do not have to be relayed.		You do not need to connect to the grid master to manage the grid -- any member gives you the whole grid. Management operations may feel more responsive when run against the master, because operations that need coordination do not have to be relayed.

	~~'''~~If the grid master is lost, storage keeps serving but grid management degrades~~'''~~ unless you have a Grid VIF configured which will automatically elect another node as the new grid master. Pools stay online and clients keep their connections, because the master is not in the data path. Management operations that require coordination will fail until a new master is elected -- see '''[[#Changing the Grid Master\|Changing the Grid Master]]'''.		If the grid master is lost, storage keeps serving but grid management degrades unless you have a Grid VIF configured which will automatically elect another node as the new grid master. Pools stay online and clients keep their connections, because the master is not in the data path. Management operations that require coordination will fail until a new master is elected -- see '''[[#Changing the Grid Master\|Changing the Grid Master]]'''.

	== Creating a Grid ==		== Creating a Grid ==

Qadmin: /* The Grid Master */

2026-09-03T23:30:45Z

The Grid Master

← Older revision		Revision as of 23:30, 3 September 2026
Line 50:		Line 50:
	You do not need to connect to the grid master to manage the grid -- any member gives you the whole grid. Management operations may feel more responsive when run against the master, because operations that need coordination do not have to be relayed.		You do not need to connect to the grid master to manage the grid -- any member gives you the whole grid. Management operations may feel more responsive when run against the master, because operations that need coordination do not have to be relayed.

	'''If the grid master is lost, storage keeps serving but grid management degrades.''' Pools stay online and clients keep their connections, because the master is not in the data path. Management operations that require coordination will fail until a new master is elected -- see '''[[#Changing the Grid Master\|Changing the Grid Master]]'''.		'''If the grid master is lost, storage keeps serving but grid management degrades''' unless you have a Grid VIF configured which will automatically elect another node as the new grid master. Pools stay online and clients keep their connections, because the master is not in the data path. Management operations that require coordination will fail until a new master is elected -- see '''[[#Changing the Grid Master\|Changing the Grid Master]]'''.

	== Creating a Grid ==		== Creating a Grid ==

Qadmin: Document what the Force option actually does: on Set Grid Master it promotes a member directly when the coordinated election cannot complete (the unreachable-master recovery case), and on Add System it overrides the already-in-a-grid guard and turns the join into a full grid merge (QSTOR-12352)

2026-09-03T04:13:32Z

Document what the Force option actually does: on Set Grid Master it promotes a member directly when the coordinated election cannot complete (the unreachable-master recovery case), and on Add System it overrides the already-in-a-grid guard and turns the join into a full grid merge (QSTOR-12352)

← Older revision		Revision as of 04:13, 3 September 2026
Line 71:		Line 71:
	* '''Admin Username''' / '''Admin Password''' -- credentials on the '''system being added''', not on the grid you are adding it to. QuantaStor authenticates against the remote system to establish the join, so these are its own local administrator credentials.		* '''Admin Username''' / '''Admin Password''' -- credentials on the '''system being added''', not on the grid you are adding it to. QuantaStor authenticates against the remote system to establish the join, so these are its own local administrator credentials.

	Run this from a member of the grid you want to grow. The system being added must not already belong to another grid.		Run this from a member of the grid you want to grow.

			'''The system being added must not already belong to another grid.''' If it does, the join is refused with "This node is already a member of grid '<name>', cannot join grid '<name>'".

			'''Forcing a join of an already-gridded system merges the two grids.''' The force flag overrides that guard, and the operation then becomes a merge -- every system in the other grid is brought in, not just the one you named. That is a much larger change than adding one appliance, and it is the same operation as [[#Managing a Grid from the CLI\|<code>qs grid-merge</code>]]. If a merge is what you want, use <code>grid-merge</code>, where the intent is explicit.

	=== What merges when a system joins ===		=== What merges when a system joins ===
Line 100:		Line 104:

	* '''Storage System''' -- the member to elect as the primary coordinator for synchronizing grid configuration state.		* '''Storage System''' -- the member to elect as the primary coordinator for synchronizing grid configuration state.
	* '''Force''' -- ~~carries~~ the ~~force flag through to~~ the ~~operation. Use it when a~~ normal election ~~will not proceed~~.		* '''Force''' -- promotes the selected member even when the normal election cannot complete.

	Use this to move the coordinator role deliberately -- before taking the current master down for maintenance, for instance -- and to recover grid management after a master is lost.		Use this to move the coordinator role deliberately -- before taking the current master down for maintenance, for instance -- and to recover grid management after a master is lost.

			'''When Force is needed.''' A normal election coordinates with the existing master and, in a grid with a grid-management virtual interface, moves that interface to the new master. If that step fails -- which is what happens when the member cannot reach the current master -- the operation is refused and nothing changes. Selecting '''Force''' makes QuantaStor promote the member directly instead, without that coordination.

			So the ordinary reason to reach for Force is the one that matters most: '''the current master is unreachable and you need to promote a surviving member to get grid management back.''' It is not a retry switch for an election that failed for some other reason.

			Because a forced promotion skips coordination with the existing master, only use it when you are confident the old master is genuinely down. Forcing a promotion while the old master is still running and merely unreachable from this member leaves two systems believing they coordinate the grid.

	== Removing a System ==		== Removing a System ==

Qadmin: Rewrite from the product: document all six Storage System Grid operations with new screenshots, correct the false claim that duplicate user accounts resolve by grid-master precedence (only admin does; User/UserGroup/Role merge keep-superset so both survive), explain the four names for the grid master role, document that Force is required to remove a Ceph cluster member, add the 12 grid CLI commands including grid-merge/grid-split, and drop the QuantaStor 5 video (QSTOR-12352)

2026-09-03T04:11:54Z

Rewrite from the product: document all six Storage System Grid operations with new screenshots, correct the false claim that duplicate user accounts resolve by grid-master precedence (only admin does; User/UserGroup/Role merge keep-superset so both survive), explain the four names for the grid master role, document that Force is required to remove a Ceph cluster member, add the 12 grid CLI commands including grid-merge/grid-split, and drop the QuantaStor 5 video (QSTOR-12352)

Show changes

Qadmin at 19:25, 26 October 2020

2020-10-26T19:25:07Z

← Older revision		Revision as of 19:25, 26 October 2020
Line 5:		Line 5:

	''' OSNEXUS Videos '''		''' OSNEXUS Videos '''
	* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup. ~~(17~~:~~44)~~]		* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup. [10:58]]


	{{Template:GridSetupProceedure}}		{{Template:GridSetupProceedure}}

Qadmin at 19:56, 1 October 2020

2020-10-01T19:56:03Z

← Older revision		Revision as of 19:56, 1 October 2020
Line 5:		Line 5:

	''' OSNEXUS Videos '''		''' OSNEXUS Videos '''
	* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup.]		* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup. (17:44)]


	{{Template:GridSetupProceedure}}		{{Template:GridSetupProceedure}}

Qadmin: /* OSNEXUS Videos */

2020-10-01T19:40:36Z

OSNEXUS Videos

← Older revision		Revision as of 19:40, 1 October 2020
Line 4:		Line 4:


	= OSNEXUS Videos =		''' OSNEXUS Videos '''
	* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup.]		* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup.]


	{{Template:GridSetupProceedure}}		{{Template:GridSetupProceedure}}

Qadmin: /* OSNEXUS Videos */

2020-10-01T19:16:12Z

OSNEXUS Videos

← Older revision		Revision as of 19:16, 1 October 2020
Line 4:		Line 4:


	== OSNEXUS Videos ==		= OSNEXUS Videos =
	* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup.]		* [[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=MeX9rAmskvo]] [https://www.youtube.com/watch?v=VpfcjZDO3Ys Covers QuantaStor 5 Storage Grid Setup.]


	{{Template:GridSetupProceedure}}		{{Template:GridSetupProceedure}}