operation engine should work with brief keystone response
Bug #1577697 reported by
yinwei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Karbor |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
During integrating smaug with hybrid cloud, we found that fsp will cut keystone response to a brief format, where service catelogs are not included here.
This will make operation engine not work.
We need have operation engine to be compatible with this case, say, read service catelog from config file etc.
Revision history for this message
| Saggi Mizrahi (ficoos) wrote | #1 |
| Changed in karbor: | |
| importance: | Undecided → Low |
| importance: | Low → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
We need the service catalog to know where everything is. I don't see how it makes sense to force admins to keep the config file in sync with the actual service configuration.
I think the problem is in hybrid cloud and not Karbor.