Docker best practices

Hi Alex, would you mind being more specific with your question? What are you trying to achieve? Petr On 16.7.2018 17:42, Николаев Алексей wrote:
Hi, community! What are best practices to run docker images into oVirt infra: core os or something else?
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/UB4H3Y7VYQ6R2A...

I'm currently using CoreOS as a VM and I like it. RancherOS performs similarly, but appears to have a smaller footprint. I doubt you will see a big different in performance. I'm sure ovirt can handle them both fine. You can also spin up a RH or CentOS vm and install docker just fine. But the smaller footprints are nice. CoreOS was recently aquired by redhat if I'm not mistaken, so I went with CoreOS personally. On Mon, Jul 16, 2018, 11:45 AM Николаев Алексей < alexeynikolaev.post@yandex.ru> wrote:
Hi, community!
What are best practices to run docker images into oVirt infra: core os or something else? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/UB4H3Y7VYQ6R2A...

We're using rancher on Ovirt and it's great. No problems to report. On Wed, Jul 18, 2018, 1:08 PM Wesley Stewart, <wstewart3@gmail.com> wrote:
I'm currently using CoreOS as a VM and I like it. RancherOS performs similarly, but appears to have a smaller footprint.
I doubt you will see a big different in performance. I'm sure ovirt can handle them both fine.
You can also spin up a RH or CentOS vm and install docker just fine. But the smaller footprints are nice.
CoreOS was recently aquired by redhat if I'm not mistaken, so I went with CoreOS personally.
On Mon, Jul 16, 2018, 11:45 AM Николаев Алексей < alexeynikolaev.post@yandex.ru> wrote:
Hi, community!
What are best practices to run docker images into oVirt infra: core os or something else? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/UB4H3Y7VYQ6R2A...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/3YXYZF474MNLNJ...

On Thu, 19 Jul 2018 at 02:37 Vincent Royer <vincent@epicenergy.ca> wrote:
We're using rancher on Ovirt and it's great. No problems to report.
On Wed, Jul 18, 2018, 1:08 PM Wesley Stewart, <wstewart3@gmail.com> wrote:
I'm currently using CoreOS as a VM and I like it. RancherOS performs similarly, but appears to have a smaller footprint.
I doubt you will see a big different in performance. I'm sure ovirt can handle them both fine.
You can also spin up a RH or CentOS vm and install docker just fine. But the smaller footprints are nice.
CoreOS was recently aquired by redhat if I'm not mistaken, so I went with CoreOS personally.
On Mon, Jul 16, 2018, 11:45 AM Николаев Алексей < alexeynikolaev.post@yandex.ru> wrote:
Hi, community!
What are best practices to run docker images into oVirt infra: core os or something else? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/UB4H3Y7VYQ6R2A...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/3YXYZF474MNLNJ...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/PJCTK6O6UL7XRX...
We are working on expanding the integration of oVirt with Openshift origin - see ovirt-openshift-extensions[1] project for the details. A core feature of this integration is to get your container's persistent volumes from ovirt storage, which takes advantage of any storage setup you set for ovirt - ISCSI/FS/NFS/FS/Gluster etc. This blog bost[2] in ovirt site covers that as well. [1] https://github.com/oVirt/ovirt-openshift-extensions [2] https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/

On 19 July 2018 at 17:41, Николаев Алексей <alexeynikolaev.post@yandex.ru> wrote:
Thx for all.
18.07.2018, 10:37, "Petr Kotas" <pkotas@redhat.com>:
Hi Alex,
would you mind being more specific with your question?
What are you trying to achieve?
According to documentation https://ovirt.org/feature/container-support/ there are two different approaches to working with Docker: 1. run the container on hosts virtualization, along with the VM; 2. run containers inside VMS managed by oVirt.
I would like to hear the pros and cons of each method. Which one is preferable to use in the oVirt infrastructure.
Please don't take the following statement as being an official statement of any sort as I'm not personally involved with any of the ongoing development of the features mentioned above, but from my POV being involved in the oVirt CI/release process it seems that: As far as #1 goes, it seems to have never made it past an initial POC + a blog post. Option #2 seems to have much more work being put into it including guest agent features, Ansible modules and playbooks, OpenShift/Kubernetes drivers and an end-to-end testing suit in CI
We are working on expanding the integration of oVirt with Openshift origin.
Pre-requisite:
- Openshift 3.9.0 - Running service catalog
Does it require installation of Openshift Origin?
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/L3ZI27M74UC6GCK2WDCGC5AUGONVGRO2/
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

On 07/22/2018 11:01 AM, Barak Korren wrote:
On 19 July 2018 at 17:41, Николаев Алексей <alexeynikolaev.post@yandex.ru <mailto:alexeynikolaev.post@yandex.ru>> wrote:
Thx for all. 18.07.2018, 10:37, "Petr Kotas" <pkotas@redhat.com <mailto:pkotas@redhat.com>>:
Hi Alex,
would you mind being more specific with your question?
What are you trying to achieve?
According to documentation https://ovirt.org/feature/container-support/ <https://ovirt.org/feature/container-support/> there are two different approaches to working with Docker: 1. run the container on hosts virtualization, along with the VM; 2. run containers inside VMS managed by oVirt. I would like to hear the pros and cons of each method. Which one is preferable to use in the oVirt infrastructure.
Please don't take the following statement as being an official statement of any sort as I'm not personally involved with any of the ongoing development of the features mentioned above, but from my POV being involved in the oVirt CI/release process it seems that:
As far as #1 goes, it seems to have never made it past an initial POC + a blog post.
Yep. We made a PoC but it never gained traction. The code is still there, but it is pretty much unsupported and it is going to be removed in future releases. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

On Thu, 19 Jul 2018 at 17:41 Николаев Алексей <alexeynikolaev.post@yandex.ru> wrote:
Thx for all.
18.07.2018, 10:37, "Petr Kotas" <pkotas@redhat.com>:
Hi Alex,
would you mind being more specific with your question?
What are you trying to achieve?
According to documentation https://ovirt.org/feature/container-support/ there are two different approaches to working with Docker: 1. run the container on hosts virtualization, along with the VM; 2. run containers inside VMS managed by oVirt.
I would like to hear the pros and cons of each method. Which one is preferable to use in the oVirt infrastructure.
Again you didn't specify your needs so those answers maybe too general. Anyhow, when you run openshift on ovirt you get all all the advantages you get when running any workload on vms. Example when your VMs are the openshift nodes or masters, your can migrate them, snapshot them, duplicate them etc... Plus the flex storage plugin that will use your underlying storage if that is something your workloads need.
We are working on expanding the integration of oVirt with Openshift origin.
Pre-requisite:
- Openshift 3.9.0 - Running service catalog
Does it require installation of Openshift Origin?
You can use openshift or kubernetes.
participants (7)
-
Barak Korren
-
Francesco Romani
-
Petr Kotas
-
Roy Golan
-
Vincent Royer
-
Wesley Stewart
-
Николаев Алексей