Repo lockdown (#3423)

* [RA2, RC2, RI2]: Removal of .readthedocs.yaml They seem to cause a circular reference in the documentation. Signed-off-by: Gergely Csatari <[email protected]> * [root]: Disabling pull requests Pull requests to RM, RA1, RI1, RC1, RA2, RI2 and RC2 should be opened in their respective repository and not here. Signed-off-by: Gergely Csatari <[email protected]> * [RM, RA*, RI*, RC*]: Removal the repos moved to individual repos Signed-off-by: Gergely Csatari <[email protected]> * Fixing build errors Signed-off-by: Gergely Csatari <[email protected]> --------- Signed-off-by: Gergely Csatari <[email protected]>
anuket-project · Feb 20, 2024 · 5756cf4 · 5756cf4
1 parent 8c232a2
commit 5756cf4
Show file tree

Hide file tree

Showing 388 changed files with 52 additions and 30,814 deletions.
diff --git a/.github/workflows/repo-lockdown.yml b/.github/workflows/repo-lockdown.yml
@@ -0,0 +1,24 @@
+name: 'Repo Lockdown'
+
+on:
+    pull_request_target:
+      types: opened
+      paths:
+        - doc/ref_arch/**
+        - doc/ref_cert/**
+        - doc/ref_impl/**
+        - doc/ref_model/**
+
+permissions:
+    pull-requests: write
+
+jobs:
+    action:
+        runs-on: ubuntu-latest
+        steps:
+        - uses: dessant/repo-lockdown@v4
+          with:
+                github-token: ${{ github.token }}
+                pr-comment: 'This repository does not accept pull requests, see README for details.'
+                skip-closed-pr-comment: true
+                close-pr: true
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
@@ -78,6 +78,7 @@ Issues
 Pull Requests
 -------------
 
+-  Every sub-project should hadle their own PR-s in their respective repository.
 -  Minor editorial change PRs can be raised without a corresponding
    Issue, but must be labelled as “Minor”. Otherwise, PRs must only be
    created when there is an issue present and a decision to create a PR

diff --git a/README.rst b/README.rst
@@ -1,9 +1,26 @@
-Anuket
-======
+Anuket Specifications
+=====================
 
-This repository contains specification and documentation of the
-Reference Model, Reference Architectures, Reference Implementations and
-Reference Conformance projects of `Anuket <https://anuket.io/>`__.
+This repository contains the governance and generic description of `Anuket Specifications
+<https://cntt.readthedocs.io/en/stable-orinoco//>`__.
+The actual technical specification is done in the following repositories:
+
+* Reference Model (RM): `anuket-project/RM <https://github.com/anuket-project/RM>`__
+* Reference Architecture (RA1) for OpenStack based cloud infrastructure:
+  `anuket-project/RA1 <https://github.com/anuket-project/RA1>`__
+* Reference Conformance (RC1) for RA1 based Implementations:
+  `anuket-project/RC <https://github.com/anuket-project/RC>`__
+* Reference Architecture (RA2) for Kubernetes based cloud infrastructure:
+  `anuket-project/RA2 <https://github.com/anuket-project/RA2>`__
+* Reference Conformance (RC2) for RA2 based Implementations:
+  `anuket-project/RC2 <https://github.com/anuket-project/RC2>`__
+* Reference Implementation based on RA1 specifications (RI1):
+  `anuket-project/RI1 <https://github.com/anuket-project/RI1>`__
+* Reference Implementation based on RA2 specifications (RI2):
+  `anuket-project/RI2 <https://github.com/anuket-project/RI2>`__
+
+The development of the specifications happen in the respective repository of the sub-projects. Pull requests related to
+the sub-projects should be created to the sub-project repos and not to this repo.
 
 Available Specifications
 ------------------------

diff --git a/doc/common/roadmap.rst b/doc/common/roadmap.rst
@@ -89,7 +89,11 @@ The various workstreams in the Anuket Project are:
 -  Reference Implementation (RI)
 -  Reference Conformance (RC)
 
-The workstream dependency relationship in simple terms, `Reference Conformance <../ref_cert>`__ verifies and tests the `Reference Implementation <../ref_impl>`__ which follows the requirements and architecture defined in the `Reference Architectures <../ref_arch>`__ and Reference Architecture describes the high level system components and its interactions by adhering to the requirements and expectations set by the `Reference Model <../ref_model>`__ which sets the standards for infrastructure abstraction, compliance and verification.
+The workstream dependency relationship in simple terms, Reference Conformance verifies and tests the Reference
+Implementation which follows the requirements and architecture defined in the Reference Architectures and Reference
+Architecture describes the high level system components and its interactions by adhering to the requirements and
+expectations set by the Reference Model which sets the standards for infrastructure abstraction, compliance and
+verification.
 
 For the standard release stabilisation, On each release, All documents that are related to each other will have the same **main** version number as shown in the Figure 3.
 

diff --git a/doc/ref_arch/README.rst b/doc/ref_arch/README.rst
diff --git a/doc/ref_arch/figures/ref-arch-figures.pptx b/doc/ref_arch/figures/ref-arch-figures.pptx
diff --git a/doc/ref_arch/figures/ref_arch_ra2_relationships.png b/doc/ref_arch/figures/ref_arch_ra2_relationships.png
diff --git a/doc/ref_arch/figures/ref_arch_relationships.png b/doc/ref_arch/figures/ref_arch_relationships.png
diff --git a/doc/ref_arch/index.rst b/doc/ref_arch/index.rst
diff --git a/doc/ref_arch/kubernetes/.readthedocs.yaml b/doc/ref_arch/kubernetes/.readthedocs.yaml
diff --git a/doc/ref_arch/kubernetes/README.rst b/doc/ref_arch/kubernetes/README.rst
diff --git a/doc/ref_arch/kubernetes/_static/anuket-logo.png b/doc/ref_arch/kubernetes/_static/anuket-logo.png
diff --git a/doc/ref_arch/kubernetes/_static/custom.css b/doc/ref_arch/kubernetes/_static/custom.css
diff --git a/doc/ref_arch/kubernetes/_static/favicon.ico b/doc/ref_arch/kubernetes/_static/favicon.ico
diff --git a/doc/ref_arch/kubernetes/chapters/appendix-a.rst b/doc/ref_arch/kubernetes/chapters/appendix-a.rst