Dl/devops - Revision history

Stonezhong at 18:06, 23 March 2023

2023-03-23T18:06:01Z

← Older revision		Revision as of 18:06, 23 March 2023
Line 1:		Line 1:
			<p> [[dl/home\|Data Lake Knowledge Center]] </p>

	= Purpose =		= Purpose =
	<div class="toccolours mw-collapsible mw-collapsed expandable">		<div class="toccolours mw-collapsible mw-collapsed expandable">

2023-03-23T18:03:44Z

Best Practices

← Older revision		Revision as of 18:03, 23 March 2023
Line 17:		Line 17:
	* Create a standard for solving the same type of problems, thus reduce human mistakes.		* Create a standard for solving the same type of problems, thus reduce human mistakes.
	* Prevent people from wasting time, since they just need to follow runbooks or SOPs.		* Prevent people from wasting time, since they just need to follow runbooks or SOPs.
	* Help the team to predict the workload the time for solving devop issues based on runbooks or SOPs.		* Help the team to predict the workload and the time for solving devop issues based on runbooks or SOPs.
	</div>		</div>
	</div>		</div>

2023-03-23T18:02:09Z

Purpose

← Older revision		Revision as of 18:02, 23 March 2023
Line 3:		Line 3:
	<div class="mw-collapsible-preview"></div>		<div class="mw-collapsible-preview"></div>
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	* Fix problems promptly to make sure the team ~~deliver~~ what it promised with high quality.		* Fix problems promptly to make sure the team delivers what it promised with high quality.
	</div>		</div>
	</div>		</div>

2023-03-23T17:41:08Z

Best Practices

← Older revision		Revision as of 17:41, 23 March 2023
Line 26:		Line 26:
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	Many times, operational failure reveals weakness about the underlying product. In such cases, you should also think about fixing the underlying product, improve robustness so it is more resistance to operational failure.		Many times, operational failure reveals weakness about the underlying product. In such cases, you should also think about fixing the underlying product, improve robustness so it is more resistance to operational failure.
			</div>
			</div>
			<p></p>

			<div class="toccolours mw-collapsible mw-collapsed expandable">
			<div class="mw-collapsible-preview">Make sure any failures are reported</div>
			<div class="mw-collapsible-content">
			For example, any data pipeline failure, which require human to restart the pipeline should have a ticket cut. Having a failure without the team being notified should be absolutely avoided.
	</div>		</div>
	</div>		</div>
	<p></p>		<p></p>

2023-03-23T17:39:15Z

Best Practices

← Older revision		Revision as of 17:39, 23 March 2023
Line 18:		Line 18:
	* Prevent people from wasting time, since they just need to follow runbooks or SOPs.		* Prevent people from wasting time, since they just need to follow runbooks or SOPs.
	* Help the team to predict the workload the time for solving devop issues based on runbooks or SOPs.		* Help the team to predict the workload the time for solving devop issues based on runbooks or SOPs.
			</div>
			</div>
			<p></p>

			<div class="toccolours mw-collapsible mw-collapsed expandable">
			<div class="mw-collapsible-preview">Always tries to fix the root cause</div>
			<div class="mw-collapsible-content">
			Many times, operational failure reveals weakness about the underlying product. In such cases, you should also think about fixing the underlying product, improve robustness so it is more resistance to operational failure.
	</div>		</div>
	</div>		</div>
	<p></p>		<p></p>

2023-03-23T17:36:05Z

Best Practices

← Older revision		Revision as of 17:36, 23 March 2023
Line 14:		Line 14:
	For any typical devop task, make sure you have runbooks or SOPs well documented. This helps:		For any typical devop task, make sure you have runbooks or SOPs well documented. This helps:

	* ~~new~~ team member to ramp up quickly		* New team member to ramp up quickly
	* ~~create~~ a standard for solving the same type of problems, thus reduce human mistakes.		* Create a standard for solving the same type of problems, thus reduce human mistakes.
	* ~~prevent~~ people from wasting time, since they just need to follow runbooks or SOPs.		* Prevent people from wasting time, since they just need to follow runbooks or SOPs.
	* ~~help~~ the team to predict the workload the time for solving devop issues based on runbooks or SOPs.		* Help the team to predict the workload the time for solving devop issues based on runbooks or SOPs.
	</div>		</div>
	</div>		</div>
	<p></p>		<p></p>

2023-03-23T17:35:49Z

Best Practices

← Older revision		Revision as of 17:35, 23 March 2023
Line 16:		Line 16:
	* new team member to ramp up quickly		* new team member to ramp up quickly
	* create a standard for solving the same type of problems, thus reduce human mistakes.		* create a standard for solving the same type of problems, thus reduce human mistakes.
			* prevent people from wasting time, since they just need to follow runbooks or SOPs.
			* help the team to predict the workload the time for solving devop issues based on runbooks or SOPs.
	</div>		</div>
	</div>		</div>
	<p></p>		<p></p>

2023-03-23T17:33:46Z

Best Practices

← Older revision		Revision as of 17:33, 23 March 2023
Line 9:		Line 9:

	= Best Practices =		= Best Practices =
			<div class="toccolours mw-collapsible mw-collapsed expandable">
			<div class="mw-collapsible-preview">Always have runbook or SOP</div>
			<div class="mw-collapsible-content">
			For any typical devop task, make sure you have runbooks or SOPs well documented. This helps:

			* new team member to ramp up quickly
			* create a standard for solving the same type of problems, thus reduce human mistakes.
			</div>
			</div>
			<p></p>

2023-03-23T17:31:39Z

Purpose

2023-03-23T17:29:05Z

Purpose

← Older revision		Revision as of 17:29, 23 March 2023
Line 3:		Line 3:
	<div class="mw-collapsible-preview"></div>		<div class="mw-collapsible-preview"></div>
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
			* Fix problems promptly to make sure the team deliver what it promised with high quality.
	</div>		</div>
	</div>		</div>
	<p></p>		<p></p>