Slides from Senior Software Architect Laurence Liss' Probo.ci presentation to Drupal 4 Gov's DevOps 1/2 day event, held on April 20, 2017.

1. Probo.CI

2. zivtech.com, probo.ci
Laurence Liss
Senior Software Architect

4. Devops is…

5. testing, deployment, monitoring,
security, backups, feedback, approval…
It depends who you ask.

6. Devops is an idea.
Close the gap between software and the
systems that run it.
Create a culture of mutual ownership.
Involve more stakeholders in the process.

7. Some processes are
easily automated.
But not all.

8. Perfect automated testing is
nearly impossible.
Most software is too complex

9. Code Review
Are you doing it?

10. Think about software as science.

11. - repeatable
- peer reviewed
- independently verifiable

12. Tools such as git (and services
such as bitbucket and github)
make this easier to do.

14. Create and assign ticket
Code
Commit
Review
Workflows - One pool of
code
Release

15. Workflows - Web apps
Database
Code
Staging
Database
Code
Production
Database
Code
Dev
Database
Code
Local

16. Create and assign issue
Code
Commit to a feature branch
Code review the branch before merging
Workflows - Using git

17. Our Old Workflow

18. Our woes

19. Lead assigns tickets

20. Devs are happy to help

21. Dev thinks and codes

22. Project Manager checks in

23. Dev promises it's all done

24. PM asks for a review

25. Lead checks out the branch

26. Lead finds problems

27. Devs hear the grumbling

28. *Grumbling*

29. PM fears the deadline

30. Dev regrets the mistake

31. PM hopes it's right now

32. Lead sees it finally works

33. Lead merges the fix

34. But the client
hasn't reviewed it!

35. Clients want some fixes

36. a277cf0 Ticket #1, adding an image content type.
4483681 Ticket #3, adding view for the news section.
a65c40e Ticket #1, creating the homepage slider.
1a1df95 Ticket #4, making name required on registration.
0dbe2e6 Ticket #1, updating the image style.
24b55b6 Ticket #4, adding middle initial field.
0dbe2e6 Ticket #5, adding login rule for redirect.
But it was all merged to get it to the dev
environment

37. a277cf0 Ticket #1, adding an image content type.
4483681 Ticket #3, adding view for the news section.
a65c40e Ticket #1, creating the homepage slider.
1a1df95 Ticket #4, making name required on registration.
0dbe2e6 Ticket #1, updating the image style.
24b55b6 Ticket #4, adding middle initial field.
0dbe2e6 Ticket #5, adding login rule for redirect.
The client wants to deploy only one feature
they need and are happy with

38. Hey Jason, just deploy some of
that

39. a277cf0 Ticket #1, adding an image content type.
4483681 Ticket #3, adding view for the news section.
a65c40e Ticket #1, creating the homepage slider.
1a1df95 Ticket #4, making name required on registration.
0dbe2e6 Ticket #1, updating the image style.
24b55b6 Ticket #4, adding middle initial field.
0dbe2e6 Ticket #5, adding login rule for redirect.
`git cherry-pick`, I guess?

40. Meet Probo.CI

41. - An Open Source Continuous Integration tool
- A continuous collaboration tool
- A Software as a Service platform for running tests
Probo.CI is…

42. Our new workflow

43. Lead assigns tickets

44. Devs are happy to help

45. Dev thinks and codes

46. Dev opens a pull request

47. Project Manager checks it

48. PM sees it is right

49. Client sees that it is right

50. Lead merges and deploys it

51. Projects run smoothly

52. There is relief

53. And much rejoicing

54. - The in-progress application has a mix of things
that are and are not yet vetted by clients
- Testing a feature branch is complex
- Devs waste time switching tasks.
- It is difficult to share in-progress features.
- Useful test content gets lost before feedback comes in.
Without Probo.CI

55. With Probo.CI
- In-progress application has only work approved.
by the client and is always ready for deployment.
- Every team member and client can see each feature.
- Reviewing is easy and can be done by non developers.
- Test content needed for review doesn’t get wiped.
- Deployment steps have always been verified.

57. Github & Bitbucket Integration

59. Runs fat containers
- A node.js process manager runs child
processes
- Multiplexes the log output
- Allows us to easily treat an environment as a
single unit

60. Github Handler
Loom
Container Manager
Docker
Proxy
Open Source

61. Nginx
- Terminate SSL
- Routes to the appropriate microservice

62. Github Handler
- Responsible for receiving GitHub Webhook calls
- Responsible for sending status and deployment
updates back to Github
- Retrieves .probo.yaml configuration

63. Container manager
- Drives docker
- Starts and stops containers
- Runs build steps
- Sends messages to loom
- Reports on containers running on the system

64. Loom
- Receives any kind of arbitrary stream and stores
it with metadata
- Supports tailing these streams
- Supports stream multiplexing

65. Web Proxy
- Fetches the container address and port
- Proxies the web request to the proper container
- Supports Drupal’s domain access
- Supports Drupal multi-site setups

66. Asset Receiver
- Receives uploads and puts files in a bucket
- Supports access tokens
- Stores, compresses, and encrypts files
- Allows them to be downloaded

67. Github Handler
Loom
Container Manager
Docker
Proxy
Open Source

68. Proxy
Github Handler
Loom
Container Manager
Docker
Software as a Service
web (UI) coordinator

69. Coordinator
- Proprietary part of SaaS service
- Only responsible for enforcing resource restrictions
- Enables massive deployments with multiple Container
Managers

70. To the Demo!

71. probo.ci
app.probo.ci

72. Thank you!