Integrating oVirt and Foreman to Empower your Data-Center

Integrating oVirt and Foreman to Empower your Data-Center

In this session Yaniv will give a short introduction to oVirt and Foreman and discuss about integrating the two in order to ease deployment of hypervisors and VMs in a virtualized environment. Yaniv will describe how oVirt leverages Foreman functionality to provision bare-metal hosts or add existing ones as oVirt hypervisors, and how we plan to extend that in order to provisioning VMs, configure existing hypervisors, and more.

Share the knowledge
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

25 thoughts on “Integrating oVirt and Foreman to Empower your Data-Center

  1. Ohad, updated to 5 years (my bad). guess also the amount of contributes and
    users grew since then 

  2. I only understand less than a third of the video because your english
    pronunciation on the video was far from that of native speakers.

  3. it is supposed to be able to set PXE, DHCP, and etc… in order to be able
    to start the bare metal machine.

  4. Foreman allows you to configure a lot more than cobbler. stuff like puppet
    classes, templates, host groups, networking stuff, and etc…

  5. did i misunderstand? It looked like the new hardware pxe-booted foreman’s
    tinyos, in order to report back to foeman. Wouldnt that mean pxeboot in the
    same network as the nodes?

  6. I am running a tiny cobbler setup for managing my oVirt development
    environment. I guess it’s time to upgrade 🙂

  7. Red Hat seems to think so. The next version of satellite abandons cobbler,
    for newer rechnologies. Foreman included.

  8. Including a “helper address” in your router will allow you to serve
    multiple subnets from a DHCP server not on the subnet.

  9. but saying that Foreman is “just” a replacement for cobbler is a
    mis-statement, it does a lot more than Cobbler does.

  10. The oVirt-Foreman integration allows you to have a bare-metal host and make
    it a hypervisor, without the need to manually install OS on it.

  11. we run a segregated build network, and machines get moved out of tht
    network once theyre built. Is there any nice way to automate a move like
    that via foreman?

  12. does this require that you run a foreman proxy, with dhcp and tftp and
    whatnot, in the same subnet as your rhev-h/ovirt-nodes?

Leave a Reply

Your email address will not be published. Required fields are marked *