-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with ansible 2.1 #4
Comments
Good catch -- I haven't tried Ansible 2.1 at all yet. I'll have to see what isn't backwards compatible. |
This is 2016 issue... is this project abandoned? |
Hello @holms, REX-Ray adopted the Docker managed plugin model which greatly decreased the reliance on operators to run REX-Ray as a standalone plugin. This project was never brought into the REX-Ray project itself but could if the community is interested in it. Can you describe your usage? |
Just want to have distributed volumes in Docker Swarm via digital ocean spaces. I have I'm actually almost done with my PR wonder it would be accepted here |
Is this something that you'd be willing to answer questions on? If so we
can move it over to the rexray/ github org.
…On Wed, Aug 8, 2018 at 2:26 PM, Roman Gorodeckij ***@***.***> wrote:
Just want to have distributed volumes in Docker Swarm via digital ocean
spaces. I have I'm actually almost done with my PR wonder it would be
accepted here
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABVMMXXEBs2GOBNyhb4q3xtjgPG2RZHNks5uO1edgaJpZM4IyrEV>
.
|
@clintkitson I'm not sure what you mean. Rexray already supports docker swarm and digital ocean spaces. It's just this playbook doesn't have such configuration implemented somehow |
We are looking for community members to help support features like Ansible
automation. If that is the case then we can justify bringing it into the
REX-Ray project and getting it more visibility.
…On Fri, Aug 10, 2018 at 2:25 AM Roman Gorodeckij ***@***.***> wrote:
@clintkitson <https://github.com/clintkitson> I'm not sure what you mean.
Rexray already supports docker swarm and digital ocean spaces. It's just
automation doesn't have such configuration implemented somehow
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABVMMcG-QvzJTi3ohdVER06p_amTDnhnks5uPVGEgaJpZM4IyrEV>
.
|
@clintkitson Would be nice, because I have at least 5 PR's to make in here in order to use this automation. I can help with reviewing PR's in here, I'm automating with ansible for years already :) |
Hi,
My Rexray deployment was broken when upgrading to ansible 2.1
In this case it must be a problem with ansible reading playbook configuration and the template is not fulfill anymore, so that it don't works.
I forced install ansible 2.0.1 which I was using previously and then my workflows works again.
http://releases.ansible.com/ansible/ansible-2.0.1.0.tar.gz
I didnt' find what changes in ansible 2.1 but it must be something that broke the actual playbook definition.
The text was updated successfully, but these errors were encountered: