In Ia400b5b6919753d6241233a6666a2c30c7618bc9, we are
adding a new library to global requirements. This
python-k8sclient library essentially has the same
code that was in Magnum so it's a straight replace.
Change-Id: Ib85bcf532e4163d5c1ac95ef701a1ec3133b69eb
This patch does, basically, three things:
* Updates the default auth section to keystone_auth;
* Introduces keystoneauth sessions and plugins;
* Adds a deprecation warning and options when loading
legacy auth.
Config, tests and client code are also updated.
Co-Authored-By: Henrique Truta <henrique@lsd.ufcg.edu.br>
Co-Authored-By: Raildo Mascena <raildo@lsd.ufcg.edu.br>
Closes-Bug: 1496810
Closes-Bug: 1515014
Change-Id: I5c1cd24ca28d66ae7ae40e7f707b81870cf0e457
For good user experience, we should validate if Baymodel's network
is existed in Bay creation. Currently in Magnum there is no Neutron
client support. Neutron client is added for network related
resources validation.
Change-Id: I5668e3b67b8addbff14c7f859a5124c099f35a88
Patially-Implements: blueprint api-parameter-validation
tox -e pip-missing-reqs reported two are missing,
so add them in requirements.
Closes-Bug: #1516849
Change-Id: Id5447241cbc605d305ab9fbcfab1b2aa10feaec6
This adds the CORS support middleware to Magnum, allowing a deployer
to optionally configure rules under which a javascript client may
break the single-origin policy and access the API directly.
For magnum, the CORS middleware was directly added to the setup_app
method, as the last middleware to be wrapped around the application
instance. Common headers were added, in order to avoid magic
configuration moments where a feature does not function without
an operator having to read code.
OpenStack CrossProject Spec:
http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html
Oslo_Middleware Docs:
http://docs.openstack.org/developer/oslo.middleware/cors.html
OpenStack Cloud Admin Guide:
http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html
DocImpact
Change-Id: I7e6d7e2145e3bf883b8a28071c949e10e5c207e0
Closes-bug: #1508209
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
k8s methods.
3. Configuration for k8s services and docker updated with
new parameters.
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 <hongbin.lu@huawei.com>
Change-Id: I046931ad491e8b7ee45943852901eac5c3df913e
Partially-Implements: blueprint kubernetes-v1
While creating the baymodel we must check existence of keypair-id,
So that we can avoid keypair NotFound error while creating the bay.
Change-Id: I3796503bac05a9aa1c9d155e93447a95fb567daf
Closes-Bug: #1476500
Magnum should manage x509 objects,
* To generate CA key and cert for each bay
* To generate client key for magnum-conductor
* To sign a public key for kube-apiserver
* To sign a public key for end user
This patch adds these abilities to Magnum.
Change-Id: Ib5d7180a230dad635b3b570122c5af88cd1ac7a7
Partial-Implements: blueprint magnum-as-a-ca
pip-missing-reqs shows the following
Missing requirements:
magnum/api/validation.py:16 dist=decorator module=decorator
We should add that to our requirements as we have an import
that uses that package/module
Closes-Bug: #1490083
Change-Id: I8c9a4e1145fc99deddf92033e7e644c18dacc8b4