[WIP] Project and Server Policy

In this article:

Policy Brief

---

Our [NAME] Policy refers to Agate’s value [if any related]. With this policy, Agate ensure that [Purpose of policy]

Paragraph summarizing policy for quick info to the reader if they are reading the right doc

Scope

---

What/Who/When/etc is affected by this policy

Policy Elements

---

[belum makes sense elementsnya, gimana terbaginya, categorizenya]

[ini seperti sop ya]

Prerequisite

Crew (Lead?) are required to give DevOps the project detail to prevent customization project and scalability for DevOps support service [who responsible to create plan?]

• Can be provided used discus and create Devops Support Group
• Bikin Dashboard dan butuh di hitung dari dashboard tersebut untuk estimasi cost server

Budgeting

DevOps will provide [Crew] with [server?] capacity planning. DevOps will also split the server into two environment—Development and Production.

• Development environment will be started [initiated? created? configured?] before project start development [who responsible? i think devops]
• Production: Do some stresstest in staging / sandbox [unclear meaning] [who responsible?]

Quest/Project Plan

Quest that request must have plan/target for

• Start development, raise to go production [the when i think] [who responsible?]
• End development and end of production [when jg] [who responsible?]
• Devops support [service used?] [who responsible?]
• Budget for development and production on server side [who responsible?]

Adding new services

• Need notify devops PIC for adding new service for updating total budget of capacity planning [who responsible?]
• Need detail for what kind service to make sure for data traffic is not wasting current infra, specially for redis and database [who responsible?]
• Bikin tambahan opsi ketika staging butuh up 24 jam [unclear, apakah ini todo devops?]
• Butuh Flow Approval [backlog] [unclear, apakah ini todo devops?]
  • ticketing

Infrastructure decides

• Devops will give detail plan for server and give best practice and alternative for infra, need approval from PM and Lead
• Infra side decides: Need information of development / production server will be on agate or client side [who responsible?]
• Switching infrastructure cost detail [who responsible?]

Related Pages

---

SOP nya di sini nanti bikin lagi page

Maintainability Server SOP :

• Prepare doc for project
  • Before
    • Capacity Planning
    • Target budget for server
  • Progress
    • Listup all server and services
    • Fill Incident Report
  • End
    • Termination / Pause Infra Plan
• Every PIC for that Quest must be fill the quest dashboard
  • Who the PM, Producer, Lead Programmer
  • Mark due of the project ended for development and production progress based on prerequisite
  • Repo
• Invite each PIC to the current dashboard and give access “can comment” (for some page can be edited)