PCF Features for Improving Dev-Ops goals of : 1.Developer Self-Svc 2.Incremental Deploys 3.Fas...

Jetzt loslegen. Gratis!
oder registrieren mit Ihrer E-Mail-Adresse
PCF Features for Improving Dev-Ops goals of : 1.Developer Self-Svc 2.Incremental Deploys 3.Fast Feedback 4.Continuous Learning and 5.Refactorability von Mind Map: PCF Features for Improving Dev-Ops goals of :  1.Developer Self-Svc  2.Incremental Deploys  3.Fast Feedback  4.Continuous Learning  and   5.Refactorability

1. CLI

1.1. Developer Friendly & lower friction

1.2. Works like other tools

1.3. Works with other tools(e.g. git)

1.3.1. Maven

1.3.2. Gradle

1.3.3. Jenkins

1.3.4. STS (Eclipse)

2. Services Marketplace and framework for Dependencie mgmt

2.1. Clear visibility of dependencies

2.2. Supports provisioning -if needed

2.3. Services can be used across languages

2.4. Not tied to hardware/network/install decisions

2.5. Applications can be added as Services to Marketplace

3. Org & Account Isolation

3.1. Flexible mapping of your org and projects and environments

3.2. Not tied to hardware/network/install decisions

4. Container Isolation for Apps

4.1. Every App gets its own stack and container

4.2. Repeatable across "Pushes" and Instances and upgrades

4.3. Network isolation is supported via groups

4.4. No changes required for Microservices

4.4.1. Microservices support smaller increments of Development, Testing, and Deployment for Rapid Learning

5. 4 Levels of HA

5.1. VM restarts

5.2. Health manager restarts failed container

5.3. Availability Zones

5.4. Bosh management of ER processes

6. Structure vs Unstructured Platform

6.1. PCF is a structured platform

6.2. DevOps for Unstructured will need to support higher variance of process

6.3. PCF implies an agreed contract between dev and infra. That allows us to keep our promises. One of our promises is the most simplistic DevOps where a Service (app) is the top of the hierarchy instead of a Server being top of hierarchy.

7. Route Managment

7.1. manage routes independently of Apps

7.2. Blue-Green deployment

7.3. Canary deployment

7.4. GEO-Distributed architectures

8. Polyglot support

8.1. Support for mixed-skill teams

8.2. Experimentation has a lower Risk and Cost

8.3. Migration and Using the Best Language for the App is supported.

9. CF Push

9.1. All deployment concerns are handled by a single command + simple YAML manifest

10. Cloud Agnostic

10.1. CF runs apps the same in every cloud...and apps are easily moved

11. Log Aggregation

11.1. All relevant log data for an app is aggregated for easy visibility