Hi all,
I came across an interesting bug today which can result in high wait times on
System VMs & agents.
While processing a Command on system VM or an agent, even if the management
server is no longer waiting for an answer the Command still keeps on getting
processed. This can lead to
rohityadavcloud merged PR #328:
URL: https://github.com/apache/cloudstack-documentation/pull/328
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
rohityadavcloud merged PR #345:
URL: https://github.com/apache/cloudstack-documentation/pull/345
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
cleanup is initiated to
during live patching to ensure all rules
are re-applied.
- **NOTE:** In case there is an absolute need to upgrade the system VM
template due to availability of
- security patches or update in a package provided by the template, then the
old workflow of recreating
weizhouapache commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717566414
looks good
https://qa.cloudstack.cloud/builds/docs-build/pr/345/upgrading/upgrade/_sysvm_restart.html
Pearl1594 commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717533724
@blueorangutan docbuild
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
blueorangutan commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717538325
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/345.
(QA-JID 119)
--
This is an automated message from the Apache Git Service.
To respond
blueorangutan commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717534459
@Pearl1594 a Jenkins job has been kicked to build the document. I'll keep
you posted as I make progress.
--
This is an automated message from the Apache Git
blueorangutan commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717529838
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/345.
(QA-JID 118)
--
This is an automated message from the Apache Git Service.
To respond
blueorangutan commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717528450
@Pearl1594 a Jenkins job has been kicked to build the document. I'll keep
you posted as I make progress.
--
This is an automated message from the Apache Git
Pearl1594 commented on PR #345:
URL:
https://github.com/apache/cloudstack-documentation/pull/345#issuecomment-1717526822
@blueorangutan docbuild
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
Pearl1594 opened a new pull request, #345:
URL: https://github.com/apache/cloudstack-documentation/pull/345
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
pedrofurtado opened a new pull request, #328:
URL: https://github.com/apache/cloudstack-documentation/pull/328
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
rhtyd merged pull request #134:
URL: https://github.com/apache/cloudstack-documentation/pull/134
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
ACSGitBot commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637516625
Build finished. You can review it at:
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr134
Build Log Output:
No log errors found to
ACSGitBot commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637515504
Your request had been received, i'll go and build the documentation and
check the output log for errors.
This shouldn't take long.
shwstppr commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637515453
request docbuild
This is an automated message from the Apache Git Service.
To respond to the
shwstppr commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637515746
@andrijapanicsb should be okay now
This is an automated message from the Apache Git Service.
andrijapanicsb commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637492571
@shwstppr can you please rebased against 4.14 branch - as we need the fix in
4.14 Docs (and I will forward merge later to master) - thx
andrijapanicsb commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637491957
@nvazquez can we also please include the improvements around supporting
local/sharedMount points please, and also make correction/update that template
is
for a template:
After the template is registered, it is automatically available for VM
deployments.
+From CloudStack 4.14.0, system VM also support direct download templates. An
administrator can register a new system VM template as ROUTING or USER type
with the direct download flag, and it can
shwstppr commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637462649
@andrijapanicsb please check
This is an automated message from the Apache Git Service.
To
ACSGitBot commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637460039
Build finished. You can review it at:
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr134
Build Log Output:
No log errors found to
shwstppr commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637458994
request docbuild
This is an automated message from the Apache Git Service.
To respond to the
ACSGitBot commented on pull request #134:
URL:
https://github.com/apache/cloudstack-documentation/pull/134#issuecomment-637459037
Your request had been received, i'll go and build the documentation and
check the output log for errors.
This shouldn't take long.
shwstppr opened a new pull request #134:
URL: https://github.com/apache/cloudstack-documentation/pull/134
System VMs now support direct download templates.
Different direct download timeouts have been made configurable with new
global settings.
Added with
rhtyd merged pull request #270: view: added get diagnostics action for system vm
URL: https://github.com/apache/cloudstack-primate/pull/270
This is an automated message from the Apache Git Service.
To respond to the message
shwstppr commented on issue #270: view: added get diagnostics action for system
vm
URL:
https://github.com/apache/cloudstack-primate/pull/270#issuecomment-615039569
@rhtyd this can be reviewed
This is an automated message
shwstppr opened a new pull request #270: view: added get diagnostics action for
system vm
URL: https://github.com/apache/cloudstack-primate/pull/270
Fixes #201
Fixes #202
Added action for Get Diagnostics Data for system VMs, VR
![Screenshot from 2020-03-30
17-20-03
(awesome new feature imho! )...
On Wed, 29 Jan 2020, 11:56 Darrin Hüsselmann, <
darrin.husselm...@shapeblue.com> wrote:
> Hi All,
>
> There is a new feature we have been working on to minimize the effort of
> installing and managing system VM templates in Cloudstack. The wiki p
Hi All,
There is a new feature we have been working on to minimize the effort of
installing and managing system VM templates in Cloudstack. The wiki page can be
found at the link and comments are welcome:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/System+VM+Template+API
Cheers
PaulAngus merged pull request #72: add current system vm version variable (
|sysvm64-version| )
URL: https://github.com/apache/cloudstack-documentation/pull/72
This is an automated message from the Apache Git Service
ACSGitBot commented on issue #72: add current system vm version variable (
|sysvm64-version| )
URL:
https://github.com/apache/cloudstack-documentation/pull/72#issuecomment-537561258
Build finished. You can review it at:
https://acs-www.shapeblue.com/docs/pr72
Build Log Output
PaulAngus commented on issue #72: add current system vm version variable (
|sysvm64-version| )
URL:
https://github.com/apache/cloudstack-documentation/pull/72#issuecomment-537557408
request docbuild
This is an automated
ACSGitBot commented on issue #72: add current system vm version variable (
|sysvm64-version| )
URL:
https://github.com/apache/cloudstack-documentation/pull/72#issuecomment-537557449
Your request had been received, i'll go and build the documentation and
check the output log for errors
PaulAngus opened a new pull request #72: add current system vm version variable
( |sysvm64-version| )
URL: https://github.com/apache/cloudstack-documentation/pull/72
update 'update from' 4.11.x and 4.12.x pages with better template
requirement statement
dstack.apache.org>
>
>
>
>
> From: Rafael Weingärtner <rafaelweingart...@gmail.com>
> Sent: Thursday, April 5, 2018 10:43:35 PM
> To: dev
> Subject: Re: System VM Template
>
> I am using this template for system VMs:
> http:
reproduced this and will try to fix this for 4.11.1.0 milestone next week.
- Rohit
<https://cloudstack.apache.org>
From: Rafael Weingärtner <rafaelweingart...@gmail.com>
Sent: Thursday, April 5, 2018 10:43:35 PM
To: dev
Subject: Re: System VM Template
the VR is not in the proper state (because it’s stuck
> in the Starting state).
>
> The system VM template I am working with is the following:
> http://cloudstack.apt-get.eu/systemvm/4.11/
>
> In case anyone sees something, I’ve included the contents of my VR’s
> cloud.log fi
r state (because it’s stuck in
the Starting state).
The system VM template I am working with is the following:
http://cloudstack.apt-get.eu/systemvm/4.11/
In case anyone sees something, I’ve included the contents of my VR’s
cloud.log file below.
Thanks!
Thu Apr
Upgrade” column
says, “Yes”. However, when I try to initiate the upgrade, I get an error
message stating that the VR is not in the proper state (because it’s stuck in
the Starting state).
The system VM template I am working with is the following:
http://cloudstack.apt-get.eu/systemvm/4.11/
In case
Hey Mike,
This week I have been using ACS 4.12 to do some testing. VRs and system VMs
are deploying just fine with the system VM template of 4.11. Of course, by
using this template (the 4.11) I am not receiving the changes already made
to it in both 4.11 and current master branch.
During my
Hi,
I may have missed an e-mail about this recently.
Can someone provide me with the current URL I can use to download system VM
templates for 4.12?
I’ve tried 4.11 from here:
http://cloudstack.apt-get.eu/systemvm/4.11/
and master from here:
https://builds.cloudstack.org/job/build-master
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/2023
---
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 wido commented on the issue:
https://github.com/apache/cloudstack/pull/2023
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/2023
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
Github user DaanHoogland commented on the issue:
https://github.com/apache/cloudstack/pull/2023
@karuturi I think it is easiest to just reapply and not search for the
cause of an 8 month old PR resulting in conflicts. (if the original code has
the right URLS in it)
---
If your
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/2023
code LGTM. Need to check why xenserver and KVM still have wrong urls on PR
https://github.com/apache/cloudstack/pull/1582#issuecomment-288310796
---
If your project is set up for it, you can
Github user DaanHoogland commented on the issue:
https://github.com/apache/cloudstack/pull/2023
LGTM
@kishankavala did you check what went wrong with the kvm template.
@karuturi reported that and it was probably some auto-conflict-resolution.
---
If your project is set up for
GitHub user kishankavala opened a pull request:
https://github.com/apache/cloudstack/pull/2023
BUG-ID: CLOUDSTACK-9808 Added system Vm upgrade path for LXC and OVM
`mysql> select id,unique_name,name,type,url,updated,created from
vm_template where type='SYS
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1915
LGTM @karuturi this is ready for merge
Ping @abhinandanprateek in case you want to review?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
LGTM. 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
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@serbaut Can you do a force push to kick off jenkins again. I'm guessing
Jenkins just had an issue and not the PR.
---
If your project is set up for it, you can reply to this email and have
Github user serbaut commented on the issue:
https://github.com/apache/cloudstack/pull/1915
Ok. I removed it from rsyslog since it should be safe there.
---
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
Github user leprechau commented on the issue:
https://github.com/apache/cloudstack/pull/1915
We always want `compress` ... but the only time you need or want
`delaycompress` is if you can't be sure that the program writing to the log can
be successfully told to stop appending to that
Github user serbaut commented on the issue:
https://github.com/apache/cloudstack/pull/1915
Is it safe to remove delaycompress across the board, I assume it is there
for a reason?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@serbaut I agree with @ustcweizhou. Please remove delaycompress and up to
10. I'd like to get this PR in as it is the second part of the problem
resolution for my issue. After that LGTM.
Github user kiwiflyer commented on the issue:
https://github.com/apache/cloudstack/pull/1915
We pulled this in and tested it alongside
https://github.com/apache/cloudstack/pull/1954
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@serbaut maxsize is fine for me.
Could you please remove delaycompress, and increase rotate in
systemvm/patches/debian/config/etc/logrotate.d/cloud (eg from 4 to 10) ?
LTGM after
Github user serbaut commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@dmabry yes we are using redundant VPC routers.
Using `size` instead of `maxsize` would delay the rotation of logs until
they reach `size`. 10 logfiles with size 10MB could consume
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@ustcweizhou Thanks for taking the time to test as well. I confirm in our
testing over the weekend that we were able to consistently
create/destroy/expunge VMs every 2 minutes without issue.
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
I have submitted a PR against master that fixes cloud-early-config.
https://github.com/apache/cloudstack/pull/1954
---
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/1915
1. As @dmabry said, the logrotate is moved from cron.daily to cron.hourly
in isolated network VR in commit.
We should make similar change for VPC VR and VR for shared network.
```
nice explanation Will, c to the wiki and docs, i'd say
On Fri, Feb 17, 2017 at 6:06 PM, Will Stevens <williamstev...@gmail.com> wrote:
> Yes. Exactly. The "patches" don't require a new system vm template to be
> distributed, but changes to the "appliance" does re
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@serbaut Just curious, are you using VPC routers?
---
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 ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@dmabry I will test it and update you.
---
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 dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@ustcweizhou - Thanks for the +1 on cron.hourly move. From looking at the
code, it looks like non-redundant VRs are already moving to cron.hourly, but
vpcrouter isn't. In our case, we are
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1915
agree with @dmabry
logrotate need to be moved (or copied) to cron.hourly
```
diff --git a/systemvm/patches/debian/config/etc/cron.hourly/logrotate
Yes. Exactly. The "patches" don't require a new system vm template to be
distributed, but changes to the "appliance" does require a new system vm
template.
On Feb 17, 2017 12:04 PM, "David Mabry" <dma...@ena.com> wrote:
> Awesome. Thanks for the quick answ
, "williamstev...@gmail.com on behalf of Will Stevens"
<williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
So the System VM is "built" from two sources.
1)
https://github.com/apache/cloudstack/tree/master/tools/appliance/de
So the System VM is "built" from two sources.
1)
https://github.com/apache/cloudstack/tree/master/tools/appliance/definitions/systemvmtemplate
This defines what is actually built and is distributed as the SystemVM
Template. You MUST use it if you change the packages included in th
Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
Agreed with @leprechau . I don't think just changing logrotate to compress
and rotate at smaller size intervals will not completely solve our issues here.
We really need to adjust logrotate to
Hello everyone,
I’m looking at making some changes to the system vm, but I have found that
there looks like there are 2 different places in the code that “build” the
systemvm. There is there is
https://github.com/apache/cloudstack/tree/13bfdd71e6f52d2f613a802b3d16c9b40af7/systemvm/patches
Github user leprechau commented on the issue:
https://github.com/apache/cloudstack/pull/1915
We are seeing issues under heavy user interaction cycles with redundant
VRs. In testing you can reliably completely fill the `/var/log/` partition
with data primarily from `cloud.log` when
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@serbaut I agree with reducing the size.
However, I suggest to
(1) remove the delaycompress, then the files like syslog.1 or rsyslog.1
will be compressed.
(2) keep rotate ,
GitHub user serbaut opened a pull request:
https://github.com/apache/cloudstack/pull/1915
CLOUDSTACK-9746 system-vm: logrotate config causes critical failures
* rotate both daily and by size by using maxsize in stead of size
* decrease the max size to 10M and reduce the number
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
@rhtyd, in my opinion the two commits are functionally separate enough that
they should remain separate (and this might have been asked for in one of the
various previous incarnations of
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1559
Thanks @ProjectMoon can you squash your commits.
@murali-reddy @abhinandanprateek can you help review this?
---
If your project is set up for it, you can reply to this email and have your
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
Addressed the comments. For some reason the tests for VolumeDataFactoryImpl
were being skipped. Will try to see why.
---
If your project is set up for it, you can reply to this email and
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
Updated to latest 4.8. Will also address the comments too.
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1559
@ProjectMoon can you fix the conflicts, 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 this
) {
return getEndPointFromHostId(hostId);
}
}
}
+
+//Handle case where the volume is a volume of an expunging
system VM and there are
+//no other system VMs existing in the zone
Github user GabrielBrascher commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1559#discussion_r83628876
--- Diff:
engine/storage/volume/src/org/apache/cloudstack/storage/volume/VolumeDataFactoryImpl.java
---
@@ -77,22 +80,51 @@ public VolumeInfo
Github user GabrielBrascher commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1559#discussion_r83647727
--- Diff:
engine/storage/test/org/apache/cloudstack/storage/endpoint/DefaultEndPointSelectorTest.java
---
@@ -0,0 +1,167 @@
+// Licensed to
Github user GabrielBrascher commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1559#discussion_r83600411
--- Diff:
engine/storage/test/org/apache/cloudstack/storage/endpoint/DefaultEndPointSelectorTest.java
---
@@ -0,0 +1,167 @@
+// Licensed to
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
Looks like Travis worked this time.
---
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 ProjectMoon reopened a pull request:
https://github.com/apache/cloudstack/pull/1559
CLOUDSTACK-9280: System VM volumes can be expunged if no SSVM exists.
This commit adds a special SSVM endpoint which simply returns true for
all operations sent to it, without
Github user ProjectMoon closed the pull request at:
https://github.com/apache/cloudstack/pull/1559
---
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
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
The OOBM power off test keeps failing. I've run the test locally with the
simulator and it succeeds fine. Going to try to kick Travis again to see if it
works (third time's the charm?).
GitHub user ProjectMoon reopened a pull request:
https://github.com/apache/cloudstack/pull/1559
CLOUDSTACK-9280: System VM volumes can be expunged if no SSVM exists.
This commit adds a special SSVM endpoint which simply returns true for
all operations sent to it, without
Github user ProjectMoon closed the pull request at:
https://github.com/apache/cloudstack/pull/1559
---
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
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
This pull request has been updated with another commit that fixes a bug
where volumes cannot be expunged because the loading of the volume fails to
find a primary data store (despite the
That worked. Thanks!
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Wednesday, September 28, 2016 12:18 PM
To: dev@cloudstack.apache.org
Subject: Re: can I login to a system vm using virsh?
Jeroen,
You should ssh on the system vm's IP from the host
Jeroen,
You should ssh on the system vm's IP from the host it is running on, on port
3922 as described in the wiki [1].
If you still want to use virsh, ssh to the host where the system vm or user vms
are running, you can log in using:
virsh list # confirm that the vm is running on the host
If I can get a console through virsh for the 2 system vm's, where can I find a
login to use for network troubleshooting?
Jeroen Baten
Specialist ICT
T +31(0)88335 7941
M+31(0)6 4691 4649
[Description: Description: cid:image002.png@01CE9846.E058C610]
P.O. Box 177
2600 MH Delft
The Netherlands
Github user ProjectMoon commented on the issue:
https://github.com/apache/cloudstack/pull/1559
Updated to latest master.
---
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 bvbharatk commented on the issue:
https://github.com/apache/cloudstack/pull/1559
### ACS CI BVT Run
**Sumarry:**
Build Number 186
Hypervisor xenserver
NetworkType Advanced
Passed=68
Failed=5
Skipped=3
_Link to logs Folder (search
Github user bvbharatk commented on the pull request:
https://github.com/apache/cloudstack/pull/1360#issuecomment-221940475
### ACS CI BVT Run
**Sumarry:**
Build Number 58
Hypervisor xenserver
NetworkType Advanced
Passed=67
Failed=4
Skipped=3
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1360
---
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
1 - 100 of 502 matches
Mail list logo
