docs(orc8r): Adds how-to guide for deploying orc8r with Juju

[gruyaume]

Summary

This PR contains the same code as #13008.
Adds documentation to deploy orc8r using Juju.

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[gruyaume]

This PR contains the same code as #13008. @maxhbr @voisey

[maxhbr]

just saw that the table does not seem to render correctly:

[gruyaume]

just saw that the table does not seem to render correctly:

This should be fixed now.

[github-actions]

Oops! Looks like you failed the Markdown lint check.

Howto

• Instructions on formatting your Markdown changes
• Guide to the different CI checks and resolution guidelines

♻️ Updated: ✅ The check is passing the Markdown lint check after the last commit.

[Neudrino]

Looks good in general. We should make the linters happy before merge.
FYI: https://docs.magmacore.org/docs/next/docs/docs_overview#howto

[github-actions]

Oops! Looks like you failed the DCO check. Be sure to sign all your commits.

Howto

• Magma guidelines on signing commits
• About the signoff feature
• Howto: sign-off most-recent commit
• Howto: sign-off multiple past commits
• Guide to the different CI checks and resolution guidelines

♻️ Updated: ✅ The check is passing the DCO check after the last commit.

[voisey]

Hi @gruyaume, thanks for this. It seems your last commit is missing the sign off - could you please add this and rebase while doing so? Then I think we can merge 🙂

[gruyaume]

Hi @gruyaume, thanks for this. It seems your last commit is missing the sign off - could you please add this and rebase while doing so? Then I think we can merge slightly_smiling_face

Should be fixed now, hopefully...

[maxhbr]

Sorry to be annoying, but Check Rebase is red and that prevents merge, can you please rebase ;)

[gruyaume]

Sorry to be annoying, but Check Rebase is red and that prevents merge, can you please rebase ;)

Sure I just rebased and now this PR contains 95 commits (still only my 3 files changed though). I'm not sure if this was the expected behaviour.

[sebathomas]

Normally, this shouldn't happen. Maybe you accidentally merged instead of rebasing? Why do you get the commit "Merge remote-tracking branch 'origin/dev-juju' into dev-juju"?

[gruyaume]

Normally, this shouldn't happen. Maybe you accidentally merged instead of rebasing? Why do you get the commit "Merge remote-tracking branch 'origin/dev-juju' into dev-juju"?

Yeah I managed to fix this, thank you!

[voisey]

Thanks for fixing this @gruyaume! I've set auto-merge so this will get merged once the Jenkins job passes