Delivering simple, clear, fast, humane government services with Cloud Foundry

Delivering simple, clear, fast, humane government services with Cloud Foundry

Fad1e9ed293fc5b3ec7d4abdffeb636f?s=128

Lindsay Holmwood

November 26, 2015
Tweet

Transcript

  1. Delivering simple, clear, fast, humane government services with Cloud Foundry

    Lindsay Holmwood @auxesis Infrastructure & Platforms Lead, DTO
  2. Digital Transformation Office

  3. Clear, simple, fast, humane digital services

  4. Transformation programme & Exemplars

  5. None
  6. How do teams work?

  7. Cross-functional

  8. Focus on meeting user needs

  9. Dev & Ops & Security & Design & UX &

    Content & Management
  10. Discovery ↲ Alpha ↲ Beta ↲ Live ↲ Retirement ↲

  11. Build fast & Iterate quickly

  12. The unit of delivery is the team

  13. Everyone is responsible for delivery

  14. None
  15. Service

  16. Service App App App

  17. Service App App App Platform

  18. Service App App App Platform Service App App App

  19. Service App App App Platform Service App App App Platform

  20. Service delivery teams OWN THEIR AVAILABILITY

  21. And we’ll provide a platform to deliver on

  22. Innovate on service delivery NOT TECHNOLOGY

  23. Help delivery teams make the journey to go-live

  24. Work as Imagined vs Work as Done

  25. None
  26. What do teams need?

  27. a way to get their code running in front of

    users
  28. insight into how that code is working (or failing)

  29. data to test hypotheses about user and system behaviour

  30. None
  31. How do teams actually work?

  32. Validate assumptions early

  33. Observe users, work in the team

  34. None
  35. None
  36. None
  37. None
  38. None
  39. What we thought teams needed (in order of importance)

  40. • Console (to link it all up) • CD pipeline

    • Application runtime & environment • Metrics & Monitoring • Logging
  41. None
  42. What we found teams actually needed (in order of importance)

  43. • Logging • Application runtime & environment • CD pipeline

    • Metrics & Monitoring • Console (to link it all up)
  44. What are we doing now?

  45. ~10 apps

  46. PWS & Jenkins & GitHub & Slack

  47. Continuous Deployment

  48. None
  49. 25 50 75 100 Oct 29 Nov 2 Nov 5

    Nov 9 Nov 12 Nov 15 Nov 18 Nov 22 Nov 25
  50. 75 150 225 300 Week 44 Week 45 Week 46

    Week 47 Week 48 218 295 96 37 13
  51. 15 contributors Dev & Ops & Design & UX &

    Content & Management
  52. The unit of delivery is the team

  53. blue / green

  54. #!/bin/bash # Update the blue app cf unmap-route dto-blue cfapps.io

    -n dto cf push dto-blue --no-hostname --no-manifest --no-route -i 1 -m 256M cf map-route dto-blue cfapps.io -n dto # Update the green app cf unmap-route dto-green cfapps.io -n dto cf push dto-green --no-hostname --no-manifest --no-route -i 1 -m 256M cf map-route dto-green cfapps.io -n dto
  55. Prior art?

  56. GDS Cloud Foundry & Tsuru

  57. 18f Cloud Foundry cloud.gov

  58. None
  59. None
  60. Focused on the application runtime

  61. None
  62. What is the DTO doing differently?

  63. PaaS is important

  64. But PaaS is bigger than an app runtime

  65. Make the right things easy

  66. Clear integration points build, test, deploy, secure, monitor, …

  67. Technology is cheap, people are dear

  68. Free people up to help org learn

  69. What puzzles us?

  70. How do we integrate with protected environments?

  71. Mini CF per agency? Gateway services?

  72. Australian Privacy Principles PATRIOT Act, cross-border disclosure, ‘use’ vs ‘disclosure’

  73. Is government ready for this?

  74. Yes! With guidelines and human help!

  75. • Logging • Application runtime & environment • CD pipeline

    • Metrics & Monitoring • Console (to link it all up)
  76. Thank you!

  77. Thank you! ❤ the talk? Let @auxesis know!