[
https://issues.apache.org/jira/browse/CLOUDSTACK-9566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611173#comment-15611173
]
ASF GitHub Bot commented on CLOUDSTACK-9566:
--------------------------------------------
GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/1738
CLOUDSTACK-9566 instance-id metadata for baremetal VM returns ID
There is difference in instance-id metadata across baremetal and other
hypervisors.
On Baremetal
[root@ip-172-17-0-144 ~]# curl
http://8.37.203.221/latest/meta-data/instance-id
6021
on Xen
[root@ip-172-17-2-103 ~]# curl
http://172.17.0.252/latest/meta-data/instance-id
cbeb517a-e833-4a0c-b1e8-9ed70200fbbf
In both cases it should be vm's uuid.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SudharmaJain/cloudstack cs-9566
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1738.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1738
----
commit 759a92d2516a99b90b59dc096f23e2e903d0673b
Author: Sudharma Jain <[email protected]>
Date: 2016-10-27T08:20:39Z
CLOUDSTACK-9566 instance-id metadata for baremetal VM returns ID
----
> instance-id metadata for baremetal VM returns ID
> ------------------------------------------------
>
> Key: CLOUDSTACK-9566
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9566
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: sudharma jain
>
> On Baremetal
> [root@ip-172-17-0-144 ~]# curl
> http://8.37.203.221/latest/meta-data/instance-id
> 6021
> on Xen
> [root@ip-172-17-2-103 ~]# curl
> http://172.17.0.252/latest/meta-data/instance-id
> cbeb517a-e833-4a0c-b1e8-9ed70200fbbf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
