Setup Service Ownership and Definition
Closed this issue · 5 comments
Setup Service Ownership and Definition
TL;DR
Video explanation: https://videobin.shopify.io/v/LNEwPb
Services must have their ownership defined and service type and subtype configured under the Service Details section in Services DB. See What is a Service? section in our documentation for more context.
Please verify that all the requirements below are met:
An owner is defined
You can assign ownership by visiting the Services DB overview page of your service. It's preferable to assign the ownership to your direct team, but you can also assign to individuals if it makes more sense.
The service type and subtype are set
This guide can help determine a service type. In order to change the service type, click the Edit button beside Classification in the Service Details section. Avoid Other and Unknown as much as you can. If none of the subtypes fit your service, check if there is a tag that better categorizes your service or propose a new tag.
If you select Other as your service type, this action item will not be considered complete unless you have at least one tag applied to your service.
A slack channel is set
If your service has production platform support enabled, you are required to have a Slack channel set for your service.
Slack is where communication happens. Making sure we can ping you when there's a problem is essential. You can configure your Slack channel on the service overview page.
Exceptions
- If this service is part of the Logistics org, then it must have a
logisticstag. There is no requirement for a Slack channel for services in the Logistics org. - If this service is part of
infra-central, then it must have aninfra-centraltag. There is no requirement for an owner to be set forinfra-centralrepositories - in the future ownership will be read from infra-central.
Why is this being asked?
Services are the Services DB domain concept for any business activity backed by a repository. This includes web apps, libraries, documentation sites or even repositories used for GitHub issue tracking.
Every repository must have an owner tracked via the corresponding service for its business activity.
This action item does apply to you
Defining ownership is important so we can reach out to service owners when there is a problem with their services. It also helps us understand the reason why that service exists.
Service categorization (type, subtype, tags, etc) will help us identify groups of services more easily when defining new action items/health check, for example. It also helps SME teams to find services of their interest when defining policies across Shopify.
What will happen if it doesn't get done within the expected timeframe?
There is a risk that your service will be discontinued if we cannot identify the ownership and categorize it properly. This is necessary to mitigate security risks and reduce the operational cost.
When does it need to get done?
At the latest, this should be done before 2023-03-20.
This doesn't apply to my service. What do I do?
This action item is mandatory for all services. If you still think it does not apply to your service, please reach out to #help-eng-infrastructure.
Detailed description
I have questions/concerns about this
Please contact the Production Excellence team using #help-eng-infrastructure.
Your service: ruvy
For more information on setting service types, please see this guideline
This action item is now overdue and still has no owners assigned.
Based on recent contributions and/or the CODEOWNERS file, these users/teams are the most likely to have context on the ownership of this Service:
@davejcameron
@saulecabrera
Please note that failing to fill in Service Ownership information may lead to the deletion of this service
The action item description has been updated. Please review the changes.
@jianghong Not sure if we want to setup services DB for this repo given that we're going to open source it soon-ish?
We already have one for ruvy created, so I went ahead and assigned our team as owners https://services.shopify.io/services/ruvy/overview