Cloud Foundry - Going Cloud Native With Cloud Foundry

Going Cloud Native with Cloud Foundry@chipchildersChip Childers, VP TechnologyCloud Foundry Foundation

Why does Cloud Nativematter?

Since 2000, 52% of the Fortune500 are no longer on the list

Continuous Innovation

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure (cattlenot pets). And so on.Stephen O’Grady, -native-implications/

There is a rough consensus on many Cloud Native traits.Containers as an atomic unit, for example. Micro-servicesas the means of both construction and communication.Platform independence. Multiple language support.Automation as a feature of everything from build todeployment. High uptime. Ephemeral infrastructure(cattle not pets). And so on.Stephen O’Grady, -native-implications/

The Cloud Native Advantage:Simple PatternsHighly AutomatedScaled with Ease

Fast, Safe, Scalable Pick 3

Fast – Focus on Takt TimeDefinition: the desired time between units of production output,synchronized to customer demandhttp://www.strategosinc.com/takt time.htm

SafeA.B.T. - Always Be Testing (automatically)

Safe – Runtime Characteristics Matter Visibility – Measure all the things. Translate data into knowledge. (see:OODA loop) Fault Isolation – Smaller applications, released independently, isolate thescope of a fault condition. Fault Tolerance – Failures happen (see: Circuit Breaker Pattern / Designfor Failure) Autonomic Recovery – Humans have better things to do at night

Scale – Prepare (as best you can) to Succeed Demand elastic infrastructure Separate concerns - Isolated ephemeral services, Solve persistenceindependently Accept that the scalability of a system can be a series of plateaus

“Any organization that designsa system (defined broadly) willproduce a design whosestructure is a copy of theorganization's communicationstructure.Melvyn Conway, 1967

Microservices are great, but they require:rapid provisioningbasic monitoringrapid application deploymentdevops cultureMartin Fowler

Use declarative formats for setup automation, to minimize timeand cost for new developers joining the project;Have a clean contract with the underlying OS, offering maximumportability between execution environments;Are suitable for deployment on modern cloud platforms, obviatingthe need for servers and systems administration;Minimize divergence between development and production,enabling continuous deployment for maximum agility;And can scale up without significant changes to tooling,architecture, or development practices.

But even that’s not enough

Role based access to resources: the rightpeople should be able to do things and thewrong people shouldn’tRun specified bits on demand: take code,put it together with all the rest of the thingsit needs and and get it runningCoordinate cross service configurations: ina service oriented world, services need tobe configured to connect with each otherRoute public requests to running bits: thenext big thing needs access to the internetRead and write persistent data: data has tolive somewhere Add and remove resources: scaling is agreat problem to have, but still Isolate resources and failures withoutisolation and decoupling, that is one bigdistributed single point of failure Measure performance/health: can’t managewhat you don’t measure Detect and determine failure: sometimes,things get real but how do you know Recover failures: someone is going to haveto clean this mess Work tomorrow: when everything you’vethought to be true has been shown not to

You must be this tall

We’re going to need a platform

Unit of ValueIaaS Virtual Machine Opaque to the system Orchestration is post-hoc System changes areimperative (“launch” stuff)App Platform Application Containers are transparent Lifecycle is fully managed System changes aredeclarative (manifest.yml)

Unit of ValueIaaS Virtual Machine Opaque to the system Orchestration is post-hoc System changes areimperative (“launch” stuff)App Platform ApplicationTime to release a feature or App Containers are transparent Lifecycle is fully managed System changes aredeclarative (manifest.yml)

Platforms make promisesConstraints are the contractthat allows a platform to keeppromises

Here is my source codeRun it on the cloud for meI do not care howCloud Foundry HaikuOnsi Fakhouri

End UsersElastic leIoT DevicesBuildpackDockerRocketCore Services(MySQL / RiakCS)Provider-SpecificServicesUser ProvidedService itoringAWSOpenStackVMwarevSphereOther

Turning this:.warInto rvicemanifestDBMulti- ‐serverruntimeenvironment(s)

Or even this ops/

BUILDAPPLICATION Self-serviceremoval A/B versioning Live upgradesRETIREAPPLICATIONSUPDATEAPPLICATIONS Auto-detect frameworks Link to App Platform Self-service deploy Dynamic routingPUSH FIRSTRELEASEMAINTAINAPPLICATION Elastic scaleIntegrated HALog aggregationPolicy and Auth

cf target mycf push myapp create-service myservice bind myapp myservice start myapp scale myapp -i 100 LBAppAppDBApp

Where’s the container in thisstory?

What is a “Container”? PIDUser cgroupscflinuxfs2 NetworkIsolation RulesContentsProcesses

Let’s talk about Buildpacks / Staging Ruby code that detects language,frameworks, whatnot Compiles the code into executablebinaries (*)/bin/detect Am I supposed to run?/bin/compile Build the thing/bin/release Pass along potential metadatacflinuxfs2

.next

RONOSrunC

iegoCoreServicesetcdService gatorCHRONOSCloud ControllerAuth

reServicesetcdService gatorCHRONOSCloud ControllerAuth

That was all about 12 factorapps What about services?

CF and Services- Development infrastructure components(DBs, Cache, Queue, etc )- Loopback to other CF hosted apps- Reaching out to your “legacy”- External providers

Turning this:.warInto rvicemanifestDBMulti- ‐serverruntimeenvironment(s)

The Cloud Native Advantage:Simple PatternsHighly AutomatedScaled with Ease

cloudfoundry.org

Cloud Foundry Foundation Going Cloud Native with Cloud Foundry. Why does Cloud Native matter? Since 2000, 52% of the Fortune . Continuous Innovation. There is a rough consensus on many Cloud Native traits. Containers as an atomic unit, for example. Micro-services as the means of both construction and communication. Platform independence .