Github user resmo commented on the pull request:
https://github.com/apache/cloudstack/pull/1248#issuecomment-165410616
@sureshanaparti Ok, I see. then I would indeed use old but suggest
`oldest` : `findExistentHypervisorHostInCluster`. Would you mind rebasing to
get a clean PR withou
Github user sureshanaparti commented on the pull request:
https://github.com/apache/cloudstack/pull/1248#issuecomment-165412102
@resmo, You mean findOldestExistentHypervisorHostInCluster. I'm OK with it.
Shall I create new PR without all these merges?
---
If your project is set u
Github user resmo commented on the pull request:
https://github.com/apache/cloudstack/pull/1248#issuecomment-165413590
@sureshanaparti that would be great. appreciate your work on vmware parts!
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user sureshanaparti commented on the pull request:
https://github.com/apache/cloudstack/pull/1248#issuecomment-165414155
@resmo Sure. I'll do that. Thanks.
---
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 pr
Github user resmo commented on the pull request:
https://github.com/apache/cloudstack/pull/1256#issuecomment-165420030
LGTM
---
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
enable
Github user kansal commented on the pull request:
https://github.com/apache/cloudstack/pull/1152#issuecomment-165426036
Have updated this PR. Instead of directly removing the secret key from
response, I have deprecated that as many regressions were using the secret key
from those APIs
Hi all,
My vote is +1 (binding) with following note:
We ought to mention on the release notes for 4.5.3 users workaround for
upgrading to 4.7.0: (0) register the 4.6 systemvm template, (1) shutdown mgmt
server once systemvm is registered and take db backups, (2) removing the
version 4.5.3 from
Github user voloshanenko commented on the pull request:
https://github.com/apache/cloudstack/pull/1230#issuecomment-165465027
Guys, i see that build hangs... Can you please re run them?
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Hi all,
After 72 hours, the vote for CloudStack 4.7.0 [1] *passes* with 5 PMC + 1
non-PMC votes.
+1 (PMC / binding)
* Wilder
* Wido
* Milamber
* Rohit
* Remi
+1 (non binding)
* Boris
0
* Abhinandan
* Dag
* Glenn
-1
Raja (has been discussed, seems local test configure issue)
Thanks to everyon
Hi all,
After 72 hours, the vote for CloudStack 4.6.2 [1] *passes* with 4 PMC + 1
non-PMC votes.
+1 (PMC / binding)
* Wilder
* Rohit
* Wido
* Milamber
+1 (non binding)
* Boris
0
none
-1
none
Thanks to everyone participating.
I will now prepare the release announcement to go out after 24 hou
Github user resmo commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1254#discussion_r47931786
--- Diff:
plugins/database/quota/src/org/apache/cloudstack/api/command/QuotaSummaryCmd.java
---
@@ -59,7 +59,7 @@ public QuotaSummaryCmd() {
publ
GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/1257
CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not
participate in load balancing.
Summary: When a new host is added to a cluster, Cloudstack doesn't create
all the po
Github user sureshanaparti commented on the pull request:
https://github.com/apache/cloudstack/pull/1248#issuecomment-165547302
@resmo Raised a clean PR: https://github.com/apache/cloudstack/pull/1257.
Shall I close this one?
---
If your project is set up for it, you can reply to
Github user agneya2001 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1254#discussion_r47990946
--- Diff:
plugins/database/quota/src/org/apache/cloudstack/api/command/QuotaSummaryCmd.java
---
@@ -59,7 +59,7 @@ public QuotaSummaryCmd() {
GitHub user nitin-maharana opened a pull request:
https://github.com/apache/cloudstack/pull/1258
CLOUDSTACK-9186: Root admin cannot see VPC created by Domain admin user
Issue:
=
Root admin cannot see LB rules and Public LB IP addresses created by
domain-admin in UI there
15 matches
Mail list logo
