Review hotness SOP

Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2021-09-02 14:20:36 +02:00
parent c022da81a9
commit 4cac32bc5c
2 changed files with 7 additions and 18 deletions

View file

@ -47,7 +47,7 @@
** xref:guestedit.adoc[Guest Editing - SOP] ** xref:guestedit.adoc[Guest Editing - SOP]
** xref:haproxy.adoc[Haproxy Infrastructure - SOP] ** xref:haproxy.adoc[Haproxy Infrastructure - SOP]
** xref:hotfix.adoc[HOTFIXES - SOP] ** xref:hotfix.adoc[HOTFIXES - SOP]
** xref:hotness.adoc[hotness - SOP in review ] ** xref:hotness.adoc[The New Hotness - SOP]
** xref:index.adoc[index - SOP in review ] ** xref:index.adoc[index - SOP in review ]
** xref:infra-git-repo.adoc[infra-git-repo - SOP in review ] ** xref:infra-git-repo.adoc[infra-git-repo - SOP in review ]
** xref:infra-hostrename.adoc[infra-hostrename - SOP in review ] ** xref:infra-hostrename.adoc[infra-hostrename - SOP in review ]

View file

@ -17,15 +17,7 @@ Contact::
Persons:: Persons::
zlopez zlopez
Location:: Location::
iad2.fedoraproject.org os.fedoraproject.org
Servers::
Production
+
* hotness01.iad2.fedoraproject.org
+
Staging
+
* hotness01.stg.iad2.fedoraproject.org
Purpose:: Purpose::
File issues when upstream projects release new versions of a package File issues when upstream projects release new versions of a package
@ -34,7 +26,6 @@ Purpose::
The current deployment is made up of the-new-hotness OpenShift The current deployment is made up of the-new-hotness OpenShift
namespace. namespace.
[[the-new-hotness-1]]
=== the-new-hotness === the-new-hotness
This OpenShift namespace runs following pods: This OpenShift namespace runs following pods:
@ -43,7 +34,7 @@ This OpenShift namespace runs following pods:
This OpenShift project relies on: This OpenShift project relies on:
* `anitya-sop` as message publisher * xref:anitya.adoc[Anitya] as message publisher
* Fedora messaging RabbitMQ hub for consuming messages * Fedora messaging RabbitMQ hub for consuming messages
* Koji for scratch builds * Koji for scratch builds
* Bugzilla for issue reporting * Bugzilla for issue reporting
@ -56,8 +47,7 @@ documentation].
=== Deploying === Deploying
Staging deployment of the-new-hotness is deployed in OpenShift on Staging deployment of the-new-hotness is deployed in staging OpenShift.
os-master01.stg.iad2.fedoraproject.org.
To deploy staging instance of the-new-hotness you need to push changes To deploy staging instance of the-new-hotness you need to push changes
to staging branch on to staging branch on
@ -65,8 +55,7 @@ https://github.com/fedora-infra/the-new-hotness[the-new-hotness GitHub].
GitHub webhook will then automatically deploy a new version of GitHub webhook will then automatically deploy a new version of
the-new-hotness on staging. the-new-hotness on staging.
Production deployment of the-new-hotness is deployed in OpenShift on Production deployment of the-new-hotness is deployed in production OpenShift.
os-master01.iad2.fedoraproject.org.
To deploy production instance of the-new-hotness you need to push To deploy production instance of the-new-hotness you need to push
changes to production branch on changes to production branch on
@ -78,7 +67,7 @@ the-new-hotness on production.
To deploy the new configuration, you need To deploy the new configuration, you need
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/sshaccess.html[ssh https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/sshaccess.html[ssh
access] to batcave01.iad2.fedoraproject.org and access] to _batcave01.iad2.fedoraproject.org_ and
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
to run the Ansible playbook]. to run the Ansible playbook].
@ -126,7 +115,7 @@ It can be nice to check up on the-new-hotness to make sure its behaving
correctly. You can see all the Bugzilla activity using the correctly. You can see all the Bugzilla activity using the
https://bugzilla.redhat.com/page.cgi?id=user_activity.html[user activity https://bugzilla.redhat.com/page.cgi?id=user_activity.html[user activity
query] (staging uses query] (staging uses
https://partner-bugzilla.redhat.com/page.cgi?id=user_activity.html[partner-bugzilla.redhat.com]) https://bugzilla.stage.redhat.com//page.cgi?id=user_activity.html[bugzilla.stage.redhat.com])
and querying for the `upstream-release-monitoring@fedoraproject.org` and querying for the `upstream-release-monitoring@fedoraproject.org`
user. user.