DevOps from the Provider Perspective
Download as PPTX, PDF0 likes79 views
The document discusses DevOps from the perspective of a technology provider. It suggests that providers should engage with their technical community to understand how customers are implementing DevOps and where they are getting stuck. This will help providers identify the most useful resources to prioritize in their DevOps tools. Providers should adopt an agile approach to implement these resources, starting with an MVP and iterating based on customer feedback. Releasing tools as open source and working with the community can help fill gaps and improve the tools over time.
DevOps from the Provider Perspective
- 1. September 13, 2021 DevOps from the Provider Perspective Pat Patterson Director of Developer Evangelism at Citrix @metadaddy
- 2. 1 © 2021 Citrix | Confidential 2 Provider • Technology vendor • Product Management • Engineering • Product Manager, Architect, CTO • Goals: customer satisfaction, competitiveness Consumer • Technical community • Customers • Partners • Internal: SEs, support, etc • DevOps / CloudOps Engineer, Admin, Developer, Architect • Goals: increased speed, reduced cost, higher quality DevOps: Provider vs Consumer
- 3. © 2021 Citrix | Confidential 3 Tool selection • Buy-in across enterprise • Integration with existing skills, tech • Declarative vs procedural approach • Cloud vs on-premises • Provider support Tutorials • Free hands-on learning • Local or cloud resources DevOps from the Consumer Perspective Patrick van den Born – Consultant
- 4. 1 © 2021 Citrix | Confidential 4 Procedural • "How" • Define sequence of tasks to execute • Automation • Ansible, Chef Declarative • "What" • Specify end-state of system: "desired state" • Infrastructure • Terraform, Packer Declarative vs Procedural Approaches Both have their uses – pick the appropriate tool for the job, combine to solve real-world use cases
- 5. © 2021 Citrix | Confidential 5 # Attachment of a volume to an instance is represented as a resource resource "aws_volume_attachment" "my_attachment" { device_name = "/dev/sdh" volume_id = aws_ebs_volume.my_volume.id instance_id = aws_instance.my_instance.id } resource "aws_instance" "my_instance" { ami = "ami-21f78e11" availability_zone = "us-west-2a" instance_type = "t2.micro" } resource "aws_ebs_volume" "my_volume" { availability_zone = "us-west-2a" size = 1 } Declarative Example: Terraform Configuration
- 6. © 2021 Citrix | Confidential 6 # Attaching a volume to an instance is a task # (Shortcuts can combine operations) - ec2: image: ami-21f78e11 zone: us-west-2a instance_type: t2.micro wait: yes register: my_instance - ec2_vol: volume_size: 1 zone: us-west-2a register: my_volume - ec2_vol: device_name: "/dev/sdh” id: "{{ my_volume.id }}" instance: "{{ my_instance.id }}" Procedural Example: Ansible Playbook
- 7. © 2021 Citrix | Confidential 7 What does this mean for the provider?
- 8. © 2021 Citrix | Confidential 8 Tool selection • Adoption across customer base • Integration with existing skills, tech • Declarative vs procedural • Cloud vs on-premises • Provider support Tutorials • Free hands-on learning • Local or cloud resources DevOps from the Provider Perspective Mayur Vadhar – Sr Product Manager
- 9. © 2021 Citrix | Confidential 9 Key words • Infrastructure, automation, script, toil Where are they rolling their own DevOps? Where are they getting stuck? • Installation • Maintenance Connect with the scripting stars in your community • Search for $YOURTECH plus Python, PowerShell, cURL, shell script, etc Consider complementary resources • AWS? Azure? • What tools and approaches do they support? Engage Your Technical Community! Samuel Legrand – Consultant – presenting at E2EVC Virtualization Conference, 2017
- 10. © 2021 Citrix | Confidential 10 OpenAPI Specification (Swagger) OpenAPI Generator • Go SDK (Terraform) • Python SDK (Ansible) Map your resources to framework resources Concepts vs implementation details Balance ease-of-use with flexibility Implement the provider: ‘glue code’ RESTful APIs are (mostly) necessary, but not sufficient!
- 11. © 2021 Citrix | Confidential 11 Use an agile approach Identify the 20% of functionality that is required in 80% of cases Implement an MVP in-house Release MVP, get feedback, iterate Don’t Try to Boil the Ocean! “Lava flow to ocean from Kilauea” by Robert Cudney is licensed under CC BY-SA 4.0
- 12. © 2021 Citrix | Confidential 12 Release as open source Make support position clear Work with community to fill in gaps • Customer requirements: in house • ‘Nice to have’: community Iterate until done Work in Partnership with the Community
- 13. © 2021 Citrix | Confidential 13 Engage with your technical community Understand their use cases Adopt an agile delivery model – aim for the most useful 20% of resources Conclusion
- 14. © 2021 Citrix | Confidential 14 OpenAPI Specification: swagger.io/specification OpenAPI Generator: openapi-generator.tech Hashicorp Terraform: terraform.io Red Hat Ansible: ansible.com Resources