Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Implementing "Undo" for Cloud Foundry Service B...

Implementing "Undo" for Cloud Foundry Service Brokers - CF Summit Frankfurt 2016

Dr Nic Williams

September 28, 2016
Tweet

More Decks by Dr Nic Williams

Other Decks in Technology

Transcript

  1. Plan  First-class love for databases Implementing “undo” Ǚ No

    CF CLI plugin required Example of Dingo PostgreSQL
  2.  For the love of databases 51 v3 API endpoints

    4 v3 APIs for service bindings
  3.  For the love of databases 172 cf commands 31

    cf commands for ‘services’
  4.  For the love of databases  Create service instance

    Bind to an application Unbind from an app Delete service instance Ǚ
  5.  For the love of databases Dz 0 commands for

    listing backups 0 commands for viewing DB logs 0 commands for health/monitoring ǟ 0 commands to “undo” mistakes Ǚ
  6.  For the love of databases TCP router is for

    apps Diego persistence is for apps  Loggregator is app centric CLI plugins decoupled from brokers Lj
  7. Problem ŏ Broker only receives UUIDs,
 not “production” provided by

    user ŏ Cloud Controller doesn’t remember 
 “production” after delete
  8. Implement broker 1 Receive service instance ID only 3 Look

    up service name from CF 2 Continue asynchronously 4 Cache service name
 independently of CF
  9. … Continuous archiving …  PostgreSQL write ahead logs (WAL)

    MySQL binary log files  MongoDB /dev/null Ǚ
  10. User Experience  User-initiated data recovery Continuous/near-real time archives …

     Users expect all data is recoverable  ȑ Native CLI experience would be much nicer please
  11. Future Auto-discovery of broker plugin Point in time recovery …

    CLI plugins for full experience Lj  Operator cleanup of legacy backups  Ǎ