Can we include an ORIGIN profile? Does TRAFFIC_PORTAL need a profile too? (I’ve never set it up)
—Eric > On Jun 12, 2017, at 1:14 PM, Dewayne Richardson <dewr...@gmail.com> wrote: > > Based upon the discussion around how we manage the default profiles Traffic > Ops profiles for 2.0 and 2.1, I propose we add instructions that under the > TC Website documentation "Downloads" > http://trafficcontrol.incubator.apache.org/downloads/index.html. The > profiles will be in the format that allows Traffic Ops to import and export > them, either through the UI or the API and that is the only format we > manage. > > The naming convention for the profiles (as well as the corresponding file > names) are up for discussion as well. The following naming convention > (unless a better one comes up) will be: > > *Default Profiles* > > EDGE_<ATS_VERSION>.json > MID_<ATS_VERSION>.json > TRAFFIC_MONITOR.json > TRAFFIC_ROUTER.json > TRAFFIC_STATS.json > TRAFFIC_VAULT.json > > I didn't include version numbers on the TC components because I didn't know > if that was overkill. I will move the ball forward with this ASAP if we > have enough consensus. > > Thank you, > > -Dewayne
