Skip to content

docs: add NMS setup workflow guide #37

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

Heiliger4
Copy link

Summary

Test Plan

Additional Information

  • This change is backwards-breaking

Security Considerations

Copy link
Collaborator

@lucaaamaral lucaaamaral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great and I thank you for your contribution. I left a few comments for you to take a look at, please consider them.

Also, consider separating the deployment of the two components in readmes/deployment/nms_docker.md and readmes/deplyment/orc8r_docker.md, listing the orc8r as prerequisite of the nms.

Comment on lines 49 to 83
### Important Note on Ruby Gem Compatibility

You might encounter compatibility errors with Ruby gems during this step.
Here's a recommended fix:
- Navigate to the Fluentd Dockerfile path:

```bash
cd magma/orc8r/cloud/docker/fluentd
```
- Modify the Dockerfile from:

```dockerfile
FROM fluent/fluentd:v1.14.6-debian-1.0
USER root
RUN gem install \
elasticsearch:7.13.0 \
fluent-plugin-elasticsearch:5.2.1 \
fluent-plugin-multi-format-parser:1.0.0 \
--no-document
USER fluent
```

- To this updated version:

```dockerfile
FROM fluent/fluentd:v1.14.6-debian-1.0
USER root
RUN gem install rubygems-update -v 3.2.33 --no-document && \
update_rubygems && \
gem install multi_json -v 1.15.0 --no-document && \
gem install elasticsearch -v 7.13.0 --no-document && \
gem install fluent-plugin-elasticsearch -v 5.2.1 --no-document && \
gem install fluent-plugin-multi-format-parser -v 1.0.0 --no-document
USER fluent
```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not interesting to add in the documentation.
The PR magma/magma#15699 solves this issue and is waiting to be merged.

Comment on lines 92 to 94
**Image 1: Successful Orc8r build output**
![Orc8r build output](/readmes/assets/nms/setupguide/1.png)
*Caption: Terminal output confirming the successful build of Orc8r Docker artifacts.*
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the output is textual, prefer using a code box like this.
You can add multiple lines inside it.
And it is easier to maintain in the future, as git is not very efficient with binary files such as images.

Comment on lines 14 to 44
## Step 1: Fork and Clone the Repository

The first step is straightforward but essential.
You should have already forked the Magma repository to your own GitHub account. For example:
```bash
https://github.com/username/magma.git
```

Now, clone your fork locally:

```bash
git clone https://github.com/username/magma.git
cd magma
```

## Step 2: Keep Your Fork Updated

To pull in the latest changes from the official Magma repo, add the main repository as an upstream remote:

```bash
git remote add upstream https://github.com/magma/magma.git
```

Verify your remotes:

```bash
git remote -v
```

This setup helps you sync your fork with the original repository regularly.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this is the official documentation, do you think this is necessary?

@lucaaamaral
Copy link
Collaborator

Don't forget to update the docusaurus/sidebars.json. If you need help, I can assist you in this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants