Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Agile Brazil 2016 - Scaling without Expanding: a DevOps Story

137 vues

Publié le

When your business starts to grow, specially in terms of popularity you will realize that you need to scale with a minimum level of agility, specially on IT software industry. Communication starts to be crucial to keep your workflow in a good shape and agile methodologies are part of your company DNA. But probably you are still feeling that something is missing and you don’t have the control about all project streams, right? So DevOps is the next step for you.

Through automation techniques DevOps culture removes the barriers between your teams and break company silos to make the communication flow smooth and keep the project development mainline focused on get things done without wasting time on repetitive bits and tasks.

Atlassian tools were build for automation and productivity. The integration capabilities among the stack and with several market solutions allows any company to break those walls and scale the business without expanding the teams. You can evolve from a CI/CD pipeline stage and start to define ChatOps and Tracking strategies, bringing the support team closer to the development team and creating a trust and transparency environment between your company and the customers.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Agile Brazil 2016 - Scaling without Expanding: a DevOps Story

  1. 1. VINICIUS LINCK • SOFTWARE ARCHITECT • E-CORE • @VINNYLINCK Scaling Without Expanding: A DevOps Story
  2. 2. is the driving force of DevOps
  3. 3. Automation ChatOps Tracking Support The heart Of DevOps Build Your Command Centre Create an Army of Sentinels Protect Your Project Work
  4. 4. Mandate Build and maintain the platform required by Atlasssian’s developers to build, test and release their products Build Engineering’s
  5. 5. OPERATIONS Build Engineering SUPPORT DEVELOPMENT
  6. 6. 1.8x the number of customers
  7. 7. Automation ChatOps Tracking Support The heart Of DevOps Build Your Command Centre Create an Army of Sentinels Protect Your Project Work
  8. 8. Automate facet of your work
  9. 9. Installing new infrastructure Configuring your servers Deploying a new release Stuff you actually want to get done
  10. 10. Continuous Integration The starting point of every project Bring visibility to your automation
  11. 11. Know what’s running in each environment
  12. 12. Continuous testing = more frequent releases
  13. 13. full bleed image - construction? - farming? - lego? Configuring Servers Configuration as Code
  14. 14. Building Software Building Infrastructure
  15. 15. file { ‘/etc/cron.daily/clean_m2_local': source => ‘puppet:///modules/bamboo_agent_support_maven /etc/cron.daily/clean_m2_local', owner => 'root', group => 'root', mode => '0755', } Configuration as Code ldally@ip-172-30-97-250:~$ ls -la /etc/cron.daily/clean_m2_local -rwxr-xr-x 1 root root 352 Sep 18 00:38 /etc/cron.daily/clean_m2_local
  16. 16. Puppet Bamboo
  17. 17. full bleed image - measuring something (olympics)? - science? Test Virtualization and Behavioural Testing
  18. 18. Spin up an instance Apply your configuration management and deploy your app Run your tests The Testing Process
  19. 19. Testing Tools Vagrant Cucumber Virtualization Behavioral Testing
  20. 20. Spin up an exact mirror of your server ~/s/buildeng-puppet ❯❯❯ vagrant status Current machine states: aptly not created (aws) consul not created (aws) bambooagent not created (aws) bambooserver running (aws) efs not created (aws) bambooserver_rds not created (aws) dns not created (aws) basebox not created (aws) gnomes not created (aws) status not created (aws) graphite not created (aws)
  21. 21. Easy to understand expectations Quick to write
  22. 22. full bleed image - shipping crates? - military drop from plane? - ice road trucker? Configuring Hardware Infrastructure as Code
  23. 23. Building Software Configuring Hardware
  24. 24. # Create an instance for our JIRA server resource "aws_instance" “fried_fritter_jira” { instance_type = "m4.2xlarge" ami = "ami-dfb0e7b5" disable_api_termination = "true" ebs_optimized = "true" subnet_id = “${aws_subnet.ff_us_east_1b.id}” vpc_security_group_ids = [ “${aws_security_group.fried_fritter_jira.id}” ] provider = "aws.{{ vpc.provider }}" } Infrastructure as Code
  25. 25. BambooTerraform
  26. 26. Everything = AutomatedStuff you actually want to get done
  27. 27. Automation ChatOps Tracking Support The Heart Of DevOps Build Your Command Centre Create an Army of Sentinels Protect Your Project Work
  28. 28. …software and IT teams evolved from email to chat. They also replaced repetitive tasks with automation, and replaced annual change control meetings with devops’ continuous collaboration. And they pulled it all together into a central tool like HipChat. SEAN REGAN, HIPCHAT EVANGELIST, ATLASSIAN “ ”
  29. 29. full bleed image - nasa ops room? - ? The Command Centre
  30. 30. Public Our HipChat Rooms Private Alerts The FIGHT channel
  31. 31. Pull Request approvals Green builds No open tasks
  32. 32. See which builds are (or aren’t) passing Know what needs to be done to get your PR merged
  33. 33. You have an amazing knowledge base! …but no one knows where it is :(
  34. 34. Inline access to a knowledge base
  35. 35. I heard you like bots So I put bots in your bot So you can scale while they bot
  36. 36. ChatOps helps you your DevOps culture
  37. 37. Automation ChatOps Tracking Support The Heart Of DevOps Build Your Command Centre Create an Army of Sentinels Protect Your Project Work
  38. 38. Everything you seek to you must
  39. 39. I have no idea what I’m doing
  40. 40. Keep an eye on known causes of performance issues… …Alongside the system’s resources
  41. 41. agent smith SS The most important details of each instance
  42. 42. Most of the time your deployments will succeed! … but sometimes they won’t
  43. 43. Can you see the forest for the trees?
  44. 44. What’s sending the most alerts?
  45. 45. Expose the critical stats to your users
  46. 46. If you track your service… shouldn’t you track how people use your service?
  47. 47. Contact Rate Tracking
  48. 48. Count and categorise your contacts
  49. 49. 0 12.5 25 37.5 50 Maven - Usage External Bamboo - Usage Other Agents - Capability Request Contact Analysis
  50. 50. Case Study: M.A.S.H
  51. 51. go/mash The most important details about an artefact summarised
  52. 52. your tracking
  53. 53. Automation ChatOps Tracking Support The Heart Of DevOps Build Your Command Centre Create an Army of Sentinels Protect Your Project Work
  54. 54. OPERATIONS Build Engineering SUPPORT DEVELOPMENT
  55. 55. OPERATIONS Maintenance SUPPORT DEVELOPMENT Shields
  56. 56. OPERATIONS Maintenance SUPPORT DEVELOPMENT Shields
  57. 57. MaintenanceShields Development / Operations HipChat Confluence Questions ServiceDesk “Shields” Infrastructure specialists Development specialists
  58. 58. go/buildeng full bleed of go/buildeng
  59. 59. Building Champions Public Forum User Groups Bootcamps
  60. 60. Getting proactive: Pipeline Consulting
  61. 61. PC - Criteria What makes a pipeline hard to work with?
  62. 62. Support your customers
  63. 63. Tooling Summary Atlasssian Stack Third Party Tooling
  64. 64. MonitoringHostingDeployment Configuration Testing Dependency Analytics + Security Something for everybody
  65. 65. Thank you!

×