DaanHoogland merged PR #468:
URL: https://github.com/apache/cloudstack-documentation/pull/468
--
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: dev-unsubs
rajujith closed pull request #416: system vm destroy behaviour
URL: https://github.com/apache/cloudstack-documentation/pull/416
--
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
rajujith commented on PR #416:
URL:
https://github.com/apache/cloudstack-documentation/pull/416#issuecomment-2581800870
@DaanHoogland created
https://github.com/apache/cloudstack-documentation/pull/468
--
This is an automated message from the Apache Git Service.
To respond to the messag
rajujith opened a new pull request, #468:
URL: https://github.com/apache/cloudstack-documentation/pull/468
system vm destroy behaviour
--
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
DaanHoogland commented on PR #416:
URL:
https://github.com/apache/cloudstack-documentation/pull/416#issuecomment-2569172132
It will pull in a lot from main if I just change the target branch @rajujith
. Can you rebase it on 4.19?
This would require you to do something like
```
git
rajujith commented on PR #416:
URL:
https://github.com/apache/cloudstack-documentation/pull/416#issuecomment-2565074196
> looks good, is this only for main or can this be added to older versions
as well?
It can be added to older versions as well.
--
This is an automated message fr
DaanHoogland commented on code in PR #416:
URL:
https://github.com/apache/cloudstack-documentation/pull/416#discussion_r1890402972
##
source/adminguide/systemvm.rst:
##
@@ -17,7 +17,7 @@
CloudStack uses several types of system Instances to perform
tasks in the cloud. In gener
rajujith opened a new pull request, #416:
URL: https://github.com/apache/cloudstack-documentation/pull/416
Adding a note on how system vm expunging is handled.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
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: dev-uns
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: dev-uns
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
--
This is an automated message from the Apache Git Service.
To respond to
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 Servic
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 to
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 Servic
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 t
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 ab
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 report
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 me
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.
To
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
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 be
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 respo
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 report
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 me
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
https://github.com/apache/
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
 ?
LTGM after that
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 200M
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. Be
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&p to the wiki and docs, i'd say
On Fri, Feb 17, 2017 at 6:06 PM, Will Stevens wrote:
> Yes. Exactly. The "patches" don't require a new system vm template to be
> distributed, but changes to the "appliance" does require a new syst
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 thi
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 fea
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 using
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
b/systemvm/patches/debian/confi
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" wrote:
> Awesome. Thanks for the quick answer. That t
, "williamstev...@gmail.com on behalf of Will Stevens"
wrote:
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 distrib
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 yo
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 thi
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
repl
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 ha
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 doe
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 fe
) {
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 ge
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 feature
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 featu
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 featu
1 - 100 of 565 matches
Mail list logo
