yahoo-eng-team team mailing list archive

[OpenStack Infra <1742421@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/532491
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=30786b892e45602d76cea63ca4ae1172fb2e063e
Submitter: Zuul
Branch:    master

commit 30786b892e45602d76cea63ca4ae1172fb2e063e
Author: Liam Young <liam.young@xxxxxxxxxxxxx>
Date:   Wed Jan 10 11:06:37 2018 +0000

    Add exception to no-upcall note of cells doc
    
    The cells v2 layout documentation clearly states that there are no
    upcalls from cells back to the central API services. This mislead
    me for sometime as I could not fathom how a compute node in a cell
    was supposed to report its resource info.
    
    It turns out nova looks up the placement service in the keystone
    catalogue and contacts it directly which to my mind is an upcall. I
    wonder if the author of the not felt that the placement service is
    not really part of nova?
    
    Change-Id: If14be8b182f0af4e4e6641046fec638c07e26546
    Closes-Bug: #1742421


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  Cells Layout (v2) in nova doc misleading about upcalls

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  
  - [X] This doc is inaccurate in this way: Documentation suggests nova v2 cells do not make 'upcalls' but they do when talking to the placement api.
  - [ ] This is a doc addition request.
  - [ ] I have a fix to the document that I can paste below including example: input and output. 

  
  It is important to note that services in the lower cell boxes
  only have the ability to call back to the placement API and no other
  API-layer services via RPC, nor do they have access to the API database
  for global visibility of resources across the cloud. This is intentional
  and provides security and failure domain isolation benefits, but also has 
  impacts on somethings that would otherwise require this any-to-any 
  communication style. Check the release notes for the version of Nova you 
  are using for the most up-to-date information about any caveats that may be
  present due to this limitation.

  
  -----------------------------------
  Release: 17.0.0.0b3.dev323 on 2018-01-09 21:52
  SHA: 90a92d33edaea2b7411a5fd528f3159a486e1fd0
  Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/user/cellsv2-layout.rst
  URL: https://docs.openstack.org/nova/latest/user/cellsv2-layout.html

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