yahoo-eng-team team mailing list archive

[Tracy Jones <tjones@xxxxxxxxxx>]

sorry - bugs that affect only a particular hypervisor cannot be
critical.  I'll add this to the vmwareapi-team and mark critical.

** Changed in: nova
   Importance: Critical => High

** Also affects: openstack-vmwareapi-team
   Importance: Undecided
       Status: New

** Changed in: openstack-vmwareapi-team
   Importance: Undecided => Critical

** Changed in: openstack-vmwareapi-team
       Status: New => In Progress

-- 
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/1329261

Title:
  vmware: VCdriver creates same hypervisor_hostname for different
  vcenters with same Cluster name

Status in OpenStack Compute (Nova):
  In Progress
Status in The OpenStack VMwareAPI subTeam:
  In Progress

Bug description:
  Consider the following scenario, where two nova-compute nodes are
  configured to different vcenter with same cluster named "Cluster1":

  Compute-Node #1:
  -----------------------
  hostname:  devstack1
  vmware.host_ip:  10.1.0.12
  vmware.cluster_names:  Cluster1   << Same cluster name


  
  Compute-Node #2:
  -------------------------
  hostname:  devstack2
  vmware.host_ip:  10.1.0.13
  vmware.cluster_names:  Cluster1   << Same cluster name

  hypervisor_hostname=domain-c26(Cluster1)

  
   In this scenario, VC driver creates the same value for  compute_nodes.hypervisor_hostname  as mentioned here.

  ------------------------------------------------
  Compute_node | hypervisor_hostname
  ------------------------------------------------
  #1 | domain-c26(Cluster1)
  #2 | domain-c26(Cluster1)
  ------------------------------------------------

   Because same compute_nodes.hypervisor_hostname is created for more
  than one clusters, it creates the following issues in the horizon:

  1. In admin->Hypervisors, the same CPU, Memory utilization is reported for both the clusters
  2. In admin -> Hypervisors-> [Click on Hypervisor #1]->, the details page reports the same list of instance for both the clusters.

  Though the issue is seen in the horizon, the actual root cause is
  because vcdriver creates the same hypervisor_hostname for both the
  clusters.

  so this bug is filed to fix this issue, to create the hypervisor_hostname as follows:
  <vmware.host_ip (vmware.cluster_name)> 

  Ex: 10.1.0.12 (Cluster1)

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