When users are trying to get resource details of a specified stack , there are many call's between httpd and heat-api.
For stack Identification ,the following are requested:
1) Identify the stack based on stack id
2) Get the template details
3) Gets the details of specified stack
4) Gets the resource of specified stack
5) Get implementation details with nova api
To list out resource of a stack:
1) Get the stack
2) Gets the templates details
3) Gets the resource details of a specified stack
In each case Two request have been made to get the details
1st: get : HTTP <302> response
2nd: get: HTTP <201> response
As user knows HTTP <302> used for url redirection and <201> is for success, those two request should be merged into one request to get details in one request. By which the number of interaction between httpd and heat-api can be minimize. This will improve the performance of the use case.
It is indeed unfortunate that the API requires you to know *both* the name and the UUID of the stack before you can fetch details about it directly.
That said, I am yet to be convinced that this is a major problem. It only takes one API call to figure out the name & UUID if you don't know them both already. In the context of the 5+ you're apparently doing (though I have no idea why) that seems fairly minimal.
> This will improve the performance of the use case.
Do we have any evidence for this?