OpenStack Messaging (Zaqar)
Go to file
Ghanshyam Mann 2c0e84879e [train][goal] Define new 'zaqar-tempest-swift-ipv6' job
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
we need to define the integration job which deploy services
on IPv6 and perform testing to make sure service listen and communicate
over IPv6 properly.

Zaqar has legacy zuul jobs so base zuulv3 IPv6 job 'devstack-ipv6' and
'devstack-tempest-ipv6' cannot be used and we have to copy the whole
run.yaml to set the IPv6 setting and run the IPv6 verification
script via post_test_hook.

This commit adds the new job 'zaqar-tempest-swift-ipv6'
run on gate and set the required IPv6 setting'.

Change-Id: I9aece13783a061c4214157c3f7cfc9cc9f2a3f96
Story: #2005477
Task: #35941
2019-09-20 01:26:47 +00:00
api-ref/source Miss name filter in querying queues 2018-12-17 16:27:10 +08:00
devstack [train][goal] Define new 'zaqar-tempest-swift-ipv6' job 2019-09-20 01:26:47 +00:00
doc Merge "Rename review.openstack.org to review.opendev.org" 2019-08-27 04:16:19 +00:00
etc CONF file structure refactor 2018-06-04 09:11:46 +08:00
playbooks/legacy [train][goal] Define new 'zaqar-tempest-swift-ipv6' job 2019-09-20 01:26:47 +00:00
rally-jobs Port Rally Task to format v2 2017-09-27 17:28:01 -07:00
releasenotes Imported Translations from Zanata 2019-07-08 06:23:10 +00:00
samples Update the client version in samples 2018-09-17 10:50:25 +08:00
tools Fix sqlalchemy migration 2017-02-02 20:20:29 +13:00
zaqar Quick fix for v1.1 api schema 2019-08-29 11:11:09 +08:00
zaqar_upgradetests Support cold migration 2017-02-27 01:52:38 +00:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-17 17:17:34 +05:30
.gitignore Unblock gate failures 2019-05-29 09:31:18 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:44 +00:00
.stestr.conf Add .stestr.conf configuration 2018-12-20 11:03:54 +08:00
.zuul.yaml [train][goal] Define new 'zaqar-tempest-swift-ipv6' job 2019-09-20 01:26:47 +00:00
AUTHORS.rst refactor: Rename AUTHORS so that it doesn't keep getting overwritten 2013-03-19 16:33:43 -04:00
babel.cfg Prepare marconi for localization 2014-06-04 22:31:55 +02:00
bench-requirements.txt Fix SSL and verbose issue of zaqar bench 2016-11-21 01:49:16 +00:00
bindep.txt Fix gate job failure 2017-12-02 23:21:27 +13:00
CONTRIBUTING.rst Optimize the link address 2017-06-02 23:50:39 +07:00
dox.yml Add a dox.yml config file 2014-09-08 13:55:13 +02:00
HACKING.rst Update and optimize documentation links 2017-07-20 18:31:18 +08:00
LICENSE Include full license text 2014-03-21 10:16:28 +01:00
lower-constraints.txt Switch to using stestr directly 2019-05-29 10:48:28 -05:00
README.rst Add zaqar-specs link to readme.rst 2019-08-30 07:57:30 +00:00
requirements.txt Unblock gate failures 2019-05-29 09:31:18 -05:00
setup.cfg Fit the StopIteration for py37 2019-08-01 09:07:13 +08:00
setup.py Updated from global requirements 2017-03-10 03:40:58 +00:00
test-requirements.txt Switch to using stestr directly 2019-05-29 10:48:28 -05:00
tox.ini Merge "Fit the StopIteration for py37" 2019-08-13 09:10:09 +00:00

Team and repository tags

image

Zaqar

Zaqar is a multi-tenant cloud messaging and notification service for web and mobile developers. It combines the ideas pioneered by Amazon's SQS product with additional semantics to support event broadcasting.

The service features a fully RESTful API, which developers can use to send messages between various components of their SaaS and mobile applications, by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind.

Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the "over-cloud" layer. Cloud operators can leverage Zaqar to provide equivalents of SQS and SNS to their customers.

General information is available in wiki:

https://wiki.openstack.org/wiki/Zaqar

The API v2.0 (stable) specification and documentation are available at:

https://wiki.openstack.org/wiki/Zaqar/specs/api/v2.0

Zaqar's Documentation, the source of which is in doc/source/, is available at:

https://docs.openstack.org/zaqar/latest

Zaqar's Release notes are available at:

https://docs.openstack.org/releasenotes/zaqar/

Contributors are encouraged to join IRC (#openstack-zaqar channel on irc.freenode.net):

https://wiki.openstack.org/wiki/IRC

Information on how to run unit and functional tests is available at:

https://docs.openstack.org/zaqar/latest/contributor/running_tests.html

Information on how to run benchmarking tool is available at:

https://docs.openstack.org/zaqar/latest/admin/running_benchmark.html

Zaqar's design specifications is tracked at:

https://specs.openstack.org/openstack/zaqar-specs/

Using Zaqar

If you are new to Zaqar and just want to try it, you can set up Zaqar in the development environment.

Using Zaqar in production environment:

Coming soon!

Using Zaqar in development environment:

The instruction is available at:

https://docs.openstack.org/zaqar/latest/contributor/development.environment.html

This will allow you to run local Zaqar server with MongoDB as database.

This way is the easiest, quickest and most suitable for beginners.