mlsorensen opened a new pull request, #6710:
URL: https://github.com/apache/cloudstack/pull/6710

   Signed-off-by: Marcus Sorensen <[email protected]>
   
   ### Description
   
   This PR allows the cloud admin to set either a global or domain-specific 
value "metadata.allow.expose.domain", and when set this allows the VM to see 
the name and ID of the immediate domain that contains the VM in instance 
metadata. This can be useful or a variety of things such as bootstrapping VM 
configuration and access according to domain.
   
   This PR also deletes the CloudZonesNetworkElement because it isn't referred 
to anywhere, and there was initially some confusion as to whether this code 
needed to be updated when extending metadata.  If it needs to be kept we can 
remove that delete from the PR.
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [x] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [x] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ```
   [root@test-vm ~]# cloud-init query ds.meta_data.cloud_domain
   mydomain
   
   [root@test-vm ~]# cloud-init query ds.meta_data.cloud_domain_id
   e41e92fa-0498-4e76-b4b3-5948a44a9309
   ```
   
   ### How Has This Been Tested?
   Tested in a local branch, released to an internal UAT environment for a few 
weeks. Also updated metadata Marvin test.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to