Search results

There is a page named "Zaqar" on this wiki. See also the other search results found.

Zaqar/bp/client-polling

See here

98 bytes (2 words) - 18:42, 7 August 2014
Zaqar/specs/backends

479 bytes (0 words) - 18:42, 7 August 2014
Zaqar/tests

API CLI

136 bytes (2 words) - 18:42, 7 August 2014
Give Zaqar a try (Zaqar) (section Set up a simple Zaqar deployment)

mkdir .zaqar $ git clone https://github.com/openstack/zaqar.git Copy the Zaqar config files to the directory ~/.zaqar: $ cp zaqar/etc/zaqar.conf.sample

3 KB (372 words) - 13:10, 28 August 2014
Zaqar/docs/drivers

Marconi has a modular architecture, and utilizes dynamically-loaded transport (frontend) and storage (backend) drivers via stevedore. All drivers have

1,008 bytes (126 words) - 18:42, 7 August 2014
Zaqar/specs/use-cases/2

Forward usage events to data collectors Identical to UC1, but substituting the actors Component and Collector for the actors Producer and Worker, respectively

880 bytes (71 words) - 18:42, 7 August 2014
Zaqar/releases/icehouse

Marconi is an incubated OpenStack program, preparing to graduate at the end of the Juno release cycle (fall 2014). With the close of the Icehouse cycle

1 KB (127 words) - 18:42, 7 August 2014
Zaqar/Performance (section Zaqar's Drivers Performance)

This wiki page contains current performance numbers per driver. Pilot Tests (Redis/MongoDB) Pub-Sub (Redis)

210 bytes (16 words) - 20:58, 15 September 2014
Zaqar/bp/uwsgi-sample

Consider adding a sample script and something to the docs along these lines: # marconi-wsgi.py from marconi import bootstrap boot

450 bytes (58 words) - 18:42, 7 August 2014
Reviewer guide (Zaqar)

with some important additions (see below). See also: Your first review on Zaqar. The PTL, with the support of the core reviewers, is ultimately responsible

5 KB (471 words) - 15:54, 21 October 2014
Zaqar/Blueprinting process

The page name should follow this schema: https://wiki.openstack.org/wiki/Zaqar/specs/{blueprint-name}

267 bytes (38 words) - 13:30, 28 August 2014
Zaqar/Programming style guide

Page to be filled up

20 bytes (5 words) - 13:30, 28 August 2014
Juno/Notes/Zaqar

Some thoughts were discussed around the two major groups of API symantics, their use cases, and whether we can support all the current semantics for high-throughput

2 KB (230 words) - 12:09, 23 September 2014
Zaqar/Use Cases

Marconi is designed to support several messaging patterns, including a number of Enterprise Integration Patterns, through a combination of API semantics

5 KB (845 words) - 08:07, 12 September 2014
Zaqar/guarantees

Marconi guarantees FIFO for a given queue, but only when there is a single message producer. Marconi also guarantees once-and-only-once delivery of messages

3 KB (501 words) - 18:42, 7 August 2014
Zaqar/specs/amqp/api/v1

Having support for more transport protocols would allow us to support a broader set of use-cases. AMQP is a standard protocol adopted by other messaging

2 KB (213 words) - 18:42, 7 August 2014
Zaqar/specs/use-cases/1

Distribute tasks among multiple workers. 1. Producer signs and submits work ticket to Service 2. Service acknowledges work ticket and guarantees its

2 KB (316 words) - 18:42, 7 August 2014
Zaqar/specs/use-cases/3

Publish events to any number of subscribers. This use case only covers pub-sub within a single application domain. Publishing events to 3rd-party systems

3 KB (388 words) - 18:42, 7 August 2014
Zaqar/specs/Protocols/Wire Transport

Zaqar currently has a well defined protocol that works well for HTTP. As a project, we're looking forward to welcome more transports that will work for

3 KB (330 words) - 19:56, 19 January 2015
Zaqar/specs/sharding/v1 (section Zaqar Storage Pooling: v1 Blueprint)

/v1/pools/wat HTTP/1.1 Host: zaqar.example.com Response HTTP/1.1 200 OK Content-Location: /v1/pools/wat { "uri": "mongodb://zaqar1.example.com:27017",

4 KB (501 words) - 16:41, 21 August 2014