On Wed, 14 Nov 2018 18:04:20 +0200
Dan Kenigsberg <dan...@redhat.com> wrote:

> On Sun, Nov 11, 2018 at 7:04 PM Gianluca Cecchi
> <gianluca.cec...@gmail.com> wrote:
> >
> > On Sun, Nov 11, 2018 at 3:50 PM Nir Soffer <nsof...@redhat.com> wrote:  
> >>
> >> On Sat, Nov 10, 2018 at 6:52 PM Gianluca Cecchi 
> >> <gianluca.cec...@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.  
> 
> Actually, Neutron and Glance are actively tested.
> 
> >>  
> >
> > Strange... I think oVirt is the natural platform to test features to have 
> > them on RHV if considered enterprise ready.
> > And reading the downstream latest documentation for RHV 4.2 I see this 
> > regarding external providers:
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/chap-external_providers
> >
> > And there is explicit reference to
> >
> > 1) Glance
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-adding_external_providers#Adding_an_OpenStack_Image_Service_Glance_for_Image_Management
> > without any particular restriction described
> >
> > 2) Neutron
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-adding_external_providers#Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning
> > with the note:
> > "
> > Important
> > Red Hat Virtualization supports Red Hat OpenStack Platform versions 8, 9, 
> > 10, 11, and 12 as external network providers.
> > "
> >
> > BTW: the release cycles are here:
> > https://access.redhat.com/support/policy/updates/openstack/platform
> >
> > 3) Cinder
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-adding_external_providers#Adding_an_OpenStack_Block_Storage_Cinder_Instance_for_Storage_Management
> > with the only note regarding Ceph as a provider for block storage to use 
> > with Cinder
> > "
> > Add an OpenStack Block Storage (Cinder) instance for storage management to 
> > the Red Hat Virtualization Manager. The OpenStack Cinder volumes are 
> > provisioned by Ceph Storage.
> > "
> >
> > Coming back to oVirt 4.2.7 I see all of the 3 above providers present and 
> > referenced when I go and add external providers, so it doesn't seem to the 
> > final user/admin as an abandoned feature
> >  
> >> 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.
> >>  
> >
> > Actually it seems yet a tech preview in latest 4.2, if the manual is 
> > correct (see link given above for Cinder)
> >  
> >>
> >> 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/f88f38ebb9afff656ab68a2d60c2b3ae88c21860/source/develop/release-management/features/storage/cinderlib-integration.html.md
> >>
> >> This will be tested with some version of Cinder drivers. I guess we will 
> >> have
> >> more info about it during 4.3 development.
> >>  
> >
> > I will go through reading them, thanks
> >
> >  
> >>>
> >>> 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?  
> >
> >
> > Based on the restrictions described for Neutron Provider above, I right 
> > deployed, always on CentOS 7.5 and using packstack allinone method, the 
> > oldest release I found a repo for at 
> > http://mirror.centos.org/centos/7/cloud/x86_64/ .
> > That is Ocata (aka the base for OSP 11) and at least the glance connection 
> > works now out of the box, using the same parameters that dind't work with 
> > Rocky.
> >
> > 2018-11-11 17:52:46,320+01 INFO  
> > [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> > (EE-ManagedThreadFactory-engineScheduled-Thread-14) [4e83174] Running 
> > command: SyncNetworkProviderCommand internal: true.
> > 2018-11-11 17:52:46,432+01 INFO  
> > [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-61) [] 
> > User admin@internal successfully logged in with scopes: ovirt-app-api 
> > ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search 
> > ovirt-ext=token-info:validate ovirt-ext=token:password-access
> > 2018-11-11 17:52:46,576+01 INFO  
> > [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] 
> > (EE-ManagedThreadFactory-engineScheduled-Thread-14) [4e83174] Lock freed to 
> > object 
> > 'EngineLock:{exclusiveLocks='[0799c428-dc87-4ee4-900c-1ad3927dab6c=PROVIDER]',
> >  sharedLocks=''}'
> >
> > And I'm able to see the pre-created cirros glance image provided by the 
> > packstack installation in the added storage domain in oVirt:
> > https://drive.google.com/file/d/1msHuY-3r9bgXV92PaU36dAa9Z37BXdDV/view?usp=sharing
> >
> > Donna if a problem in configuration with packstack passing from Ocata to 
> > Rocky or any feature itself that changed with Rocky.
> > I have both (Rocky server and Ocata server) and can compare them if it can 
> > be of any help to have Rocky working with oVirt 4.2.7  
> 
> Would you share your provider credentials? OpenStack dropped support
> for keystone v2, and in ovirt-4.2.7 we've introduced support for
> keystone v3. It smells related to your issue.
> 

Keystone v3 is only supported for oVirt's OpenStack Network Provider,
not for storage providers.
Please let us know, if you find any issues in using Neutron
integration as external Network provider for oVirt.
Please note, that for packstack's queens and rocky also the 
OVN layer 2 should work. In my simple packstack environment, even
physnet worked.
Please note that the oVirt's deployment of the Neutron provider on
host does not work for queens and rocky. Best way to prevent that
the deployment is triggered is to set no default network provider of
the cluster.

> >  
> >>
> >> Regarding which Openstack version can work best with oVirt, maybe
> >> Openstack guys I added can give a better answer.
> >>
> >> Nir  
> >
> >
> > Thanks Nir.
> > It would be of help to know cross relations and best combinations.
> > In the mean time I'm going ahead with Ocata and see Neutron and Cinder 
> > providers behaviour.
> >
> > Gianluca
> > _______________________________________________
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@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/TVH52LPLJT2BGTKJ2ZQH5URCQCWX2PCM/
> >   
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZBOSEMWKLSKBC27ZEEWX7DPYEMYQJEJ4/

Reply via email to