This is the content that appears on https://github.com/rhel-labs/learn-katacoda . If you have questions, contact Scott McBrien or raise an issue here at github.
For each scenario, please do the following:
- Submit your idea: https://goo.gl/forms/Fr4Ej4cqg2xJn2Gw2
- Work on the scenario, try it out in your own environment (here are some Katacoda docs for getting started: https://katacoda.com/scenario-examples )
- When you're satisfied, send in a pull request mentioning the request you created in step (1).
- Get a review and approval from the team members
- Once your merge has been completed, validate the scenario [including running the instructions on the Katacoda provided system(s)]. https://www.katacoda.com/smcbrien (this link will change when a portal is available)
- Keep it simple.
Can this be done on a single machine? The more complex the environment, the harder it is to build and maintain. - Keep it short.
Can the target audience complete this exercise within 10-15 minutes? If no, consider splitting the exercise into multiple scenarios. - Is everything in the scenario important to the concepts covered in the scenario?
For example, one of the steps in the scenario transfers data from one place to another; it takes five minutes.
Is the scenario about data transfer?
Is this five minutes of the participants time well spent (because the time waiting for the transfer is an important part of the scenario)?
Instead, can you have the user kick-off the transfer, work on some other stuff, and come back to it in a later step?
Could you pre-populate most of the data on the target system and use rsync to reduce the transfer time?