mote SOP

If you have access to rbac-playbook:

There is a playbook that can force mote to update its cache in case it gets stuck somehow:

Put a new copy of the mote rpm in the infra repo and run:

mote is a Python webapp running on Flask with mod_wsgi. It can be used to view past logs, browse meeting minutes, or glean other information relevant to Fedora’s matrix meetings. It employs a JSON file store cache, in addition to a memcached store which is currently not in use with Fedora infrastructure.

mote configuration is located in /etc/mote/config.py. The configuration contains all configurable items for all mote services. Alterations to configuration that aren’t temporary should be done through ansible playbooks. Configuration changes have no effect on running services — they need to be restarted, which can be done using the playbook.

mote does not currently utilise any databases, although it uses a file store in Fedora Infrastructure and has an optional memcached store which is currently unused.

mote is ran using mod_wsgi and httpd, hence, you must manage the httpd service to change mote’s status.

mote can be stopped by stopping the httpd service:

mote uses a set of JSON name and category definitions to provide friendly names, aliases, and listings on its interface. These definitions can be located in mote’s GitHub repository, and need to be pulled into ansible in order to be deployed.

These files are name_mappings.json and category_mappings.json. To deploy an update to these definitions, place the updated name and category mapping files in ansible/roles/mote/templates. Run the playbook in order to deploy your changes.