yahoo-eng-team team mailing list archive

[chuang <nashuiliang@xxxxxxxxx>]

Public bug reported:

Description
===========
When I is ready to install [nova-placement-api], I find that not detailed document describe how to install and configure [nova-placement-api].

Steps
=====
When I have installed [nova-compute], I found many *WARNNING* logs. eg:

WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Unable to refresh my resource provider record
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Unable to refresh my resource provider record
WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.

I carefully view the [nova-compute] code. I find that when the [nova-compute] starts to running, it invokes the "ComputeManager.update_available_resources" to update the resources of the current compute node into the database. 
Then, "ResourceTracker.update_available_resource", "ResourceTracker._init_compute_node" are invoked, this will initialize the compute node if it does not already exist. Then, "SchedulerReportClient.update_compute_node" is invoked to update the resource of  the current compute node. Here. I find that it will send the request to the placement-api, but i'm not.
So, how to install and configure placement-api?

Environment
===========
commit 7280f4fc4c5a2203ac2f59a9df0525488ac2c1ff
Author: Artom Lifshitz <alifshit@xxxxxxxxxx>
Date:   Mon Jan 9 18:57:17 2017 +0000

    Libvirt support for tagged volume attachment
    
    This patch adds support for tagged volume attachment to the libvirt
    driver.
    
    Change-Id: I8b475992b881db08cf1354299cc86042413074cc
    Implements: blueprint bp/virt-device-tagged-attach-detach

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova-placement-api detailed document

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  When I is ready to install [nova-placement-api], I find that not detailed document describe how to install and configure [nova-placement-api].

  Steps
  =====
  When I have installed [nova-compute], I found many *WARNNING* logs. eg:

  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Unable to refresh my resource provider record
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Unable to refresh my resource provider record
  WARNING nova.scheduler.client.report [req-642b06ce-08e7-4a07-b6c2-f53d429aa4fd None None] Placement API service is not responding.

  I carefully view the [nova-compute] code. I find that when the [nova-compute] starts to running, it invokes the "ComputeManager.update_available_resources" to update the resources of the current compute node into the database. 
  Then, "ResourceTracker.update_available_resource", "ResourceTracker._init_compute_node" are invoked, this will initialize the compute node if it does not already exist. Then, "SchedulerReportClient.update_compute_node" is invoked to update the resource of  the current compute node. Here. I find that it will send the request to the placement-api, but i'm not.
  So, how to install and configure placement-api?

  Environment
  ===========
  commit 7280f4fc4c5a2203ac2f59a9df0525488ac2c1ff
  Author: Artom Lifshitz <alifshit@xxxxxxxxxx>
  Date:   Mon Jan 9 18:57:17 2017 +0000

      Libvirt support for tagged volume attachment
      
      This patch adds support for tagged volume attachment to the libvirt
      driver.
      
      Change-Id: I8b475992b881db08cf1354299cc86042413074cc
      Implements: blueprint bp/virt-device-tagged-attach-detach

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