GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/1203
Fix vm cannot register and poweron on vcenter with vm.instancename.flag =
'true'
In my lab, I run with CloudStack 4.4 + VMware vCenter 5.5.
With vm.instancename.flag =
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/commit/23bde8ea7af70876592c87c7580eed35ef3a89f0#commitcomment-11019081
@heidsoft Running State just means the number of VM in State.Running, and
Active State includes State.Running
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/108#issuecomment-89128055
@karuturi Can you craete a new commit and fix it ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/108#issuecomment-89127744
@karuturi I'm sorry for this commit, it should be "Requires:
java-1.7.0-openjdk" . I make a mistake. :(
---
If your project is set up for it, y
Github user ghxandsky closed the pull request at:
https://github.com/apache/cloudstack/pull/129
---
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
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/129
Fix centos63 rpm packaging
Fix centos63 rpm packaging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ghxandsky/cloudstack 4.4
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/commit/f68b407283356dd57241af3679171e3e5b0fea82#commitcomment-10370666
In packaging/centos63/cloud.spec:
In packaging/centos63/cloud.spec on line 283:
The change of packaging/centos63
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/commit/f68b407283356dd57241af3679171e3e5b0fea82#commitcomment-10370653
The change of packaging/centos63/cloud.spec is repeate the new line. This
brings error when packaging.
---
If your
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/commit/b527aabfc352474541a2f6c7831b819356ec453a#commitcomment-10363120
I donot think this is good idea to backport centos7 packaging. There is no
strict testing on it.
---
If your project is
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/111#issuecomment-78234938
I have checked this issue in fedora20 & fedora21 is fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/111
CLOUDSTACK-7951: Limit amount of memory used by cloudstack-agent jsvc
According https://issues.apache.org/jira/browse/CLOUDSTACK-7951, and
https://git-wip-us.apache.org/repos/asf?p
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/108
fix yum install require java => 1.7.0 when build management agent and us...
...age rpm package
You can merge this pull request into a Git repository by running:
$ git pull ht
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/99#issuecomment-77675935
So good.
---
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
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/97#issuecomment-77382295
Yes, this fix make sure that the $vlanDev is noshutdown after adding vlan
operation. In CentOS 7, after adding vlan operation, the $vlanDev is shutdown
status. But
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/97
add ip set interface up because in CentOS 7 the interface will not auto p
When run "ip link add link $pif name $vlanDev type vlan id $vlanId >
/dev/null", the interface will no
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/88#issuecomment-76391714
@bhaisaab , 4.5 is different from master on CentOS7 packaging, and no
packages for Fedora 20 or 21.
---
If your project is set up for it, you can reply to this
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/88#issuecomment-76338402
@DaanHoogland Yes, I build rpms and install management & agent on the same
host.
---
If your project is set up for it, you can reply to this email and have
Github user ghxandsky closed the pull request at:
https://github.com/apache/cloudstack/pull/88
---
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
GitHub user ghxandsky reopened a pull request:
https://github.com/apache/cloudstack/pull/88
Add distribution fedora21 in packaging.sh and delete the agent dir in
cloud.spec
Add distribution fedora21 in packaging/package.sh, help to build rpm for
fedora21.
Fix cloud.spec for
Github user ghxandsky closed the pull request at:
https://github.com/apache/cloudstack/pull/74
---
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
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/88
Add distribution fedora21 in packaging/package.sh
Add distribution fedora21 in packaging/package.sh, help to build rpm for
fedora21.
You can merge this pull request into a Git repository by
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/commit/0c0c7dd070c146e2f55bfe6a3cebf3ced115690f#commitcomment-9892420
No code change?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user ghxandsky commented on the pull request:
https://github.com/apache/cloudstack/pull/74#issuecomment-73816188
Yes, this is good idea.
---
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
GitHub user ghxandsky opened a pull request:
https://github.com/apache/cloudstack/pull/74
Cloudstack doesn't consider storage overprovisioning factor when using t...
...hin Provisioning over ShareMountPoint with KVM.
You can merge this pull request into a Git repository by ru
24 matches
Mail list logo
