According to the comment in https://review.openstack.org/#/c/484602/,
introduce the new api endpoint for capsules will reduce the API burden
when changing.
Change-Id: Ia686406449fdfa3ac4947fd997d9e2a8baf8f4b6
Signed-off-by: Kevin Zhao <kevin.zhao@arm.com>
1.Add new entrypoint 'experimental', devstack will be
modified to support this.
2.Add controller Capsule
3.Add capsule create method
4.Refactor the code for _do_container_create
5.Add one capsule template
All capsule method in the API level will use:
/experimental/capsules API, apart from v1 API.
Part of blueprint introduce-compose
Change-Id: Ia031ee5beb48ec70dab6bb371944140d025a499b
Signed-off-by: Kevin Zhao <kevin.zhao@arm.com>
The 'addresses' field is a map of ip addresses. In before, it
used docker network name as key, which is hard to be interpreted
by users, since docker network is hiden from end-users. This commit
switches to use neutron network uuid as key. A use case is from our
Heat plugin, which requires neutron network information to do
orchestration.
Change-Id: Ic3e4ee80962cdd777543e5c9c988fc0cdc623dad
Support creating container with specified neutron net. Users
can pass the uuid/name of an existing neutron network via the 'nets'
parameter. If network is specified, Zun will use the specified network
instead of searching one.
NOTE: If both 'port' and 'network' is set via the 'nets' parameter,
the 'network' will be ignored since Zun will use the network of the
existing port.
Change-Id: I8a0f4f7461a99c1c3bafdfd2baa5b51800292230
Partial-Implements: blueprint multiple-networks
Closes-Bug: #1705154
When the wsgi community goal was first approved, the push was to
use mod_wsgi. mod_wsgi has many issues when being used in devstack
for development or testing (see [1]). This commit will switch the
deployment of zun-api to uwsgi.
[1] https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi
.html#uwsgi-vs-mod-wsgi
Change-Id: Iec05ccb8aceee6874e3c04280fe7596f8292e333
Closes-Bug: #1692382
Support creating container with existing neutron port. Users
can pass the uuid/name of an existing neutron port via the 'nets'
parameter. If port is specified, Zun will use the existing port
instead of creating a new port.
If a container is deleted, its neutron port will be deleted regardless
of existing or not. A future work is to determine if the port is
pre-existing and avoid deleting existing port.
Closes-Bug: #1702581
Change-Id: I204b4bbe3de9e275690c4a64acdfe557f134b7ee
In before, if there is no network available, users don't know what is
wrong until the container is scheduled to a compute node and fail.
This commit moves the searching of neutron net to zun-api so that
users will receive an error response earlier if the request is
invalid.
Change-Id: Ic9fd47c6e4aff4131ebaad73a3bed0f51eeb118c
Related-Bug: #1702581
Note:
1.Test case can be found in bug description.
2.For the bug https://bugs.launchpad.net/zun/+bug/1707069 has not
been fixed, added a dependency.
Change-Id: I82a34cfd6412f6a32a10d069c5c365ff7393cd61
Closes-Bug: #1707954
* Fix the broken add_security_group implementation in driver.
* Add tempest test case to verify this action.
Closes-Bug: #1707069
Change-Id: Iafc13bd75c5b924c3727fa1995f6a285ec794885
