A PaaS for government
•Descargar como PPTX, PDF•
3 recomendaciones•1,923 vistas
Slides from my Velocity EU keynote: http://velocityconf.com/devops-web-performance-eu-2015/public/schedule/detail/46814
Recomendados
Más contenido relacionado
Destacado
Similar a A PaaS for government
Similar a A PaaS for government (20)
Más de annashipman
Más de annashipman (11)
Último
Último (20)
A PaaS for government
- 1. Anna Shipman Technical Architect Government Digital Service @annashipman
- 3. We are a unit of government within the UK’s Cabinet Office GDS@annashipman
- 5. GDS@annashipman The best place to find government services and information
- 6. We’re not just fixing websites GDS@annashipman
- 7. We also work with departments to transform digital services GDS@annashipman
- 10. There are over 800 services GDS@annashipman
- 11. We need to look at the common problems GDS@annashipman
- 12. And the most common problem is hosting GDS@annashipman
- 14. I probably don’t need to explain PaaS to you GDS@annashipman
- 15. Here is the slide we’re using to explain the idea in government GDS@annashipman
- 16. GDS@annashipman
- 17. This detracts from the time teams can spend on their main expertise GDS@annashipman
- 18. GDS@annashipman
- 19. Additional thing for government: procurement is hard GDS@annashipman
- 22. Self-service So infrastructure team don’t just do admin GDS@annashipman
- 24. Support model App developers on-call for their apps GDS@annashipman
- 25. Support model App developers on-call for their apps Platform team on-call for platform GDS@annashipman
- 26. Support model App developers on-call for their apps Platform team on-call for platform No runbooks GDS@annashipman
- 27. Support model App developers on-call for their apps Platform team on-call for platform No runbooks Better experience for the end-user GDS@annashipman
- 29. Multi-tenancy Granularity of user permissions GDS@annashipman
- 30. Multi-tenancy Granularity of user permissions Handling resource contention GDS@annashipman
- 31. Multi-tenancy Granularity of user permissions Handling resource contention Isolation from other tenants GDS@annashipman
- 33. Multiple cloud providers To avoid vendor lock-in GDS@annashipman
- 34. Multiple cloud providers To avoid vendor lock-in Difficult to add later GDS@annashipman
- 35. Multiple cloud providers To avoid vendor lock-in Difficult to add later Details of how unclear at this stage hot/hot? hot/warm? GDS@annashipman
- 36. What we’ve done
- 37. GDS@annashipman
- 38. GDS@annashipman
- 39. GDS@annashipman
- 40. GDS@annashipman
- 41. GDS@annashipman
- 42. We decided to use Tsuru for the initial prototype GDS@annashipman
- 43. Showed it to users in government to get feedback GDS@annashipman
- 44. Meanwhile building same functionality in Cloud Foundry to compare GDS@annashipman
- 45. We haven’t worked out which is most suitable for us yet GDS@annashipman
- 46. GDS@annashipman
- 47. That’s not what I want to talk about now GDS@annashipman
- 48. Though if these are problems that interest you, we are hiring! https://gds.blog.gov.uk/jobs/@annashipman
- 49. What we’ve learned from users
- 50. They definitely like the idea of a PaaS GDS@annashipman
- 51. Self-service is good for both sides GDS@annashipman
- 53. Support model had buy-in GDS@annashipman
- 54. But the feedback from users on multiple cloud providers was not what we expected GDS@annashipman
- 55. None of our users wanted it GDS@annashipman
- 56. And it’s very hard GDS@annashipman
- 58. Google Compute Engine doesn’t have internal load balancers GDS@annashipman
- 59. Can’t take advantage of cool features of all the providers GDS@annashipman
- 60. We were conflating resilience with commercial concerns GDS@annashipman
- 61. Users still have a need to avoid being locked in to one vendor GDS@annashipman
- 62. We are now looking at other ways to address that GDS@annashipman
- 63. What we’ve learned about PaaS
- 64. I no longer think we just need to sit tight for two years GDS@annashipman
- 65. Fast growing field but it’s diversifying GDS@annashipman
- 66. For example, virtualisation vs hardware GDS@annashipman
- 67. Only some will support multi-tenancy GDS@annashipman
- 68. And we now know multi-tenancy is important to our users GDS@annashipman
- 71. Make sure you understand what your users need GDS@annashipman