From 4fd2750e34d9054805d0b3d76e53b22b3cf2fd10 Mon Sep 17 00:00:00 2001 From: Patrick Uiterwijk Date: Oct 05 2017 20:55:28 +0000 Subject: Add templates for example comments on RFR tickets Signed-off-by: Patrick Uiterwijk --- diff --git a/docs/sysadmin-guide/sops/requestforresources.rst b/docs/sysadmin-guide/sops/requestforresources.rst index e09169d..c741ac0 100644 --- a/docs/sysadmin-guide/sops/requestforresources.rst +++ b/docs/sysadmin-guide/sops/requestforresources.rst @@ -65,6 +65,14 @@ Requirements for continuing: * MUST have the ticket assigned and accepted by someone in infrastructure sysadmin-main group. +Ticket comment template: +------------------------ + +Software: +Advantage for Fedora: +Sponsor: + + Planning ======== @@ -92,6 +100,16 @@ Requirements for continuing: * MUST determine who is involved in the deployment/maintaining the resource. +Ticket comment template: +------------------------ + +Email list thread: +Upstream source: +Development contacts: +Maintainership contacts: +Load balanceable: +Caching: + Development Instance ==================== @@ -125,6 +143,13 @@ Requirements for continuing: * MUST tag in the security officer in the ticket so an audit can be scheduled. +Ticket comment template: +------------------------ + +SOP link: +Audit request: (can be same) +Audit timeline: <04-11-2025 - 06-11-2025> + Staging Instance ================ @@ -150,6 +175,14 @@ Requirements for continuing: * MUST have an approved audit by the security officer or appointed delegate. +Ticket comment template: +------------------------ + +Ansible playbooks: +Fully rebuilt from ansible: +Production goal: <08-11-2025> +Approved audit: + Production deployment =====================