~ahosmanmsft/cloud-init:azurecloudtests

Branch merges

Propose for merging

Merged into cloud-init:master at revision aa3e4961ceae5a5c5b5cf13221b5f6721991fe75

Server Team CI bot: Needs Fixing (continuous-integration) on 2019-11-25

Chad Smith: Approve on 2019-11-13

Diff: 911 lines (+760/-2)

15 files modified

.pylintrc (+1/-1)
doc/rtd/topics/tests.rst (+52/-0)
integration-requirements.txt (+9/-0)
tests/cloud_tests/platforms.yaml (+6/-0)
tests/cloud_tests/platforms/__init__.py (+2/-0)
tests/cloud_tests/platforms/azurecloud/__init__.py (+0/-0)
tests/cloud_tests/platforms/azurecloud/image.py (+108/-0)
tests/cloud_tests/platforms/azurecloud/instance.py (+243/-0)
tests/cloud_tests/platforms/azurecloud/platform.py (+232/-0)
tests/cloud_tests/platforms/azurecloud/regions.json (+42/-0)
tests/cloud_tests/platforms/azurecloud/snapshot.py (+58/-0)
tests/cloud_tests/platforms/ec2/image.py (+1/-0)
tests/cloud_tests/platforms/ec2/platform.py (+2/-1)
tests/cloud_tests/releases.yaml (+2/-0)
tox.ini (+2/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

6d682c1... by Ahmed on 2019-11-25

space to tab pylint

059e3e5... by Ahmed on 2019-11-25

pylint

2702609... by Ahmed on 2019-11-25

more pylint errors

91e4bd3... by Ahmed on 2019-11-25

fixed pylint error

57c275a... by Ahmed on 2019-11-25

added integration requirements to pylint

8529cba... by Ahmed on 2019-11-25

fixed lazy logging

3baf88c... by Ahmed on 2019-11-25

Merge branch 'master' of https://git.launchpad.net/cloud-init into azurecloudtests

4bc399e... by Ryan Harper on 2019-11-23

ec2: Add support for AWS IMDS v2 (session-oriented) (#55)

* ec2: Add support for AWS IMDS v2 (session-oriented)

AWS now supports a new version of fetching Instance Metadata[1].

Update cloud-init's ec2 utility functions and update ec2 derived
datasources accordingly. For DataSourceEc2 (versus ec2-look-alikes)
cloud-init will issue the PUT request to obtain an API token for
the maximum lifetime and then all subsequent interactions with the
IMDS will include the token in the header.

If the API token endpoint is unreachable on Ec2 platform, log a
warning and fallback to using IMDS v1 and which does not use
session tokens when communicating with the Instance metadata
service.

We handle read errors, typically seen if the IMDS is beyond one
etwork hop (IMDSv2 responses have a ttl=1), by setting the api token
to a disabled value and then using IMDSv1 paths.

To support token-based headers, ec2_utils functions were updated
to support custom headers_cb and exception_cb callback functions
so Ec2 could store, or refresh API tokens in the event of token
becoming stale.

[1] https://docs.aws.amazon.com/AWSEC2/latest/ \
UserGuide/ec2-instance-metadata.html \
#instance-metadata-v2-how-it-works

eb65ed5... by Ahmed on 2019-11-22

added pylintrc

30679da... by Ahmed on 2019-11-22

increased boot_timout