Skip to content
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

Open
allamand opened this issue Jun 10, 2016 · 8 comments
Open

Problem with ansible 2.1 #4

allamand opened this issue Jun 10, 2016 · 8 comments

Comments

@allamand
Copy link

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.

@codenrhoden
Copy link
Collaborator

Good catch -- I haven't tried Ansible 2.1 at all yet. I'll have to see what isn't backwards compatible.

@holms
Copy link
Contributor

holms commented Aug 6, 2018

This is 2016 issue... is this project abandoned?

@clintkitson
Copy link
Contributor

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?

@holms
Copy link
Contributor

holms commented Aug 8, 2018

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

@clintkitson
Copy link
Contributor

clintkitson commented Aug 8, 2018 via email

@holms
Copy link
Contributor

holms commented Aug 10, 2018

@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

@clintkitson
Copy link
Contributor

clintkitson commented Aug 10, 2018 via email

@holms
Copy link
Contributor

holms commented Aug 11, 2018

@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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants