You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by James Peach <ja...@me.com> on 2013/08/18 17:26:26 UTC
Re: git commit: start a stub of deployment Limiations.
Why would we document a list if missing features?
On Aug 18, 2013, at 5:17 AM, igalic@apache.org wrote:
> Updated Branches:
> refs/heads/master 5bf0ca124 -> 0689331ff
>
>
> start a stub of deployment Limiations.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/0689331f
> Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/0689331f
> Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/0689331f
>
> Branch: refs/heads/master
> Commit: 0689331ff4f938fff91c46adc29ab947eb6b4eb6
> Parents: 5bf0ca1
> Author: Igor Galić <i....@brainsware.org>
> Authored: Sun Aug 18 14:17:04 2013 +0200
> Committer: Igor Galić <i....@brainsware.org>
> Committed: Sun Aug 18 14:17:04 2013 +0200
>
> ----------------------------------------------------------------------
> doc/admin/index.en.rst | 9 +++++++++
> doc/reference/plugins/balancer.en.rst | 2 ++
> 2 files changed, 11 insertions(+)
> ----------------------------------------------------------------------
>
>
> http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0689331f/doc/admin/index.en.rst
> ----------------------------------------------------------------------
> diff --git a/doc/admin/index.en.rst b/doc/admin/index.en.rst
> index 8bf54d9..83ac896 100644
> --- a/doc/admin/index.en.rst
> +++ b/doc/admin/index.en.rst
> @@ -121,6 +121,15 @@ similar caching products.
> Traffic Server supports ICP (Internet Cache Protocol) peering.
> Hierarchical caching is described in more detail in :ref:`hierarchical-caching`.
>
> +Deployment Limitations
> +----------------------
> +
> +There's a number of deployment options that Traffic Server does not support right out
> +of the box. Such funcionality may be implemented in a plugin, but in some cases
> +Traffic Server's internal APIs or architectural restrictions won't make it easy:
> +
> +* Load Balancing - note that there is an experimental plugin for this: :ref:`balancer-plugin`.
> +
> Traffic Server Components
> =========================
>
>
> http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0689331f/doc/reference/plugins/balancer.en.rst
> ----------------------------------------------------------------------
> diff --git a/doc/reference/plugins/balancer.en.rst b/doc/reference/plugins/balancer.en.rst
> index 9d54d91..3222184 100644
> --- a/doc/reference/plugins/balancer.en.rst
> +++ b/doc/reference/plugins/balancer.en.rst
> @@ -1,3 +1,5 @@
> +.. balancer-plugin:
> +
> Balancer Plugin
> ***************
>
>
Re: git commit: start a stub of deployment Limiations.
Posted by James Peach <jp...@apache.org>.
On Aug 19, 2013, at 3:53 AM, Igor Galić <i....@brainsware.org> wrote:
>
>
> ----- Original Message -----
>> Why would we document a list if missing features?
>
> because I think it's a better than an FAQ, and it's a
> good start for scoping the project. Somethings are
> missing because we didn't get to it yet, others are
> missing because they can (or are supposed to be)
> implemented by Plugins. Yet other features are missing
> because they are not in the scope of the project.
OK, that sounds reasonable, but I still object to a "deployment limitations" section. Perhaps a better way to do this would be to have a "Load Balancing paragraph", where you mention parent caching, SRV records, plugin development, etc. The information is valuable; you should present it neutrally without the negative framing.
J
Re: git commit: start a stub of deployment Limiations.
Posted by Igor Galić <i....@brainsware.org>.
----- Original Message -----
> Why would we document a list if missing features?
because I think it's a better than an FAQ, and it's a
good start for scoping the project. Somethings are
missing because we didn't get to it yet, others are
missing because they can (or are supposed to be)
implemented by Plugins. Yet other features are missing
because they are not in the scope of the project.
That's why.
> On Aug 18, 2013, at 5:17 AM, igalic@apache.org wrote:
>
> > Updated Branches:
> > refs/heads/master 5bf0ca124 -> 0689331ff
> >
> >
> > start a stub of deployment Limiations.
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> > Commit:
> > http://git-wip-us.apache.org/repos/asf/trafficserver/commit/0689331f
> > Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/0689331f
> > Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/0689331f
> >
> > Branch: refs/heads/master
> > Commit: 0689331ff4f938fff91c46adc29ab947eb6b4eb6
> > Parents: 5bf0ca1
> > Author: Igor Galić <i....@brainsware.org>
> > Authored: Sun Aug 18 14:17:04 2013 +0200
> > Committer: Igor Galić <i....@brainsware.org>
> > Committed: Sun Aug 18 14:17:04 2013 +0200
> >
> > ----------------------------------------------------------------------
> > doc/admin/index.en.rst | 9 +++++++++
> > doc/reference/plugins/balancer.en.rst | 2 ++
> > 2 files changed, 11 insertions(+)
> > ----------------------------------------------------------------------
> >
> >
> > http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0689331f/doc/admin/index.en.rst
> > ----------------------------------------------------------------------
> > diff --git a/doc/admin/index.en.rst b/doc/admin/index.en.rst
> > index 8bf54d9..83ac896 100644
> > --- a/doc/admin/index.en.rst
> > +++ b/doc/admin/index.en.rst
> > @@ -121,6 +121,15 @@ similar caching products.
> > Traffic Server supports ICP (Internet Cache Protocol) peering.
> > Hierarchical caching is described in more detail in
> > :ref:`hierarchical-caching`.
> >
> > +Deployment Limitations
> > +----------------------
> > +
> > +There's a number of deployment options that Traffic Server does not
> > support right out
> > +of the box. Such funcionality may be implemented in a plugin, but in some
> > cases
> > +Traffic Server's internal APIs or architectural restrictions won't make it
> > easy:
> > +
> > +* Load Balancing - note that there is an experimental plugin for this:
> > :ref:`balancer-plugin`.
> > +
> > Traffic Server Components
> > =========================
> >
> >
> > http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0689331f/doc/reference/plugins/balancer.en.rst
> > ----------------------------------------------------------------------
> > diff --git a/doc/reference/plugins/balancer.en.rst
> > b/doc/reference/plugins/balancer.en.rst
> > index 9d54d91..3222184 100644
> > --- a/doc/reference/plugins/balancer.en.rst
> > +++ b/doc/reference/plugins/balancer.en.rst
> > @@ -1,3 +1,5 @@
> > +.. balancer-plugin:
> > +
> > Balancer Plugin
> > ***************
> >
> >
>
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE