Update on Cloud Foundry Isolation Segments (formerly Elastic Clusters)
summary
Feature lets a Cloud Foundry Space be explicitly mapped to an Isolation Segment so apps land on dedicated compute, routing, and logging components without full extra CF installs. Implementation adds Cloud Controller API and CLI commands, a new BOSH deployment pattern for separate cell pools, and initial work landed in Diego, cred and Cloud Controller. First milestone (compute + CLI) targets year end. Current requirement: Consul cross‑segment comms on specific ports/IPs.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:53The Problem
- 1:55Operational Concerns
- 3:29What is an Isolation Segment
- 3:46Name Change
- 4:27Cloud Foundry Deployments
- 5:19Creating Isolation Segments
- 7:00Isolation Segment UX
- 7:33Isolation Segment Exit
- 7:58Routers and Cells
- 10:18Logging
- 10:59Authentication Authorization
- 12:08Wrap Up
- 13:24Questions
related talks
37mStay Out of My Yard! Isolation Segments - a New Feature for Isolating Workloads in Cloud Foundry
30mWhat's New in the Cloud Foundry Ecosystem?
21mA Roadmap to Active Multi Cloud
33mCloud Foundry Runtime PMC Overview - Dieu Cao, Pivotal
03mCore Project Updates Track Introduction
01h 03mDeep Dive into Pivotal Cloud Foundry 2.0
02mCloud Foundry
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art