'auth_url', 'auth_token_info' and 'trust_id' is required to create heatclient.
So this commit added these.
Change-Id: If17c87770f2e4d93dae5e1262faa5b44cc5cfdef
First cut of Docker container creation and start should be working now
Tested using the REST API:
curl -i -X POST -H 'X-Auth-Token: 1b238d90cd0645a39a626581cf0c9f19' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-d '{"image_id": "cirros", "name": "mycontainer"}' \
http://127.0.0.1:9511/v1/v1/containers
curl -i -X PUT -H 'X-Auth-Token: 1b238d90cd0645a39a626581cf0c9f19' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'User-Agent: python-magnumclient' \
http://127.0.0.1:9511/v1/containers/4e19a981-057f-4d55-9aaf-d12c06e6430a/start
And the magnum CLI:
echo '{"name":"mycontainer", "image_id":"cirros"}' | magnum --debug container-create
magnum --debug container-start --id c6d6c759-9875-4dd4-aaa3-619799015c1d
Change-Id: Ib7a46d95d2d89cd8479bb0a318a3c9efaf23f187
The baymodel_id represents the bay model used to generate this
particular Bay. This is essentially a split of Bay into multiple
objects - one for template storage - one for instantation.
Change-Id: Ie6b7220bfecfd61af0ecf9114a791dfed61b415e
The baymodel object and ReST object is used to control bay properties
for different bay models. It is then possible to launch bay models
using this functionality.
Change-Id: I317bda292719ca3f4649283f7e27674c813cc3b0
This uses "larsks/heat-kubernetes" template to build a kubernetes cluster,
to support k8s_heat type Bay.
k8s_heat type Bay provide kubernetes using heat.
Change-Id: I40980a4d264de7f59c1314b6c5a30b643d03dd92
The cmd.conductor was referencing a file that was renamed by a previous
commit. This resulted in the conductor not running.
Change-Id: Id3e08334d106cf8a1f6cc94c4905d42095a0546d
Get the work flow in place for pods and services to use rpc
backend and integrate kube handlers.
Partially-Implements: blueprint magnum-backend-kubernetes
Change-Id: Iabd7f5f1217402c18820170521354ac04e436551
This client will be used by novaclient and heatclient to create a bay.
The original sources are come from Ironic.
Change-Id: Ib075148afb0ddf503e71b333cef85523561a2732
Remove conductor. The backend will replace the conductor as the process
name to be more consistent with other OpenStack projects.
Change-Id: If69557b7ca02e48c65372cbb200d2f648613778e
This test case really only unit tests the ReST API. So rename it as such.
This file probably needs to be split into the separate objects in the tree.
Change-Id: Ifefaa25297d9737e8644948f4faed9c0abea6b38
This uses a simplified RPC model while integrating with the
versioned objects serializer.
bay-create is handled by the backend.
bay-list is handled by the RPC service.
Change-Id: I384994584ad7f928df9366a2e6f677951a450e40
The node object represents either a bare metal or virtual machine node
that is provisioned with an OS to run the containers, or alternatively,
run kubernetes.
Change-Id: I9eba14232c193688347b7ec2674c83f230404ae1
Patch Ib765d1c3ed8a6c06136233abd393fb1efae71e41 add two fields
for pods but db migration was not updated.
Change-Id: Id66b606cd11e43a8ef7b8c46f805b37c22c571a8