Why not just assign the host a publicly accessible IP address and restrict
SSH by firewall so only the engine (and possibly you) can access through
2016-08-16 23:03 GMT+01:00 Hanson :
> Hi Guys,
> Quick question, I have my nodes on a
I've a similar setup and I use a proxy (Squid) to get out of our private
LAN, all you have to do is define a proxy in your yum configuration
(/etc/yum.conf) in case of RH/CentOS Systems.
On 08/17/2016 12:03 AM, Hanson wrote:
Quick question, I have my nodes on a
you could install Katello, register your hosts to receive updates through
Katello and configure oVirt-Katello integration. You can find more
On Wed, Aug 17, 2016 at 12:03 AM, Hanson
Quick question, I have my nodes on a bond-bridge-privateVlan setup, and
my engine on a bond-bridge-publicVlan setup for remote monitoring.
Understandably, the nodes are complaining that they are failing updates.
(They're on a private vlan, and only configured with IP's in that vlan,
Mail list logo