1. DataFlow Meeting Summary & DBA Advisory Board
ALMA Integrated Computing Team Coordination & Planning Meeting #5 Santiago, 1-3 December 2011
DataFlow Meeting Summary & DBA Advisory Board
José Parra & Tsuyoshi Kobayashi

2. Dataflow Workshop 2015, CV
Summary: Technical Discussions – Operational focus
4 days
21 persons
32 topics
Infrastructure (4)
Network (2)
Databases (11)
Archive (7)
Deployment (3)
Monitoring (2)
System Administration (2)
Communications (1)

3. What is DBA Advisory Board?
A combined effort between developers and Database Administrators to share and seek expertise between two technical groups.
ICT-CPM5, 1-3 December 2015

4. What is DBA Advisory Board?
TEAM WORK !!!
ICT-CPM5, 1-3 December 2015

5. Benefits Performance improvements DB Normalization
All dev groups aware of DB-CHANGES
Controlled DB space growth
Visible DB Logical/Physical designs
Support & collaboration
This alliance will let all see the BIG PICTURE!
ICT-CPM5, 1-3 December 2015

6. Earlier discussions
ICT-CPM5, 1-3 December 2015

7. How to engage DBAs? First approach (discussed at Dataflow Workshop):
Developer create an ICT ticket with Oracle component.
DBAs are automatically added as watchers.
Coordinator assign the tickets.
DRY RUN:
3 MONTHS (Until mid-February 2016)
Currently evaluating …
Slack – “#channel”, cloud, free & paid service
Hipchat by Atlassian [JIRA company] – on premise
ICT-CPM5, 1-3 December 2015

8. When to engage DBAs? When you first start thinking in Oracle
(Research > Concept > Design > Implementation > Maintenance > Planning)
ICT-CPM5, 1-3 December 2015

9. Coordinator role
Responsible for checking all ICT Oracle tickets. Sample
Trigger the technical discussion (i.e.: chat, mail, VC, etc.)
Assign the tickets.
Follow up.
DRY RUN:
COORDINATOR: TK; Backup: JOSE
ICT-CPM5, 1-3 December 2015

10. Feedback already collected … (before end of dry-run)
Chat is possible, but online discussions will be difficult due to timezone differences (i.e.: only 1-2 DBAs at the time).
Not only Oracle ICT tickets require DBA support. Some tickets can easily be overlooked.
ICT tickets are not used exclusively for DBAs.
ICT tickets will generate way too much notification for DBAs.
ICT-CPM5, 1-3 December 2015

11. How to move forward? … still dry-run
Create an APO ticket when DBA support is required.
ICT linked with APO tickets for technical reference. (TBD with Erik)
Coordinator tracks APO tickets instead.
APO tickets assigned within 48 hrs.
Daily scrum meeting (sprint planning)
Test hipchat integration with JIRA & slack
Who creates APO tickets?
Developers, Astronomers, Data Analysts, Telescope Operators, Archive Specialists, SACM, Engineering, etc. EVERYONE doing queries to the Production database.
APO Tickets: Archive Pipeline Operations > ORACLE > DBA Advisory Board

12. Conclusions http://ictjira.alma.cl/browse/ICT-6415
To document the workflow to engage DBAs in the design phase of DB changes.
Assignee:  Ruben Soto
ICT-CPM5, 1-3 December 2015

13. Thank you!
ICT-CPM5, 1-3 December 2015