[SLIDER-1100] Support unique component names

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Slider 0.91
• Assignee: Billie Rinaldi
• Reporter: Billie Rinaldi
• Created: 15/Mar/16 21:37
• Updated: 15/Jun/16 15:20
• Resolved: 15/Jun/16 15:20

Description

I'd like to be able to specify a set of uniquely named components in a group as follows:

    "ROLE": {
      "component.unique.names": "true",
      "yarn.role.priority": "1",
      "yarn.component.instances": 3,
      "yarn.memory": "512",
      "yarn.vcores": "2"
    }

This ROLE would be a component specified in the metainfo, resources, and appConfig. When Slider sees the "unique.names" property set to true, it will create uniquely named components ROLE1, ROLE2, ROLE3, up to the number of instances specified. Each component will have a unique priority as well, allowing them to be distinguished from each other and strictly placed if desired.

This would allow the user to issue a flex command such as "slider flex clusterName --component ROLE 1" to change the number of instances; in this case, Slider would set ROLE2 and ROLE3 to zero desired instances, and leave ROLE1 at one desired instance. Uniquely named components would only have 0 or 1 desired instances. If the user flexed to a larger number of instances, Slider would create new component names as needed (e.g. ROLE4).

Issue Links

• breaks: SLIDER-1141 Populate status for unique components
• breaks: SLIDER-1138 Resource requirements not passed to unique components