Hi Robert and happy new year! :) If I understand correctly, with OKD, I just need to build full vm's in the > oVirt environment which will become hosts, compute nodes, for containers > that get deployed. >
You don't even need to build the VMs. If you follow the steps outlined here <https://docs.okd.io/3.11/install_config/configuring_for_rhv.html>, the installation playbooks will take care of creating the VMs for you. Otherwise, you're right. Those VM will become master, infra and compute nodes of OKD cluster. OKD is basically just container management and it does not care whether or > not the compute nodes are VM's or bare metal. > That's correct - at least in theory. In practice the difference is mostly in installation process. But you're right - once the OKD cluster is up and running, it does not care whether its nodes are VMs or bare metal machines. Best regards Jan On Thu, Dec 26, 2019 at 6:22 PM Robert Webb <rw...@ropeguru.com> wrote: > Jan, > > Thanks for taking the time for a great reply. > > For what I am trying to accomplish here in my home lab, it seems that OKD > is the safest path. If I understand correctly, with OKD, I just need to > build full vm's in the oVirt environment which will become hosts, compute > nodes, for containers that get deployed. OKD is basically just container > management and it does not care whether or not the compute nodes are VM's > or bare metal. > > Again, thanks for taking the time to educate me. > > Robert > > ________________________________________ > From: Jan Zmeskal <jzmes...@redhat.com> > Sent: Tuesday, December 24, 2019 4:43 PM > To: Robert Webb > Cc: users > Subject: Re: [ovirt-users] oVirt and Containers > > Okay, so this topic is quite vast, but I believe I can at the very least > give you a few pointers and maybe others might chime in as well. > > Firstly, there's the Kubevirt project. It enables you to manage both > application containers and virtual machines workloads (that cannot be > easily containerized) in a shared environment. Another benefit is getting > advantages of the powerful Kubernetes scheduler. I myself am not too > familiar with Kubevirt, so I can only offer this high-level overview. More > info here: https://kubevirt.io/ > > Then there is another approach which I am more familiar with. You might > want to use oVirt as an infrastructure layer on top of which you run > containerized workflow. This is achieved by deploying either OpenShift< > https://www.openshift.com/> or the upstream project OKD< > https://www.okd.io/> in the oVirt virtual machines. In that scenario, > oVirt VMs are considered by OpenShift as compute resources and are used for > scheduling containers. There are some advantages to this setup and two come > into mind. Firstly, you can scale such OpenShift cluster up or down by > adding/removing oVirt VMs according to your needs. Secondly, you don't need > to set up all of this yourself. > For OpenShift 3, Red Hat provides detailed guide on how to go about this. > Part of that guide are Ansible playbooks that automate the deployment for > you as long as you provide required variables. More info here: > https://docs.openshift.com/container-platform/3.11/install_config/configuring_for_rhv.html > When it comes to OpenShift 4, there are two types of deployment. There's > UPI - user provisioned infrastructure. In that scenario, you prepare all > the resources for OpenShift 4 beforehand and deploy it in that existing > environment. And there's also IPI - installer provisioned infrastructure. > This means that you just give the installer access to your environment > (e.g. AWS public cloud) and the installer provisions resources for itself > based on recommendations and best practices. At this point, neither UPI nor > IPI is supported for oVirt. However there is a GitHub repository< > https://github.com/sa-ne/openshift4-rhv-upi> that can guide you through > UPI installation on oVirt and also provides automation playbooks for that. > I have personally followed the steps from the repository and deployed > OpenShift 4.2 on top of oVirt without any major issues. As far as I > remember, I might have needed occasional variable here and there but the > process worked. > > Hope this helps! > Jan > > On Tue, Dec 24, 2019 at 8:21 PM Robert Webb <rw...@ropeguru.com<mailto: > rw...@ropeguru.com>> wrote: > Hi Jan, > > Honestly, I didn't have anything specific in mind, just what is being used > out there today and what may be more prevalent. > > Just getting my oVIrt set up and want to know what might be recommended. > Would probably be mostly deploying images like Homeassistent, piHole, etc.. > for now. > > I guess if there is good oVirt direct integration, it would be nice to > keep it all in a single interface. > > Thanks.. > > ________________________________________ > From: Jan Zmeskal <jzmes...@redhat.com<mailto:jzmes...@redhat.com>> > Sent: Tuesday, December 24, 2019 1:54 PM > To: Robert Webb > Cc: users > Subject: Re: [ovirt-users] oVirt and Containers > > Hi Robert, > > there are different answers based on what you mean by integrating oVirt > and containers. Do you mean: > > - Installing container management (Kubernetes or OpenShift) on top of > oVirt and using oVirt as infrastructure? > - Managing containers from oVirt interface? > - Running VM workloads inside containers? > - Something different? > > I can elaborate more based on your specific needs > > Best regards > Jan > > On Tue, Dec 24, 2019 at 3:52 PM Robert Webb <rw...@ropeguru.com<mailto: > rw...@ropeguru.com><mailto:rw...@ropeguru.com<mailto:rw...@ropeguru.com>>> > wrote: > I was searching around to try and figure out the best way to integrate > oVirt and containers. > > I have found some sites that discuss it but all of them are like 2017 and > older. > > Any recommendations? > > Just build VM’s to host containers or is there some direct integration? > > Here are a couple of the old sites > > https://fromanirh.github.io/containers-in-ovirt.html > > > https://kubernetes.io/docs/setup/production-environment/on-premises-vm/ovirt/ > > > https://www.ovirt.org/develop/release-management/features/integration/container-support.html > _______________________________________________ > Users mailing list -- users@ovirt.org<mailto:users@ovirt.org><mailto: > users@ovirt.org<mailto:users@ovirt.org>> > To unsubscribe send an email to users-le...@ovirt.org<mailto: > users-le...@ovirt.org><mailto:users-le...@ovirt.org<mailto: > users-le...@ovirt.org>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/7BIW2Z3ILBSAGQ4F7QB3MPEUWVW4GUUN/ > > > -- > > Jan Zmeskal > > Quality Engineer, RHV Core System > > Red Hat <https://www.redhat.com> > > [ > https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png > ]<https://www.redhat.com> > > > > -- > > Jan Zmeskal > > Quality Engineer, RHV Core System > > Red Hat <https://www.redhat.com> > > [ > https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png > ]<https://www.redhat.com> > > -- Jan Zmeskal Quality Engineer, RHV Core System Red Hat <https://www.redhat.com> <https://www.redhat.com>
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/422UVE35ZDZ7NHBLNBOJ3VPO45YKZSR4/
