HCI derived parameters workflow not using NovaVcpuPinSet

Bug #1711462 reported by Alan Bishop
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Alan Bishop

Bug Description

The mistral workflow that derives deployment parameters for HCI (hyperconverged Compute and Ceph-OSD) currently assumes all CPU cores identified in the baremetal introspection data are available for sharing between Nova and Ceph.

When NovaVcpuPinSet (THT parameter) is defined, the HCI derived parameters workflow must base its calculations on the number of cores in the set, and not use the total number of cores identified in the introspection data. NovaVcpuPinSet limits the number of cores available to Nova, and that same limit applies to Ceph-OSD in an HCI deployment.

If this issue is not corrected, the HCI derived parameters workflow will generate incorrect values that may significantly impact the performance of an HCI node.

Changed in tripleo:
assignee: nobody → Alan Bishop (alan-bishop)
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
milestone: none → pike-rc1
Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/489239
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=813e12ab9f3f49cef4dad477b15d53af9030bdf5
Submitter: Jenkins
Branch: master

commit 813e12ab9f3f49cef4dad477b15d53af9030bdf5
Author: Alan Bishop <email address hidden>
Date: Thu Aug 17 17:20:59 2017 -0400

    Use NovaVcpuPinSet when deriving HCI parameters

    When deriving deployment parameters for HCI (hyperconverged Nova compute and
    Ceph OSD nodes), use NovaVcpuPinSet to determine the number of CPU cores
    available for Nova and Ceph. When NovaVcpuPinSet isn't set, use all of the
    cores identified in the baremetal introspection data.

    Closes-Bug: #1711462
    Change-Id: I6e0a0004d3df1f7acbb15b014cc2fe5fb139c2aa

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/498549

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/pike)

Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/498549
Reason: I need to purge the gate because TripleO CI gate has critical issues right now, I'll make this patch goes to the gate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/pike)

Reviewed: https://review.openstack.org/498549
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=ac59ce053f972a28b20c0a5c22e7d073d0bb7202
Submitter: Jenkins
Branch: stable/pike

commit ac59ce053f972a28b20c0a5c22e7d073d0bb7202
Author: Alan Bishop <email address hidden>
Date: Thu Aug 17 17:20:59 2017 -0400

    Use NovaVcpuPinSet when deriving HCI parameters

    When deriving deployment parameters for HCI (hyperconverged Nova compute and
    Ceph OSD nodes), use NovaVcpuPinSet to determine the number of CPU cores
    available for Nova and Ceph. When NovaVcpuPinSet isn't set, use all of the
    cores identified in the baremetal introspection data.

    Closes-Bug: #1711462
    Change-Id: I6e0a0004d3df1f7acbb15b014cc2fe5fb139c2aa
    (cherry picked from commit 813e12ab9f3f49cef4dad477b15d53af9030bdf5)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 7.6.0

This issue was fixed in the openstack/tripleo-common 7.6.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 8.0.0

This issue was fixed in the openstack/tripleo-common 8.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.