You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
@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 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.
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.
The text was updated successfully, but these errors were encountered: