)]}'
{"specs/pike/approved/veritas-hyperscale-filter.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":27,"context_line":"resilient, high performance storage to OpenStack virtual machines."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"HyperScale will provide block storage to OpenStack VM to leverage commodity"},{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_0fc5695a","line":30,"range":{"start_line":30,"start_character":16,"end_line":30,"end_character":19},"updated":"2017-02-16 22:06:15.000000000","message":"I don\u0027t know what DAS is here, probably better to not use the acronym.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"eb773827cee0d8b9a904576feec07eeb6cf2df09","unresolved":false,"context_lines":[{"line_number":27,"context_line":"resilient, high performance storage to OpenStack virtual machines."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"HyperScale will provide block storage to OpenStack VM to leverage commodity"},{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_c1041dc8","line":30,"range":{"start_line":30,"start_character":16,"end_line":30,"end_character":19},"in_reply_to":"fa31d9ce_0fc5695a","updated":"2017-02-18 16:58:48.000000000","message":"I think it refers to direct-attached storage? But yeah, best to put \"(DAS)\" after the words \"direct-attached storage\" in your first paragraph.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"eb773827cee0d8b9a904576feec07eeb6cf2df09","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"HyperScale will provide block storage to OpenStack VM to leverage commodity"},{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_e10921df","line":31,"updated":"2017-02-18 16:58:48.000000000","message":"To be perfectly honest, there\u0027s no need to have the problem description be a product marketing blurb. :) You can just state something to the effect of \"Customers of Veritas HyperScale storage would like to use the product for storing virtual machines. This blueprint is for enabling that.\"\n\nAlso, not sure what \"off-hosting services\" is? Did you mean \"offloading services\" maybe?","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"2446ba020b700ba66839a59bb0d66c7f6c2164e7","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"HyperScale will provide block storage to OpenStack VM to leverage commodity"},{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_73ffa601","line":31,"in_reply_to":"da36d5c6_e10921df","updated":"2017-02-20 19:13:20.000000000","message":"Two points : \n* I understand this as being an use-case : \"As a customer, I\u0027d like to use my fresh and cool storage solution by making sure I\u0027m only placing calls to hosts supporting it\"\n* while I think it can be an use-case, I don\u0027t see any problem statement in there that would require a Nova modification without having other workarounds.\n\nFor example, a valid solution is to use aggregates, right? Why that is not enough so that it would require to write a totally new filter?","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"eb773827cee0d8b9a904576feec07eeb6cf2df09","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"},{"line_number":35,"context_line":"sure that they have enough local storage to host the VM. This helps HyperScale"},{"line_number":36,"context_line":"maintain the locality of storage and ensure predictable IO performance."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_41202d4a","line":33,"updated":"2017-02-18 16:58:48.000000000","message":"What is a \"HyperScale enabled compute\"? Is that just a compute node that is attached to a Veritas HyperScale storage solution? Or is there some special configuration or something?","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"},{"line_number":35,"context_line":"sure that they have enough local storage to host the VM. This helps HyperScale"},{"line_number":36,"context_line":"maintain the locality of storage and ensure predictable IO performance."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Without such a filter, Nova VMs may get deployed on computes with less than"},{"line_number":39,"context_line":"adequate local storage with undesirable results."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_0f73a94e","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":71},"updated":"2017-02-16 22:06:15.000000000","message":"Why can\u0027t we use the existing scheduler filters that rely on host aggregate metadata and flavor extra specs for matching a particular flavor with a particular set of hosts? For example, the admin creates a veritas aggregate and puts 3 hosts in it which are using veritas for storage, and then adds metadata to the aggregate. They then create specific flavors with extra specs that match the aggregate and then instances created from those flavors are placed on those hosts. I think there are other filters that make it possible to only match instances with certain flavor extra specs to land on those hosts, but would need to dig into those details - but the point being those flavors and only those flavors are used to put instances on those specific hosts, and nothing else. Sylvain probably knows the specific filters for this.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"2446ba020b700ba66839a59bb0d66c7f6c2164e7","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"},{"line_number":35,"context_line":"sure that they have enough local storage to host the VM. This helps HyperScale"},{"line_number":36,"context_line":"maintain the locality of storage and ensure predictable IO performance."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Without such a filter, Nova VMs may get deployed on computes with less than"},{"line_number":39,"context_line":"adequate local storage with undesirable results."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_b3091e2f","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":71},"in_reply_to":"da36d5c6_41f90dc8","updated":"2017-02-20 19:13:20.000000000","message":"See my comment above. Things can be done without requiring a specific filter that would expose a specific hardware type.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"eb773827cee0d8b9a904576feec07eeb6cf2df09","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storage and get DAS performance combined with resiliency, quality of service"},{"line_number":31,"context_line":"and off-hosting services."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"In order to place virtual machines on HyperScale enabled computes this filter"},{"line_number":34,"context_line":"is required which will identify and filter HyperScale enabled hosts and make"},{"line_number":35,"context_line":"sure that they have enough local storage to host the VM. This helps HyperScale"},{"line_number":36,"context_line":"maintain the locality of storage and ensure predictable IO performance."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Without such a filter, Nova VMs may get deployed on computes with less than"},{"line_number":39,"context_line":"adequate local storage with undesirable results."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_41f90dc8","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":71},"in_reply_to":"fa31d9ce_0f73a94e","updated":"2017-02-18 16:58:48.000000000","message":"Yes, agreed with Matt. That was my first thought: what makes the Veritas HyperScale scenario different from, say, a compute attached to an NFS share or one that uses a Ceph volume group?","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"2446ba020b700ba66839a59bb0d66c7f6c2164e7","unresolved":false,"context_lines":[{"line_number":36,"context_line":"maintain the locality of storage and ensure predictable IO performance."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Without such a filter, Nova VMs may get deployed on computes with less than"},{"line_number":39,"context_line":"adequate local storage with undesirable results."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"This blueprint proposes to add such a filter to Nova."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_7326c6bb","line":39,"updated":"2017-02-20 19:13:20.000000000","message":"That\u0027s untrue, you can totally achieve your usecase without requiring this filter. Again, see above the problem with that not being a real problem statement.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":51,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"A Nova filter for Veritas HyperScale called hyperscale_filter.py will be added"},{"line_number":54,"context_line":"to nova/scheduler/filters directory. This module will implement the"},{"line_number":55,"context_line":"\"host_passes\" function to filter out the hosts based on the criteria mentioned"},{"line_number":56,"context_line":"above."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"To use this driver, the user has to have the Veritas HyperScale compute"},{"line_number":59,"context_line":"package installed. This provides the following components that are required"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_afd0ddf8","line":56,"range":{"start_line":54,"start_character":37,"end_line":56,"end_character":6},"updated":"2017-02-16 22:06:15.000000000","message":"Again, what is special about this that can\u0027t be solved with aggregates and flavor extra specs? Does something in the scheduler filter actually inspect the host capabilities to see if they are running veritas and get their resource usage to tell if they can fit a given instance for build? If so, that is completely bypassing the nova compute resource tracker, compute_nodes table and placement service, so it\u0027s not something we\u0027d want to include in Nova I don\u0027t think.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"2446ba020b700ba66839a59bb0d66c7f6c2164e7","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":"This software can be downloaded from the following location:"},{"line_number":65,"context_line":"https://www.veritas.com/product/software-defined-storage/hyperscale-for-openstack.html"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"Alternatives"},{"line_number":68,"context_line":"------------"},{"line_number":69,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da36d5c6_334c4e70","line":66,"updated":"2017-02-20 19:13:20.000000000","message":"I\u0027m very against adding an in-tree filter that would require a very specific implementation of a driver that couldn\u0027t be tested unless requiring a specific access to download it and install it.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":67,"context_line":"Alternatives"},{"line_number":68,"context_line":"------------"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"None."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Data model impact"},{"line_number":73,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_6f0b457e","line":70,"updated":"2017-02-16 22:06:15.000000000","message":"There are alternatives to this as noted above.\n\nAlso, I think it\u0027s worth talking to Jay Pipes, Ed Leafe, Chris Dent and/or Sylvain Bauza about how this could be integrated with the placement service such that an external system running your mgmt package can mark certain resource providers (compute hosts) in the placement service as being able to serve these types of requests, either using traits (something we\u0027ll be talking about for the Pike release) or custom resource classes:\n\nhttps://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/custom-resource-classes.html","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":93,"context_line":"---------------------"},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"In cases where the filter is enabled and unable to find the right kind of hosts"},{"line_number":96,"context_line":"scheduler will not eb able to place the VM and instance will fail to deploy."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Performance Impact"},{"line_number":99,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_af253d0b","line":96,"range":{"start_line":96,"start_character":19,"end_line":96,"end_character":21},"updated":"2017-02-16 22:06:15.000000000","message":"be","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Performance Impact"},{"line_number":99,"context_line":"------------------"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"None."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"Other deployer impact"},{"line_number":104,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_cf699127","line":101,"updated":"2017-02-16 22:06:15.000000000","message":"I don\u0027t believe this - if the management package in your filter has to call out to an external system, or inspect the hosts at the time of scheduling, there is going to be a cost associated with that.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":104,"context_line":"---------------------"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Veritas HyperScale Management software must be installed on the OpenStack"},{"line_number":107,"context_line":"control plane. Atleast one compute must have the Veritas HyperScale storage"},{"line_number":108,"context_line":"service installed on it. This new filter must be enabled in nova.conf and"},{"line_number":109,"context_line":"added to the list of existing filters. This will be done by the HyperScale"},{"line_number":110,"context_line":"deployment mechanism."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_ef765505","line":107,"range":{"start_line":107,"start_character":15,"end_line":107,"end_character":22},"updated":"2017-02-16 22:06:15.000000000","message":"At least","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":135,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Nova blueprint for Veritas HyperScale volume driver extension"},{"line_number":138,"context_line":"https://blueprints.launchpad.net/nova/+spec/veritas-hyperscale-libvirt-volume-driver"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"Testing"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa31d9ce_af537d6b","line":138,"updated":"2017-02-16 22:06:15.000000000","message":"Why is the libvirt volume driver a dependency for this? Because you have to have those types of volumes attached to the instances for this to work? Please explain.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"fb16a56c1141701706c23015e56eff9ab2cd09e1","unresolved":false,"context_lines":[{"line_number":140,"context_line":"Testing"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"None."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"Documentation Impact"},{"line_number":146,"context_line":"\u003d\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":3,"id":"fa31d9ce_8fd5d9ba","line":143,"updated":"2017-02-16 22:06:15.000000000","message":"I think we\u0027re going to at least require 3rd party CI for a scheduler filter whose control logic is entirely packaged in a proprietary external management system.","commit_id":"c8f084432c110d4db5f8246f37a7db2a8ccdeb08"}]}