Github user ramkatru commented on the issue:
https://github.com/apache/cloudstack/pull/1868
tag:mergeready
---
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,
Github user cloudmonger commented on the issue:
https://github.com/apache/cloudstack/pull/1868
### ACS CI BVT Run
**Sumarry:**
Build Number 448
Hypervisor xenserver
NetworkType Advanced
Passed=104
Failed=1
Skipped=7
_Link to logs Folder
Github user sateesh-chodapuneedi commented on the issue:
https://github.com/apache/cloudstack/pull/1868
The point of specifying a host is in deploy request itself means
inclination towards using that host for instance. Hence I think default value
should be false.
While global
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1868
Trillian test result (tid-942)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 38934 seconds
Marvin logs:
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has
been kicked to run smoke tests
---
If your project is set up for it, you can reply to this email and have your
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@blueorangutan test
---
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
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1868
Packaging result: âcentos6 âcentos7 âdebian. JID-579
---
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
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@blueorangutan package
---
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
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep
you posted as I make progress.
---
If your project is set up for it, you can reply to this email and have your
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@ustcweizhou I think default value should be false. As it tells the user to
make informed decision instead of misleading according to original purpose of
parameter. @sateesh-chodapuneedi
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@anshul1886 good, I will test it.
Could you please change the default value to true ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@ustcweizhou Added the global setting
allow.deploy.vm.if.deploy.on.given.host.fails to control the behaviour.
---
If your project is set up for it, you can reply to this email and have
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@anshul1886
Sorry I think it would be better to add a global setting.
This is campatible with 3.X, but not with 4.X which has more users.
---
If your project is set up for it, you
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@ustcweizhou, Is it looking good to you now?
---
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
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@ustcweizhou, Actually I am restoring to old behaviour of 3.x release which
got changed to current behaviour because of bug.
---
If your project is set up for it, you can reply to this
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@anshul1886
Considering about backwards compatibility. I would like to add the global
setting, then users will have two options
(1) deploy vm fails if specified host does not have
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@ustcweizhou, In my opinion we should not do that as that way we are giving
them option of silently deploying VM on some host which he might not be aware
of. As after specifying host he is
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1868
Do we need to add a global setting to determine whether deploy to other
hosts if the specified host is out of capacity ?
---
If your project is set up for it, you can reply to this email
Github user cloudmonger commented on the issue:
https://github.com/apache/cloudstack/pull/1868
### ACS CI BVT Run
**Sumarry:**
Build Number 323
Hypervisor xenserver
NetworkType Advanced
Passed=104
Failed=0
Skipped=7
_Link to logs Folder
19 matches
Mail list logo
