You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/12/28 00:36:45 UTC

[GitHub] JBevillC opened a new pull request #3169: CIAB: Fix Automatic snapshot/queue-updates on startup.

JBevillC opened a new pull request #3169: CIAB: Fix Automatic snapshot/queue-updates on startup.
URL: https://github.com/apache/trafficcontrol/pull/3169
 
 
   #### What does this PR do?
   
   CIAB: Fix Automatic Snapshot and Queue Updates upon startup.
   
   The "fixed" automatic snapshot/queue-updates procedure:
   
   1) Poll servers from traffic ops with repeated requsets to 'api/1.x/servers'
   2) Verify a minimum of servers have been enrolled.
   3) Sleep for a configurable amount of seconds
   4) Perform snapshot request via API
   5) Sleep for a configuration amount of seconds
   6) Perform queue-updates request via API
   
   Documentation has been updated to reflect this "fixed" feature.
   
   Traffic Router has been updated to enroll itself before waiting for the traffic monitor to start (chicken-egg problem)
   
   Minor fix to to-enroll.sh to clean up temporary files.
   
   #### Which TC components are affected by this PR?
   
   - [ ] Documentation
   - [ ] Grove
   - [ ] Traffic Analytics
   - [ ] Traffic Monitor
   - [ ] Traffic Ops
   - [ ] Traffic Ops ORT
   - [ ] Traffic Portal
   - [ ] Traffic Router
   - [ ] Traffic Stats
   - [ ] Traffic Vault
   - [ ] Other _________
   
   #### What is the best way to verify this PR?
   
   1) Build trafifcops-perl, trafficops, and trafficrouter containers
   
   2) Start up the stack with "docker-compose up"
   
   3) Monitor the "trafficops" container logs for the following:
   AUTO-SNAPQUEUE - Expected Servers (7): edge,mid,trafficmonitor,trafficops,trafficops-perl,trafficrouter,trafficvault
   AUTO-SNAPQUEUE - Current Servers (10): db,dns,edge,enroller,mid,trafficmonitor,trafficops,trafficportal,trafficrouter,trafficvault
   AUTO-SNAPQUEUE - Remain Servers (1): trafficops-perl
   AUTO-SNAPQUEUE - Expected Servers (7): edge,mid,trafficmonitor,trafficops,trafficops-perl,trafficrouter,trafficvault
   AUTO-SNAPQUEUE - Current Servers (11): db,dns,edge,enroller,mid,trafficmonitor,trafficops,trafficops-perl,trafficportal,trafficrouter,trafficvault
   AUTO-SNAPQUEUE - Remain Servers (0): 
   AUTO-SNAPQUEUE - All expected servers enrolled.
   AUTO-SNAPQUEUE - Do automatic snapshot...
   AUTO-SNAPQUEUE - Do queue updates...
   
   4) After queue updates has been performed it may take traffic monitor up to 30 seconds to see the new snapshot.
   
   5) Login to traffic portal and verify that a snapshot diff  has no additional changes other than the timestamp.
   
   6) The traffic router should start (ignore the SSL exception) within 15 seconds after traffic monitor has received new snapshot.
   
   7) Should be able to ping the "demo1" delivery service URL once the traffic router has started.
   
   #### Check all that apply
   
   - [ ] This PR includes tests
   - [X] This PR includes documentation updates
   - [ ] This PR includes an update to CHANGELOG.md
   - [X] This PR includes all required license headers
   - [ ] This PR includes a database migration (ensure that migration sequence is correct)
   - [ ] This PR fixes a serious security flaw. Read more: [www.apache.org/security](http://www.apache.org/security/)
   
   <!--
       Licensed to the Apache Software Foundation (ASF) under one
       or more contributor license agreements.  See the NOTICE file
       distributed with this work for additional information
       regarding copyright ownership.  The ASF licenses this file
       to you under the Apache License, Version 2.0 (the
       "License"); you may not use this file except in compliance
       with the License.  You may obtain a copy of the License at
   
         http://www.apache.org/licenses/LICENSE-2.0
   
       Unless required by applicable law or agreed to in writing,
       software distributed under the License is distributed on an
       "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
       KIND, either express or implied.  See the License for the
       specific language governing permissions and limitations
       under the License.
   -->
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services