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.

Sign up for GitHub

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

Jump to bottom

GlusterFS support #613

Open
rgooch opened this issue Jun 8, 2019 · 3 comments
Open

GlusterFS support #613

rgooch opened this issue Jun 8, 2019 · 3 comments

Comments

@rgooch
Copy link
Contributor

rgooch commented Jun 8, 2019 •
edited
Loading

@cviecco I'm thinking about some implementation questions. I'll put each one in a separate comment so that each can be replied to independently.

First, should VM owners specify which Gluster/volume to use for the backing store, or should they just specify that they want any GlusterFs volume?
@rgooch
Copy link
Contributor Author

rgooch commented Jun 8, 2019

@cviecco Secondly, should a common set of credentials be distributed to all Hypervisors, or should they be partitioned so that different sets of credentials are distributed to different groups of Hypervisors?

@cviecco
Copy link
Contributor

cviecco commented Jun 11, 2019

I am assuming each hypervisor will have its own set of TLS certs. But I could be convinced otherwise

@rgooch
Copy link
Contributor Author

rgooch commented Jun 11, 2019

No, the Hypervisors share the same client certificate. It's not a very powerful certificate. These are the permitted methods:
Hypervisor.PrepareVmForMigration ImageServer.CheckDirectory ImageServer.FindLatestImage ImageServer.GetImage ObjectServer.GetObjects

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cviecco @rgooch