"and lets the storage framework coordinate orchestration activities (like
ask the storage plug-in for a volume, then send a message to the hypervisor
to attach the resultant volume)."
I said that a little incorrectly. The storage framework shouldn't be
sending those messages to the hypervisors (as
I agree you'd want to get away from going from the agent to the SAN API.
My storage plug-in doesn't have any hypervisor dependencies, though. It
creates volumes, deletes them, and other SAN-related activities and lets
the storage framework coordinate orchestration activities (like ask the
storage
It's fine, I can leave that code as-is from 4.1 to 4.2 in my plugin,
but if the capability is there to move it I'd prefer to do so. I'm not
sure how we'd get away from calling into any of the hypervisors if we
need to attach disks, or manage default storage types. I can't create
storage on Xen with
I believe, though, we should look into adding calls to grantAccess and
revokeAccess for 4.3.
For 4.2 I didn't worry about it because my plug-in didn't work with KVM. I
set XenServer and VMware up to use shared SRs/datastores using CHAP
credentials that I added to all hosts in the cluster (programm
Also, we can bring John Burwell into this as he had related comments
several months ago, but we did not want to have the storage plug-ins
calling into the hypervisors. The idea was to get away from having any
hypervisor dependencies in the storage plug-ins.
The default storage plug-in does not fol
Hey Marcus,
As far as I remember, grantAccess and revokeAccess are not invoked at all
in 4.2. Edison may be able to elaborate more on this, but I don't believe
the framework ever calls them.
Talk to you later
On Sat, Sep 21, 2013 at 11:02 PM, Marcus Sorensen wrote:
> Oh, one more question. Is
Oh, one more question. Is grantAccess/revokeAccess called as I'd
expect for migration, e.g. when PrepareForMigrationCommand is called
on the target host we can grantAccess to the new host, and then when
MigrateCommand returns successfully from the old host we revokeAccess
from the old host?
On Sat
All,
We've had our own storage plugins based on the 4.1 branch for
awhile now. Basically everything was done in KVM on the Agent side.
With the new storage framework in place for 4.2, I'm working on
splitting this code between Agent-specific (attach to VM, etc) and the
code that talks to the SAN
