Flavor detail page does not exist

[Sudheer Kalla]

Horizon dashboard does not contain over view page for each flavor . While CLI having support for flavor details by the command nova flavor-show {id}, I guess dashboard should also contain an option to view the flavor details .

[Nikunj Aggarwal (nikunj2512)]

Can you expand on the bug summary because the heading and the summary are mismatched.

You want details of which flavors are there on the project-> overview page or you want details page for the flavors??

[Sudheer Kalla (sudheer-kalla)]

Just like instance or networks provide an overview page when we click on a particular instance or network, similarly flavor too should have an overview page which gives the details of the flavor

[Sudheer Kalla (sudheer-kalla)]

Hi Nikunj Aggarwal,

Thank you for assigning this bug but iam already started working on this bug so iam re-assigning my slef to this bug

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/145696

[OpenStack Infra (hudson-openstack)]

Change abandoned by David Lyle (<email address hidden>) on branch: master
Review: https://review.openstack.org/145696
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Matt Borland (palecrow)]

Confirmed that there is no 'details' page for Flavors. Low priority, Wishlist feature item.

[Ankur (ankur-gupta-f)]

Not sure what other details one would create in an Overview page for flavors. What would be details would need to go into an overview page.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/410693

[OpenStack Infra (hudson-openstack)]

Change abandoned by Yakup Adaklı (<email address hidden>) on branch: master
Review: https://review.openstack.org/410693

[Akihiro Motoki (amotoki)]

The patch mentioned in #8 was abandoned in favor of AngularJS implementation, but we no longer apply such strong requirements and we also accept Django based implementation for new features.

[Akihiro Motoki (amotoki)]

Actually all fields are displayed in the flavor overview page, so there is no need to have a flavor detail page.
In most cases, detail pages are to show more information on resources, but a flavor detail is not the case.
We don't deny to add the flavor detail page, but this is super low priority.