From users-return-7612-archive-asf-public=cust-asf.ponee.io@trafficserver.apache.org Thu Mar 14 23:07:18 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 18B64180630 for ; Fri, 15 Mar 2019 00:07:17 +0100 (CET) Received: (qmail 58724 invoked by uid 500); 14 Mar 2019 23:07:16 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 58707 invoked by uid 99); 14 Mar 2019 23:07:16 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Mar 2019 23:07:16 +0000 Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id C30FC12BC; Thu, 14 Mar 2019 23:07:14 +0000 (UTC) Received: by mail-lj1-f170.google.com with SMTP id n18so4356298ljg.11; Thu, 14 Mar 2019 16:07:14 -0700 (PDT) X-Gm-Message-State: APjAAAWLYjbWkQxI/a7nL6O19IUX89nuC7ahmb+VkvqtICA5hUZq2AcS HN7zN95jY76cdpb4gS3AbhuRLPuZp30w7XpRUnw= X-Google-Smtp-Source: APXvYqy0DLWcbxc6IS0Ml0VzWt4bJwiK6Lyx4E/loD8iw7QP8fjEkqPYQDI1d2CrNyFO6icaYdWichmJrM9lt/3eS5c= X-Received: by 2002:a2e:8694:: with SMTP id l20mr308612lji.152.1552604833601; Thu, 14 Mar 2019 16:07:13 -0700 (PDT) MIME-Version: 1.0 References: <0481811D-62DF-42C8-9CDC-CFABFA196187@apache.org> In-Reply-To: <0481811D-62DF-42C8-9CDC-CFABFA196187@apache.org> From: Masaori Koshiba Date: Fri, 15 Mar 2019 08:07:02 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PROPOSAL] YAML migration for 9.0.0 To: dev@trafficserver.apache.org Cc: Mailing-List trafficserver Content-Type: multipart/alternative; boundary="00000000000095606f058415fb09" --00000000000095606f058415fb09 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > 2) We remove the following configurations from records.config, and only > support the default config files names (e.g. ip_allow.yaml). > proxy.config.cache.storage_filename > proxy.config.cache.control.filename > proxy.config.cache.ip_allow.filename > proxy.config.cache.hosting_filename > proxy.config.cache.volume_filename > proxy.config.dns.splitdns.filename > proxy.config.log.config.filename > proxy.config.url_remap.filename Is "proxy.config.ssl.server.multicert.filename" also included? It will be ssl_multicert.yaml, I think. - Masaori On Fri, Mar 15, 2019 at 3:26 AM Leif Hedstrom wrote: > Hi all, > > As we=E2=80=99re making more progress migrating towards YAML configuratio= ns, I=E2=80=99d > like to make two proposals for v9.0.0: > > > 1) As we migrate a configuration to the new YAML format, we only support > YAML. I.e. no backwards compatibility layers. Of course, we only break > such compatibility in major versions, which is also why we want to get as > much of this in before 9.0.0 as possible. > > 2) We remove the following configurations from records.config, and only > support the default config files names (e.g. ip_allow.yaml). > > proxy.config.cache.storage_filename > proxy.config.cache.control.filename > proxy.config.cache.ip_allow.filename > proxy.config.cache.hosting_filename > proxy.config.cache.volume_filename > proxy.config.dns.splitdns.filename > proxy.config.log.config.filename > proxy.config.url_remap.filename > > > Some justifications: > > For 1; We will name the new configs .yaml, e.g. ip_allow.yaml, which > allows everyone to keep the old .config file (e.g. ip_allow.config), such > that you can downgrade the ATS binaries, and keep the configuration tree. > > For 1; A big reason for the migration to the new YAML is that we can add > new features here in a much more reasonable way. Trying to maintain both > the old and the new configuration formats puts an unreasonable burden on > development. It also makes for a less friendly UX IMO, where if you stick > to the old version of the configurations, you won=E2=80=99t be able to us= e the same > features as if you pick the YAML format. > > For 2: These configurations were just kinda useless to begin with, and > with YAML, and the organization of YAML configs into name spaces, we can > move towards a single configuration file / format approach (with #include > and config.d/ directories). These old configurations do not play well wi= th > this goal. > > > If there are concerns about any of these, please voice them here. I > imagine the most controversial is 1) above, so if you feel strongly here, > be prepared to back this with valid arguments, and development resources > :-). > > Cheers, > > =E2=80=94 Leif > > --00000000000095606f058415fb09 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2) We remove the following configurations from records.config, an= d only support the default config files names (e.g. ip_allow.yaml).
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.storage_filename
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 proxy.config.cache.control.filename
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 proxy.config.cache.ip_allow.filename
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 proxy.config.cache.hosting_filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 prox= y.config.cache.volume_filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.= dns.splitdns.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.log.confi= g.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.url_remap.filename

Is "proxy.config.ssl.server.multicert.f= ilename" also included? It will be ssl_multicert.yaml, I think.
<= div>
- Masaori

On Fri, Mar 15, 2019 at= 3:26 AM Leif Hedstrom <zwoop@apache= .org> wrote:
Hi all,

As we=E2=80=99re making more progress migrating towards YAML configurations= , I=E2=80=99d like to make two proposals for v9.0.0:


1) As we migrate a configuration to the new YAML format, we only support YA= ML. I.e. no backwards compatibility layers.=C2=A0 Of course, we only break = such compatibility in major versions, which is also why we want to get as m= uch of this in before 9.0.0 as possible.

2) We remove the following configurations from records.config, and only sup= port the default config files names (e.g. ip_allow.yaml).

=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.storage_filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.control.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.ip_allow.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.hosting_filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.cache.volume_filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.dns.splitdns.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.log.config.filename
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proxy.config.url_remap.filename


Some justifications:

For 1;=C2=A0 We will name the new configs .yaml, e.g. ip_allow.yaml, which = allows everyone to keep the old .config file (e.g. ip_allow.config), such t= hat you can downgrade the ATS binaries, and keep the configuration tree.
For 1; A big reason for the migration to the new YAML is that we can add ne= w features here in a much more reasonable way. Trying to maintain both the = old and the new configuration formats puts an unreasonable burden on develo= pment. It also makes for a less friendly UX IMO, where if you stick to the = old version of the configurations, you won=E2=80=99t be able to use the sam= e features as if you pick the YAML format.

For 2: These configurations were just kinda useless to begin with, and with= YAML, and the organization of YAML configs into name spaces, we can move t= owards a single configuration file / format approach (with #include and con= fig.d/=C2=A0 directories). These old configurations do not play well with t= his goal.


If there are concerns about any of these, please voice them here. I imagine= the most controversial is 1) above, so if you feel strongly here, be prepa= red to back this with valid arguments, and development resources :-).

Cheers,

=E2=80=94 Leif

--00000000000095606f058415fb09--