From 127af1ce43b8d5b6264f65622ab61d0568317033 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Wed, 4 May 2022 21:54:14 +0900 Subject: [PATCH] Replace github by opendev ... because now opendev is the source repository and github is its mirror. Change-Id: I55ab8bb845e73bba0375ac30fd126c92a4278bd3 --- CONTRIBUTING.rst | 2 +- StorletSamples/java/CompressStorlet/build.xml | 2 +- doc/source/archive/building_and_deploying_docker_images.rst | 4 ++-- doc/source/archive/invoking_storlets.rst | 2 +- doc/source/archive/storlet_api.rst | 4 ++-- doc/source/archive/storlets_management.rst | 6 +++--- doc/source/engine_dev_installation.rst | 4 ++-- doc/source/s2aio_dev_host_include.rst | 2 +- s2aio.sh | 2 +- tox.ini | 6 +++--- 10 files changed, 17 insertions(+), 17 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index d7797325..98b1ecb9 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -12,7 +12,7 @@ Building changes off the upstream repository: --------------------------------------------- This covers the scenario where you'd like to add / change code on the latest version of the storlet repo, do read the initial gerrit setup section if you haven't already done so. -* ``git clone https://github.com/openstack/storlets.git`` +* ``git clone https://opendev.org/openstack/storlets.git`` This will clone the upstream repo. diff --git a/StorletSamples/java/CompressStorlet/build.xml b/StorletSamples/java/CompressStorlet/build.xml index cd4a01e4..94bbe907 100644 --- a/StorletSamples/java/CompressStorlet/build.xml +++ b/StorletSamples/java/CompressStorlet/build.xml @@ -27,7 +27,7 @@ - + diff --git a/doc/source/archive/building_and_deploying_docker_images.rst b/doc/source/archive/building_and_deploying_docker_images.rst index 4bcc4625..670a9094 100644 --- a/doc/source/archive/building_and_deploying_docker_images.rst +++ b/doc/source/archive/building_and_deploying_docker_images.rst @@ -24,7 +24,7 @@ Below are the steps of this flow: #. A prerequisite for the account manager to deploy a Docker image to Swift is having an account that is enabled for Storlets. This is an operation that is done by the Swift Storlet - manager and is explained in . + manager and is explained in . #. Once the account is enabled for Storlets, a container named docker_images is created, with access to both the account manager as well as the storlet manager. That container will include a basic Docker image consisting of some Storlet @@ -33,7 +33,7 @@ Below are the steps of this flow: the installed software stack, and upload it back to the docker_images container. #. Once uploaded, the account manager must notify the Swift Storlet engine manager of the update. The storlets manager would take care of testing and deploying - it to all Swift nodes. Again, + it to all Swift nodes. Again, describes the provided tool the Storlet manager can use for the actual deployment. The sections below describe in detail the steps taken by the account manager. diff --git a/doc/source/archive/invoking_storlets.rst b/doc/source/archive/invoking_storlets.rst index 796eeb40..62161caf 100644 --- a/doc/source/archive/invoking_storlets.rst +++ b/doc/source/archive/invoking_storlets.rst @@ -11,7 +11,7 @@ Storlets can be invoked in 2 ways: 2. Invocation upon PUT. In this case the data kept in the store is a transformation of the object uploaded by the user (as opposed to the actual uploaded data or metadata). A typical use case is metadata enrichment, where a Storlet extracts format specific metadata from the uploaded data and adds it as Swift metadata. Invocation involves adding an extra header to the Swift original -PUT/GET requests. Following our Identity Storlet example given in , here are invocation examples. This time the examples make use of the python swift client. +PUT/GET requests. Following our Identity Storlet example given in , here are invocation examples. This time the examples make use of the python swift client. Invocation on GET ================= diff --git a/doc/source/archive/storlet_api.rst b/doc/source/archive/storlet_api.rst index 948f6cd3..cbb0dfcd 100644 --- a/doc/source/archive/storlet_api.rst +++ b/doc/source/archive/storlet_api.rst @@ -54,7 +54,7 @@ The X-Object-Meta-Storlet-Interface-Version header should be provided and set to Although not currently used, the X-Object-Meta-Storlet-Object-Metadata header must be provided and set to 'no'. See the Storlets Developer's manual for details of the signature of the invoke method. The content-type of the request should be set to 'application/octet-stream'. -Additional details and examples can be found at . +Additional details and examples can be found at . :: @@ -120,7 +120,7 @@ Storlets can be invoked in 3 ways: thumbnail extraction from an existing jpg. Invocation involves adding an extra header ('X-Run-Storlet') to the Swift original PUT/GET/COPY requests. -Additional details and examples can be found in . +Additional details and examples can be found in . Invoke a storlet upon object download ------------------------------------- diff --git a/doc/source/archive/storlets_management.rst b/doc/source/archive/storlets_management.rst index 21c8a5d6..2bb4678d 100644 --- a/doc/source/archive/storlets_management.rst +++ b/doc/source/archive/storlets_management.rst @@ -7,7 +7,7 @@ Introduction The Storlet manager operations currently include: #. Creating a Storlet enabled tenant. -#. Deploying an image that was created by the tenant admin as described in +#. Deploying an image that was created by the tenant admin as described in The scripts providing these operations are located under /opt/ibm in the storlet management machine. @@ -31,7 +31,7 @@ The script takes 3 parameters: #. The password for the account manager Note that the script is aware of the Keystone admin credentials as they -were provided to the initial installation script as described in +were provided to the initial installation script as described in Below is a sample invocation: @@ -95,7 +95,7 @@ Below is a sample invocation: Deploying a Tenant Image ======================== -Recall that in the Docker image build (described in ) the image was given a name +Recall that in the Docker image build (described in ) the image was given a name (specified after -t in the docker build command) and was uploaded as a .tar file to the tenant's docker_images Swift container. When deploying an image, the Storlet's admin needs to provide the tenant name, the .tar object name and the image name. diff --git a/doc/source/engine_dev_installation.rst b/doc/source/engine_dev_installation.rst index 9836e86e..bc643fbf 100644 --- a/doc/source/engine_dev_installation.rst +++ b/doc/source/engine_dev_installation.rst @@ -13,7 +13,7 @@ Clone devstack: :: - git clone https://github.com/openstack/devstack.git + git clone https://opendev.org/openstack/devstack.git Create a localrc file under the devstack repository root directory: @@ -144,7 +144,7 @@ Get and install the storlets code :: cd $HOME - git clone https://github.com/openstack/storlets.git + git clone https://opendev.org/openstack/storlets.git cd storlets sudo ./install_libs.sh sudo python setup.py install diff --git a/doc/source/s2aio_dev_host_include.rst b/doc/source/s2aio_dev_host_include.rst index 468284e1..75948e9a 100644 --- a/doc/source/s2aio_dev_host_include.rst +++ b/doc/source/s2aio_dev_host_include.rst @@ -5,6 +5,6 @@ With that user just do: sudo apt-get update sudo apt-get install python-tox python-nose git - git clone https://github.com/openstack/storlets.git + git clone https://opendev.org/openstack/storlets.git cd storlets ./s2aio.sh install diff --git a/s2aio.sh b/s2aio.sh index ad735953..5f4a5a79 100755 --- a/s2aio.sh +++ b/s2aio.sh @@ -33,7 +33,7 @@ function usage { function _prepare_devstack_env { # Checkout devstack if [ ! -e $DEVSTACK_DIR ]; then - git clone https://github.com/openstack-dev/devstack.git $DEVSTACK_DIR + git clone https://opendev.org/openstack/devstack.git $DEVSTACK_DIR cp devstack/localrc.sample $DEVSTACK_DIR/localrc fi diff --git a/tox.ini b/tox.ini index 93109e74..7627f68e 100644 --- a/tox.ini +++ b/tox.ini @@ -17,7 +17,7 @@ deps = -c{env:TOX_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt - git+https://github.com/openstack/swift.git + git+https://opendev.org/openstack/swift.git commands = find . -type f -name "*.py[c|o]" -delete find . -type d -name "__pycache__" -delete @@ -35,7 +35,7 @@ commands = [testenv:func] deps = -r{toxinidir}/test-requirements.txt - git+https://github.com/openstack/swift.git + git+https://opendev.org/openstack/swift.git setenv = VIRTUAL_ENV={envdir} STORLET_SAMPLE_PATH={toxinidir}/StorletSamples @@ -60,7 +60,7 @@ deps = -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/doc/requirements.txt - git+https://github.com/openstack/swift.git + git+https://opendev.org/openstack/swift.git commands = sphinx-build -a -W -E -b html doc/source doc/build/html