Provisionr Proposal

Abstract

Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds in an automatic or semi-automatic fashion.

Proposal

Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward & reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc.

As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above.

Background

• cloud native apps
• advanced automation
• semi-automated workflows
• common API = hard to win battle

Rationale

Before configuring any kind of service we need to provision a set of machines.

Initial Goals

• build a community
• add support for more providers
• provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck)

Current Status

Meritocracy

Community

The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure.

Core developers

Alignment

Provisionr complements Whirr and later on it should provide a robust foundation for advanced functionalities.

Known Risks

Orphaned products

Inexperience with Open Source

Homogenous Developers

Reliance on Salaried Developers

Relationships with Other Apache Products

A Excessive Fascination with the Apache Brand

We think that Provisionr will benefit from the community sharing ideas and best practices for running cloud services. The ASF does a great job at building communities, which is why we want to build Provisionr at Apache.

Documentation

Initial Source

Available on GitHub: https://github.com/axemblr/axemblr-provisionr

Source and Intellectual Property Submission Plan

We are going to prepare a software grant as needed.

External Dependencies

Cryptography

Required Resources

Mailing lists

• provisionr-private
• provisionr-dev
• provisionr-user

Version Control

Git repository

Issue Tracking

JIRA Provisionr (PROVISIONR)

Other Resources

The existing code already has unit and integration tests so we would like a Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation.

Initial Committers

• Andrei Savu
• Ioan Eugen Stan
• Alex Ciminian

Sponsors

Champion

Andrei Savu - asavu at apache dot org

Nominated Mentors

• Tom White - tomwhite at apache dot org

Sponsoring

Incubator PMC