)]}'
{"nova/scheduler/weights/rendezvous_hash.py":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"947e6f515941baf7f54c9ecd2ea13ec2320093c4","unresolved":true,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"class RendezvousHashingWeigher(weights.BaseHostWeigher):"},{"line_number":26,"context_line":"    \"\"\"Rendezvous hashing weigher."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"    Weigh hosts by their rendezvous hashing score."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-python","patch_set":2,"id":"3614f983_8957a9e9","line":26,"updated":"2024-10-26 00:55:28.000000000","message":"this is combiningn 2 diffent idea i had that perhaps should not be combined.\n\n1 i have wanted to have a \"boreing host weigher\" that prefers host with the the minium number of resocue classes and trait for  a long time\n\ni also learned about Rendezvous hashing today and that i can be used to avoid thundering heard probelems\n\n\nim not sure if combingn the two in this form makes sense but i think teh \n\"boreing host weigher\"\n\nprobably should exist","commit_id":"57527d6e34b004eebf9b4ca82d88509e5d3f0099"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"947e6f515941baf7f54c9ecd2ea13ec2320093c4","unresolved":true,"context_lines":[{"line_number":71,"context_line":"        # into a string. A more robust implementation would be to"},{"line_number":72,"context_line":"        # bias the hash by factoring in resource usage and other"},{"line_number":73,"context_line":"        # factors such as which resources are available but not requested"},{"line_number":74,"context_line":"        keys \u003d mapping.keys()"},{"line_number":75,"context_line":"        # We want to shuffle the keys if the weight multiplier is negative"},{"line_number":76,"context_line":"        # so that we don\u0027t always pick the same host when the multiplier"},{"line_number":77,"context_line":"        # is negative."}],"source_content_type":"text/x-python","patch_set":2,"id":"6a697d46_0ffa4db5","line":74,"updated":"2024-10-26 00:55:28.000000000","message":"i dont think this is actully correct what i wanted to pull was the list of resocue classes and traits form the provider summaries assocated with the current host.","commit_id":"57527d6e34b004eebf9b4ca82d88509e5d3f0099"}]}