[JIRA] (OVIRT-2917) Vagrant VM container

[Anton Marchukov (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Marchukov reassigned OVIRT-2917:
--

Assignee: Anton Marchukov  (was: infra)

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: Anton Marchukov
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LEIXFYBLNRXEQYUNDOZBIDZGJIFWV5PO/

[JIRA] (OVIRT-2917) Vagrant VM container

[Ales Musil (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40410#comment-40410
 ] 

Ales Musil commented on OVIRT-2917:
---

{quote}We already have a set of working containers that spawn VMs using 
lago/OST - can we leverage that to use for VDSM testing?{quote}

If it helps I am in. Is there any documentation how to do that? 

{quote}From the infra point of view we want to limit the potential effect on 
the host and network tests may try to reconfigure NICs etc. Can’t we use 
existing VMs running mocks for these kinds of tests? What’s the 
[quay.io/ovirt/vdsm-test-func-network-centos-8|http://quay.io/ovirt/vdsm-test-func-network-centos-8]
 container and where is it currently used?{quote}

Mock is slowing down the tests which makes it unstable and we cant relay on 
results. That’s why we want to switch in first place. The container is used to 
run network functional tests on check patch is something has changed in 
networking code. Everything I have shared about services and modules is from 
this container. 



> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TKRRU4OBXYTF7NQJWITKATCFFJ56NKBJ/

[JIRA] (OVIRT-2917) Vagrant VM container

[Evgheni Dereveanchin (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40409#comment-40409
 ] 

Evgheni Dereveanchin commented on OVIRT-2917:
-

We already have a set of working containers that spawn VMs using lago/OST - can 
we leverage that to use for VDSM testing?

From the infra point of view we want to limit the potential effect on the host 
and network tests may try to reconfigure NICs etc. Can’t we use existing VMs 
running mocks for these kinds of tests? What’s the 
[quay.io/ovirt/vdsm-test-func-network-centos-8|http://quay.io/ovirt/vdsm-test-func-network-centos-8]
 container and where is it currently used?

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZJMEABN52ZUIO2OAVAJXQOBAY6YAUVUK/

[JIRA] (OVIRT-2917) Vagrant VM container

[Ales Musil (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40406#comment-40406
 ] 

Ales Musil commented on OVIRT-2917:
---

No, vagrant is not going to be used. The original question was if we can use  
CI container that runs vagrant VM. Because this option is not good idea as we 
were told, we would like to have privileged container running directly on CI. 



As requested here is list of services that we run in container:

UNIT LOAD   ACTIVE SUB DESCRIPTION
dbus.service loaded active running D-Bus System Message Bus
NetworkManager.service   loaded active running Network Manager
selinux-autorelabel-mark.service loaded active exited  Mark the need to relabel 
after reboot
systemd-journald.service loaded active running Journal Service
systemd-resolved.service loaded active running Network Name Resolution
systemd-tmpfiles-setup.service   loaded active exited  Create Volatile Files 
and Directories
systemd-udevd.serviceloaded active running udev Kernel Device 
Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.

7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.



> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SJCIL7AM4OF44HYZVU5B66YUXXELPBAF/

[JIRA] (OVIRT-2917) Vagrant VM container

[Evgheni Dereveanchin (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40405#comment-40405
 ] 

Evgheni Dereveanchin commented on OVIRT-2917:
-

I’m not sure why the container would need these features if Vagrant is also 
going to be used: I would expect all tests to run inside the Vagrant VM, not on 
the container. The privileged part is only needed to start the VM. Please 
correct me if I’m wrong.

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GIDFKPBJLFUDRQNIJ5ALUH3R3D652BT4/

[JIRA] (OVIRT-2917) Vagrant VM container

[Anton Marchukov (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40404#comment-40404
 ] 

Anton Marchukov commented on OVIRT-2917:


[~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] any updates here? 
Seems like we do not have any evident side effect but as usual we can have it 
unexpectedly by some system component such as firewalld or so? 

I think if we can filter out all known causes of modules being unloaded and 
make sure they do not have it we can go ahead and try. This is because we do 
not have any alternative solution yet unfortunately.

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WFCB7QW5C6IBCTYGHYMIW4MBAS5EDG2B/

[JIRA] (OVIRT-2917) Vagrant VM container

[Ales Musil (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40380#comment-40380
 ] 

Ales Musil commented on OVIRT-2917:
---

Forgot to mention that we are also loading three kernel modules:

8021q, bonding and openvswitch



We do not unload any module. 

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BGSMK66JG6ZCIZKZQXIFLEOHP5V47BSF/

[JIRA] (OVIRT-2917) Vagrant VM container

[Ales Musil (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40375#comment-40375
 ] 

Ales Musil commented on OVIRT-2917:
---

The container needs systemd up and running for NetworkManager and Dbus. Other 
than that it does basically all network operations via sysctl or ip link or 
through the NM service. Not sure what side effect it might have but I am 
running it locally several times almost every day and I didn’t find anything 
that it would mess with on my system. 

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/X66T3QAIFUFETT2F35JGAMQ4SOKFUHSN/

[JIRA] (OVIRT-2917) Vagrant VM container

[Anton Marchukov (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40369#comment-40369
 ] 

Anton Marchukov commented on OVIRT-2917:


[~accountid:557058:45c1e87b-8519-415a-bd15-264ead82844a] can you please briefly 
describe what those tests are doing in terms of privileged operations? I 
understand that we have to somehow manage the current solution till the better 
one is created. But since we already had multiple cases of privileged 
containers producing side effects it is good to review what they are doing in 
each case. Adding [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] here 
who usually see the side effects in live and can help to asses. 

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W5OALICVN4YWTVHWDHQVPEBMCHY5JVSS/

[JIRA] (OVIRT-2917) Vagrant VM container

[Dominik Holler (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40364#comment-40364
 ] 

Dominik Holler commented on OVIRT-2917:
---

[~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143]
Would you add the quay.io/ovirt/vdsm-test-func-network-centos-8 to the withe 
list  until we have another way to run a privileged container?


> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/G3YIAPYI4M5ZOYFE3ISKRUBDW7TKXIC5/

[JIRA] (OVIRT-2917) Vagrant VM container

[Barak Korren (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40355#comment-40355
 ] 

Barak Korren commented on OVIRT-2917:
-

no. no docs atm.

Also despite what I wrote before, workloads using such a container may not 
continue to be supported in the near future.

Due to the age of the existing oVirt CI hardware, and the new requirements 
introduced by RHEL8, The oVirt CI infrastructure is going to undergo some 
massive transformations in the near future. We're basically going to rebuild a 
lot of it from scratch.

In the meantime I'd advise against making any significant changes to existing 
CI workloads or adding any major new ones.

Sorry for the inconvenience.

cc: [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] 

> Vagrant VM container
> 
>
> Key: OVIRT-2917
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ales Musil
>Assignee: infra
>
> Hi,
> is there any documentation on how to use the new container backend with the
> CI container that spawns VM for privileged operations?
> Thank you.
> Regards,
> Ales
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.comIM: amusil
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LUOTSINXSA5VTMWVK6PG7LYHL4FYIUOL/

[JIRA] (OVIRT-2917) Vagrant VM container

[Ales Musil (oVirt JIRA)]

Ales Musil created OVIRT-2917:
-

 Summary: Vagrant VM container
 Key: OVIRT-2917
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Ales Musil
Assignee: infra


Hi,
is there any documentation on how to use the new container backend with the
CI container that spawns VM for privileged operations?

Thank you.
Regards,
Ales

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OLS45L4FPFXLQSH5T64YFUPZAEBOETFA/