Change domain from opencord.org to lfbroadband.org
We have moved all sites from the opencord.org domain to
lfbroadband.org (except wiki/Jira, which are now hosted on Atlassian
Cloud).
Signed-off-by: Eric Ball <eball@linuxfoundation.org>
Change-Id: I9624ae92e9c193fa2d2fac9ab30ad108a812306e
diff --git a/overview/contributing.rst b/overview/contributing.rst
index 7473a61..3e8416e 100644
--- a/overview/contributing.rst
+++ b/overview/contributing.rst
@@ -58,7 +58,7 @@
4. :ref:`Commit message syntax and testing directives <pull-request--commit-message>`
5. Submitting your patch will initiate a validation
- `jenkins job <https://jenkins.opencord.org>`_.
+ `jenkins job <https://jenkins.lfbroadband.org>`_.
Wait for job completion status before proceeding.
- Job status will be sent to you asynchronously in email at job completion.
@@ -70,7 +70,7 @@
To view accumulated job status:
- - `navigate to a patch <https://gerrit.opencord.org/c/ci-management/+/34599>`_
+ - `navigate to a patch <https://gerrit.lfbroadband.org/c/ci-management/+/34599>`_
- View "Submit requirements" in the top left.
- Verified ``+1 Jenkins Technical User`` will indicate SUCCESS.
- Verified ``-1 Jenkins Technical User`` will indicate FAILURE.
@@ -79,7 +79,7 @@
un-related to a changeset you can re-trigger by commenting on the
patch with `recheck <https://docs.voltha.org/master/howto/code/pull_request.html#development-and-code-reviews>`_
- If failures persist `ask for assistance <https://wiki.opencord.org>`_ in slack or a mailing list.
+ If failures persist `ask for assistance <https://lf-broadband.atlassian.net/wiki>`_ in slack or a mailing list.
6. When patch comments are offered please make the appropriate fixes and then
amend your commit with `git commit --amend` and re-upload to gerrit with `git review`.
@@ -89,7 +89,7 @@
**All changes must acquire +2 Approval**.
- Join one of the `communication channels <https://wiki.opencord.org>`_
+ Join one of the `communication channels <https://lf-broadband.atlassian.net/wiki>`_
to request a review or to bring additional attention to your patch.
8. A patch will be ready to submit a merge request when
@@ -105,7 +105,7 @@
All of the VOLTHA components and the charts include a VERSION file that specifies
the version of the service, library, protobuf, test suite included in the repository.
-- The `VERSION <https://gerrit.opencord.org/plugins/gitiles/voltha-go/+/refs/heads/master/VERSION>`_ file can be found in a repository root directory.
+- The `VERSION <https://gerrit.lfbroadband.org/plugins/gitiles/voltha-go/+/refs/heads/master/VERSION>`_ file can be found in a repository root directory.
- One exception: maven based builds using pom.xml files.
The VERSION is in the format and follows the `SemVer principles <https://semver.org>`_
diff --git a/overview/contributing/copyright.rst b/overview/contributing/copyright.rst
index 93a8295..9473672 100644
--- a/overview/contributing/copyright.rst
+++ b/overview/contributing/copyright.rst
@@ -37,6 +37,6 @@
- `Copyright notices <https://github.com/joey-onf/copyright>`_
- `Message syntax <https://github.com/joey-onf/copyright/blob/origin/master/notice>`_
-- `ONF CLA Information <https://wiki.opencord.org>`_
+- `ONF CLA Information <https://lf-broadband.atlassian.net/wiki>`_
:doc:`Copyrights <copyright/copyright>`
diff --git a/overview/contributing/copyright/copyright.rst b/overview/contributing/copyright/copyright.rst
index 42d1938..19737f6 100644
--- a/overview/contributing/copyright/copyright.rst
+++ b/overview/contributing/copyright/copyright.rst
@@ -32,7 +32,7 @@
- `Copyright notices <https://github.com/joey-onf/copyright>`_
- `Message syntax <https://github.com/joey-onf/copyright/blob/origin/master/notice>`_
-- `ONF CLA Information <https://wiki.opencord.org>`_
+- `ONF CLA Information <https://lf-broadband.atlassian.net/wiki>`_
SPDX
^^^^
diff --git a/overview/contributing/jira_tickets.rst b/overview/contributing/jira_tickets.rst
index 76dc7e5..053a196 100644
--- a/overview/contributing/jira_tickets.rst
+++ b/overview/contributing/jira_tickets.rst
@@ -41,7 +41,7 @@
- Note: Jenkins job logs will age out and disappear over time.
- To prevent this view the job history panel in jenkins UI
- - `View a jenkins job page <https://jenkins.opencord.org/view/All%20Jobs/job/bbsim_scale_test/>`_
+ - `View a jenkins job page <https://jenkins.lfbroadband.org/view/All%20Jobs/job/bbsim_scale_test/>`_
- Two links are available in history (lower left corner), colored icon on the left and #job on the right.
- Click the #job link to view job.
- Top right corner will contain a clickable button "Keep this build forever".
@@ -68,9 +68,9 @@
- Notes
* - `VOL-5214 <https://lf-broadband.atlassian.net/browse/VOL-5214>`__
- Jira ticket
- * - `jenkins <https://jenkins.opencord.org/>`_
+ * - `jenkins <https://jenkins.lfbroadband.org/>`_
- Capture job URLs to document errors and log messages.
- * - `gerrit:34854 <https://gerrit.opencord.org/c/ci-management/+/34854>`_
+ * - `gerrit:34854 <https://gerrit.lfbroadband.org/c/ci-management/+/34854>`_
- Capture gerrit patch URLs for state and job reconstruction.
- NOTE: Jenkins logs become unavailable due to aging
diff --git a/overview/contributing/patch_followup.rst b/overview/contributing/patch_followup.rst
index f218b3d..20c0abb 100644
--- a/overview/contributing/patch_followup.rst
+++ b/overview/contributing/patch_followup.rst
@@ -44,9 +44,9 @@
remote:
remote: SUCCESS
remote:
- remote: https://gerrit.opencord.org/c/ci-management/+/34600 Disable jobs dependent on offline menlo-3 node [NEW]
+ remote: https://gerrit.lfbroadband.org/c/ci-management/+/34600 Disable jobs dependent on offline menlo-3 node [NEW]
fremote:
- To ssh://gerrit.opencord.org:29418/ci-management.git
+ To ssh://gerrit.lfbroadband.org:29418/ci-management.git
* [new reference] HEAD -> refs/for/master%topic=dev-joey
.. list-table:: Git commit message
@@ -59,7 +59,7 @@
* -
- 2
- Git commit hash
- * - `34598 <https://gerrit.opencord.org/c/ci-management/+/34598>`_
+ * - `34598 <https://gerrit.lfbroadband.org/c/ci-management/+/34598>`_
- 10
- Gerrit URL for direct patch access
* -
@@ -113,25 +113,25 @@
- Change-Id: Ic8ca17f5923496731f88ce8918c9852d904ea066
- - Visit the `Gerrit dashboard <https://gerrit.opencord.org/dashboard/self>`_
+ - Visit the `Gerrit dashboard <https://gerrit.lfbroadband.org/dashboard/self>`_
- Paste Change-Id into the search box at the top right
- Gerrit UI will navigate to the patch.
Brute force patch lookup
^^^^^^^^^^^^^^^^^^^^^^^^
-- Visit `Gerrit dashboard open+is:wip <https://gerrit.opencord.org/q/status:open+-is:wip>`_
+- Visit `Gerrit dashboard open+is:wip <https://gerrit.lfbroadband.org/q/status:open+-is:wip>`_
- View all open/unmerged patches
- Scroll down through the list until something of interest is found.
- Under the # column (2nd column on left hand side) right click and open
to view the patch.
- - For example: `repo:voltha-system-tests <https://gerrit.opencord.org/c/voltha-system-tests/+/33380>`_
+ - For example: `repo:voltha-system-tests <https://gerrit.lfbroadband.org/c/voltha-system-tests/+/33380>`_
Patch history and jenkins jobs
------------------------------
-While viewing a patch (`repo:voltha-system-tests <https://gerrit.opencord.org/c/voltha-system-tests/+/33380>`_)
+While viewing a patch (`repo:voltha-system-tests <https://gerrit.lfbroadband.org/c/voltha-system-tests/+/33380>`_)
scroll down to the 'Change Log' section at the bottom.
| Line items represent historical comments, code review messages and
processed job status.
@@ -143,7 +143,7 @@
To view job logs click on an entry to expand (Verified +1, 4th entry from
the bottom) to view a set of clickable jenkins URLs.
-- `Patch 33380 <https://gerrit.opencord.org/c/voltha-system-tests/+/33380>`_
- - `verify_voltha-system-tests_unit-test <https://jenkins.opencord.org/job/verify_voltha-system-tests_unit-test>`_ : SUCCESS
- - `verify_voltha-system-tests_licensed <https://jenkins.opencord.org/job/verify_voltha-system-tests_licensed>`_ : SUCCESS
- - `verify_voltha-system-tests_sanity-test <https://jenkins.opencord.org/job/verify_voltha-system-tests_sanity-test>`_ : FAILED
+- `Patch 33380 <https://gerrit.lfbroadband.org/c/voltha-system-tests/+/33380>`_
+ - `verify_voltha-system-tests_unit-test <https://jenkins.lfbroadband.org/job/verify_voltha-system-tests_unit-test>`_ : SUCCESS
+ - `verify_voltha-system-tests_licensed <https://jenkins.lfbroadband.org/job/verify_voltha-system-tests_licensed>`_ : SUCCESS
+ - `verify_voltha-system-tests_sanity-test <https://jenkins.lfbroadband.org/job/verify_voltha-system-tests_sanity-test>`_ : FAILED
diff --git a/overview/jenkins_node.rst b/overview/jenkins_node.rst
index 7c40683..962d4a9 100644
--- a/overview/jenkins_node.rst
+++ b/overview/jenkins_node.rst
@@ -8,7 +8,7 @@
This page is intended to provide pointers to useful instructions
that you need to setup your ``Jenkins`` executor and a list of tools install on it in order to
-run the automated tests using the ``ci-management`` pipelines that are used on the `OpenCORD Jenkins <https://jenkins.opencord.org/>`_
+run the automated tests using the ``ci-management`` pipelines that are used on the `OpenCORD Jenkins <https://jenkins.lfbroadband.org/>`_
.. _jenkins_node:
diff --git a/overview/release_process.rst b/overview/release_process.rst
index 093842e..7d63c87 100644
--- a/overview/release_process.rst
+++ b/overview/release_process.rst
@@ -81,16 +81,16 @@
The ONOS Apps need to be released in a different manner.
-A dedicated Jenkins job is used to release ONOS app: https://jenkins.opencord.org/job/onos-app-release.
+A dedicated Jenkins job is used to release ONOS app: https://jenkins.lfbroadband.org/job/onos-app-release.
The job will need to be initiated using specific parameters, for an example view the lateset pipeline job.
-1. `Build with parameters <https://jenkins.opencord.org/job/onos-app-release>`_: use the name of the repo (not of the app itself)
+1. `Build with parameters <https://jenkins.lfbroadband.org/job/onos-app-release>`_: use the name of the repo (not of the app itself)
- appRepo: sadis
- appName: sadis
- - apiVersion: `sadis:5.12.0-SNAPSHOT <https://gerrit.opencord.org/plugins/gitiles/sadis/+/refs/heads/master/api/pom.xml#22>`__
+ - apiVersion: `sadis:5.12.0-SNAPSHOT <https://gerrit.lfbroadband.org/plugins/gitiles/sadis/+/refs/heads/master/api/pom.xml#22>`__
- nextApiVersion: version+1
- - version: `sadis:5.12.0-SNAPSHOT <https://gerrit.opencord.org/plugins/gitiles/sadis/+/refs/heads/master/app/pom.xml#20>`__
+ - version: `sadis:5.12.0-SNAPSHOT <https://gerrit.lfbroadband.org/plugins/gitiles/sadis/+/refs/heads/master/app/pom.xml#20>`__
- nextVersion: version+1
- branch: master
- jdkDistro: java-11-amazon-corretto
@@ -98,12 +98,12 @@
2. Wait for build to complete
3. Merge the component patches on gerrit
- - `View <https://gerrit.opencord.org/q/owner:do-not-reply%2540opennetworking.org>`_
+ - `View <https://gerrit.lfbroadband.org/q/owner:do-not-reply%2540opennetworking.org>`_
- Two pull requests are created modifying pom.xml.
- Approve patch one (-SNAPSHOT: no) to initiate a release build.
- Approve patch two (-SNAPSHOT: yes) to revert pom.xml to a non-release version.
-4. Approval and merge will trigger `jenkins::maven-publish_sadis <https://jenkins.opencord.org/job/maven-publish_sadis/>`_
+4. Approval and merge will trigger `jenkins::maven-publish_sadis <https://jenkins.lfbroadband.org/job/maven-publish_sadis/>`_
that will publish an artifact into the staging repo on `sonatype <https://oss.sonatype.org>`_.
Once published to the staging server the artifact will need to be released to maven central.
@@ -199,7 +199,7 @@
- `VOLTHA Helm Charts <https://github.com/opencord/voltha-helm-charts>`_
- `VOLTHA System Tests <https://github.com/opencord/voltha-system-tests>`_
- `VOLTHA docs <https://github.com/opencord/voltha-docs>`_
-- `repo:ci-management <https://gerrit.opencord.org/plugins/gitiles/ci-management>`_
+- `repo:ci-management <https://gerrit.lfbroadband.org/plugins/gitiles/ci-management>`_
These 4 repos are the only ones that receive a X.Y.Z tag.
Other repos that contain individual components have their own
@@ -294,10 +294,10 @@
If a fix is needed to the ONOS apps:
-- Create a branch here https://gerrit.opencord.org/plugins/gitiles/olt/+/refs/heads/olt-4.1
+- Create a branch here https://gerrit.lfbroadband.org/plugins/gitiles/olt/+/refs/heads/olt-4.1
- then `Git checkout -b <branch-name> opencord/<version>`
-- Then push a commit changing to `.1-SNAPSHOT` more (see e.g. https://gerrit.opencord.org/c/igmpproxy/+/19589)
-- Then push you changes (e.g. https://gerrit.opencord.org/c/igmpproxy/+/19590)
+- Then push a commit changing to `.1-SNAPSHOT` more (see e.g. https://gerrit.lfbroadband.org/c/igmpproxy/+/19589)
+- Then push you changes (e.g. https://gerrit.lfbroadband.org/c/igmpproxy/+/19590)
- Then release as per the process above.
See Also
diff --git a/overview/troubleshooting.rst b/overview/troubleshooting.rst
index 1f08de9..09c1010 100644
--- a/overview/troubleshooting.rst
+++ b/overview/troubleshooting.rst
@@ -7,10 +7,10 @@
Depending on your issue useful tips and tricks can be found:
-- `No ONUs are discovered <https://guide.opencord.org/master/profiles/seba/troubleshoot/no-onus.html>`_
-- `Can't authenticate <https://guide.opencord.org/master/profiles/seba/troubleshoot/no-aaa.html>`_
-- `DHCP is not working <https://guide.opencord.org/master/profiles/seba/troubleshoot/no-dhcp.html>`_
-- `No Ping <https://guide.opencord.org/master/profiles/seba/troubleshoot/no-ping.html>`_
+- `No ONUs are discovered <https://guide.lfbroadband.org/master/profiles/seba/troubleshoot/no-onus.html>`_
+- `Can't authenticate <https://guide.lfbroadband.org/master/profiles/seba/troubleshoot/no-aaa.html>`_
+- `DHCP is not working <https://guide.lfbroadband.org/master/profiles/seba/troubleshoot/no-dhcp.html>`_
+- `No Ping <https://guide.lfbroadband.org/master/profiles/seba/troubleshoot/no-ping.html>`_
Trace Packets across components