6:43 a.m.
Hi,
we're also extensively using ceph via cinder on docker (Kolla project),
but we're stuck on Pike for the missing keystone v3 support.
While cinderlib is desirable and it's a good solution for simple uses,
adding support for keystone v3 and keeping the native cinder interface
would also be good, for cases where you already have an openstack
infrastructure available and you want to manage a storage system from a
single place. The other reason to keep the current solution, at least
for now, is what Matthias is mentioning: the transition phases.
How difficult it is to add the keystone v3 support for the storage side
in ovirt, given you should already have the needed libs as you use them
for the networking?
Thanks,
Alessandro
Il 15/11/18 12:58, Matthias Leopold ha scritto:
> Hi,
>
> we are extensively using Ceph storage using the present
> OpenStack/Cinder integration in oVirt 4.2 which works for us.
> Openstack version in use is Pike.
>
> I already heard about the plan to move to cinderlib which sounds
> promising. I very much hope there will be a migration scenario for
> users of "full" Openstack/Cinder installations when upgrading to oVirt
> 4.3.
>
> thanks
> Matthias
>
> Am 11.11.18 um 15:49 schrieb Nir Soffer:
>> On Sat, Nov 10, 2018 at 6:52 PM Gianluca Cecchi
>> <gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>>
wrote:
>>
>> Hello,
>> do you think it is ok to use Rocky version of Openstack to integrate
>> its services with oVirt 4.2.7 on CentOS 7?
>> I see on https://repos.fedorapeople.org/repos/openstack/ that, if
>> Rocky is too new, between the older releases available there are,
>> from newer to older:
>> Queens
>> Pike
>> Ocata
>> Newton
>>
>>
>> Nobody working on oVirt is testing any release of Openstack in the
>> recent years.
>>
>> The Cinder/Ceph support was released as tech preview in 3.6, and no
>> work was
>> done since then, and I think this will be deprecated soon.
>>
>> For 4.3 we are working on a different direction, using Cinderlib
>> https://github.com/Akrog/cinderlib
>>
>> This is a way to use Cinder drivers without Openstack installation.
>> The same library is used to provide Cinder based storage in Kubernetes.
>> https://github.com/Akrog/ember-csi
>>
>> You can find an early draft here for this feature. Note that it is
>> expected to be
>> updated in the next weeks, but it can give you some idea on what we are
>> working on.
>>
https://github.com/oVirt/ovirt-site/blob/f88f38ebb9afff656ab68a2d60c2b3ae...
>>
>>
>> This will be tested with some version of Cinder drivers. I guess we
>> will have
>> more info about it during 4.3 development.
>>
>> At the moment I have two separate lab environments:
>> oVirt with 4.2.7
>> Openstack with Rocky (single host with packstack allinone)
>>
>> just trying first integration steps with these versions, it seems
>> I'm not able to communicate with glance, because I get in engine.log
>> 2018-11-10 17:32:58,386+01 ERROR
>>
[org.ovirt.engine.core.bll.provider.storage.AbstractOpenStackStorageProviderProxy]
>> (default task-51) [e2fccee7-1bb2-400f-b8d3-b87b679117d1] Not Found
>> (OpenStack response error code: 404)
>>
>>
>> I think Glance support should work. Elad, which version of Glance was
>> tested for 4.2?
>>
>> Regarding which Openstack version can work best with oVirt, maybe
>> Openstack guys I added can give a better answer.
>>
>> Nir
>>
>> Nothing in glance logs on openstack, apparently.
>> In my test I'm using
>> http://xxx.xxx.xxx.xxx:9292 as provider url
>> checked the authentication check box and
>> glance user with its password
>> 35357 as the port and services as the tenant
>>
>> a telnet on port 9292 of openstack server from engine to
>> openstack is ok
>>
>> similar with cinder I get:
>> 2018-11-10 17:45:42,226+01 ERROR
>>
[org.ovirt.engine.core.bll.provider.storage.AbstractOpenStackStorageProviderProxy]
>> (default task-50) [32a31aa7-fe3f-460c-a8b9-cc9b277deab7] Not Found
>> (OpenStack response error code: 404)
>>
>> So before digging more I would lile to be certain which one is
>> currently the best combination, possibly keeping as fixed the oVirt
>> version to 4.2.7.
>>
>> Thanks,
>> Gianluca
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> <mailto:users-leave@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C46XG5YF3JT...
>>
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZPHSATIWZXF...
>>
>