Hello guys,
Thanks, Felipe Rossi for the reply, operators are a vital part of the
community and your opinions are of the greatest importance to the project's
advancement.
I already did a lot of tests with the patch and I think we are in a good
way to place it. I am +1 on it.
Regarding Wei's
Hi,
It seems not supported for now. Each ACL rule can have only 1 cidr, which
is the source cidr for Ingress rules, and destination cidr for Egress rules.
Can you log an issue or a feature request on github ?
-Wei
On Fri, 28 Apr 2023 at 09:24, Lokeswaran T wrote:
> Hi All,
>
> Here is my
Hi Joao,
Thanks for bringing this to our attention.
I am +1 with log4j 2.x. It is not urgent to me, as we are currently using
reload4j which is still well maintained:
https://mvnrepository.com/artifact/ch.qos.reload4j/reload4j
My concern is, you have made a huge amount of rename of variables,
hey Loges,
Why would you create a port forwarding rule to then disallow it?
I am not sure but I think the rule makes the iptables rules be set as well.
On Fri, Apr 28, 2023 at 9:24 AM Lokeswaran T wrote:
> Hi All,
>
> Here is my scenario.
>
> I have created a VPC then create a new ACL list name
Hi Pierre,
In the past we try a similar solution than you to increase the
realiability of storages using ZFS (in our case was ubuntu). ZFS borns
to be safe, so when you write a block the system don't write other
block until this block confirms that is ok, so it slow.
In our case, we can
Hello everyone,
This upgrade is fundamental, because log4j is deprecated, not possible to
make new updates/upgrades.
with log4j2 we can expand, receive new upgrades/updates, with maintenance
of a secure environment and evolution.
the importance of this is not questionable.
Att / Regards
In PR #7131 (https://github.com/apache/cloudstack/pull/7131) I have
proposed to normalize ACS's loggers, and more importantly, upgrade the
library log4j to log4j2 version 2.19.
Log4j2 has a lot of features that could offer benefits to ACS:
* Async Loggers - performance similar to logging
Thank you so much Bryan! It worked!
I would like to comment on two things.
The migration I was trying, using web gui options and the secondary storage
as intermediate, probably was failing because of two timeout parameters.
kvm.storage.offline.migration.wait: 28800
Hello All
Kubernetes cluster is stuck in the 'Starting' state, and gets error state
after some time even though VM's, LB, Firewall Rules are been created
properly.
cloudstack version: 4.18.0
kubernetes version : Kubernetes 1.23.3
Any help would be really appreciated.
Regards,
S Kumar
Hi all,
We're working on upgrading our storage solution to a proper network
attached storage.
Before this, we had an NFS share on some mounted disks on the management
server. Our new setup is a NAS running TrueNAS (zfs) with 64 GB ram and
8x8TB, 7200 rpm hard disks mounted to cloudstack over NFS.
Hi All,
Here is my scenario.
I have created a VPC then create a new ACL list name my-ACL and added the
below rules.
*For Egress:*
ALL Egress allow
*For Ingress:*
CIDR: 0.0.0.0/0
Protocol: TCP
>From Port: 3389
To Port: 3389
Then I created two Windows VMs under this new network. Then I
11 matches
Mail list logo