Where we are - and where we go with oVirt Node Fabian Deutsch, Red - - PowerPoint PPT Presentation

▶
where we are and where we go with ovirt node
SMART_READER_LITE
LIVE PREVIEW

Where we are - and where we go with oVirt Node Fabian Deutsch, Red - - PowerPoint PPT Presentation

Aug 23, 2023 249 likes •407 views

Where we are - and where we go with oVirt Node Fabian Deutsch, Red Hat oVirt Workshop Oct 16 2014 https://www.flickr.com/photos/mrmuskrat/3637703614 What it is Hypervisor for oVirt Minimal OS image prepared for oVirt

slide-1
SLIDE 1

Where we are - and where we go with oVirt Node

Fabian Deutsch, Red Hat

  • Virt Workshop

Oct 16 2014

slide-2
SLIDE 2

What it is

  • “Hypervisor” for oVirt
  • Minimal OS image prepared for oVirt
  • Installation/upgrade on bare-metal
  • Custom Installer TUI & Setup TUI
  • Easy to deploy, manage and upgrade

https://www.flickr.com/photos/mrmuskrat/3637703614

slide-3
SLIDE 3

What it is

Demo

https://www.flickr.com/photos/mrmuskrat/3637703614

slide-4
SLIDE 4

Pains

  • User Experience

○ SELinux ○ Installation (multipath, iscsi, efi, secureboot, …) ○ Customization (kmods, offline + online) ○ Consumption (persistence)

  • Maintenance
  • Build

https://www.flickr.com/photos/transposition/4448015432

slide-5
SLIDE 5

Causes

  • User experience

○ read-only rootfs ○ installation ○ customization

  • Developers

○ consumption / persistence ○ testing

https://www.flickr.com/photos/31031835@N08/10007190363

slide-6
SLIDE 6

Changes

  • No custom installer
  • Regular “writable” root filesystem

Technically behaves like a regular OS

  • Split rootfs, from TUI, from deployment
slide-7
SLIDE 7

Installation

  • Installer: Anaconda

○ Using a regular kickstart

slide-8
SLIDE 8

Storage

  • Specific LVM usage pattern

○ Boot into writable thin-volume a top a read-only “original”

https://www.flickr.com/photos/ejorpin/6480285651

slide-9
SLIDE 9

Upgrade

  • Add a new image + new boot entry

○ Number of upgrades is limited by disk size ○ Rollback: Select old entry, boot into old image

slide-10
SLIDE 10

Local Administration

  • Runtime Setup TUI is kept

○ Simplified below the surface

slide-11
SLIDE 11

Improvements

★ Easier

○ to consume by payloads (vdsm, ...) ○ building + test ○ to extend (just a package)

★ Open to configuration management ★ Add packages/kmods (at runtime)

https://www.flickr.com/photos/therealmichaelmoore/5471061169

slide-12
SLIDE 12

Links

  • Prosa

○ http://dummdida.tumblr.com/tagged/node

  • Sources

○ https://github.com/fabiand/imgbased/

  • CI

○ https://travis-ci.org/fabiand/imgbased ○ http://jenkins.ovirt.org/view/All/job/fabiand_ovirt-node- tng_image_build_daily/ ○ http://jenkins.ovirt.org/view/All/job/fabiand_ovirt-node- tng_image_check_functional/ ○ http://jenkins.ovirt.org/view/All/job/fabiand_ovirt-node- tng_image_check_install/

https://www.flickr.com/photos/therealmichaelmoore/5471061169

slide-13
SLIDE 13

Open questions

  • Stateless

○ Previous Node side blocker: Where to keep the state ○ Option: Generic Registration and/or Foreman ○ Diskless?

  • Maximum minimization (smallest size)

○ Foreman Discovery Image

slide-14
SLIDE 14
slide-15
SLIDE 15

Tech - Components