Switch over to the new plugin style as documented here:
http://docs.openstack.org/developer/devstack/plugins.html
Makes it very easy to setup a CI job. Added a new
directory for functional job and the tests are run
from the post_test_hook.sh. There's even a "magnum bay-list"
in the shell script to show that we are actually making
calls to the magnum API endpoint and things are working
fine. Note that this is just the minimal plumbing needed
and there's a lot more effort needed to come up with
proper test cases for testing magnum functionality.
Closes-Bug: #1439621
Change-Id: I88d45015338ef55713b32de196f9071c8fc2031b
We need to consolidate the unit tests into a separate
directory so we can run just the unit tests in our py27
tox target. And we can in subsequent reviews add a parallel
directory with functional tests.
Related-Bug: #1439621
Change-Id: I8bf5af953fb31080096c371966f7dfda9edb1bf4
This patch add tests for container
start/stop/pause/reboot
unpause/delete/create/show
Also add ContainerException, as pep8 not allow Exception check
which it thinks too board.
Partial-Bug: #1439129
Change-Id: I3baeb2c91a7c49cc1871912a58fef23bebf68822
Minions are a Kubernetes concept that maps directly to Magnum's
concept of nodes. This patch renames the column 'minions_address'
to 'node_addresses', so that it is more clear what is stored there
and to be more agnostic across each Container Orchestration
Environment.
Change-Id: I551b0774a08492cb0d45c17b905a830a173522e0
Partial-Implements: blueprint multiple-bay-templates
Magnum region should be 'RegionOne' in keystone to be compatible
with devstack environment. Devstack sets OS_REGION_NAME to
'RegionOne'.
Hence this patch specify region name while creating magnum
endpoint in keystone.
Change-Id: I9cb10e5ef487cdf88f39e27ee1d2c9177896a72d
Closes-bug: #1438018
Magnum is now moved to openstack namespace, all of the document
should also be updated to reflect this.
Change-Id: I8c91e99098acdfd2253b2ecd7100fc54aae370af
Remove downgrade from all existing migrations.
Related cross-project spec: https://review.openstack.org/152337
Change-Id: I39135d99278b6bba13b5f09ffa382b87051d09ad
Partial-Bug: 1434103
According to Heat documentation, AWS::CloudFormation::WaitCondition
timeout attribute should be a number but magnum templates use strings:
master_wait_condition:
type: "AWS::CloudFormation::WaitCondition"
properties:
Handle:
get_resource: master_wait_handle
Timeout: "6000"
This change replaces string timeouts ("6000") by number timeout (6000).
Change-Id: I2ad6825899dca551a152c101832c2d38c61a113e
Closes-Bug: #1437234
Magnum client support name based management when bay and k8s resources are
created. This change reflect it to document.
Partially implements blueprint name-based-resource-management
Change-Id: I60724c3ae110227177031640c5c4d3224ea2dba3
This change enables keystone region support by defining the option
'region_name' in 'heat_client' section:
* magnum searchs only in region_name region for heat endpoint when
region_name is not None,
* otherwise magnum search in all regions.
DocImpact
Closes-Bug: #1437049
Change-Id: Ib2895e7b56e48d6dfa8fe4680e12fc897d5cef03
Magnum get/show pod/rc/service from db directly, not call
kubectl, and besides those code not tested and have no function
needs now. We can add them according to needs later.
Closes-Bug: #1436628
Change-Id: Ibd75eae3a6b6408a035f7889d6dbf527a70b3505
The idea of having a master is a Kubernetes concept and isn't
necessarily a bay concept. In Magnum, we are actually using this
value as the API endpoint. Thus, this patch renames the column
in order to be more clear about what this value is used for, and
also to be more agnostic across each Container Orchestration
Environment.
Partial-Implements: blueprint multiple-bay-templates
Change-Id: Ifaaf626377b8b302e5b390deea53be7be85e88f7
Tested with fedora 20, fedora 20 was supportted.
And fedora 20 is officially supported in devstack,
http://docs.openstack.org/developer/devstack/
Change-Id: Ibef90c6d97032ba9208ec28f0b050167c0a2e61a
The latest kubernetes has changed the log message when a pod
is not found, from "pod 'x' not found" to "pods 'x' not found".
To handle this, and maintain compatibility, this removes the
check for 'pod ' and just checks the log message for
"'x' not found".
Change-Id: Id3a847a576beed383bb0e382afa545828047648b
Closes-Bug: #1435575
The current fedora atomic image uses kubernetes 0.6.0. The latest
atomic image uses 0.11.0. Unfortunately the Fedora community doesn't
release updates to atomic until a major release.
Change-Id: I6ab93469b7e57e1eeeb730189bcc63f1cd5da0bb
Closes-bug: #1434468
While creating bay with baymodel which has invalid
paramaters, 500 status is returned to user. This
change handles the same and raise a magnum exception.
Closes-bug: 1431113
Change-Id: If908e7989feee6179dce7b27672063e92cd393f7
Fix an incorrect option for starting kubelet which was stopping
kubernetes from operating with new fedora atomic images.
See:
https://github.com/larsks/heat-kubernetes/pull/16/
Change-Id: Idfc276b39eb761727a4ecb87991e9866fab6692a
Closes-bug: #1434468
Pull request 14 changes the start order of Kubernetes. The master
now starts first, and the minion starts after the master completes.
This prevents flanneld in the minions from timing out and failing to
start the kubernetes services on the minions.
See:
https://github.com/larsks/heat-kubernetes/pull/14/
Change-Id: Ia823fd3593dc7c5d9d9c6327e009b833ad586a5c
Closes-bug: #1434468
Originally magnum-conductor was called magnum-backend, but was renamed.
Apparently the documentation didn't get completely modified.
Change-Id: I369a21b4b05192ea16171f53089c5220bd5c8ef5
Davanum Srinivas