The image needs to be pulled so that it's available for
subsequent inspect and create calls.
Change-Id: I7f2731911a3fc71fbbf3b408b39e57b7521db81f
Closes-bug: #1408101
Now kube_utils.py supports creation/updating from k8s resource data.
User will be able to updload pod/service/replication_controller data to
create or update resource.
Change-Id: I98f7ab2eab7ac9e68c4e4a313a61f7d39b7596b2
This patch is adding some comments for why adding delete logic
in bay_create for bay_k8s_heat.py
Closes-Bug: #1407832
Change-Id: I7cb103e5370f1c367b20272918314231e65f35e7
kubeutils.py support k8s master endpoint url to connect remote k8s cluster.
In this change, some method signatures are refactored for future works.
Change-Id: Ie065abeef3c65ea429b799a932fe39d868fabcbf
Do the following fixes to pass the tests:
* Add unique constraint to 'ironic_node_id'.
* Throw an exception on deleting a non-existent Node or Container.
* Throw an exception on associating an ironic node to an already
associated magnum node.
* Throw an exception on associating an already associated ironic
node to a magnum node.
* Fix the methods _add_containers_filters and _add_nodes_filters.
Change-Id: Ibf71853e2468ff95d4055be09cb0b460be28a3db
This tests create and delete at the AMQP level and makes certain the AMQP
code is being called. This does not actually test the connection to the
handlers, which would be more like a functional test.
This test case purpose is meant to introduce pain when changing the
interface. The interface should not be changed, a new version should
be implemented.
Change-Id: Icfca04df842497515c20138ba58694805b266b55
The API had an exception that is not being used (BayLocked)
being executed. The API calling the exception is not used
by the codebase.
Change-Id: Ib4c6ea7f3a7bf82a136e4234c7d618444413b46d
there is a lot of options not include in opts, which cause genconfig
not include such config, this patch fix that
Change-Id: I3774930563644b402b74b66b776f13d810fe6f32
This contains temporary implementation of updating master_address, refactoring
rpc handler and some tests.
Change-Id: Idc88795908441d987d9bb63292daccae523f7cbf
the rpcapi does not need ctxt for pod create. This results in an error
creating the POD complaining about incorrect number of parameters.
Change-Id: I98adb0c68fbcc527cd012ff353e4fd831297658b
The rpcapi client does not need ctxt. the rpcapi delivery will generate
a context automatically via the RPC subsystem.
Change-Id: Iac1e8937a24db193db94cf20307fdabba408037f
Did the following fix/modification to make the tests pass:
* Raise an exception on deleting non-existent pod or service.
* Rename the following methods:
get_service_by_bay_uuid -> get_services_by_bay_uuid (db)
get_by_bay_uuid -> list_by_bay_uuid (objects)
Change-Id: I7cbeb119550acecdbf0697df19172a8285eabca8
Did the following fixes/modifications to pass the tests:
* Raise an exception when deleting an non-empty Bay (A bay with
pod(s)/service(s).
* Fixed methods _add_bays_filters, _add_pods_filters and
_add_services_filters.
Change-Id: Iaaeb3f4b49337a822cc79e06fe620b8b11b0acbd
All other methods take in a parameter that can be either a dict with
container information or a string id. pause/unpause should be the
same. Also we have pause/unpause here explicitly is because they
are missing from some versions of the docker-py client.
Change-Id: I882326b718f1252c757fe13f0de3844e02cc9d08
Hongbin Lu