Cloud Foundry Advisory Board Meeting, Sep 2018: Service Fabrik 2.0

by Roger StrukhoffSeptember 20, 2018
The major updates included CFCR going BOSH-native (enabling multi-master Kubernetes setups) and the release of Service Fabrik 2.0.

The ongoing confluence of Cloud Foundry and Kubernetes was a key topic during this month’s CF Community Advisory Board (CAB) call. Other highlights included a new Service Fabrik demo, the latest project reports, and conversation about the upcoming Cloud Foundry Summit Europe 2018, to be held in Basel, Switzerland, October 10–11.

September’s CAB call in progress (Image credit: Swarna Podila)

The call was held on Wednesday, September 19, and was led by Michael Maximilien (aka Dr. Max) of IBM.

 

CFCR steers toward BOSH-native

Urvashi Reddy

Urvashi Reddy of Pivotal led the discussion around Cloud Foundry and Kubernetes. She represented the team responsible for Cloud Foundry Container Runtime (CFCR), members of which are located primarily in Dublin, with Urvashi in San Francisco and another team member in Portland.

CFCR was originally called Kubo (a portmanteau of Kubernetes and BOSH), with the original mission “to package Kubernetes into a BOSH release,” Urvashi said. “We thought we were letting people install Kubernetes, but we were just one of many installers in the community,” she added. “And, by abstracting the BOSH layer, we were actually doing a disservice to BOSH developers who wanted to use Kubernetes. So, we decided to be more BOSH-native.” Urvashi also noted the existence of some remaining technical debt from original efforts to abstract BOSH away from developers.

The current activities include a continued focus on the BOSH-native experience for developers, enabling secure clusters through PodSecurityPolicy and creating back-up and restore capabilities. According to info provided on CFCR’s GitHub repo, the back up takes an etcd snapshot without interruptions to the cluster. For restore, it takes both the kube-apiserver and etcd offline to restore the cluster with the specified snapshot, as restore is a destructive operation that overwrites existing data on the cluster.

The current efforts mean to provide functionality for multi-master Kubernetes setups in addition to a currently available single-master enablement. Up next, according to Urvashi, is the integration with Azure and enabling the rotation of certificates.

CFCR’s GitHub repo

 

Service Fabrik 2.0 outlined

Subhankar Chattopadhyay

The team of SAP Bangalore responsible for Service Fabrik—a multi-cloud provisioning broker—also made a presentation during the call, a year after first presenting it to the board. A CAB call of July 2018 also featured an update around Service Fabrik’s fault-tolerance capability.

This time out, Subhankar Chattopadhyay went over the latest release—Service Fabrik 2.0. He said key aspects of the release include:

  • reduced platform dependency by maintaining a minimal state in the broker
  • integration of a new provisioner
  • easy pluggability for monitoring and logging through an event-driven architecture
  • a built-in back-up mechanism

Service Fabrik’s high-level architecture shows operators (whether BOSH, Docker, or something else) interacting API servers to reach the actual, consuming platforms (e.g., Cloud Foundry or Kubernetes).

Service Fabrik’s high-level architecture (Image credit)

Subhankar pointed out that new operators can be written in any language, “enabling polyglot programming and in a way helping open-source contributions.” He also said it is easy to integrate new components for additional functionality any particular developers and companies may want.

A live demo showed how Service Fabrik can be spun up through cf-services.

Spinning up Service Fabrik through cf-services

Service Fabrik’s GitHub repo

 

Kubernetes consulting for the insurance sector.

Runtime PMC

Eric Malm

Eric Malm and Dieu Cao of Pivotal provided a list of several recent developments:

Dieu Cao

Eric noted that routing has hit “a big milestone with Istio” and can now support 500 apps with 500 routes.

Dieu added that the CAPI team is “setting a timeline for deprecating v2 endpoints and hopes to communicate about this more widely soon.”

Runtime PMC’s GitHub repo

 

BOSH

Frederic Desbiens

Frederic Desbiens of Pivotal reported the following BOSH developments:

  • Huawei CPI proposal under discussion with a vote coming soon.
  • A few CPIs have graduated and moving from CF Incubator to BOSH.
  • The team has kept busy with various small features, new improvements to DNS, and drain scripts.

BOSH’s GitHub repo

 

CF Extensions/Abacus

Dr. Max

Dr. Max of IBM made a final project note, about CF Extensions, commenting that the Abacus team has submitted a proposal for a usage sampler API that is now open for viewing.

CF Extension’s GitHub repo | Abacus GitHub repo

 

Gathering in Basel

Swarna Podila

Swarna Podila from the Cloud Foundry Foundation reminded everyone that the European summit is almost here and has 710+ registrations to date. In addition to the full two-day program, there will be an announcement of community awards and several activities on October 9, the day before the conference officially opens.

The Foundation has also announced next year’s North American Summit, to be held in Philadelphia on April 2–4, 2019. The call for papers is now open!

Next month’s call will be held at the Europe summit, on Thursday, October 11, at 3 p.m. in the Rio room at the show’s venue, the Congress Center Basel. All are welcome to attend.

 

Want details? Watch the video!


This post was written by Roger Strukhoff and edited by Sophie Turol, Carlo Gutierrez, and Alex Khizhniak.
Get an ultimate architect's guide to understand what you need for a successful Cloud Foundry implementation

To stay tuned with the latest updates, subscribe to our blog or follow @altoros.

  •  
  •  
  •  
218