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.

New Capabilities and Product Strategy for .NET on PCF

275 views

Published on

SpringOne Platform 2018
New Capabilities and Product Strategy for .NET on PCF - William Martin, Pivotal

Published in: Software
  • Be the first to like this

New Capabilities and Product Strategy for .NET on PCF

  1. 1. New Capabilities and Product Strategy for .NET on PCF Allan William Martin, Product Lead at Pivotal, .NET + Windows @awmartin
  2. 2. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Safe Harbor Statement The following is intended to outline the general direction of Pivotal's offerings. It is intended for information purposes only and may not be incorporated into any contract. Any information regarding pre-release of Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal and is subject to change. This information is provided without warranty or any kind, express or implied, and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions regarding Pivotal's offerings. These purchasing decisions should only be based on features currently available. The development, release, and timing of any features or functionality described for Pivotal's offerings in this presentation remain at the sole discretion of Pivotal. Pivotal has no obligation to update forward looking information in this presentation. 2
  3. 3. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Disclaimer
  4. 4. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Who are we? We are the engineers, designers, product managers, platform architects, solution architects, and others building the future of cloud-native .NET at Pivotal. Shanfan Huang, design lead Matthew Horan, engineering lead Kartik Lunkad, product manager Natalie Arellano, anchor engineer Ashwin Venkatesh, anchor engineer (edit) Amin Jamali, engineer Sam Smith, engineer Andrew Keesler, engineer Arjun Sreedharan, engineer Gabelan Satchithanantham, engineer Jason Smith, engineer Malini Valliath, engineer Micah Young, engineer Sam Peinado, designer Simon Jones, engineer Yael Harel, engineer Zander Mackie, engineer Ben Moss, engineer Leah Hanson, engineer Kenneth DuMez, engineer Stuart Pollock, engineer David Jahn, engineer Paul Nikonowicz, engineer Sameer Vohra, product manager Colin Jackson, product manager Shawn Neal, solutions architect Chris DeLashmutt, platform architect Cornelius Mendoza, platform architect Chris Umbel, solutions architect, .NET lead David Dieruf, platform architect Michael Lipscomb, solutions architect Eamon Ryan, solutions architect Shana King, support engineer Nikhil Suvarna, support lead Sunjay Bhatia, engineer Andrew Stakhov, platform architect … and many more!
  5. 5. .NET enterprise portfolios are complex. The enterprise cloud-native movement has focused on Java, and .NET is now poised for change.
  6. 6. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server Workloads in your datacenter often aren’t easily portable Dependencies installed on the host; apps are tied to a particular server; apps use OS APIs. ?
  7. 7. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server Workloads are difficult to modernize Monoliths and large legacy portfolios are inherently challenging, and you still need them.
  8. 8. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server High cost to maintain Maintaining many Windows servers, sprawl of potentially outdated frameworks or APIs, many other Windows-hosted dependencies (DBs, COTS, services, etc.). Windows 2012 R2 Server Windows 2003 Server
  9. 9. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server Difficult to adopt new Windows versions Standing up new servers can take months. Windows 2008 is still popular and EOL this year. Windows 2012 R2 Server Windows 2003 Server Windows 2019 ???
  10. 10. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server Not always worth rewriting in .NET Core While .NET Core promises a lot, it’s still costly to rewrite all your apps. Windows 2012 R2 Server Windows 2003 Server .NET Core ??? .NET Core .NET Core
  11. 11. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Challenges .NET APP Windows 2008 Server .NET Core may not yet meet all your needs It’s maturing quickly, but the libraries you need may not be ready. Windows 2012 R2 Server Windows 2003 Server .NET Core ??? .NET Core .NET Core
  12. 12. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Opportunities .NET APP Windows 2008 Server Microsoft sets a bright future with new technologies and approaches. Windows 2012 R2 Server Windows 2003 Server Microsoft - .NET Core - Azure services - multi-/hybrid cloud - docker - … THE ASPIRATIONS
  13. 13. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET – Opportunities .NET APP Windows 2008 Server OSS is accelerating the game for enterprise software. Windows 2012 R2 Server Windows 2003 Server Microsoft - .NET Core - Azure services - multi-/hybrid cloud - docker - … ASPIRATIONS OSS - microservices - event sourcing - service mesh - container orchestration - functions - …
  14. 14. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Diagnosing Enterprise .NET .NET APP Windows 2008 Server How can you cross this chasm between .NET’s current state and the bright future of OSS, Microsoft, and cloud-native? Windows 2012 R2 Server Windows 2003 Server Microsoft - .NET Core - Azure services - multi-/hybrid cloud - docker - … ASPIRATIONS OSS - microservices - event sourcing - service mesh - container orchestration - functions - … CHASM
  15. 15. Our mission is to establish cloud-native .NET. The .NET Renaissance is in full swing. PCF will be an opinionated place where .NET enterprises can be confident about their future.
  16. 16. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Vision: Complete Transformation Platform + Practices PLATFORM A complete platform that seamlessly enables healthy patterns for modern .NET apps. ● Aim to host the most transformative and important .NET and Windows apps. ● Enable the path to the .NET Core future, to build and host .NET Core microservices together with .NET Framework and Windows-hosted services. ● Make an adaptable platform, so operators can satisfy the needs of their own dev teams to move faster. 16
  17. 17. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Vision: Complete Transformation Platform + Practices PLATFORM A complete platform that seamlessly enables healthy patterns for modern .NET apps. ● Aim to host the most transformative and important .NET and Windows apps. ● Enable the path to the .NET Core future, to build and host .NET Core microservices together with .NET Framework and Windows-hosted services. ● Make an adaptable platform, so operators can satisfy the needs of their own dev teams to move faster. 17 PRACTICES App transformation practices that define cloud-native .NET: Move and Improve! ● Pivotal builds “best practices” for cloud- native app creation and migration. ● Focus on core benefits of sustainable security, speed, stability, scale, savings. ● Co-create these practices and opinions with customers, partners, field teams, and the .NET community.
  18. 18. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Vision: Complete Transformation Platform + Practices PLATFORM A complete platform that seamlessly enables healthy patterns for modern .NET apps. ● Aim to host the most transformative and important .NET and Windows apps. ● Enable the path to the .NET Core future, to build and host .NET Core microservices together with .NET Framework and Windows-hosted services. ● Make an adaptable platform, so operators can satisfy the needs of their own dev teams to move faster. 18 PRACTICES App transformation practices that define cloud-native .NET: Move and Improve! ● Pivotal builds “best practices” for cloud- native app creation and migration. ● Focus on core benefits of sustainable security, speed, stability, scale, savings. ● Co-create these practices and opinions with customers, partners, field teams, and the .NET community.
  19. 19. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Our Teams’ Guiding Principles 1. Strive for “pragmatic parity” for features available to Linux-hosted and Windows- hosted apps. 2.Stay true to the value propositions of PCF and cloud-native. 3.Address the specific needs of .NET and Windows workloads, including developing new tools and automation. 4.Consider Microsoft’s evolving cloud (Azure) and developer (365) strategy. 5.Secure by default. Ensure Windows platform security delivers modern best practices. 6.Co-create product features with our customers and partners.
  20. 20. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ .NET Portfolio Strategy New / greenfield Modernize Legacy lift-and-shift Divest Depend heavily on non-cloud-native patterns (local state, file system dependencies, etc.) Use a variety of Windows / IIS technologies (COM+ assemblies, GAC, registry) Leverages Integrated Windows Authentication The .NET Core future. Opportunity for new patterns like microservices, functions, event-driven architectures, etc. More easily movable to a cloud-friendly state Platform provides support for most common IIS / .NET / Windows technologies Flexibility to decide the modernization strategy
  21. 21. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ .NET Portfolio Strategy – Product New / greenfield Modernize Legacy lift-and-shift Divest Steeltoe Concourse PASWPAS PKSW (Proposed) PFS (Future) PCF BOSH
  22. 22. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ .NET Portfolio Strategy – Practices We’re aiming to provide a platform that supports hosting and transforming a .NET and Windows portfolio.
  23. 23. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Benefits of Running .NET and Windows on PCF Applications ● Increased developer productivity. Iterate rapidly with cf push. ● Deploy .NET Core, .NET Framework, and Windows services side-by-side. ● Incrementally break up the .NET monolith into .NET Core microservices with much less friction. ● Automatically builds a full, OCI-compliant container image, supplying key .NET, IIS, and Windows capabilities. ● Scale out .NET running apps live, either manually or based on CPU load or traffic. ● Transparently patch all apps in production with no downtime, through the container “rootfs.” Operations ● Reduce complexity of managing fleets of Windows servers automatically with BOSH. ● Scale out the Windows deployments simply. ● Deploy Windows Updates reliably in rolling fashion with no downtime in production. ● Automate the deployment of host-provided system and application dependencies. ● Deploy and adopt new Windows versions transparently with no downtime.
  24. 24. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How we defined this vision…
  25. 25. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Product Evolution Java .NET Common platform capabilities, potentially available to both ecosystems.
  26. 26. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PCF, Java, Spring Java .NET
  27. 27. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Feedback: “What about our .NET workloads?” Java .NET
  28. 28. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Looks like an opportunity! Java .NET
  29. 29. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ In 2015, we introduced Diego for Windows. Java .NET The MVP of our product line, PCF Diego for Windows. (ca. Oct 2015)
  30. 30. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PCF Runtime for Windows (with BOSH) Java .NET PCF Runtime for Windows Introduced automated Windows Server 2012 R2 management with BOSH. (April 2017)
  31. 31. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Feedback: “We need the rest.” Java .NET The remaining feature set is important. And customers were interested in Microsoft’s containerization and Windows 2016.
  32. 32. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Application Service for Windows Java .NET Pivotal Application Service for Windows Introduced a containerized runtime using Windows Server Containers. (March 2018) Full potential for pragmatic parity
  33. 33. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Adapting to the needs of customers. Java .NET Steeltoe (corollary to Spring) - Config server - Circuit breaker - Service discovery - Connectors - Actuators - GA March 2017 Windows operations - RDP + SSH - Automated activation - Security policies Developer integrations - IIS modules - Remote debugging - Buildpack extensions
  34. 34. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The Complete Platform with First-Class Support Java .NET
  35. 35. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Application Service for Windows
  36. 36. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Application Service Pivotal Application Service for Windows is a scalable runtime extension to Pivotal Application Service that enables PCF to host applications powered by the .NET Framework, the latest Windows® Server operating system, and Windows Server Containers.
  37. 37. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The PCF .NET + Windows “Stack”
  38. 38. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The PCF .NET + Windows “Stack”
  39. 39. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Application Service for Windows
  40. 40. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Deploying Windows Servers
  41. 41. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW Improvements 41 Improved runtime performance. CPU shares solves potential noisy-neighbor issues with long-running, CPU-intensive workloads. Better overall security from containerization. Network, file system, process isolation. On 2012 R2, all apps shared the same network. Better app portability. A container image with a full isolated file system. Remote debugging, cf ssh, and more. Troubleshoot Windows containers for faster iteration and insights into the app deployment. Higher container density. PASW can host more AIs on a single cell than could be on 2012 R2 + IronFrame, meaning fewer VMs. Critical known Windows exploits are mitigated. (e.g. conhost “fork bombs” can be constrained). Greater speed, configurability, and flexibility. Patterns like multi-buildpacks enable developers to leverage all the benefits of the platform experience. Better integrations with IIS and Windows. Technologies are now on the roadmap. More modern OSS capabilities. Emerging technologies like Kubernetes, Envoy route integrity, Istio service mesh, etc., are now possible for .NET workloads.
  42. 42. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Current .NET Framework Compatibilities and Recommendations
  43. 43. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Deploying .NET apps to PASW cf push -s windows2016 -b hwc_buildpack PAS tile deployment PAS for Windows tile deployment Linux Diego Cells Windows Diego Cells CAPI Diego cf push -s cflinuxfs3 GoRouter TRAFFIC
  44. 44. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ .NET Developer Experience 4 4 cf push a .NET Framework and .NET Core applications with buildpacks. cf ssh enables developers to inspect a container on PASW with a PowerShell session. Remote debugging for .NET Framework into a PCF foundation is now possible on PASW by leveraging the cf ssh port forwarding feature. A similar process is available for debugging .NET Core applications hosted on Linux.
  45. 45. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW Details 4 5 Core Capabilities Container orchestration (Diego + Garden) BOSH-managed VMs BOSH add-ons (for OS dependencies) BOSH SSH Azure + AWS + GCP + vSphere Buildpacks (for app dependencies) Application security groups App scaling Service bindings Syslog forwarding Diego tasks Isolation segments Configurable health check Log aggregation (cf logs)
  46. 46. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW Details 4 6 Core Capabilities Container orchestration (Diego + Garden) BOSH-managed VMs BOSH add-ons (for OS dependencies) BOSH SSH Azure + AWS + GCP + vSphere Buildpacks (for app dependencies) Application security groups App scaling Service bindings Syslog forwarding Diego tasks Isolation segments Configurable health check Log aggregation (cf logs) PASW 2.1 Supporting Windows Server, version 1709 CPU metrics + network limits Full autoscaler support CredHub encrypted service creds Diego SSH (i.e. cf ssh) PASW 2.2 .profile.bat scripts Additional IIS feature support PASW 2.3 (Shipped on Monday!) Supporting Windows Server, version 1803 Multi-buildpacks integrations Ephemeral disk size selection
  47. 47. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW Details 4 7 Core Capabilities Container orchestration (Diego + Garden) BOSH-managed VMs BOSH add-ons (for OS dependencies) BOSH SSH Azure + AWS + GCP + vSphere Buildpacks (for app dependencies) Application security groups App scaling Service bindings Syslog forwarding Diego tasks Isolation segments Configurable health check Log aggregation (cf logs) PASW 2.1 Supporting Windows Server, version 1709 CPU metrics + network limits Full autoscaler support CredHub encrypted service creds Diego SSH (i.e. cf ssh) PASW 2.2 .profile.bat scripts Additional IIS feature support PASW 2.3 (Shipped on Monday!) Supporting Windows Server, version 1803 Multi-buildpacks integrations Ephemeral disk size selection .NET Features URL rewrite module Virtual directories HTTP compression module Dedicated file system User-scoped registry access Windows Operations PCF-compatible security hardening Administrator password management Windows Event Logs forwarding via syslog KMS activation RDP support
  48. 48. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How does it work?
  49. 49. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Windows Versions Windows Server 2012 R2 ●Released in Oct 2013. ●Notable improvement over Windows Server 2012. ●No containerization features. ●Supported by Pivotal as a BOSH Stemcell since April 2017. ●Microsoft mainstream support ends in Oct 2018. ●End-of-availability status for Pivotal products.
  50. 50. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Windows Versions Windows Server 2016 ●Released in Oct 2016. ●Introduced Windows Server Containers. ●4.5GB container image. ●5 years mainstream support + 5 years extended. ●Not for use with PASW. Windows Server 2012 R2 Windows Server, version 1709 ●Released in Oct 2013. ●Notable improvement over Windows Server 2012. ●No containerization features. ●Supported by Pivotal as a BOSH Stemcell since April 2017. ●Microsoft mainstream support ends in Oct 2018. ●End-of-availability status for Pivotal products. ●Released Oct 2017. ●Available as a “Server Core” version, a leaner image w/ a minimal UI. ●Containers can recover from conhost exploits. ●Improved container networking capabilities. ●Smaller container base image (2.2GB). ●18 months support. ●Supported in PASW 2.1 + 2.2 ●Released May 2018. ●Containers now have network access control lists (ACLs), meaning better container security. ●New system events give insights into container lifecycle for apps. ●Even smaller container base image (1.6GB). ●Supported in PASW 2.3 Windows Server, version 1803
  51. 51. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Windows Versions Windows Server 2016 ●Released in Oct 2016. ●Introduced Windows Server Containers. ●4.5GB container image. ●5 years mainstream support + 5 years extended. ●Not for use with PASW. Windows Server 2012 R2 Windows Server, version 1709 ●Released in Oct 2013. ●Notable improvement over Windows Server 2012. ●No containerization features. ●Supported by Pivotal as a BOSH Stemcell since April 2017. ●Microsoft mainstream support ends in Oct 2018. ●End-of-availability status for Pivotal products. ●Released Oct 2017. ●Available as a “Server Core” version, a leaner image w/ a minimal UI. ●Containers can recover from conhost exploits. ●Improved container networking capabilities. ●Smaller container base image (2.2GB). ●18 months support. ●Supported in PASW 2.1 + 2.2 ●Released May 2018. ●Containers now have network access control lists (ACLs), meaning better container security. ●New system events give insights into container lifecycle for apps. ●Even smaller container base image (1.6GB). ●Supported in PASW 2.3 Windows Server, version 1803 ●Released Oct 2018. ●Next LTSC release of Windows. Successor to 2016. ●Expecting stabilized, documented container APIs and improved container networking. Windows Server 2019
  52. 52. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW support for Windows versions Windows Server version 1709 + 1803 The releases currently supported by PASW. The “Semi-Annual Channel” (SAC) is a new servicing channel that offers a new release of Windows Server every 6 months. Each release contains significant new features and improvements, especially to containerization, needed for PASW. Windows Server 2016 + 2019 The Long-Term Servicing Channel (LTSC) releases ship every 2-3 years, 5 years mainstream + 5 years extended support. While Windows 2016 presented challenges for PCF, Windows Server 2019 aims to stabilize the container APIs, which we plan to leverage starting with PASW 2.5. Ongoing support is still TBD. (Your insights and feedback welcome!) LTSC SAC v1709 v1803 2016 Sept 2017 Sept 2018 March 2018 Sept Windows Server 2019 Windows Server 2016 (v1607) 2.1 2.2 2.3 2.4 2.5 2.6 2019 March v1903 TBD TBD
  53. 53. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How does the Windows stack work? cf push -s windows2016 -b hwc_buildpack PAS tile deployment PAS for Windows tile deployment Linux Diego Cells Windows Diego Cells CAPI Diego cf push -s cflinuxfs3 GoRouter TRAFFIC
  54. 54. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Anatomy of a Windows Diego Cell Guardian BOSH Agent + BOSH DNS server Garden server rootfs plugin container plugin network plugin Diego Rep Metron Agent Consul Client Local Route Emitter Windows containers • • •
  55. 55. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How PASW builds containers… Your .NET build artifacts + Web.config Platform Blobstore HWC Buildpack Droplet Windows staging container Windows Diego cell PS> cf push Diego Auctioneer Windows Diego cell hwc.exe Cloud Controller Is there a cell available to run this workload? Then…
  56. 56. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Anatomy of a PASW container Windows Server Core container base image Common Windows features (.NET, HWC, etc.) Config Utilities (git, tar) Windows Server Container Common .NET modules (URL rewrite, HTTP compression), etc. Buildpacks App Droplet Staging The root file system, or “rootfs.” Resulting container image at runtime.
  57. 57. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Windows Server Containers 5 7 Container Base Images Windows Server Core - Effectively a full OS (≈ 1.6 GB image) - Can support .NET Framework and .NET Core Nano Server - Minimal OS image with small surface area - Faster startup, smaller size (<100 MB) - “Like Alpine Linux” - Only .NET Core and Windows executables OOTB Isolation Types Windows Server Container - Shared kernel using one of the base images - Leverages HCS and HNS Windows Server Container with Hyper-V Isolation - Dedicated kernel - Effectively wraps a single container in a small VM - Uses Hyper-V nested virtualization - Only supported by MSFT on Hyper-V and Azure - Larger container overhead + longer startup time - Originally designed for untrusted, multi-tenant workloads
  58. 58. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs
  59. 59. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs .NET App Container Structure BOSH Windows VM host dependencies PASW Platform
  60. 60. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs .NET App Container Structure BOSH Windows VM host dependencies PASW Platform 12-Factor Applications Cloud-Native .NET Practices Bin-deployable dependencies
  61. 61. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs .NET App Container Structure BOSH Windows VM host dependencies PASW Platform 12-Factor Applications Cloud-Native .NET Practices Bin-deployable dependencies Extension buildpacks (yours and vendor-provided)
  62. 62. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs .NET App Container Structure BOSH Windows VM host dependencies PASW Platform 12-Factor Applications Cloud-Native .NET Practices Bin-deployable dependencies Extension buildpacks (yours and vendor-provided) BOSH add-ons
  63. 63. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ How You Can Adapt the Platform to Your Needs .NET App Container Structure BOSH Windows VM host dependencies PASW Platform 12-Factor Applications Cloud-Native .NET Practices Bin-deployable dependencies Extension buildpacks (yours and vendor-provided) BOSH add-ons Work with us! We continue to improve the platform based on your feedback.
  64. 64. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The Future…
  65. 65. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The Future of .NET and Windows on PCF Pivotal continues to invest in advancing the cloud-native future of .NET and Windows. PCF is building an aspirational combination of Microsoft’s aspirations and emerging OSS technologies and patterns.
  66. 66. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PCF brings the best of OSS to .NET
  67. 67. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ 2018 Investments Platform Automation Provide the best experience to deploy PASW on multiple foundations and customizing stemcells. Container Workload Strategy Legacy are better suited for containerized deployment patterns. .NET AppTx Success Drive a vision for how cloud-native .NET applications can be deployed on PCF. Developers App Operators Platform Operators Retire 2012 R2 Ensure we’re providing the best product possible for our customers. Expand New IaaSes Aim to support soverign clouds, OpenStack, Azure Stack, and other infrastructure options. Ongoing Security Improvements Windows Security is a critical component of operating the platform. Security Infrastructure Stability
  68. 68. Unless otherwise indicated, these slides are © 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ PASW Roadmap + Aspirations 6 8 PKS with Windows workers Envoy-based route integrity Istio-powered microservices Visual Studio Integrations PASW 2.4 and beyond Support for Envoy proxy and route integrity Improved container configuration Apps take advantage of a shutdown grace period Support for Windows Server 2019 Extension buildpacks for APM agents and other partners
  69. 69. > Stay Connected. Reach out to us! Let’s build this platform together. Your Pivotal account team + Cloud Foundry OSS Slack. #springone@s1p

×