Marketplace is a key CF differentiator

enterprise use cases and community strengths

Guillaume Berche, Orange�Feb 17th 2021

Agenda

1. CF Marketplace primary use cases still unrivalled
1. CF marketplace use-cases strengths and limitations
2. OSS alternatives
3. Osb-to-helm-poc�
2. Other additional valuable use-cases to enterprise market
• Osb-cmdb: “Sharing a marketplace among multiple platforms”
• Unified on-boarding�
3. Conclusion/discussion

Agenda

• CF Marketplace primary use cases still unrivalled
• CF marketplace use-cases strengths and limitations
• OSS alternatives
• Osb-to-helm-poc�
• Other additional valuable use-cases to enterprise market
• Osb-cmdb: “Sharing a marketplace among multiple platforms”
• Unified on-boarding�
• Conclusion/discussion

CF Marketplace primary use cases still unrivalled

Use cases: consume managed services from app workloads

• Discover offers
• Service definition
• Service plan & metadata
• Service plan visibility within orgs
• Provision
• Params
• Dashboard SSO + AuthZ (read/manage)
• Quotas
• Update plan, maintenance upgrade
• Share service instance
• Bind
• Credentials
• Route service
• Syslog drain
• Unbind
• Unprovision

😃

Simple UX

Consistent across services

​

😴

Send annotation to brokers

Service logs

Service metrics

Backup/restore 1st class UX

Composition

Stop/start, hibernate/resume

​

CF Marketplace primary use case: OSS alternatives

1st class K8S CRs

& “operator packaging” E.g. OLM

|| “helm chart packaging”

​

Terraform module

& CR wrapping ? (See isaaguilar/terraform-operator )

​

​

K8S Service catalog (i.e. OSB api client in K8S):

CRs:

• Poor discovery UX

CLI:

• Incomplete feature coverage

UI:

• Missing from OSS community, see kubeapps/kubeapps/issues/2125
• Helm chart facade (Osb-to-helm-poc)

​

​

​

Osb-to-helm-poc: Helm facade to service catalog

Goal: provide a web UX to consumme OSB API offerings in K8S

• Discovery
• Provisioning
• Service plan completion
• Service parameter forms
• Dashboard URL access
• Binding / Unbinding
• Service instance update/upgrade
• Deprovisionning��How: dynamically generate helm chart from OSB catalog. Helm chart provisions service catalog CRs�https://github.com/orange-cloudfoundry/osb-to-helm-poc

Service discovery in rancher UI

7

Service provisioning in rancher UI

8

Service provisioning in rancher UI

9

Service provisioning in rancher UI

10

Service provisioning in rancher UI

11

Dashboard access in rancher UI

12

Service instance in rancher UI

13

Agenda

• CF Marketplace primary use cases still unrivalled
• CF marketplace use-cases strengths and limitations
• OSS alternatives
• Osb-to-helm-poc�
• Other additional valuable use-cases to enterprise market
• Osb-cmdb: “Sharing a marketplace among multiple platforms”
• Unified on-boarding (thoughts)�
• Conclusion/discussion

Other additional valuable use-cases to enterprise market

• Marketplace shared among multiple platforms (CF foundations, K8S clusters, Iaas tenants): osb-cmdb
• Full slide deck
• https://github.com/orange-cloudfoundry/osb-cmdb
• “CF as an (OSB) database”

​

• “CF as IAM’: unified onboarding on multiple cloud hosting offers
• (Just thoughts so far)

Iaas

Maps cloud hosting offers onboarding/IAM

Agenda

• CF Marketplace primary use cases still unrivalled
• CF marketplace use-cases strengths and limitations
• OSS alternatives
• Osb-to-helm-poc�
• Other additional valuable use-cases to enterprise market
• Osb-cmdb: “Sharing a marketplace among multiple platforms”
• Unified on-boarding (thoughts)�
• Conclusion/discussion

OSB-CMDB: manage multi client platforms and multi service providers

18

On prem service providers

Public cloud service providers

Osb-cmdb:

Track and control

Iaas

On prem/ Public

xN

xN

xN

OSB API

OSB API

Why do we need an intermediate between osb clients and osb brokers ?

• Provide a consistent marketplace offering among multiple client platforms
• Get a comprehensive view of service usage among multiple client platforms

​

• More generally, provide common operability to all OSB client and service providers
• Inventory
• Access usage history
• Traceability to client platforms, consumer users, apps
• Log OSB API calls received
• Control
• Ensure OSB API conformance (OSB API is versatile, e.g. K8S reconciliation loop and eventual consistency)
• Control service plan visibility.
• Set limits / quotas. �
• And more ?
• Soft delete / undelete ?
• Service instance/binding sharing among distinct client platforms ?
• Recharging ?

19

Osb-cmdb functional overview

20

Osb-cmdb leverages CF marketplace ecosystem

Osb-cmdb interactions with CF API

22

Typical cmdb-content

