Merge ~jingni.wjj/cloud-init:aliyun_dev into cloud-init:master
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 4a60af54957634920e84a928aa22b4fc9a6dfd11 | ||||
| Proposed branch: | ~jingni.wjj/cloud-init:aliyun_dev | ||||
| Merge into: | cloud-init:master | ||||
| Diff against target: |
52 lines (+9/-1) 3 files modified
cloudinit/settings.py (+1/-0) cloudinit/sources/DataSourceAliYun.py (+7/-1) tests/unittests/test_datasource/test_common.py (+1/-0) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Moser | Needs Fixing on 2017-05-22 | ||
| Server Team CI bot | continuous-integration | 2017-04-27 | Approve on 2017-04-27 |
| Junjie.Wang (community) | Approve on 2017-04-27 | ||
|
Review via email:
|
|||
This proposal supersedes a proposal from 2017-04-27.
Commit Message
AliYun: Enable platform identification and enable by default.
AliYun cloud platform is now identifying themselves by setting the dmi product id to the well known value "Alibaba Cloud ECS". The changes here identify that properly in tools/ds-identify and in the DataSourceAliYun.
Since the 'get_data' for AliYun now identifies itself correctly, we
can enable AliYun by default.
LP: #1638931
Description of the Change
AliYunDataSource support get platform from bios dmi
Eanble AliYunDataSource by default
PASSED: Continuous integration, rev:50339971d26
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Junjie.Wang (jingni.wjj) wrote : | # |
hi smoser,
I have some change here, and they seem to work fine.
cloud_platform: get platform from bios,in our cloud platform , an instance vm could use an asm instructions `cpuid` (with eax setted to 0x40000100 ), it will returned our platform id keyword "AliYun" into register ebx and ecx, and if vm is not running on our environment, the value is others. so cloud-init will not block a long time when call datesource's get_data() method if it's use network
| Scott Moser (smoser) wrote : | # |
Junjie,
This looks great.
You should also make a change to tools/ds-identify.
Then, thanks!
I'll look at this again on monday.
| Scott Moser (smoser) wrote : | # |
Junjie,
Thanks again. I've put some changes in at
http://
And updated the commit message here.
Please integrate those changes into this branch, test and then comment.
I'm really happy to see AliYun supported by default.
Scott
| Scott Moser (smoser) wrote : | # |
Junjie,
I've proposed a merge at
https:/
that has your changes and then my suggested changes on top.
I'd appreciate your feedback there.
| Junjie.Wang (jingni.wjj) wrote : | # |
> Junjie,
> I've proposed a merge at
> https:/
> that has your changes and then my suggested changes on top.
>
> I'd appreciate your feedback there.
I am sorry for late reply,i review this code that is good ,and test it in our AliYun paltform ,it also work fine.thanks very much
| Scott Moser (smoser) wrote : | # |
I marked this merged based on the other branch being merged.
Thanks again, Junjie.


FAILED: Continuous integration, rev:2bb7e229703 544aac1ca2d6420 cabaf40aa70509 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 286/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/286/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/286/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 286/console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/286/ console /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/286/ console
https:/
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 286/rebuild
https:/