Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
From 0 to 1000 Apps
The first year of Pivotal Cloud Foundry @ The Home
Depot from a platform operator’s perspective.
From 0 to 1000 Apps
The first year of Pivotal Cloud Foundry @ The Home
Depot from a platform operator’s perspective.
introductions
setting expectations
reminisce & learn
aha moment
questions
Agenda
Well, hi!
15 years
Anthony McCulley
Manager, Application Platforms
The Home Depot
anthonymcculley
amcculley@gmail.com
Star...
Platform operator perspective
Being a platform operator
A year-long retrospective
A surprise reveal at the end…
A surprise reveal at the end…
We ready?
Jun 2015
June 2015
?
PCF installed on-
prem
Jul 2015
July 2015
?
July 2015
Lesson #1
Be empathetic to the
people, processes, and
technology already in
place.
July 2015
2 teams using Pivotal Cloud Foundry (Pivotal Labs)
3 foundations (Sandbox, Nonprod, Prod)
? App instances
Aug 2015
August 2015
Dev Forum: Introducing PCF
Lesson #2
Let your community know
that a thing exists… and
real.
August 2015 – PCF is here but has caveats
Platform requires permission to use it
Platform isn’t self-service
No idea how t...
Sep 2015
September 2015
Gave prod access to devs
Lesson #3
Use new things as an
excuse to question
everything and do things
differently.
September 2015
Enabled dev teams to be Org Managers in Prod
Decided on no chargebacks… PCF is “free” to use
Several teams ...
Oct 2015
October 2015
October 2015
Not much going on…
Data center incident impacts Nonprod for 5 days
Great blameless retro as a result
Attend o...
Nov 2015
November 2015
Dev Forum: GitHub, Slack
Lesson #4
Establish a reliable
cadence for
communicating to
community.
November 2015
Slack doubles overnight to 300 people
We pilot self-provisioning in Non Prod
Pivotal (Josh Kruck) asks me to...
Dec 2015
December 2015
Make it accessible
December 2015
Josh asks (again) if we considered running workshops
Self-provisioning added for Production
WillItConnect ma...
Lesson #5
Remove all barriers to
entry – human or
otherwise.
Jan 2016
January 2016
Pupil becomes the master
January 2016
We start running several PCF workshops
2x a week, every week for next 4 months
800 developers will eventually...
Lesson #6
Go beyond operating the
platform – be an advocate,
a teacher, and a thought
leader.
Feb 2016
February 2016
February 2016
Workshop tweaked and rebranded
Removed deeper CF topics
Added organizational change topics
Git, Slack, Full ...
Lesson #7
Establish a scalable
customer service and
support model.
Customer Support
Encourage pair programming
Devs: Ask your pair -> then slack -> then the internet
We dedicate a pair each...
Mar 2016
March 2016
March 2016
250 devs go through Modern Development Workshop
Highest single month
We create #pcf-operators slack channel
Pub...
Apr 2016
April 2016
?
April 2016
Production is running out of capacity just as…
”PCF is the strategic platform of choice”
May 2016
May 2016
May 2016
Prod runs out of capacity
April 2016
We turn off self-provisioning in Production
Lesson #8
Don’t run out of capacity.
Lesson #8 (again)
No. Seriously. Don’t run
out of capacity.
Get really good at
monitoring capacity.
Lesson #9
Be careful about your
choice of words.
“Use PCF” changed to
“Build 12 Factor Apps”.
Jun 2016
June 2016
June 2016
We stand up 2nd production foundation
We increase capacity on existing foundation
And then…
Red Alert: 1st Major Incident
Red Alert: 1st Major Incident
Its okay. We
are all
learning.
Lesson #10
Don’t over react to first
incident. Avoid
operational scarring.
Takes great leaders!
Lesson #11
Have a dedicated team…
dedicated to PCF.
Lesson #12
Don’t hand “support” of
platform off to another
team.
Jul 2016
July 2016
Today
By the numbers
3000 Apps
4000 App Instances
5800 people in Slack – over 1100 of them in #cloudfoundry
1300 unique platform...
Lesson #12
Don’t police developers.
Study them with user
analytics.
Lesson #13
Based on analytics, single
out people and teams to
have discussions with.
What’s next?
Motivate teams to be lean with capacity
Showback model
quota vs. utilization ratios
Remove all matrixed depen...
I promised an aha moment!
We don’t “operate a
platform”.
We enable developers.
We are a product team.
Developers are our
c...
Thanks! Any questions?
Upcoming SlideShare
Loading in …5
×

From 0 to 1000 Apps: The First Year of Cloud Foundry at the Home Depot

3,819 views

Published on

SpringOne Platform 2016
Speaker: Anthony McCulley; Change Leader, The Home Depot.

From one team and some hardware in a closet to becoming the platform of choice for hundreds of developers across multiple data centers - what has our journey with Pivotal Cloud Foundry looked like in our first year?

How did we get our development community to quickly adopt the platform? What are some things we did wrong and would like to help others avoid in their own transformation and adoption? What are some things we did right and would encourage? What were the technical, organizational, and people challenges along the way?

Some we solved. Some we are still working out. We would like to have an interactive discussion about where we are and see what we can all learn from each other about organizational change and driving adoption.

Published in: Technology
  • Be the first to comment