• One org per osb client (cf1, cf2, k8s1, k8s2, …)
• One space per service definition (mysql, cassandra, …)
• One backing service instance for each brokered service instance (guid1, guid2, …)
• One service key by service binding (guid1, guid2)

​

Osb-cmdb roadmap

See orange-cloudfoundry/osb-cmdb/projects/1

Full slide deck with detailed features and UX

​

Q: is there community interest for CFF incubation into extension PMC ?

Agenda

• CF Marketplace primary use cases still unrivalled
• CF marketplace use-cases strengths and limitations
• OSS alternatives
• Osb-to-helm-poc�
• Other additional valuable use-cases to enterprise market
• Osb-cmdb
• Unified on-boarding�
• Conclusion/discussion

Unified onboarding overview

Unified onboarding: 2- Declare project / self-training

27

Unified onboarding: 2- Declare project / self-training

28

Dashboard brings to organization page, e.g. https://stratos.redacted-domain.org/cloud-foundry/-o1F0L956QhAIK7R56Uc1lMh5L4/organizations/d3bf122e-8539-42cd-af11-8d91c4f66b61/summary

Unified onboarding: 3- Declare project members

29

Unified onboarding: 2- Declare project / self-training

30

Provisions project

Recap

1. Project subscription in unified onboarding
1. Team members definition and role assignment
2. Cloud hosting subscription
• CloudFoundry tenant�(org/space)
• K8S on prem / public tenant (namespace)
• K8S onprem /public cluster
• Iaas tenant
3. Data service subscription within cloud hosting
4. Data service console access from project team
5. Governance perspective

​

31

Unified onboarding: 3- Subscribe to cloud offers

​

​

32

Unified onboarding: 3- Subscribe to cloud offers

​

​

33

Unified onboarding: 3- Subscribe to cloud offers

​

​

34

Dashboard brings to cloud app hosting offer (aerofoundry) welcome page.

​

Members are provisionned and can login (SSO or login/password with corporate identity)

Unified onboarding: 3b- Review/track

​

​

35

Org view lists spaces, users, and total subscriptions

Services view with filtering by org and space:��Tracks subscriptions

Unified onboarding: 3- Refresh cloud offers subscriptions

​

​

36

1. [Update project members]
2. Refresh cloud offers subscriptions

Recap

• Project subscription in unified onboarding
• Team members definition and role assignment
• Cloud hosting subscription
• CloudFoundry tenant�(org/space)
• K8S on prem / public tenant (namespace)
• K8S onprem /public cluster
• Iaas tenant
• Data service subscription within cloud hosting
• Data service console access from project team
• Governance perspective

​

37

Architecture and software design

38

Osb-cmdb

CF CAPI

Stratos UI�(CF)

GCP terraform provider�

Cloud service broker

AWS/Azure/ OVH terraform provider�

K8S terraform provider�

K8S CR / operator�(e.g google GCC)

Onboarding IAM/UI

Cloud Service Providers

Orange

CSP

CF vendors

K8S community

CF community

K8S vendors

Orange� (to create)

OSB API

K8S client

(svcat)

Osb2 helm

Helm chart UI (kubeapp�/openshift/�rancher)

App hosting platforms: Paas, Caas, Iaas�

OSB API

OSB API

CF OSB client

Stratos UI�(CF)

CF OSB client

Stratos UI�(CF) ?

IAAS UI (VRA/�Openstack Horizon)

Iaas vendors

Cloud service broker

K8S terraform provider�

CF terraform provider�

Iaas terraform provider�

Onboarding service brokers

Onboarding brokerpak

Data service brokers

OSB API

CC API: �use CF as IAM

Agenda

• CF Marketplace primary use cases still unrivalled
• CF marketplace use-cases strengths and limitations
• OSS alternatives
• Osb-to-helm-poc�
• Other additional valuable use-cases to enterprise market
• Osb-cmdb
• Unified on-boarding�
• Conclusion/discussion

OSB ecosystem provides strong value to the enterprise market

​

​

• CF service api V3 and SAPI backlog, e.g.
• OSB 2.16 support (CF annotation in CF context)
• stratos CF marketplace support
• cf-java-client V3 api support
• cloud-service-broker (terraform ecosystem)
• K8S OSB client
• Svcat
• K8S svcat ui: Osb2Helm
• OSB brokers deploying K8S resources
• Service-fabrik-broker
• cloud-service-broker
• + terraform-provider-kubernetes-alpha ?
• + terraform-provider-kubernetes (see GSA/eks-brokerpak example)
• + terraform-provider-helm (see issues/114 )
• Mini-broker
• Others ?

​

Discussion

Do Orange use-cases also apply to other enterprise customers ?

Can CFF downstream vendors also leverage OSB/CF marketplace to serve their enterprise customers “advanced marketplace use cases” ?

Can these enterprise use cases help fueling maintenance of CF marketplace differentiating features ?