Shihta closed pull request #3160: Add some steps in the CIAB README URL: https://github.com/apache/trafficcontrol/pull/3160
This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/docs/source/admin/quick_howto/ciab.rst b/docs/source/admin/quick_howto/ciab.rst index 770e4ff5c..2c14b4885 100644 --- a/docs/source/admin/quick_howto/ciab.rst +++ b/docs/source/admin/quick_howto/ciab.rst @@ -77,7 +77,15 @@ In a typical scenario, if the steps in `Building`_ have been followed, all that' .. seealso:: :ref:`tr-api` and :ref:`tm-api` -While the components may be interacted with by the host using these ports, the true operation of the CDN can only truly be seen from within the Docker network. To see the CDN in action, connect to a container within the CDN in a Box project and use cURL to request the URL ``http://video.demo1.mycdn.ciab.test`` which will be resolved by the DNS container to the IP of the Traffic Router, which will provide a ``302 FOUND`` response pointing to the Edge-Tier cache. A typical choice for this is the "enroller" service, which has a very nuanced purpose not discussed here but already has the ``curl`` command line tool installed. For a more user-friendly interface into the CDN network, see `VNC Server`_. +While the components may be interacted with by the host using these ports, the true operation of the CDN can only truly be seen from within the Docker network. + +Before you go to see the CDN in action, there is an additional action must operate on the portal: + +1. Visit your Traffic Portal and go to `CDNs / CDN-in-a-Box <https://trafficportal.infra.ciab.test/#!/cdns/2>`_ +2. Click on **Diff CDN Config Snapshot** +3. Click on **Perform Snapshot** after you checked those changes + +After that, connect to a container within the CDN in a Box project and use cURL to request the URL ``http://video.demo1.mycdn.ciab.test`` which will be resolved by the DNS container to the IP of the Traffic Router, which will provide a ``302 FOUND`` response pointing to the Edge-Tier cache. A typical choice for this is the "enroller" service, which has a very nuanced purpose not discussed here but already has the ``curl`` command line tool installed. For a more user-friendly interface into the CDN network, see `VNC Server`_. .. code-block:: shell :caption: Example Command to See the CDN in Action diff --git a/infrastructure/cdn-in-a-box/README.md b/infrastructure/cdn-in-a-box/README.md index 7a5be291c..4fc33f75d 100644 --- a/infrastructure/cdn-in-a-box/README.md +++ b/infrastructure/cdn-in-a-box/README.md @@ -46,12 +46,21 @@ directories, such that their filenames are as follows: * `traffic_ops/traffic_ops.rpm` * `traffic_portal/traffic_portal.rpm` -Finally, run the test CDN using the command: +Run the test CDN using the command: ```bash docker-compose up --build ``` +Take a CDN config snapshot after your containers are all set: + +1. Visit your Traffic Portal and go to [`https://trafficportal.infra.ciab.test/#!/cdns/2`](https://trafficportal.infra.ciab.test/#!/cdns/2) +2. Click on **Diff CDN Config Snapshot** +3. Click on **Perform Snapshot** after you checked those changes + +Your CIAB is ready and you can access the demo site now: +[`http://video.demo1.mycdn.ciab.test`](http://video.demo1.mycdn.ciab.test) + ## Components > The following assumes that the default configuration provided in > [`variables.env`](./variables.env) is used. ---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
