From c8588fd436df6c7b04cdf356e566d4be233aa3be Mon Sep 17 00:00:00 2001 From: Stephen J Smoogen Date: Jul 07 2018 01:01:49 +0000 Subject: Merge #118 `Put in first stage of SLES into infra-docs` --- 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/General-SLE.rst b/docs/sysadmin-guide/sles/General-SLE.rst new file mode 100644 index 0000000..2628ee2 --- /dev/null +++ b/docs/sysadmin-guide/sles/General-SLE.rst @@ -0,0 +1,215 @@ +=================== + Purpose and scope +=================== + +This Service Level Expectations document is to help provide a high +level description of the services, equipment and duties of the Fedora +Infrastructure team. It will touch upon the responsibilities of both +customers and Infrastructure towards providing and receiving +services. + +Further documents will be added to cover each service in more +detail. This document is a work in progress and will be modified in +response to the ever changing goals and needs of the project. + +================ + Group Overview +================ + +The consistency of the Fedora Infrastructure team is covered in the +external document: https://fedoraproject.org/wiki/Infrastructure + +The primary purpose of Fedora Infrastructure is to help produce +regular releases of the Fedora Operating System. Services which are +aligned with that purpose will be alloted a higher priority than other +services. + +Secondary purposes are to help provide services for other parts of the +Fedora Project to communicate effectively, gather information about +uses, and market their work. + +======================== + Primary Business Hours +======================== + +Fedora Infrastructure's primary business hours are aligned with the +work schedule of Red Hat Inc. Normal hours should be seen as during +Monday through Friday 1400 UTC to 2300 UTC with US national holidays +and a 2 week end of year closure affecting staffing and response +times. + +Services outside of primary business hours are done on call and depend +on the availability of staff. + + +============================ + Roles and Responsibilities +============================ + +Fedora Infrastructure to Community +---------------------------------- +* To have staff present and available in appropriate IRC channels to + answer questions during primary hours. +* To have particular staff on-call during off hours so that community + members can contact for Critical and Important services. +* Interact with community members with respect and courtesy. +* Work with community members to get accurate and thorough + documentation of incidents, problems, or feature requests. +* When possible resolve the problem as soon as acknowledged. +* Communicate clearly estimated resolution times. +* Move items which can not be resolved within a reasonable time to + future feature requests or close out. + +Community Member to Fedora Infrastructure +----------------------------------------- +* Give full and detailed reports of the problem or requested service. +* Provide clear and complete contact information and times when + available. +* Leave alternative contacts who can also be available in case of + vacation or other emergencies. +* When contacted by Fedora IT, respond back within 5 business days + +Fedora Infrastructure to Fedora Infrastructure +---------------------------------------------- +* Have a clear schedule of reachable hours. +* Set and take regular vacation time to be rested. +* Rotate through days on-call in IRC and tickets. +* If adding a new service, be available outside of normal business + hours to help debug problems. +* Follow procedures and checklists when adding or updating services. +* Help with regular audits of the documentation + +================================== + Definition of Service Priorities +================================== + +The general design of service priorities is that of concentric circles +where items rely on services in their own circle or a circle below +them. + +1. Critical services are ones which Fedora Infrastructure will work on + 24x7 with 52 week coverage if an unplanned outage occurs. Services + will be configured to be highly available with an estimated + planned/unplanned uptime of 95%. Response time should be within 1 + hour. + +2. Important services are ones which Fedora Infrastructure will work + to be available 24x7 with 50 week coverage. Response times during + primary hours should be 1 hour and outside of it should be 4 + hours. + +3. Normal services are ones which Fedora Infrastructure will work to + be available during primary work hours. Problems outside of these + hours will be looked at as people are available. The services may + be available outside of these but are of a lower priority than + important services. + +4. Low priority services are ones which are not critical or important for the + primary function of Fedora Infrastructure. They will be worked on + and looked at during primary business hours. Response times should + be within 1 business day. + +5. Third Party services are ones which Fedora Infrastructure has + outsourced tools and services to. Uptimes, service hours, and + coverage are dictated by the third party. Depending on the type of + problem, Fedora Infrastructure will act as an intermediary or in + the case of tools like retrace and COPR direct the user to talk + with the service owners. + +6. Deprecated services are ones which Fedora Infrastructure are no + longer putting resources into. This may be because the project has + completed its mission, the upstream software is dead, or the + original reasons for the product are available. Problems with these + services will be looked at during primary business hours. Responses + may be mostly "Will Not Fix". + +======================== + Limitations on Support +======================== +* Some services that are associated with Fedora are provided by third + parties. Changes and outages which affect them are outside the + control of Fedora Infrastructure. +* Fedora Infrastructure will prioritize issues and requests that + affect multiple people or teams over a smaller group or individual. +* Fedora Infrastructure has limited budget and hours. Requests and + features will be prioritized to fit within those. +* Fedora Infrastructure is bound by the laws and regulations of the + United States of America. This means that certain requests, changes + and problems are outside the ability of members to deal with. + + +========== + Glossary +========== + +Planned outage: A planned outage is one that is announced with enough +time to give most user's the ability to plan around it. + +Unplanned outage: An outage that occurs suddenly without proper +allowance for users to plan around it. + +Scheduled outage: An outage which has been scheduled to occur but may +not have been announced with enough time for users to plan around it. + +High Availability: Systems are available during specified operating +hours with any unplanned outages 'masked' by other tools. + +Continuous Operations: Systems are available 24 hours a day, 7 days a week +with no scheduled outages. Unplanned outages are possible during this +time. + +Continuous Availability: Systems or applications are available 24x7 +with no planned or unplanned outages. This is a combination of high +availability and continuous operations. + +Level of availability: +| Percentage | Max outage time per day | +| 90% | 144.0 minutes | +| 95% | 72.0 minutes | +| 99% | 14.4 minutes | +| 99.9% | 1.4 minutes | + +Commited Hours of Availability: Hours that an organization will have staff +available to help deal with issues with systems, services, and +applications. Also known as "Regular Business Hours" + +Outage Hours: Total number of hours of outage considered normal for +calculating achieved availability. + +Response Time: The time between the users notification of the problem +and when the help desk will begin to work on that problem. + +Resolution Update: The frequency of updates to tickets + +Estimated Time of Resolution: + +Priority Levels: + * Emergency: Problems which are site wide, and affect the core + functions of the project. + * Urgent: Problems which affect multiple functions and groups in the + project. + * Normal: Problems which affect a single user from performing needed + duties. + * Low: A request for service, instruction, information that has no + immediate impact on services. + + +=================== + Outside Resources +=================== + +The following sites were used in building the general forms and data +for the SLE. + +* https://en.wikipedia.org/wiki/IT_service_management +* https://en.wikipedia.org/wiki/ITIL + +* https://confluence.cornell.edu/display/itsmp/Service+Level+Management +* https://kb.brandeis.edu/display/LTS/Help+Desk+Service+Level+Expectations +* https://www.givainc.com/blog/index.cfm/2009/9/1/Improving-Customer-Satisfaction-by-Implementing-a-Service-Level-Agreement-SLA +* https://www.emich.edu/it/help/pdf/ithdsle.pdf +* http://blog.altairci.com/service-level-expectations +* https://cms.montgomerycollege.edu/oit/HelpAndSupport.aspx?id=91 +* http://www.harriskern.com/wp-content/uploads/2012/05/Managing-User-Service-Level-Expectations.pdf +* http://www.myitstudy.com/blog/2013/05/service-level-management/ +* https://its.uiowa.edu/support/article/2790 diff --git a/docs/sysadmin-guide/sles/Service-List.rst b/docs/sysadmin-guide/sles/Service-List.rst new file mode 100644 index 0000000..e7883d7 --- /dev/null +++ b/docs/sysadmin-guide/sles/Service-List.rst @@ -0,0 +1,141 @@ +Critical +======== + +1. DNS +2. Bastion ssh +3. Authentication/authorization (FAS) https://admin.fedoraproject.org/accounts/ +4. Authentication/authorization (Ipsilon) https://id.fedoraproject.org +5. Configuration Management (ansible) +6. Source control (git) +7. Backups +8. DHCP/PXE +9. IPA + +Important +========= + +1. Koji https://koji.fedoraproject.org +2. Bodhi https://bodhi.fedoraproject.org +3. Downloads https://dl.fedoraproject.org/ +4. Fedora Souce code https://src.fedoraproject.org/ +5. MirrorManager https://admin.fedoraproject.org/mirrormanager +6. Nagios https://nagios.fedoraproject.org +7. HAProxy https://admin.fedoraproject.org/haproxy/proxy01 +8. Postgres databases +9. Mysql databases +10. Product Definition Center https://pdc.fedoraproject.org/ +11. Greenwave +12. Fedmsg +13. DataGrepper https://apps.fedoraproject.org/datagrepper/ +14. Email gateway bastion.fedoraproject.org +15. Autosign +16. Composer +17. Buildhosts +18. Docker registry +19. Memcached +20. Logging +21. Basset +22. PDC +23. resultsdb +24. certgetter +25. mbs +26. odcs + +Normal +====== + +1. Pagure https://pagure.io +2. The Mailing Lists https://lists.fedoraproject.org +3. Wiki https://fedoraproject.org/wiki/Fedora_Project_Wiki +4. Documentation +5. Notifications https://apps.fedoraproject.org/notifications +6. Kerneltest https://apps.fedoraproject.org/kerneltest +7. Fedora InfraCloud https://fedorainfracloud.org +8. FMN +9. FAF +10. Beaker +11. Freshmaker +12. Data Analysis + +Low +=== + +1. Ambassadors https://fedoraproject.org/membership-map/ambassadors.html +2. Asknot http://whatcanidoforfedora.org/ +3. Badges https://badges.fedoraproject.org/ +4. Blocker Bugs https://qa.fedoraproject.org/blockerbugs/ +5. Easyfix https://fedoraproject.org/easyfix/ +6. Elections https://apps.fedoraproject.org/#Elections +7. FedoCal https://apps.fedoraproject.org/#FedoCal +8. Fedora Magazine https://fedoramagazine.org/ +9. Fedora People https://fedorapeople.org/ +10. GeoIP https://geoip.fedoraproject.org/ +11. github2fedmsg https://apps.fedoraproject.org/github2fedmsg +12. Mdapi https://apps.fedoraproject.org/mdapi/ +13. Meetbot https://apps.fedoraproject.org/#Meetbot +14. Nuancier https://apps.fedoraproject.org/#Nuancier +15. Paste https://paste.fedoraproject.org +16. Release Monitoring https://release-monitoring.org/ +17. Review Status https://fedoraproject.org/PackageReviewStatus/ +18. Tagger https://apps.fedoraproject.org/tagger/ +19. Taiga https://taiga.fedorainfracloud.org/ +20. The Planet https://fedoraplanet.org/ +21. Unbound +22. Anitya +23. Autocloud +24. Bugyou +25. Gobby +26. Keys +27. Koschei +28. Loopabull +29. Hotness +30. OpenShift +31. Packages +32. statscache +33. Packages https://admin.fedoraproject.org/pkgdb/packages/ +34. bugzilla2fedmsg +35. fed-image +36. zanata2fedmsg +37. secondary +38. freemedia +39. pager_server +40. bz_review +41. websites + +Websites +-------- + +1. fedora-web +2. fedora-budget +3. fedora-docs +4. developer +5. whatcanidoforfedora +6. membership-map +7. zanata +8. review-stats +9. fedora_owner_change + +Third Party +=========== + +* Outside of Fedora Infrastructure to fix. + +1. Network connectivity to PHX2/RDU2 +2. FreeNode IRC https://freenode.net +3. Ask Fedora https://ask.fedoraproject.org/ +4. COPR https://copr.fedorainfracloud.org/ +5. CI https://ci.centos.org +6. Retrace https://retrace.fedoraproject.org +7. Bugzilla https://bugzilla.redhat.com/ +8. Status https://status.fedoraproject.org +9. Taskotron https://taskotron.fedoraproject.org/ +10. Openqa + + +Deprecated(?) +============= +1. Torrents https://torrent.fedoraproject.org +2. Darkserver https://darkserver.fedoraproject.org/ +3. PkgDB https://admin.fedoraproject.org/pkgdb/ +4. Jenkins https://jenkins.fedorainfracloud.org/ +5. summershum 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: +=========== + diff --git a/docs/sysadmin-guide/sops/guestmigrate.rst b/docs/sysadmin-guide/sops/guestmigrate.rst deleted file mode 100644 index 4df35ad..0000000 --- a/docs/sysadmin-guide/sops/guestmigrate.rst +++ /dev/null @@ -1,90 +0,0 @@ -.. title: Guest Migration SOP -.. slug: infra-guest-migration -.. date: 2011-10-07 -.. taxonomy: Contributors/Infrastructure - -============================== -Guest migration between hosts. -============================== - -Move guests from one host to another. - -Contact Information -=================== - -Owner - Fedora Infrastructure Team - -Contact - #fedora-admin, sysadmin-main - -Location - PHX, Tummy, ibiblio, Telia, OSUOSL - -Servers - All xen servers, kvm/libvirt servers. - -Purpose - Migrate guests - -How to do it -============ - -1. Schedule outage time if any. This will need to be long enough to copy - the data from one host to another, so will depend on guest disk - size. - -2. Turn off monitoring in nagios - -3. On new host create disk space for server:: - - lvcreate -n app03 -L 32G vg_guests00 - -4. prepare old guest for migration: - a) if system is xen, install a regular kernel - b) look for entries for xenblk and hvc0 in /etc files - -5. Shutdown the guest. - -6. :: - - virsh dumpxml guestname > guest.xml - -7. Copy guest.xml to the new machine. You will need to make various - edits depending on if the system was originally xen or such. I - normally need to compare an existing xml on the target system and the - one we dumped out to make up the differences. - -8. Define the guest on the new machine: 'virsh define guest.xml'. - Depending on the changes in the xml this may not work and you will - need to make many manual changes plus copy the guest.xml to - ``/etc/libvirtd/qemu`` and do a ``/sbin/service libvirtd restart`` - -9. Insert iptables rule for nc transfer:: - - iptables -I INPUT 14 -s -m tcp -p tcp --dport 11111 -j ACCEPT - -10. On the destination host: - - - RHEL-5:: - - nc -l -p 11111 | dd of=/dev/mapper/ - - - RHEL-6:: - - nc -l 11111 | dd of=/dev/mapper/ - -11. On the source host:: - - dd if=/dev/mapper/guest-partition | nc desthost 11111 - - Wait for the copy to finish. You can do the following to track how - far something has gone by finding the dd pid and then sending a - 'kill -USR1' to it. - -11. start the guest on the new host:: - - ``virsh start guest`` - -12. On the source host, rename storage and undefine guest so it's not started. - diff --git a/docs/sysadmin-guide/sops/ibm-drive-replacement.rst b/docs/sysadmin-guide/sops/ibm-drive-replacement.rst deleted file mode 100644 index afafe0c..0000000 --- a/docs/sysadmin-guide/sops/ibm-drive-replacement.rst +++ /dev/null @@ -1,342 +0,0 @@ -.. title: Drive Replacement SOP -.. slug: infra-drive-replacement -.. date: 2012-07-13 -.. taxonomy: Contributors/Infrastructure - -==================================== -Drive Replacement Infrastructure SOP -==================================== - -At present this SOP only works for the X series IBM servers. - -We have multiple machines with lots of different drives in them. For the -most part now though, we are trying to standardise on IBM X series -servers. At present I've not figured out how to disable onboard raid, as a -result of this many of our servers have two raid 0 arrays then we do -software raid on this. - -The system xen11 is currently an HP ProLiant DL180 G5 with its own -interesting RAID system (using Compaq Smart Array ccis). Like the IBM X -series each drive is considered a single RAID-0 instance which is then -accessed through a logical drive. - -Contents -======== - -1. Contact Information -2. Verify the drive is dead - - 1. Re-adding a drive (poor man's fix) - -3. Actually replacing the drive (IBM) - - 1. Collecting Data - 2. Call IBM - 3. Get the package, give access to the tech - 4. Prepwork before the tech arrives - 5. Tech on site - 6. Rebuild the array - -4. Actually Replacing the Drive (HP) - - 1. Collecting data - 2. Call HP - 3. Get the package, give access to the tech - 4. Prepwork before the tech arrives - 5. Tech on site - 6. Rebuild the array - -5. Installing RaidMan (IBM Only) - -Database - DriveReplacement - -Contact Information -=================== - -Owner - Fedora Infrastructure Team -Contact - #fedora-admin, sysadmin-main -Location - All -Servers - All -Purpose - Steps for drive replacement. - -Verify the drive is dead -======================== - -:: - - $ cat /proc/mdadm - Personalities : [raid1] - md0 : active raid1 sdb1[1] sda1[0] - 513984 blocks [2/2] [UU] - - md1 : active raid1 sdb2[2](F) sda2[0] - 487717248 blocks [2/1] [U_] - -This indicates that md1 is in a degraded state and that /dev/sdb2 is the -failed drive. Notice that /dev/sdb1 (same physical drive as /dev/sdb2) is -not failed. /dev/md0 (not yet degraded) is showing a good state. This is -because /dev/md0 is /boot. If you run:: - - touch /boot/t - sync - rm /boot/t - -That should make /dev/md0 notice that its drive is also failed. If it does -not fail, its possible the drive is fine and that some blip happened that -caused it to get flagged as dead. It is also worthwhile to log in to -xenX-mgmt to determine if the RSAII adapter has noticed the drive is dead. - -If you think the drive just had a blip and is fine, see "Re-adding" below - -Re-adding a drive (poor man's fix) ------------------------------------ - -Basically what we're doing here is making sure the drive is, infact, dead. -Obviously you don't want to do this more then once on a drive, if it -continues to fail. Replace it. - -:: - - # cat /proc/mdadm - Personalities : [raid1] - md0 : active raid1 sdb1[1] sda1[0] - 513984 blocks [2/2] [UU] - - md1 : active raid1 sdb2[2](F) sda2[0] - 487717248 blocks [2/1] [U_] - # mdadm /dev/md1 --remove /dev/sdb2 - # mdadm /dev/md1 --add /dev/sdb2 - # cat /proc/mdstat - md0 : active raid1 sdb1[1] sda1[0] - 513984 blocks [2/1] [U_] - resync=DELAYED - - md1 : active raid1 sdb2[2] sda2[0] - 487717248 blocks [2/1] [U_] - [=>...................] recovery = 9.2% (45229120/487717248) finish=145.2min speed=50771K/sec - -So we removed the bad drive, added it again and you can now see the -recovery status. Watch it carefully. If it fails again, time for a drive -replacement. - -Actually replacing the drive (IBM) -================================== - -Actually replacing the drive is a bit of a todo. If the box is in a RH -owned location, we'll have to file a ticket and get someone access to the -colo. If it is at another location, we may be able to just ship the drive -there and have someone do it on site. Please follow the below steps for -drive replacement. - -Collecting Data ----------------- - -There's a not insignificant amount of data you'll need to place the call. -Please have the following information handy: - -1) The hosts machine type (this is not model number).:: - - # lshal | grep system.product - system.product = 'IBM System x3550 -[7978AC1]-' (string) - - In the above case, the machine type is encoded into [7978AC1]. And is just - the first 4 numbers. So this machine type is 7978. M/T (machine type) is - always 4 digits for IBM boxes. - -2) Machine's serial number:: - - # lshal | grep system.hardware.serial - system.hardware.serial = 'FAAKKEE' (string) - - The above's serial number is 'FAAKKEE' - -3) Drive Stats - - There are two ways to get the drive stats. You can get some of this - information via hal, but for the full complete information you need to - either have someone physically go look at the drive (some of which is in - inventory) or use RaidMan. See "Installing RaidMan" below for more - information on how to install RaidMan. - - Specifically you need: - - - Drive Size (in G) - - Drive Type (SAS or SATA?) - - Drive Model - - Drive Vendor - - To get this information run:: - - # cd /usr/RaidMan/ - # ./arcconf GETCONFIG 1 - -4) The phone number and address of the building where the drive is - currently located. This will go to the RH cage. - - This information is located in the contacts.txt of private git repo on - batcave01 (only available to sysadmin-main people) - - Call IBM - - Call 1-800-426-7378 and follow the directions they give you. You'll need - to use the M/T above to get to the correct rep. They will ask you for the - information above (you wrote it down, right?) - - When they agree to replace the drive, make sure to tell them you need the - shipping number of the drive as well as the name of the tech who will do - the drive replacement. Sometimes the tech will just bring the drive. If - not though, you need to open a ticket with the colo to let them know a - drive is coming. - - Get the package, give access to the tech - - As SOON as you get this information, open a ticket with RH. at - is-ops-tickets redhat.com. Request a ticket ID from RH. If the tech has - any issues getting into the colo, you can give the AT&T ticket request to - the tech to get them in. - - NOTE: this can often take hours. We have 4 hour on site response time from - IBM. This time goes very quickly, sometimes you may need to page out - someone in IS to ensure it gets created quickly. To get this pager - information see contacts.txt in batcave01's private repo (if batcave01 is down - for some reason see the dr copy on backup2.fedoraproject.org:/srv/ - - Prepwork before the tech arrives - - Really the big thing here is to remove the broken drive from the array. In - our earlier example we found /dev/sdb failed. We'll want to remove it from - both arrays: - - # mdadm /dev/md0 --remove /dev/sdb1 - # mdadm /dev/md1 --remove /dev/sdb2 - - Next get the current state of the drives and save it somewhere. See - "Installing RaidMan" for more information if RaidMan is not installed. - - # cd /usr/RaidMan - # ./arcconf GETCONFIG 1 > /tmp/raid1.txt - - Copy /tmp/raid1.txt off to some other device and save it until the tech is - on site. It should contain information about the failed drive. - - Tech on site - - When the tech is on site you may have to give him the rack location. All - of our Mesa servers are in one location, "the same room that the desk is - in". You may have to give him the serial number of the server, or possibly - make it blink. It's either the first rack on the left labeled: "01 2 55" - or "01 2 58". - - Once he's replaced the drive, he'll have you verify. Use the RaidMan tools - to do the following: - - # cd /usr/RaidMan - # ./arcconf RESCAN 1 - # ./arcconf GETCONFIG 1 > /tmp/raid2.txt - # # arcconf CREATE LOGICALDRIVE [Options] - # ./arcconf create 1 LOGICALDRIVE 476790 Simple_volume 0 1 - - First we're going to re-scan the array for the new drive. Then we'll - re-get the configs. Compare /tmp/raid2.txt to /tmp/raid1.txt and verify - the bad drive is fixed and that it has a different serial number. Also - make sure its the correct size. Thank the tech and send him on his way. - The last line there creates a new logical drive from the physical drive. - "Simple_volume" tells it to create a raid0 array of one drive. The size - was pulled out of our initial /tmp/raid1.txt (should match the other - drive). The last two numbers are the Channel and ID of the new drive. - - Rebuild the array - - Now that the disk has been replaced we need to put a partition table on - the new drive and add it to the array: - - * /dev/sdGOOD is the *GOOD* drive - * /dev/sdBAD is the *BAD* drive - - # dd if=/dev/sdGOOD of=/tmp/sda-mbr.bin bs=512 count=1 - # dd if=/tmp/sda-mbr.bin of=/dev/sdBAD - # partprobe - - Next re-add the drives to the array: - - * /dev/sdBAD1 and /dev/sdBAD2 are the partitons on the new drive which - is no longer bad. - - # mdadm /dev/md0 --add /dev/sdBAD1 - # mdadm /dev/md1 --add /dev/sdBAD2 - # cat /proc/mdadm - - This starts rebuilding the arrays, the last line checks the status. - -Actually Replacing the Drive (HP) - - Replacing the drive on the HP's is similar to the IBM's. First you will - need to contact HP, then you will need to open a ticket with Red Hat's - Helpdesk to get into the PHX2 facility. Then you will need to coordinate - with the technician on the colocation's rules for entry and who to - call/talk with. - - Collecting data - - Call HP - - Get the package, give access to the tech - - Prepwork before the tech arrives - - Tech on site - - Rebuild the array - - Now that the disk has been replaced we need to put a partition table on - the new drive and add it to the array: - - * /dev/cciss/c0dGOOD is the *GOOD* drive. The HP utilities will have a - code like 1I:1:1 - * /dev/cciss/c0dBAD is the *BAD* drive. The HP utilities will have a - code like 2I:1:1 - - First we need to create the logical drive on the system. - - # hpacucli controller serialnumber=P61630H9SVU4JF create type=ld sectors=63 drives=2I:1:1 raid=0 - - # dd if=/dev/ccis/c0dGOOD of=/tmp/sda-mbr.bin bs=512 count=1 - # dd if=/tmp/sda-mbr.bin of=/dev/ccis/c0dBAD - # partprobe - - Next re-add the drives to the array: - - * /dev/sdBAD1 and /dev/sdBAD2 are the partitons on the new drive which - is no longer bad. - - # mdadm /dev/md0 --add /dev/sdBAD1 - # mdadm /dev/md1 --add /dev/sdBAD2 - # cat /proc/mdadm - - This starts rebuilding the arrays, the last line checks the status. - -Installing RaidMan (IBM Only) - - Unfortunately there is no feasible alternative to managing IBM Raid Arrays - without causing downtime. You can get and do this via the pre-POST - interface. This requires downtime, and if the first drive is the failed - drive, may result in a non-booting system. So for now RaidMan it is until - we can figure out how to get rid of the raid controllers in these boxes - completely. - - yum -y install compat-libstdc++-33.i686 - rpm -ihv https://infrastructure.fedoraproject.org/rhel/RaidMan/RaidMan-9.00.i386.rpm - - To verify installation has completed successfully: - - # cd /usr/RaidMan/ - # ./arcconf GETCONFIG 1 - - This should print the current configuration of the raid controller and its - logical drives. - diff --git a/docs/sysadmin-guide/sops/old/guestmigrate.rst b/docs/sysadmin-guide/sops/old/guestmigrate.rst new file mode 100644 index 0000000..4df35ad --- /dev/null +++ b/docs/sysadmin-guide/sops/old/guestmigrate.rst @@ -0,0 +1,90 @@ +.. title: Guest Migration SOP +.. slug: infra-guest-migration +.. date: 2011-10-07 +.. taxonomy: Contributors/Infrastructure + +============================== +Guest migration between hosts. +============================== + +Move guests from one host to another. + +Contact Information +=================== + +Owner + Fedora Infrastructure Team + +Contact + #fedora-admin, sysadmin-main + +Location + PHX, Tummy, ibiblio, Telia, OSUOSL + +Servers + All xen servers, kvm/libvirt servers. + +Purpose + Migrate guests + +How to do it +============ + +1. Schedule outage time if any. This will need to be long enough to copy + the data from one host to another, so will depend on guest disk + size. + +2. Turn off monitoring in nagios + +3. On new host create disk space for server:: + + lvcreate -n app03 -L 32G vg_guests00 + +4. prepare old guest for migration: + a) if system is xen, install a regular kernel + b) look for entries for xenblk and hvc0 in /etc files + +5. Shutdown the guest. + +6. :: + + virsh dumpxml guestname > guest.xml + +7. Copy guest.xml to the new machine. You will need to make various + edits depending on if the system was originally xen or such. I + normally need to compare an existing xml on the target system and the + one we dumped out to make up the differences. + +8. Define the guest on the new machine: 'virsh define guest.xml'. + Depending on the changes in the xml this may not work and you will + need to make many manual changes plus copy the guest.xml to + ``/etc/libvirtd/qemu`` and do a ``/sbin/service libvirtd restart`` + +9. Insert iptables rule for nc transfer:: + + iptables -I INPUT 14 -s -m tcp -p tcp --dport 11111 -j ACCEPT + +10. On the destination host: + + - RHEL-5:: + + nc -l -p 11111 | dd of=/dev/mapper/ + + - RHEL-6:: + + nc -l 11111 | dd of=/dev/mapper/ + +11. On the source host:: + + dd if=/dev/mapper/guest-partition | nc desthost 11111 + + Wait for the copy to finish. You can do the following to track how + far something has gone by finding the dd pid and then sending a + 'kill -USR1' to it. + +11. start the guest on the new host:: + + ``virsh start guest`` + +12. On the source host, rename storage and undefine guest so it's not started. + diff --git a/docs/sysadmin-guide/sops/old/ibm-drive-replacement.rst b/docs/sysadmin-guide/sops/old/ibm-drive-replacement.rst new file mode 100644 index 0000000..afafe0c --- /dev/null +++ b/docs/sysadmin-guide/sops/old/ibm-drive-replacement.rst @@ -0,0 +1,342 @@ +.. title: Drive Replacement SOP +.. slug: infra-drive-replacement +.. date: 2012-07-13 +.. taxonomy: Contributors/Infrastructure + +==================================== +Drive Replacement Infrastructure SOP +==================================== + +At present this SOP only works for the X series IBM servers. + +We have multiple machines with lots of different drives in them. For the +most part now though, we are trying to standardise on IBM X series +servers. At present I've not figured out how to disable onboard raid, as a +result of this many of our servers have two raid 0 arrays then we do +software raid on this. + +The system xen11 is currently an HP ProLiant DL180 G5 with its own +interesting RAID system (using Compaq Smart Array ccis). Like the IBM X +series each drive is considered a single RAID-0 instance which is then +accessed through a logical drive. + +Contents +======== + +1. Contact Information +2. Verify the drive is dead + + 1. Re-adding a drive (poor man's fix) + +3. Actually replacing the drive (IBM) + + 1. Collecting Data + 2. Call IBM + 3. Get the package, give access to the tech + 4. Prepwork before the tech arrives + 5. Tech on site + 6. Rebuild the array + +4. Actually Replacing the Drive (HP) + + 1. Collecting data + 2. Call HP + 3. Get the package, give access to the tech + 4. Prepwork before the tech arrives + 5. Tech on site + 6. Rebuild the array + +5. Installing RaidMan (IBM Only) + +Database - DriveReplacement + +Contact Information +=================== + +Owner + Fedora Infrastructure Team +Contact + #fedora-admin, sysadmin-main +Location + All +Servers + All +Purpose + Steps for drive replacement. + +Verify the drive is dead +======================== + +:: + + $ cat /proc/mdadm + Personalities : [raid1] + md0 : active raid1 sdb1[1] sda1[0] + 513984 blocks [2/2] [UU] + + md1 : active raid1 sdb2[2](F) sda2[0] + 487717248 blocks [2/1] [U_] + +This indicates that md1 is in a degraded state and that /dev/sdb2 is the +failed drive. Notice that /dev/sdb1 (same physical drive as /dev/sdb2) is +not failed. /dev/md0 (not yet degraded) is showing a good state. This is +because /dev/md0 is /boot. If you run:: + + touch /boot/t + sync + rm /boot/t + +That should make /dev/md0 notice that its drive is also failed. If it does +not fail, its possible the drive is fine and that some blip happened that +caused it to get flagged as dead. It is also worthwhile to log in to +xenX-mgmt to determine if the RSAII adapter has noticed the drive is dead. + +If you think the drive just had a blip and is fine, see "Re-adding" below + +Re-adding a drive (poor man's fix) +----------------------------------- + +Basically what we're doing here is making sure the drive is, infact, dead. +Obviously you don't want to do this more then once on a drive, if it +continues to fail. Replace it. + +:: + + # cat /proc/mdadm + Personalities : [raid1] + md0 : active raid1 sdb1[1] sda1[0] + 513984 blocks [2/2] [UU] + + md1 : active raid1 sdb2[2](F) sda2[0] + 487717248 blocks [2/1] [U_] + # mdadm /dev/md1 --remove /dev/sdb2 + # mdadm /dev/md1 --add /dev/sdb2 + # cat /proc/mdstat + md0 : active raid1 sdb1[1] sda1[0] + 513984 blocks [2/1] [U_] + resync=DELAYED + + md1 : active raid1 sdb2[2] sda2[0] + 487717248 blocks [2/1] [U_] + [=>...................] recovery = 9.2% (45229120/487717248) finish=145.2min speed=50771K/sec + +So we removed the bad drive, added it again and you can now see the +recovery status. Watch it carefully. If it fails again, time for a drive +replacement. + +Actually replacing the drive (IBM) +================================== + +Actually replacing the drive is a bit of a todo. If the box is in a RH +owned location, we'll have to file a ticket and get someone access to the +colo. If it is at another location, we may be able to just ship the drive +there and have someone do it on site. Please follow the below steps for +drive replacement. + +Collecting Data +---------------- + +There's a not insignificant amount of data you'll need to place the call. +Please have the following information handy: + +1) The hosts machine type (this is not model number).:: + + # lshal | grep system.product + system.product = 'IBM System x3550 -[7978AC1]-' (string) + + In the above case, the machine type is encoded into [7978AC1]. And is just + the first 4 numbers. So this machine type is 7978. M/T (machine type) is + always 4 digits for IBM boxes. + +2) Machine's serial number:: + + # lshal | grep system.hardware.serial + system.hardware.serial = 'FAAKKEE' (string) + + The above's serial number is 'FAAKKEE' + +3) Drive Stats + + There are two ways to get the drive stats. You can get some of this + information via hal, but for the full complete information you need to + either have someone physically go look at the drive (some of which is in + inventory) or use RaidMan. See "Installing RaidMan" below for more + information on how to install RaidMan. + + Specifically you need: + + - Drive Size (in G) + - Drive Type (SAS or SATA?) + - Drive Model + - Drive Vendor + + To get this information run:: + + # cd /usr/RaidMan/ + # ./arcconf GETCONFIG 1 + +4) The phone number and address of the building where the drive is + currently located. This will go to the RH cage. + + This information is located in the contacts.txt of private git repo on + batcave01 (only available to sysadmin-main people) + + Call IBM + + Call 1-800-426-7378 and follow the directions they give you. You'll need + to use the M/T above to get to the correct rep. They will ask you for the + information above (you wrote it down, right?) + + When they agree to replace the drive, make sure to tell them you need the + shipping number of the drive as well as the name of the tech who will do + the drive replacement. Sometimes the tech will just bring the drive. If + not though, you need to open a ticket with the colo to let them know a + drive is coming. + + Get the package, give access to the tech + + As SOON as you get this information, open a ticket with RH. at + is-ops-tickets redhat.com. Request a ticket ID from RH. If the tech has + any issues getting into the colo, you can give the AT&T ticket request to + the tech to get them in. + + NOTE: this can often take hours. We have 4 hour on site response time from + IBM. This time goes very quickly, sometimes you may need to page out + someone in IS to ensure it gets created quickly. To get this pager + information see contacts.txt in batcave01's private repo (if batcave01 is down + for some reason see the dr copy on backup2.fedoraproject.org:/srv/ + + Prepwork before the tech arrives + + Really the big thing here is to remove the broken drive from the array. In + our earlier example we found /dev/sdb failed. We'll want to remove it from + both arrays: + + # mdadm /dev/md0 --remove /dev/sdb1 + # mdadm /dev/md1 --remove /dev/sdb2 + + Next get the current state of the drives and save it somewhere. See + "Installing RaidMan" for more information if RaidMan is not installed. + + # cd /usr/RaidMan + # ./arcconf GETCONFIG 1 > /tmp/raid1.txt + + Copy /tmp/raid1.txt off to some other device and save it until the tech is + on site. It should contain information about the failed drive. + + Tech on site + + When the tech is on site you may have to give him the rack location. All + of our Mesa servers are in one location, "the same room that the desk is + in". You may have to give him the serial number of the server, or possibly + make it blink. It's either the first rack on the left labeled: "01 2 55" + or "01 2 58". + + Once he's replaced the drive, he'll have you verify. Use the RaidMan tools + to do the following: + + # cd /usr/RaidMan + # ./arcconf RESCAN 1 + # ./arcconf GETCONFIG 1 > /tmp/raid2.txt + # # arcconf CREATE LOGICALDRIVE [Options] + # ./arcconf create 1 LOGICALDRIVE 476790 Simple_volume 0 1 + + First we're going to re-scan the array for the new drive. Then we'll + re-get the configs. Compare /tmp/raid2.txt to /tmp/raid1.txt and verify + the bad drive is fixed and that it has a different serial number. Also + make sure its the correct size. Thank the tech and send him on his way. + The last line there creates a new logical drive from the physical drive. + "Simple_volume" tells it to create a raid0 array of one drive. The size + was pulled out of our initial /tmp/raid1.txt (should match the other + drive). The last two numbers are the Channel and ID of the new drive. + + Rebuild the array + + Now that the disk has been replaced we need to put a partition table on + the new drive and add it to the array: + + * /dev/sdGOOD is the *GOOD* drive + * /dev/sdBAD is the *BAD* drive + + # dd if=/dev/sdGOOD of=/tmp/sda-mbr.bin bs=512 count=1 + # dd if=/tmp/sda-mbr.bin of=/dev/sdBAD + # partprobe + + Next re-add the drives to the array: + + * /dev/sdBAD1 and /dev/sdBAD2 are the partitons on the new drive which + is no longer bad. + + # mdadm /dev/md0 --add /dev/sdBAD1 + # mdadm /dev/md1 --add /dev/sdBAD2 + # cat /proc/mdadm + + This starts rebuilding the arrays, the last line checks the status. + +Actually Replacing the Drive (HP) + + Replacing the drive on the HP's is similar to the IBM's. First you will + need to contact HP, then you will need to open a ticket with Red Hat's + Helpdesk to get into the PHX2 facility. Then you will need to coordinate + with the technician on the colocation's rules for entry and who to + call/talk with. + + Collecting data + + Call HP + + Get the package, give access to the tech + + Prepwork before the tech arrives + + Tech on site + + Rebuild the array + + Now that the disk has been replaced we need to put a partition table on + the new drive and add it to the array: + + * /dev/cciss/c0dGOOD is the *GOOD* drive. The HP utilities will have a + code like 1I:1:1 + * /dev/cciss/c0dBAD is the *BAD* drive. The HP utilities will have a + code like 2I:1:1 + + First we need to create the logical drive on the system. + + # hpacucli controller serialnumber=P61630H9SVU4JF create type=ld sectors=63 drives=2I:1:1 raid=0 + + # dd if=/dev/ccis/c0dGOOD of=/tmp/sda-mbr.bin bs=512 count=1 + # dd if=/tmp/sda-mbr.bin of=/dev/ccis/c0dBAD + # partprobe + + Next re-add the drives to the array: + + * /dev/sdBAD1 and /dev/sdBAD2 are the partitons on the new drive which + is no longer bad. + + # mdadm /dev/md0 --add /dev/sdBAD1 + # mdadm /dev/md1 --add /dev/sdBAD2 + # cat /proc/mdadm + + This starts rebuilding the arrays, the last line checks the status. + +Installing RaidMan (IBM Only) + + Unfortunately there is no feasible alternative to managing IBM Raid Arrays + without causing downtime. You can get and do this via the pre-POST + interface. This requires downtime, and if the first drive is the failed + drive, may result in a non-booting system. So for now RaidMan it is until + we can figure out how to get rid of the raid controllers in these boxes + completely. + + yum -y install compat-libstdc++-33.i686 + rpm -ihv https://infrastructure.fedoraproject.org/rhel/RaidMan/RaidMan-9.00.i386.rpm + + To verify installation has completed successfully: + + # cd /usr/RaidMan/ + # ./arcconf GETCONFIG 1 + + This should print the current configuration of the raid controller and its + logical drives. + diff --git a/docs/sysadmin-guide/sops/virt-notes.rst b/docs/sysadmin-guide/sops/virt-notes.rst index 9ade5f2..00d1638 100644 --- a/docs/sysadmin-guide/sops/virt-notes.rst +++ b/docs/sysadmin-guide/sops/virt-notes.rst @@ -19,17 +19,25 @@ multiple steps: it is not a big deal. Right now, this also means modifying the ``/etc/ssh/sshd_config`` to ``permitroot without-password``. -2. setup storage on the destination end to match the source storage. - If the path to the storage is not the same on both systems - (ie: not the same path into ``/dev/Guests00/myguest``) then take a copy - of the guest xml file from ``/etc/libvirt/qemu`` and modify it so it has - the right path. If you need to do this you need to add ``--xml thisfile.xml`` - to the arguments below AFTER the word 'migrate' +2. Determine whatever changes need to be made to the guest. This can + be the number of cpus, the amount of memory, or the disk location + as this may not be standard on the current server. + +3. Make a dump of the current virtual guest using the virsh + command. Use ``virsh dumpxml --migratable guestname`` and then edit + any changes in disk layout, memory and cpu needed. + +4. setup storage on the destination end to match the source + storage. ``lvs`` will give the amount of disk space. Due to some + vaguries on disk sizes, it is always better to round up so if the + original server says it is using 19.85 GB, make the next image 20 + GB. On the new server, use ``lvcreate -L+${SIZE}GB -n ${FQDN} vg_guests`` + 3. as root on source location:: - virsh -c qemu:///system migrate --p2p --tunnelled \ - --copy-storage-all myguest \ + virsh -c qemu:///system migrate --xml ${XML_FILE_FROM_3} \ + --copy-storage-all ${GUESTNAME} \ qemu+ssh://root@destinationvirthost/system This should start the migration process and it will output absolutely @@ -37,17 +45,87 @@ multiple steps: go look in /var/log/libvirt/qemu/myguest.log (tail -f will show you the progress results as a percentage completed) - .. note:: - --p2p and --tunnelled are so it goes direct from one host to the other - but uses ssh. - 4. Once the migration is complete you will probably need to run this on the new virthost:: - virsh dumpxml myguest > /etc/libvirt/qemu/myguest.xml - virsh destroy myguest - virsh define /etc/libvirt/qemu/myguest.xml - virsh autostart myguest - virsh start myguest + scp ${XML_FILE_FROM_3} root@destinationvirthost: + + ssh root@destinationvirthost + virsh define ${XML_FILE_FROM_3} + virsh autostart ${GUESTNAME} + +5. Edit ansible host_vars of the guest and make sure that the + associated values are correct:: + + volgroup: /dev/vg_guests + vmhost: virthost??.phx2.fedoraproject.org + +6. Run the noc.yml ansible playbook to update nagios. + +This should work for most systems. However in some cases, the virtual +servers on either side may have too much activity to 'settle' down +enough for a migration to work. In other cases the guest may be on a +disk like ISCSI which may not allow for direct migration. In this case +you will need to use a more direct movement. + +1. Schedule outage time if any. This will need to be long enough to copy + the data from one host to another, so will depend on guest disk + size. + +2. Turn off monitoring in nagios + +3. setup an unpassworded root ssh key to allow communication between + the two virthosts as root. This is only temporary, so, while scary + it is not a big deal. Right now, this also means modifying + the ``/etc/ssh/sshd_config`` to ``permitroot without-password``. + +4. Determine whatever changes need to be made to the guest. This can + be the number of cpus, the amount of memory, or the disk location + as this may not be standard on the current server. + +5. Make a dump of the current virtual guest using the virsh + command. Use ``virsh dumpxml --migratable guestname`` and then edit + any changes in disk layout, memory and cpu needed. + +6. setup storage on the destination end to match the source + storage. ``lvs`` will give the amount of disk space. Due to some + vaguries on disk sizes, it is always better to round up so if the + original server says it is using 19.85 GB, make the next image 20 + GB. On the new server, use ``lvcreate -L+${SIZE}GB -n ${FQDN} vg_guests`` + +7. Shutdown the guest. + +8. Insert iptables rule for nc transfer:: + + iptables -I INPUT 14 -s -m tcp -p tcp --dport 11111 -j ACCEPT + +9. On the destination host: + + - RHEL-7:: + + nc -l 11111 | dd of=/dev// + +10. On the source host:: + + dd if=/dev// | nc desthost 11111 + + Wait for the copy to finish. You can do the following to track how + far something has gone by finding the dd pid and then sending a + 'kill -USR1' to it. + +11. Once the migration is complete you will probably need to run this + on the new virthost:: + + scp ${XML_FILE_FROM_3} root@destinationvirthost: + + ssh root@destinationvirthost + virsh define ${XML_FILE_FROM_3} + virsh autostart ${GUESTNAME} + +12. Edit ansible host_vars of the guest and make sure that the + associated values are correct:: + volgroup: /dev/vg_guests + vmhost: virthost??.phx2.fedoraproject.org +13. Run the noc.yml ansible playbook to update nagios.