Freeze Break Request: Turn on fedmsg for PDC

[Ralph Bean]

We currently use a fedmsg-driven daemon to update PDC about stuff that
gets composed by pungi.

This patch turns on a new layer that lets PDC publish its own messages
when it gets updated (the software comes with fedmsg as one of four
different message-publication methods it can use, which is cool!)

adamw wants to use these new messages to drive the validation event
creation project.

The iptables rules and the fedmsg.d/ endpoints and the certs were all
set up when I first stood up PDC.. this patch just turns on the
plugin, and adds the one topic PDC produces to our fedmsg policy.

I'll have to do a master.yml playbook run of the 'fedmsgdconfig' tag,
which will touch all hosts.. but I expect this will be "fine".

Can I get two +1's to push this out?



diff --git a/inventory/group_vars/pdc-web b/inventory/group_vars/pdc-web
index f07deb7..59073da 100644
--- a/inventory/group_vars/pdc-web
+++ b/inventory/group_vars/pdc-web
@@ -29,6 +29,5 @@ fedmsg_certs:
 - service: pdc
   owner: root
   group: apache
-  # We don't have notifications from PDC yet, but when we do, add them here.
-  #can_send:
-  #- pdc.somethingorother
+  can_send:
+  - pdc.compose
diff --git a/inventory/group_vars/pdc-web-stg b/inventory/group_vars/pdc-web-stg
index 1c55f07..a7e45f9 100644
--- a/inventory/group_vars/pdc-web-stg
+++ b/inventory/group_vars/pdc-web-stg
@@ -29,6 +29,5 @@ fedmsg_certs:
 - service: pdc
   owner: root
   group: apache
-  # We don't have notifications from PDC yet, but when we do, add them here.
-  #can_send:
-  #- pdc.somethingorother
+  can_send:
+  - pdc.compose
diff --git a/roles/pdc/frontend/templates/settings_local.py 
b/roles/pdc/frontend/templates/settings_local.py
index 2d021a5..256260c 100644
--- a/roles/pdc/frontend/templates/settings_local.py
+++ b/roles/pdc/frontend/templates/settings_local.py
@@ -10,6 +10,11 @@
 #   settings, please remember to update your settings_local.py
 #   when the items you extended got updated in settings.py.
 
