-
Notifications
You must be signed in to change notification settings - Fork 290
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
Flocker abandoned? #3017
Comments
Yes, the project ended quite a while ago, unfortunately. https://portworx.com/helping-clusterhq-flocker-customers-move-forward-2017/ |
That portworx seems to be not for virtual machines? It requires some kind of partition to exist on machine, which is non-sense in IAAS environment. |
@holms how so? Portworx just need a disk/device. It’s fairly common to attach disks to virtual machines and in fact we deploy this way with customers today. Let me know If you would like more information. In the meantime you can take a look at https://docs.portworx.com/scheduler/docker/install-swarm.html |
Creating storage for every node.. why? Just use local disk space. Thanks for link though. |
@holms I think I saw you on slack? But the difference is that the vms would participate in a Portworx storage cluster using the block device on the vms you want Portworx to run on. Then other vms (or the same ones) can run applications and can create many volumes from that cluster and set per volume settings on them like replication etc. |
Alright trying to automate digital ocean volumes, also got etcd cluster installed will see how it will go :) Portworx seems to be the only stable solution for swarm :/ |
Great, I’m happy to help any way I can. Feel feel to email me directly [email protected] or on slack @wallnerryan |
Hi @holms: This might help too ... |
@jsilberm alright! you saved my day! |
Please archive repo or add a deprecation notice to the readme. |
Sorry but last commit is in 2017 + your installation steps doesn't work as S3 bucket URL throws 404 error
So I assume this project is abandoned? Without flocker using docker-swarm is absolutely impossible.
The text was updated successfully, but these errors were encountered: