introducing infrastructure mapping: helping devops design infrastructure
TRANSCRIPT
Test Drive Your Infrastructure
MAGENTYSHelp people deliver better software, faster!
Automation
Behaviour Driven Development
DevOps
A word on where we have come from...
DEVOPS!
“Solutions to problems are proven through implementing, testing and measuring”
- Kief Morris
Infrastructure as Code
CODE WITHOUT
TESTS IS BAD!“Solutions to problems are proven through implementing, testing and measuring”
Why Bother?➜ We have BDD Specs - If the
environment doesn’t work, the tests will fail
➜ We have monitoring
Example Mapping● Shared Understanding● Team process
https://cucumber.io/blog/2015/12/08/example-mapping-introduction
Behaviour Driven Infrastructure - a starting point
Infrastructure Mapping
Context
Rules / Categories
Examples
Questions
Putting it Together
Infrastructure Specification (BDI)
describe "Logged into application server" do describe "Inbound/outbound rules" do describe "Internet connectivity is enabled" do describe host('www.google.com.au') do it { should be_resolvable } it { should be_reachable } end describe "should be routed via the NAT" do describe command ('traceroute 8.8.8.8') do its(:stdout) { should contain nat_internal_ip } end end end endend
Pitfalls
● Reflective Tests
● Testing Cupcake
● Testing vs monitoring
Patterns
➜ Standardise Infrastructure Mapping
sessions
➜ Organise by context/role
➜ Generate your inventory
➜ Co-locate with config
Final Thoughts
● Specify Behaviour over Configuration● Think about context● Standardise Infrastructure Mapping
sessions● Specs form part of your overall suite● Monitoring
That’s me!
I can be found here:
https://au.linkedin.com/in/hamishtedeschi
The blog on Infrastructure Mapping can be found here:
https://magentys.io/blogs/introducing-infrastructure-mapping/