[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi Strahil, Ok done; https://bugzilla.redhat.com/show_bug.cgi?id=1868393 only it didn't allow me to select the most recent 4.3. Thanks Olaf Op wo 12 aug. 2020 om 15:58 schreef Strahil Nikolov : > Hi Olaf, > > yes but mark it as '[RFE]' in the name of the bug. > > Best Regards, > Strahil Nikolov > > На 12 август 2020 г. 12:41:55 GMT+03:00, olaf.buitel...@gmail.com написа: > >Hi Strahil, > > > >It's not really clear how i can pull requests to the oVirt repo. > >I've found this bugzilla issue for going from v5 to v6; > >https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this > >corresponding commit; https://gerrit.ovirt.org/#/c/100701/ > >Would the correct route be to issue a bugzilla request for this? > > > >Thanks Olaf > >___ > >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/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/ > ___ 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/AECOZINFZHHFJHJLLWGJ6GYOFIMTVVZO/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi Olaf, yes but mark it as '[RFE]' in the name of the bug. Best Regards, Strahil Nikolov На 12 август 2020 г. 12:41:55 GMT+03:00, olaf.buitel...@gmail.com написа: >Hi Strahil, > >It's not really clear how i can pull requests to the oVirt repo. >I've found this bugzilla issue for going from v5 to v6; >https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this >corresponding commit; https://gerrit.ovirt.org/#/c/100701/ >Would the correct route be to issue a bugzilla request for this? > >Thanks Olaf >___ >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/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/ ___ 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/WQ6IF7WCE6G5YP4UX5L2AF3LSKINWOAJ/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi Strahil, It's not really clear how i can pull requests to the oVirt repo. I've found this bugzilla issue for going from v5 to v6; https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this corresponding commit; https://gerrit.ovirt.org/#/c/100701/ Would the correct route be to issue a bugzilla request for this? Thanks Olaf ___ 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/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hey Olaf, you can add the CentOS Storage SIG repo and patch. Best Regards, Strahil Nikolov На 11 август 2020 г. 21:27:23 GMT+03:00, Olaf Buitelaar написа: >Hi Strahil, > >Thanks for confirming v7 is working fine with oVirt 4.3, it being from >you, >gives quite some faith. >If that's generally the case it would be nice if the yum repo >ovirt-4.3-dependencies.repo >could be updated to the gluster - v7 in the official repository e.g.; >[ovirt-4.3-centos-gluster7] >name=CentOS-$releasever - Gluster 7 >baseurl=http://mirror.centos.org/centos/7/storage/$basearch/gluster-7/ >gpgcheck=1 >enabled=1 >gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Storage > >keeping the gluster support up-to-date, gives at least some users the >time >to plan the upgrade path to oVirt 4.4, while remaining to not to run on >EOL >gluster's. > >Thanks Olaf > > >Op di 11 aug. 2020 om 19:35 schreef Strahil Nikolov >: > >> I have been using v7 for quite some time. >> >> >> Best Regards, >> Strahil Nikolov >> >> На 11 август 2020 г. 15:26:51 GMT+03:00, olaf.buitel...@gmail.com >написа: >> >Dear oVirt users, >> > >> >any news on the gluster support side on oVirt 4.3. With 6.10 being >> >possibly the latest release, it would be nice if there is an known >> >stable upgrade path to either gluster 7 and possibly 8 for the oVirt >> >4.3 branch. >> > >> >Thanks Olaf >> >___ >> >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/CPHD2NBWBSAL2UQ7JNR5A266OWZ4XU2T/ >> ___ 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/TXGENNZOBUTLG4HD4CKHMLYPG4BMOHFX/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi Strahil, Thanks for confirming v7 is working fine with oVirt 4.3, it being from you, gives quite some faith. If that's generally the case it would be nice if the yum repo ovirt-4.3-dependencies.repo could be updated to the gluster - v7 in the official repository e.g.; [ovirt-4.3-centos-gluster7] name=CentOS-$releasever - Gluster 7 baseurl=http://mirror.centos.org/centos/7/storage/$basearch/gluster-7/ gpgcheck=1 enabled=1 gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Storage keeping the gluster support up-to-date, gives at least some users the time to plan the upgrade path to oVirt 4.4, while remaining to not to run on EOL gluster's. Thanks Olaf Op di 11 aug. 2020 om 19:35 schreef Strahil Nikolov : > I have been using v7 for quite some time. > > > Best Regards, > Strahil Nikolov > > На 11 август 2020 г. 15:26:51 GMT+03:00, olaf.buitel...@gmail.com написа: > >Dear oVirt users, > > > >any news on the gluster support side on oVirt 4.3. With 6.10 being > >possibly the latest release, it would be nice if there is an known > >stable upgrade path to either gluster 7 and possibly 8 for the oVirt > >4.3 branch. > > > >Thanks Olaf > >___ > >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/CPHD2NBWBSAL2UQ7JNR5A266OWZ4XU2T/ > ___ 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/S7Y5CN5N7GTZFNUWEUP5XHTBDOQCFJER/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
I have been using v7 for quite some time. Best Regards, Strahil Nikolov На 11 август 2020 г. 15:26:51 GMT+03:00, olaf.buitel...@gmail.com написа: >Dear oVirt users, > >any news on the gluster support side on oVirt 4.3. With 6.10 being >possibly the latest release, it would be nice if there is an known >stable upgrade path to either gluster 7 and possibly 8 for the oVirt >4.3 branch. > >Thanks Olaf >___ >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/CPHD2NBWBSAL2UQ7JNR5A266OWZ4XU2T/ ___ 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/ZIPHSLIDILEY3FJGLD25ZE37VNGVN4Z3/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Dear oVirt users, any news on the gluster support side on oVirt 4.3. With 6.10 being possibly the latest release, it would be nice if there is an known stable upgrade path to either gluster 7 and possibly 8 for the oVirt 4.3 branch. Thanks Olaf ___ 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/CPHD2NBWBSAL2UQ7JNR5A266OWZ4XU2T/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Dear oVirt users, I was wondering with the release of 4.4, but having a quite difficult upgrade path; reinstalling the engine, and moving all machines to rhel/centos 8. Are there any plans to update the gluster dependencies to version 7 in the the ovirt-4.3-dependencies.repo? Or will oVirt 4.3 always be stuck at gluster version 6? Thanks Olaf ___ 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/PBCMNR7RDGGANVAJM3KF7V6Y3G4NV27L/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
May be we need to check for VDO version. Will check and update. @Prajith Kesava Prasad Can please take a look? On Wed, Jun 17, 2020 at 7:43 PM Yedidyah Bar David wrote: > On Wed, Jun 17, 2020 at 4:57 PM wrote: > > > > Ciao Sandro, > > > > just tried to re-install a Centos7 based HCI cluster because it had > moved to another network. > > > > And from what I can tell it fails because Gobinda Das introduced a > hot-fix into > 'gluster-ansible-infra/roles/backend_setup/tasks/vdo_create.yml' that adds > a '--maxDiscardSize 16M' option statically on April 13th. > > > > Only problem, the vdo 6.1 that is part of the CentOS7/oVirt 4.3.10 stack > doesn't know that option at all, it seems to have been introduced for VDO > 6.2 which is COS 8 based. > > > > Questions: > > Should this not be caught by automated testing? > > Where and how do I need to fill a bug report in such a way that it gets > to Gobinda or his team? > > Adding Gobinda. > -- > Didi > > -- Thanks, Gobinda ___ 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/KBVAZCJUKMLUFGWRT7W46SJ4TWXIUOKY/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Wed, Jun 17, 2020 at 4:57 PM wrote: > > Ciao Sandro, > > just tried to re-install a Centos7 based HCI cluster because it had moved to > another network. > > And from what I can tell it fails because Gobinda Das introduced a hot-fix > into 'gluster-ansible-infra/roles/backend_setup/tasks/vdo_create.yml' that > adds a '--maxDiscardSize 16M' option statically on April 13th. > > Only problem, the vdo 6.1 that is part of the CentOS7/oVirt 4.3.10 stack > doesn't know that option at all, it seems to have been introduced for VDO 6.2 > which is COS 8 based. > > Questions: > Should this not be caught by automated testing? > Where and how do I need to fill a bug report in such a way that it gets to > Gobinda or his team? Adding Gobinda. -- 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/USWR6KZSA2QGMIQ7TM2NCHMZTENSRRFJ/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Ciao Sandro, just tried to re-install a Centos7 based HCI cluster because it had moved to another network. And from what I can tell it fails because Gobinda Das introduced a hot-fix into 'gluster-ansible-infra/roles/backend_setup/tasks/vdo_create.yml' that adds a '--maxDiscardSize 16M' option statically on April 13th. Only problem, the vdo 6.1 that is part of the CentOS7/oVirt 4.3.10 stack doesn't know that option at all, it seems to have been introduced for VDO 6.2 which is COS 8 based. Questions: Should this not be caught by automated testing? Where and how do I need to fill a bug report in such a way that it gets to Gobinda or his team? ___ 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/BKLZ27FLJXSLQF5VD45LZOLV44KMABVD/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On May 22, 2020 7:23:45 PM GMT+03:00, Gianluca Cecchi wrote: >On Fri, May 22, 2020 at 6:18 PM Strahil Nikolov >wrote: > >> >> 5. The storage domains for the VM are up >> > >As I wrote, it happens sometime that the storage domains are marked as >up, >but actually they are not (the related /rhev/data-center/mnt/... >filesystem >not mounted) > >It happened to me several times, only when restarting from a crash (not >always though) and only in single host configurations. >Both in NFS config (not supported actually) and in Gluster config >(supposed >to be supported). > >Gianluca Usually, There should be some indicator why this has happened. Can you check the engine's log when this happens ? Best Regards, Strahil Nikolov ___ 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/A2J5ANIIFMWK3HO6LJDT7CVUJBTERUWV/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Fri, May 22, 2020 at 6:18 PM Strahil Nikolov wrote: > > 5. The storage domains for the VM are up > As I wrote, it happens sometime that the storage domains are marked as up, but actually they are not (the related /rhev/data-center/mnt/... filesystem not mounted) It happened to me several times, only when restarting from a crash (not always though) and only in single host configurations. Both in NFS config (not supported actually) and in Gluster config (supposed to be supported). Gianluca ___ 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/OM5HJWOVGELMZTR3NRY6QO4T7RKQAVEH/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On May 22, 2020 6:48:43 PM GMT+03:00, Gianluca Cecchi wrote: >On Fri, May 22, 2020 at 4:17 PM Derek Atkins wrote: > >> >> >> FTR: I don't think I need to check that the datacenter status is up; >I >> added that in not really understanding the changes between 4.1 and >4.3. >> The issue is that the storage domain status isn't initialized to >'down' >> when the engine first comes up so my script was testing that and >seeing >> all domains up when they really weren't. >> >> >Actually at least one time last week I had a situation where after a >crash >of a single host environment with 4.3.9 and gluster on host itself, all >3 >gluster storage domains resulted active but actually only the engine >rhev >mount point was up and not the other 3 configured >Something like this: >/rhev/data-center/mnt/glusterSD/ovirtst.mydomai.storage:_engine > >While for the other 3 storage domains I only had the gluster brick >active >but not the filesystem mounted. >In web admin gui all the storage domains was marked as active and >as >soon as I powered on the first VM the operation went into error of >course >and only at that time the 3 storage domains were marked as down... >From the web admin gui I was able to then activate them and start VMs. >I had no time to investigate more and so opening a bug for that... >The problem is that in my opinion the datacenter was marked as up too, >so >your check would not be of great meaning. >In my opinion you could crosscheck also storage domains number with >expected mount points of type /rhev/data-center/mnt/... > >Gianluca In order to have a full operational environment you will need (they depend on each other): 1. Engine is up and healthy 2. Master storage domain is up 3. Datacenter is up 4. A host is selected for SPM 5. The storage domains for the VM are up 6. At least one Host in the cluster is up and running (usually that's the node in step 4) Best Regards, Strahil Nikolov ___ 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/OHEHUWMMY7ZHLA3BV4Q3JZ2IW2HRDGWT/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Fri, May 22, 2020 at 4:17 PM Derek Atkins wrote: > > > FTR: I don't think I need to check that the datacenter status is up; I > added that in not really understanding the changes between 4.1 and 4.3. > The issue is that the storage domain status isn't initialized to 'down' > when the engine first comes up so my script was testing that and seeing > all domains up when they really weren't. > > Actually at least one time last week I had a situation where after a crash of a single host environment with 4.3.9 and gluster on host itself, all 3 gluster storage domains resulted active but actually only the engine rhev mount point was up and not the other 3 configured Something like this: /rhev/data-center/mnt/glusterSD/ovirtst.mydomai.storage:_engine While for the other 3 storage domains I only had the gluster brick active but not the filesystem mounted. In web admin gui all the storage domains was marked as active and as soon as I powered on the first VM the operation went into error of course and only at that time the 3 storage domains were marked as down... >From the web admin gui I was able to then activate them and start VMs. I had no time to investigate more and so opening a bug for that... The problem is that in my opinion the datacenter was marked as up too, so your check would not be of great meaning. In my opinion you could crosscheck also storage domains number with expected mount points of type /rhev/data-center/mnt/... Gianluca ___ 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/25KYZTFKX5Y4UOEL2SNHUUC7M4WAJ5NO/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi, Strahil Nikolov writes: > Actually, > You can use Ansible and 'uri' module to communicate wwith the engine > via the API. Most probably the 'uri' module was written in python - > but you don't have to deal with python code - just ansible. > Also, it's worth checking the ansible Ovirt modules , as they are kept > up to date evwn when the API endpoint changes. > > I think it won't be too hard to get a list of the VMs and then create > some logic how to order them for the 'ignition'. I took a much closer look at the examples yesterday and there are 2 of the 3 things I need already there: 1) test_connection.py -- make sure the engine is up 2) [ get list of total and attached storage domains ] 3) start_vm.pl -- start a VM (by name, it looks like) So really it's only #2 that is missing. There is a show_summary.py in there, but that doesn't give me *all* the code I need to piece together (but I suspect it's close to what I need as I was calling the 'summary' ovirt-shell api to get the info I needed before). I suspect I just need to pull apart the api.summary.storage_domains class to figure out what I need. Clearly there is a 'total', so I just need to figure out 'up', and it looks like I might be able to rewrite my script. Python... EWW. FTR: I don't think I need to check that the datacenter status is up; I added that in not really understanding the changes between 4.1 and 4.3. The issue is that the storage domain status isn't initialized to 'down' when the engine first comes up so my script was testing that and seeing all domains up when they really weren't. > Best Regards, > Strahil Nikolov -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/CHFRKNZLNHNJOGSEHOX5QAIMBYUYD3VZ/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On May 21, 2020 6:08:19 PM GMT+03:00, Derek Atkins wrote: >Nir, > >Nir Soffer writes: > >> Why not open RFE to add the feature you need? > >I did -- about 3-4 years ago. SOME of them have been implemented, some >have been partially implemented, but I am still waiting for ovirt to >support the full VM startup functionality that I had in vmware-server >from like 2007 (or earlier). > >Part of the issue here is that I suspect most ovirt users have multiple >hosts and therefore rarely have to worry about how host-system >maintenance affects the VMs, and probably live in data centers with >redundant power supplies, UPSes, and backup generators. > >I, on the other hand, I've got a single system so when I need to >perform any maintenance I need to take down everything, or if I have a >power outage that outlasts my UPS, or... I want the VMs to come back >up >automatically -- and in a particular order (e.g., I need my DNS and KDC >servers to come up before others). > >I filed these RFEs during the 4.0 days, which is when I first started >using ovirt and put it into deployment. > >> You can use the python SDK to do anything supported by oVirt API. >> Did you look here? >> https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples > >I have looked there, but I stopped reading after seeing "python". ;) >Frankly I detest python. I think it's an abomination. There are so >many other, better languages out there and I don't understand why so >many people like it (and worse, force it down everyone else's throats). >But I'll step off my soap-box (and get off my lawn!) lol. > >Honestly, I already spent the time to build a tool to do what I need. >I >even had to update the tool going from 4.1 to 4.3 because some startup >assumptions changed. I really don't want to spend the time again, time >I frankly don't have right now, to re-implement what I've already got. >It's easier for me to just stay put on 4.3.x. > >Yes, I realize that in about 2 years or so I will need to do so. I'll >worry about that then. > >Of course, since the (partial?) functionality is only in 4.4, I really >have no way to test it to make sure it does what I need, so see what >I'm >missing. I don't have a testbed to play with it, just my one system. > >Thanks, > >-derek Actually, You can use Ansible and 'uri' module to communicate wwith the engine via the API. Most probably the 'uri' module was written in python - but you don't have to deal with python code - just ansible. Also, it's worth checking the ansible Ovirt modules , as they are kept up to date evwn when the API endpoint changes. I think it won't be too hard to get a list of the VMs and then create some logic how to order them for the 'ignition'. Best Regards, Strahil Nikolov ___ 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/DQAGPB64SN33OOGYO3MBG4NS4ZBEUNSU/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Nir, Nir Soffer writes: > Why not open RFE to add the feature you need? I did -- about 3-4 years ago. SOME of them have been implemented, some have been partially implemented, but I am still waiting for ovirt to support the full VM startup functionality that I had in vmware-server from like 2007 (or earlier). Part of the issue here is that I suspect most ovirt users have multiple hosts and therefore rarely have to worry about how host-system maintenance affects the VMs, and probably live in data centers with redundant power supplies, UPSes, and backup generators. I, on the other hand, I've got a single system so when I need to perform any maintenance I need to take down everything, or if I have a power outage that outlasts my UPS, or... I want the VMs to come back up automatically -- and in a particular order (e.g., I need my DNS and KDC servers to come up before others). I filed these RFEs during the 4.0 days, which is when I first started using ovirt and put it into deployment. > You can use the python SDK to do anything supported by oVirt API. > Did you look here? > https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples I have looked there, but I stopped reading after seeing "python". ;) Frankly I detest python. I think it's an abomination. There are so many other, better languages out there and I don't understand why so many people like it (and worse, force it down everyone else's throats). But I'll step off my soap-box (and get off my lawn!) lol. Honestly, I already spent the time to build a tool to do what I need. I even had to update the tool going from 4.1 to 4.3 because some startup assumptions changed. I really don't want to spend the time again, time I frankly don't have right now, to re-implement what I've already got. It's easier for me to just stay put on 4.3.x. Yes, I realize that in about 2 years or so I will need to do so. I'll worry about that then. Of course, since the (partial?) functionality is only in 4.4, I really have no way to test it to make sure it does what I need, so see what I'm missing. I don't have a testbed to play with it, just my one system. Thanks, -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/X7LYSJ6M2YUUKSRT3H4A5RR4MUOTNYOS/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi, On Wed, May 20, 2020 3:06 pm, Gianluca Cecchi wrote: > In the mean time, just to better understand your environment, you say that > you are in a single host environment. > Can you detail where does your engine live? Is it a server outside the > host > or are you in a Self Hosted Engine configuration? Self-hosted engine. > And what are the kind of your storage domains, are they NFS served by the > server itself or by Gluster on the host or external hosts or what? NFS served by the host itself. Both Host and Engine are CentOS-based systems with ovirt installed on top of it. Currently running 4.3.8; I plan to upgrade to 4.3.10 (and 7.8) once it goes GA. The start_vms.sh script is, of course, run on the engine, and runs with a user with appropriate privs to start VMs. Thanks! > Gianluca -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/G6E2M52VW4QZQM46SRCKSW4UXZHH5K7P/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Wed, May 20, 2020 at 7:46 PM Nir Soffer wrote: > On Wed, May 20, 2020 at 7:16 PM Derek Atkins wrote: > > > [snip] > > Granted, I suspect SOME of the reasons I have this script might be > > implemented in 4.4 (e.g. auto-start of VMs). However, my understanding > of > > the auto-start feature is that it's really an auto-restart -- it will > > restart a VM that was running if the datacenter crashes, but if I shut it > > down manually and then "reboot" the cluster, those VMs wont come back > > automatically. As I am on a single-host system, I need it to start from > a > > clean shutdown and bring up all the VMs in addition to dealing with > > power-outage reboots. > > > > I work from the "if it aint broke, don't fix it" camp. So I think I'm > > going to stick with 4.3 until I can't anymore. > > Why not open RFE to add the feature you need? > > You can use the python SDK to do anything supported by oVirt API. > Did you look here? > https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples > > > I am happy to share my startup script if someone else wants to port it to > > work with 4.4. :-) > > > > -derek > > > In the mean time, just to better understand your environment, you say that you are in a single host environment. Can you detail where does your engine live? Is it a server outside the host or are you in a Self Hosted Engine configuration? And what are the kind of your storage domains, are they NFS served by the server itself or by Gluster on the host or external hosts or what? Gianluca ___ 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/UOAITBVADGIGUHFURZZ3BR4MOHRVSAG2/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Wed, May 20, 2020 at 7:16 PM Derek Atkins wrote: > > > On Wed, May 20, 2020 11:19 am, Sandro Bonazzola wrote: > > Il giorno mer 20 mag 2020 alle ore 16:33 ha scritto: > > > >> My enthusiasm for CentOS8 is limited. > >> My enthusiasm for a hard migration even more so. > >> So how much time do I have before 4.3 becomes inoperable? > >> > > > > oVirt 4.3.10 is approaching GA and we expect 4.3.11 to be released too > > before declaring 4.3 at the end of life. > > After that, 4.3 should keep working till CentOS 7 or any other repo on the > > system will break it with some incompatible change. > > I totally understand system administrators' point of view and how > > difficult > > it is to find a good maintenance window for a busy production > > environment, ensuring backups are recent enough, check new requirements > > matching, give it a try on a test environment if it's available and so on. > > That said, I would really encourage starting to plan a maintenance window > > for upgrading to 4.4 as soon as practical. > > It will be easier to help with upgrade from 4.3 at this time than 2 years > > from now when 4.3 can be broken (or new hardware replacement will be > > missing drivers on CentOS 7) and there won't be any additional release for > > fixing upgrade incompatibilities. > > I can't speak to other people, but the lack of "ovirt-shell" for 4.4 is a > deal-breaker for me to upgrade at this time, and probably for the > forseeable future. I've been working on migrating my mail server for 3 > years now and still haven't finished that; migrating ovirt to a new > platform that requires new startup support?? Haha. > > Granted, I suspect SOME of the reasons I have this script might be > implemented in 4.4 (e.g. auto-start of VMs). However, my understanding of > the auto-start feature is that it's really an auto-restart -- it will > restart a VM that was running if the datacenter crashes, but if I shut it > down manually and then "reboot" the cluster, those VMs wont come back > automatically. As I am on a single-host system, I need it to start from a > clean shutdown and bring up all the VMs in addition to dealing with > power-outage reboots. > > I work from the "if it aint broke, don't fix it" camp. So I think I'm > going to stick with 4.3 until I can't anymore. Why not open RFE to add the feature you need? You can use the python SDK to do anything supported by oVirt API. Did you look here? https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples > I am happy to share my startup script if someone else wants to port it to > work with 4.4. :-) > > -derek > > -- >Derek Atkins 617-623-3745 >de...@ihtfp.com www.ihtfp.com >Computer and Internet Security Consultant > ___ > 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/NHIGVCJOWLGUB4LJOKXNTFUJRNVYA5RB/ ___ 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/LA3GT6ZBOV25X35QGG7LMGSYIG4O5IWC/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Hi,
On Wed, May 20, 2020 12:28 pm, Gianluca Cecchi wrote:
> Il Mer 20 Mag 2020, 18:15 Derek Atkins ha scritto:
>
> [snip]
>
> I am happy to share my startup script if someone else wants to port it to
>> work with 4.4. :-)
>>
>> -derek
>>
>
> Interesting. yes, please.
> We could try to convert to python or through ansible and/or leverage
> already existing roles/modules.
>
> Gianluca
Sure,
I cannot attach the script because it will get blocked by the mailer, so
I'll just copy-and-paste it below (which of course means that it'll be
line-wrapped, which might break it but you'll at least see what it's
doing).
The script does have some embedded assumptions about my system (like the
number of storage domains to look for).
It's broken into two parts, the script itself (start_vms.sh) and a
sysconfig script that says what VMs to start. I run start_vms.sh from
/etc/rc.d/rc.local:
/usr/local/sbin/start_vms.sh > /var/log/start_vms 2>&1 &
The /etc/sysconfig/vm_list file looks like:
default_timeout=10
# Ordered list of VMs
declare -a vm_list=(
first-vm
second-vm
)
# Timeout override (otherwise use default_timeout)
declare -A vm_timeout=(
[first-vm]=30
)
The start_vms.sh script itself:
#!/bin/bash
[ -f /etc/sysconfig/vm_list ] || exit 0
. /etc/sysconfig/vm_list
echo -n "Starting at "
date
# Wait for the engine to respond
while [ `ovirt-shell -I -c -F -T 50 -E ping 2>/dev/null | grep -c success`
!= 1 ]
do
echo "Not ready... Sleeping..."
sleep 60
done
# Now wait for the storage domain to appear active
echo -n "Engine up. Searching for disks at " ; date
# The 4.3.x engine keeps stale data, so let's wait for it to update
# to the correct state before we start looking for storage domains
sleep 60
total_disks=`ovirt-shell -I -c -E summary | grep storage_domains-total |
sed -e 's/.*: //'`
# subtract one because we know we're not using the image-repository
total_disks=`expr $total_disks - 1`
active_disks=`ovirt-shell -I -c -E summary | grep storage_domains-active |
sed -e 's/.*: //'`
while [ $active_disks -lt $total_disks ]
do
echo "Storage Domains not active yet. Only found
$active_disks/$total_disks. Waiting..."
sleep 60
active_disks=`ovirt-shell -I -c -E summary | grep
storage_domains-active | sed -e 's/.*: //'`
done
# Now wait for the data center to show up
echo -n "All storage mounted. Waiting for datacenter to be up at "
date
while [ `ovirt-shell -I -c -E 'show datacenter Default' | grep
status-state | sed -e 's/.*: //'` != 'up' ]
do
echo "Not ready... Sleeping..."
sleep 60
done
# Now start all of the VMs in the requested order.
echo -n "Datacenter up. Starting VMs at "; date
for vm in "${vm_list[@]}"
do
timeout=${vm_timeout[$vm]:-$default_timeout}
ovirt-shell -I -c -E "action vm $vm start"
sleep "$timeout"
done
Enjoy!
-derek
--
Derek Atkins 617-623-3745
de...@ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
___
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/O3TENJOBFUZN6PYI3OR5TK3S5YJJJ6WH/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
Il Mer 20 Mag 2020, 18:15 Derek Atkins ha scritto: [snip] I am happy to share my startup script if someone else wants to port it to > work with 4.4. :-) > > -derek > Interesting. yes, please. We could try to convert to python or through ansible and/or leverage already existing roles/modules. Gianluca > > ___ 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/FZVZDWUQEKS6NEZBW2S3ZZVXL4ARMKVM/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
On Wed, May 20, 2020 11:19 am, Sandro Bonazzola wrote: > Il giorno mer 20 mag 2020 alle ore 16:33 ha scritto: > >> My enthusiasm for CentOS8 is limited. >> My enthusiasm for a hard migration even more so. >> So how much time do I have before 4.3 becomes inoperable? >> > > oVirt 4.3.10 is approaching GA and we expect 4.3.11 to be released too > before declaring 4.3 at the end of life. > After that, 4.3 should keep working till CentOS 7 or any other repo on the > system will break it with some incompatible change. > I totally understand system administrators' point of view and how > difficult > it is to find a good maintenance window for a busy production > environment, ensuring backups are recent enough, check new requirements > matching, give it a try on a test environment if it's available and so on. > That said, I would really encourage starting to plan a maintenance window > for upgrading to 4.4 as soon as practical. > It will be easier to help with upgrade from 4.3 at this time than 2 years > from now when 4.3 can be broken (or new hardware replacement will be > missing drivers on CentOS 7) and there won't be any additional release for > fixing upgrade incompatibilities. I can't speak to other people, but the lack of "ovirt-shell" for 4.4 is a deal-breaker for me to upgrade at this time, and probably for the forseeable future. I've been working on migrating my mail server for 3 years now and still haven't finished that; migrating ovirt to a new platform that requires new startup support?? Haha. Granted, I suspect SOME of the reasons I have this script might be implemented in 4.4 (e.g. auto-start of VMs). However, my understanding of the auto-start feature is that it's really an auto-restart -- it will restart a VM that was running if the datacenter crashes, but if I shut it down manually and then "reboot" the cluster, those VMs wont come back automatically. As I am on a single-host system, I need it to start from a clean shutdown and bring up all the VMs in addition to dealing with power-outage reboots. I work from the "if it aint broke, don't fix it" camp. So I think I'm going to stick with 4.3 until I can't anymore. I am happy to share my startup script if someone else wants to port it to work with 4.4. :-) -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/NHIGVCJOWLGUB4LJOKXNTFUJRNVYA5RB/
[ovirt-users] Re: oVirt 4.4.0 Release is now generally available
My enthusiasm for CentOS8 is limited. My enthusiasm for a hard migration even more so. So how much time do I have before 4.3 becomes inoperable? ___ 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/EJ4SDWF5SR3HOA5AAZZDRSIYBR73IORC/