+# Turn on the fedmsg publishing plugin.
+MESSAGE_BUS = {
+'MLP': 'fedmsg',  # MLP: Messaging Library Package
+}
+
 REST_FRAMEWORK = {
 'DEFAULT_AUTHENTICATION_CLASSES': (
 'pdc.apps.auth.authentication.TokenAuthenticationWithChangeSet',


signature.asc
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Freeze Break Request: Turn on fedmsg for PDC

[Kevin Fenzi]

On Wed, 16 Mar 2016 10:10:39 -0400
Ralph Bean  wrote:

> We currently use a fedmsg-driven daemon to update PDC about stuff that
> gets composed by pungi.
> 
> This patch turns on a new layer that lets PDC publish its own messages
> when it gets updated (the software comes with fedmsg as one of four
> different message-publication methods it can use, which is cool!)
> 
> adamw wants to use these new messages to drive the validation event
> creation project.
> 
> The iptables rules and the fedmsg.d/ endpoints and the certs were all
> set up when I first stood up PDC.. this patch just turns on the
> plugin, and adds the one topic PDC produces to our fedmsg policy.
> 
> I'll have to do a master.yml playbook run of the 'fedmsgdconfig' tag,
> which will touch all hosts.. but I expect this will be "fine".
> 
> Can I get two +1's to push this out?

+1 here. 

Might run a -t fedmsgmonitor too after the fedmsgdconfig (to set the
monitoring perms right on all the sockets). 

kevin
--
> 
> 
> 
> diff --git a/inventory/group_vars/pdc-web
> b/inventory/group_vars/pdc-web index f07deb7..59073da 100644
> --- a/inventory/group_vars/pdc-web
> +++ b/inventory/group_vars/pdc-web
> @@ -29,6 +29,5 @@ fedmsg_certs:
>  - service: pdc
>owner: root
>group: apache
> -  # We don't have notifications from PDC yet, but when we do, add
> them here.
> -  #can_send:
> -  #- pdc.somethingorother
> +  can_send:
> +  - pdc.compose
> diff --git a/inventory/group_vars/pdc-web-stg
> b/inventory/group_vars/pdc-web-stg index 1c55f07..a7e45f9 100644
> --- a/inventory/group_vars/pdc-web-stg
> +++ b/inventory/group_vars/pdc-web-stg
> @@ -29,6 +29,5 @@ fedmsg_certs:
>  - service: pdc
>owner: root
>group: apache
> -  # We don't have notifications from PDC yet, but when we do, add
> them here.
> -  #can_send:
> -  #- pdc.somethingorother
> +  can_send:
> +  - pdc.compose
> diff --git a/roles/pdc/frontend/templates/settings_local.py
> b/roles/pdc/frontend/templates/settings_local.py index
> 2d021a5..256260c 100644 ---
> a/roles/pdc/frontend/templates/settings_local.py +++
> b/roles/pdc/frontend/templates/settings_local.py @@ -10,6 +10,11 @@
>  #   settings, please remember to update your settings_local.py
>  #   when the items you extended got updated in settings.py.
>  
> +# Turn on the fedmsg publishing plugin.
> +MESSAGE_BUS = {
> +'MLP': 'fedmsg',  # MLP: Messaging Library Package
> +}
> +
>  REST_FRAMEWORK = {
>  'DEFAULT_AUTHENTICATION_CLASSES': (
>  'pdc.apps.auth.authentication.TokenAuthenticationWithChangeSet',



pgp9gYKHTsvZD.pgp
Description: OpenPGP digital signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Freeze Break Request: Turn on fedmsg for PDC

[Pierre-Yves Chibon]

On Wed, Mar 16, 2016 at 10:10:39AM -0400, Ralph Bean wrote:
> We currently use a fedmsg-driven daemon to update PDC about stuff that
> gets composed by pungi.
> 
> This patch turns on a new layer that lets PDC publish its own messages
> when it gets updated (the software comes with fedmsg as one of four
> different message-publication methods it can use, which is cool!)
> 
> adamw wants to use these new messages to drive the validation event
> creation project.
> 
> The iptables rules and the fedmsg.d/ endpoints and the certs were all
> set up when I first stood up PDC.. this patch just turns on the
> plugin, and adds the one topic PDC produces to our fedmsg policy.
> 
> I'll have to do a master.yml playbook run of the 'fedmsgdconfig' tag,
> which will touch all hosts.. but I expect this will be "fine".
> 
> Can I get two +1's to push this out?
> 
> 
> 
> diff --git a/inventory/group_vars/pdc-web b/inventory/group_vars/pdc-web
> index f07deb7..59073da 100644
> --- a/inventory/group_vars/pdc-web
> +++ b/inventory/group_vars/pdc-web
> @@ -29,6 +29,5 @@ fedmsg_certs:
>  - service: pdc
>owner: root
>group: apache
> -  # We don't have notifications from PDC yet, but when we do, add them here.
> -  #can_send:
> -  #- pdc.somethingorother
> +  can_send:
> +  - pdc.compose
> diff --git a/inventory/group_vars/pdc-web-stg 
> b/inventory/group_vars/pdc-web-stg
> index 1c55f07..a7e45f9 100644
> --- a/inventory/group_vars/pdc-web-stg
> +++ b/inventory/group_vars/pdc-web-stg
> @@ -29,6 +29,5 @@ fedmsg_certs:
>  - service: pdc
>owner: root
>group: apache
> -  # We don't have notifications from PDC yet, but when we do, add them here.
> -  #can_send:
> -  #- pdc.somethingorother
> +  can_send:
> +  - pdc.compose
> diff --git a/roles/pdc/frontend/templates/settings_local.py 
> b/roles/pdc/frontend/templates/settings_local.py
> index 2d021a5..256260c 100644
> --- a/roles/pdc/frontend/templates/settings_local.py
> +++ b/roles/pdc/frontend/templates/settings_local.py
> @@ -10,6 +10,11 @@
>  #   settings, please remember to update your settings_local.py
>  #   when the items you extended got updated in settings.py.
>  
> +# Turn on the fedmsg publishing plugin.
> +MESSAGE_BUS = {
> +'MLP': 'fedmsg',  # MLP: Messaging Library Package
> +}
> +
>  REST_FRAMEWORK = {
>  'DEFAULT_AUTHENTICATION_CLASSES': (
>  'pdc.apps.auth.authentication.TokenAuthenticationWithChangeSet',

+1 for me as well

Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Freeze Break Request: Turn on fedmsg for PDC

[Ralph Bean]

This has been applied and is being pushed out.


signature.asc
Description: PGP signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org