Hey, We're looking into implementing the VolumeReplication_V2<https://github.com/openstack/cinder-specs/blob/master/specs/liberty/replication_v2.rst> spec for our NetApp E-Series volume driver. Looking at the specification, I can foresee a problem with implementing the new API call "failover_replicated_volume(volume) " with an unmanaged replication target. I believe with a managed target we can provide it, if I'm understanding correctly that it merely requires updating the host id for the volume. Based on that, I have two questions:
1. Is it acceptable, in implementing this spec, to only provide this API for managed targets (and either throw an exception or essentially make a no-op) for an unmanaged replication target? 2. In general, if a storage backend is incapable of performing a certain operation, what is the correct way to handle it? Can the driver implement the spec at all? Should it throw a NotImplementedError? No-op? Thanks, Michael Price
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
