Cloud Foundry Advisory Board Meeting, March 2017: Mantra, Dingo PostgreSQL

200+ CF summit proposals

IBM’s Michael Maxmilien (aka Dr. Max) said there were more than 200 submissions for the upcoming Cloud Foundry Summit, to be held June 13–15 in Santa Clara, as he led the monthly Cloud Foundry Community Advisory Board (CAB) call.

“It will be a very exciting summit, maybe the best we’ve had,” he said. The Call for Papers is now closed, accepted speakers are scheduled to be notified the week of March 27, and the conference agenda is scheduled to be published the week of April 3.

Altoros and Stark & Wayne presented short demos during this month’s call, and there were also a few technical updates.

 

Mantra

Alexander Lomov from Altoros tackled the subject of Manifest Transformation in BOSH called “Mantra.”

Mantra enables users to:

• find manifest parts
• extract cloud configs for BOSH v2 from BOSH v1 manifests
• convert v1 manifests to v2
• convert manifests into BOSH-CLI templates

Alex said it is desinged to be easily extendable, so users can add new commands and transforms themselves.

GitHub repo

 

Dingo PostgreSQL

Dr. Nic Williams from Stark & Wayne demoed what he calls Dingo PostgreSQL, which he described as “a BOSH-deployed PostgreSQL service broker for Cloud Foundry. Each service instance is a highly available pair of Docker containers running PG, with continuous archiving and BOSH-run errand disaster recovery.”

GitHub repo

 

Diego

Pivotal’s Eric Malm reported on three developments:

• Efforts continue to extract Cloud Foundry from the Consul dependency. Some more testing needs to be done.
• The team is integrating with a new locket component that manages all of the image layers for containers on the cells part of runC, something that is “progressing nicely.”
• Integrating with new the Loggregator API, not fully stabilized yet, but can at least be used for app logs and container metrics. Have a track to pass to other diego components.

GitHub repo | Pivotal Tracker

 

CAPI

Pivotal’s Dieu Cao had a brief report, with a few items:

• The team members are working with the Diego team on eliminating the Bridge components. They are targeting v255 to eliminate all the remaining elements.
• There’s work being done with the CLI team on how to expose building blocks in v3 GA.
• Runtime projects are also moving away from Consul and etcd.

GitHub repo | Pivotal Tracker

 

BOSH

The BOSH team submitted a report with several items:

• Continuing to work on the config server integration, almost there.
• CF-deployment with the CredHub integration instead of a temporary CLI workaround.
• CredHub integration will be soon documented and announced in the next major BOSH release.
• Moving around a lot of repos.
• Stemcell versions will be moved out.
• Bosh.io will continue to be updated.
• Kicked off work to do DNS stage 2, which brings closer to links and DNS support—the latter will unblock removal of Consul usage.
• CLI v2 is about to be announced, with perhaps one remaining story to switch over BOSH acceptance tests to switch over the CLI.

GitHub repo | Pivotal Tracker

 

CF-Extensions and the next call

Dr. Max reported progress on the CF-Extensions project that he’s leading, noting some interesting ideas, including one of a Unikernel.

The next CAB call is scheduled for Wednesday, April 19 at 8 a.m. Pacific Time. The calls are open to anyone. People who are interested in participating in Cloud Foundry are encouraged to register to the community’s Slack channel.

 

Related video