Juniper Openstack

Bug #1715427
Comment #8

Comment 8 for bug 1715427

Revision history for this message

Ramprakash R (ramprakash) wrote on 2017-09-09:

Screen Shot 2017-09-08 at 4.34.02 PM.png Edit (372.2 KiB, image/png)

@Ritam: With the above commit, please note the following (number corresponds to the item number in the bug description above):

1. Horizon now comes up with option for Domain when version is set to v3 (see attachment)?field.comment=@Ritam: With the above commit, please note the following (number corresponds to the item number in the bug description above):

1. Authorization errors are not seen now. Horizon now comes up with option for Domain when version is set to v3 (see attachment)

2. For keystone policy.json, the way Kolla handles this is the user crafts his own policy.json based on https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json and then if this is placed in /etc/kolla/configs/keystone/policy.json of the SM machine (where sensible is going to be run) this will be copied into the container during provision. So if you need a policy with cloud_admin, you can craft one yourself and place it in the directory mentioned above and then issue provision. If there is a change, you can change it and then issue retrovision for it to take effect.

3. The provisioning code seems to set the version information correctly, but I suspect the internal Ansible is not handling this to set in the config.global.js file OR it may not be required.

*** Please raise a separate bug and track this with the config/controller team. ***

4. openstack-dashboard/localsettings will now have MULTIDOMAIN configs enabled when v3 is enabled.

5. nova.conf seems to be coming directly form upstream kolla nova templates. Please check if this is causing operational issues and then we can debug/fix if required.