Github user xenserverarmy commented on the pull request:
https://github.com/apache/cloudstack/pull/970#issuecomment-151157372
@koushik-das One of the goals of a8212d9ef458dd7ac64b021e6fa33fcf64b3cce0
was to ensure that we have clarity in which hypervisor we support since Xen !=
XenServer. Reverting based on name IMO might be the simple solution, but could
ultimately cause additional confusion as we don't currently have a pure Xen
hypervisor implementation.
@wilderrodrigues @remibergsma, I didn't have s3 or swift storage to test
with at the time of my changes. Would not the better solution be to rename the
plugin s3xenserver and swiftxenserver?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
