You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Aaron Peeler (JIRA)" <ji...@apache.org> on 2013/05/07 19:27:15 UTC
[jira] [Updated] (VCL-585) Migrate time source variable to variable
table
[ https://issues.apache.org/jira/browse/VCL-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Peeler updated VCL-585:
-----------------------------
Description:
The Windows.pm had a the variable $time_source hardcoded to nist.gov or windows.com addresses.
Linux.pm update ntp.conf file
Convert code in the configure_time_synchronization to check for and use data from the variable table. If data does not exist, then use hardcoded value.
Data in the variable table can be in the format:
timesource|<FQDN of management node>
or
timesource|global
FQDN of MN - can be if a centrally managed VCL needs to have different values
Global if only using one management node, or all management nodes can use the same value.
Database and Backend completed
was:
The Windows.pm had a the variable $time_source hardcoded to nist.gov or windows.com addresses.
Convert code in the configure_time_synchronization to check for and use data from the variable table. If data does not exist, then use hardcoded value.
Data in the variable table can be in the format:
timesource|<FQDN of management node>
or
timesource|global
FQDN of MN - can be if a centrally managed VCL needs to have different values
Global if only using one management node, or all management nodes can use the same value.
> Migrate time source variable to variable table
> ----------------------------------------------
>
> Key: VCL-585
> URL: https://issues.apache.org/jira/browse/VCL-585
> Project: VCL
> Issue Type: Improvement
> Components: database, vcld (backend), web gui (frontend)
> Reporter: Aaron Peeler
> Assignee: Aaron Peeler
> Priority: Minor
> Fix For: 2.4
>
>
> The Windows.pm had a the variable $time_source hardcoded to nist.gov or windows.com addresses.
> Linux.pm update ntp.conf file
> Convert code in the configure_time_synchronization to check for and use data from the variable table. If data does not exist, then use hardcoded value.
> Data in the variable table can be in the format:
> timesource|<FQDN of management node>
> or
> timesource|global
> FQDN of MN - can be if a centrally managed VCL needs to have different values
> Global if only using one management node, or all management nodes can use the same value.
> Database and Backend completed
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira