Slides for All Things Open Conference, 2017. Sample code here: https://github.com/joatmon08/2017-demo-ato.

1. How to Treat a Network as
a Container
(or get close)

2. whoami
rosemary wang
platform & infra
@thoughtworks
@joatmon08

3. containersCIDR

4. “digital transformation”
regressive automated

5. compute
regressive automated

6. build
ship
run

7. network
???????????

8. 99 problems
terminology
api
non-standard
“distributed system”
protocols are specialized
+94 more

9. connectivity
service discovery
policy

10. network
regressive automated
traditional containers
dynamic
infrastructure*
*software-defined X

11. build
ship
run
test
test
test

12. TEST

13. E2E
Integration
Service/Contract
Unit
Manualcost
validate
configuration
confirm
interaction
validate
interaction
“the real deal”
“The Testing Pyramid”

14. Manualcost
E2E
Integration
Service/Contract
Unit
“The Testing Signpost”

15. build

16. helpful references
[Name Your Device Here] + Chef / Ansible / Puppet / Salt (NAPALM)
SDN (Open vSwitch, OpenStack Neutron)
Container Networking (Calico / Flannel / Weave / Kuryr / Consul / Istio /
HAProxy / and more)

17. Given ⇨ the component to automate
When ⇨ some event happens
Then ⇨ the component should be configured

18. connectivity
https://github.com/joatmon08/2017-demo-ato

19. topology from http://docker-k8s-lab.readthedocs.io/en/latest/docker/docker-ovs.html

20. connectivity
Integration Tests!
tests/smoke/features/connectivity.feature
Ansible Playbook
playbook/
Mock Virtual Device
ovs-vagrant/

21. unit: check_ansible_syntax check_openvswitch_playbook
Creates a Vagrant box with Open vSwitch image, checks that the
playbook runs to completion.
integration: bootstrap
sh -c '. venv/bin/activate; cd tests/smoke && behave'
Creates two Open vSwitch hosts via Vagrant, runs playbook,
creates a container on each and checks connectivity.
contract: bootstrap
sh -c '. venv/bin/activate; pytest tests/contract --capture=no'
Create Open vSwitch host via Vagrant, captures output of Consul
Handler and compares to input of playbook
Same tests as integration, on real device.
E2E
Integration
Service/Contract
Unit
makefile
testing the feature

22. list of tools
Vagrant: for virtual devices
Ansible: for device automation
Python: for coding
pytest: for running unit/service tests
behave: BDD for running integration tests
makefile: shortcuts for staging & running tests

23. Automation Tool
Linting Program
Testing Framework
Smoke Test
Testing Framework
Scripts/BDD
Smoke Test
test
Config/Template
Validation
Functional Validation
Output/Input
Certification
Staging/Production E2E
Integration
Service/Contract
Unit

24. ship

25. tests include
standards
+
enforcement

26. service discovery
Given I have a DNS, DHCP, IP address management
solution
When I create a service (or application)
Then I should set up an alias and use the wildcard
root certificate for that service.

27. set those standards!
▢ names - {service}.{business}.companyxyz.net
▢ design principles - only use private domain, SSL
▢ common template/code formatting - Chef automation
▢ testing/development setup - container
▢ event triggers - ticket system

28. enforce those standards!
▢ quality review - 2 peer reviewers
▢ linting programs - foodcritic linting
▢ version control - Git
▢ CI/CD framework - Jenkins
▢ documentation - Wiki-style

29. changes fail
when
patterns break

30. tests fail
when
patterns break

31. run

32. upgrade
scale
secure

33. upgrade
in-place
blue/green
depends on
risk
configuration

34. connectivity
Given I have a container or software-defined network
When I need to upgrade that network*
Then I should create a new network with the same
configuration and use it.
*Assumes no IP address affinity

35. blue
network
orchestrator
compute
cluster
compute
orchestrator
green

36. blue
network
orchestrator
compute
cluster
tests
compute
orchestrator
green

37. blue
network
orchestrator
compute
cluster
compute
orchestrator
green

38. blue
network
orchestrator
compute
cluster
compute
orchestrator
green
50%50%

39. blue
network
orchestrator
compute
orchestrator
green
100%

40. blue
network
orchestrator
compute
orchestrator
green
100%

41. networking is challenging
invest in tests
patterns & standards are useful

42. learn more
▢ hack
▢ read examples
▢ repurpose
▢ befriend a network engineer/qa/dev

43. thank you!