From 5d9ebe5281674feb9228b02a717567af099d09a5 Mon Sep 17 00:00:00 2001 From: des Date: Thu, 23 Feb 2006 11:36:27 +0000 Subject: [PATCH] Thursday morning's work. git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@19 d4fa192b-c00b-0410-8231-f00ffab90ce4 --- .../en/varnish-specification/article.xml | 107 +++++++++++++++--- 1 file changed, 94 insertions(+), 13 deletions(-) diff --git a/varnish-doc/en/varnish-specification/article.xml b/varnish-doc/en/varnish-specification/article.xml index ce3fb486..7cee30f5 100644 --- a/varnish-doc/en/varnish-specification/article.xml +++ b/varnish-doc/en/varnish-specification/article.xml @@ -9,7 +9,7 @@ Varnish HTTP Accelerator Draft Specification - +
Introduction
@@ -44,9 +44,9 @@ tuning facility (split in two? does this overlap with configuration facility?)
- +
- +
General requirements
@@ -223,9 +223,9 @@
-
+ - +
Functional requirements
@@ -341,13 +341,78 @@
Management +
+ Management interface + + Varnish must provide an interface for external + management utilities. This interface must accept connections + on a Unix socket and / or a TCP socket, depending on + configuration. + + Varnish may assume that the management interface is + adequately protected by socket permissions or firewall rules, + as applicable, and that any data it receives through this + interface is valid management data from an authorized + administrator. + + Varnish may further assume that all data received + through the management interface is well-formed and + meaningful. +
+ +
+ Management library + + Varnish must be accompanied by a C library, hereafter + referred to as the management library, which provides a + reasonably high-level API to the management interface + + Varnish should be accompanied by a Perl library which + provides Perl bindings to the management library. + + Varnish may be accompanied by libraries which provide + appropriate bindings to the management library for other + programming or scripting languages. +
+ +
+ CLI management tool + + Varnish must be accompanied by a CLI management tool, + written in C, which serves as a front-end to the management + library. + + The CLI management tool must allow management commands + to be passed on the command line. + + In addition, the CLI management tool should offer an + interactive mode using libreadline, libedit or a similar + line-editing library. +
+ +
+ Web-based management tool + + Varnish should be accompanied by a web-based management + tool. This tool should have the ability to generate graphs + and histograms based on the data described in . +
+ +
+ Plugins for third-party tools + + Varnish may be accompanied by plugins for third-party + management tools such as Munin, Nagios and NAV. +
+
Configuration XXX
-
+
Logging and statistics A separate application is responsible for collecting, @@ -356,6 +421,7 @@ Varnish must provide the data necessary to compute lifetime totals and sliding averages for the following: + Total size of documents served to clients @@ -420,6 +486,7 @@ In addition, Varnish must provide the data necessary to compute the average, median and distribution for the following: + Size of documents served, per unique document @@ -504,6 +571,20 @@ configuration, serving data from the same content servers to the same set of clients. +
+ Management + + Varnish must be accompanied by a multiplexer for the + management interface which provide a single point of access to + the entire cluster for management tools such as the CLI + management tool or a web-based management interface. + + The management protocol must be designed to allow + management commands to be targeted at individual nodes. The + default behaviour must be to propagate management commands to + all nodes in the cluster. +
+
Configuration @@ -534,9 +615,9 @@ servers in the cluster.
- +
- +
Application structure
@@ -624,14 +705,14 @@ log data to the Logger.
-
+
References - - - - + + + + -- 2.39.5