Actually say what a test bed is. - #1390
Open
ximon18 wants to merge 3 commits into
Open
Conversation
Update the test bed documentation to actually say what a test bed is in high level terms before diving in to the technical details.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the test bed documentation to actually say what a test bed is in high level terms before diving in to the technical details. I made this PR because when I went to read the test bed documentation I felt that it didn't actually tell me early enough what it is about but rather dives straight into technical details, and I missed a higher level introduction to what a test bed actually is.
I also replaced references to Test Environment as I feel that term is misleading. The page describes how to run a test bed which is not required to setup a test environment that includes Krill, you can run Krill safely as the docs say by using it with a public test bed such as we offer or equivalent test modes offered by RIRs (which I assume exist but don't recall if that's really the case, and thus didn't mention in my doc update)
This PR also fixes the link to the public test bed as I discovered it results in a HTTP 404 error!
As I've been busy with DNS for a while and not with RPKI, please check that I haven't said anything factually incorrect in this PR.