-
Notifications
You must be signed in to change notification settings - Fork 31
How to add a new Cloud Foundry service
mrdavidlaing edited this page Mar 6, 2013
·
7 revisions
TODO: Add link to CloudCredo QCon London presentation that this info taken from
If you have an existing service you can run it alongside your Cloud Foundry installation, and have your Cloud Foundry apps access it
Pros:
- Nothing new to do!
Cons:
- Manual provision
- Credential management
- Cloud Foundry facade over an existing external service
Pros:
- Use existing service
- Credential management
Pros:
- First class service support
Cons:
- Development overhead writing tight integrations
Implemented in Ruby
See architecture diagram from slides:
Gateway - records which node a service is running on
- Extend existing CF class (eg, CassandraGateway)
- Configure cloud controller to know about new gateway
- Advertised by vmc
Node - adapter between Cloud Foundry and service being running
Must implement Service Node API
- provision / unprovision
- bind / unbind - create credentials, create DBs, cleanup
- enable_instance / disable_instance
- announcement - advertise data to rest of Cloud Foundry services - eg, capacity remaining, memory etc
??
- backup for backup manager
- Unit (eg, rspec / minitest - logic valid, mocked out nodes)
- Integration (run against deployed nodes; DBs actually get created etc)
- Yeti - End to end testing - deploy application, ensure application runs as expected
- Stac2 - Load testing
- BOSH
- Chef
- No need to ask permission - if you want to make an edit or add a new section, just do it!
- The official cf-docs maintainers cherry-pick content from this wiki for the official docs
- The contents of this wiki are in no way endorsed, maintained or supported by the core Cloud Foundry team
- Development Process
- Mailing Lists & Chats
- CI and the Commit Pipeline
- Contributing Code or Docs
- Contribution Standards
- Design Documents
- Proposing New Features
- Adding New Services
- Project Incubator
- Reporting Security Vulnerabilities
- CFF vulnerability mgt
- CAB meeting minutes
See CFF official project list.
Roadmaps are reflected in pivotal trackers. Tracker Instructions and steps to watch stories. Here is a flat list of all trackers:
- BOSH
- BBR
- CF Abacus
- CF App Autoscaler
- CF Buildpacks
- Concourse roadmap, and milestones
- CF Containerization/quarks
- CF Container Networking
- CF CAPI
- CF API K8s Evolution
- CredHub
- CF CLI
- CF CLI V3 acceleration
- CF Diego
- CF Docs
- CF Eclipse
- CF Eirini
- CF Flintstone
- CF Foundation
- CF Garden
- CF Greenhouse (windows)
- CF GrootFS (aka Garden RootFs)
- CF Identity (aka UAA)
- CF Infrastructure (incls BBL)
- CF Java Buildpack
- CF Java Client
- CF Lattice
- CF Logging and Metrics
- CF MEGA (Release Integration)
- CF Networking - CF K8S
- CF Networking - CFAR Mesh
- CF Mysql (core services)
- CF Notifications
- CF Permissions
- CF Persistence
- CF Postgres-release
- CF Runtime OG
- CF Routing
- CF Routing TCP
- CF services API (aka SAPI)
- Cloud Service Brokers (by SAPI/service enablement team)
- Kubo
- License Finder
- BBR
- Buildpacks
- BOSH
- BOSH CPIs
- Cf Java Client
- Core services (mysql) - repo
- Garden
- Grootfs
- Infra/tools
- Java Buildpack
- Kubo - repo
- Loggregator
- Persistence
- Release integration - repo
- Routing
- Runtime - repo
- Service API (aka SAPI)
Maybe other CIs hosted on cf-app.com are mentioned in slack ?
- See Client Tools on docs
- 3rd Party Compatible Apps