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

Flocker abandoned? #3017

Open
holms opened this issue Aug 23, 2018 · 11 comments
Open

Flocker abandoned? #3017

holms opened this issue Aug 23, 2018 · 11 comments

Comments

@holms
Copy link

holms commented Aug 23, 2018

Sorry but last commit is in 2017 + your installation steps doesn't work as S3 bucket URL throws 404 error

Err:18 https://clusterhq-archive.s3.amazonaws.com/ubuntu/9.5/amd64  Release
  404  Not Found

So I assume this project is abandoned? Without flocker using docker-swarm is absolutely impossible.

@stmcginnis
Copy link

Yes, the project ended quite a while ago, unfortunately.

https://portworx.com/helping-clusterhq-flocker-customers-move-forward-2017/

@holms
Copy link
Author

holms commented Aug 23, 2018

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.

@wallnerryan
Copy link
Contributor

@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

@holms
Copy link
Author

holms commented Aug 23, 2018

Creating storage for every node.. why? Just use local disk space. Thanks for link though.
Also having port opened, no idea if I can use consul from swarm itself.. This lot more painful solution than netshare https://github.com/ContainX/docker-volume-netshare, because after all I need to automate all of it, and it's lot more body movements in here.

@wallnerryan
Copy link
Contributor

wallnerryan commented Aug 24, 2018

@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.

@holms
Copy link
Author

holms commented Aug 24, 2018

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 :/

@wallnerryan
Copy link
Contributor

Great, I’m happy to help any way I can. Feel feel to email me directly [email protected] or on slack @wallnerryan

@jsilberm
Copy link

Hi @holms: This might help too ...

@jsilberm
Copy link

https://github.com/portworx/terraporx/tree/master/digital_ocean

@holms
Copy link
Author

holms commented Aug 28, 2018

@jsilberm alright! you saved my day!

@ghost
Copy link

ghost commented Jan 5, 2019

Please archive repo or add a deprecation notice to the readme.

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

No branches or pull requests

4 participants