You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by rob05c <gi...@git.apache.org> on 2017/03/15 21:45:06 UTC

[GitHub] incubator-trafficcontrol pull request #372: Add Traffic Monitor 2.0 getting ...

GitHub user rob05c opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/372

    Add Traffic Monitor 2.0 getting its CDN from Traffic Ops

    Adds Traffic Monitor 2.0 getting the name of the CDN to monitor from
    Traffic Ops. The CDN is the CDN that this Traffic Monitor is assigned
    to in TO (known by the hostname command). If this TO hostname doesn't
    exist in Traffic Ops, an error is logged and the old traffic_ops.cfg
    cdnName value is used. If a config cdnName is set which differs from
    the TO CDN, the TO CDN is used, and a warning is logged (TO is the
    Source of Truth).
    
    This makes deployment easier and safer: Traffic Monitor deployment
    configs need only the Traffic Ops URL and login, and the Traffic Ops
    CDN will be used, so it isn't possible to accidentally deploy a
    Monitor configured to use a different CDN than is in Traffic Ops.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rob05c/incubator-trafficcontrol tm2-dynamiccdn

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/372.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #372
    
----
commit a4bb507d25a3f5da7987434e37e01649318f9e77
Author: Robert Butts <ro...@gmail.com>
Date:   2017-03-15T21:29:59Z

    Add TM2 getting CDN name from Traffic Ops
    
    Adds Traffic Monitor 2.0 getting the name of the CDN to monitor from
    Traffic Ops. The CDN is the CDN that this Traffic Monitor is assigned
    to in TO (known by the hostname command). If this TO hostname doesn't
    exist in Traffic Ops, an error is logged and the old traffic_ops.cfg
    cdnName value is used. If a config cdnName is set which differs from
    the TO CDN, the TO CDN is used, and a warning is logged (TO is the
    Source of Truth).
    
    This makes deployment easier and safer: Traffic Monitor deployment
    configs need only the Traffic Ops URL and login, and the Traffic Ops
    CDN will be used, so it isn't possible to accidentally deploy a
    Monitor configured to use a different CDN than is in Traffic Ops.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #372: Add Traffic Monitor 2.0 getting ...

Posted by dneuman64 <gi...@git.apache.org>.
Github user dneuman64 commented on a diff in the pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/372#discussion_r106654812
  
    --- Diff: traffic_monitor_golang/traffic_monitor/enum/enum.go ---
    @@ -32,6 +32,9 @@ import (
     	"strings"
     )
     
    +// TrafficMonitorType is the Traffic Ops 'type' of Traffic Monitor servers. This is case-sensitive.
    --- End diff --
    
    I think this should be a config. Someone could setup their CDN with a different type, or we could potentially use a different type in the future.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #372: Add Traffic Monitor 2.0 getting ...

Posted by dneuman64 <gi...@git.apache.org>.
Github user dneuman64 commented on a diff in the pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/372#discussion_r106654897
  
    --- Diff: traffic_monitor_golang/traffic_monitor/enum/enum.go ---
    @@ -32,6 +32,9 @@ import (
     	"strings"
     )
     
    +// TrafficMonitorType is the Traffic Ops 'type' of Traffic Monitor servers. This is case-sensitive.
    +const TrafficMonitorType = "RASCAL"
    --- End diff --
    
    I think this should be a config. Someone could setup their CDN with a different type, or we could potentially use a different type in the future.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #372: Add Traffic Monitor 2.0 getting ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-trafficcontrol/pull/372


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---