Magnum always need to have neutron enabled to work,
so the test with neutron disabled will always fail.
Change-Id: I9d37a052d0beef3b837385324d9f9fa2f1ec9617
In order to validate the magnum plugin integration,
add more experimental jobs to ensure we have proper coverage
of all tests before moving to check.
Change-Id: Ic3ffc4996eac2d3a7e817ef732f75d0204bd3a80
This is a repo for integration tests for all StackLight plugins:
- Elasticsearch-Kibana
- InfluxDB-Grafana
- LMA Collector
- LMA Infrastructure Alerting
Change-Id: Iab22ff0ce1929144d4b0230092341ea18b622c48
We do not need both server-release and publish-to-pypi jobs, it's an
either or. Server projects do not release to PyPI and vice versa.
Having the publish-to-pypi template as well as openstack-server-release-jobs
results in duplicates of some of the jobs running, especially the
tarball and announcement email jobs.
Change-Id: Ic2a82d440577154126218feaaa17cde28ffbf5fa
The translation team only handles official projects - and even
prioritizes there. There's no real translated content up for vmware-nsx
- only filling by translation memory.
Change-Id: If1eb167309e4c5a1de6aa8baed5ff4fc6cfe8b5b
Depends-On: Icb3d33af0e32919bb13c52b3662f481c2c99011c
Now Zaqar supports mongodb and redis as backends. So it would be
nice if the tempest job can support both.
Change-Id: Ie56471c866ff890988d2ced10253051552c73123
The current tempest-dsvm-full-ceph-src jobs aren't using the
ceph devstack plugin, so this adds a template for a new job that
uses the plugin: tempest-dsvm-full-ceph-plugin-src and replaces
the old ceph-src job with it.
Change-Id: I91742ba412d742e9a24681dbc124f00500537315
This reverts commit 4f96b2727c2afd3c3d6b888c21c8d18ba1cb7376.
The correct fix for this is not to stop using the feature.
Change-Id: I4b35a6ca13153257984074b5145a5e691564e0ca
This patch had been proposed before:
https://review.openstack.org/#/c/295969
But had to be reverted because we were consuming external images
from fedorapeople, that caused our tests to timeout. We are now on
the situation where we have our own custom atomic images, to start
adding that on shade as a previous step for adding magnum integration
to shade.
Change-Id: Ifae8e54e78f6f36cf025ac92ba704391b2052769
Inspector tempest plugin was moved to ironic_inspector/test
directory, so we need to exclude inspector_tempest_plugin directory
from regex for matching all tests.
Change-Id: I857a39a72bfebbacd48e9f3d76431367f43d72a7
The main reason to create this new project is a request from the
community in the context of this devstack patch:
https://review.openstack.org/#/c/108714/
The objective is to enable devstack to install software
(QEMU and libvirt for the time being) from tar releases. The
project devstack-plugin-tar-installer will host the devstack plugin
which implements this feature.
Change-Id: Iddaf12ba79aa70b6045826568319a163e75347b6
Signed-off-by: Michele Paolino <m.paolino@virtualopensystems.com>
networking-nec liberty and older does not support python34.
When python34 job was added, I forgot to add branch condition.
Change-Id: Id0ef0ff2c8f4f423babc870421ce9e118745b46a
Currently failures of this job leave a broken comment that doesn't
match the test-result regexes, meaning that you can't see the result
in the callout box. See [1].
I863d88e9a7ed2fd41924b8fc4a12dbea3ee2b205 fixes the root cause, but
this message is still a bit wrong because it doesn't have the
[PASSED|FAILURE] bit.
I don't really see why we need this special result at all. If it
fails, you have to read the log anyway to figure out what is wrong, so
move the message pointing to the docs to where the failure actually
happens in the logs.
[1] https://review.openstack.org/#/c/292193/
Change-Id: Ie5e7d2318a510a5811c9131d56594e856da9dcc5
We created the job for puppet-aodh first, so we could test.
Now it's in place, we would like the jobs for all modules.
Change-Id: I03e0235b0cd8f216b952c03145d158577862c0fc
This patch adds releasenote jobs to all OpenStack-Ansible
repositories to ensure the appropriate processing and publishing
of release notes for each role.
Change-Id: I60f3377e2b2e24ef2b870e925be89737b76e21ba
VirtualBMC is a utility that allows virtual/fake BMCs to be created
handling the IPMI commands and converting it to calls to the
python-libvirt library. The project was created to allow drivers using
the IPMI protocol to be tested in the Ironic gate.
Related-Bug: #1570301
Needed-By: I24349ce1b5c0332157f1bf8bd0613338a15495e4
Change-Id: Idf02cb28316be1846bb5fa1988c3d47ce6f9c54c
layout.yaml - Removed Python3 jobs temporarily until
we set our local tox to run py34 instead of py3.
vitrage.yaml - Fixed hook function to use source
URGENT - Thanks :)
Change-Id: I58994cf77608df5310d6a2b45de195dcc718cfe2
Turn on the keystone tempest plugin tests. From now on, tests that are
only related to the keystone API, will be placed there.
To run only keystone tempest plugin tests, we use::
$ tox -e all-plugin -- keystone
* non-voting so we can see that it works
* master-only
* run only against keystone
Change-Id: I070e1f40ecaa5d23a68c4ac23b542631ea3e2309
Partially-Implements: bp keystone-tempest-plugin-tests
