[ovirt-users] Gluster: Ideas for migration
Hello I have to migrate the Gluster volumes from an old oVirt cluster to a newly built one. I looked into migration strategies, but everything that Red Hat recommends is related to replacing old bricks. In a testing environment I created two clusters and wanted to migrate one volume after the other. Unfortunately that fails because a node cannot be part of two clusters at the same time. The next thing I see, is to recreate the volumes on the new cluster, then constantly rsync the files from the old cluster to the new one and at a specified point in time make the cut over where I stop the applicaiton, do a final rsync and remount the new volume under the old path. Is there any other, nicer way I could accomplish migrating a volume from one Gluster cluster to another? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-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/users@ovirt.org/message/N7USOAG2AZB3DBXPU6PWF4FJBTUAQFHE/
[ovirt-users] Re: oVirt 4.5.4-1: engine-setup does not renew certificates
On Thu, Sep 14, 2023 at 10:26 AM Lars Stolpe wrote: > > Hi, > I wanted to add short names to the webgui apache certificate. I followed > these instructions: > „Engine can be accessed using alternate host names (or IP addresses) that can > configured by adding a new configuration file (for example > /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf) with following > content: SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com" > The list of alternate names has to be listed separated by spaces. It's > possible to add also IP addresses of engine host, but using IP addresses > instead of DNS names is not considered to be a good practise. Run > engine-setup to generate new certificates.“ Where did you copy this from? > > Certificates where not renewed. How do i get engine-setup to renew the apache > certificate? engine-setup can renew certificates that were generated by itself, not any random cert. If you add new names to the engine using SSO_ALTERNATE_ENGINE_FQDNS, you usually use certs generated elsewhere, not ones from engine-setup. Best regards, -- Didi ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-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/users@ovirt.org/message/NBUUWKIEQAOFXSUQDD4PQWOMOSBGHJAI/
[ovirt-users] oVirt 4.5.4-1: engine-setup does not renew certificates
Hi, I wanted to add short names to the webgui apache certificate. I followed these instructions: „Engine can be accessed using alternate host names (or IP addresses) that can configured by adding a new configuration file (for example /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf) with following content: SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com" The list of alternate names has to be listed separated by spaces. It's possible to add also IP addresses of engine host, but using IP addresses instead of DNS names is not considered to be a good practise. Run engine-setup to generate new certificates.“ Certificates where not renewed. How do i get engine-setup to renew the apache certificate? oVirt: 4.5.4-1 Regards, Lars ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-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/users@ovirt.org/message/5BW24KEOMEMGWTJJN4QGNJQVXYLNL3RX/