Skip to content

Conversation

@gbenhaim
Copy link
Member

  1. user-data and meta-data can be specified directly under the cloud-init key in each
    domain definition. The content can be specified explicitly or by adding path to a file.

  2. For each domain, ISO file is generated and attached to the domain.

  3. Default settings can be found in the default templates which later will be modified using Jinja.

  4. Merge between user defined settings and default setting is done by utils.deep_update

Example:

domains:
  atomic-el:
    cloud-init:
      user-data:
        write_files:
          - path: /root/test
            content: bla_bla_bla
        users:
          - name: galito
        chpasswd:
          list: |
            galito:galgal

Signed-off-by: gbenhaim galbh2@gmail.com

@gbenhaim gbenhaim requested a review from nvgoldin August 23, 2017 08:49
@gbenhaim gbenhaim force-pushed the adding_cloud_init_support branch from 062643a to bf14669 Compare May 2, 2018 16:35
@gbenhaim
Copy link
Member Author

gbenhaim commented May 2, 2018

ci test please

@gbenhaim gbenhaim requested a review from mykaul May 3, 2018 14:22
@gbenhaim
Copy link
Member Author

gbenhaim commented May 3, 2018

I still need to complete the docstrings and do some cosmetics, but the overall functionality and basic unit/functional tests are implemented.

Signed-off-by: gbenhaim <galbh2@gmail.com>
@gbenhaim gbenhaim force-pushed the adding_cloud_init_support branch from bf14669 to 32e3671 Compare June 3, 2018 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants