2ee8f4e1e6
Using --no-cache-dir flag in pip install ,make sure dowloaded packages by pip don't cached on system . This is a best practise which make sure to fetch ftom repo instead of using local cached one . Further , in case of Docker Containers , by restricing caching , we can reduce image size. In term of stats , it depends upon the number of python packages multiplied by their respective size . e.g for heavy packages with a lot of dependencies it reduce a lot by don't caching pip packages. Further , more detail information can be found at https://medium.com/sciforce/strategies-of-docker-images-optimization-2ca9cc5719b6 Change-Id: I1281de6e297fdae73ea285b0c7ccc4db3d64123d Signed-off-by: Pratik Raj <rajpratik71@gmail.com> |
||
---|---|---|
reactive | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
LICENSE | ||
README.md | ||
config.yaml | ||
layer.yaml | ||
metadata.yaml | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
README.md
Overview
This layer provides the base layer for OpenStack charms that are will deploy API services, and provides all of the core functionality for:
- HA (using the hacluster charm)
- Juju 2.0 network space support for API endpoints
- Configuration based network binding of API endpoints
To use this layer, including the following in the layer.yaml of your charm:
include: ['layer:openstack-api']
And then read the new API charm guide for details on how to use this layer in-conjuction with the charms.openstack Python module to quickly and easily put together a new API charm.