A Unikernel Compiler (UniK) Added to the Cloud Foundry Extensions Incubation
An initiative called CF-Extensions is a new idea from IBM Chief Architect of PaaS Innovation Michael Maximilien (a.k.a. Dr. Max), launched late in 2016 and starting to gain some traction within the Cloud Foundry community.
The UniK compiler is unique
There are now several projects in incubation, covering a wide range of services and functions. The latest is a unikernel compiling tool called UniK (pronounced like “unique”), which works with several unikernels and cloud providers. UniK has been offered up by Dell EMC.
There has been some talk of unikernels, which are lighter and perhaps more secure than containers, in recent years. They are described in the Dell EMC proposal as “lightweight, immutable operating systems compiled specifically to run a single application.”
UniK produces lightweight, bootable machine images that can run directly on hypervisors or bare metal, with no need of Linux (or other host OS).
UniK currently supports the following unikernel types:
It can manage instances locally, as well as with several cloud providers: VirtualBox, AWS, Google Cloud, vCenter, QEMU, UKVM, Xen, OpenStack, and Photon.
The proposal says UniK’s developers wanted to integrate with Cloud Foundry “to leverage its higher-level features like management, monitoring, and health.”
CF-Extensions projects in incubation
The CF-Extensions project has embraced some initiatives that have been around for awhile (such as Abacus and buildpacks), as well as newer ideas. The projects currently in incubation within CF-Extensions include:
Abacus. This is described as “a metering engine for Cloud Foundry.” It was put forward by IBM and “allows accumulation, aggregation, and queries of usage information from the Cloud Foundry runtime, as well as any compliant service broker. Abacus is currently deployed in IBM Bluemix and SAP HANA.”
AutoScaler. This is another project from IBM, which “provides the capability to adjust the computation resources for Cloud Foundry applications through: a) dynamic scaling based on application performance metrics, and b) scheduled scaling based on time,” according to its proposal. Any application bound with the CF-AutoScaler service can use it.
Brooklyn Broker. This project was proposed by Cloudsoft, and is described as “a service broker that allows services to be defined using OASIS CAMP blueprints and deployed and managed by Apache Brooklyn.” It is currently deployed in the certified Atos Cloud Foundry distro. (Previously, we’ve covered the Brooklyn plugin.)
Notifications. This idea comes from Pivotal; the project “deploys the Cloud Foundry notification service as an application onto the Cloud Foundry platform. A running CF (with UAA) and a MySQL instance are required to deploy notifications.”
MS SQL Broker. This is a Go-based broker for the MS SQL service. According to its proposal, “it implements and exposes the Cloud Foundry Service Broker API to facilitate the management of a single Microsoft SQL Server instance. The minimum version supported is SQL Server 2012 Express. The broker service does not need to save any state, thus it can be farmed or deployed on another box without any data migration.“
Dr. Max continues to encourage members of the Cloud Foundry community to make incubation proposals for CF-Extensions. He also holds conference calls, with the next one scheduled for Monday, April 24, at 11 a.m. Pacific Time.
- Cloud Foundry Advisory Board Meeting, Jan 2017: CF Summit’s CFP Is Open
- Cloud Foundry After Dark: Bridging Brooklyn
- Creating a Sample Service Broker for Cloud Foundry with Python’s Flask