You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Progress
Plugin Source https://github.com/lafferty/cshv3
CS 4.0 Hyper-V Plugin
Target Hyper-V Server 2012
- Hyper-V 3.0
- WMI for VMM control
- No NFS client
Strategy: Connected Agent Model
- Java-based Container executes on each Hyper-V
- Business Logic accesses WMI via scripts
- Use existing SystemVMs
- Run on surrogate XenServer cluster
Current Limits
- Reduced set of commands and command options
- VLAN isolation only
- Use virtual router SystemVM for isolation
- Local Primary Storage
- Admin manually configures shares to appear as local folder
- NFS Secondary storage via Windows Server 2012
- Windows Server 2012 exposes share as NFS and SMB
Problem Areas
Lack of detail for Service Contract parameters
-
- The meaning of parameters in Command objects not clear. E.g. Volume objects in CreateCommand
- If volumes keyed by UUID, does the plugin need to persist the volume name?
- If UUIDs are arbitrary, can they include the volume file extension?
- Can the volume path include the file name?
NFS configuration on Windows Server
-
- Need technical assistance, as XenServer SSVM not able to mount NFS folder shared by a Windows Server 2012. Work around is manually mirroring templates on share mounted on Hyper-V.
Future
- WMI expertise
- Examples from OpenStack driver not in depth enough
- Java / WMI interop
- Recommendations for avoiding calling WMI through Python welcome. Calling scripts problematic if it turns out that they freeze.
Road Map
- Provide Windows Service for connected agent
- Windows Service is equivalent to Linux daemons.
- Integrate with Javelin storage model
- Make WMI access more robust.
- Access WMI directly from Plugin to avoid script maintenance.
- Support basic networking
- Support broader set of CloudStack commands
Background
Original Feature Spec