[Bug 683463] Review Request: trafficserver - Apache Traffic Server

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=683463

--- Comment #18 from Zhao Yongming <ming.zym at gmail.com> 2011-06-18 05:55:43 EDT ---
dwalsh: yes, all files in /etc/trafficserver should be modified by
traffic_manager.
I am a trafficserver devel, that is why I request this pkg :D
Trafficserver is a property enterprise grade system before opensource, and the
config management is one of the most powerful designs:
1, ts will backup each version of the config file, with a _XXX suffix, the
default is set to keep 3 versions for each file
2, ts config file can be changed by many ways:
   2.1, edit directly(or by any means for common config management)
   2.2, changed by traffic_manager, triggered by commands such as traffic_line
and traffic_shell
   2.3, changed by the Cluster management, with broadcast like protocol.
   2.4, changed by other config management function, such as config
upload/rollback etc.
   2.5, the remote config management interface, port 8083

there are problems when we deal with trafficserver and the modern operation
systems:
1, for security reason, traffics_manager process will drop root privileges to
nobody. and the configs is located in /etc/trafficserver, but it must be set to
nobody writable.
   this is a problem that we still have no idea how to fix in the following
release, maybe the config system will be changed to something like config
database etc.
2, many config files in /etc/trafficserver can be override by configs(ie: most
files can be refined in records.config) and environment variables, the config
may be lose the meaning.
   in the opensource release, we have dropped the most config environment
variables, and even command options etc, we make the release file directory a
httpd like layout, that is Gentoo layout for. and most config options in
records.config is a hiden options. that will prevent most confusion for common
users. that is the most things we have done to make it much easy for users to
manage the big ship( you can config 500 options in the records.config file for
now, after we have removed many functions in the past 2 years ).

for now, I don't think we have a quick solution to get all things settle. so
I'd suggest we take it and give the devel team to get it improved. these cool
features is very useful for ISP grade CDN operations, we'd like not get it
removed blindly.

hopes the information not miss-leading
many thanks for you help!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.