#1 fedora messaging docs
Merged 9 months ago by lrossett. Opened 9 months ago by lrossett.
centos/ lrossett/stream-team-docs fedora-messaging  into  master

file modified
+6 -1

@@ -1,4 +1,9 @@ 

  # Stream Team Docs

  

- This repository aims to contain several procedures for the centos steam team members.

+ This repository aims to contain several procedures for the centos stream team members.

  

+ ## Index

+ 

+ [MBBOX](./mbbox)

+ 

+ [Fedora Messaging](./fedora-messaging/)

@@ -0,0 +1,53 @@ 

+ # Fedora Messaging

+ 

+ ## Requesting Access

+ 

+ What needs to be done:

+ 

+ * Request certificates from the fedora infrastructure team;

+ * Ansible changes to create a new user, queue and topic in fedora messaging.

+ 

+ You can request a new certificate and a private key by opening a fedora infrastructure ticket: https://pagure.io/fedora-infrastructure (Example: https://pagure.io/fedora-infrastructure/issue/9494).

+ 

+ The ticket should request a new username for fedora messaging (either prod or stg) - the result of that ticket will be a new certificate and private key for that user (the certificate CN field should contain the requested username as its value).

+ 

+ The next step is to add the new user, queue and topic binding into fedora's Rabbit MQ instance.

+ 

+ This can be done by sending a pull request to their ansible repository (https://pagure.io/fedora-infra/ansible): https://pagure.io/fedora-infra/ansible/pull-request/302#request_diff.

+ 

+ The topic format uses the following scheme: `org.<SOURCE>.<ENV>.<APP>.#` where:

+ 

+ * `<SOURCE>`: source as entity, should be `centos` in our case

+ * `<ENV>`: env is either `prod` or `stg` but you should use the ansible var `short_env`

+ * `<APP>`: the application the message belongs to, which matches your username.

+ 

+ A topic for centos koji would be: `org.centos.prod.koji.#` (`#` means Rabbit MQ will match the topic as long as it starts with `org.centos.prod.koji.`).

+ 

+ Those changes will also need to be run by someone from the fedora infrastructure team.

+ 

+ ### Example

+ 

+ The following ansible code is an example of how to add an user and a queue with a routing key.

+ 

+ ```yaml

+ # adding "centos-koji" user as an example

+ 

+ - name: Add centos-koji User

+   run_once: true

+   include_role:

+     name: rabbit/user

+   vars:

+      username: centos-koji{{ env_suffix }}

+ 

+ - name: Add centos-koji queue

+   run_once: true

+   include_role:

+     name: rabbit/queue

+   vars:

+     username: centos-koji{{ env_suffix }}

+     queue_name: centos-koji{{ env_suffix }}

+     # TTL: 10 days (in miliseconds)

+     message_ttl: 864000000

+     routing_keys:

+       - "org.centos.{{ env_short }}.koji.#"

+ ```

mbbox/README.md mbbox/deployment.md
file renamed
file was moved with no change to the file

Adding fedora messaging docs for requesting new user access + queue creation.

Metadata Update from @lrossett:
- Request assigned

9 months ago

Metadata Update from @lrossett:
- Request assignee reset

9 months ago

rebased onto f728bc7

9 months ago

1 new commit added

  • fix index newline
9 months ago

1 new commit added

  • fix links
9 months ago

4 new commits added

  • fix links
  • fix index newline
  • add mbbox in index + fedora-messaging example
  • fedora messaging docs
9 months ago

4 new commits added

  • fix links
  • fix index newline
  • add mbbox in index + fedora-messaging example
  • fedora messaging docs
9 months ago

Pull-Request has been merged by lrossett

9 months ago