Github user marcaurele commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1768#discussion_r103394277
--- Diff: engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java
---
@@ -424,27 +421,9 @@ protected void upgrade(CloudStackVersion dbVersion
Github user DaanHoogland commented on the issue:
https://github.com/apache/cloudstack/pull/1768
[1768.network.results.txt](https://github.com/apache/cloudstack/files/805988/1768.network.results.txt)
[1768.vpc_routers.results.txt](https://github.com/apache/cloudstack/files/805989/1
Github user DaanHoogland commented on the issue:
https://github.com/apache/cloudstack/pull/1768
@rhtyd I don't see how your concern is more true for the new code by
@marcaurele then it is true for old code. cleanup is still going to be executed
after the scripts, is it? only directly
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1975
---
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
Github user karuturi closed the pull request at:
https://github.com/apache/cloudstack/pull/1977
---
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 karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1977
PR #1975 has the same fix. closing this in favour of #1975 as jenkins
already passed there.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user srinivas-gandikota commented on the issue:
https://github.com/apache/cloudstack/pull/1883
LGTM
Reviewed code -- looks good
I see even the BVTs have passed without any failures
---
If your project is set up for it, you can reply to this email and have your
repl
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1977
LGTM. This change occurs due to code around that are gets diverged in
master and 4.9 with merge of PR #1727.
---
If your project is set up for it, you can reply to this email and have your
r
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1977
Thanks for the review anshul.
---
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
FYI,
master is broken due to a merge conflict.
I created PR https://github.com/apache/cloudstack/pull/1977 to
fix the same.
Will merge it ASAP.
~ Rajani
http://cloudplatform.accelerite.com/
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1958
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
enabled and wishes so, or if the fe
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1768
@marcaurele I appreciate the cleanup, it should have been like this from
the beginning but since we've the workflow to execute all the upgrades first
and then the cleanup. In
`https://github.com/
Github user rhtyd commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1768#discussion_r103388263
--- Diff: engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java
---
@@ -424,27 +421,9 @@ protected void upgrade(CloudStackVersion dbVersion,
Cl
GitHub user karuturi opened a pull request:
https://github.com/apache/cloudstack/pull/1977
fixed the merge conflict on merging #1941
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack build-fix
Alternatively y
Github user jayapalu commented on the issue:
https://github.com/apache/cloudstack/pull/1824
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 niteshsarda closed the pull request at:
https://github.com/apache/cloudstack/pull/1972
---
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 featu
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/commit/fa85151be962824cc88776a0264e1ac6ef90560c#commitcomment-21082422
In server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java:
In server/src/com/cloud/vm/snapshot/VMSnapshotManagerIm
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1975
LGTM, found the build failure locally today. Introduced in `a2428508`.
---
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 proje
Github user nitin-maharana commented on the pull request:
https://github.com/apache/cloudstack/commit/fa85151be962824cc88776a0264e1ac6ef90560c#commitcomment-21082376
In server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java:
In server/src/com/cloud/vm/snapshot/VMSnapshotManage
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1944
Thanks @rashmidixit
@karuturi this is ready for merge, as soon as Travis passes. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1976
This is not going to fix the build issue. The issue is different. I will
open a new PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user karuturi closed the pull request at:
https://github.com/apache/cloudstack/pull/1976
---
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 karuturi opened a pull request:
https://github.com/apache/cloudstack/pull/1976
Revert "Merge pull request #1829 from syed/hvm-volume-attach-restart-fix"
This reverts commit d9bd01266ffb23f591283c058beff6e65d1cc4aa, reversing
changes made to ea7c48cf6127aeb73c1d25
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1829
Both #1829 and #1941 are merged and is causing build failures. I am
creating new PR with the revert.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user rhtyd commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1950#discussion_r103382438
--- Diff: debian/control ---
@@ -16,14 +16,15 @@ Description: A common package which contains files
which are shared by several C
Package: cloudstack
Github user rashmidixit commented on the issue:
https://github.com/apache/cloudstack/pull/1944
@rhtyd I guess this is fine for now. 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 project does not have thi
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1975
ping @karuturi
---
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 s
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/1975
Fix build failure on master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack build-failure
Alternatively you can
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1944
CLOUDSTACK-9783: Improve metrics view performance
This improves the metrics view feature by improving the rendering
performance
of metrics view tables, by re-implementing the logic at the b
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1944
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1944
@rashmidixit the current UI does not support support pluggability of
components within UI like the backend does. We can have a separate tab but not
the implementation that the current metrics view
Github user priyankparihar commented on the issue:
https://github.com/apache/cloudstack/pull/1779
>can you run internal CI and post @cloudmonger test results?
@karuturi running.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user ramkatru commented on the issue:
https://github.com/apache/cloudstack/pull/847
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, o
Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/669
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 karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1768
Actually, BVT is not going to verify this as this is db upgrade related and
travis would have tested it.
I am merging this.
---
If your project is set up for it, you can reply to this ema
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack/commit/fa85151be962824cc88776a0264e1ac6ef90560c#commitcomment-21080945
In server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java:
In server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1919
This is usefull when using VPC.
+1
---
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 fe
The cloud templates provided by Ubuntu and CentOS (Debian doesn't provide
one) can work out of the box if we support http://1692.254.169.254/ as a
metadata URL. I believe this is as simple as adding this IP to the VR (+ a
DNAT rule in the VR?) for advanced zone. For Basic Zone the default router
is
hi!
I think we should work with distro provider to have their cloud builds work
with cloudstack. Good example is CoreOS, it work out of the box from their
channel builds.
it shouldn't be too complicated to have centos, ubuntu and debian, unless
...
For our systemvm templates, can we just change t
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1257
after code changes, suresh requested for another test run on vmware.
@rhtyd @borisroman can you run vmware tests?
---
If your project is set up for it, you can reply to this email and have
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1779
@priyankparihar can you run internal CI and post @cloudmonger test results?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov can you post test results?
---
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 feat
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/815
---
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
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1302
@blueorangutan @rhtyd @borisroman vmware tests please
---
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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/843
---
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
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1241
@rhtyd @borisstoyanov can you run tests on this pr?
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1825
---
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
I like it very much!
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1873
@ustcweizhou can you review the updated code?
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1907
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1922
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1946
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1829
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1941
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1915
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1948
---
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
My stance is that the current workflow does a disservice to the user
community by letting them install / use outdated and insecure templates.
Now, let's assume download.cloud.com is gone forever. What do we tell ACS
users pre-4.11 as far as *built-in templates* go?
1. Direct them to update template
Welcome to the CloudStack Community! :)
> On Feb 24, 2017, at 9:30 AM, Nathan Johnson wrote:
>
> Vishwas Pathak wrote:
>
>> Hello CloudStack team,
>>
>> My name is Vishwas Pathak and I am working with Accelerite CloudPlatform
>> testing team. Earlier I have worked in storage systems, cloud
Agree with you.
We need to support the current working flow. And then, define the first
version that will start using the new approach.
On Mon, Feb 27, 2017 at 5:36 PM, Will Stevens wrote:
> I think we almost need a two pronged approach.
>
> 1) Get a solution in place which will enable us to doc
I think we almost need a two pronged approach.
1) Get a solution in place which will enable us to document and serve
templates for legacy systems. I will work on this.
2) Discuss and understand how we SHOULD be handling this problem in the
future and in what release we can expect it.
I think we
Github user cloudmonger commented on the issue:
https://github.com/apache/cloudstack/pull/1965
### ACS CI BVT Run
**Sumarry:**
Build Number 400
Hypervisor xenserver
NetworkType Advanced
Passed=105
Failed=0
Skipped=7
_Link to logs Folder (searc
Another thing, in my opinion, we should avoid these hashes (MD5, SHA1, and
others) where hash collisions have already been found; if we will be
working to create a new working flow for managing these system VMs
templates, I think we should instead use SHA256 or SHA512.
On Mon, Feb 27, 2017 at 4:55
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1973
@dmabry as I posted on the other PR, I only suggested `git cherry-pick`
because I thought it would preserve the commit hash. It was a misunderstanding
from me. The git hash is generate
@rafael: Yes, I think it makes sense to support sub-paths. It will make
things a lot easier to work with. The security question is an interesting
one. I am not sure I would be the best person to answer that. I would say
that we would want to have the MD5s hosted in the same repo as the mirror
l
My worry is exactly with system VMs templates.
Currently, we indicate administrators to download them from
http://cloudstack.apt-get.eu/systemvm/4.6/ [1]. However, the installation
docs do not mention the expected hashes for the file that is going to be
downloaded.
Also, I do not know the code tha
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1973
Did a git cherry-pick as suggested by @rafaelweingartner.
---
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 dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1974
Done. I'll also do a cherry pick on the other PR. Thanks for the guidance
@rafaelweingartner.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Hashes are checked (md5 IIRC) today.
But given the issues, I think the project should steer away from hosting
templates except the systemvm template.
On Mon, Feb 27, 2017 at 1:31 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> Will, I think we could support different path structure
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1974
@rafaelweingartner No problem.
---
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 a
Infra supports Ubuntu VMs apparently so you could do what you want there
https://www.apache.org/dev/services#virtual-servers
Another idea is to distribute the http server binary with ACS - the
CloudStack admin installs the http server and gives it a reachable fqdn /
ip and updates the templates ta
Will, I think we could support different path structures. This can
facilitate different deployment of mirrors based on the structure the host
has.
Could I add something else to the discussion? Have we discussed the
security impacts of setting up this mirrors approach?
I mean, if any of the mirrors
I've added another project to the list.
CLOUDSTACK-9804 : Add Cinder as a storage driver to Cloudstack
The idea is to add cinder support for managed storage. Cinder is *The*
platform for doing Software defined storage. Every vendor has plugged in
their device to Cinder. We can run Cinder standal
Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1974
@dmabry what about using `git cherry-pick` to introduce the changes that
were already merged into master in 4.9? Then, we can maintain the same commit
hash. This would facilitate trac
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1954
@rhtyd I have created PRs for 4.8 and 4.9. They are PR #1973 and PR #1974
respectively.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user dmabry opened a pull request:
https://github.com/apache/cloudstack/pull/1974
CLOUDSTACK-9795: moved logrotate from cron.daily to cron.hourly for
vpcrouter
[BACKPORT PR1954]
moved logrotate from cron.daily to cron.hourly for vpcrouter in
cloud-early-config. This
Github user mike-tutkowski commented on the issue:
https://github.com/apache/cloudstack/pull/1962
@syed Yes, I can include you as a reviewer for the relevant PR.
---
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 pro
so this is what I am looking to do. Please let me know if you have
suggestions for me or think I should be solving the problem a different way.
- We request a new Github repository from the ASF at:
'apache/cloudstack-mirror-list'
- In this repository we track a text file in the 'gh-pages' branch
GitHub user dmabry opened a pull request:
https://github.com/apache/cloudstack/pull/1973
CLOUDSTACK-9795: moved logrotate from cron.daily to cron.hourly for
vpcrouter
[BACKPORT PR1954]
moved logrotate from cron.daily to cron.hourly for vpcrouter in
cloud-early-config. This
I’m looking forward to attending. Thanks for host this, Interoute!
On 2/27/17, 5:54 AM, "Steve Roles" wrote:
Hi guys,
The next meetup is Wednesday, April 12, hosted by Interoute Prague. As
always, there will be some great speakers, the chance to meet and collaborate
with other Clo
My bad. A few lines down, this has been added recently:
this.request.setFollowRedirects(true);
On Mon, Feb 27, 2017 at 10:15 AM, Will Stevens
wrote:
> OK. Thanks for the heads up.
>
> On Feb 27, 2017 1:08 PM, "Chiradeep Vittal" wrote:
>
> > Sounds workable. The downloader code in the SSVM won'
The alternative foolproof way is to simply not provide the automatic
download.
Just document the mirror list URL where the templates can be found. I don't
know why people reject this option.
https://shankerbalan.net/blog/seed-cloudstack-templates-offline/
On Mon, Feb 27, 2017 at 10:15 AM, Will S
OK. Thanks for the heads up.
On Feb 27, 2017 1:08 PM, "Chiradeep Vittal" wrote:
> Sounds workable. The downloader code in the SSVM won't follow redirects I
> think.
> https://github.com/apache/cloudstack/blob/5511065fc20787619d9cd0444a65a3
> 155fc9c921/core/src/com/cloud/storage/template/
> Http
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1940
Trillian test result (tid-901)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30078 seconds
Marvin logs:
https://github.com/blueoranguta
Sounds workable. The downloader code in the SSVM won't follow redirects I
think.
https://github.com/apache/cloudstack/blob/5511065fc20787619d9cd0444a65a3155fc9c921/core/src/com/cloud/storage/template/HttpTemplateDownloader.java#L93
https://goo.gl/dSi0r5
Might need to add
client.setRedirectStrategy
We haven't opened a ticket yet because we don't have a strategy yet.
What do you guys think of this:
- We setup a new github repo in the 'apache' org which consists of a single
file with a list of active/supported mirrors.
- I write a small web server, distributed as a binary, which can be hosted
Github user kiwiflyer commented on the issue:
https://github.com/apache/cloudstack/pull/1941
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,
What steps are needed to set up a mirror? What does Infra need to do? Has
anybody filed a ticket with Infra?
On Sun, Feb 26, 2017 at 10:17 PM, Raja Pullela
wrote:
> Hi will,
>
> I believe, we didn’t get to close ‘getting a mirror on Apache’ because we
> needed someone on the Apache Infra side to
Paul Angus wrote:
> Hi Nathan,
>
> Ideally, if you put the template location in (or use a template defined
> in) test_data.py then the actual location can be overridden by anyone
> testing.
>
> For Trillian, we've copied all of the templates that people have define
> to a local repo and th
Github user syed closed the pull request at:
https://github.com/apache/cloudstack/pull/1962
---
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 e
Github user syed commented on the issue:
https://github.com/apache/cloudstack/pull/1962
@mike-tutkowski If you already have incorporated these changes, I'll close
this one. If possible, please add me as reviewer when you open the other PR
---
If your project is set up for it, you ca
Github user syed commented on the issue:
https://github.com/apache/cloudstack/pull/1829
@rhtyd @anshul1886 I suggest merging this first as the changes here are
very limited and tested. We can refactor the change out from #1941
---
If your project is set up for it, you can reply to
Github user syed commented on the issue:
https://github.com/apache/cloudstack/pull/1951
Thanks @rhtyd for confirming. LGTM :+1:
---
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
e
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1960#discussion_r103207344
--- Diff: .travis.yml ---
@@ -42,13 +42,18 @@ env:
smoke/test_dynamicroles
smoke/test_global_settings
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1960#discussion_r103210828
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/ha/DisableHAForClusterCmd.java
---
@@ -0,0 +1,114 @@
+// Licensed to the Apache Soft
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1960#discussion_r103213259
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/ha/EnableHAForZoneCmd.java ---
@@ -0,0 +1,115 @@
+// Licensed to the Apache Software
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1960#discussion_r103212736
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/ha/DisableHAForZoneCmd.java ---
@@ -0,0 +1,115 @@
+// Licensed to the Apache Software
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1960#discussion_r103212914
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/ha/EnableHAForClusterCmd.java
---
@@ -0,0 +1,114 @@
+// Licensed to the Apache Softw
Github user marcaurele commented on the issue:
https://github.com/apache/cloudstack/pull/1768
@rhtyd I don't see how I could write such a test case. My point is exactly
what you're saying, the upgrade would be different today for anyone who comes
from an older version, which I don't t
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1954
@rhtyd Sure, no problem. How would you like to handle the back porting?
Do you want me to open PRs against 4.8 and 4.9?
---
If your project is set up for it, you can reply to this email and ha
Hi guys,
The next meetup is Wednesday, April 12, hosted by Interoute Prague. As always,
there will be some great speakers, the chance to meet and collaborate with
other CloudStack users, and an informal gathering afterwards over a drink!
Agenda and speakers: TBC; Venue: Interoute Czech s.r.o. S
1 - 100 of 160 matches
Mail list logo
