Has anyone had any success installing the docker Cinder interface for oVirt3.6 on
Centos7.1?
Using the current Engine installation ends up with a non-functioning cinder
a83ce47cef7e kollaglue/centos-rdo-cinder:kilo "/start.sh"
4 days ago Restarting (127) 11 minutes ago ?
The Kolla project changed the way it distributed it's docker instances to use Ansible
to configure the image.
oVirt has yet to implement a way of using the Ansible configuration and recommends using
the Kolla documentation.
I have been beating my head against the kolla 'so called' quick start guide
https://github.com/openstack/kolla/blob/master/doc/quickstart.rst
I haven't followed the guide to the letter, eg I want to use the Centos docker package
which does seem to be the correct version, rather than build the very latest Docker as
recommended.
The error seems to indicate that the client has moved past the server version
recommended.
failed: [localhost] => {"changed": false, "failed": true}
msg: Docker API Error: client is newer than server (client API version: 1.21, server API
version: 1.20)
FATAL: all hosts have already failed -- aborting
I can't work out whether the build just broken or I have missed something. It's
not obvious from the documentation exactly what I must do to get a usable image to test
Ceph on oVirt.
I think I need to just configure the container but it seems I have build a complete
Openstack Kolla implementation from source and load it into my own docker registry and
then configure it????
Regards
Darryl
________________________________
The contents of this electronic message and any attachments are intended only for the
addressee and may contain legally privileged, personal, sensitive or confidential
information. If you are not the intended addressee, and have received this email, any
transmission, distribution, downloading, printing or photocopying of the contents of this
message or attachments is strictly prohibited. Any legal privilege or confidentiality
attached to this message and attachments is not waived, lost or destroyed by reason of
delivery to any person other than intended addressee. If you have received this message
and are not the intended addressee you should notify the sender by return email and
destroy all copies of the message and any attachments. Unless expressly attributed, the
views expressed in this email do not necessarily represent the views of the company.