Brooklyn Container Service is a set of locations and entities for Apache Brooklyn that allow deployment of applications to container based locations. The locations provided use the jclouds Docker provider and the fabric8 Kubernetes client to give Brooklyn access to Docker Engine, Docker Swarm, Kubernetes and OpenShift. As well as these locations, entities that represent Docker containers and Kubernetes pods are included, which can be used to build applications. Blueprints for containerised applications can also be developed and deployed using the usual Brooklyn components. This is a useful addition to Apache Brooklyn and allows the project to extend its scope to include this essential part of the Cloud Native ecosystem.
The Apache Brooklyn PMC will be responsible for the code.
It will be integrated into the Apache Brooklyn project, into a new brooklyn-location-container module.
The following people will be managing this contribution:
Completed tasks are shown by the completion date (YYYY-MM-dd).
date | item |
---|---|
2017-06-05 | If applicable, make sure that any associated name does not already exist and is not already trademarked for an existing software product. |
date | item |
---|---|
2017-06-08 | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. |
2017-06-05 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. |
Identify name recorded for software grant: brooklyn-container-service
Corporations and individuals holding existing distribution rights:
date | item |
---|---|
2017-06-08 | Check that all active committers have a signed CLA on record. |
2017-06-08 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA. |
2017-06-07 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. |
2017-06-07 | Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. |
Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
Related votes held on the Apache Brooklyn dev list: