When a user launches an instance, set the instance name based on the Server Template.

If the same instance name exists, the number postfix (#1, #2, #3…) can be added at the end of the Server Template name.

e.g. Server Template name: Cloud Orchestrator

  • The 1st instance name: Cloud Orchestrator #1
  • The 2nd instance name: Cloud Orchestrator #2
  • The 3rd instance name: Cloud Orchestrator #3

If a user specify more than two instance count, the naming assignment should follow the above naming convention.

If a user specify only one single instance count (1), the naming assignment doesn't have to follow the above naming convention. The naming assignment should be e.g. Cloud Orchestrator as it is.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Xiaohua Guan created an issue. See original summary.

Xiaohua Guan’s picture

Xiaohua Guan’s picture

FileSize
4.53 KB
Xiaohua Guan’s picture

FileSize
4.53 KB
Xiaohua Guan’s picture

Status: Active » Needs review
yas’s picture

Issue summary: View changes
FileSize
280.98 KB

@xiaohua-guan

Thank you for the patch. I found that the ServerTemplate name didn't have the postfix #2, #3 in my environment. Could you please check that? FYI, I attached the screenshot.

screenshot-20190409a

On second thought, I changed the specification for the multiple count use case. I made the font bold that

yas’s picture

Issue summary: View changes
FileSize
205.52 KB

@xiaohua-guan,

More diving into the detail use case, please see also the following screenshot:

screenshot-20190409b

yas’s picture

@xiaohua-guan

It would be nice if you can implement (three (3) instance count):

  1. 1st Launch:
    1. Cloud Orchestrator #1
    2. Cloud Orchestrator #2
    3. Cloud Orchestrator #3
  2. 2nd Launch:
    1. Cloud Orchestrator #2-1
    2. Cloud Orchestrator #2-2
    3. Cloud Orchestrator #2-3
  3. 3rd Launch:
    1. Cloud Orchestrator #3-1
    2. Cloud Orchestrator #3-2
    3. Cloud Orchestrator #3-3
  4. ...

Probably it is rather easier to implement by preserving the current patch?

yas’s picture

Status: Needs review » Needs work
Xiaohua Guan’s picture

FileSize
10.3 KB
Xiaohua Guan’s picture

Status: Needs work » Needs review
Xiaohua Guan’s picture

@yas

I changed the name as you said in comment #8. Please confirm and review the patch file. Thanks.

yas’s picture

FileSize
209.74 KB

@xiaohua-guan

Thank you for the updated patch. I tested and looks good to me as the following screenshot:

screenshot-20190410a_0

@baldwinlouie
@masami

What do you think?

baldwinlouie’s picture

@all, this looks good.

yas’s picture

Status: Needs review » Reviewed & tested by the community

@baldwinlouie

Thank you for your review. I'll merge the patch to 8.x-1.x and 8.x-2.x and close this issue as Fixed.

  • yas committed c510b48 on 8.x-1.x authored by Xiaohua Guan
    Issue #3046737 by Xiaohua Guan, yas, baldwinlouie: Assign the Instance...

  • yas committed 36cbf22 on 8.x-2.x authored by Xiaohua Guan
    Issue #3046737 by Xiaohua Guan, yas, baldwinlouie: Assign the Instance...
yas’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.