cloud-init/doc/examples/cloud-config-datasources.txt
Scott Moser c10de5db0f add reading of 'seedfrom' via DataSourceNoCloud's DataSourceConfig
What this does is provide an second DataSource that could use the
kernel command line url=.  For example:
  ro root=/dev/vda url=http://example.com/i-abcdefg/

http://example.com/i-abcdefg/ would contain:
datasource:
  NoCloud:
    # default seedfrom is None
    # if found, then it should contain a url with:
    #    <url>/user-data and <url>/meta-data
    # seedfrom: http://my.example.com/i-abcde
    seedfrom: http://example.com/i-abcdefg/

Then, the NoCloudNet DataSource would find that seedfrom config
and consume data at
  http://example.com/i-abcdefg/user-data
and
  http://example.com/i-abcdefg/meta-data
2012-04-04 22:05:17 -04:00

34 lines
1.0 KiB
Plaintext

# Documentation on data sources configuration options
datasource:
# Ec2
Ec2:
# timeout: the timeout value for a request at metadata service
timeout : 50
# The length in seconds to wait before giving up on the metadata
# service. The actual total wait could be up to
# len(resolvable_metadata_urls)*timeout
max_wait : 120
#metadata_url: a list of URLs to check for metadata services
metadata_urls:
- http://169.254.169.254:80
- http://instance-data:8773
MAAS:
timeout : 50
max_wait : 120
# there are no default values for metadata_url or oauth credentials
# If no credentials are present, non-authed attempts will be made.
metadata_url: http://mass-host.localdomain/source
consumer_key: Xh234sdkljf
token_key: kjfhgb3n
token_secret: 24uysdfx1w4
NoCloud:
# default seedfrom is None
# if found, then it should contain a url with:
# <url>/user-data and <url>/meta-data
# seedfrom: http://my.example.com/i-abcde
seedfrom: None