Hi,
I'm trying to use the Ceph iSCSI gateway with oVirt.
According to my tests with oVirt 4.3.2
* you cannot separate iSCSI discovery auth and target auth
* you cannot use an iSCSI gateway that has no discovery auth, but uses
CHAP for targets
This means I'm forced to use the same credentials for discovery auth and
target auth.
In Ceph iSCSI gateway I can have multiple targets with use different
credentials, but I can define discovery auth only once for the whole
gateway (or have no discovery auth).
If all of this is correct and I want to use the Ceph iSCSI gateway with
oVirt
* I have to use discovery auth
* the credentials for discovery auth will give every other Ceph iSCSI
gateway user access to the oVirt target
This is not a desirable situation.
Did I understand anything wrong? Are there other ways to solve this?
thx
matthias
hello dear all,
is it possible to make a compute-nove VM inside oVirt, using which, to be able to create VM instances inside oVirt through openstack horizon?
to make it simple, is it possible to have oVirt has the hypervisor for openstack, while having a nova-compute node as a VM inside ovirt?
as a hint, the same thing is possible via vsphere vCenter, if we install vCenter driver on the nova-compute node.
thank you for your support!
Hi All,
I have stumbled upon a potential bug in UI. Can someone test it , in order to reproduce it ?
How to reproduce:1. Create a VM2. Within the new VM wizard - Create a disk and select Thin Provision.3. Create the VM and wait for the disk to be completed.4. Check the disk within UI - Allocation Policy is set to "Preallocation"
Best Regards,Strahil Nikolov
Hi,
I'm trying to update a storage lease via python sdk but I can’t seem to
figure out how to wait for the storage lease configuration to finish.
The vm status does not show “configuration in progress” just “up” and
the event is created as soon as I issue the update, not when its done.
Can someone give me a hint or point me to an example?
https://github.com/Klaas-/ovirt-engine-sdk/blob/4094d3a2d4b011d4926e58374...
Greetings
Klaas
Complete shutdown of 4.3.3 cluster, change cluster from 4.2 to 4.3 compatibility and upgrade of all hosts to current 4.3.3 with patches has seemingly fixed everything.
> Each data has to be written on the host itself and on the two remote ones so you are going to have 1000 mbps / 2 (external replicas ) / 8 (bit/bytes) = a max of 62.5 MB/s sustained throughput shared between all the VMs and this ignoring all the overheads.
> In practice it will be much less ending in a barely usable environment.
I am currently in this type of setup (replica 2 arbiter 1 on 1 gbit/s both storage and oVirt connectivity) and the maximum write (sequential) speed I can reach is aprox 89 MB/s.
I guess with replica 3 the maximum will be as Simone stated.
My maximum read speed is aprox 500 MB/s despite that local NVMe is capable of 1.3 GB/s and I guess FUSE is not using the local brick no matter I have set it up with cluster.use-local (or whatever it was called).
If possible , get a 10 gbit/s connectivity or multiple gbit interfaces ( as I'm planing to do in the nearest future).
Best Regards,
Strahil Nikolov
I worked through this previously and posted in IRC yesterday about
working around running ovirt nested under VMWare. I figured i'd post
it to the mail group so that it would be available in it's entirety
here for future reference:
The following gists explain the 3 major adjustments that have to be
made currently to get nested virt under vmware working:
https://gist.github.com/RabidCicada/993349b3a7eaf35637122f0122fdedb3https://gist.github.com/RabidCicada/bc01eb0b13195faa26520c0fb666ec34https://gist.github.com/RabidCicada/37ff6f1ed2afd8dd4edefac735536c69https://gist.github.com/RabidCicada/40655db1582ca5d07c9bbf2c429cdd01
Hopefully it can save others the huge amount of time it took me to
figure it all out.
Specifically it's a problem with the --machine type at 3 major parts
of the vm creation for the hosted-engine.
1) You have to fix the virt-install to use --machine pc-i440fx-rhel7.2.0
2) You have to fix the guestfish spinup of the partially configured vm
to use --machine pc-i440fx-rhel7.2.0, where they edit the nic config
among other things
3) You have to tell vdsm on the node to use --machine pc-i440fx-rhel7.2.0
I don't know the underlying reason why a --machine type >
pc-i440fx-rhel7.2.0 breaks the system but it ends up resulting in a
bios freeze.
Again, Hope this helps someone. Suggested only to use for a test/dev system.
Hi All,
I'm having an issue to create a VM in my second cluster called "Intel" which consists of only 1 Host -> ovirt3 which plays the role of a gluster arbiter in my hyperconverged setup.
When I try to create the VM (via UI) I receive: "Cannot add VM. CPU Profile doesn't match provided Cluster."
When I try to select the host where I can put the VM , I see only ovirt1 or ovirt2 which are part of the 'Default' Cluster .
Do we have an opened bug for that ?
Note: A workaround is to create the VM in the Default cluster and later edit it to match the needed Cluster.
Best Regards,Strahil Nikolov
