This document summarizes the author's work on infrastructure projects at Ericsson including Pharos, Octopus, and Releng. It describes the early challenges of integrating different upstream projects and tools. It then discusses progress made in automating continuous integration and deployment with Jenkins, and using hardware resources from Ericsson Montreal and Linux Foundation PODs. Key milestones achieved include the Arno and Brahmaputra releases, which integrated an increasing number of projects and combinations through improved automation and CI processes. The author encourages more involvement to further develop these practices for the benefit of all.

1. Diary of an Infra Guy
Fatih Degirmenci
Master Software Developer, Ericsson

2. Infrastructure Projects
• Pharos
– Community Test Infrastructure
• Octopus
– Continuous Integration
• Releng
– Automation, Tooling, Software Development Infrastructure
11/11/2015 Diary of an Infra Guy 2

3. Towards Arno

4. Early Days
• Different views
• Many upstream projects
• Good ideas but still quite complicated
11/11/2015 Diary of an Infra Guy 4

5. Tools
11/11/2015 Diary of an Infra Guy 5

6. Automation and Continuous Integration
• Jenkins jobs were already there!
• Jobs were doing stuff…
• Late to the party?
11/11/2015 Diary of an Infra Guy 6

7. Hardware Resources
11/11/2015 Diary of an Infra Guy 7

8. Arno

9. How did we start?
11/11/2015 Diary of an Infra Guy 9

10. What did we do in Prague?
• Discussed how to bring something up and quick
• Some projects took the lead
– BGS
– Octopus
– Functest
– Pharos
11/11/2015 Diary of an Infra Guy 10

11. CI First Steps
• CI put requirements on BGS
• Do the upstream integration yourselves
• Provide simple scripts for us
11/11/2015 Diary of an Infra Guy 11

12. Bringing up the CI
• Got HW resources
– Server from Ericsson Montreal Lab => builds
– LF PODs became operational => bare metal deployment
• Created real Jenkins jobs
• Integrated testing into CI using Functest scripts
– Tempest/Rally
– Robot
– vPing
11/11/2015 Diary of an Infra Guy 12

13. Hardware Resources
11/11/2015 Diary of an Infra Guy 13

14. CI Setup for Arno
• Project CI
– Project specific verify, merge, and daily jobs
– Project CI != part of OPNFV Platform CI
• OPNFV Platform CI
– Jobs from different projects tied together to do build,
installation, and testing, creating CI loops
11/11/2015 Diary of an Infra Guy 14

15. What else?
• Using OpenStack Infra Utilities, JJB
• We also “Swim Upstream”
• Fixed upstream first!
11/11/2015 Diary of an Infra Guy 15

16. Arno
• R1 released on June 4th
• SR1 released on October 1st
• 5 projects participated in Arno
– BGS
– Functest
– Octopus
– Pharos
– Opnfvdocs
11/11/2015 Diary of an Infra Guy 16

17. Beyond Arno

18. Brahmaputra
• 38 projects
• Many different combinations
• High demand on automation and CI
• More labs becoming online
11/11/2015 Diary of an Infra Guy 18

19. Hardware Resources
11/11/2015 Diary of an Infra Guy 19

20. Automation and CI Next Steps
• Increased automation & CI coverage
• Produce & integrate artifacts
• Automate resource/lab handling
• Continue working upstream
11/11/2015 Diary of an Infra Guy 20

21. What else?
• Work closer with upstream projects
– OpenDaylight
– OpenStack
• Involve more OPNFV folks in automation/CI
– About 10 contributors for Arno
– Now 20+ contributors and still increasing
11/11/2015 Diary of an Infra Guy 21

22. We need you!
• CI is a development practice
• It is everyone’s benefit to have CI
• Raise your needs so we fix them together
• Join and have some fun

23. Thank you