You can change the systemvm.iso. Some configurations will not work on
template because the ACS will override them with the iso configurations;
one example is the rsyslog.conf.
When configuring RSyslog in the SystemVM iso you can extract the
cloud-scripts.tgz and find the /etc/rsyslog.conf file. Ho
Well, quite easy my dear Watson... ;)
First, download the current system VM template that you are using. Then,
you can execute this template in a player such as VMware player or
Virtualbox. You have to access the VM, log into it (roor/password).
Afterward, you can install and configure whateve
Hi. We customized template for VR in the past and use it. But we use big
basic zone, so our VR is a singleton.
>From the other hand you can do ansible-based scenario since VR is
ssh-accesible from the host where it runs with the key.
9 окт. 2017 г. 3:46 ПП пользователь "Remi Bergsma" <
rberg...@s
Hi,
For your information: This how we implemented the VPC syslog server feature:
https://github.com/MissionCriticalCloud/cosmic/pull/418
You don’t need to alter the template, it can be handled in the python code on
the router itself.
However, I’m quite sure the patch doesn’t apply to CloudStack
Yes, this is what we need! :)
But... how can i do it?? :DDD
On Mon, Oct 9, 2017 at 3:32 PM, Rafael Weingärtner <
raf...@autonomiccs.com.br> wrote:
> Yes it is possible.
>
> We already did that, we direct all the logs to a remote log repository,
> and then using Graylog we present the information
Yes it is possible.
We already did that, we direct all the logs to a remote log repository,
and then using Graylog we present the information that is aggregated.
On 10/9/2017 10:30 AM, Alessandro Caviglione wrote:
Hi,
I'm replying because I'm already interested in this topic.
In fact, we'd li
Hi,
I'm replying because I'm already interested in this topic.
In fact, we'd like to monitor VR and collect logs with rsyslog.
So, is it possible to modify the template image to configure an rsyslog and
snmp to allow monitoring of all new deployed VR?
Thank you.
On Wed, Oct 4, 2017 at 5:10 PM, Da
Hi Alexander,
As you point out the attack surface of the VRs have been minimised and the
system VMs overall hardened.
You have two issues with updating the software on the VRs – an update has the
potential to break VR services (or agent services on SSVM/CPVM) as you already
mentioned, in addi
