devs,
The console proxy has its own logger, which is actually a wrapper around
log4j. Is there a compelling reason to keep it?
Background: We are using log4j sl4j and this wrapper in our code base but
as log4j2 is the de-facto standard I would like to unify them all and
upgrade.
tnx
--
Daan
Yes, I can debug it more. I’m in the middle of some other task at the moment,
so I might not be able to get to it until later this evening. In the meanwhile,
I figured I’d send out the previous e-mail in case it might sound like
something one of our networking devs recognize. :) Thanks!
On Oct
Congrats Syed!
Thanks guys :)
On Thu, Oct 12, 2017 at 10:19 AM Nathan Johnson
wrote:
> Congrats Syed!
>
It looks like this commit broke support for Basic Zones:
a06530d (Daan: Can you look into this?)
4.10
@Override
protected boolean canHandle(NetworkOffering offering, DataCenter dc) {
// this guru handles system Direct pod based network
if (dc.getNetworkType() == NetworkType.Basic &&
isM
All,
Recently, a number of security flaws were recently found in the DNSMasq
tool. This tool is used by many systems to provide DNS and DHCP services,
including by the CloudStack System VMs.
CloudStack users can go through the following advisory to know more and how
to mitigate the issue in their
