yahoo-eng-team team mailing list archive

[Augustina Ragwitz <1548443@xxxxxxxxxxxxxxxxxx>]

Documentation that talks about allocation ratio need to be updated.

For instance, this:
http://docs.openstack.org/openstack-ops/content/compute_nodes.html#overcommit

Here is the added help text for the cli:
https://review.openstack.org/#/c/277953/11/nova/compute/resource_tracker.py


** Also affects: openstack-manuals
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Invalid

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

Title:
      Update ComputeNode values with disk allocation ratios in the RT

Status in OpenStack Compute (nova):
  Invalid
Status in openstack-manuals:
  New

Bug description:
  https://review.openstack.org/277953
  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 ad6654eaa7c44267ae3a4952a8359459fbec4c0c
  Author: Sylvain Bauza <sbauza@xxxxxxxxxx>
  Date:   Tue Feb 9 17:35:47 2016 +0100

      Update ComputeNode values with disk allocation ratios in the RT
      
      Now that we have added the field for persisting the disk alloc ratio, we can
      have the ResouceTracker persisting it by adding it to the local ComputeNode
      object which is persisted by calling the _update() method.
      It will then send by default 0.0 unless the operator explicitely specified an
      allocation ratio in the compute nova.conf.
      
      Thanks to the ComputeNode object hydratation on the scheduler side, the facade
      will make sure that if a default 0.0 is provided by either a compute node or
      by the scheduler's nova.conf, it will actually get the original allocation
      ratios (ie. 1.0 for disk)
      Since the Scheduler reads the same RT opt but goes thru the ComputeNode object,
      it will also get the Facade returning 1.0 unless the operator
      explicitely provided other ratios for the scheduler's nova.conf
      
      Amending the release note now that the behaviour is changing.
      
      DocImpact Disk alloc ratio is now per computenode
      UpgradeImpact
      
      Change-Id: Ief6fa32429d58b80e70029ed67c7f42e0bdc986d
      Implements: blueprint disk-allocation-ratio-to-rt

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