11:27 p.m.
----- Original Message -----
From: "Moti Asayag" <masayag(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "Eli Mesika" <emesika(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, April 23, 2014 11:20:25 PM
Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
----- Original Message -----
> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> To: "Moti Asayag" <masayag(a)redhat.com>
> Cc: "Eli Mesika" <emesika(a)redhat.com>, devel(a)ovirt.org
> Sent: Wednesday, April 23, 2014 10:47:04 PM
> Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
>
>
>
> ----- Original Message -----
> > From: "Moti Asayag" <masayag(a)redhat.com>
> > To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > Cc: "Eli Mesika" <emesika(a)redhat.com>, devel(a)ovirt.org
> > Sent: Wednesday, April 23, 2014 10:36:54 PM
> > Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
> >
> >
> >
> > ----- Original Message -----
> > > From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > > To: "Eli Mesika" <emesika(a)redhat.com>
> > > Cc: devel(a)ovirt.org
> > > Sent: Friday, April 18, 2014 1:19:41 AM
> > > Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Eli Mesika" <emesika(a)redhat.com>
> > > > To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > > > Cc: devel(a)ovirt.org, "Barak Azulay"
<bazulay(a)redhat.com>, "Oved
> > > > Ourfalli"
> > > > <oourfali(a)redhat.com>
> > > > Sent: Friday, April 18, 2014 12:06:38 AM
> > > > Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > > > > To: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> > > > > Cc: devel(a)ovirt.org
> > > > > Sent: Thursday, April 17, 2014 10:45:40 PM
> > > > > Subject: Re: [ovirt-devel] Small reminder about 0000_config.sql
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > > From: "Yair Zaslavsky"
<yzaslavs(a)redhat.com>
> > > > > > To: devel(a)ovirt.org
> > > > > > Sent: Thursday, April 17, 2014 12:43:37 PM
> > > > > > Subject: [ovirt-devel] Small reminder about
0000_config.sql
> > > > > >
> > > > > > Hi all, and happy holidays.
> > > > > > I would like to give a small reminder about the contents
of
> > > > > > 0000_config.sql
> > > > > > -
> > > > > > We are trying to keep an alphabetical order when it comes
to the
> > > > > > option
> > > > > > names
> > > > > > (the keys).
> > > > >
> > > > > We really need to remove this mechanism of config and hold
within
> > > > > database
> > > > > only non default values.
> > > > > Default values should go into properties file or even into
code.
> > > > > We need someone to take ownership of this ask, I will be happy
to
> > > > > instruct.
> > > >
> > > > Alon, I will be glad to own that (CCing Barak & Oved) , can you
> > > > please
> > > > open
> > > > a
> > > > oVirt RFE on that ?
> > >
> > > Thanks!
> > >
> > > Done[1]
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1089093
> > >
> >
> > How would it combine with the auto-reloadable feature [1] ? (was nacked
> > ages
> > ago)
>
> Use the restapi to set non persistent configuration for subset of the keys?
>
I'm wearing the "Captain Obvious" hat for a second, just for laying more
context
to my question: If the engine-config remains as the measure for the user to
alter
configuration values, there should be a mean to reflect the changes to the
engine
without restarting the service.
How rest takes place in this scenario ? Do you imply it (rest call) should be
invoked by the engine-config ? Meaning, the engine-config will update the
configuration
file and will send a request for the engine to reload the configuration
values from
that file ?
I do not imply anything at this point, I just want to remove the defaults from vdc_options
and the duplications of sources.
But... if you asked... what I thought is to have:
engine-config --persist option=value - to database
engine-config option=value - via restapi
User who wants to set persistent and non runtime should invoke both, or we create
shortcut.
Also, there should be no requirement to support the entire configuration as non
persistent, due to the complexity of the implementation. So only selected options should
be marked for runtime change.
Another (generic) question - how does a local configuration file (vs
DB)
integrate
with HA solution for ovirt-engine ?
The configuration of non default setting will be in database, please review the bug[1].
The defaults are set within distribution, and distribution should be synced across all
nodes of cluster.
So there is no problem with high availability solution.
BTW: even with files there is no actual problem as the filesystem that holds the data can
also be on shared storage, but this is not the case.
Regards,
Alon
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1089093
> >
> > [1] www.ovirt.org/Features/ReloadableConfiguration
> >
> > > >
> > > > >
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Yair
> > > > > > _______________________________________________
> > > > > > Devel mailing list
> > > > > > Devel(a)ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > > >
> > > > > _______________________________________________
> > > > > Devel mailing list
> > > > > Devel(a)ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > >
> > > >
> > > _______________________________________________
> > > Devel mailing list
> > > Devel(a)ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> >
>