Skip to end of banner
Go to start of banner

Rancher support duties

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Communication

#rancher-support

Please avoid direct communication via personal messages.

Engage people to use official Slack communication channel.


Ask to create jira in RANCHER project for tasks that require more than 1 hour.

Duties schedule

Sprint

Person

Availability time

Backup Person

185

Renat Safiulin

10 AM - 8 PM Uzbekistan

12 AM - 10 AM EST


186

Arsen Atoyan

10 AM - 7 PM Armenia

1 AM - 10 AM EST


187

oleksandr_haimanov

10 AM - 7 PM Ukraine

3 AM - 12 PM EST


188

Eldiiar Duishenaliev

12 PM - 9 PM Kyrgyzstan

1 AM - 10 AM EST

oleksandr_haimanov

189

Dmytro

9 AM - 6 PM Ukraine

2 AM - 11 AM EST


190

Vasyl Avramenko

9 AM - 6 PM Ukraine

2 AM - 11 AM EST


191

Yaroslav Ishchenko

9 AM - 6 PM Ukraine

2 AM - 11 AM EST


192

Arsen Atoyan

10 AM - 7 PM Armenia

1 AM - 10 AM EST


193

Eldiiar Duishenaliev

12 PM - 9 PM Kyrgyzstan

1 AM - 10 AM EST


194

oleksandr_haimanov

9 AM - 6 PM Ukraine

2 AM - 11 AM EST


195

Dmytro

10 AM - 7 PM Ukraine

3 AM - 12 PM EST


196

Vasyl Avramenko

9 AM - 6 PM Ukraine

2 AM - 11 AM EST


197

Yaroslav Ishchenko

9 AM - 6 PM Ukraine

2 AM - 11 AM EST

198

Arsen Atoyan

10 AM - 7 PM Armenia

1 AM - 10 AM EST

199

Eldiiar Duishenaliev

12 PM - 9 PM Kyrgyzstan

1 AM - 10 AM EST

SHIFT DUTIES

1.During working hours answer the request within 1hr (related to the situation when a person on duty might be absent from his desk for an ~1hr because of lunch, project call in progress, etc. and cannot see the request)

2. Check all scheduled jobs status: Map jobs = [            
    Karate: https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/
    Cypress: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioScheduledTesting/job/runNightlyCypressTests/
    MamagePods: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioNamespaceTools/job/managePods/
                createDailySnapshotECS: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioNamespaceTools/job/createDailySnapshotECS/
    ] → Jenkins pipelines views
2. Monitor & respond to All incoming requests: Slack & Teams
3. Prepare a list of created tasks during shift day
4. Announce previously created tasks list on a daily standaUp
5. Rancher: check at least twice a day the statuses of environments
6. Monitor MSTeams chats: Map chats = [
    chat_name_1: 'FOLIO - cypress tests in CI'
    chat_name_2: 'Sprint testing env questions'
    ]
7. AWS infra: Kafka, RDS, OpenSearch (check statuses: CPU, RAM, etc.) at the beginning of shift working day
8. Jenkins: check slaves at the beginning of the shift working day for any technical issues: Status, Free space, availability | us-east-1 AWS region
9. Create a Jira ticket for any implementation incoming requests & share its' number with the reporter (if any)
10. ReportPortal: review the last scheduled tests results, analyze and perform initial investigation & inform the responsible team about the issue
11. Update sprint testing environment | 1st priority item, when shift started! | FISRT ITEM IN THE ROW!!! → (After Backend was updated, please build new UIs for the following tenants: fs09000000, cs00000int(Consortia enabled), fs09000003 via this pipeline: ui-bundle-deploy



  • No labels