[GitHub] cloudstack pull request: CLOUDSTACK-8395: vmops plugin should work...
Github user xenserverarmy commented on the pull request: https://github.com/apache/cloudstack/pull/186#issuecomment-94880329 This looks solid, but I'd update line 457 to tick-quote the vmchain as you've done elsewhere --- 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. ---
[GitHub] cloudstack-docs-rn pull request: add note on XenServer: we depend ...
Github user xenserverarmy commented on the pull request:
https://github.com/apache/cloudstack-docs-rn/pull/21#issuecomment-104945193
I agree that we should add this to the 4.4 and 4.5 notes, but would suggest
an addition relating to the config-timeout. The default has changed with
XenServer version, and I don't recall it ever being 180. Text similar to the
following would alert admins to the issue of aggressive fencing with redundant
controllers.
Occasionally XenServer will determine that a storage heartbeat failure has
occurred and fence a host, or worse an entire pool. This typically occurs when
a redundant storage solution or a storage solution with redundant controllers
is used, and the failover timer used by the storage solution is longer than the
default XenServer HA timeout of 30 seconds. The value for this timeout can be
changed, but itâs important to know that simply enabling HA from within
XenCenter, or using the default form of the pool-enable-ha command will reset
the timeout to the default value. In the following example, the timeout has
been increased from the default to two minutes.
# xe pool-enable-ha heartbeat-sr-uuids={SR-UUID} ha-config:timeout=120
---
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.
---
[GitHub] cloudstack pull request: Fix/citrix resource base packages
Github user xenserverarmy commented on the pull request: https://github.com/apache/cloudstack/pull/317#issuecomment-105936788 One suggestion. In the future we may have pure Xen support, so if possible we should ensure all naming for XenServer is "XenServer" and not Xen. So please change "com.cloud.hypervisor.xenserver.resource.wrapper.xenbase" to "com.cloud.hypervisor.xenserver.resource.wrapper.xenserverbase" --- 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. ---
[GitHub] cloudstack pull request: CLOUDSTACK-8987 call s3xen/swiftxen plugi...
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. ---
[GitHub] cloudstack pull request: Rename xapi plugins for s3 and swift to m...
Github user xenserverarmy commented on the pull request: https://github.com/apache/cloudstack/pull/982#issuecomment-151967711 @remibergsma How did the tests work out? --- 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. ---
