Review koschei SOP
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
parent
11c1fc3e55
commit
5a42d63c77
2 changed files with 12 additions and 10 deletions
|
@ -61,7 +61,7 @@
|
||||||
** xref:koji.adoc[Koji Infrastructure - SOP]
|
** xref:koji.adoc[Koji Infrastructure - SOP]
|
||||||
** xref:koji-archive.adoc[Koji Archive - SOP]
|
** xref:koji-archive.adoc[Koji Archive - SOP]
|
||||||
** xref:koji-builder-setup.adoc[Setup Koji Builder - SOP]
|
** xref:koji-builder-setup.adoc[Setup Koji Builder - SOP]
|
||||||
** xref:koschei.adoc[koschei - SOP in review ]
|
** xref:koschei.adoc[Koschei - SOP]
|
||||||
** xref:layered-image-buildsys.adoc[layered-image-buildsys - SOP in review ]
|
** xref:layered-image-buildsys.adoc[layered-image-buildsys - SOP in review ]
|
||||||
** xref:librariesio2fedmsg.adoc[librariesio2fedmsg - SOP in review ]
|
** xref:librariesio2fedmsg.adoc[librariesio2fedmsg - SOP in review ]
|
||||||
** xref:mailman.adoc[mailman - SOP in review ]
|
** xref:mailman.adoc[mailman - SOP in review ]
|
||||||
|
|
|
@ -4,8 +4,10 @@ Koschei is a continuous integration system for RPM packages. Koschei
|
||||||
runs package scratch builds after dependency change or after time elapse
|
runs package scratch builds after dependency change or after time elapse
|
||||||
and reports package buildability status to interested parties.
|
and reports package buildability status to interested parties.
|
||||||
|
|
||||||
Production instance: https://apps.fedoraproject.org/koschei Staging
|
Production instance::
|
||||||
instance: https://apps.stg.fedoraproject.org/koschei
|
https://apps.fedoraproject.org/koschei
|
||||||
|
Staginginstance::
|
||||||
|
https://apps.stg.fedoraproject.org/koschei
|
||||||
|
|
||||||
== Contact Information
|
== Contact Information
|
||||||
|
|
||||||
|
@ -71,8 +73,8 @@ happens automatically when using the playbook.
|
||||||
|
|
||||||
== Disk usage
|
== Disk usage
|
||||||
|
|
||||||
Koschei doesn't keep on disk anything that couldn't be recreated easily
|
Koschei doesn't keep on disk anything that couldn't be recreated easily -
|
||||||
- all important data is stored in PostgreSQL database, configuration is
|
all important data is stored in PostgreSQL database, configuration is
|
||||||
managed by Ansible, code installed by RPM and so on.
|
managed by Ansible, code installed by RPM and so on.
|
||||||
|
|
||||||
To speed up operation and reduce load on external servers, Koschei
|
To speed up operation and reduce load on external servers, Koschei
|
||||||
|
@ -109,7 +111,7 @@ Koschei services are systemd units managed through `systemctl`. They can
|
||||||
be started and stopped independently in any order. The frontend is run
|
be started and stopped independently in any order. The frontend is run
|
||||||
using httpd.
|
using httpd.
|
||||||
|
|
||||||
== Suspespending koschei operation
|
== Suspending koschei operation
|
||||||
|
|
||||||
For stopping builds from being scheduled, stopping the
|
For stopping builds from being scheduled, stopping the
|
||||||
`koschei-scheduler` service is enough. For planned Koji outages, it's
|
`koschei-scheduler` service is enough. For planned Koji outages, it's
|
||||||
|
@ -163,14 +165,14 @@ koschei-admin clear-notice
|
||||||
|
|
||||||
Packages can be added to one or more group.
|
Packages can be added to one or more group.
|
||||||
|
|
||||||
To add new group named "mynewgroup", run as koschei user:
|
To add new group named `mynewgroup`, run as `koschei` user:
|
||||||
|
|
||||||
....
|
....
|
||||||
koschei-admin add-group mynewgroup
|
koschei-admin add-group mynewgroup
|
||||||
....
|
....
|
||||||
|
|
||||||
To add new group named "mynewgroup" and populate it with some packages,
|
To add new group named `mynewgroup` and populate it with some packages,
|
||||||
run as koschei user:
|
run as `koschei` user:
|
||||||
|
|
||||||
....
|
....
|
||||||
koschei-admin add-group mynewgroup pkg1 pkg2 pkg3
|
koschei-admin add-group mynewgroup pkg1 pkg2 pkg3
|
||||||
|
@ -183,7 +185,7 @@ priority. Any user can change manual priority, which is reset after
|
||||||
package is rebuilt. Admins can additionally set static priority, which
|
package is rebuilt. Admins can additionally set static priority, which
|
||||||
is not affected by package rebuilds.
|
is not affected by package rebuilds.
|
||||||
|
|
||||||
To set static priority of package "foo" to value "100", run as koschei
|
To set static priority of package `foo` to value `100`, run as `koschei`
|
||||||
user:
|
user:
|
||||||
|
|
||||||
....
|
....
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue