[jira] [Commented] (TS-3192) implement proxy.config.config_dir
[
https://issues.apache.org/jira/browse/TS-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211591#comment-14211591
]
ASF subversion and git services commented on TS-3192:
-
Commit d513cf7412d20670fce512b1e910ec5aff83e13e in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=d513cf7 ]
TS-3192: implement proxy.config.config_dir
proxy.config.config_dir is supposed to nominate the configuration
directory. However, it has never been implemented making it difficult
to bootstrap a Traffic Server instance into a configuration environment
that was not compiled in.
Add the RecConfigReadConfigDir() and RecConfigReadConfigPath()
management APIs to deal with correctly allowing proxy.config.config_dir
to override the compiled in layout. Apply these everywhere that
uses sysconfdir so that we get consistent behavior.
Separate default records configuration for traffic_cop. We don't
want traffic_cop to pull in all of libmgmt, but we need the default
records values so that we can correctly process environment overrides.
Split RecordsConfig.cc into data and API components so that traffic_cop
can get the raw data. Update traffic_cop to initialize its defaults
before loading records.config.
Merge environment veriable overrides into LibRecordsConfigInit()
and make sure we always call this. This solves initializatino
problems in early startup when traffic_server needs to know
configuration paths before it can sync with traffic_manager. Without
this we can only use TS_ROOT and the compiled-in layout.
implement proxy.config.config_dir
-
Key: TS-3192
URL: https://issues.apache.org/jira/browse/TS-3192
Project: Traffic Server
Issue Type: New Feature
Components: Configuration
Reporter: James Peach
Assignee: James Peach
Fix For: 5.2.0
{{proxy.config.config_dir}} has never been implemented, but there are various
scenarios where is it useful to be able to point Traffic Server to a
non-default set of configuration files. {{TS_ROOT}} is not always sufficient
for this because the system config directory is a path relative to the prefix
which otherwise cannot be altered (even assuming you know it).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3192) implement proxy.config.config_dir
[
https://issues.apache.org/jira/browse/TS-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208322#comment-14208322
]
James Peach commented on TS-3192:
-
This is needed for the test suite, where you have a single build that you want
to run multiple instances of with different configurations. In practice, this
is also a useful deployment capability. In past lives, I've deployed httpd
using isolated configuration files and it is very helpful.
implement proxy.config.config_dir
-
Key: TS-3192
URL: https://issues.apache.org/jira/browse/TS-3192
Project: Traffic Server
Issue Type: New Feature
Components: Configuration
Reporter: James Peach
Assignee: James Peach
Fix For: 5.2.0
{{proxy.config.config_dir}} has never been implemented, but there are various
scenarios where is it useful to be able to point Traffic Server to a
non-default set of configuration files. {{TS_ROOT}} is not always sufficient
for this because the system config directory is a path relative to the prefix
which otherwise cannot be altered (even assuming you know it).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3192) implement proxy.config.config_dir
[
https://issues.apache.org/jira/browse/TS-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14207663#comment-14207663
]
Zhao Yongming commented on TS-3192:
---
that is a pending to removing feature, IMO. the origin TS is desgin to be
relocatable for the config files due to binary distribution. it may accept
records config and shell ENV settings, after the opensource, we can set the
config dir by configure options and there is no need to make things that
complex.
FYI
implement proxy.config.config_dir
-
Key: TS-3192
URL: https://issues.apache.org/jira/browse/TS-3192
Project: Traffic Server
Issue Type: New Feature
Components: Configuration
Reporter: James Peach
Assignee: James Peach
Fix For: 5.2.0
{{proxy.config.config_dir}} has never been implemented, but there are various
scenarios where is it useful to be able to point Traffic Server to a
non-default set of configuration files. {{TS_ROOT}} is not always sufficient
for this because the system config directory is a path relative to the prefix
which otherwise cannot be altered (even assuming you know it).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
