Disable Quantum in Folsom
Hi,
Same question as this: https:/
The question answer was that to disable quantum, you should remove the related entries from keystone, so I've done that.
But Quantum is still showing up in Horizon.
I've also set QUANTUM_ENABLED = False in my local_settings, but that shouldn't matter if I understand it correctly.
Screenshot of Horizon showing the Quantum service is still there: http://
>> keystone catalog
Service: compute
+------
| Property | Value |
+------
| adminURL | http://
| id | c230882ea4874fe
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Service: image
+------
| Property | Value |
+------
| adminURL | http://
| id | b6ddac4a17f349c
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Service: volume
+------
| Property | Value |
+------
| adminURL | http://
| id | 44bc8e81ba774e5
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Service: ec2
+------
| Property | Value |
+------
| adminURL | http://
| id | e00fb0efde18460
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Service: object-store
+------
| Property | Value |
+------
| adminURL | http://
| id | 810b13e78e02438
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Service: identity
+------
| Property | Value |
+------
| adminURL | http://
| id | cbe6686559e949e
| internalURL | http://
| publicURL | http://
| region | RegionOne |
+------
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Sam Stoelinga
- Solved:
- Last query:
- Last reply: