Re: [ovirt-devel] Engine High Availability

It seems one engine has limitation such as not supporting over thousands or ten thousands of hosts. I heard that openstack supports unlimited(?) hosts with engine clustering similar to active-active ha. So, I thought that if active-active ha is supported, much more hosts are supported with one

Re: [ovirt-devel] Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?

On Fri, Mar 4, 2016 at 1:24 PM, Oved Ourfali wrote: > I'd open it by default, if the user asks to configure the firewall. > We ask that on host bootstrapping, so one can choose not to let us configure > the firewall if he controls his own firewall configuration. True - we

Re: [ovirt-devel] Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?

On Fri, Mar 4, 2016 at 1:02 PM, Fabian Deutsch wrote: > Btw. This question is now asked for Node, but it also affects other > hosts which are running Cockpit. > > You can add a line with the cockpit firewall port to the sql script which defines the ports to be opened in

Re: [ovirt-devel] Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?

I'd open it by default, if the user asks to configure the firewall. We ask that on host bootstrapping, so one can choose not to let us configure the firewall if he controls his own firewall configuration. On Mar 4, 2016 14:02, "Fabian Deutsch" wrote: > Btw. This question is

[ovirt-devel] Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?

Hey, Node Next will ship Cockpit by default. When the host is getting installed, Cockpit can be reached by default over it's port 9090/tcp. But after the host was added to Engine, Engine/vdsm is setting up it's own iptables rules which then prevent further access to Cockpit. How do we want

Re: [ovirt-devel] Engine High Availability

Yaniv, Could you a little bit more elaborate what you are working on for engine scailability? I thought that active-active ha is the only way for that. Sunny 2016년 3월 4일 금요일, Yaniv Kaul님이 작성한 메시지: > > > On Fri, Mar 4, 2016 at 10:45 AM, Sunny Shin

Re: [ovirt-devel] Engine High Availability

On Fri, Mar 4, 2016 at 10:45 AM, Sunny Shin wrote: > Hi Yaniv, > > Is there a plan to implement active-active HA in the near future? Is there > any progress on it since the discussion in August 2013? > No, not at the moment. We feel that Self-Hosted Engine (SHE) is a

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

- Original Message - > From: "Nir Soffer" > To: "Sandro Bonazzola" , "Francesco Romani" > , "Dan Kenigsberg" > , "Yaniv Bronheim" > Cc: "devel" > Sent: Friday, March

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

On Fri, Mar 4, 2016 at 10:29 AM, Sandro Bonazzola wrote: > Hi, > I think I already raised the issue several times, but let me raise this > again. > VDSM building / automated versioning is badly broken. > Currently, 3.6 snapshot is building: >

Re: [ovirt-devel] Engine High Availability

Hi Yaniv, Is there a plan to implement active-active HA in the near future? Is there any progress on it since the discussion in August 2013? Sunny 2016-03-04 17:38 GMT+09:00 Yaniv Kaul : > > > On Fri, Mar 4, 2016 at 2:03 AM, Sunny Shin wrote: > >> Hi

Re: [ovirt-devel] Engine High Availability

On Fri, Mar 4, 2016 at 2:03 AM, Sunny Shin wrote: > Hi All, > > In the new architecture page ( > http://www.ovirt.org/documentation/architecture/architecture/), overall > architecture picture shows that engine supports active-active high > availability. > This is