[Call for feedback] anybody gave 4.1 beta a try?
Hi, any feedback on 4.1 beta we released last week? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Sandro, just tried to install self hosted engine in a nested environment (host is free ESXi 6.0 where I also have a working nested oVirt cluster of 3 HCI gluster hosts). The host is CentOS 7.2 updated with CR repo enabled (so it should be an upcoming CentOS 7.3). I used the provided appliance in ovirt-engine-appliance-4.1-20161202.1.el7.centos.noarch the deploy command arrived at this point and then failed [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Configuring libvirt [ INFO ] Configuring VDSM [ INFO ] Starting vdsmd [ INFO ] Configuring the management bridge [ INFO ] Creating Storage Domain [ INFO ] Creating Storage Pool [ INFO ] Connecting Storage Pool [ INFO ] Verifying sanlock lockspace initialization [ INFO ] Creating Image for 'hosted-engine.lockspace' ... [ INFO ] Image for 'hosted-engine.lockspace' created successfully [ INFO ] Creating Image for 'hosted-engine.metadata' ... [ INFO ] Image for 'hosted-engine.metadata' created successfully [ INFO ] Creating VM Image [ INFO ] Extracting disk image from OVF archive (could take a few minutes depending on archive size) [ INFO ] Validating pre-allocated volume size [ INFO ] Uploading volume to data domain (could take a few minutes depending on archive size) [ INFO ] Image successfully imported from OVF [ INFO ] Destroying Storage Pool [ INFO ] Start monitoring domain [ INFO ] Configuring VM [ INFO ] Updating hosted-engine configuration [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Creating VM [ ERROR ] Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20161206171233.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161206165954-m8tml8.log Inside the logfile I see this: 2016-12-06 17:12:26 DEBUG otopi.context context._executeMethod:128 Stage closeup METHOD otopi.p lugins.gr_he_setup.vm.runvm.Plugin._boot_from_hd 2016-12-06 17:12:31 DEBUG otopi.ovirt_hosted_engine_setup.tasks tasks.wait:52 Waiting for VM do wn 2016-12-06 17:12:31 DEBUG otopi.ovirt_hosted_engine_setup.tasks tasks.wait:58 Virtual machine d oes not exist 2016-12-06 17:12:31 INFO otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:149 Creating VM 2016-12-06 17:12:31 DEBUG otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:281 {'status': { 'message': u'Error creating the requested VM', 'code': 9}} 2016-12-06 17:12:31 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/vm/runvm.py", line 168, in _boot_from_hd self._create_vm() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/mixins.py", line 287, in _create_vm message=status['status']['message'] RuntimeError: Cannot create the VM: Error creating the requested VM 2016-12-06 17:12:31 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM Anything I can check?
On Tue, Dec 6, 2016 at 5:18 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Sandro, just tried to install self hosted engine in a nested environment (host is free ESXi 6.0 where I also have a working nested oVirt cluster of 3 HCI gluster hosts).
The host is CentOS 7.2 updated with CR repo enabled (so it should be an upcoming CentOS 7.3).
Note that if you're using CR repo you'll need the new qemu-kvm-ev 2.6 from virt sig testing: http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/
I used the provided appliance in ovirt-engine-appliance-4.1- 20161202.1.el7.centos.noarch
the deploy command arrived at this point and then failed
[ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Configuring libvirt [ INFO ] Configuring VDSM [ INFO ] Starting vdsmd [ INFO ] Configuring the management bridge [ INFO ] Creating Storage Domain [ INFO ] Creating Storage Pool [ INFO ] Connecting Storage Pool [ INFO ] Verifying sanlock lockspace initialization [ INFO ] Creating Image for 'hosted-engine.lockspace' ... [ INFO ] Image for 'hosted-engine.lockspace' created successfully [ INFO ] Creating Image for 'hosted-engine.metadata' ... [ INFO ] Image for 'hosted-engine.metadata' created successfully [ INFO ] Creating VM Image [ INFO ] Extracting disk image from OVF archive (could take a few minutes depending on archive size) [ INFO ] Validating pre-allocated volume size [ INFO ] Uploading volume to data domain (could take a few minutes depending on archive size) [ INFO ] Image successfully imported from OVF [ INFO ] Destroying Storage Pool [ INFO ] Start monitoring domain [ INFO ] Configuring VM [ INFO ] Updating hosted-engine configuration [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Creating VM [ ERROR ] Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20161206171233.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy Log file is located at /var/log/ovirt-hosted-engine- setup/ovirt-hosted-engine-setup-20161206165954-m8tml8.log
Inside the logfile I see this:
2016-12-06 17:12:26 DEBUG otopi.context context._executeMethod:128 Stage closeup METHOD otopi.p lugins.gr_he_setup.vm.runvm.Plugin._boot_from_hd 2016-12-06 17:12:31 DEBUG otopi.ovirt_hosted_engine_setup.tasks tasks.wait:52 Waiting for VM do wn 2016-12-06 17:12:31 DEBUG otopi.ovirt_hosted_engine_setup.tasks tasks.wait:58 Virtual machine d oes not exist 2016-12-06 17:12:31 INFO otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:149 Creating VM 2016-12-06 17:12:31 DEBUG otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:281 {'status': { 'message': u'Error creating the requested VM', 'code': 9}} 2016-12-06 17:12:31 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../ plugins/gr-he-setup/vm/runvm.py", line 168, in _boot_from_hd self._create_vm() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/mixins.py", line 287, in _create_vm message=status['status']['message'] RuntimeError: Cannot create the VM: Error creating the requested VM 2016-12-06 17:12:31 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM
Anything I can check?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Dec 6, 2016 at 5:23 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi Sandro, just tried to install self hosted engine in a nested environment (host is free ESXi 6.0 where I also have a working nested oVirt cluster of 3 HCI gluster hosts).
The host is CentOS 7.2 updated with CR repo enabled (so it should be an upcoming CentOS 7.3).
Note that if you're using CR repo you'll need the new qemu-kvm-ev 2.6 from virt sig testing: http://buildlogs.centos.org/centos/7/virt/x86_ 64/kvm-common/
OK. Must I start from scratch or can I use the generated answer file from previous step in any way? [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20161206171233.conf' Best way to clean up the host from where I executed "hosted-engine --deploy" command? Thanks, Gianluca
On Tue, Dec 6, 2016 at 5:32 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Dec 6, 2016 at 5:23 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi Sandro, just tried to install self hosted engine in a nested environment (host is free ESXi 6.0 where I also have a working nested oVirt cluster of 3 HCI gluster hosts).
The host is CentOS 7.2 updated with CR repo enabled (so it should be an upcoming CentOS 7.3).
Note that if you're using CR repo you'll need the new qemu-kvm-ev 2.6 from virt sig testing: http://buildlogs.centos.org/centos/7/virt/x86_64/ kvm-common/
OK. Must I start from scratch or can I use the generated answer file from previous step in any way?
[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20161206171233.conf'
You can re-use the answer file: hosted-engine --deploy --config-append=/var/lib/ovirt-hosted-engine- setup/answers/answers-20161206171233.conf
Best way to clean up the host from where I executed "hosted-engine --deploy" command?
Simone ^^
Thanks, Gianluca
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Dec 6, 2016 at 5:45 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Tue, Dec 6, 2016 at 5:32 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
On Tue, Dec 6, 2016 at 5:23 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi Sandro, just tried to install self hosted engine in a nested environment (host is free ESXi 6.0 where I also have a working nested oVirt cluster of 3 HCI gluster hosts).
The host is CentOS 7.2 updated with CR repo enabled (so it should be an upcoming CentOS 7.3).
Note that if you're using CR repo you'll need the new qemu-kvm-ev 2.6 from virt sig testing: http://buildlogs.cent os.org/centos/7/virt/x86_64/kvm-common/
OK. Must I start from scratch or can I use the generated answer file from previous step in any way?
[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20161206171233.conf'
You can re-use the answer file: hosted-engine --deploy --config-append=/var/lib/ovirt-hosted-engine-setup/ answers/answers-20161206171233.conf
Best way to clean up the host from where I executed "hosted-engine --deploy" command?
Simone ^^
Look here: https://gerrit.ovirt.org/#/c/67592 Still under testing: if something goes wrong you could just reinstall vdsm, libvirt and ovirt-hosted-engine-setup rpms to get the missing files.
Thanks, Gianluca
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Dec 6, 2016 at 5:45 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
OK. Must I start from scratch or can I use the generated answer file from previous step in any way?
[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-
setup/answers/answers-20161206171233.conf'
You can re-use the answer file: hosted-engine --deploy --config-append=/var/lib/ovirt-hosted-engine-setup/ answers/answers-20161206171233.conf
It seems I got the same inside the new log file 2016-12-06 21:13:31 INFO otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:149 Creating VM 2016-12-06 21:13:31 DEBUG otopi.plugins.gr_he_setup.vm.runvm mixins._create_vm:281 {'status': { 'message': u'Error creating the requested VM', 'code': 9}} 2016-12-06 21:13:31 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/vm/runvm.py", line 168, in _boot_from_hd self._create_vm() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/mixins.py", line 287, in _create_vm message=status['status']['message'] RuntimeError: Cannot create the VM: Error creating the requested VM 2016-12-06 21:13:31 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM 2016-12-06 21:13:31 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Cannot create the VM: Error creating the requested VM 2016-12-06 21:13:31 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN 2016-12-06 21:13:31 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/error=bool:'True' 2016-12-06 21:13:31 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Cannot create the VM: Error creating the requested VM',), <traceback object at 0x5cd7dd0>)]' Current packages: [root@ovirt41 ~]# rpm -qa|grep qemu | grep kvm qemu-kvm-ev-2.6.0-27.1.el7.x86_64 qemu-kvm-tools-ev-2.6.0-27.1.el7.x86_64 qemu-kvm-common-ev-2.6.0-27.1.el7.x86_64 [root@ovirt41 ~]# But in vdsm.log I see this message: 2016-12-06 21:13:25,587 ERROR (jsonrpc/6) [root] failed to retrieve Hosted Engine HA info (api: 252) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 231, in _getHaInfo stats = instance.get_all_stats() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", line 102, in get_all_stats with broker.connection(self._retries, self._wait): File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 99, in connection self.connect(retries, wait) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 78, in connect raise BrokerConnectionError(error_msg) BrokerConnectionError: Failed to connect to broker, the number of errors has exceeded the limit (1) 2016-12-06 21:13:25,589 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getStats succee ded in 0.01 seconds (__init__:515) 2016-12-06 21:13:31,796 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call VM.getStats failed ( error 1) in 0.00 seconds (__init__:515) 2016-12-06 21:13:31,806 ERROR (jsonrpc/0) [virt.api] FINISH create error=Error creating the requested VM (api:54) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 52, in method ret = func(*args, **kwargs) File "/usr/share/vdsm/API.py", line 220, in create 'Unknown display type %s' % vmParams.get('display')) CannotCreateVM: Error creating the requested VM 2016-12-06 21:13:31,808 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.create failed (error 9) in 0.00 seconds (__init__:515) So I think the problem consists in trying to create engine with qxl video device (that is a right initial option offered...) I changed the answer file this way old = < new = > < OVEHOSTED_VDSM/consoleType=str:qxl ---
OVEHOSTED_VDSM/consoleType=str:vnc
and the deploy went ahead creating the VM [ INFO ] Creating VM You can now connect to the VM with the following command: hosted-engine --console You can also graphically connect to the VM from your system with the following command: remote-viewer vnc://ovirt41.localdomain.local:5900 Use temporary password "0979VeaN" to connect to vnc console. Please ensure that your Guest OS is properly configured to support serial console according to your distro documentation. Follow http://www.ovirt.org/Serial_Console_Setup#I_need_to_access_the_console_the_o... for more info. If you need to reboot the VM you will need to start it manually using the command: hosted-engine --vm-start You can then set a temporary password using the command: hosted-engine --add-console-password [ INFO ] Running engine-setup on the appliance But it seems stuck in the bios.... see: https://drive.google.com/file/d/0BwoPbcrMv8mvSE1mWFVIUEhiRTg/view?usp=sharin...
On Tue, Dec 6, 2016 at 9:43 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I changed the answer file this way
old = < new = >
< OVEHOSTED_VDSM/consoleType=str:qxl ---
OVEHOSTED_VDSM/consoleType=str:vnc
and the deploy went ahead creating the VM
[ INFO ] Creating VM You can now connect to the VM with the following command: hosted-engine --console You can also graphically connect to the VM from your system with the following command: remote-viewer vnc://ovirt41.localdomain.local:5900 Use temporary password "0979VeaN" to connect to vnc console. Please ensure that your Guest OS is properly configured to support serial console according to your distro documentation. Follow http://www.ovirt.org/Serial_Console_Setup#I_need_to_ access_the_console_the_old_way for more info. If you need to reboot the VM you will need to start it manually using the command: hosted-engine --vm-start You can then set a temporary password using the command: hosted-engine --add-console-password [ INFO ] Running engine-setup on the appliance
But it seems stuck in the bios.... see: https://drive.google.com/file/d/0BwoPbcrMv8mvSE1mWFVIUEhiRTg/ view?usp=sharing
Here the HostedEngine.log generated under /var/log/libvirt/qemu https://drive.google.com/file/d/0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/view?usp=sharin... I see at the end of it the line warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
On Tue, Dec 6, 2016 at 9:51 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Here the HostedEngine.log generated under /var/log/libvirt/qemu
https://drive.google.com/file/d/0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/ view?usp=sharing
I see at the end of it the line
warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
It seems this second problem was due to qemu-kvm 2.6 too restrictive.... So I reverted to 2.3: Downgrading: qemu-img-ev x86_64 10:2.3.0-31.el7_2.21.1 ovirt-4.1-pre 791 k qemu-kvm-common-ev x86_64 10:2.3.0-31.el7_2.21.1 ovirt-4.1-pre 449 k qemu-kvm-ev x86_64 10:2.3.0-31.el7_2.21.1 ovirt-4.1-pre 2.1 M qemu-kvm-tools-ev x86_64 10:2.3.0-31.el7_2.21.1 ovirt-4.1-pre 250 k clean done with (my env is single host providing nfs export): umount /rhev/data-center/mnt/_var_lib_ovirt-hosted-engine-setup_tmpBrbRge umount /rhev/data-center/mnt/ovirt41\:_SHE__DOMAIN/ rm -rf /SHE_DOMAIN/* hosted-engine --vm-poweroff (vm was actually already down but the setup claimed it was up...) re-run host-deploy and completed successfully... [ INFO ] Engine is still not reachable, waiting... [ INFO ] Engine replied: DB Up!Welcome to Health Status! [ INFO ] Acquiring internal CA cert from the engine [ INFO ] The following CA certificate is going to be used, please immediately interrupt if not correct: [ INFO ] Issuer: C=US, O=localdomain.local, CN=ovirt41she.localdomain.local.40445, Subject: C=US, O=localdomain.local, CN=ovirt41she.localdomain.local.40445, Fingerprint (SHA-1): 744EDCF02EC8AC74E4C5E549AC464B1EC939D7DC [ INFO ] Connecting to the Engine [ INFO ] Waiting for the host to become operational in the engine. This may take several minutes... [ INFO ] Still waiting for VDSM host to become operational... [ INFO ] The VDSM Host is now operational [ INFO ] Saving hosted-engine configuration on the shared storage domain [ INFO ] Shutting down the engine VM [ INFO ] Enabling and starting HA services [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20161207111416.conf' [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Hosted Engine successfully deployed [root@ovirt41 ~]# Now going to test ... ;-)
Hi, any feedback on 4.1 beta we released last week? Thanks,
- I upgraded from 4.0 to 4.1pre yesterday and had a couple of problems
On 6-12-2016 9:38, Sandro Bonazzola wrote: that I think are of my own doing. I'm running hosted-engine on my laptop with a NFS data domain (I know about the deadlock possibility) Host OS was FC23 and needed to be upped to FC24 and the engine is running Centos-7.2 so no changes. Updated the engine first and then updated my fedora version. That went well except that it complained about I think vdsm needing a version that conflicted with an existing one (libvirt-client). After allowing the update to erase the problematic packages I ended up with another slight problem but fixed that by deinstalling the problematic packages and reinstalling hosted-engine. I ofcourse lost the configuration files but they are all saved as *.rpmsave. Finding those files and moving them back into place and reinstalling hosted-engine-ha-setup and hosted-engine-ha fixed most of not all problems (systemd autostarting services). Restarting my system and everything came backup up :-) Next up is testing all those shiny new items. Joop
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is marked as V3. The nfs mount from host is still v3, but I think it is not related and instead V4 refers to functionalities of storage domain itself... In this case, where to find V3 vs V4 storage domain features? Gianluca
The storage domain version is now v4 to support the new qcow2v3 version. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Wed, Dec 7, 2016 at 3:10 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is marked as V3. The nfs mount from host is still v3, but I think it is not related and instead V4 refers to functionalities of storage domain itself... In this case, where to find V3 vs V4 storage domain features?
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Dec 7, 2016 at 3:10 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is marked as V3. The nfs mount from host is still v3, but I think it is not related and instead V4 refers to functionalities of storage domain itself...
Right.
In this case, where to find V3 vs V4 storage domain features?
http://www.ovirt.org/develop/release-management/features/storage/DataCenterV... - but it may need some updates. Y.
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Dec 8, 2016 at 5:33 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Wed, Dec 7, 2016 at 3:10 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is marked as V3. The nfs mount from host is still v3, but I think it is not related and instead V4 refers to functionalities of storage domain itself...
Right.
In this case, where to find V3 vs V4 storage domain features?
http://www.ovirt.org/develop/release-management/features/ storage/DataCenterV4_1/ - but it may need some updates. Y.
There is a more detailed feature page for qcow2v3 which is currently under review, here it is: https://github.com/maorlipchuk/ovirt-site/blob/cdbbfa5250af0e207ff151af67f18...
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
First glance at 4.1 Installation seemed easier than with earlier versions ( but I have installed it a few times now ). Hosted engine reports 100% CPU usage even if the host is basically idle [image: Inline images 1] I'll feed back more as and when I get chance to use it, feels good so far though. Keep on with the great work! Regards, Brett On 12 December 2016 at 17:44, Maor Lipchuk <mlipchuk@redhat.com> wrote:
On Thu, Dec 8, 2016 at 5:33 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Wed, Dec 7, 2016 at 3:10 PM, Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, any feedback on 4.1 beta we released last week? Thanks,
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is marked as V3. The nfs mount from host is still v3, but I think it is not related and instead V4 refers to functionalities of storage domain itself...
Right.
In this case, where to find V3 vs V4 storage domain features?
http://www.ovirt.org/develop/release-management/features/sto rage/DataCenterV4_1/ - but it may need some updates. Y.
There is a more detailed feature page for qcow2v3 which is currently under review, here it is:
https://github.com/maorlipchuk/ovirt-site/blob/ cdbbfa5250af0e207ff151af67f188b3451d4c33/source/develop/ release-management/features/storage/qcow2v3.html.md
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/users
participants (8)
-
Gianluca Cecchi -
Joop -
Maor Lipchuk -
Maton, Brett -
Sandro Bonazzola -
Simone Tiraboschi -
Yaniv Dary -
Yaniv Kaul