software/js-drone: rename subinstances

Rename subinstances to avoid conflict. Once a subinstance is allocated on a
computer, changing `sla-computer_guid` does not move the subinstance. Therefore
an instance name containing the computer's guid is necessary.

software/js-drone/buildout.hash.cfg

@@ -22,7 +22,7 @@ md5sum = e0ea95530bf84edfc37eea994cc9ee86
 
 [instance-default]
 filename = instance-default.cfg.jinja2
-md5sum = 069f8947c55420ec013497d9eba56252
+md5sum = 2572f4c8e0f9bda92a5db1909c81b932
 
 [instance-peer]
 filename = instance-peer.cfg.jinja2.in

software/js-drone/instance-default.cfg.jinja2

@@ -10,7 +10,11 @@
 [{{ request_peer_section_title }}]
 <= slap-connection
 recipe = slapos.cookbook:request.serialised
-name = Peer{{ id }}
+{% if id < len(parameter_dict['droneGuidList']) -%}
+name = Drone{{ id }}_{{ guid }}
+{% else -%}
+name = Subscriber{{ len(parameter_dict['droneGuidList']) - id }}_{{ guid }}
+{% endif -%}
 software-url = ${:software-release-url}
 software-type = peer
 return = instance-path