Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Review publictest-dev-stg-production SOP

Browse source 
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2021-09-10 12:10:32 +02:00
parent e41063673a
commit a747e79919
2 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/sysadmin_guide/nav.adoc
View file

@ -89,7 +89,7 @@
** xref:pdc.adoc[PDC - SOP]
** xref:pesign-upgrade.adoc[Pesign upgrades/reboots - SOP]
** xref:planetsubgroup.adoc[Planet Subgroup Infrastructure - SOP]
** xref:publictest-dev-stg-production.adoc[publictest-dev-stg-production - SOP in review ]
** xref:publictest-dev-stg-production.adoc[Fedora Infrastructure Machine Classes - SOP]
** xref:rabbitmq.adoc[rabbitmq - SOP in review ]
** xref:rdiff-backup.adoc[rdiff-backup - SOP in review ]
** xref:registry.adoc[registry - SOP in review ]

11
modules/sysadmin_guide/pages/publictest-dev-stg-production.adoc
View file

@ -23,16 +23,15 @@ in the life cycle of providing an application or resource.
publictest instances are used for early investigation into a resource or
application. At this stage the application might not be packaged yet,
and we want to see if it's worth packaging and starting it on the
process to be available in production. These machines are accessable to
process to be available in production. These machines are accessible to
anyone in the sysadmin-test group, and coordination of use of instances
is done on an ad-hock basis. These machines are re-installed every cycle
is done on an ad-hoc basis. These machines are re-installed every cycle
cleanly, so all work must be saved before this occurs.
Authentication must not be against the production fas server. We have
fakefas.fedoraproject.org setup for these systems instead.
_fakefas.fedoraproject.org_ setup for these systems instead.
[NOTE]
.Note
====
We're planning on merging publictest into the development servers.
Environment-wise they'll be mostly the same (one service per machine, a
@ -59,13 +58,13 @@ to maintain the .dev server so that newer contributors don't have to
perform that setup in order to work on the service.
Authentication must not be against the production fas server. We have
fakefas.fedoraproject.org setup for these systems instead.
_fakefas.fedoraproject.org_ setup for these systems instead.
[NOTE]
.Note
====
fakefas will be renamed fas01.dev at some point in the future
====
== Staging
These instances are used to integrate the application or resource into