yahoo-eng-team team mailing list archive

[OpenStack Infra <1655892@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

https://review.openstack.org/282407
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/nova" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 2195e4d68486ed70e55d0b5f038b13bd35e3271c
Author: Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Fri Feb 19 18:12:57 2016 +0200

    Hyper-V: Adds vNUMA implementation
    
    vNUMA can improve the performance of workloads running on virtual machines
    that are configured with large amounts of memory. This feature is useful
    for high-performance NUMA-aware applications, such as database or web
    servers.
    
    Returns Hyper-V host NUMA node information during get_available_resource
    Adds validation for instances requiring NUMA topology (no asymmetric
    topology and no CPU pinning supported).
    Creates NUMA aware instances, if necessary.
    
    The compute-cpu-topologies page in the admin-guide will have to be
    updated to include Hyper-V NUMA topologies usage and configuration.
    
    DocImpact
    
    Change-Id: Iba2110e95e80b9511698cb7df2963fd218264c8e
    Implements: blueprint hyper-v-vnuma-enable

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: doc nova

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1655892

Title:
      Hyper-V: Adds vNUMA implementation

Status in OpenStack Compute (nova):
  New

Bug description:
  https://review.openstack.org/282407
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/nova" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 2195e4d68486ed70e55d0b5f038b13bd35e3271c
  Author: Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>
  Date:   Fri Feb 19 18:12:57 2016 +0200

      Hyper-V: Adds vNUMA implementation
      
      vNUMA can improve the performance of workloads running on virtual machines
      that are configured with large amounts of memory. This feature is useful
      for high-performance NUMA-aware applications, such as database or web
      servers.
      
      Returns Hyper-V host NUMA node information during get_available_resource
      Adds validation for instances requiring NUMA topology (no asymmetric
      topology and no CPU pinning supported).
      Creates NUMA aware instances, if necessary.
      
      The compute-cpu-topologies page in the admin-guide will have to be
      updated to include Hyper-V NUMA topologies usage and configuration.
      
      DocImpact
      
      Change-Id: Iba2110e95e80b9511698cb7df2963fd218264c8e
      Implements: blueprint hyper-v-vnuma-enable

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1655892/+subscriptions