The plugin has been split into its own repository [1] in accordance
with Queens Goal "Split Tempest Plugins into Separate Repos/Projects"
[2]. This patch removes the local copy as well as the setuptools
entry point.
[1] https://github.com/openstack/zun-tempest-plugin
[2] https://governance.openstack.org/tc/goals/queens/
split-tempest-plugins.html
Implements: blueprint zun-split-tempest-plugins
Change-Id: Ibfeb38b52c05a9f886dc7524d892842971cbd264
The attach workflow is as following:
* reserve_volume in Cinder
* initialize_connection in Cinder
* connect_volume in os_brick
* attach in Cinder
If the workflow executes sucessfully, the Cinder volume
is attached to the compute host as a device. Zun will
mount the device to the filesystem in order to use it.
The detach workflow is as following:
* begin_detach in Cinder
* disconnect_volume in os_brick
* terminate_connection in Cinder
* detach in Cinder
Partial-Implements: blueprint direct-cinder-integration
Change-Id: Ib47e76d14b3dc036f903a3988bb138288cdb601e
Update keystone auth_uri and auth_url in zun.conf to connect with keystone
using /identity/v3 and /identity_admin/v3.
Closes-Bug: #1692576
Change-Id: Ie107e6ef9d3ebfee77b4782842e1ed966738c6cd
In devstack setup, zun-ui failed to attach to the container.
This is because the base_url is not configured and the default
value doesn't allow a remote attach. This patch fixed it.
Change-Id: Ie47e424c2e1542a290419df952019363711b9fd0
This commit uses the existing policy-in-code module to move all
default policies for networks into code. This commit also adds
helpful documetation about each API those policies protect, which
will be generated in sample policy files.
bp policy-and-docs-in-code
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
Change-Id: I3d5486c2b4d696c364eef1d16db403db6504da70
- Check glance is enabled or not before upload sandbox
image to glance.
- Remove unused function is_zun_enabled.
Change-Id: I426298816e1144c66fd13f21949afdb058bce9cb
Closes-Bug: #1650245
Screen support has been completely removed from devstack.
So we don't need anymore
[1] the change id of I8c27182f60b0f5310b3a8bf5feb02beb7ffbb26a
the change set of cdba1b371628aa0e8bc5b687351c5ee9b39e9bc6
Change-Id: Id0b5243746aaf519d2f7e887bdbfe9d0a9e78c2f
We decided to deprecated NovaDocker driver in the team meeting [1].
Therefore, we moved the driver to the contrib folder. NovaDocker
was an experimental driver that attempts to leverage Nova to provide
networking to containers. However, as kuryr integration implemented,
this driver is not needed anymore.
[1] http://eavesdrop.openstack.org/meetings/zun/2017/
zun.2017-07-11-03.00.log.html
Change-Id: I770fe13a004dc56ad20fe8eca545f05c4504e48e
Devstack set the docker cluster store to point to the etcd cluster
in current host. In multinode gate, each node setup an independent
etcd cluster so docker in each host uses an independent store.
This will result in an issue that resources (i.e. network) created
in one node cannot be found in another node.
This commit fix it by making all nodes use the same etcd cluster
in service host.
Partial-Implements: blueprint multi-node-ci
Change-Id: Ieeecc2ef14a1077a2ef91ee369b317f53d7ffb81
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>
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
* Switch to file backend if python35 is enabled because the default
backend is swift that hasn't migrate to py35 yet.
* Safe decode bytes string of response body.
Depends-On: Ib222bf2e84f4b06b0dc3981fc3554510658d4ef0
Partial-Implements: blueprint support-python-35
Change-Id: I2d9a95dda8ead16421186116118badfce1de7ba6
This config is set to hostname by default, but this won't work in
multi-host setup. Therefore, we set it to host_ip instead.
Change-Id: I023bf4823513bae277ab08db62f103642b87accb
For the nodes other than service host, only enable zun-compute.
q-agt and kuryr is also required to provide network connection,
which need to be specified in local.conf.
Change-Id: I78055c75ad545cf8809dae973d1180dce2ecf77f
Closes-Bug: #1691606
For devstack-plugin-container plugin, existing docker-ce checks added in zun
and kuryr-libnetwork. Update - Proxy configuration changes and
docker daemon command is deprecated since 1.12, update with dockerd command
Change-Id: Ibd5ac7f933570688523ba273e0413a0d8eae1681
Related-Bug: #1684057
If both Zun and Kuryr-libnetwork are enabled in devstack, the script
might fail since etcd will be installed and started twice. This commit
fixed it.
Change-Id: Ieffbb7a86e99a3e9a03cbfcadb2daf92d8f62cfb
* Add a dev document for how to run tempest tests locally.
* Pull the instruction of running unit tests out of quickstart
guide and make it a standalone document.
* Fix the unit tests guide to make it work at Ubuntu 16.04.
* Add a sample local.conf as minimal to run devstack
* Add osprofiler guide to the index page.
Change-Id: I31794733c9225478f5df029279c8415a23b1caa0
In before, zun devstack plugin enabled wsgi mode by default. This
patch proposed the reverse: disable wsgi mode by default. This fall
back to the screen mode if users haven't explicitly set
ZUN_USE_MOD_WSGI to True. However, we enable wsgi mode in gate to
satisfy the requirement of community wsgi goal [1].
The rational of this change is to ease the development process by
running zun-api at screen, which is more dev-friendly than running
it in apache2/httpd. In screen, it is easier to do dev operations
like shutdown/restart/debug.
[1] https://governance.openstack.org/tc/goals/pike/
deploy-api-in-wsgi.html
Change-Id: I8b47a23e94de8676c415a66da2097fc69ceb8336
If wsgi mode is enabled, zun-api should be disabled in apache,
otherwise shutdown the process as before.
Change-Id: I33979a5454a3d68415fcfff01e9de6e99f8b31d6
1. Rename zun_error.log to zun_api.log
2. Start the zun-api and create two tabs in devstack screen:
the first tab is for taling the zun_api.log, the second tab
is for tailing the zun_access.log
Change-Id: I10a75c09e7a577615c331ceb0f422375443afeee
Closes-Bug: #1674028
Last commit [0], using sudo cat, this will gievs the error:
/etc/systemd/system/docker.service.d/docker.conf: Permission denied
This patch will fix this.
[0]: I2154919c394e546edac56934c8860d4177fc9603
Change-Id: I87a8b7397d2dad2d26eac9a020d5ea3b21645aa2
Now devstack docker install in centos will gives the error:
sed: can't read /etc/systemd/system/docker.service.d/docker.conf: No such file or directory
ref the docker install guide [0], fix this error.
[0]: https://docs.docker.com/engine/admin/#centos--red-hat-enterprise-linux--fedora
Change-Id: I2154919c394e546edac56934c8860d4177fc9603
Added new config which is used in devstack zun lib,
``ZUN_USE_MOD_WSGI``, default value is False.
Added ZUN_USE_MOD_WSGI=True in Setting file of zun gate.
Implements: blueprint deploy-zun-api-in-wsgi
Change-Id: I99fe6bf762942d306b305619199575a060ba82f5
Because of the wrong usage of sed command, we cannot deploy zun
with devstack on ubuntu 14. This patch aims to fix this problem.
Change-Id: I7a6ea3ccf3dda1429d37974e6c142b4b1d97865d
Close-Bug: #1662788
Copy zun.bash_completion script to /etc/bash_completion.d
so that users/developers can take advantage of auto completion
of zun commands.
Closes-Bug: #1657004
Change-Id: Icb47fe4864176d4ca3699b0616f2c222eba22ae3
