[tripleo-ui] Include deployed nodes in nodes assignment

Bug #1686037 reported by Jiri Tomasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Jiri Tomasek

Bug Description

Nodes deployed with a plan need to be included in available nodes counts in nodes assignment.

- include only nodes deployed to a currently active plan/stack
- scope nodes to a role - a deployed node can not be assigned to different role before it is undeployed (scaled down) in separate (re)deploy run.

expected DeployedNodes object (a selector return value):
{
  control: { node_uuid: { ...<node object>... }, ...},
  compute: { ... },
  ...
}

Ways to retrieve this data:
- resources of type OS::Tripleo::Server have physical_resource_id which is the nova instance uuid. A deployed node has instance_uuid.

Alternative:
- provide the information explicitly in stack output such as https://review.openstack.org/#/c/455753/1/overcloud.j2.yaml
- this approach is much more performant and simpler

Tags: ui
Jiri Tomasek (jtomasek)
Changed in tripleo:
milestone: none → pike-3
status: New → Triaged
Jiri Tomasek (jtomasek)
description: updated
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-ui (master)

Reviewed: https://review.openstack.org/455336
Committed: https://git.openstack.org/cgit/openstack/tripleo-ui/commit/?id=407b7eaac68ebc5211bbc8cf4ba62d10daaae9e9
Submitter: Jenkins
Branch: master

commit 407b7eaac68ebc5211bbc8cf4ba62d10daaae9e9
Author: Jiri Tomasek <email address hidden>
Date: Tue Apr 25 10:17:47 2017 +0200

    Include Deployed Nodes in NodesAssignment counts

    The nodes available for assigning are all nodes which
    are in available state or nodes which are deployed with
    currently selected plan.

    This change adds all deployed nodes to available nodes
    selector.

    This functionality needs to be further improved to completely
    fix referenced bug

    Partial-Bug: 1686037
    Change-Id: I2e33c2b32510a98a189425964e2e6269e5fbf741

Revision history for this message
Emilien Macchi (emilienm) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in tripleo:
status: In Progress → Triaged
assignee: Jiri Tomasek (jtomasek) → nobody
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Jiri Tomasek (jtomasek)
Changed in tripleo:
assignee: nobody → Jiri Tomasek (jtomasek)
status: Triaged → Fix Released
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.