Merge lp:~edouardb/cloud-init/scaleway-datasource into lp:~cloud-init-dev/cloud-init/trunk
| Status: | Rejected |
|---|---|
| Rejected by: | Scott Moser on 2017-06-06 |
| Proposed branch: | lp:~edouardb/cloud-init/scaleway-datasource |
| Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
| Diff against target: |
443 lines (+414/-2) 3 files modified
cloudinit/sources/DataSourceScaleway.py (+216/-0) cloudinit/url_helper.py (+5/-2) tests/unittests/test_datasource/test_scaleway.py (+193/-0) |
| To merge this branch: | bzr merge lp:~edouardb/cloud-init/scaleway-datasource |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| cloud-init commiters | 2015-10-19 | Pending | |
|
Review via email:
|
|||
Description of the Change
Add Datasource for Scaleway's metadata service
| Julien Castets (jcastets) wrote : | # |
| Scott Moser (smoser) wrote : | # |
Hey,
This looks well done, thanks.
A couple comments
a.) we'll need some unit tests to ensure we dont inadvertently break this.
b.) is there some way (anyway) we can detect if we're on scaleway? As it is right now, it looks like we're just going to block and retry for the availability of the MD. That is much less than ideal, and the only current "on by default" datasource thtat does that is EC2 (which only gets that privilege from being first). Other vendors provide some dmi data or another quick local test.
c.) you'll need to sign the Canonical Contributors License Agreement (http://
d.) vendor-data would be nice (and helpful to you as the operator of the cloud.
again, though. Thanks, it looks really good.
Feel free to ping in #cloud-init if you have questions.
| Julien Castets (jcastets) wrote : | # |
Hi,
a) Done
b) Done. Unfortunately, there's no way to ensure you're running on Scaleway without hitting a network resource
c) Done
d) Indeed. Can we consider adding them later?
| Scott Moser (smoser) wrote : | # |
Julien,
Thanks.
for 'd', sure you can add vendor-data later.
if its not in the cloud provider anyway, not much use for cluod-init to support it.
The big issue is just 'b'. We can't enable by default without solid way of knowing that we should hit a http source that might hang indefinitely.
I'll revewi shortly.
| Julien Castets (jcastets) wrote : | # |
Great, thanks :) Waiting for your review then.
| Scott Moser (smoser) wrote : | # |
two nitpicks. but this looks good other than failing tests.
b
| Manfred Touron (moul) wrote : | # |
To check if you are on scaleway:
$ test -f /run/oc-
0
This file is populated when something fetches the api metadata.
Our initrd (https:/
| Scott Moser (smoser) wrote : | # |
Hi Eduardo,
Looking at this again.
Could you please sign the contributors agreement please feel free to contact me if you have any questions (freenode 'smoser') http://
Second, i think the check for /run/oc-
| Scott Moser (smoser) wrote : | # |
Hello,
Thank you for taking the time to contribute to cloud-init. Cloud-init has moved its revision control system to git. As a result, we are marking all bzr merge proposals as 'rejected'. If you would like to re-submit this proposal for review, please do so by following the current HACKING documentation at http://
Unmerged revisions
- 1154. By Edouard Bonlieu <email address hidden> on 2015-10-28
-
Merge jcastets PR
- 1153. By Edouard Bonlieu <email address hidden> on 2015-10-21
-
Pass userdata url and retries as parameters
- 1152. By Edouard Bonlieu <email address hidden> on 2015-10-21
-
Add a check to ensure we are on Scaleway
- 1151. By Edouard Bonlieu <email address hidden> on 2015-10-15
-
Add Datasource for Scaleway's metadata service (https:/
/www.scaleway. com) - 1150. By Edouard Bonlieu <email address hidden> on 2015-10-15
-
Add optional session parameter to readurl


Unlike other providers, the Scaleway user-data API is restricted to privileged ports (< 1024) to prevent non-root users accessing to it.
We added a new parameter to readurl to specify the requests session object, to bind on a specific port.