[ovirt-devel] Re: How to add imageio configuration into engine?
On Mon, Apr 6, 2020 at 7:43 PM Nir Soffer wrote: > On Mon, Apr 6, 2020 at 7:49 PM Vojtech Juranek > wrote: > > > > Hi, > > I'd like to add imageio configuration into engine. Previously, it was > done by > > dedicated setup code in imageio-proxy [1], but in new imageio we remove > the > > proxy package and to configure imageio for engine we need just to place > > firewalld and imageio config files into proper place. > We should probably also add imageio dependency to the engine spec file, because I understand that imageio proxy running on engine is always required, right? > > > > Initial idea was to do it directly in engine spec file, but it seems to > me > > that configuration of the engine is done by dedicated packages and custom > > code. Ansible roles in packaging/ansible-runner-service-project seem to > be > > only for host configuration. > > > > What is a proper way how to configure imageio? > All engine and related services configuration is performed via engine-setup, which is based on otopi. > > More correctly, how to configure engine for using imageio daemon. > Please write a plugin to engine-setup which will handle imageio proxy configuration > > In the past we supported these options: > > - configuration without imageio proxy. This does not make sense since > without the proxy you cannot > upload images from the UI. We don't want to support such > configuration. The imageio proxy must always > be available, and there is nothing which is user configurable (in the > context of engine setup). > > - proxy address. This configuration is not needed since the only > supported configuration is proxy > installed on the engine host, and engine already knows it's address. > > - certificates - in the past we created certificates and key for the > proxy. This has been a constant source > of trouble. Recently Didi switched to using apache pki files. There > is no need to support other > configurations. If users want to change the certificates, they can > edit the imageio daemon > configuration file. > Well, you need to support not only engine CA and engine certificate, but also custom engine HTTPS certificate signed by custom CA in the same way as engine: https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL.html So even if proxy is going to use the same custom certificate and CA as engine, we at least need to update documentation with the need to restart imageio service on the host. And more thing: are all clients connecting only to imageio proxy on engine or is there any connection directly to imageio running on the host? > imageio provides a sample configuration file, and leaves the actual > configuration to the user of the > package. We have 2 users - vdsm and engine. > > Vdsm handles imageio configuration by installing the static > configuration files in the spec. I don't > see why engine cannot use the same simple solution. However if engine > needs special configuration > code (e.g. engine setup plugin), it must be part of engine repo and > maintained by engine maintainers. > > The configuration for using imageio in engine: > - tls - paths to apache certificates > - remote port - always 54323 > - control port - accessible only locally, TBD > > The remote port must be open in the engine host firewall, and requires > another static file for firewalld rule. > Every engine configuration is handled within engine-setup, so please write a plugin for engine-setup to configure imageio proxy on engine > > Vojta, can you share a working configuration file and firewalld rule, > or post a patch adding them to > engine? > > Nir > ___ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/message/NLV2DRTUAFY2WWX3NVGQT6X7VMQXR2YA/ > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/V6VYRMNVLFZIZTOI2KUJ5Q34Y3DTXA4N/
[ovirt-devel] Re: How to add imageio configuration into engine?
On Mon, Apr 6, 2020 at 7:49 PM Vojtech Juranek wrote: > > Hi, > I'd like to add imageio configuration into engine. Previously, it was done by > dedicated setup code in imageio-proxy [1], but in new imageio we remove the > proxy package and to configure imageio for engine we need just to place > firewalld and imageio config files into proper place. > > Initial idea was to do it directly in engine spec file, but it seems to me > that configuration of the engine is done by dedicated packages and custom > code. Ansible roles in packaging/ansible-runner-service-project seem to be > only for host configuration. > > What is a proper way how to configure imageio? More correctly, how to configure engine for using imageio daemon. In the past we supported these options: - configuration without imageio proxy. This does not make sense since without the proxy you cannot upload images from the UI. We don't want to support such configuration. The imageio proxy must always be available, and there is nothing which is user configurable (in the context of engine setup). - proxy address. This configuration is not needed since the only supported configuration is proxy installed on the engine host, and engine already knows it's address. - certificates - in the past we created certificates and key for the proxy. This has been a constant source of trouble. Recently Didi switched to using apache pki files. There is no need to support other configurations. If users want to change the certificates, they can edit the imageio daemon configuration file. imageio provides a sample configuration file, and leaves the actual configuration to the user of the package. We have 2 users - vdsm and engine. Vdsm handles imageio configuration by installing the static configuration files in the spec. I don't see why engine cannot use the same simple solution. However if engine needs special configuration code (e.g. engine setup plugin), it must be part of engine repo and maintained by engine maintainers. The configuration for using imageio in engine: - tls - paths to apache certificates - remote port - always 54323 - control port - accessible only locally, TBD The remote port must be open in the engine host firewall, and requires another static file for firewalld rule. Vojta, can you share a working configuration file and firewalld rule, or post a patch adding them to engine? Nir ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/NLV2DRTUAFY2WWX3NVGQT6X7VMQXR2YA/
[ovirt-devel] How to add imageio configuration into engine?
Hi, I'd like to add imageio configuration into engine. Previously, it was done by dedicated setup code in imageio-proxy [1], but in new imageio we remove the proxy package and to configure imageio for engine we need just to place firewalld and imageio config files into proper place. Initial idea was to do it directly in engine spec file, but it seems to me that configuration of the engine is done by dedicated packages and custom code. Ansible roles in packaging/ansible-runner-service-project seem to be only for host configuration. What is a proper way how to configure imageio? Thanks Vojta [1] https://github.com/oVirt/ovirt-imageio/tree/master/proxy/setup signature.asc Description: This is a digitally signed message part. ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/B37AHP52UKPHLXHKO6X6QHEOWRQTV5AB/
[ovirt-devel] OST:: hc-basic-suite-master failing
Hello! The hc-basic-suite-master fails at + lago shell lago-hc-basic-suite-master-host-0 /root/exec_playbook.sh lago-hc-basic-suite-master-host-0 lago-hc-basic-suite-master-host-1 lago-hc-basic-suite-master-host-2 + RET_CODE=2 + '[' 2 -ne 0 ']' + echo 'ansible setup on lago-hc-basic-suite-master-host-0 failed with status 2.' Is this issue because of an ansible issue or a lago error? ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/EAJHJCG2277CT4YK3TJCIC3DFFH2O3H3/
[ovirt-devel] hover_to_id couldnt find element compute
Hi all, Almost two years ago I started a thread on this list with the same subject. Eventually I pushed a small patch to make it try longer (24 seconds instead of 2.4). Later this happened again, but I didn't post publicly - only corresponded with Greg Sheremeta who helped me originally (and is now in OpenShift), not doing anything else eventually. At the time, he said this might not have been simple normal slowness, but some other problem. Now it happened again: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6747/ Last screenshot, taken before the failure, just shows "Loading ...", just as then. Any UI expert wants to spend some time looking at this? Perhaps adding what's needed to have more debug information etc.? For now I'll just retry, anyway. Thanks and best regards, -- Didi ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/BQODQEGZREWRSUVEWV2J7DQ4OSK7KKYP/
[ovirt-devel] Re: Change in ovirt-provider-ovn[master]: test, do not merge: Drop el7
On Sun, Apr 5, 2020 at 12:40 PM Yedidyah Bar David wrote: > On Sun, Apr 5, 2020 at 1:35 PM Code Review wrote: > > > > From gerrit-hooks : > > > > gerrit-hooks has posted comments on this change. > > > > Change subject: test, do not merge: Drop el7 > > Seems to me like CQ is failing due to failed check-merged: > > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/22088/ > > > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/22088/consoleFull > > 04:53:13 ovirt-provider-ovn_standard-on-merge (423) failed building > > And indeed last patch to ovirt-provider-ovn: > > https://gerrit.ovirt.org/#/c/107970/ > > Failed: > > https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-on-merge/423/ > > > https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-on-merge/423/artifact/check-merged.el7.x86_64/mock_logs/script/stdout_stderr.log > > ERROR: Could not find a version that satisfies the requirement > futurist>=2.1.0 (from openstacksdk) (from versions: 0.1.0, 0.1.1, > 0.1.2, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.0, > 0.11.0, 0.12.0, 0.13.0, 0.14.0, 0.15.0, 0.16.0, 0.17.0, 0.18.0, > 0.19.0, 0.20.0, 0.21.0, 0.21.1, 0.22.0, 0.23.0, 1.0.0, 1.1.0, 1.2.0, > 1.3.0, 1.3.1, 1.3.2, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.8.1, 1.9.0, > 1.10.0) > ERROR: No matching distribution found for futurist>=2.1.0 (from > openstacksdk) > > So perhaps branch ovirt-provider-ovn for 4.3 (and fix what's needed > there, if anything) > and drop el7 support from master. > > Thanks for the heads up. Hopefully https://gerrit.ovirt.org/#/c/107996/ will be good enough. > Best regards, > > .. > > > > > > Patch Set 1: > > > > * Update Tracker::IGNORE, no bug url/s found > > > > -- > > To view, visit https://gerrit.ovirt.org/108219 > > To unsubscribe, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-provider-ovn > > Gerrit-Branch: master > > Gerrit-MessageType: comment > > Gerrit-Change-Id: Iff6b57f8e3965d559566f9bb026a3439fc0b857d > > Gerrit-Change-Number: 108219 > > Gerrit-PatchSet: 1 > > Gerrit-Owner: Yedidyah Bar David > > Gerrit-Reviewer: gerrit-hooks > > Gerrit-Comment-Date: Sun, 05 Apr 2020 10:35:05 + > > Gerrit-HasComments: No > > > > > -- > Didi > > ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/YLDGCR3D27H44DLWUOUZ5K3QDL3XMW5L/
