Open stack jobs avoiding the axe
Download as PPTX, PDF1 like746 views
The presentation by Jim Leitch discusses the impact of cloud technology on system engineering, highlighting the transition from traditional roles to automated environments in the cloud. He emphasizes the importance of adopting software-defined approaches and provides practical tips for building and testing a personal OpenStack cloud environment. Leitch also touches on the necessity of embracing DevOps practices for improved efficiency and agility in cloud deployments.
Open stack jobs avoiding the axe
- 1. SYSTEM ENGINEER 2016 Jim Leitch (jim.leitch@test-rig.com) Fairbanks OpenStack Jobs Meetup 13/1/2016
- 2. SYSTEM ENGINEER 2016 “Waiting for the Software Defined Axe or Learning to Wield it” https://www.flickr.com/photos/adulau/ https://creativecommons.org/licenses/by-sa/2.0/
- 3. START DEMO
- 4. WHO AM I ? •Originally From Scotland/UK •Live in Netherlands •Family Man •Guitar Hero •Dog Lover •Nerd
- 5. THAT’S NICE, BUT WHAT ARE WE GOING TO TALK ABOUT ? •Topics: • Cloud technology and how it affects my job (and probably yours too) • Awesome, but does it DevOps ?? • “Do you have any starter tips on software defined axe-avoidance ?” • all in the next 20 minutes
- 6. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO)
- 7. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - 1 • What I told people did: • Linux Build Team Leader • 8 Technicians • Oracle Linux on VMWare • 3000 Hosts • “National Infrastructure” • Cool !
- 8. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - 2 • What I really did: • 50% - Chasing free IPs • 20% - Explaining why project builds late • 20% - Explaining why project builds broken • 9.8% - Refactoring the IP spreadsheet • 0.2% - Reading “The Register” • 0% - Automating system deployment • BORING !!!
- 9. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) – 3 • http://www.theregister.co.uk/2013/08/09/sysadmins_to_devops_job_migrations/ • Cloud technology will take away the boring stuff • Networking – largely automated, just the big stuff • Storage allocation – bye • OS Installs and updates - nope • Project setups – Self Service for scrum teams • No more boring stuff • Which might be a bad thing if your job is to do the boring stuff
- 10. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - 4 • what is this cloud thing anyway ??? - Software Defined “X” • Software defined hosts • Software defined network • Software defined storage • Software defined data center • Vendors providing Puppet and Chef APIs to their products • No more custom admin interface for every widget in your DataCenter • Cisco/EMC/etc all configurable by Puppet/Chef • All versioned in your GIT repo
- 11. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - 5 • The Evidence – some examples • WorldWide Year on Year cloud revenues up 28% • AWS EC2 Instances • 95% year on year increases • Exchange / Office365 • Who would choose to build and run their own green field Exchange infra now ? • AT&T • 50% of AT&T networks are controlled by OpenStack SDN • Microsoft / HP • “HPE Hyper Converged 250 for Microsoft CPS Standard” – worst product name ever • Better called “The Software Defined Job Axe Murderer”
- 12. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - 6 • HPE Hyper Converged 250 for Microsoft CPS Standard • Looks innocent enough • 24 cores, 512 GB (x4) • Storage and networking built in (20Gb/s) • Factory configured • System Center • HPE Oneview • Azure pack Single interface for seamless spinning up of environments in either private or public Azure cloud, all factory configured, just slide it in the rack • “But hang on a minute, that’s my job !! .... oh yeah, ok, I’ll just get my coat......”
- 13. CLOUD TECHNOLOGY AND HOW IT AFFECTS MY JOB (AND PROBABLY YOURS TOO) - SUMMARY • Software Defined Everything • Cloud • HyperConvergence are all coming along to play with your dog, steal your lunch, sit in your chair, wear your slippers sooner than you could expect But It’s not all bad news
- 14. AWESOME, BUT WILL IT DEVOPS ?
- 15. AWESOME, BUT WILL IT DEVOPS ?
- 16. DEVOPS/AGILE/BLAH QUICK RECAP: o Faster Time To market o Fail Fast o Programmatic Approach / Everything is Code o Version All The Things o predictable-efficient-secure-maintainable
- 17. Agile Devops Continuous Deployment Cloud (wel of niet private) NO X WITHOUT Y
- 18. LAYERS • Layers • Cloud • HyperConvergence are all coming along to play with your dog, steal your lunch, sit in your chair, wear your slippers sooner than you could expect But It’s not all bad news
- 19. LAYER0
- 20. LAYER0 TOOLS • Terraform • Cloud Formation • Cloudify
- 21. LAYER1
- 22. LAYER1 TOOLS • Puppet • Chef • Ansible • Salt • CFEngine • OpenStack HEAT
- 23. LAYER2
- 24. LAYER2 TOOLS • Capistrano • Phing • Gradle • Jenkins Lifecycle • Octopus Deploy • Xebia XL Deploy • Nolio / CA Release Automation
- 25. WHAT I AM ACTUALLY DOING
- 26. “STARTER TIPS ?” • Be Cloud Agnostic • Spin up your cloud test lab • Clone a known production environment • Be familiar with Continuous Deployment • START NOW
- 27. BUZZWORDS • Buzzwords • Packer • vagrant • DNsimple • GitLAB • RDO • Mirantis FUEL • Ceph
- 28. YOUR VERY OWN CLOUD - 1 Recommdation: • Build your own OpenStack environment if you have not done it already • Get your hands dirty • Run a PoC • Sneak in the backdoor with Development and Test • (just like virtualisation back in the day)
- 29. YOUR VERY OWN CLOUD - 2 OPTIONS: • Repurpose older kit at work • You might not just have this kit hanging around • Build Your Own budget cloud and keep it in your garage • Messy, Noisy, Time Eating • Forever rebuilding, need to be onsite • Buy Secondhand servers and put them in co-location • EUR 5000+ initial investment • EUR 300/month hosting costs • Use a Public Cloud • AWS = No fun, not actually working with cloud tech • Azure = Same as AWS with nicer interface • FUGA.IO = Dutch OpenStack Public Cloud • PACKET.NET = Bare Metal Hosting = Nice !
- 30. YOUR VERY OWN CLOUD - 2 RECOMMENDATION: • Use Packet.Net • Bare Metal Hosting • Get Hands On With OpenStack
- 31. YOUR VERY OWN CLOUD - 3 How To: Pre-requisites: Install Terraform Install GIT • Register with packet.net • Use voucher supplied • Note API Key • Follow instructions: https://github.com/jimleitch01/packet-openstack-demos
- 32. YOUR VERY OWN CLOUD - 4 Next Steps: • Multi-node OpenStack • CI/CD Environment • Be the new AWS
Editor's Notes
- #2: Hope no-one minds but going to do this presentation in English If anyone doesn’t understand my Scottish accent then it’s your own fault
- #3: You had a choice of meetup options, thanks for choosing this one, and thanks to Fairbanks for organising it When Guston called he asked me if I could scare the crap out of people about how cloud technologies were going to take away their way of working This photo is called “Do you like my axe ? Welcome to Belgium.
- #4: Just before I start talking I’d like to start the demo environment, so please ignore the following pray to the demo gods
- #6: Starter tips – right now building openstack on baremetal adn am going to share the scripts to do it
- #9: nmap
- #10: turned out that reading The Register wasn;t so bad after all
- #11: turned out that reading The Register wasn;t so bad after all
- #12: urned out that reading The Register wasn;t so bad after all
- #13: This 2U costs the same as 6 months FTE
- #14: urned out that reading The Register wasn;t so bad after all
- #20: Bootstrapping and Deployment
- #22: Configuration Management
- #24: Software Deployment
- #27: I know we are here at an OpenStack event, but it’s in your interest not to rely in one certain platform Be familiar with continuous deplyment becasue your boss/customer is going to be talking to you about it
- #28: Terraform is vagrant for infra
- #29: Our stack actually honestly got hit by lightning
- #30: Our stack actually honestly got hit by lightning
- #31: Our stack actually honestly got hit by lightning
- #32: Our stack actually honestly got hit by lightning
- #33: Our stack actually honestly got hit by lightning