From b5b5fe731837bfcc1b3b6ba8413d92a8e576a2eb Mon Sep 17 00:00:00 2001 From: Renato Westphal Date: Tue, 7 Nov 2023 18:18:08 -0300 Subject: [PATCH] doc, docker: update links following repository migration to a new account Signed-off-by: Renato Westphal --- .github/workflows/ci.yaml | 4 ++-- INSTALL.md | 8 ++++---- README.md | 24 ++++++++++++------------ 3 files changed, 18 insertions(+), 18 deletions(-) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 35834e3d..32e2e2b9 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -66,5 +66,5 @@ jobs: password: ${{secrets.GITHUB_TOKEN}} - name: Build and push container image run: | - docker build . -f docker/Dockerfile --tag ghcr.io/rwestphal/holo:latest - docker push ghcr.io/rwestphal/holo:latest + docker build . -f docker/Dockerfile --tag ghcr.io/holo-routing/holo:latest + docker push ghcr.io/holo-routing/holo:latest diff --git a/INSTALL.md b/INSTALL.md index 01c1e2ba..0e06aaeb 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -11,7 +11,7 @@ If you don't already have Rust in your system, the best way to install it is via 2. Clone Holo's git repository ``` -$ git clone https://github.com/rwestphal/holo.git +$ git clone https://github.com/holo-routing/holo.git ``` 3. Install build dependencies: @@ -50,6 +50,6 @@ Alternatively, you can use `cargo install` to install these binaries into the `$ Here's an [example](holo-daemon/holod.toml) containing the default values. If this file doesn't exist, the default values will be used. * Running configuration: this is the normal YANG-modeled configuration that can only be changed through a northbound client -(e.g. [gRPC](https://github.com/rwestphal/holo/wiki/gRPC), -[gNMI](https://github.com/rwestphal/holo/wiki/gNMI), -[CLI](https://github.com/rwestphal/holo/wiki/CLI), etc). +(e.g. [gRPC](https://github.com/holo-routing/holo/wiki/gRPC), +[gNMI](https://github.com/holo-routing/holo/wiki/gNMI), +[CLI](https://github.com/holo-routing/holo/wiki/CLI), etc). diff --git a/README.md b/README.md index ad3a7b74..0558af9c 100644 --- a/README.md +++ b/README.md @@ -4,11 +4,11 @@ [![Discord][discord-badge]][discord-url] [mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg -[mit-url]: https://github.com/rwestphal/holo/blob/master/LICENSE -[actions-badge]: https://github.com/rwestphal/holo/workflows/CI/badge.svg -[actions-url]: https://github.com/rwestphal/holo/actions?query=workflow%3ACI+branch%3Amaster -[codecov-badge]: https://codecov.io/gh/rwestphal/holo/branch/master/graph/badge.svg?token=OMV0RMNVY8 -[codecov-url]: https://codecov.io/gh/rwestphal/holo +[mit-url]: https://github.com/holo-routing/holo/blob/master/LICENSE +[actions-badge]: https://github.com/holo-routing/holo/workflows/CI/badge.svg +[actions-url]: https://github.com/holo-routing/holo/actions?query=workflow%3ACI+branch%3Amaster +[codecov-badge]: https://codecov.io/gh/holo-routing/holo/branch/master/graph/badge.svg?token=OMV0RMNVY8 +[codecov-url]: https://codecov.io/gh/holo-routing/holo [discord-badge]: https://img.shields.io/discord/1090816494524452935.svg?logo=discord [discord-url]: https://discord.gg/deqkRvhHB9 @@ -27,7 +27,7 @@ The image below shows the different logical layers of the Holo software stack:

Items with a gray background have not been implemented yet. -For more comprehensive and detailed information, please refer to the [Architecture](https://github.com/rwestphal/holo/wiki/Architecture) page. +For more comprehensive and detailed information, please refer to the [Architecture](https://github.com/holo-routing/holo/wiki/Architecture) page. ## Features @@ -48,9 +48,9 @@ Holo was developed specifically for high-scale, automation-driven networks that require programmable configuration and monitoring using structured and modeled data. Holo natively implements standard YANG modules from IETF and supports multiple management interfaces, -including native [gRPC](https://github.com/rwestphal/holo/wiki/gRPC) and -[gNMI](https://github.com/rwestphal/holo/wiki/gNMI). Additionally, Holo -features a standalone [CLI](https://github.com/rwestphal/holo/wiki/CLI) +including native [gRPC](https://github.com/holo-routing/holo/wiki/gRPC) and +[gNMI](https://github.com/holo-routing/holo/wiki/gNMI). Additionally, Holo +features a standalone [CLI](https://github.com/holo-routing/holo/wiki/CLI) that dynamically renders commands from YANG modules and communicates with the Holo daemon through gRPC. @@ -132,7 +132,7 @@ experimentation more convenient and accessible to everyone. The easiest way to start using Holo is by using pre-built Docker containers in combination with the [containerlab](https://containerlab.dev/) software. You can find a variety of pre-configured network topologies at [this -link](https://github.com/rwestphal/containerlab-topologies). These topologies +link](https://github.com/holo-routing/containerlab-topologies). These topologies can be deployed with a single command, allowing you to test Holo in various network setups, including interoperability testing with other implementations. @@ -212,12 +212,12 @@ Holo supports the following IETF RFCs and Internet drafts: This project is licensed under the [MIT license]. -[MIT license]: https://github.com/rwestphal/holo/blob/master/LICENSE +[MIT license]: https://github.com/holo-routing/holo/blob/master/LICENSE ### Contribution We welcome any contributions, from bug reports to Pull Requests. Please refer -to our [Project Wishlist](https://github.com/users/rwestphal/projects/3) +to our [Project Wishlist](https://github.com/users/holo-routing/projects/2) for ideas on where to contribute. Unless you explicitly state otherwise, any contribution intentionally submitted