atomictore.blogg.se

Ying yang git it
Ying yang git it












ying yang git it
  1. Ying yang git it how to#
  2. Ying yang git it update#
  3. Ying yang git it code#

  • yang/experimental/odp: experimental modules intended for OpenDaylight submission.
  • yang/experimental/ietf: experimental modules intended for IETF submission.
  • yang/experimental: contains experimental YANG modules.
  • The following directories are maintained for YANG models : To Subscribe and Browse Click Here Models Directory Structure An example of such a tool is the OpenDaylight controller. As such, models available in this repository may not be accepted by tools that perform more complete semantic validation.

    Ying yang git it code#

    The minimum requirement is that the models contributed compile correctly such that pyang plugins such as the tree plugin will function correctly, and the schema tree is available for interrogation and tasks such as code generation.Īs noted above, the check scripts today depend on pyang, and, as of writing, this tool does not support validation of content such as regular expressions or XPath constraints. As can be seen from existing check scipts, all of which use pyang today, the bar is set fairly low. In general, pull requests will not be accepted without check.sh scripts being in place and a clean Github Actions CI build being achieved. Changes may be suggested during this process, so patience is requested during this process.

    Ying yang git it update#

    Subsequently, when an updated set of models needs to be released, fork, clone, update submodule, commit and submit PR, also ensuring that Github Actions are again enabled on your fork to allow pre-pull request checks.Īll Pull Requests must be reviewed and as such one of the repository's Committers must review the request prior to actually committing the request. This will take the latest commit from your repository and make it available as a submodule. Test the Github Actions CI run of your fork as well as test it by running the testall.sh script from the top level directory.Īfter you've verified that the submodule addition and module checking is working ok, submit a PR to the main repository.Multiple examples are already in place to copy and modify as required, but in general, one is present at the top-most level of each major submodule area. Note: this requires a call to a check.sh script provided by the contributors, which should be referenced from the complete_check.yml file for CI builds.Add appropriate entry to the complete_check.yml file to check your models.cd into vendor or standards directory (depending on the source of your models).

    ying yang git it

  • Add your source git repository as a submodule to your fork:.
  • Enable Github Actions on your fork in the Actions tab.
  • An example of this may be found in the BBF's submodule, and a sample invocation here.ĭirect contributions to the top level of the repository are not encouraged instead each "organization" should create a top-level folder as described above. By convention, if a submodule is used, there should also be an equivalent check.sh provided by the contributors, which should be referenced from the complete_check.yml file for CI builds. Examples of this can be see under standard directory, with the BBF and MEF submodules. Standards bodies or vendors may also provide models to the main repository via a git submodule. Multiple examples are already in place to copy and modify as required.

    ying yang git it

    Ying yang git it how to#

    Note that there are at least two different approaches to how to do Pull Requests: using a shell/commandline or using the web interface, so if you do not find what you need below, look elsewhere or ask the committers for pointers.īy convention, there should also be a check.sh script provided by the contributors, which should be referenced from the complete_check.yml file for CI builds. You can find a tutorial here for how to do push requests. All push requests must be reviewed by at least one of the repository's Committers, so when pushing a PR, please assign it to one of the committers. With this approach you pick where your models will reside in the directory hierarchy, and manage the files mainly in your own fork of the main repository, submitting a pull request when you wish to make public updated models. This is the preferred method of contribution. This repository contains a collection of YANG modules:Ĭontribution Procedures Direct Contributions














    Ying yang git it