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, 5 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
Funnelling newcomers to Fedora Join: taking over newbie group
membership
by Ankur Sinha
Hello,
We've written a proposal here[1] to move to a more people-centric workflow
for newcomers. The idea is that instead of asking newcomers to dive in
to tasks as we do now, we'll make them get to know the people in the
community first. You can read more on the ticket.
As part of this, we were hoping to set up an FAS group for newbies, and
let the Join SIG add newcomers to it while they find their teams and
tasks of interest in the community.
In this workflow, infra would no longer have to maintain the wikiedit
group as they do so now. It really shouldn't be infra's job in the first
place :)
What do we think? Please leave your comments on the ticket. The plan is
only a proposal and will change as we get more feedback from the
community.
[1] https://pagure.io/mindshare/issue/147
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
3 years, 10 months
Greenwave release
by Giulia Naponiello
Hello,
I'm going to release now to a new version of Greenwave (1.2.1).
It shouldn't take long.
I'll let you know once is done.
Cheers
Giulia
3 years, 10 months