Project

General

Profile

Feature #20590

Full cloud-init support with ovirt provider

Added by Ivan Necas 11 months ago. Updated 10 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

the cloud-init
integration with ovirt supports just a sub-set of cloud-init keys.

The following template seems to be the maximal set of keys we
can currently pass successfully to the cloud-init via user_data:

#cloud-init
hostname: test.example.com
ssh_authorized_keys:
- ssh-rsa test123123123 test.example.com
runcmd:
- ls /
phone_home:
  url: satellite.example.com
  post: []

Cloud-init supports much wider range or modules and configuration options,
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#. Currently
we don't support those and this options get ignored.

Version-Release number of selected component (if applicable):
Foreman 1.15 with fog-1.42.0

How reproducible:
Always

Steps to Reproduce:
1. add user_data image with cloud-init installed and configured.
2. use one of the valid cloud-init keys that ARE NOT one of `hostname`, `ssh_authorized_keys`, `runcmd`, `phone_home`,
an example could be:

#cloud-init
yum_repos:
    zoo:
        baseurl: https://inecas.fedorapeople.org/fakerepos/new_cds/content/zoo/1.0/x86_64/rpms/
        name: zoo
        enabled: true

Actual results:
Many cloud-init modules options get ignored (including the `yum_repos` one in the example)

Expected results:
All cloud-init modules options get passed to cloud-init (including the `yum_repos` one in the example)


Related issues

Related to Foreman - Bug #20591: Support for multi-line runcmd cloudinit commands in oVirtClosed2017-08-14
Related to Foreman - Bug #24217: Support shell script cloud-init format for oVirtClosed2018-07-10

Associated revisions

Revision d3cd2536 (diff)
Added by Ivan Necas 3 months ago

Fixes #20590 - full ovirt cloud-init support

Currently, the cloud-init integration supports only a sub-set of
cloud-init commands. With `custom_script` support, one can pass
arbitrary cloud-init yaml to the managed host and make sure
the provisioned host will get it unchanged (which is not the case
when passing the user data currently, as the rbovirt parses into
ovirt-specific keys)

After the change, we would pass the cloud-init template to the ovirt as
is via `custom_script` ovirt functionality, and it would get to the
cloud-init directly, without any ovirt pre-processing.

Depends on https://github.com/fog/fog/pull/3961

History

#1 Updated by Ivan Necas 11 months ago

  • Related to Feature #8289: use cloudinit user data in ovirt/rhev compute ressource added

#2 Updated by Ivan Necas 11 months ago

  • Bugzilla link set to 1481315

#3 Updated by Ivan Necas 11 months ago

  • Category set to Compute resources - oVirt

#4 Updated by Ivan Necas 11 months ago

  • Related to Bug #20591: Support for multi-line runcmd cloudinit commands in oVirt added

#5 Updated by The Foreman Bot 11 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4744 added

#6 Updated by Ivan Necas 11 months ago

  • Pull request https://github.com/fog/fog/pull/3961 added

#7 Updated by Ivan Necas 11 months ago

  • Pull request https://github.com/abenari/rbovirt/pull/121 added

#8 Updated by keith lin 4 months ago

  • Related to deleted (Feature #8289: use cloudinit user data in ovirt/rhev compute ressource)

#9 Updated by Ivan Necas 3 months ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#10 Updated by Ori Rabin about 2 months ago

  • Legacy Backlogs Release (now unused) set to 353

#11 Updated by Ivan Necas 10 days ago

  • Related to Bug #24217: Support shell script cloud-init format for oVirt added

Also available in: Atom PDF