Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

Merge branch 'master' of /git/ansible

Browse source
This commit is contained in:
Rick Elrod 2015-05-12 22:11:45 +00:00
commit 944541b913
14 changed files with 342 additions and 271 deletions
Download patch file Download diff file Expand all files Collapse all files

10
inventory/group_vars/koschei
View file

@ -7,17 +7,19 @@ num_cpus: 4
# for systems that do not match the above - specify the same parameter in # for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file # the host_vars/$hostname file
koschei_topurl: https://apps.fedoraproject.org/koschei
koschei_pgsql_hostname: FIXME koschei_pgsql_hostname: FIXME
koschei_koji_hub: koji02.phx2.fedoraproject.org koschei_koji_hub: koji02.phx2.fedoraproject.org
koschei_kojipkgs: kojipkgs.fedoraproject.org koschei_kojipkgs: kojipkgs01.phx2.fedoraproject.org
koschei_koji_web: koji.fedoraproject.org
koschei_koji_tag: f23 koschei_koji_tag: f23
koschei_openid_provider: id.fedoraproject.org koschei_openid_provider: id.fedoraproject.org
koschei_bugzilla: bugzilla.redhat.com
tcp_ports: [ 80, 443, tcp_ports: [ 80, 443,
# These 9 are for fedmsg right now, but we need to check with the koschei # These 3 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
# devs if this is enough or too much. See also /etc/fedmsg.d/endpoints.py 3000, 3001, 3002,
3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008,
] ]
custom_rules: [ custom_rules: [

11
inventory/group_vars/koschei-stg
View file

@ -7,16 +7,19 @@ num_cpus: 2
# for systems that do not match the above - specify the same parameter in # for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file # the host_vars/$hostname file
koschei_topurl: https://apps.stg.fedoraproject.org/koschei
koschei_pgsql_hostname: db01.stg.phx2.fedoraproject.org koschei_pgsql_hostname: db01.stg.phx2.fedoraproject.org
koschei_koji_hub: koji01.stg.phx2.fedoraproject.org koschei_koji_hub: koji01.stg.phx2.fedoraproject.org
koschei_kojipkgs: koji01.stg.phx2.fedoraproject.org koschei_kojipkgs: koji01.stg.phx2.fedoraproject.org
koschei_koji_web: koji.stg.fedoraproject.org
koschei_koji_tag: f23 koschei_koji_tag: f23
koschei_openid_provider: id.fedoraproject.org koschei_openid_provider: id.stg.fedoraproject.org
koschei_bugzilla: partner-bugzilla.redhat.com
tcp_ports: [ 80, 443, tcp_ports: [ 80, 443,
# These 9 are for fedmsg right now, but we need to check with the koschei # These 3 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
# devs if this is enough or too much. See also /etc/fedmsg.d/endpoints.py 3000, 3001, 3002,
3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008,
] ]
custom_rules: [ custom_rules: [

2
playbooks/hosts/fed-cloud09.cloud.fedoraproject.org.yml
View file

@ -626,6 +626,7 @@
- { name: twisted, email: 'buildbot@twistedmatrix.com', tenant: pythonbots, password: "{{twisted_password}}" } - { name: twisted, email: 'buildbot@twistedmatrix.com', tenant: pythonbots, password: "{{twisted_password}}" }
- { name: vgologuz, email: 'vgologuz@redhat.com', tenant: copr, password: "{{vgologuz_password}}" } - { name: vgologuz, email: 'vgologuz@redhat.com', tenant: copr, password: "{{vgologuz_password}}" }
- { name: roshi, email: 'roshi@fedoraproject.org', tenant: qa, password: "{{roshi_password}}" } - { name: roshi, email: 'roshi@fedoraproject.org', tenant: qa, password: "{{roshi_password}}" }
- { name: maxamillion, email: 'maxamillion@fedoraproject.org', tenant: infrastructure, password: "{{maxamillion_password}}" }
- name: upload SSH keys for users - name: upload SSH keys for users
nova_keypair: nova_keypair:
auth_url="https://{{controller_hostname}}:35357/v2.0" auth_url="https://{{controller_hostname}}:35357/v2.0"
@ -642,6 +643,7 @@
- { username: gholms, name: gholms, tenant: cloudintern, password: "{{gholms_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas gholms') }}" } - { username: gholms, name: gholms, tenant: cloudintern, password: "{{gholms_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas gholms') }}" }
- { username: jskladan, name: jskladan, tenant: qa, password: "{{jskladan_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas jskladan') }}" } - { username: jskladan, name: jskladan, tenant: qa, password: "{{jskladan_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas jskladan') }}" }
- { username: kevin, name: kevin, tenant: infrastructure, password: "{{kevin_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas kevin') }}" } - { username: kevin, name: kevin, tenant: infrastructure, password: "{{kevin_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas kevin') }}" }
- { username: maxamillion, name: maxamillion, tenant: infrastructure, password: "{{maxamillion_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas maxamillion') }}" }
- { username: laxathom, name: laxathom, tenant: infrastructure, password: "{{laxathom_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas laxathom') }}" } - { username: laxathom, name: laxathom, tenant: infrastructure, password: "{{laxathom_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas laxathom') }}" }
- { username: mattdm, name: mattdm, tenant: infrastructure, password: "{{mattdm_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas mattdm') }}" } - { username: mattdm, name: mattdm, tenant: infrastructure, password: "{{mattdm_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas mattdm') }}" }
- { username: msuchy, name: msuchy, tenant: copr, password: "{{msuchy_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas msuchy') }}" } - { username: msuchy, name: msuchy, tenant: copr, password: "{{msuchy_password}}", public_key: "{{ lookup('pipe', '/srv/web/infra/ansible/scripts/auth-keys-from-fas msuchy') }}" }

3
playbooks/hosts/koschei.cloud.fedoraproject.org.yml
View file

@ -23,13 +23,16 @@
- /srv/web/infra/ansible/vars/{{ ansible_distribution }}.yml - /srv/web/infra/ansible/vars/{{ ansible_distribution }}.yml
vars: vars:
- koschei_topurl: http://koschei.cloud.fedoraproject.org
- koschei_pgsql_hostname: localhost - koschei_pgsql_hostname: localhost
- koscheiuser_db_password: "{{ koschei_pgsql_password }}" - koscheiuser_db_password: "{{ koschei_pgsql_password }}"
- koscheiadmin_db_password: "{{ koschei_pgsql_password }}" - koscheiadmin_db_password: "{{ koschei_pgsql_password }}"
- koschei_koji_hub: koji.fedoraproject.org - koschei_koji_hub: koji.fedoraproject.org
- koschei_kojipkgs: kojipkgs.fedoraproject.org - koschei_kojipkgs: kojipkgs.fedoraproject.org
- koschei_koji_web: koji.fedoraproject.org
- koschei_koji_tag: f23 - koschei_koji_tag: f23
- koschei_openid_provider: id.fedoraproject.org - koschei_openid_provider: id.fedoraproject.org
- koschei_bugzilla: bugzilla.redhat.com
roles: roles:
- koschei - koschei

503
roles/apps-fp-o/files/apps.yaml
View file

@ -7,140 +7,115 @@ data:
<em>huge</em>; this page details only the public facing portion of <em>huge</em>; this page details only the public facing portion of
it all. Explore! it all. Explore!
children: children:
- name: In Development - name: Accounts
data: data:
description: > description: >
These are the apps that we're working on, but that aren't quite Tools for everybody -- use these things to manage your Fedora
ready for prime-time yet. Try and use them, and report bugs when Account.
they're broken -- it's a big help!.
Check back here from time to time, as this section will change.
children: children:
- name: Koschei - name: Ambassadors Map
data: data:
url: http://koschei.cloud.fedoraproject.org url: http://fedoraproject.org/membership-map/ambassadors.html
package_url: http://koschei.cloud.fedoraproject.org/package/{package}
description: > description: >
Koschei is a continuous integration system for RPM packages. It Ambassadors are the representatives of Fedora. Ambassadors
tracks dependency changes done in Koji repositories and rebuilds ensure the public understand Fedora's principles and the work
packages whose dependencies change. It can help packagers to that Fedora is doing. Additionally Ambassadors are responsible
detect failures early and provide relevant information to narrow for helping to grow the contributor base, and to act as a
down the cause. liaison between other FLOSS projects and the Fedora community.
- name: Release Monitoring
data:
url: http://release-monitoring.org
package_url: https://release-monitoring.org/projects/search/?pattern={package}
description: >
Code named <a
href="https://github.com/fedora-infra/anitya">anitya</a>, this
project is slated to replace <a
href="https://fedoraproject.org/wiki/Upstream_Release_Monitoring">the
old wiki page</a> for Upstream Release Monitoring. It will
track upstream tarball locations and publish notifications to
the fedmsg bus when new ones are found. Other daemons will
then be responsible for filing bugs, attempting to
automatically build packages, perform some preliminary QA
checks, etc..
- name: Jenkins
data:
url: http://jenkins.cloud.fedoraproject.org
description: >
Our own continuous integration (CI) service! It works now and
you can use it.. we just don't yet give it the same kind of
guarantees that we give our other apps. Look forwards to us
promoting it soon..
- name: faitout
data:
url: http://209.132.184.152/faitout/
description: >
Provides access to temporary postgresql databases. This
database can be used for unit-test thus reducing the
differences between testing and production environment.
- name: Infrastructure This thing is a map of where all the <a
data: href="https://fedoraproject.org/wiki/Ambassadors">Fedora
description: > Ambassadors</a> live showing just how vibrant the Fedora
Tools for sysadmins -- the people who run the servers that run Community really is. (It's easy to <a
Fedora (and otherwise). href="https://fedoraproject.org/wiki/Fedora_ambassadors_map">add
children: yourself</a> to the map too, if you can't find yourself on it.)
- name: GeoIP - name: FedoraPeople
data: data:
url: https://geoip.fedoraproject.org url: https://fedorapeople.org
user_url: https://{user}.fedorapeople.org
status_mappings: ['people']
description: > description: >
A simple web service running <a Being a community member you gain access to fedorapeople which
href="https://github.com/fedora-infra/geoip-city-wsgi">geoip-city-wsgi</a> provides you with a space on the web where you can upload
that will return geoip information to you. files to share them with the community.
- name: Easyfix - name: FAS
data: data:
url: http://fedoraproject.org/easyfix url: http://admin.fedoraproject.org/accounts
user_url: https://admin.fedoraproject.org/accounts/view/{user}
status_mappings: ['fas']
description: > description: >
A list of easy-to-fix problems for the different projects in The Fedora Account System. Update your profile
Fedora. Interested in getting into helping out with sysadmin information and apply for membership in groups.
work or web application development? This should be useful - name: Notifications
to you.
- name: DataGrepper
data: data:
icon: fedmsg.png icon: fedmsg.png
url: https://apps.fedoraproject.org/datagrepper url: https://apps.fedoraproject.org/notifications
package_url: https://apps.fedoraproject.org/datagrepper/raw?package={package}
user_url: https://apps.fedoraproject.org/datagrepper/raw?user={user}
status_mappings: ['fedmsg'] status_mappings: ['fedmsg']
description: > description: >
DataGrepper is an HTTP API for querying the datanommer Centrally managed preferences for Fedora Infrastructure
database. You can use it to dig into the history of the notifications to your inbox, irc client, and mobile device.
<a href="http://fedmsg.com">fedmsg</a> message bus. You - name: Badges
can grab events by username, by package, by message status_mappings: ['badges']
source, by topic... you name it.
- name: Status
data: data:
icon: status-good.png icon: badges.png
url: http://status.fedoraproject.org url: https://badges.fedoraproject.org
user_url: https://badges.fedoraproject.org/user/{user}
description: > description: >
Sometimes the Fedora Infrastructure team messes up (or An achievements system for Fedora Contributors! "Badges"
lightning strikes our datacenter(s)). Sorry about that. are awarded based on activity in the community. Can you
You can use this website to check the status. Is it unlock them all?
"down for everyone, or just me?"<br/>Notice the favicon You can export your badges to Mozilla's
in your browser tab. It changes based on the status, <a href="http://openbadges.org">Open Badges
so if you keep this open you can check back to it at a Infrastructure</a>
glance. - name: Content
- name: MirrorManager data:
description: >
Tools for wordsmiths -- the apps that store and archive the troves
of content that Fedora authors produce. Blog posts, the wiki, and
more..
children:
- name: Ask Fedora
data: data:
icon: downloads.png icon: ask_fedora.png
url: http://mirrors.fedoraproject.org url: https://ask.fedoraproject.org/
status_mappings: ['mirrormanager', 'mirrorlist'] status_mappings: ['ask']
description: > description: >
Fedora is distributed to millions of systems globally. Any question at all about Fedora? Ask it here.
This would not be possible without the donations of time, - name: The Wiki
disk space, and bandwidth by hundreds of volunteer system
administrators and their companies or institutions. Your
fast download experience is made possible by these
donations. The list on the <strong>MirrorManager</strong>
site is dynamically generated every hour, listing only
up-to-date mirrors.
- name: Nagios
data: data:
icon: nagios-logo.png icon: mediawiki.png
url: http://admin.fedoraproject.org/nagios url: http://fedoraproject.org/wiki
user_url: https://fedoraproject.org/wiki/User:{user}
status_mappings: ['wiki']
description: > description: >
"Is telia down?" The answer can most definitively be Maintain your own user profile page, contribute to
found here (and in detail). The Fedora Infrastructure documents about features, process, and governance.
team uses Nagios to monitor the servers that serve - name: Fedora Magazine
Fedora. Accessing most details requires membership
in the <em>sysadmin</em> group.
- name: Collectd
data: data:
icon: collectd.png icon: magazine.png
url: http://admin.fedoraproject.org/collectd/ url: http://fedoramagazine.org
description: > description: >
Tracks and displays statistics on the Fedora Fedora Magazine is a WordPress-based site which delivers all
Infrastructure machines over time. Useful for debugging the news of the Fedora Community. (It replaces the previous
ineffeciencies and problems. Fedora Weekly News.)
- name: HAProxy - name: The Planet
data: data:
url: http://admin.fedoraproject.org/haproxy/proxy1 icon: planet_logo.png
url: http://planet.fedoraproject.org
description: > description: >
Shows the health of our proxies. How many bytes? The planet is a blog aggregator, a space accessible to you
Concurrent sessions? Health checks? as a community member where you can express your opinion and
talk about what you are doing for Fedora.
- name: Docs
data:
url: https://docs.fedoraproject.org
status_mappings: ['docs']
description: >
RTFM! Everything you could ever want to know.
Probably the best place to find documentation about Fedora,
including the changes between releases (and a big kudos to
the translation teams to keep this resource up to date in
the different languages!)
- name: QA - name: QA
data: data:
description: > description: >
@ -271,148 +246,6 @@ children:
Among its many and varied functions is logging IRC meetings, Among its many and varied functions is logging IRC meetings,
the archives of which you can find here. the archives of which you can find here.
- name: Upstream
data:
description: >
Tools for <a
href="https://fedoraproject.org/wiki/Staying_close_to_upstream_projects">upstream</a>
developers -- because we love you.
children:
- name: github2fedmsg
data:
icon: github.png
url: https://apps.fedoraproject.org/github2fedmsg
status_mappings: ['fedmsg']
description: >
github2fedmsg is a web service that bridges upstream
development activity from <a
href="https://github.com">GitHub</a> into the <a
href="http://fedmsg.com">Fedora Infrastructure message
bus</a>. Visit the self-service dashboard to toggle the
status of your repositories.
- name: Fedora Hosted
data:
icon: trac.png
url: http://fedorahosted.org
status_mappings: ['fedorahosted']
description: >
Fedora is dedicated to open source software. This
commitment can extend beyond regular Fedora offerings.<br/>
<strong>Fedora Hosted</strong> is our most feature rich
hosting solution. It includes an scm, trac instance,
release dir, account system for access control, etc.
This is our most common hosting option. When most groups
want hosting, this is what they want.
- name: Accounts
data:
description: >
Tools for everybody -- use these things to manage your Fedora
Account.
children:
- name: Ambassadors Map
data:
url: http://fedoraproject.org/membership-map/ambassadors.html
description: >
Ambassadors are the representatives of Fedora. Ambassadors
ensure the public understand Fedora's principles and the work
that Fedora is doing. Additionally Ambassadors are responsible
for helping to grow the contributor base, and to act as a
liaison between other FLOSS projects and the Fedora community.
This thing is a map of where all the <a
href="https://fedoraproject.org/wiki/Ambassadors">Fedora
Ambassadors</a> live showing just how vibrant the Fedora
Community really is. (It's easy to <a
href="https://fedoraproject.org/wiki/Fedora_ambassadors_map">add
yourself</a> to the map too, if you can't find yourself on it.)
- name: FedoraPeople
data:
url: https://fedorapeople.org
user_url: https://{user}.fedorapeople.org
status_mappings: ['people']
description: >
Being a community member you gain access to fedorapeople which
provides you with a space on the web where you can upload
files to share them with the community.
- name: FAS
data:
url: http://admin.fedoraproject.org/accounts
user_url: https://admin.fedoraproject.org/accounts/view/{user}
status_mappings: ['fas']
description: >
The Fedora Account System. Update your profile
information and apply for membership in groups.
- name: Notifications
data:
icon: fedmsg.png
url: https://apps.fedoraproject.org/notifications
status_mappings: ['fedmsg']
description: >
Centrally managed preferences for Fedora Infrastructure
notifications to your inbox, irc client, and mobile device.
- name: Badges
status_mappings: ['badges']
data:
icon: badges.png
url: https://badges.fedoraproject.org
user_url: https://badges.fedoraproject.org/user/{user}
description: >
An achievements system for Fedora Contributors! "Badges"
are awarded based on activity in the community. Can you
unlock them all?
You can export your badges to Mozilla's
<a href="http://openbadges.org">Open Badges
Infrastructure</a>
- name: Content
data:
description: >
Tools for wordsmiths -- the apps that store and archive the troves
of content that Fedora authors produce. Blog posts, the wiki, and
more..
children:
- name: Ask Fedora
data:
icon: ask_fedora.png
url: https://ask.fedoraproject.org/
status_mappings: ['ask']
description: >
Any question at all about Fedora? Ask it here.
- name: The Wiki
data:
icon: mediawiki.png
url: http://fedoraproject.org/wiki
user_url: https://fedoraproject.org/wiki/User:{user}
status_mappings: ['wiki']
description: >
Maintain your own user profile page, contribute to
documents about features, process, and governance.
- name: Fedora Magazine
data:
icon: magazine.png
url: http://fedoramagazine.org
description: >
Fedora Magazine is a WordPress-based site which delivers all
the news of the Fedora Community. (It replaces the previous
Fedora Weekly News.)
- name: The Planet
data:
icon: planet_logo.png
url: http://planet.fedoraproject.org
description: >
The planet is a blog aggregator, a space accessible to you
as a community member where you can express your opinion and
talk about what you are doing for Fedora.
- name: Docs
data:
url: https://docs.fedoraproject.org
status_mappings: ['docs']
description: >
RTFM! Everything you could ever want to know.
Probably the best place to find documentation about Fedora,
including the changes between releases (and a big kudos to
the translation teams to keep this resource up to date in
the different languages!)
- name: Packaging - name: Packaging
data: data:
description: > description: >
@ -511,3 +344,169 @@ children:
You can read more about <a You can read more about <a
href="https://fedoraproject.org/wiki/Darkserver">why you href="https://fedoraproject.org/wiki/Darkserver">why you
might want to use it</a> or you can just click below to... might want to use it</a> or you can just click below to...
- name: Upstream
data:
description: >
Tools for <a
href="https://fedoraproject.org/wiki/Staying_close_to_upstream_projects">upstream</a>
developers -- because we love you.
children:
- name: Release Monitoring
data:
url: http://release-monitoring.org
package_url: https://release-monitoring.org/projects/search/?pattern={package}
description: >
Code named <a
href="https://github.com/fedora-infra/anitya">anitya</a>, this
project is slated to replace <a
href="https://fedoraproject.org/wiki/Upstream_Release_Monitoring">the
old wiki page</a> for Upstream Release Monitoring. It will
track upstream tarball locations and publish notifications to
the fedmsg bus when new ones are found. Other daemons will
then be responsible for filing bugs, attempting to
automatically build packages, perform some preliminary QA
checks, etc..
- name: github2fedmsg
data:
icon: github.png
url: https://apps.fedoraproject.org/github2fedmsg
status_mappings: ['fedmsg']
description: >
github2fedmsg is a web service that bridges upstream
development activity from <a
href="https://github.com">GitHub</a> into the <a
href="http://fedmsg.com">Fedora Infrastructure message
bus</a>. Visit the self-service dashboard to toggle the
status of your repositories.
- name: Fedora Hosted
data:
icon: trac.png
url: http://fedorahosted.org
status_mappings: ['fedorahosted']
description: >
Fedora is dedicated to open source software. This
commitment can extend beyond regular Fedora offerings.<br/>
<strong>Fedora Hosted</strong> is our most feature rich
hosting solution. It includes an scm, trac instance,
release dir, account system for access control, etc.
This is our most common hosting option. When most groups
want hosting, this is what they want.
- name: Infrastructure
data:
description: >
Tools for sysadmins -- the people who run the servers that run
Fedora (and otherwise).
children:
- name: GeoIP
data:
url: https://geoip.fedoraproject.org
description: >
A simple web service running <a
href="https://github.com/fedora-infra/geoip-city-wsgi">geoip-city-wsgi</a>
that will return geoip information to you.
- name: Easyfix
data:
url: http://fedoraproject.org/easyfix
description: >
A list of easy-to-fix problems for the different projects in
Fedora. Interested in getting into helping out with sysadmin
work or web application development? This should be useful
to you.
- name: DataGrepper
data:
icon: fedmsg.png
url: https://apps.fedoraproject.org/datagrepper
package_url: https://apps.fedoraproject.org/datagrepper/raw?package={package}
user_url: https://apps.fedoraproject.org/datagrepper/raw?user={user}
status_mappings: ['fedmsg']
description: >
DataGrepper is an HTTP API for querying the datanommer
database. You can use it to dig into the history of the
<a href="http://fedmsg.com">fedmsg</a> message bus. You
can grab events by username, by package, by message
source, by topic... you name it.
- name: Status
data:
icon: status-good.png
url: http://status.fedoraproject.org
description: >
Sometimes the Fedora Infrastructure team messes up (or
lightning strikes our datacenter(s)). Sorry about that.
You can use this website to check the status. Is it
"down for everyone, or just me?"<br/>Notice the favicon
in your browser tab. It changes based on the status,
so if you keep this open you can check back to it at a
glance.
- name: MirrorManager
data:
icon: downloads.png
url: http://mirrors.fedoraproject.org
status_mappings: ['mirrormanager', 'mirrorlist']
description: >
Fedora is distributed to millions of systems globally.
This would not be possible without the donations of time,
disk space, and bandwidth by hundreds of volunteer system
administrators and their companies or institutions. Your
fast download experience is made possible by these
donations. The list on the <strong>MirrorManager</strong>
site is dynamically generated every hour, listing only
up-to-date mirrors.
- name: Nagios
data:
icon: nagios-logo.png
url: http://admin.fedoraproject.org/nagios
description: >
"Is telia down?" The answer can most definitively be
found here (and in detail). The Fedora Infrastructure
team uses Nagios to monitor the servers that serve
Fedora. Accessing most details requires membership
in the <em>sysadmin</em> group.
- name: Collectd
data:
icon: collectd.png
url: http://admin.fedoraproject.org/collectd/
description: >
Tracks and displays statistics on the Fedora
Infrastructure machines over time. Useful for debugging
ineffeciencies and problems.
- name: HAProxy
data:
url: http://admin.fedoraproject.org/haproxy/proxy1
description: >
Shows the health of our proxies. How many bytes?
Concurrent sessions? Health checks?
- name: In Development
data:
description: >
These are the apps that we're working on, but that aren't quite
ready for prime-time yet. Try and use them, and report bugs when
they're broken -- it's a big help!.
Check back here from time to time, as this section will change.
children:
- name: Koschei
data:
url: http://koschei.cloud.fedoraproject.org
package_url: http://koschei.cloud.fedoraproject.org/package/{package}
description: >
Koschei is a continuous integration system for RPM packages. It
tracks dependency changes done in Koji repositories and rebuilds
packages whose dependencies change. It can help packagers to
detect failures early and provide relevant information to narrow
down the cause.
- name: Jenkins
data:
url: http://jenkins.cloud.fedoraproject.org
description: >
Our own continuous integration (CI) service! It works now and
you can use it.. we just don't yet give it the same kind of
guarantees that we give our other apps. Look forwards to us
promoting it soon..
- name: faitout
data:
url: http://209.132.184.152/faitout/
description: >
Provides access to temporary postgresql databases. This
database can be used for unit-test thus reducing the
differences between testing and production environment.

2
roles/easyfix/gather/files/gather_easyfix.py
View file

@ -252,7 +252,7 @@ def main():
ticketobj.id = ticket[0] ticketobj.id = ticket[0]
ticketobj.title = ticket[3]['summary'] ticketobj.title = ticket[3]['summary']
ticketobj.url = 'https://fedorahosted.org/%s/ticket/%s' %( ticketobj.url = 'https://fedorahosted.org/%s/ticket/%s' %(
project, ticket[0]) project.name, ticket[0])
ticketobj.status = ticket[3]['status'] ticketobj.status = ticket[3]['status']
ticketobj.type = ticket[3]['type'] ticketobj.type = ticket[3]['type']
ticketobj.component = ticket[3]['component'] ticketobj.component = ticket[3]['component']

9
roles/easyfix/gather/tasks/main.yml
View file

@ -6,11 +6,15 @@
action: file state=directory action: file state=directory
path=/srv/web/easyfix path=/srv/web/easyfix
owner=apache group=apache mode=0755 owner=apache group=apache mode=0755
tags:
- easyfix
- name: Create the easyfix configuration folder - name: Create the easyfix configuration folder
action: file state=directory action: file state=directory
path=/etc/fedora-gather-easyfix/ path=/etc/fedora-gather-easyfix/
owner=root group=root mode=0755 owner=root group=root mode=0755
tags:
- easyfix
## Install packages ## Install packages
@ -23,6 +27,7 @@
- python-bugzilla - python-bugzilla
tags: tags:
- packages - packages
- easyfix
## Install all files ## Install all files
@ -37,6 +42,7 @@
- jquery.ui.widget.js - jquery.ui.widget.js
tags: tags:
- files - files
- easyfix
- name: Install the easyfix template - name: Install the easyfix template
copy: > copy: >
@ -44,6 +50,7 @@
owner=root group=root mode=0644 owner=root group=root mode=0644
tags: tags:
- files - files
- easyfix
- name: Install the easyfix script - name: Install the easyfix script
copy: > copy: >
@ -51,6 +58,7 @@
owner=root group=root mode=0755 owner=root group=root mode=0755
tags: tags:
- files - files
- easyfix
## Install the cron job ## Install the cron job
@ -60,3 +68,4 @@
owner=root group=root mode=0644 owner=root group=root mode=0644
tags: tags:
- files - files
- easyfix

11
roles/fedmsg/base/templates/endpoints.py.j2
View file

@ -89,14 +89,13 @@ config = dict(
for i in range(2) for i in range(2)
], ],
# I'm not sure how many endpoints koschei needs. There are four backend # mizdebsk says he thinks we'll need three sockets. Two services
# processes.. i'm not sure how many of them publish messages and how # (koschei-resolver and koschei-polling) are only sending messages, one
# many threads each of them might have. And there's a wsgi frontend # service (koschei-watcher) can both send and receive them. The wsgi
# with 5 threads, but I don't think it publishes any messages. # webapp doesn't use fedmsg at all and all services are single-threaded
# TODO -- update this after talking with the koschei devs.
"koschei.koschei01": [ "koschei.koschei01": [
"tcp://koschei01.%s:30%02i" % (suffix, i) "tcp://koschei01.%s:30%02i" % (suffix, i)
for i in range(9) for i in range(3)
], ],
# koji is not listed here since it publishes to the fedmsg-relay # koji is not listed here since it publishes to the fedmsg-relay

7
roles/koschei/files/koschei.py Normal file
View file

@ -0,0 +1,7 @@
import socket
hostname = socket.gethostname().split('.', 1)[0]
config = {
"name": "koschei.%s" % hostname,
}

12
roles/koschei/tasks/main.yml
View file

@ -26,6 +26,18 @@
- koschei - koschei
- config - config
- name: install koschei fedmsg config
copy: src=koschei.py dest=/etc/fedmsg.d/koschei.py
notify:
- restart koschei-polling
- restart koschei-resolver
- restart koschei-scheduler
- restart koschei-watcher
tags:
- koschei
- config
- fedmsgdconfig
- name: install koji key and cert - name: install koji key and cert
copy: > copy: >
src="{{ private }}/files/koschei/koschei.pem" src="{{ private }}/files/koschei/koschei.pem"

4
roles/koschei/templates/config-admin.cfg.j2
View file

@ -2,9 +2,9 @@
config = { config = {
"database_config": { "database_config": {
"username": "koscheiadmin", "username": "koscheiadmin",
"unpriv_username": "koscheiuser",
"password": "{{ koscheiadmin_db_password }}", "password": "{{ koscheiadmin_db_password }}",
} },
"unpriv_db_username": "koscheiuser",
} }
# Local Variables: # Local Variables:

29
roles/koschei/templates/config.cfg.j2
View file

@ -12,7 +12,7 @@ config = {
"koji_config": { "koji_config": {
"server": "http://{{ koschei_koji_hub }}/kojihub", "server": "http://{{ koschei_koji_hub }}/kojihub",
"topurl": "http://{{ koschei_kojipkgs }}", "topurl": "http://{{ koschei_kojipkgs }}",
"weburl": "http://{{ koschei_koji_hub }}/koji", "weburl": "http://{{ koschei_koji_web }}/koji",
"cert": "/etc/koschei/koschei.pem", "cert": "/etc/koschei/koschei.pem",
"ca": "/etc/koschei/fedora-ca.cert", "ca": "/etc/koschei/fedora-ca.cert",
"server_ca": "/etc/koschei/fedora-ca.cert", "server_ca": "/etc/koschei/fedora-ca.cert",
@ -46,7 +46,11 @@ config = {
}, },
"services": { "services": {
"watcher": { "watcher": {
{% if env == 'staging' %}
"watchdog_interval": None, # there are almost no messages in stg
{% else %}
"watchdog_interval": 600, # in seconds "watchdog_interval": 600, # in seconds
{% endif %}
}, },
"polling": { "polling": {
"interval": 20 * 60, "interval": 20 * 60,
@ -107,6 +111,29 @@ config = {
"openid": { "openid": {
"openid_provider": "{{ koschei_openid_provider }}", "openid_provider": "{{ koschei_openid_provider }}",
}, },
"bugreport": {
"url": "https://{{ koschei_bugzilla }}/enter_bug.cgi?%s",
"template": {
"product": "Fedora",
"component": "{name}",
"version": "rawhide",
"short_desc": "{name}: FTBFS in rawhide",
"bug_file_loc": "{{ koschei_topurl }}/package/{name}",
"comment": """
Description of problem:
Package {name} fails to build from source in rawhide.
Version-Release number of selected component (if applicable):
{version}-{release}
Steps to Reproduce:
koji build --scratch {{ koschei_koji_tag }} {nvr}.{arch}.rpm
Additional info:
This package is tracked by Koschei. See:
{{ koschei_topurl }}/package/{name}"""
},
},
} }
# Local Variables: # Local Variables:

2
roles/nfs/server/files/koji01.stg.phx2.fedoraproject.org-exports
View file

@ -1 +1 @@
/mnt/fedora_koji 10.5.126.90(rw,no_root_squash) 10.5.126.14(rw,no_root_squash) 10.5.126.6(rw,no_root_squash) /mnt/fedora_koji 10.5.126.90(rw,no_root_squash) 10.5.126.14(rw,no_root_squash) 10.5.126.6(rw,no_root_squash) 10.5.126.221(ro,no_root_squash)

8
roles/pagure/tasks/main.yml
View file

@ -12,6 +12,14 @@
- pagure - pagure
- packages - packages
- name: Initialize postgres if necessary
command: /usr/bin/postgresql-setup initdb
creates=/var/lib/pgsql/data
notify:
- restart postgresql
tags:
- pagure
# Set-up gitolite # Set-up gitolite