RabbitmqHA
- Launchpad Entry: NovaSpec:tbd
- Created: 19 October 2010
- Last updated: 19 October 2010
- Contributors: Armando Migliaccio
Summary
This specification covers how Nova supports RabbitMQ configurations like clustering and active/passive replication.
Release Note
Austin release of Nova RPC mappings deals with intermittent network connectivity only. In order to support RabbitMQ clusters and active/passive brokers, more advanced Nova RPC mappings need to be provided such as strategies to deal with node failures within clusters and/or master/slave failover in active/passive replication.
Rationale
Currently Nova RPC implementation deals with intermittent network connectivity, i.e. if the connection between a RabbitMQ server and a Nova component (e.g. scheduler, API or compute) drops, the RabbitMQ client adapter tries to recover from it. On the other hand, RabbitMQ provides solutions like clustering and active/passive replication for a greater deal of scalability and reliability. If these
However, RabbitMQ clustering and active/passive replication may provide a greater deal of scalability and/or fault-tolerance, but support must be provided by the Nova RPC make sure that proper fail-over strategies are implemented
User stories
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
