On 06/17/2011 02:12 PM, Jan-Frode Myklebust wrote:
It could be nice to have a selinux boolean controlling if
traffic_manager is allowed to write to the /etc/trafficserver/filename.config
files, and maybe only allow it to write to the _$number backup-files.
That would allow us to use an external configuration manager for the
real config-files.
Also see https://issues.apache.org/jira/browse/TS-315. This would
effectively disable clustering though, not sure how things would work
without a writeable .../etc for clustering.
I think multiple domains makes sense. One for each of the traffic_cop,
traffic_manager and traffic_server. To get an idea of the role of each
of these (from the old admin manual):
traffic_server:
---------------
The traffic_server process is the transaction processing engine of
Traffic Edge. It is responsible for accepting connections,
processing protocol requests, and serving documents from the cache
or origin server.
traffic_manager:
----------------
The traffic_manager process is the command and control facility of
the Traffic Edge, responsible for launching, monitoring, and
reconfiguring the traffic_server process. The traffic_manager
process is also responsible for the Traffic Manager UI, the proxy
autoconfiguration port, the statistics interface, cluster
administration, and virtual IP failover.
The Web UI no longer exists :).
-- Leif
