This patch aimed to reduce db call count when we invode k8sAPI.
For those user using bay name to do pod/rc/service operations, we
can saving a db call.
There are files containing string format arguments inside logging
messages. Using logging function parameters should be preferred.
Kubernetes Release 1.0 was announced at OSCON
A new Fedora Atomic image has been built with version 1.0.4 and
this series of patches will update the templates, scripts, documents
to work with the new image.
The api has also been changed from v1beta3 to v1 and the beta
api is no longer available, so the interface between Magnum and
Kubernetes master are updated as well in this series of patches.
This particular patch will bring up a V1 cluster with the
bay-create command. Because the switch to the V1 API requires
all the code changes to be applied at once, this patch pulls
in portion of 3 patches together. The changes include:
1. devstack plugin downloads the new image.
2. k8s conductor and other code calls the new V1 client and
3. Configuration for k8s services and docker updated with
4. Minion registration and example code updated to V1.
5. Functional tests updated to V1.
6. Gate test setup points to the new image.
Co-Authored-By: Hongbin Lu <email@example.com>
Partially-Implements: blueprint kubernetes-v1
This patch makes some general cleanup changes to help strings to tidy
up various areas of the code. No functional impacts result from the
changes within this patch.
We currently allow Magnum to scale down bays by removing nodes from
the Bay's ResourceGroup by updating the heat stack that created the bay.
The problem with this approach is that Heat decides which node to delete,
and all containers on that node will also be deleted. This patch make
the selection process smarter: we ask Heat to delete Bay node(s)
that have NO CONTAINERS on them.
Implements: blueprint magnum-smart-bay-scale-down