From 41e1be93ac3b96dfa274c7932a0e81ea93565a03 Mon Sep 17 00:00:00 2001 From: Stephen Smoogen Date: Jul 06 2018 21:41:04 +0000 Subject: create base templates for each task.. need to get them filled out now --- diff --git a/docs/sysadmin-guide/sles/3rdparty/askfedora.rst b/docs/sysadmin-guide/sles/3rdparty/askfedora.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/askfedora.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/bugzilla.rst b/docs/sysadmin-guide/sles/3rdparty/bugzilla.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/bugzilla.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/centos-ci.rst b/docs/sysadmin-guide/sles/3rdparty/centos-ci.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/centos-ci.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/copr.rst b/docs/sysadmin-guide/sles/3rdparty/copr.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/copr.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/freenode.rst b/docs/sysadmin-guide/sles/3rdparty/freenode.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/freenode.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/openqa.rst b/docs/sysadmin-guide/sles/3rdparty/openqa.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/openqa.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/retrace.rst b/docs/sysadmin-guide/sles/3rdparty/retrace.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/retrace.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/status.rst b/docs/sysadmin-guide/sles/3rdparty/status.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/status.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/3rdparty/taskotron.rst b/docs/sysadmin-guide/sles/3rdparty/taskotron.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/3rdparty/taskotron.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/SLE-DNS.rst b/docs/sysadmin-guide/sles/SLE-DNS.rst deleted file mode 100644 index 4761528..0000000 --- a/docs/sysadmin-guide/sles/SLE-DNS.rst +++ /dev/null @@ -1,124 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-03-08 | -+---------------+----------------------------------------+ -| Last Updated | 2018-03-08 | -+---------------+----------------------------------------+ -| Service | DNS | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Stephen Smoogen | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, All Fedora Users | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the DNS servers that the Fedora Project -provides as master domains for the various 'Fedora' owned domains. - - -Description of the Service: -=========================== -The DNS nameservers are BIND named servers which provide data to the -Internet for all official FedoraProject domains (fedoraproject.org, -fedorapeople.org, fedoraplanet.org, etc). This allows for computers -connected to the Internet to be able to locate the IP addresses for -services attached to that. - -https://en.wikipedia.org/wiki/Domain_Name_System - -Location of the Service: -======================== -The Fedoraproject nameservers are split around the world at different -datacenters. The main servers are at PHX2 with some servers in Europe, -RDU2, and elsewhere. - -Service functionality: -====================== -The service allows for systems connected to the internet to do ip and -name lookups of systems controlled by the Fedora Project. It is -required to be working for most network related services to work. - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: Collectd -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html - - -Cost: -===== -Several virtual systems run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - -Other virtual systems run on servers provided by various ISPs. Network -costs are covered by them. - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-FAS.rst b/docs/sysadmin-guide/sles/SLE-FAS.rst deleted file mode 100644 index 84b0ac4..0000000 --- a/docs/sysadmin-guide/sles/SLE-FAS.rst +++ /dev/null @@ -1,129 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-03-08 | -+---------------+----------------------------------------+ -| Last Updated | 2018-03-08 | -+---------------+----------------------------------------+ -| Service | Fedora Account System | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Patrick Uiterwijk | -| | Secondary: Kevin Fenzi | -+---------------+----------------------------------------+ -| Customer | Infrastructure, All Fedora Account | -| | Users | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the Fedora Account System (FAS) which is -an application written by Fedora Infrastructure for authentication, -and authorization of users, groups and services within the Fedora -Project infrastructure. - - -Description of the Service: -=========================== - -The Fedora Account System was written to cover the account needs of -the Fedora Project. It ties into every part of the Fedora Project -ranging from who can commit to packages, who can build packages, who -can log into servers and what rules bots and services may have in -interacting with users. The system was originally written as a web -application which used SSL certificates and custom passwd databases on -each client. It is now backed in part by another service of kerberos -and IPSILON. - -Location of the Service: -======================== -The main FAS servers are in the PHX2 colocation. All client systems -will update their logins by querying the servers and the FAS servers -will then talk to a backing postgres database. - -Service functionality: -====================== -This service allows for users to log into systems and operate nearly -all Fedora services. - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -This system should only allow logins by people in restricted sysadmin -groups. These groups will be regularly audited and admins removed as -needed. - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/fas-notes.rst -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/fas-openid.rst - - -Cost: -===== -The virtual systems run on Dell r630's that are houses in the PHX2 -colocation. Costs for this are covered by Red Hat. - -Development costs are covered by Fedora Infrastructure and volunteers. - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-Ipsilon.rst b/docs/sysadmin-guide/sles/SLE-Ipsilon.rst deleted file mode 100644 index 82385b4..0000000 --- a/docs/sysadmin-guide/sles/SLE-Ipsilon.rst +++ /dev/null @@ -1,117 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-03-08 | -+---------------+----------------------------------------+ -| Last Updated | 2018-03-08 | -+---------------+----------------------------------------+ -| Service | IPSILON | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Patrick Uiterwijk | -| | Secondary: Kevin Fenzi | -+---------------+----------------------------------------+ -| Customer | Infrastructure, | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the IPSILON service which backs up the -Fedora Account System. - - -Description of the Service: -=========================== -IPSILON is our central authentication service which authenticates -users against FAS. The service is important to 2factor authentication -needed by system administration to sudo. - -Location of the Service: -======================== -The IPSILON services are are the PHX2 colocation. Client systems -connect to it through a web interface which is balanced by haproxy. - -Service functionality: -====================== -The service is meant to authenticate users for web applications and -other systems. - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -This system should only allow logins by people in restricted sysadmin -groups. These groups will be regularly audited and admins removed as -needed. - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/ipsilon.html - -Cost: -===== -The services run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - -Development costs are covered by Fedora Infrastructure and volunteers. - -Glossary of Terms: -================== - -References: -=========== diff --git a/docs/sysadmin-guide/sles/SLE-ansible.rst b/docs/sysadmin-guide/sles/SLE-ansible.rst deleted file mode 100644 index cd8b8fb..0000000 --- a/docs/sysadmin-guide/sles/SLE-ansible.rst +++ /dev/null @@ -1,121 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-03-08 | -+---------------+----------------------------------------+ -| Last Updated | 2018-03-08 | -+---------------+----------------------------------------+ -| Service | Ansible | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Kevin Fenzi | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the Fedora Infrastructure ansible command -and repository. - - -Description of the Service: -=========================== -The ansible program is a deployment software which will operate -command by command over a set of configurations. The Fedora -Infrastructure uses a central configuration of ansible to control and -deploy most of the servers used. - -Location of the Service: -======================== -The central ansible server is deployed in the PHX2 colocation. A -secondary backup server is maintained offline in RDU2. - -Service functionality: -====================== -The service is a scripted installation service versus a full -configuration management system like puppet, chef, or cfengine. There -is no service running 24x7 on batcave which checks configurations and -updates clients. Instead after changes have been made, the system -administrator will run an ansible-playbook or script to finish client -configuration. - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -The ansible playbooks can be run by only people who have certain -sysadmin classes or are able to run it via a rbac command system. - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/ansible.rst - -Cost: -===== -The services run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-backups.rst b/docs/sysadmin-guide/sles/SLE-backups.rst deleted file mode 100644 index 718f3b3..0000000 --- a/docs/sysadmin-guide/sles/SLE-backups.rst +++ /dev/null @@ -1,110 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-04-09 | -+---------------+----------------------------------------+ -| Last Updated | 2018-04-09 | -+---------------+----------------------------------------+ -| Service | Backups | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Kevin Fenzi | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, All Fedora Users | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the backups system that - - -Description of the Service: -=========================== - -Location of the Service: -======================== - -Service functionality: -====================== - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: Collectd -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html - - -Cost: -===== -Several virtual systems run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - -Other virtual systems run on servers provided by various ISPs. Network -costs are covered by them. - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-bastion.rst b/docs/sysadmin-guide/sles/SLE-bastion.rst deleted file mode 100644 index c20ccb7..0000000 --- a/docs/sysadmin-guide/sles/SLE-bastion.rst +++ /dev/null @@ -1,131 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | SSH Bastion | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Patrick Uiterwijk | -| | Secondary: Stephen Smoogen | -+---------------+----------------------------------------+ -| Customer | Infrastructure, Release Engineering, | -| | Quality Assurance | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the SSH on various bastion servers run by -Fedora Infrastructure. - -Description of the Service: -=========================== -The SSH Bastions are secure shell gateways from the Internet to Fedoraproject -internal networks. This is to allow various groups to be able to come -from their external networks using a cryptographic protocol. The main -purpose of the gateways are for interactive remote logins, however -they are also used as a throughpoint for other servers. - -https://en.wikipedia.org/wiki/Secure_Shell - -Location of the Service: -======================== -The SSH bastions reside in two physical locations: the PHX2 and RDU2 -Red Hat IT cages. The primary servers are in PHX2 and for disaester -recovery the ones in RDU2 are available. Secondary services are -available for Quality Assurance to get into their dedicated network. - -Service functionality: -====================== -The service needs to allow authorized users access to servers inside -of the associated facility. They should also allow for the user to -'hop' via appropriate methods to other servers they are authorized to -do so. - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems with bastion should be reported to Fedora Infrastructure -in the following order: -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -The authorized users of this server are required to do the following: -1. Keep the SSH keys they use to login password encrypted. -2. To not upload the private keys to non-private servers (cloud, - bastion itself, fedorapeople, school home directory, etc.) -3. To report lost or stolen keys as quickly as found so that - Infrastructure can audit systems. - -The server will be routinely audited and the list of authorized users -will be regularly 'cleaned' of users who have not logged in within the -last 6 months. - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: Collectd -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/bastion-hosts-info.html -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/sshaccess.html - -Cost: -===== -The services run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-dhcp.rst b/docs/sysadmin-guide/sles/SLE-dhcp.rst deleted file mode 100644 index 69fba62..0000000 --- a/docs/sysadmin-guide/sles/SLE-dhcp.rst +++ /dev/null @@ -1,116 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-04-09 | -+---------------+----------------------------------------+ -| Last Updated | 2018-04-09 | -+---------------+----------------------------------------+ -| Service | DHCP/PXE | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Stephen Smoogen | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, All Fedora Users | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== - -This document covers the DHCP/PXE services available at restricted -locations for the installation, setup and build of new systems. - -Description of the Service: -=========================== -DHCP services allows for systems to get set IP addresses during -boot. PXE allows for the system to get a specific kernel and -additional files which allows for quicker installs of systems. - -Location of the Service: -======================== -The primary DHCP servers are in PHX2. - - -Service functionality: -====================== - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: Nagios -- Reporting: Collectd -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html - - -Cost: -===== -Several virtual systems run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - -Other virtual systems run on servers provided by various ISPs. Network -costs are covered by them. - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-infrastructure-git.rst b/docs/sysadmin-guide/sles/SLE-infrastructure-git.rst deleted file mode 100644 index 6dd1fc8..0000000 --- a/docs/sysadmin-guide/sles/SLE-infrastructure-git.rst +++ /dev/null @@ -1,119 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-03-08 | -+---------------+----------------------------------------+ -| Last Updated | 2018-03-08 | -+---------------+----------------------------------------+ -| Service | Infrastructure Git | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: Kevin Fenzi | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -This document is limited to the Fedora Infrastructure GIT repositories -which are maintained on a central server. These are used to hold all -configuration files for things like ansible, DNS, private passwords, -and other files which should be under version control. - - -Description of the Service: -=========================== -This covers git file repositories - -Location of the Service: -======================== -These files are currently maintained on the batcave servers. - - -Service functionality: -====================== -This is less of a service than a needed resource. All files which -should be considered centrally configured and controlled should be -kept in a GIT repository on the infrastructure server. - - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -This resource should have write access limited to approved system -administrators. Read access for most repositories should be considered -public by any sysadmin. Files which are needing to be protected should -be kept in the private repository. - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -https://docs.pagure.org/infra-docs/sysadmin-guide/sops/infra-git-repo.rst - -Cost: -===== -The services run on Dell r630's that are housed in the PHX2 -location. Costs for this are covered by Red Hat Inc. - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-3rdParty.rst b/docs/sysadmin-guide/sles/SLE-template-3rdParty.rst deleted file mode 100644 index 2e10b65..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-3rdParty.rst +++ /dev/null @@ -1,123 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | 3rd Party | -+---------------+----------------------------------------+ -| Availability | 50 weeks x 5 days Regular Bus | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -This service is run by a third party and the service hours are under -control of that provider. Services may be unavailable and unrepairable -by any Fedora Infrastructure employee. - -Service Availability: -===================== -This service should be available for 90% per day. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service by Fedora Infrastructure will be announce -through emails to the following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Maintenance by the provider may be announced at locations unknown to -Fedora Infrastructure. - -Service Provider Responsibilities -================================= -Fedora Infrastructure will attempt to contact the 3rd party service -provider with any issues that they are notified of. Repairs of the -service are outside the control of Fedora Infrastructure. - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -[How is feedback gathered on the service] - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-Critical.rst b/docs/sysadmin-guide/sles/SLE-template-Critical.rst deleted file mode 100644 index e0d4a8a..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-Critical.rst +++ /dev/null @@ -1,108 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Intial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | Infrastructure, | -| | | -+---------------+----------------------------------------+ -| Priority | Critical | -+---------------+----------------------------------------+ -| Availability | 24x7x365 | -+---------------+----------------------------------------+ - - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -This service is considered critical to Fedora and is to be up 24x7x365. - - -Service Availability: -===================== -The service at PHX2 should be available 99.9% of the time with a -backup server that users can switch to in case the primary is down. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities: -================================== -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== - -Cost: -===== - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-Depracated.rst b/docs/sysadmin-guide/sles/SLE-template-Depracated.rst deleted file mode 100644 index 4fa5049..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-Depracated.rst +++ /dev/null @@ -1,121 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | Deprecated | -+---------------+----------------------------------------+ -| Availability | 50 weeks x 5 days Regular Bus | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== - -This service is considered deprecated and to be end of lifed at some -point in the future. Repairs to the service will be below any higher -level service. While generally available 24x7x365 may be taken down -and fixed during Normal Business Hours. - -Service Availability: -===================== -This service should be available for 90% per day. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities -================================= -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -[How is feedback gathered on the service] - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-Important.rst b/docs/sysadmin-guide/sles/SLE-template-Important.rst deleted file mode 100644 index 2147ad9..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-Important.rst +++ /dev/null @@ -1,123 +0,0 @@ -========= - Service -========= - - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | Important | -+---------------+----------------------------------------+ -| Availability | 50x5 Regular Business Hours | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -This service is considered important to Fedora and will be generally -available 24x7x365. Maintenance will be generally done outside of -"Normal Business Hours". Repairs and reported problems will have -priority over Normal, Low, 3rd Party or Deprecated services. Staff -will generally be available for on-call repairs. - -Service Availability: -===================== -This service should be available for 99% per day. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities -================================= -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -Feedback on the service should be either given to the infrastructure -mailing list or the infrastructure ticketing system. - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-Low.rst b/docs/sysadmin-guide/sles/SLE-template-Low.rst deleted file mode 100644 index 1d965b4..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-Low.rst +++ /dev/null @@ -1,119 +0,0 @@ -========= - Service -========= - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | Low | -+---------------+----------------------------------------+ -| Availability | 50 weeks x 5 days Regular Bus | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -This service is considered of low importance to the creation of a -Fedora release and while generally available 24x7x365 may be taken -down and fixed during Normal Business Hours. - -Service Availability: -===================== -This service should be available for 90% per day. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities -================================= -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -[How is feedback gathered on the service] - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template-Normal.rst b/docs/sysadmin-guide/sles/SLE-template-Normal.rst deleted file mode 100644 index 703ec90..0000000 --- a/docs/sysadmin-guide/sles/SLE-template-Normal.rst +++ /dev/null @@ -1,120 +0,0 @@ -========= - Service -========= - - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | 2018-01-19 | -+---------------+----------------------------------------+ -| Last Updated | 2018-01-19 | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | Primary: | -| | Secondary: | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | Normal | -+---------------+----------------------------------------+ -| Availability | Regular Business Hours | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -This service is considered a normal part of the Fedora -project. Services may be up 24x7x365 but operations staff will only -work on repairs during "Regular Business Hours" - -Service Availability: -===================== -This service should be available 95% of a day. - -Incidents, Requests and Problem Management: -=========================================== -Problems should be reported to Fedora Infrastructure in the following -order: - -* https://webchat.freenode.net/?channels=#fedora-admin -* https://pagure.io/fedora-infrastructure/issues -* https://admin.fedoraproject.org/pager - - -Maintenance Windows: -==================== -Maintenance of the service will be announced through emails to the -following Fedora Project mailing lists: -https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ -https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ - -Service Provider Responsibilities -================================= -* Updating the system to latest security release -* Keeping the system backed up - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -[How is feedback gathered on the service] - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/SLE-template.rst b/docs/sysadmin-guide/sles/SLE-template.rst deleted file mode 100644 index 73c103f..0000000 --- a/docs/sysadmin-guide/sles/SLE-template.rst +++ /dev/null @@ -1,108 +0,0 @@ -========= - Service -========= - - -+---------------+----------------------------------------+ -| Field | | -+===============+========================================+ -| Initial Date | | -+---------------+----------------------------------------+ -| Last Updated | | -+---------------+----------------------------------------+ -| Service | | -| | | -+---------------+----------------------------------------+ -| Service Owner | | -| | | -+---------------+----------------------------------------+ -| Customer | | -| | | -+---------------+----------------------------------------+ -| Priority | | -+---------------+----------------------------------------+ -| Availability | | -+---------------+----------------------------------------+ - -========================================= - Service Level Requirements/Expectations -========================================= - -Scope: -====== -[What is included in this service and if needed what is not] - - -Description of the Service: -=========================== -[Services that this SLE covers need to be included] - -Location of the Service: -======================== -[Where are the parts of this service located. While not part of -general SLE's it is a question that is asked a lot due to the -distributed nature of Fedora.] - -Service functionality: -====================== -[What is the service supposed to do? What are general response times -of the service.] - -Service Hours: -============== -[When is the service expected to be available to consumers.] - -Service Availability: -===================== -[What is expected amount that the service should be up per day.] - -Incidents, Requests and Problem Management: -=========================================== -[Where are requests filed. What is the target initial response time -and closure time.] - -Maintenance Windows: -==================== -[How is the service updated over time. How are maintenances announced.] - -Service Provider Responsibilities -================================= - -Security and Governance: -======================== -[Site and user responsibilities are outlined here.] - -User Feedback Mechanism: -======================== -[How is feedback gathered on the service] - -Service Reporting and Metrics: -============================== -- Monitoring: -- Reporting: -- Metrics: - -Training and Documentation: -=========================== -Where is the training and documentation on how the service is -installed, how it is implemented and how it is serviced. - -Other Service Provider Responsibilities: -======================================== -[What is the sp responsible for] - -Service Recipient Responsilities: -================================= -[What is the user responsible for ] - -Cost: -===== -[Cost to the site. Cost to the users] - - -Glossary of Terms: -================== - -References: -=========== - diff --git a/docs/sysadmin-guide/sles/Service-List.rst b/docs/sysadmin-guide/sles/Service-List.rst index 6353864..0d4b865 100644 --- a/docs/sysadmin-guide/sles/Service-List.rst +++ b/docs/sysadmin-guide/sles/Service-List.rst @@ -89,12 +89,10 @@ Low 32. Packages 33. statscache 34. Packages https://admin.fedoraproject.org/pkgdb/packages/ -35. github2fedmsg 36. bugzilla2fedmsg 37. fed-image 38. zanata2fedmsg 39. secondary -40. geoip 41. freemedia 42. pager_server 43. bz_review @@ -131,4 +129,3 @@ Deprecated(?) 4. PkgDB https://admin.fedoraproject.org/pkgdb/ 5. Jenkins https://jenkins.fedorainfracloud.org/ 34. summershum -37. zanata2fedmsg diff --git a/docs/sysadmin-guide/sles/critical/DNS.rst b/docs/sysadmin-guide/sles/critical/DNS.rst new file mode 100644 index 0000000..4761528 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/DNS.rst @@ -0,0 +1,124 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-03-08 | ++---------------+----------------------------------------+ +| Last Updated | 2018-03-08 | ++---------------+----------------------------------------+ +| Service | DNS | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Stephen Smoogen | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, All Fedora Users | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the DNS servers that the Fedora Project +provides as master domains for the various 'Fedora' owned domains. + + +Description of the Service: +=========================== +The DNS nameservers are BIND named servers which provide data to the +Internet for all official FedoraProject domains (fedoraproject.org, +fedorapeople.org, fedoraplanet.org, etc). This allows for computers +connected to the Internet to be able to locate the IP addresses for +services attached to that. + +https://en.wikipedia.org/wiki/Domain_Name_System + +Location of the Service: +======================== +The Fedoraproject nameservers are split around the world at different +datacenters. The main servers are at PHX2 with some servers in Europe, +RDU2, and elsewhere. + +Service functionality: +====================== +The service allows for systems connected to the internet to do ip and +name lookups of systems controlled by the Fedora Project. It is +required to be working for most network related services to work. + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: Collectd +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html + + +Cost: +===== +Several virtual systems run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + +Other virtual systems run on servers provided by various ISPs. Network +costs are covered by them. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/FAS.rst b/docs/sysadmin-guide/sles/critical/FAS.rst new file mode 100644 index 0000000..84b0ac4 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/FAS.rst @@ -0,0 +1,129 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-03-08 | ++---------------+----------------------------------------+ +| Last Updated | 2018-03-08 | ++---------------+----------------------------------------+ +| Service | Fedora Account System | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Patrick Uiterwijk | +| | Secondary: Kevin Fenzi | ++---------------+----------------------------------------+ +| Customer | Infrastructure, All Fedora Account | +| | Users | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the Fedora Account System (FAS) which is +an application written by Fedora Infrastructure for authentication, +and authorization of users, groups and services within the Fedora +Project infrastructure. + + +Description of the Service: +=========================== + +The Fedora Account System was written to cover the account needs of +the Fedora Project. It ties into every part of the Fedora Project +ranging from who can commit to packages, who can build packages, who +can log into servers and what rules bots and services may have in +interacting with users. The system was originally written as a web +application which used SSL certificates and custom passwd databases on +each client. It is now backed in part by another service of kerberos +and IPSILON. + +Location of the Service: +======================== +The main FAS servers are in the PHX2 colocation. All client systems +will update their logins by querying the servers and the FAS servers +will then talk to a backing postgres database. + +Service functionality: +====================== +This service allows for users to log into systems and operate nearly +all Fedora services. + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +This system should only allow logins by people in restricted sysadmin +groups. These groups will be regularly audited and admins removed as +needed. + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/fas-notes.rst +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/fas-openid.rst + + +Cost: +===== +The virtual systems run on Dell r630's that are houses in the PHX2 +colocation. Costs for this are covered by Red Hat. + +Development costs are covered by Fedora Infrastructure and volunteers. + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/Ipsilon.rst b/docs/sysadmin-guide/sles/critical/Ipsilon.rst new file mode 100644 index 0000000..82385b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/Ipsilon.rst @@ -0,0 +1,117 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-03-08 | ++---------------+----------------------------------------+ +| Last Updated | 2018-03-08 | ++---------------+----------------------------------------+ +| Service | IPSILON | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Patrick Uiterwijk | +| | Secondary: Kevin Fenzi | ++---------------+----------------------------------------+ +| Customer | Infrastructure, | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the IPSILON service which backs up the +Fedora Account System. + + +Description of the Service: +=========================== +IPSILON is our central authentication service which authenticates +users against FAS. The service is important to 2factor authentication +needed by system administration to sudo. + +Location of the Service: +======================== +The IPSILON services are are the PHX2 colocation. Client systems +connect to it through a web interface which is balanced by haproxy. + +Service functionality: +====================== +The service is meant to authenticate users for web applications and +other systems. + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +This system should only allow logins by people in restricted sysadmin +groups. These groups will be regularly audited and admins removed as +needed. + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/ipsilon.html + +Cost: +===== +The services run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + +Development costs are covered by Fedora Infrastructure and volunteers. + +Glossary of Terms: +================== + +References: +=========== diff --git a/docs/sysadmin-guide/sles/critical/ansible.rst b/docs/sysadmin-guide/sles/critical/ansible.rst new file mode 100644 index 0000000..cd8b8fb --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/ansible.rst @@ -0,0 +1,121 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-03-08 | ++---------------+----------------------------------------+ +| Last Updated | 2018-03-08 | ++---------------+----------------------------------------+ +| Service | Ansible | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Kevin Fenzi | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the Fedora Infrastructure ansible command +and repository. + + +Description of the Service: +=========================== +The ansible program is a deployment software which will operate +command by command over a set of configurations. The Fedora +Infrastructure uses a central configuration of ansible to control and +deploy most of the servers used. + +Location of the Service: +======================== +The central ansible server is deployed in the PHX2 colocation. A +secondary backup server is maintained offline in RDU2. + +Service functionality: +====================== +The service is a scripted installation service versus a full +configuration management system like puppet, chef, or cfengine. There +is no service running 24x7 on batcave which checks configurations and +updates clients. Instead after changes have been made, the system +administrator will run an ansible-playbook or script to finish client +configuration. + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +The ansible playbooks can be run by only people who have certain +sysadmin classes or are able to run it via a rbac command system. + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/ansible.rst + +Cost: +===== +The services run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/backups.rst b/docs/sysadmin-guide/sles/critical/backups.rst new file mode 100644 index 0000000..718f3b3 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/backups.rst @@ -0,0 +1,110 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-04-09 | ++---------------+----------------------------------------+ +| Last Updated | 2018-04-09 | ++---------------+----------------------------------------+ +| Service | Backups | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Kevin Fenzi | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, All Fedora Users | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the backups system that + + +Description of the Service: +=========================== + +Location of the Service: +======================== + +Service functionality: +====================== + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: Collectd +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html + + +Cost: +===== +Several virtual systems run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + +Other virtual systems run on servers provided by various ISPs. Network +costs are covered by them. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/bastion.rst b/docs/sysadmin-guide/sles/critical/bastion.rst new file mode 100644 index 0000000..c20ccb7 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/bastion.rst @@ -0,0 +1,131 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | SSH Bastion | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Patrick Uiterwijk | +| | Secondary: Stephen Smoogen | ++---------------+----------------------------------------+ +| Customer | Infrastructure, Release Engineering, | +| | Quality Assurance | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the SSH on various bastion servers run by +Fedora Infrastructure. + +Description of the Service: +=========================== +The SSH Bastions are secure shell gateways from the Internet to Fedoraproject +internal networks. This is to allow various groups to be able to come +from their external networks using a cryptographic protocol. The main +purpose of the gateways are for interactive remote logins, however +they are also used as a throughpoint for other servers. + +https://en.wikipedia.org/wiki/Secure_Shell + +Location of the Service: +======================== +The SSH bastions reside in two physical locations: the PHX2 and RDU2 +Red Hat IT cages. The primary servers are in PHX2 and for disaester +recovery the ones in RDU2 are available. Secondary services are +available for Quality Assurance to get into their dedicated network. + +Service functionality: +====================== +The service needs to allow authorized users access to servers inside +of the associated facility. They should also allow for the user to +'hop' via appropriate methods to other servers they are authorized to +do so. + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems with bastion should be reported to Fedora Infrastructure +in the following order: +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +The authorized users of this server are required to do the following: +1. Keep the SSH keys they use to login password encrypted. +2. To not upload the private keys to non-private servers (cloud, + bastion itself, fedorapeople, school home directory, etc.) +3. To report lost or stolen keys as quickly as found so that + Infrastructure can audit systems. + +The server will be routinely audited and the list of authorized users +will be regularly 'cleaned' of users who have not logged in within the +last 6 months. + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: Collectd +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/bastion-hosts-info.html +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/sshaccess.html + +Cost: +===== +The services run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/dhcp.rst b/docs/sysadmin-guide/sles/critical/dhcp.rst new file mode 100644 index 0000000..69fba62 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/dhcp.rst @@ -0,0 +1,116 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-04-09 | ++---------------+----------------------------------------+ +| Last Updated | 2018-04-09 | ++---------------+----------------------------------------+ +| Service | DHCP/PXE | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Stephen Smoogen | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, All Fedora Users | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== + +This document covers the DHCP/PXE services available at restricted +locations for the installation, setup and build of new systems. + +Description of the Service: +=========================== +DHCP services allows for systems to get set IP addresses during +boot. PXE allows for the system to get a specific kernel and +additional files which allows for quicker installs of systems. + +Location of the Service: +======================== +The primary DHCP servers are in PHX2. + + +Service functionality: +====================== + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: Nagios +- Reporting: Collectd +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/dns.html + + +Cost: +===== +Several virtual systems run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + +Other virtual systems run on servers provided by various ISPs. Network +costs are covered by them. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/critical/infrastructure-git.rst b/docs/sysadmin-guide/sles/critical/infrastructure-git.rst new file mode 100644 index 0000000..6dd1fc8 --- /dev/null +++ b/docs/sysadmin-guide/sles/critical/infrastructure-git.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-03-08 | ++---------------+----------------------------------------+ +| Last Updated | 2018-03-08 | ++---------------+----------------------------------------+ +| Service | Infrastructure Git | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: Kevin Fenzi | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +This document is limited to the Fedora Infrastructure GIT repositories +which are maintained on a central server. These are used to hold all +configuration files for things like ansible, DNS, private passwords, +and other files which should be under version control. + + +Description of the Service: +=========================== +This covers git file repositories + +Location of the Service: +======================== +These files are currently maintained on the batcave servers. + + +Service functionality: +====================== +This is less of a service than a needed resource. All files which +should be considered centrally configured and controlled should be +kept in a GIT repository on the infrastructure server. + + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +This resource should have write access limited to approved system +administrators. Read access for most repositories should be considered +public by any sysadmin. Files which are needing to be protected should +be kept in the private repository. + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +https://docs.pagure.org/infra-docs/sysadmin-guide/sops/infra-git-repo.rst + +Cost: +===== +The services run on Dell r630's that are housed in the PHX2 +location. Costs for this are covered by Red Hat Inc. + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/deprecated/torrent.rst b/docs/sysadmin-guide/sles/deprecated/torrent.rst new file mode 100644 index 0000000..e99d1d4 --- /dev/null +++ b/docs/sysadmin-guide/sles/deprecated/torrent.rst @@ -0,0 +1,126 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Deprecated | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== + +This document covers the bittorrent services available on the internet +for users to download a restricted set of isos from. + +Description of the Service: +=========================== +Torrent acts as a seeder for various releases and spins so that users +may use the bittorrent protocol to download ISOs. Torrents were useful +for users in low bandwidth areas to get faster downloads however they +require a large number of volunteer participants. + + +Location of the Service: +======================== +The torrent seeder resides in Ibiblio network. + +Service functionality: +====================== + + +Service Hours: +============== + +This service is considered deprecated and to be end of lifed at some +point in the future. Repairs to the service will be below any higher +level service. While generally available 24x7x365 may be taken down +and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +The torrent seeder software and related software have had limited +support from their upstreams. The service may be blocked on many +networks as torrent sharing can cause audit problems. + +User Feedback Mechanism: +======================== +Service problems should have tickets opened in the Fedora +infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +There is no training or documentation on this service. + +Other Service Provider Responsibilities: +======================================== +* Responding to outages and seeing if they can be fixed +* Cleaning up old torrents + +Cost: +===== +This service has different costs to different groups. This tool is not +automated so releng has to build torrents each release. This tool +sometimes gets blocked on networks it is served from. The software +does only snapshots of usage so tracking how well it is serving the +community is hard. + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/autosign.rst b/docs/sysadmin-guide/sles/important/autosign.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/autosign.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/basset.rst b/docs/sysadmin-guide/sles/important/basset.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/basset.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/bodhi.rst b/docs/sysadmin-guide/sles/important/bodhi.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/bodhi.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/buildhosts.rst b/docs/sysadmin-guide/sles/important/buildhosts.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/buildhosts.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/certgetter.rst b/docs/sysadmin-guide/sles/important/certgetter.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/certgetter.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/composers.rst b/docs/sysadmin-guide/sles/important/composers.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/composers.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/datagrepper.rst b/docs/sysadmin-guide/sles/important/datagrepper.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/datagrepper.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/downloads.rst b/docs/sysadmin-guide/sles/important/downloads.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/downloads.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/fedmsg.rst b/docs/sysadmin-guide/sles/important/fedmsg.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/fedmsg.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/fedora-src.rst b/docs/sysadmin-guide/sles/important/fedora-src.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/fedora-src.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/greenwave.rst b/docs/sysadmin-guide/sles/important/greenwave.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/greenwave.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/haproxy.rst b/docs/sysadmin-guide/sles/important/haproxy.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/haproxy.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/koji.rst b/docs/sysadmin-guide/sles/important/koji.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/koji.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/logging.rst b/docs/sysadmin-guide/sles/important/logging.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/logging.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/mbs.rst b/docs/sysadmin-guide/sles/important/mbs.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/mbs.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/memcached.rst b/docs/sysadmin-guide/sles/important/memcached.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/memcached.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/mirrormanager.rst b/docs/sysadmin-guide/sles/important/mirrormanager.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/mirrormanager.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/mobyregistry.rst b/docs/sysadmin-guide/sles/important/mobyregistry.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/mobyregistry.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/mysql.rst b/docs/sysadmin-guide/sles/important/mysql.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/mysql.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/nagios.rst b/docs/sysadmin-guide/sles/important/nagios.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/nagios.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/odcs.rst b/docs/sysadmin-guide/sles/important/odcs.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/odcs.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/pdc.rst b/docs/sysadmin-guide/sles/important/pdc.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/pdc.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/postgresql.rst b/docs/sysadmin-guide/sles/important/postgresql.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/postgresql.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/resultsdb.rst b/docs/sysadmin-guide/sles/important/resultsdb.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/resultsdb.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/important/smtp-gateway.rst b/docs/sysadmin-guide/sles/important/smtp-gateway.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/important/smtp-gateway.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/ambassadors.rst b/docs/sysadmin-guide/sles/low/ambassadors.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/ambassadors.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/anitya.rst b/docs/sysadmin-guide/sles/low/anitya.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/anitya.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/ansiblemagazine.rst b/docs/sysadmin-guide/sles/low/ansiblemagazine.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/ansiblemagazine.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/asknot.rst b/docs/sysadmin-guide/sles/low/asknot.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/asknot.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/autocloud.rst b/docs/sysadmin-guide/sles/low/autocloud.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/autocloud.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/badges.rst b/docs/sysadmin-guide/sles/low/badges.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/badges.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/blockerbugs.rst b/docs/sysadmin-guide/sles/low/blockerbugs.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/blockerbugs.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/bugyou.rst b/docs/sysadmin-guide/sles/low/bugyou.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/bugyou.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/bugzilla2fedmsg.rst b/docs/sysadmin-guide/sles/low/bugzilla2fedmsg.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/bugzilla2fedmsg.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/bz_review.rst b/docs/sysadmin-guide/sles/low/bz_review.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/bz_review.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/easyfix.rst b/docs/sysadmin-guide/sles/low/easyfix.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/easyfix.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/elections.rst b/docs/sysadmin-guide/sles/low/elections.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/elections.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/fed-image.rst b/docs/sysadmin-guide/sles/low/fed-image.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/fed-image.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/fedocal.rst b/docs/sysadmin-guide/sles/low/fedocal.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/fedocal.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/fedoramagazine.rst b/docs/sysadmin-guide/sles/low/fedoramagazine.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/fedoramagazine.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/fedorapeople.rst b/docs/sysadmin-guide/sles/low/fedorapeople.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/fedorapeople.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/fedoraplanet.rst b/docs/sysadmin-guide/sles/low/fedoraplanet.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/fedoraplanet.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/freemedia.rst b/docs/sysadmin-guide/sles/low/freemedia.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/freemedia.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/geoip.rst b/docs/sysadmin-guide/sles/low/geoip.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/geoip.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/github2fedmsg.rst b/docs/sysadmin-guide/sles/low/github2fedmsg.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/github2fedmsg.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/gobby.rst b/docs/sysadmin-guide/sles/low/gobby.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/gobby.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/hotness.rst b/docs/sysadmin-guide/sles/low/hotness.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/hotness.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/keys.rst b/docs/sysadmin-guide/sles/low/keys.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/keys.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/koschei.rst b/docs/sysadmin-guide/sles/low/koschei.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/koschei.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/loopabull.rst b/docs/sysadmin-guide/sles/low/loopabull.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/loopabull.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/mdapi.rst b/docs/sysadmin-guide/sles/low/mdapi.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/mdapi.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/meetbot.rst b/docs/sysadmin-guide/sles/low/meetbot.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/meetbot.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/nuancier.rst b/docs/sysadmin-guide/sles/low/nuancier.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/nuancier.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/openshift.rst b/docs/sysadmin-guide/sles/low/openshift.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/openshift.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/package-review-status.rst b/docs/sysadmin-guide/sles/low/package-review-status.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/package-review-status.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/packages.rst b/docs/sysadmin-guide/sles/low/packages.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/packages.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/pager_server.rst b/docs/sysadmin-guide/sles/low/pager_server.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/pager_server.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/pastebin.rst b/docs/sysadmin-guide/sles/low/pastebin.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/pastebin.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/release-monitoring.rst b/docs/sysadmin-guide/sles/low/release-monitoring.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/release-monitoring.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/statscache.rst b/docs/sysadmin-guide/sles/low/statscache.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/statscache.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/tagger.rst b/docs/sysadmin-guide/sles/low/tagger.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/tagger.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/taiga.rst b/docs/sysadmin-guide/sles/low/taiga.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/taiga.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/unbound.rst b/docs/sysadmin-guide/sles/low/unbound.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/unbound.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/websites-misc.rst b/docs/sysadmin-guide/sles/low/websites-misc.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/websites-misc.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/low/zanata2fedmsg.rst b/docs/sysadmin-guide/sles/low/zanata2fedmsg.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/low/zanata2fedmsg.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/beaker.rst b/docs/sysadmin-guide/sles/normal/beaker.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/beaker.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/data-analysis.rst b/docs/sysadmin-guide/sles/normal/data-analysis.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/data-analysis.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/faf.rst b/docs/sysadmin-guide/sles/normal/faf.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/faf.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/fmn.rst b/docs/sysadmin-guide/sles/normal/fmn.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/fmn.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/freshmaker.rst b/docs/sysadmin-guide/sles/normal/freshmaker.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/freshmaker.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/infracloud.rst b/docs/sysadmin-guide/sles/normal/infracloud.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/infracloud.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/kerneltest.rst b/docs/sysadmin-guide/sles/normal/kerneltest.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/kerneltest.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/mailman3.rst b/docs/sysadmin-guide/sles/normal/mailman3.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/mailman3.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/notifications.rst b/docs/sysadmin-guide/sles/normal/notifications.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/notifications.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/pagure.rst b/docs/sysadmin-guide/sles/normal/pagure.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/pagure.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/www-docs.rst b/docs/sysadmin-guide/sles/normal/www-docs.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/www-docs.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/normal/www-wiki.rst b/docs/sysadmin-guide/sles/normal/www-wiki.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/normal/www-wiki.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-3rdParty.rst b/docs/sysadmin-guide/sles/templates/SLE-template-3rdParty.rst new file mode 100644 index 0000000..2e10b65 --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-3rdParty.rst @@ -0,0 +1,123 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | 3rd Party | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is run by a third party and the service hours are under +control of that provider. Services may be unavailable and unrepairable +by any Fedora Infrastructure employee. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service by Fedora Infrastructure will be announce +through emails to the following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Maintenance by the provider may be announced at locations unknown to +Fedora Infrastructure. + +Service Provider Responsibilities +================================= +Fedora Infrastructure will attempt to contact the 3rd party service +provider with any issues that they are notified of. Repairs of the +service are outside the control of Fedora Infrastructure. + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-Critical.rst b/docs/sysadmin-guide/sles/templates/SLE-template-Critical.rst new file mode 100644 index 0000000..e0d4a8a --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-Critical.rst @@ -0,0 +1,108 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Intial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | Infrastructure, | +| | | ++---------------+----------------------------------------+ +| Priority | Critical | ++---------------+----------------------------------------+ +| Availability | 24x7x365 | ++---------------+----------------------------------------+ + + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered critical to Fedora and is to be up 24x7x365. + + +Service Availability: +===================== +The service at PHX2 should be available 99.9% of the time with a +backup server that users can switch to in case the primary is down. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities: +================================== +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== + +Cost: +===== + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-Depracated.rst b/docs/sysadmin-guide/sles/templates/SLE-template-Depracated.rst new file mode 100644 index 0000000..4fa5049 --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-Depracated.rst @@ -0,0 +1,121 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Deprecated | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== + +This service is considered deprecated and to be end of lifed at some +point in the future. Repairs to the service will be below any higher +level service. While generally available 24x7x365 may be taken down +and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-Important.rst b/docs/sysadmin-guide/sles/templates/SLE-template-Important.rst new file mode 100644 index 0000000..2147ad9 --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-Important.rst @@ -0,0 +1,123 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Important | ++---------------+----------------------------------------+ +| Availability | 50x5 Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered important to Fedora and will be generally +available 24x7x365. Maintenance will be generally done outside of +"Normal Business Hours". Repairs and reported problems will have +priority over Normal, Low, 3rd Party or Deprecated services. Staff +will generally be available for on-call repairs. + +Service Availability: +===================== +This service should be available for 99% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +Feedback on the service should be either given to the infrastructure +mailing list or the infrastructure ticketing system. + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-Low.rst b/docs/sysadmin-guide/sles/templates/SLE-template-Low.rst new file mode 100644 index 0000000..1d965b4 --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-Low.rst @@ -0,0 +1,119 @@ +========= + Service +========= + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Low | ++---------------+----------------------------------------+ +| Availability | 50 weeks x 5 days Regular Bus | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered of low importance to the creation of a +Fedora release and while generally available 24x7x365 may be taken +down and fixed during Normal Business Hours. + +Service Availability: +===================== +This service should be available for 90% per day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template-Normal.rst b/docs/sysadmin-guide/sles/templates/SLE-template-Normal.rst new file mode 100644 index 0000000..703ec90 --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template-Normal.rst @@ -0,0 +1,120 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | 2018-01-19 | ++---------------+----------------------------------------+ +| Last Updated | 2018-01-19 | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | Primary: | +| | Secondary: | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | Normal | ++---------------+----------------------------------------+ +| Availability | Regular Business Hours | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +This service is considered a normal part of the Fedora +project. Services may be up 24x7x365 but operations staff will only +work on repairs during "Regular Business Hours" + +Service Availability: +===================== +This service should be available 95% of a day. + +Incidents, Requests and Problem Management: +=========================================== +Problems should be reported to Fedora Infrastructure in the following +order: + +* https://webchat.freenode.net/?channels=#fedora-admin +* https://pagure.io/fedora-infrastructure/issues +* https://admin.fedoraproject.org/pager + + +Maintenance Windows: +==================== +Maintenance of the service will be announced through emails to the +following Fedora Project mailing lists: +https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/ +https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/ + +Service Provider Responsibilities +================================= +* Updating the system to latest security release +* Keeping the system backed up + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== + diff --git a/docs/sysadmin-guide/sles/templates/SLE-template.rst b/docs/sysadmin-guide/sles/templates/SLE-template.rst new file mode 100644 index 0000000..73c103f --- /dev/null +++ b/docs/sysadmin-guide/sles/templates/SLE-template.rst @@ -0,0 +1,108 @@ +========= + Service +========= + + ++---------------+----------------------------------------+ +| Field | | ++===============+========================================+ +| Initial Date | | ++---------------+----------------------------------------+ +| Last Updated | | ++---------------+----------------------------------------+ +| Service | | +| | | ++---------------+----------------------------------------+ +| Service Owner | | +| | | ++---------------+----------------------------------------+ +| Customer | | +| | | ++---------------+----------------------------------------+ +| Priority | | ++---------------+----------------------------------------+ +| Availability | | ++---------------+----------------------------------------+ + +========================================= + Service Level Requirements/Expectations +========================================= + +Scope: +====== +[What is included in this service and if needed what is not] + + +Description of the Service: +=========================== +[Services that this SLE covers need to be included] + +Location of the Service: +======================== +[Where are the parts of this service located. While not part of +general SLE's it is a question that is asked a lot due to the +distributed nature of Fedora.] + +Service functionality: +====================== +[What is the service supposed to do? What are general response times +of the service.] + +Service Hours: +============== +[When is the service expected to be available to consumers.] + +Service Availability: +===================== +[What is expected amount that the service should be up per day.] + +Incidents, Requests and Problem Management: +=========================================== +[Where are requests filed. What is the target initial response time +and closure time.] + +Maintenance Windows: +==================== +[How is the service updated over time. How are maintenances announced.] + +Service Provider Responsibilities +================================= + +Security and Governance: +======================== +[Site and user responsibilities are outlined here.] + +User Feedback Mechanism: +======================== +[How is feedback gathered on the service] + +Service Reporting and Metrics: +============================== +- Monitoring: +- Reporting: +- Metrics: + +Training and Documentation: +=========================== +Where is the training and documentation on how the service is +installed, how it is implemented and how it is serviced. + +Other Service Provider Responsibilities: +======================================== +[What is the sp responsible for] + +Service Recipient Responsilities: +================================= +[What is the user responsible for ] + +Cost: +===== +[Cost to the site. Cost to the users] + + +Glossary of Terms: +================== + +References: +=========== +