airship/spyglass
Code Issues Proposed changes

Replace git.openstack.org URLs with opendev.org URLs

Browse Source 
Change-Id: I1a933b8794c97244b95b6782033b52cbca74b0b6
This commit is contained in:
Ian Pittwood 2019-05-03 13:46:00 -05:00
parent 1f88747974
commit 69f0975dec
4 changed files with 5 additions and 5 deletions
doc/source
getting_started.rst
setup.py
spyglass/examples/templates
deployment
deployment-strategy.yaml.j2
secrets/certificates
certificates.yaml.j2

4
doc/source/getting_started.rst

@ -28,7 +28,7 @@ for a site deployment. These site manifest YAML files generated
by spyglass will be saved in a Git repository, from where Pegleg by spyglass will be saved in a Git repository, from where Pegleg
can access and aggregate them. This aggregated file can then be can access and aggregate them. This aggregated file can then be
fed to Shipyard for site deployment / updates. fed to Shipyard for site deployment / updates.
Reference: https://review.openstack.org/#/c/605227 Reference: https://review.opendev.org/#/c/605227
Architecture Architecture
------------ ------------
@ -129,7 +129,7 @@ Before using Spyglass you must:
.. code-block:: console .. code-block:: console
git clone https://github.com/openstack/airship-spyglass git clone https://opendev.org/airship/spyglass.git
2. Install the required packages in spyglass: 2. Install the required packages in spyglass:

2
setup.py

@ -19,7 +19,7 @@ setup(
name='spyglass', name='spyglass',
version='0.0.1', version='0.0.1',
description='Generate Airship specific yaml manifests from data sources', description='Generate Airship specific yaml manifests from data sources',
url='http://github.com/openstack/airship-spyglass', url='https://opendev.org/airship/spyglass.git',
python_requires='>=3.5.0', python_requires='>=3.5.0',
license='Apache 2.0', license='Apache 2.0',
packages=find_packages(), packages=find_packages(),

2
spyglass/examples/templates/deployment/deployment-strategy.yaml.j2

@ -7,7 +7,7 @@
# deploy first, followed by half of the computes, followed by the second half of the # deploy first, followed by half of the computes, followed by the second half of the
# computes. Shipyard deployment strategies can be very useful in getting around certain # computes. Shipyard deployment strategies can be very useful in getting around certain
# failures, like misbehaving nodes that may hold up the deployment. See more at: # failures, like misbehaving nodes that may hold up the deployment. See more at:
# https://github.com/openstack/airship-shipyard/blob/master/doc/source/site-definition-documents.rst#deployment-strategy # https://opendev.org/airship/shipyard/src/branch/master/doc/source/site-definition-documents.rst#deployment-strategy
schema: shipyard/DeploymentStrategy/v1 schema: shipyard/DeploymentStrategy/v1
metadata: metadata:
schema: metadata/Document/v1 schema: metadata/Document/v1

2
spyglass/examples/templates/secrets/certificates/certificates.yaml.j2

@ -1,6 +1,6 @@
--- ---
# Certs generated by Promenade, see docs at # Certs generated by Promenade, see docs at
# https://github.com/openstack/airship-treasuremap/blob/master/doc/source/authoring_and_deployment.rst # https://opendev.org/airship/treasuremap/src/branch/master/doc/source/authoring_and_deployment.rst
data: | data: |
-----BEGIN CERTIFICATE----- -----BEGIN CERTIFICATE-----
MIIDSDCCAjCgAwIBAgIUegkh/antB1XyDVHdP5dv+0MZyBcwDQYJKoZIhvcNAQEL MIIDSDCCAjCgAwIBAgIUegkh/antB1XyDVHdP5dv+0MZyBcwDQYJKoZIhvcNAQEL