From 0 to 1000 Apps: The First Year of Cloud Foundry at the Home Depot

  1. 1. From 0 to 1000 Apps The first year of Pivotal Cloud Foundry @ The Home Depot from a platform operator’s perspective.
  2. 2. From 0 to 1000 Apps The first year of Pivotal Cloud Foundry @ The Home Depot from a platform operator’s perspective.
  3. 3. introductions setting expectations reminisce & learn aha moment questions Agenda
  4. 4. Well, hi! 15 years Anthony McCulley Manager, Application Platforms The Home Depot anthonymcculley amcculley@gmail.com Startups
  5. 5. Platform operator perspective
  6. 6. Being a platform operator
  7. 7. A year-long retrospective
  8. 8. A surprise reveal at the end…
  9. 9. A surprise reveal at the end…
  10. 10. We ready?
  11. 11. Jun 2015
  12. 12. June 2015 ? PCF installed on- prem
  13. 13. Jul 2015
  14. 14. July 2015 ?
  15. 15. July 2015
  16. 16. Lesson #1 Be empathetic to the people, processes, and technology already in place.
  17. 17. July 2015 2 teams using Pivotal Cloud Foundry (Pivotal Labs) 3 foundations (Sandbox, Nonprod, Prod) ? App instances
  18. 18. Aug 2015
  19. 19. August 2015
  20. 20. Dev Forum: Introducing PCF
  21. 21. Lesson #2 Let your community know that a thing exists… and real.
  22. 22. August 2015 – PCF is here but has caveats Platform requires permission to use it Platform isn’t self-service No idea how to charge customers for it…. so we don’t (yet) 1st team goes to production… takes 4.5 hours!
  23. 23. Sep 2015
  24. 24. September 2015
  25. 25. Gave prod access to devs
  26. 26. Lesson #3 Use new things as an excuse to question everything and do things differently.
  27. 27. September 2015 Enabled dev teams to be Org Managers in Prod Decided on no chargebacks… PCF is “free” to use Several teams using their own Slack channels
  28. 28. Oct 2015
  29. 29. October 2015
  30. 30. October 2015 Not much going on… Data center incident impacts Nonprod for 5 days Great blameless retro as a result Attend our first “Cloud Foundry Workshop” with Pivotal
  31. 31. Nov 2015
  32. 32. November 2015
  33. 33. Dev Forum: GitHub, Slack
  34. 34. Lesson #4 Establish a reliable cadence for communicating to community.
  35. 35. November 2015 Slack doubles overnight to 300 people We pilot self-provisioning in Non Prod Pivotal (Josh Kruck) asks me to consider running workshops I give a videotaped talk at a Cloud Foundry meetup This spawns internal discussions – “Orange Tape”
  36. 36. Dec 2015
  37. 37. December 2015
  38. 38. Make it accessible
  39. 39. December 2015 Josh asks (again) if we considered running workshops Self-provisioning added for Production WillItConnect madness begins Remove need to request Org Manager
  40. 40. Lesson #5 Remove all barriers to entry – human or otherwise.
  41. 41. Jan 2016
  42. 42. January 2016
  43. 43. Pupil becomes the master
  44. 44. January 2016 We start running several PCF workshops 2x a week, every week for next 4 months 800 developers will eventually do workshop
  45. 45. Lesson #6 Go beyond operating the platform – be an advocate, a teacher, and a thought leader.
  46. 46. Feb 2016
  47. 47. February 2016
  48. 48. February 2016 Workshop tweaked and rebranded Removed deeper CF topics Added organizational change topics Git, Slack, Full Stack, Paired Programming My team adopts 100% paired “programming”
  49. 49. Lesson #7 Establish a scalable customer service and support model.
  50. 50. Customer Support Encourage pair programming Devs: Ask your pair -> then slack -> then the internet We dedicate a pair each iteration to 100% customer service Conversational support. No tickets No queues
  51. 51. Mar 2016
  52. 52. March 2016
  53. 53. March 2016 250 devs go through Modern Development Workshop Highest single month We create #pcf-operators slack channel Public channel for matrixed teams to engage Infrastructure, networking, Pivotal, platform, security
  54. 54. Apr 2016
  55. 55. April 2016 ?
  56. 56. April 2016 Production is running out of capacity just as…
  57. 57. ”PCF is the strategic platform of choice”
  58. 58. May 2016
  59. 59. May 2016
  60. 60. May 2016 Prod runs out of capacity
  61. 61. April 2016 We turn off self-provisioning in Production
  62. 62. Lesson #8 Don’t run out of capacity.
  63. 63. Lesson #8 (again) No. Seriously. Don’t run out of capacity. Get really good at monitoring capacity.
  64. 64. Lesson #9 Be careful about your choice of words. “Use PCF” changed to “Build 12 Factor Apps”.
  65. 65. Jun 2016
  66. 66. June 2016
  67. 67. June 2016 We stand up 2nd production foundation We increase capacity on existing foundation And then…
  68. 68. Red Alert: 1st Major Incident
  69. 69. Red Alert: 1st Major Incident Its okay. We are all learning.
  70. 70. Lesson #10 Don’t over react to first incident. Avoid operational scarring. Takes great leaders!
  71. 71. Lesson #11 Have a dedicated team… dedicated to PCF.
  72. 72. Lesson #12 Don’t hand “support” of platform off to another team.
  73. 73. Jul 2016
  74. 74. July 2016
  75. 75. Today
  76. 76. By the numbers 3000 Apps 4000 App Instances 5800 people in Slack – over 1100 of them in #cloudfoundry 1300 unique platform users 6 foundations (more planned EOY) 14000 cf push – 1500 to Production in June alone > 2 billion log messages a month
  77. 77. Lesson #12 Don’t police developers. Study them with user analytics.
  78. 78. Lesson #13 Based on analytics, single out people and teams to have discussions with.
  79. 79. What’s next? Motivate teams to be lean with capacity Showback model quota vs. utilization ratios Remove all matrixed dependencies for teams Automate network and security requests Community-built smoke tests Add app tests to our tests on changes
  80. 80. I promised an aha moment! We don’t “operate a platform”. We enable developers. We are a product team. Developers are our customers.
  81. 81. Thanks! Any questions?

×