[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-19 Thread Alexey Serbin (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Serbin updated KUDU-3067:

Fix Version/s: 1.12.0
   Resolution: Fixed
   Status: Resolved  (was: In Review)

> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Assignee: Alexey Serbin
>Priority: Major
> Fix For: 1.12.0
>
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-18 Thread Alexey Serbin (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Serbin updated KUDU-3067:

Code Review: http://gerrit.cloudera.org:8080/15488

[~seanlau], could you verify that the fix published at 
http://gerrit.cloudera.org:8080/15488 works as expected?

> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Assignee: Alexey Serbin
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-18 Thread Alexey Serbin (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Serbin updated KUDU-3067:

Status: In Review  (was: In Progress)

> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Assignee: Alexey Serbin
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-18 Thread Alexey Serbin (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Serbin updated KUDU-3067:

Status: Open  (was: In Review)

> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Assignee: Alexey Serbin
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-18 Thread Alexey Serbin (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Serbin updated KUDU-3067:

Status: In Review  (was: Open)

> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Assignee: Alexey Serbin
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-02 Thread liusheng (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liusheng updated KUDU-3067:
---
Description: 
The cloud detector is used to check the cloud provider of the instance, see 
[here|#L59-L93]],  For AWS cloud it using the URL 
[http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
 to check the specific metadata to determine it is AWS instance. This is OK, 
but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
also be accessed. So this cannot distinct the AWS and other OpenStack based 
clouds. This caused an issue when run "HybridClockTest.TimeSourceAutoSelection" 
test case, this test will use the above URL to detect the Cloud of instance 
current running on and then try to call the NTP service, for AWS, the dedicated 
NTP service is "169.254.169.123", but for OpenStack based cloud, there isn't 
such a dedicated NTP service. So this test case will fail if I run on a 
instance of OpenStack based cloud because the cloud detector suppose it is AWS 
instance and try to access "169.254.169.123".

 

  was:
The cloud detector is used to check the cloud provider of the instance, see 
[here|#L59-L93]],  For AWS cloud it using the URL 
[http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
 to check the specific metadata to determine it is AWS instance. This is OK, 
but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
also be accessed. So this cannot distinct the AWS and other OpenStack based 
clouds. This caused an issue when run "HybridClockTest.TimeSourceAutoSelection" 
test case, this test will use the above URL to detect the Cloud of instance 
current running on and then try to call the NTP service, for AWS, the dedicated 
NTP service is "169.254.169.123", but for OpenStack based cloud, there isn't 
such a dedicated NTP service. So this test case will fail if I run on a 
instance of OpenStack based cloud.

 


> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud because the cloud detector suppose it is AWS instance 
> and try to access "169.254.169.123".
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-02 Thread liusheng (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liusheng updated KUDU-3067:
---
Description: 
The cloud detector is used to check the cloud provider of the instance, see 
[here|[https://github.com/apache/kudu/blob/master/src/kudu/util/cloud/instance_detector.cc#L59-L93]],
  For AWS cloud it using the URL 
"*http://169.254.169.254/latest/meta-data/instance-id*"; to check the specific 
metadata to determine it is AWS instance. This is OK, but for OpenStack based 
cloud, the metadata is same with AWS, so this URL can also be accessed. So this 
cannot distinct the AWS and other OpenStack based clouds. This caused an issue 
when run "HybridClockTest.TimeSourceAutoSelection" test case, this test will 
use the above URL to detect the Cloud of instance current running on and then 
try to call the NTP service, for AWS, the dedicated NTP service is 
"169.254.169.123", but for OpenStack based cloud, there isn't such a dedicated 
NTP service. So this test case will fail if I run on a instance of OpenStack 
based cloud.

 

  was:
The cloud detector is used to check the cloud provider of the instance, see 
[here|[[1]https://github.com/apache/kudu/blob/master/src/kudu/util/cloud/instance_detector.cc#L59-L93|https://github.com/apache/kudu/blob/master/src/kudu/util/cloud/instance_detector.cc#L59-L93]],
  For AWS cloud it using the URL 
"http://169.254.169.254/latest/meta-data/instance-id"; to check the specific 
metadata to determine it is AWS instance. This is OK, but for OpenStack based 
cloud, the metadata is same with AWS, so this URL can also be accessed. So this 
cannot distinct the AWS and other OpenStack based clouds. This caused an issue 
when run "HybridClockTest.TimeSourceAutoSelection" test case, this test will 
use the above URL to detect the Cloud of instance current running on and then 
try to call the NTP service, for AWS, the dedicated NTP service is 
"169.254.169.123", but for OpenStack based cloud, there isn't such a dedicated 
NTP service. So this test case will fail if I run on a instance of OpenStack 
based cloud.

 


> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|[https://github.com/apache/kudu/blob/master/src/kudu/util/cloud/instance_detector.cc#L59-L93]],
>   For AWS cloud it using the URL 
> "*http://169.254.169.254/latest/meta-data/instance-id*"; to check the specific 
> metadata to determine it is AWS instance. This is OK, but for OpenStack based 
> cloud, the metadata is same with AWS, so this URL can also be accessed. So 
> this cannot distinct the AWS and other OpenStack based clouds. This caused an 
> issue when run "HybridClockTest.TimeSourceAutoSelection" test case, this test 
> will use the above URL to detect the Cloud of instance current running on and 
> then try to call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-02 Thread liusheng (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liusheng updated KUDU-3067:
---
Description: 
The cloud detector is used to check the cloud provider of the instance, see 
[here|#L59-L93]],  For AWS cloud it using the URL 
[http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
 to check the specific metadata to determine it is AWS instance. This is OK, 
but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
also be accessed. So this cannot distinct the AWS and other OpenStack based 
clouds. This caused an issue when run "HybridClockTest.TimeSourceAutoSelection" 
test case, this test will use the above URL to detect the Cloud of instance 
current running on and then try to call the NTP service, for AWS, the dedicated 
NTP service is "169.254.169.123", but for OpenStack based cloud, there isn't 
such a dedicated NTP service. So this test case will fail if I run on a 
instance of OpenStack based cloud.

 

  was:
The cloud detector is used to check the cloud provider of the instance, see 
[here|#L59-L93]],  For AWS cloud it using the URL 
*[http://169.254.169.254/latest/meta-data/instance-id*] to check the specific 
metadata to determine it is AWS instance. This is OK, but for OpenStack based 
cloud, the metadata is same with AWS, so this URL can also be accessed. So this 
cannot distinct the AWS and other OpenStack based clouds. This caused an issue 
when run "HybridClockTest.TimeSourceAutoSelection" test case, this test will 
use the above URL to detect the Cloud of instance current running on and then 
try to call the NTP service, for AWS, the dedicated NTP service is 
"169.254.169.123", but for OpenStack based cloud, there isn't such a dedicated 
NTP service. So this test case will fail if I run on a instance of OpenStack 
based cloud.

 


> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> [http://169.254.169.254/latest/meta-data/instance-id|http://169.254.169.254/latest/meta-data/instance-id*]
>  to check the specific metadata to determine it is AWS instance. This is OK, 
> but for OpenStack based cloud, the metadata is same with AWS, so this URL can 
> also be accessed. So this cannot distinct the AWS and other OpenStack based 
> clouds. This caused an issue when run 
> "HybridClockTest.TimeSourceAutoSelection" test case, this test will use the 
> above URL to detect the Cloud of instance current running on and then try to 
> call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

2020-03-02 Thread liusheng (Jira)


 [ 
https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liusheng updated KUDU-3067:
---
Description: 
The cloud detector is used to check the cloud provider of the instance, see 
[here|#L59-L93]],  For AWS cloud it using the URL 
*[http://169.254.169.254/latest/meta-data/instance-id*] to check the specific 
metadata to determine it is AWS instance. This is OK, but for OpenStack based 
cloud, the metadata is same with AWS, so this URL can also be accessed. So this 
cannot distinct the AWS and other OpenStack based clouds. This caused an issue 
when run "HybridClockTest.TimeSourceAutoSelection" test case, this test will 
use the above URL to detect the Cloud of instance current running on and then 
try to call the NTP service, for AWS, the dedicated NTP service is 
"169.254.169.123", but for OpenStack based cloud, there isn't such a dedicated 
NTP service. So this test case will fail if I run on a instance of OpenStack 
based cloud.

 

  was:
The cloud detector is used to check the cloud provider of the instance, see 
[here|[https://github.com/apache/kudu/blob/master/src/kudu/util/cloud/instance_detector.cc#L59-L93]],
  For AWS cloud it using the URL 
"*http://169.254.169.254/latest/meta-data/instance-id*"; to check the specific 
metadata to determine it is AWS instance. This is OK, but for OpenStack based 
cloud, the metadata is same with AWS, so this URL can also be accessed. So this 
cannot distinct the AWS and other OpenStack based clouds. This caused an issue 
when run "HybridClockTest.TimeSourceAutoSelection" test case, this test will 
use the above URL to detect the Cloud of instance current running on and then 
try to call the NTP service, for AWS, the dedicated NTP service is 
"169.254.169.123", but for OpenStack based cloud, there isn't such a dedicated 
NTP service. So this test case will fail if I run on a instance of OpenStack 
based cloud.

 


> Inexplict cloud detection for AWS and OpenStack based cloud by querying 
> metadata
> 
>
> Key: KUDU-3067
> URL: https://issues.apache.org/jira/browse/KUDU-3067
> Project: Kudu
>  Issue Type: Bug
>Reporter: liusheng
>Priority: Major
>
> The cloud detector is used to check the cloud provider of the instance, see 
> [here|#L59-L93]],  For AWS cloud it using the URL 
> *[http://169.254.169.254/latest/meta-data/instance-id*] to check the specific 
> metadata to determine it is AWS instance. This is OK, but for OpenStack based 
> cloud, the metadata is same with AWS, so this URL can also be accessed. So 
> this cannot distinct the AWS and other OpenStack based clouds. This caused an 
> issue when run "HybridClockTest.TimeSourceAutoSelection" test case, this test 
> will use the above URL to detect the Cloud of instance current running on and 
> then try to call the NTP service, for AWS, the dedicated NTP service is 
> "169.254.169.123", but for OpenStack based cloud, there isn't such a 
> dedicated NTP service. So this test case will fail if I run on a instance of 
> OpenStack based cloud.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)