Ce diaporama a bien été signalé.
Le téléchargement de votre SlideShare est en cours. ×

10 Lessons We Learned with Cloud Foundry

Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité

Les vidéos YouTube ne sont plus prises en charge sur SlideShare

Regarder la vidéo sur YouTube

10 lessons we learned
with Cloud Foundry
By Neville George with Comcast
@findneville
1
Copyright Comcast 2017
2
ENVIRONMENTALS
12
PCF
foundations
2100
developers
~9K
applications
~19K
application
instances
Chargement dans…3
×

Consultez-les par la suite

1 sur 19 Publicité

10 Lessons We Learned with Cloud Foundry

Télécharger pour lire hors ligne

SpringOne Platform 2017
Neville George, Comcast

Our journey with Cloud Foundry over the past three years is strewn with high moments, epiphanies and realizations that we could have done things different. Do naming conventions really matter? Is it necessary to backup everything in CF? Who are the major consumers of the platform? Join us to hear the top 10 challenges Comcast has faced and adapted to over the past three years, so that you can take them on your journey.

SpringOne Platform 2017
Neville George, Comcast

Our journey with Cloud Foundry over the past three years is strewn with high moments, epiphanies and realizations that we could have done things different. Do naming conventions really matter? Is it necessary to backup everything in CF? Who are the major consumers of the platform? Join us to hear the top 10 challenges Comcast has faced and adapted to over the past three years, so that you can take them on your journey.

Publicité
Publicité

Plus De Contenu Connexe

Diaporamas pour vous (20)

Similaire à 10 Lessons We Learned with Cloud Foundry (20)

Publicité

Plus par VMware Tanzu (20)

Plus récents (20)

Publicité

10 Lessons We Learned with Cloud Foundry

  1. 1. 10 lessons we learned with Cloud Foundry By Neville George with Comcast @findneville 1
  2. 2. Copyright Comcast 2017 2 ENVIRONMENTALS 12 PCF foundations 2100 developers ~9K applications ~19K application instances
  3. 3. Copyright Comcast 2017 3 CHAMPION FIND A#1  “How do we onboard developers onto the platform?” - most requested discussion topic at CF summit customer forum  Champions enable developers to envision the journey and articulate how the platform can get you there  “Build and they will come” may not always be a successful strategy
  4. 4. Copyright Comcast 2017 4 AMBITIOUS BE#2  Onboarding big monolithic applications attracts more developers to the platform  Bigger apps helps standardize on frameworks for future innovators on the platform  These success stories become testimonials and the associated teams become endorsers of the platform
  5. 5. Copyright Comcast 2017 5 LOWER THE BAR FOR ENTRY #3  Un-necessary ticketing slows down a fast platform. Evaluate and eliminate the slowest link on the platform constantly.  Build tools, services and documentation to make the platform faster  Evaluate periodically what your biggest ticket generators are move them up on your backlog for automation
  6. 6. Copyright Comcast 2017
  7. 7. Copyright Comcast 2017 7 SE-APS-USAGE-PRD-AS UltraSuperAwesomeSpaceOfMindblowinglyAwesomeAwesomeness
  8. 8. Copyright Comcast 2017 8 FORMALIZE YOUR ENVIRONMENT #4  Institute overall platform standards and individual foundation standards  Onboard new development teams with DO and DO-NOTs  Remind and reinforce when rules are broken
  9. 9. Copyright Comcast 2017 9 #5 COLLABORATION FOSTER  Enable the platform developer community to grow organically  Allows platform operators to focus on delivering more tools and services for the developers  Developers have brought other developers to the community. Today we are a grand (1K) community.
  10. 10. Copyright Comcast 2017 10 #freefood
  11. 11. Copyright Comcast 2017 11 #6 TRUST ESTABLISH  Keep customers informed of platform activities proactively  Establish regular briefings for customers to voice concerns, ask questions and for operators to provide platform updates  Publicize your platform metrics for consumption by anyone within your company
  12. 12. Copyright Comcast 2017 12 #7 CROWD SOURCE  Consolidate your documentation to avoid discrepancies  Create a system where developers can edit and contribute to your documentation  Leverage Github and automated pipelines to automate crowd sourced documentation
  13. 13. Copyright Comcast 2017 13 CONTROL YOUR DESTINY #8  Handoffs to other teams generally increases the time to deliver anything  Invest in open source tooling; Make your customers’ priority your problem to solve.  Tools you use / share with the community may spark interest in other teams to do the same.
  14. 14. Copyright Comcast 2017 14 #9 CHANGE MANAGE  Traditional tools like Application Metadata stores and Change Management teams are here to stay  Educating teams on how the platform is different from IaaS is crucial to ensure maintenances happen without friction  Enable developers to advertise their applications to Application metadata stores by providing guidelines
  15. 15. Copyright Comcast 2017 15 #10 CREATE YOUR OWN SERVICES  Services help reduce the burden on application owners managing infrastructure and creating microcosms  Ticketing trends & collaboration with developers help identify the slowest gear in the platform  Collect information. Create services. Repeat.
  16. 16. Learn More. Stay Connected. 16 #springone@s1p Expand Cloud Foundry for the Enterprise Tim Leong | Wed 11:30 | Room 2004 How Comcast embraced Open Nithya & Shilla | Wed 17:40 | Room 2010 Keynote Panel with Comcast Greg Otto | Thur 9:35 AM Reimagining customer experiences utilizing Pivotal Cloud Foundry Jason & Vipul | Tues 3:20 | Room 2012 Going cloud native at Comcast Todd Migliore | Tues 17:00 | Room 2011
  17. 17. Learn More. Stay Connected. 17 #springone@s1p Comcast Booth * Platform Operators * * Application Owners * * Open Source Promoters * * Recruting *
  18. 18. Copyright Comcast 2017 18 Q & A

Notes de l'éditeur

  • Talk about the levels of the champions

×