Category:CHGs - Revision history

Maltfield at 13:01, 23 April 2020

2020-04-23T13:01:56Z

← Older revision		Revision as of 13:01, 23 April 2020
Line 8:		Line 8:
	# How long the change is expected to take		# How long the change is expected to take
	# What systems will be impacted by the change		# What systems will be impacted by the change
			# When this CHG has been tested in staging
	# How to prove the system is in the pre-change state		# How to prove the system is in the pre-change state
	# What exact commands will be run to change the system		# What exact commands will be run to change the system

Maltfield at 12:47, 23 April 2020

2020-04-23T12:47:00Z

← Older revision		Revision as of 12:47, 23 April 2020
Line 4:		Line 4:

	# The exact date and time (including timezone, ideally UTC) for when the CHG is scheduled		# The exact date and time (including timezone, ideally UTC) for when the CHG is scheduled
			# The names and contact info of all the potentially affected system owners
	# Why the change is needed		# Why the change is needed
	# How long the change is expected to take		# How long the change is expected to take

Maltfield at 12:44, 23 April 2020

2020-04-23T12:44:53Z

← Older revision		Revision as of 12:44, 23 April 2020
Line 1:		Line 1:
	What is ~~CHG? Chlorhexidine gluconate?~~		As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track production changes

			CHG stands for CHanGe. It's a process used to prepare for a CHANGE in production system. A CHG ticket should clearly state:

			# The exact date and time (including timezone, ideally UTC) for when the CHG is scheduled
			# Why the change is needed
			# How long the change is expected to take
			# What systems will be impacted by the change
			# How to prove the system is in the pre-change state
			# What exact commands will be run to change the system
			# How to prove that the system is in the post-change state
			# How to validate that the change was successful
			# If the change was unsuccessful, list the exact commands to be run to revert to the pre-change state

	~~As of 2018-07, we have no ticket tracking or change control process. For now, everything~~ is ~~on the wiki as there's higher priorities~~. ~~Hence, here's some articles used to track production changes~~		All stakeholders should be notified and approve the CHG well before the CHG is scheduled to take place.

Marcin at 16:10, 16 February 2019

2019-02-16T16:10:58Z

← Older revision		Revision as of 16:10, 16 February 2019
Line 1:		Line 1:
			What is CHG? Chlorhexidine gluconate?

	As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track production changes		As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track production changes

Maltfield: Created page with "As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track..."

2018-07-11T16:47:18Z

Created page with "As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track..."

New page

As of 2018-07, we have no ticket tracking or change control process. For now, everything is on the wiki as there's higher priorities. Hence, here's some articles used to track production changes