About JS framework
by Pierre-Yves Chibon
Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
Pierre
7 months, 2 weeks
Re: Deprecating Autocloud
by Sinny Kumari
On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral <kparal(a)redhat.com> wrote:
> On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari <ksinny(a)gmail.com> wrote:
>
>>
>>
>> On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin(a)scrye.com> wrote:
>>
>>> Or could we move f29+ all to whatever is replacing it? (taskotron?)
>>>
>>
>> It will be nice but I am not aware of any other system in place which
>> would
>> replace checks performed by autocloud.
>>
>> (CC'ed tflink and kparal)
>> Does taskotron provides capability to perform tests on Fedora cloud
>> Images like booting images and other basic checks?
>>
>
> Theoretically it is possible using nested virt. However, Taskotron is
> going away as well. The replacement is Fedora CI:
> https://docs.fedoraproject.org/en-US/ci/
>
Thanks kamil! yeah, it doesn't make sense to move to Taskotron if it is
going to be deprecated as well.
> I recommend to ask in the CI list:
> https://lists.fedoraproject.org/archives/list/ci%40lists.fedoraproject.org/
>
> It should be possible for them to provide the infrastructure you need.
>
Hmm, I am not very sure if we should spend time investigating and setting
up alternative
to autocloud unless we have usecases for long run. Fedora Atomic Host Two
Week releases ends with F29 EOL.
--
http://sinny.io/
3 years, 6 months
[PATCH] Add a nagios check for each rabbitmq server
by Jeremy Cline
Commit eae92f73e95 installed the nagios scripts[0] that are packaged for
epel7-infra on the RabbitMQ hosts. This is an attempt to use them with
nagios. I don't know anything about nagios though, so I have no idea if
this is even close to right, or if it works.
[0] https://github.com/nagios-plugins-rabbitmq/nagios-plugins-rabbitmq
Signed-off-by: Jeremy Cline <jcline(a)redhat.com>
---
roles/nagios_client/tasks/main.yml | 15 +++++++++++++
.../templates/check_rabbitmq_server.cfg.j2 | 1 +
roles/nagios_server/tasks/main.yml | 22 +++++++++++++++++++
.../nrpe/check_rabbitmq_server.cfg.j2 | 1 +
4 files changed, 39 insertions(+)
create mode 100644 roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
create mode 100644 roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
diff --git a/roles/nagios_client/tasks/main.yml b/roles/nagios_client/tasks/main.yml
index 0259a43ca..65a60a7c3 100644
--- a/roles/nagios_client/tasks/main.yml
+++ b/roles/nagios_client/tasks/main.yml
@@ -233,6 +233,21 @@
tags:
- nagios_client
+- name: install nrpe checks for the RabbitMQ cluster
+ template:
+ src: "{{ item }}.j2"
+ dest: "/etc/nrpe.d/{{ item }}"
+ owner: root
+ group: root
+ mode: 0600
+ with_items:
+ - check_rabbitmq_server.cfg
+ when: inventory_hostname.startswith('rabbitmq')
+ notify:
+ - restart nrpe
+ tags:
+ - nagios_client
+
- name: nrpe service start
service: name=nrpe state=started enabled=true
tags:
diff --git a/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2 b/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
new file mode 100644
index 000000000..498a8757e
--- /dev/null
+++ b/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
@@ -0,0 +1 @@
+command[check_nrpe_check_rabbitmq_server]=exec /usr/lib64/nagios/plugins-rabbitmq/check_rabbitmq_server -H localhost --password "{{ (env == 'production')|ternary(rabbitmq_monitoring_password_production, rabbitmq_monitoring_password_staging) }}" --user nagios-monitoring
diff --git a/roles/nagios_server/tasks/main.yml b/roles/nagios_server/tasks/main.yml
index 2d6d50c31..f61584ed6 100644
--- a/roles/nagios_server/tasks/main.yml
+++ b/roles/nagios_server/tasks/main.yml
@@ -110,6 +110,28 @@
- config
- nagios_server
+- name: Ensure the nrpe.d directory exists for nrpe configs
+ file:
+ dest: /etc/nrpe.d
+ state: directory
+ tags:
+ - nagios_server
+
+- name: Add nrpe configurations to /etc/nrpe.d
+ template:
+ src: "/nrpe/{{ item }}.j2"
+ dest: "/etc/nrpe.d/{{ item }}"
+ owner: root
+ group: root
+ mode: 0600
+ with_items:
+ - check_rabbitmq_server.cfg
+ notify:
+ - restart nrpe
+ tags:
+ - config
+ - nagios_server
+
## Copy over the nagios configs
- name: Copy /etc/nagios/conf.d/*cfg files
copy: src=nagios/configs/{{ item }} dest=/etc/nagios/conf.d/{{ item }}
diff --git a/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2 b/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
new file mode 100644
index 000000000..498a8757e
--- /dev/null
+++ b/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
@@ -0,0 +1 @@
+command[check_nrpe_check_rabbitmq_server]=exec /usr/lib64/nagios/plugins-rabbitmq/check_rabbitmq_server -H localhost --password "{{ (env == 'production')|ternary(rabbitmq_monitoring_password_production, rabbitmq_monitoring_password_staging) }}" --user nagios-monitoring
--
2.21.0
3 years, 10 months
taiga and fas login auth api integration
by Manas Mangaonkar
Hey,
Gsoc Intern here,want to fetch auth token for the user from
team.fedoraproject.taiga via the api to do stuff but it seems there is
no integration on the api end. Would love some more information about
it.
Another thing i noticed is one should be able to login via the normal
login via api even if the user is registered using fas.
- Manas(Pac23)
3 years, 11 months
pastebin plans
by Kevin Fenzi
Greetings.
We are currently running modernpaste for paste.fedoraproject.org.
It's pretty dead upstream. The primary maintainer said they wanted to
make a v2 version that was a complete re-write. That was about a year
ago and nothing has happened since. ;( We have several outstanding
issues against it and some folks don't really like it. It's one of the
few things left we have that is using mariadb instead of postgres.
It collects spam and has to be cleaned up all the time.
So, we need a plan. I think our options are:
1) Just keep using modernpaste and hope it stays working/secure.
2) Reach out to CentOS folks and see if we can work out some way to
share a pastebin. Either rebrand things for both, have some way of
branding per virthost or at least run the same code so we can share
knowledge about it.
3) Just stop providing a pastebin and ask people to use any of the other
ones out there.
4) Find another supported open source one and run it in OpenShift.
(perhaps the community openshift since it should have a low SLE)
5) Your clever idea here.
Thoughts?
kevin
3 years, 12 months
Proposed Meeting Agenda for 2019-05-30
by Stephen John Smoogen
The infrastructure team will be having its weekly meeting tomorrow,
2019-05-30 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see:
https://fedoraproject.org/wiki/Gobby )
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info
and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2019-05-30)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk
mkonecny abompard bowlofeggs
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to
discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info bowlofeggs will be going on extended leave in June
#info nirik will be on leave from 2019-06-03 to 2019-06-07
#info many people will be at a community platform engineering f2f
2019-06-10 to 14
#info Flock2Fedora 2019-08-08 -> 2019-08-11
#info bodhi 4.0.0 was deployed to production. There is a known
incompatibility between the bodhi 3 client and bodhi 4 server:
https://pagure.io/fesco/issue/2137
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk
about
as a group and come up with some consensus /suor decision or just
brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Oncall
#info https://fedoraproject.org/wiki/Infrastructure/Oncall
#info relrod is on call from 2019-05-23 -> 2019-05-30
#info smooge is on call from 2019-05-30 -> 2019-06-06
#info no one is on call from 2019-06-06 -> 2019-06-20
#info pingou is on call from 2019-06-20 -> 2019-06-27
#info Summary of last week: (from relrod )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
=====
Put all topics for discussion under here
=====
Here we will discuss any apprentice questions, try and match up people
looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or
setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In
the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
4 years
Re: Bodhi 4.0.0 deployed, one known issue so far
by Randy Barlow
On Tue, 2019-05-28 at 17:41 -0400, Dan Čermák wrote:
> I just tried to submit an update via `fedpkg update` but got a
> failure
> via the cli:
> $ fedpkg update
> Could not execute update: Could not generate update request:
> 'anonymous'
> A copy of the filled in template is saved as bodhi.template.last
>
> Nevertheless the update got submitted and is available on Bodhi (it's
> this one:
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e).
Hi Dan!
I presume you are using a Bodhi 2 or 3 client there? This is a known
compatibility issue between the Bodhi 3 client and the Bodhi 4 server:
https://bugzilla.redhat.com/show_bug.cgi?id=1714950
There's a FESCo ticket where we are discussing what to do about it. I'm
kind of undecided between putting Bodhi 4 into Fedora 29+ (and maybe
even EPEL 7, which may be tricky due to dependencies) and making a
Bodhi 3.15 that can talk to Bodhi 4 server (downside is that this will
require more effort on my part, and I have a lot on my plate ☹). Feel
free to voice your opinions on the FESCo ticket!
4 years
