cinder-api should run as active/standby
Bug #1393331 reported by
Bogdan Dobrelya
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Michael Polenchuk | ||
7.0.x |
Won't Fix
|
High
|
Fuel Library (Deprecated) | ||
8.0.x |
Fix Released
|
High
|
Michael Polenchuk |
Bug Description
Cinder is no A/A ready, see http://
and http://
http://
Fuel should configure Cinder API to be active standby, like Galera.
HAproxy should be reconfigured to make only one API node serving requests at any time.
Not sure how this bug affects cinder-scheduler.
Update: it affects the volume services as well
Changed in fuel: | |
status: | New → Triaged |
milestone: | none → 6.1 |
importance: | Undecided → High |
assignee: | nobody → Fuel Library Team (fuel-library) |
description: | updated |
tags: | added: cinder ha |
description: | updated |
Changed in fuel: | |
milestone: | 8.0 → 7.0 |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Michael Polenchuk (mpolenchuk) |
Changed in fuel: | |
status: | Confirmed → In Progress |
description: | updated |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | added: area-library team-bugfix |
summary: |
- cinder-api and volume should run as active/standby + cinder-api should run as active/standby |
To post a comment you must log in.
According to Jay Pipes comments: "I do not think you need to put nova-scheduler as a single resource for pacemaker, no. The state that each scheduler process keeps is kept up to date with calls to ComputeNode. get_all( ) during each beginning of scheduler select_ destinations( ) loop call.
So there is no stale data anywhere... and when the compute node aborts a resource claim, the resource request is rescheduled to another host. so no, I don't think the scheduler needs to be a single resource for pacemaker :)
for cinder-api, there is no state, therefore it should be active/active as well."