-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable AliYun datasource by default #2751
Comments
Launchpad user lawrence peng(kaihuan-pkh) wrote on 2016-11-24T06:33:51.874710+00:00 hi, Scott, as we discussed before, I need execute a I wonder to know is this plan could be feasible ? because of cloud-init source code is pure python, if I add the C code, it must compile when installed. the another hand, there are some third library module in python which could execute assembly, maybe I could import these module instead of write by myself ? thx ~ |
Launchpad user Scott Moser(smoser) wrote on 2016-12-13T14:51:14.537421+00:00 I really dont want to pick up a dependency on a library for this. It seems like surely there is some way to get at this information, or possibly we could work together to find a way for the platform to more obviously identify itself. Other platforms identify themselves in dmi data. $ cat /sys/class/dmi/id/sys_vendor |
Launchpad user Scott Moser(smoser) wrote on 2017-05-23T15:40:22.036893+00:00 The merge proposal attached here |
Launchpad user Chris J Arges(arges) wrote on 2017-08-23T12:27:47.637351+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-233-ge586fe35-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Chris J Arges(arges) wrote on 2017-08-23T12:31:13.644752+00:00 Hello Scott, or anyone else affected, Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-233-ge586fe35-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Chad Smith(chad.smith) wrote on 2017-08-29T20:52:30.347223+00:00 Hello Junjie.Wang, I believe you may be the best equipped to validate that this SRU works without error on AliYun cloud instances. Can you validate the bug per verification instructions that Best regards, |
Launchpad user Chad Smith(chad.smith) wrote on 2017-09-12T21:03:24.862143+00:00 Verifying this bug as it was originally contributed by the AliYun cloud maintainer as 'working' in their environment. Impact is limited only to the AliYun instances in this case and since we don't have access to easily deploy instance in AliYun's cloud, we take Junjie's recommendation here. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-09-13T01:26:05.837714+00:00 This bug was fixed in the package cloud-init - 0.7.9-233-ge586fe35-0ubuntu1~16.04.1 cloud-init (0.7.9-233-ge586fe35-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 31 Jul 2017 16:36:16 -0400 |
Launchpad user Chris Halse Rogers(raof) wrote on 2017-09-13T01:26:32.553792+00:00 The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-09-13T01:27:27.937540+00:00 This bug was fixed in the package cloud-init - 0.7.9-233-ge586fe35-0ubuntu1~17.04.1 cloud-init (0.7.9-233-ge586fe35-0ubuntu1~17.04.1) zesty; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 31 Jul 2017 16:33:24 -0400 |
Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:14:21.797692+00:00 This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. |
This bug was originally filed in Launchpad as LP: #1638931
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2016-11-03T14:05:04.694810+00:00
=== Begin SRU Template ===
[Impact]
Ubuntu cloud-images do not identify the Aliyun cloud platform.
Until this change was put in place, they would fail to boot and consume
user-data or metadata there.
With the change in place, an official Ubuntu image from
http://cloud-images.ubuntu.com will work properly on Aliyun.
[Test Case]
The ideal test case is:
a.) download a cloud image, update its cloud-init
The tool 'get-proposed-cloudimg' [1] can be used to do this.
b.) publish that image to Aliyun cloud
c.) boot an instance from that image.
d.) verify function by ssh in verifying /run/cloud-init/result.json shows
that aliyun datasource was used.
Ideally post /var/log/cloud-init.log as an attachment to this bug.
[Regression Potential]
Generally small chance for regression, but a regression would most likely
be seen as an attempt to hit the metadata service at the well known end point
http://100.100.100.200.
This should be fairly well confined as attempts to use the Aliyun datasource
are gated by 'is_aliyun' which does verifies that the dmi product name is
"Alibaba Cloud ECS"
[Other Info]
Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=4a60af5495
=== End SRU Template ===
As discussed at [1], the addition of AliYun datasource did not enable it by default.
This is because it has no definitive check before polling the network for data.
Lawrence suggested he has a solution for this:
| 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 I
| guess this is a method to identify our platform ?
--
[1] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/309614
The text was updated successfully, but these errors were encountered: