Message Tagging Service SOP
Factory2 Team, Fedora QA Team, Infrastructure Team
cqi, lucarval, vmaljulin
Tag module build
Message Tagging Service, aka MTS, is an event-driven microservice to tag a module build triggered by MBS specific event.
MTS basically listens on message bus for the MBS event
mbs.build.state.change. Once a message is received, the module build
represented by that message will be tested if it matches any predefined
rules. Each rule definition has destination tag defined. If a rule
matches the build, the destination tag will be applied to that build.
Only module build in ready state is handled by MTS for now.
authenticate remotely with openshift using
oc login https://os.fedoraproject.org), and run:
oc project mts oc status -v oc logs -f dc/mts
Please do remember to increase
MTS_CONFIG_VERSION so that Openshift
creates a new pod after running the playbook.
You can roll out configuration changes by changing the files in
roles/openshift-apps/message-tagging-service/ and running the
MTS docker image is built automatically and pushed to upstream quay.io.
By default, tag
latest is applied to a fresh image. Tag
applied to image, then run the playbook
playbooks/openshift-apps/message-tagging-service.yml with environment
Want to help? Learn how to contribute to Fedora Docs ›