Disable Quantum in Folsom

Asked by Sam Stoelinga

Hi,

Same question as this: https://answers.launchpad.net/horizon/+question/210437

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://www.mediafire.com/view/?cruxp4tznlqmfq6

>> keystone catalog
Service: compute
+-------------+-------------------------------------------------------------+
| Property | Value |
+-------------+-------------------------------------------------------------+
| adminURL | http://192.168.0.1:8774/v2/127cdfa47e544df080d2ede5c38797d1 |
| id | c230882ea4874fedb82eb66515d7f679 |
| internalURL | http://192.168.0.1:8774/v2/127cdfa47e544df080d2ede5c38797d1 |
| publicURL | http://192.168.0.1:8774/v2/127cdfa47e544df080d2ede5c38797d1 |
| region | RegionOne |
+-------------+-------------------------------------------------------------+
Service: image
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| adminURL | http://192.168.0.1:9292/v2 |
| id | b6ddac4a17f349cbb03be4b72328fdc2 |
| internalURL | http://192.168.0.1:9292/v2 |
| publicURL | http://192.168.0.1:9292/v2 |
| region | RegionOne |
+-------------+----------------------------------+
Service: volume
+-------------+-------------------------------------------------------------+
| Property | Value |
+-------------+-------------------------------------------------------------+
| adminURL | http://192.168.0.1:8776/v1/127cdfa47e544df080d2ede5c38797d1 |
| id | 44bc8e81ba774e509b0d18e117f68c98 |
| internalURL | http://192.168.0.1:8776/v1/127cdfa47e544df080d2ede5c38797d1 |
| publicURL | http://192.168.0.1:8776/v1/127cdfa47e544df080d2ede5c38797d1 |
| region | RegionOne |
+-------------+-------------------------------------------------------------+
Service: ec2
+-------------+----------------------------------------+
| Property | Value |
+-------------+----------------------------------------+
| adminURL | http://192.168.0.1:8773/services/Admin |
| id | e00fb0efde1846009e9b70c280eff60c |
| internalURL | http://192.168.0.1:8773/services/Cloud |
| publicURL | http://192.168.0.1:8773/services/Cloud |
| region | RegionOne |
+-------------+----------------------------------------+
Service: object-store
+-------------+------------------------------------------------------------------+
| Property | Value |
+-------------+------------------------------------------------------------------+
| adminURL | http://192.168.0.1:8080/v1 |
| id | 810b13e78e02438f8e2c9126535ca41a |
| internalURL | http://192.168.0.1:8080/v1/AUTH_127cdfa47e544df080d2ede5c38797d1 |
| publicURL | http://192.168.0.1:8080/v1/AUTH_127cdfa47e544df080d2ede5c38797d1 |
| region | RegionOne |
+-------------+------------------------------------------------------------------+
Service: identity
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| adminURL | http://192.168.0.1:35357/v2.0 |
| id | cbe6686559e949e5be1e27a574806bdd |
| internalURL | http://192.168.0.1:5000/v2.0 |
| publicURL | http://192.168.0.1:5000/v2.0 |
| region | RegionOne |
+-------------+----------------------------------+

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Dashboard (Horizon) Edit question
Assignee:
No assignee Edit question
Solved by:
Sam Stoelinga
Solved:
Last query:
Last reply:
Revision history for this message
Sam Stoelinga (sammiestoel) said :
#1

After several hours Horizon seemed to pickup the changes, maybe this was because of caching?
Are the keystone calls being cached, such as endpoints / services?

Problem is solved but still wondering about the cause.