When we setup things we didn't setup fedmsg in iad2 staging.
Now we are using it, so we should configure it until we get rid of it.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I think the only reason this worked in phx2 was because we also had a
firewall rule that was blocking the staging subnet on all prod machines.
Instead of doing that here, lets just make fedmsg only deal with the
staging hosts in staging. The only thing this might break is things that
aren't in staging_friendly that should be.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I don't think this is needed any more. openQA publishes natively
to fedora-messaging these days, and these groups never have done
anything there. ResultsDB still publishes to fedmsg, it seems,
but the new instances were not added to these groups and I don't
think we need/want to do that, we should just make sure they
have the necessary access via other more widely-used groups if
anything. (It seems like the restrictions these groups used to
affect have been - possibly temporarily - removed entirely at
present, but we can figure out any necessary changes there if the
restrictions are restored).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In ansible 2.8 the - character isn't supposed to be valid in group names.
While we could override this, might has well just bite the bullet and change it.
So, just switch all group names to use _ instead of -
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
