Re: [PROPOSAL] Replace LuaJIT configurations with YAML
+1 for replacing LuaJIT configs with YAML. On Tue, May 8, 2018 at 3:01 AM, Bryan Callwrote: > +1 > > -Bryan > > > > On May 7, 2018, at 12:47 PM, Leif Hedstrom wrote: > > > > Hi, > > > > I’d like to propose that we eliminate the existing LuaJIT configurations > with a simple YAML format. This would be the first step towards a unified > configuration format, and I think we have to admit defeat on Lua, and do > something simpler and more normal for both developers and users. > > > > There are only 2 (or 3) configurations using the LuaJIT configurations: > > > > logging.config > > sni.config > > > > > > But, also see my other proposal of killing metrics.config, which is > currently in LuaJIT as well. > > > > If we agree to this, we’ll remove LuaJIT as a first class citizen from > ATS v8.0.0. For the ts-lua plugin, we’ll continue to support this (of > course), but it will require an externally provided LuaJIT distribution. We > already have the —with-luajit configure option, and we’ll expand on that to > auto-detect system level LuaJIT availability. > > > > If there are no strong arguments against this proposal, I’d like to get > this change done for ATS v8.0.0. > > > > Thanks, > > > > — Leif > > > > -- Derek
Re: [PROPOSAL] Replace LuaJIT configurations with YAML
+1 From: Veiko Kukk <veiko.k...@gmail.com> Reply-To: "users@trafficserver.apache.org" <users@trafficserver.apache.org> Date: Tuesday, May 8, 2018 at 4:03 AM To: "users@trafficserver.apache.org" <users@trafficserver.apache.org> Subject: Re: [PROPOSAL] Replace LuaJIT configurations with YAML +1 from me too. It would be nice to have modern, easily parsable (for whatever automation) configuration file syntax. Veiko 2018-05-08 11:01 GMT+03:00 Bryan Call <bc...@apache.org<mailto:bc...@apache.org>>: +1 -Bryan > On May 7, 2018, at 12:47 PM, Leif Hedstrom > <zw...@apache.org<mailto:zw...@apache.org>> wrote: > > Hi, > > I’d like to propose that we eliminate the existing LuaJIT configurations with > a simple YAML format. This would be the first step towards a unified > configuration format, and I think we have to admit defeat on Lua, and do > something simpler and more normal for both developers and users. > > There are only 2 (or 3) configurations using the LuaJIT configurations: > > logging.config > sni.config > > > But, also see my other proposal of killing metrics.config, which is currently > in LuaJIT as well. > > If we agree to this, we’ll remove LuaJIT as a first class citizen from ATS > v8.0.0. For the ts-lua plugin, we’ll continue to support this (of course), > but it will require an externally provided LuaJIT distribution. We already > have the —with-luajit configure option, and we’ll expand on that to > auto-detect system level LuaJIT availability. > > If there are no strong arguments against this proposal, I’d like to get this > change done for ATS v8.0.0. > > Thanks, > > — Leif >
Re: [PROPOSAL] Replace LuaJIT configurations with YAML
+1 from me too. It would be nice to have modern, easily parsable (for whatever automation) configuration file syntax. Veiko 2018-05-08 11:01 GMT+03:00 Bryan Call: > +1 > > -Bryan > > > > On May 7, 2018, at 12:47 PM, Leif Hedstrom wrote: > > > > Hi, > > > > I’d like to propose that we eliminate the existing LuaJIT configurations > with a simple YAML format. This would be the first step towards a unified > configuration format, and I think we have to admit defeat on Lua, and do > something simpler and more normal for both developers and users. > > > > There are only 2 (or 3) configurations using the LuaJIT configurations: > > > > logging.config > > sni.config > > > > > > But, also see my other proposal of killing metrics.config, which is > currently in LuaJIT as well. > > > > If we agree to this, we’ll remove LuaJIT as a first class citizen from > ATS v8.0.0. For the ts-lua plugin, we’ll continue to support this (of > course), but it will require an externally provided LuaJIT distribution. We > already have the —with-luajit configure option, and we’ll expand on that to > auto-detect system level LuaJIT availability. > > > > If there are no strong arguments against this proposal, I’d like to get > this change done for ATS v8.0.0. > > > > Thanks, > > > > — Leif > > > >
Re: [PROPOSAL] Replace LuaJIT configurations with YAML
+1 -Bryan > On May 7, 2018, at 12:47 PM, Leif Hedstromwrote: > > Hi, > > I’d like to propose that we eliminate the existing LuaJIT configurations with > a simple YAML format. This would be the first step towards a unified > configuration format, and I think we have to admit defeat on Lua, and do > something simpler and more normal for both developers and users. > > There are only 2 (or 3) configurations using the LuaJIT configurations: > > logging.config > sni.config > > > But, also see my other proposal of killing metrics.config, which is currently > in LuaJIT as well. > > If we agree to this, we’ll remove LuaJIT as a first class citizen from ATS > v8.0.0. For the ts-lua plugin, we’ll continue to support this (of course), > but it will require an externally provided LuaJIT distribution. We already > have the —with-luajit configure option, and we’ll expand on that to > auto-detect system level LuaJIT availability. > > If there are no strong arguments against this proposal, I’d like to get this > change done for ATS v8.0.0. > > Thanks, > > — Leif >
Re: [PROPOSAL] Replace LuaJIT configurations with YAML
On Mon, May 7, 2018 at 5:47 AM Leif Hedstromwrote: > Hi, > > I’d like to propose that we eliminate the existing LuaJIT configurations > with a simple YAML format. This would be the first step towards a unified > configuration format, and I think we have to admit defeat on Lua, and do > something simpler and more normal for both developers and users. > +1. Keep it for plugins, (remap especially) but for config it seems overkill. > > There are only 2 (or 3) configurations using the LuaJIT configurations: > > logging.config > sni.config > > > But, also see my other proposal of killing metrics.config, which is > currently in LuaJIT as well. > > If we agree to this, we’ll remove LuaJIT as a first class citizen from ATS > v8.0.0. For the ts-lua plugin, we’ll continue to support this (of course), > but it will require an externally provided LuaJIT distribution. We already > have the —with-luajit configure option, and we’ll expand on that to > auto-detect system level LuaJIT availability. > > If there are no strong arguments against this proposal, I’d like to get > this change done for ATS v8.0.0. > > Thanks, > > — Leif > >