Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Support getting VM ID from photon for the volume plugin #907

Closed
govint opened this issue Feb 13, 2017 · 3 comments
Closed

Support getting VM ID from photon for the volume plugin #907

govint opened this issue Feb 13, 2017 · 3 comments

Comments

@govint
Copy link
Contributor

govint commented Feb 13, 2017

ON plugin startup for photon driver, get the VM ID from photon.

Actually, given the photon controller IP we may as well query all tenants, projects and then figure the project and VM ID. Ideally Photon should be able to give this. but at the cost of a slower plugin start up (for a photon controller with large number of clients/projects and VMs) we can do with a single input from the user.

@govint govint added this to the 0.12 milestone Feb 13, 2017
@govint govint self-assigned this Feb 13, 2017
@tusharnt tusharnt modified the milestones: 0.13, 0.12 Feb 23, 2017
@tusharnt tusharnt added P1 and removed P0 labels Mar 2, 2017
@tusharnt
Copy link
Contributor

tusharnt commented Mar 2, 2017

@govint can you please confirm whether this is a purely a performance issue? Can you please post some analysis of how much performance improvement we will get if we do this fix?

@tusharnt tusharnt modified the milestones: v1 GA, 0.13 Mar 2, 2017
@govint
Copy link
Contributor Author

govint commented Mar 2, 2017

@tusharnt this is not a performance issue as much as its a user experience issue. I don't believe Photon deployments will be loaded with tenants and projects that fetching the tenant and project list per tenant will be hugely impactful. Plus Photon Controller is planning on exposing a meta-data service that will remove the need for the VM to identify itself in this way in the future. This change simplifies the user's work a lot.

Currently user has to provide the VM and project IDs to run the plugin - from discussions it was felt that this is cumbersome for the user and hence the change.

@tusharnt tusharnt modified the milestones: Future, v1 GA Jul 11, 2017
@govint
Copy link
Contributor Author

govint commented Jul 17, 2017

PC platform issues will be picked up later as needed. Closing.

@govint govint closed this as completed Jul 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants