Opened 10 months ago

Last modified 13 days ago

#29398 new task

Create a template for requesting infrastructure resources

Reported by: ln5 Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Publish the template decided upon in the Brussels meeting and announce it internaly.

cf https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdminTeamMinutes#Helpusersimprovewhenrequestingresources

Child Tickets

Change History (2)

comment:2 Changed 13 days ago by Alan khan

The next step is to create a staging instance for the resource. In this
step the resource is fully added to Ansible/configuration management. The
resource is added to caching/load balancing/databases and tested in this
new env. Once initial deployment is done and tested, another email to the
infrastructure list is done to note that the resource is available in
staging.

The security officer should be informed as soon as the code is reasonably
stable, so that they can start the audit or delegate the audit to someone.

Requirements for continuing:


  • MUST have sign off of RFR sponsor that the resource is fully configured in Ansible and ready to be deployed.
  • MUST have a deployment schedule for going to production. This will need to account for things like freezes and availability of infrastructure folks.
  • MUST have an approved audit by the security officer or appointed delegate.

Production deployment
=====================

Finally the staging changes are merged over to production and the resource
is deployed.

Monitoring of the resource is added and confirmed to be effective.

Maintenance
===========

The resource will then follow the normal rules for production. Honoring
freezes, updating for issues or security bugs, adjusting for capacity,
etc.

Ticket comment template
=======================

You can copy/paste this template into your RFR ticket. Keep the values empty
until you know answers - you can go back later and edit the ticket to fill in
information as it develops.

Phase I

  • Software: <mynewservice>
  • Advantage for Fedora: <It will give us unicorns>
  • Sponsor: <someone>

Phase II

Phase III

Phase IV

.. _Application Security Policy: https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/security_policy.html

Note: See TracTickets for help on using tickets.