That's true, and works well in our environment too. It's deserved to be
included in 4.9.x
在2016年07月16 04时45分, "Simon Weller"写道:
So to be clear here, there is an existing PR awaiting merge that adds KVM VM
snapshotting to ACS (including memory). It supports storage backends that
utilize
So to be clear here, there is an existing PR awaiting merge that adds KVM VM
snapshotting to ACS (including memory). It supports storage backends that
utilize QCOW2.
The PR is here: https://github.com/apache/cloudstack/pull/977
- Si
From: Haijiao <18602198..
Github user pdube commented on the issue:
https://github.com/apache/cloudstack/pull/1611
Nice. LGTM, code reviewed
---
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 wis
Github user pdube commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1611#discussion_r71037734
--- Diff: tools/marvin/marvin/deployDataCenter.py ---
@@ -224,6 +225,16 @@ def createClusters(self, clusters, zoneId, podId,
vmwareDc=None):
Github user pdube commented on the issue:
https://github.com/apache/cloudstack/pull/1609
Excellent. @leprechau were you able to test the fix?
---
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 t
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1609
### CI RESULTS
```
Tests Run: 82
Skipped: 0
Failed: 0
Errors: 3
Duration: 8h 27m 00s
```
**Summary of the problem(s):**
```
ERROR
Jainesh,
As Syed mentioned, today Xen support in CloudStack is limited to XenServer
(or more precisely XAPI, but today XAPI really is only used with
XenServer). In 2014, I put forth a proposal to rectify that [1]. That
proposal contained two steps, first we needed to clean up the use of Xen
when X
I can probably elaborate on this a bit. Currently Xen (XenServer) uses XAPI
to interface with Cloudstack. This works for the most part but we would
ideally want to use libvirt as communication interface. This will enable a
lot of nice things like being able to support disk formats other than VHD
an
All,
Since, we've no objections to the proposal and the PR proves that we have the
advantage of splitting Marvin library from the repository as its own separate
repository, I'll start a voting thread on the same next week.
Meanwhile, please do share if you see any issues with splitting the Ma
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1611
One can test deployment of a large simulator environment using this cfg
file with marvin+Simulator:
[1000.cfg.txt](https://github.com/apache/cloudstack/files/365853/1000.cfg.txt)
With
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1611
marvin: deploy clusters in separate threads
This speeds up cluster deployment by Marvin, each cluster deployment can be
executed in separate threads. This for example, allows for setting up a
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1595
@swill this is a simple UI bugfix, please consider merging for 4.9.0 rc2 as
well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1601
@swill before you cut the next RC, please include this as @glennwagner and
@PaulAngus found a blocker around addHost API without this fix. Thanks.
---
If your project is set up for it, you can re
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack-cloudmonkey/pull/13
Thanks for the fix @phillipkent somehow I forgot to merge this. Merging
this now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack-cloudmonkey/pull/13
---
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
> Op 13 juli 2016 om 18:25 schreef John Burwell :
>
>
> All,
>
> Since LTS introduces a new release stream, I would like to propose that we
> cut the first LTS quickly to verify that various aspects of the release cycle
> and version number dependent components will work properly with the new
16 matches
Mail list logo
