Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a second origin server to CDN in a Box #5386

Closed
wants to merge 5 commits into from

Conversation

zrhoffman
Copy link
Member

What does this PR (Pull Request) do?

This PR

  • is not related to any Issue
  • Renames the CDN in a Box origin server to origin-01
  • Adds an origin-02 server to CDN in a Box
  • Enables the multi-site origin feature for CDN in a Box's demo1 delivery service (was meant to be done in Topologies support for assigning ORG servers to Delivery Services #5164)
  • Fixes a bug where the Traffic Ops server objects for CiaB's origin server did not include an IPv6 address because the BusyBox implementation of the route command that Alpine uses by default does not include the -6 flag. Fixed by installing the actual route command.

Which Traffic Control components are affected by this PR?

  • CDN in a Box
  • Documentation
  • Traffic Ops (v1 API tests)
  • CI tests

What is the best way to verify this PR?

  • Run CDN in a Box, make sure the readiness container exits successfully
  • Build the documentation
  • Check the result of the CDN-in-a-Box CI workflow

If this is a bug fix, what versions of Traffic Control are affected?

For the origin route command fix:

  • master
  • 5.0.0 (RC5)
  • 4.1.1

The following criteria are ALL met by this PR

  • This PR includes tests
  • This PR includes documentation
  • This PR includes an update to CHANGELOG.md
  • This PR includes any and all required license headers
  • This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

@zrhoffman zrhoffman added new feature A new feature, capability or behavior documentation related to documentation cdn-in-a-box related to the Docker-based CDN-in-a-Box system labels Dec 18, 2020
@ocket8888
Copy link
Contributor

ocket8888 commented Dec 18, 2020

CDN-in-a-Box is getting pretty large... I, personally, think it ought to be kept to the absolute, simplest minimum to get a working CDN running. That was the original intention. It does support loading (somewhat) arbitrary data sets for testing purposes, but honestly I think it's high time we revisited the idea of splitting it into two. One setup for dev/demo and another for testing that can be more expansive. As a developer, I want CiaB to spin up fast and use the smallest amount of resources possible. Every new service we add impacts those two desires to some degree.

@zrhoffman
Copy link
Member Author

The origin servers run on a 26.1MB Alpine-based image. I can understand wanting to avoid adding big, bulky things to CDN in a Box, but that's not what this.

Also, servers queue for enrollment in parallel, so the additional startup time added by this PR is the time that a single POST request takes, a fraction of a second.

@zrhoffman
Copy link
Member Author

Having a second origin server in CiaB is not so important to me. PRed the bugfixes that this PR included in #5388, and closing this one.

@zrhoffman zrhoffman closed this Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cdn-in-a-box related to the Docker-based CDN-in-a-Box system documentation related to documentation new feature A new feature, capability or behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants