Some python files do not need to encode in utf-8, so just remove
"# -*- encoding: utf-8 -*-" from those files.
Change-Id: Iafdf4eda876b6599b75c7710e69f62918842ebec
Closes-Bug: #1422067
When a Bay is created, we use Heat to bring up resources to use for the Bay.
We would like to see the related status in the Bay resource that tracks what's
happening. We use the new status attribute to show what is happening with Heat
behind the scenes.
Partially-Implements: blueprint magnum-bay-status
Change-Id: I7b841f2afbe575b039ebbde0e19d8fc464246608
Oslo team is recommending everyone to use the direct imports and
not use the Oslo namespaces. So switch all our code to use oslo_*
instead of "from oslo." or "import oslo" or "from oslo"
NOTE: some of the tests still have mocks referring to oslo.utils
@mock.patch('oslo.utils.timeutils.utcnow')
as the tests break otherwise. We should do this later.
Closes-bug: #1419385
Change-Id: I8e3fbeb833cddc3f55674a0e781ffe69d5033ad4
project_id and user_id were added to the following tables:
1) container
2) node
3) bay
4) baymodel
Implements part of bp multi-tenant
Change-Id: Ied9a855251246bb087bc8bca70809a81594f26c7
Only replication controller manifest knows about rc name, so
this patch retrieve rc name from rc manifest.
Change-Id: I8193c2066ea1f0a40761f304f784fbb3b2d16796
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
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
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
The idea of bay-create is that you create a grouping of machines that run
container software. In order to do this, an image_id stored in glance is
necessary to pull the base image to modify for launching by either heat or
Ironic. A node_count is needed as well, to identify how many ironic nodes
you want to launch.
Change-Id: I5689d024f4ece93369498bd7f64cde0b8a59e292
The Ironic codebase is pretty simple for database access. This work
leads into the introduction of versioned object technology from nova
and ironic that will be entering oslo:
https://review.openstack.org/#/c/127532/
This will drastically speed up the process of implementing moving the
RPC objects across the network.
Change-Id: I38aa451b658b66f5b6f10ced03ea2e0355af4ecd
Jay Lau (Guangya Liu)