https://github.com/sonic-net/sonic-mgmt

Configuration management examples for SONiC
https://github.com/sonic-net/sonic-mgmt

hacktoberfest sonic

Last synced: 6 months ago
JSON representation

Configuration management examples for SONiC

• Host: GitHub
• URL: https://github.com/sonic-net/sonic-mgmt
• Owner: sonic-net
• License: other
• Created: 2016-02-25T21:28:59.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2025-04-09T15:47:44.000Z (over 1 year ago)
• Last Synced: 2025-04-09T16:49:21.789Z (over 1 year ago)
• Topics: hacktoberfest, sonic
• Language: Python
• Homepage:
• Size: 90.7 MB
• Stars: 205
• Watchers: 94
• Forks: 797
• Open Issues: 1,593
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Codeowners: .github/CODEOWNERS
  • Security: SECURITY.md

Awesome Lists containing this project

README

          
# Software for Open Networking in the Cloud - SONiC

# sonic-mgmt

[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/3933/badge)](https://bestpractices.coreinfrastructure.org/projects/3933)

[![Language grade: Python](https://img.shields.io/lgtm/grade/python/g/sonic-net/sonic-mgmt.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/sonic-net/sonic-mgmt/context:python)

### Description

Management and automation code used for SONiC testbed deployment, tests and reporting.

# Contribution guide

Please read the [contributor guide](https://github.com/sonic-net/SONiC/wiki/Becoming-a-contributor) for more details on how to contribute.

All contributors must sign an [Individual Contributor License Agreement (ICLA)](https://docs.linuxfoundation.org/lfx/easycla/v2-current/contributors/individual-contributor) before contributions can be accepted. Visit [EasyCLA - Linux Foundation](https://docs.linuxfoundation.org/lfx/easycla) for more details.

### GitHub Workflow

We're following basic GitHub Flow. If you have no idea what we're talking about, check out [GitHub's official guide](https://guides.github.com/introduction/flow/). Note that merge is only performed by the repository maintainer.

Guide for performing commits:

* Isolate each commit to one component/bugfix/issue/feature

* Use a standard commit message format:

>     [component/folder touched]: Description intent of your changes

>

>     [List of changes]

>

> 	  Signed-off-by: Your Name your@email.com

For example:

>     swss-common: Stabilize the ConsumerTable

>

>     * Fixing autoreconf

>     * Fixing unit-tests by adding checkers and initialize the DB before start

>     * Adding the ability to select from multiple channels

>     * Health-Monitor - The idea of the patch is that if something went wrong with the notification channel,

>       we will have the option to know about it (Query the LLEN table length).

>

>       Signed-off-by: user@dev.null

* Each developer should fork this repository and [add the team as a Contributor](https://help.github.com/articles/adding-collaborators-to-a-personal-repository)

* Push your changes to your private fork and do "pull-request" to this repository

* Use a pull request to do code review

* Use issues to keep track of what is going on

# Documentation

For more details on each component and the directory structure, please read [docs/README.md](docs/README.md)