95b70b100e
This change adds Nodes table action to tag Nodes to a Profile By selecting nodes in table and clicking 'Tag Nodes' table action, A form is displayed to let user select from existing profiles or specify custom one. Available profiles are gathered from the list of existing profiles on all nodes and roles available in current plan The way Nodes are stored in app state is slightly changed. Node ports are normalized into separate map in nodes state. References to them are stored in 'portsDetail' Node attribute rather than 'ports' so in case when node is updated (response does not include nested ports), the portsDetail won't get overwritten Partial-Bug: #1640103 Change-Id: Icc61fbeda133845b5aadef8b749db20c2c411d3a |
||
---|---|---|
.. | ||
environmentConfiguration.js | ||
nodes.js | ||
parameters.js | ||
plans.js | ||
roles.js | ||
stacks.js | ||
validations.js | ||
workflowExecutions.js |