[tripleo-ui] Include deployed nodes in nodes assignment

[Jiri Tomasek]

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

[OpenStack Infra (hudson-openstack)]

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

[Emilien Macchi (emilienm)]

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.