)]}'
{"specs/stein/approved/bandwidth-resource-provider.rst":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"81f4a7c243564192c5edd104ecdf808988373bbe","unresolved":false,"context_lines":[{"line_number":13,"context_line":"This spec proposes adding new resource classes representing network"},{"line_number":14,"context_line":"bandwidth and modeling network backends as resource providers in"},{"line_number":15,"context_line":"Placement. As well as adding scheduling support for the new resources in Nova."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Problem description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_3800e5ab","line":16,"updated":"2018-08-30 13:00:43.000000000","message":"Could you add a note that the neutron side of this lives in https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"81f4a7c243564192c5edd104ecdf808988373bbe","unresolved":false,"context_lines":[{"line_number":149,"context_line":"server in Nova and passes in the port UUID in the server create request."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"Nova fetches the port data from Neutron. This already happens in"},{"line_number":152,"context_line":"create_pci_requests_for_sriov_ports in the current code base. The port contains"},{"line_number":153,"context_line":"the requested resources and required traits. See"},{"line_number":154,"context_line":"`Resource request in the port`_."},{"line_number":155,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_82bfc9a8","line":152,"range":{"start_line":152,"start_character":0,"end_line":152,"end_character":35},"updated":"2018-08-30 13:00:43.000000000","message":"``create_resource_requests`` now, right?","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"81f4a7c243564192c5edd104ecdf808988373bbe","unresolved":false,"context_lines":[{"line_number":153,"context_line":"the requested resources and required traits. See"},{"line_number":154,"context_line":"`Resource request in the port`_."},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"The create_pci_requests_for_sriov_ports() call needs to be refactored to a more"},{"line_number":157,"context_line":"generic call that not just generates PCI requests but also collects the"},{"line_number":158,"context_line":"requested resources from the Neutron ports."},{"line_number":159,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_42e3f1d9","line":156,"range":{"start_line":156,"start_character":4,"end_line":156,"end_character":39},"updated":"2018-08-30 13:00:43.000000000","message":"ditto","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"d9f0a9141b8c9917550b98c48b8a46b668d47bda","unresolved":false,"context_lines":[{"line_number":321,"context_line":"  desirable. For example it makes perfect sense to guarantee 5 gigabits of a"},{"line_number":322,"context_line":"  10 gigabit card to somebody and let the rest to be used on a best effort"},{"line_number":323,"context_line":"  basis. To allow this we only need to turn the logic around and use traits"},{"line_number":324,"context_line":"  CUSTOM_GUARANTEED_BW and CUSTOM_BEST_EFFORT_BW. If the admin still wants to"},{"line_number":325,"context_line":"  keep guaranteed and best effort traffic fully separated then s/he never puts"},{"line_number":326,"context_line":"  both traits on the same RP. But one can mix them if one wants to. Even the"},{"line_number":327,"context_line":"  possible starvation of best effort traffic (next to guaranteed traffic) could"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_5845a142","line":324,"updated":"2018-08-29 16:04:28.000000000","message":"Are there plans to make standard traits for this kind of thing? On some other spec I said that we shouldn\u0027t ever publish code that itself uses CUSTOM traits. They should only be for individual deployments.","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"de9e8eec2dd2f1e081eb5d54ddd770b7542a2463","unresolved":false,"context_lines":[{"line_number":321,"context_line":"  desirable. For example it makes perfect sense to guarantee 5 gigabits of a"},{"line_number":322,"context_line":"  10 gigabit card to somebody and let the rest to be used on a best effort"},{"line_number":323,"context_line":"  basis. To allow this we only need to turn the logic around and use traits"},{"line_number":324,"context_line":"  CUSTOM_GUARANTEED_BW and CUSTOM_BEST_EFFORT_BW. If the admin still wants to"},{"line_number":325,"context_line":"  keep guaranteed and best effort traffic fully separated then s/he never puts"},{"line_number":326,"context_line":"  both traits on the same RP. But one can mix them if one wants to. Even the"},{"line_number":327,"context_line":"  possible starvation of best effort traffic (next to guaranteed traffic) could"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_bf25a50c","line":324,"in_reply_to":"3f79a3b5_5845a142","updated":"2018-08-30 10:50:35.000000000","message":"i had floated the idea of haveing project sepcific traists in the past we at the time the suggstion was to use the custom namesapces.\n\nwould you make these stadard traits as\nNW_GUARANTEED_BW or NEUTRON_GUARANTEED_BW?","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"6e8d511e55f57e1ce8ab85a6bf9b05810da00207","unresolved":false,"context_lines":[{"line_number":321,"context_line":"  desirable. For example it makes perfect sense to guarantee 5 gigabits of a"},{"line_number":322,"context_line":"  10 gigabit card to somebody and let the rest to be used on a best effort"},{"line_number":323,"context_line":"  basis. To allow this we only need to turn the logic around and use traits"},{"line_number":324,"context_line":"  CUSTOM_GUARANTEED_BW and CUSTOM_BEST_EFFORT_BW. If the admin still wants to"},{"line_number":325,"context_line":"  keep guaranteed and best effort traffic fully separated then s/he never puts"},{"line_number":326,"context_line":"  both traits on the same RP. But one can mix them if one wants to. Even the"},{"line_number":327,"context_line":"  possible starvation of best effort traffic (next to guaranteed traffic) could"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_f1f03100","line":324,"in_reply_to":"3f79a3b5_bf25a50c","updated":"2018-08-30 11:18:43.000000000","message":"I imagine we need to convene an international consortium of experts to decide on the right naming scheme, but I can say that putting \"neutron\" in the name is not a good reason for the same reason that the service catalog is keyed by type, not name.","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"81f4a7c243564192c5edd104ecdf808988373bbe","unresolved":false,"context_lines":[{"line_number":575,"context_line":""},{"line_number":576,"context_line":".. _`nested-resource-providers`: https://review.openstack.org/556873"},{"line_number":577,"context_line":".. _`granular-resource-request`: https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/granular-resource-requests.html"},{"line_number":578,"context_line":".. _`QoS minimum bandwidth allocation in Placement API`: https://review.openstack.org/#/c/508149"},{"line_number":579,"context_line":".. _`override-compute-node-uuid`: https://blueprints.launchpad.net/nova/+spec/override-compute-node-uuid"},{"line_number":580,"context_line":".. _`vnic_types are defined in the Neutron API`:  \u003e https://developer.openstack.org/api-ref/network/v2/#show-port-details"},{"line_number":581,"context_line":".. _`blindly copy the allocation from source host to destination host`: https://github.com/openstack/nova/blob/9273b082026080122d104762ec04591c69f75a44/nova/scheduler/utils.py#L372"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_78f65ddb","line":578,"range":{"start_line":578,"start_character":0,"end_line":578,"end_character":96},"updated":"2018-08-30 13:00:43.000000000","message":"Could you update this to https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html ?","commit_id":"ca841b773c532bfd1ea674c8b7f818cb1224cf8d"}]}