[GitHub] brooklyn-docs issue #156: Suggest using unique custom.machine.namer.machine

[aledsage <gi...@git.apache.org>]

Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/156
  
    Instead of this change, I think it would be better to add to `guide/ops/locations/_azure-ARM.md`, to say that the cloud-machine-namer needs to give a unique name for each VM (which is different from other clouds)! In aws for example, jclouds appends some randomly generated suffix for the security group it creates (I believe).
    
    If I'm right about that difference, then @bostko can you please open an issue in jclouds so that it behaves the same as other clouds for appending a random name (cc @andreaturli).
    
    See https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions for azure's guidelines on naming.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---