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
1 year, 1 month
Meeting Agenda for 2018-11-29
by Stephen John Smoogen
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-11-08 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
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 (2018-11-29)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
= 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 tflink is on extended PTO
#info bodhi updated
#info fpdc with release info available in staging
(https://fpdc.stg.fedoraproject.org/api/v1/release) - cverna
= 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 nirik is on call from 2018-11-22->2018-11-29
#info smooge is on call from 2018-11-29->2018-12-06
#info ??? is on call from 2018-12-06->2018-12-13
#info Summary of last week: (from nirik )
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
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.
5 years
ansible: fedmsg-hub-3 support
by Adam Williamson
hey folks! just wanted to pass along a note about this change I made to
the infra scripts today:
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=6c39...
What I did was extend a bit of scaffolding that already exists to
handle fedmsg deployment differently if the host is in a group with
'python34-fedmsg' in its name (the 'python34' there is a EL-ism, but I
didn't want to change it) so it now also covers fedmsg-hub as well as
fedmsg-base.
Now, if a system is in a group with 'python34-fedmsg' in its name and
the 'fedmsg/hub' role is run on that system, instead of enabling the
'fedmsg-hub' service, it'll enable the 'fedmsg-hub-3' service. The
'restart fedmsg-hub' handler is also tweaked so it conditionally
restarts *both* 'fedmsg-hub.service' *and* 'fedmsg-hub-3.service' (this
seemed like the easiest solution to the service restart problem; as
we're using conditional-restart.sh, whichever isn't present will just
be ignored).
This should help with moving things from Python 2 fedmsg to Python 3
fedmsg. It should be relatively easy to extend to the other fedmsg
roles too, if desired - I didn't do that as I didn't want to change too
much, and fedmsg-hub is all I needed for the box I'm migrating.
Please let me know if you have any comments, concerns or suggestions
about this, thanks! I did ask around on IRC and it didn't seem like
anyone had a better idea or plan for doing this, so I just went
ahead...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years
NO INFRASTRUCTURE MEETING ON 2018-11-22
by Stephen John Smoogen
There will be no Infrastructure meeting on 2018-11-22. Please have a
good and safe week and see you next week on 2018-11-29
--
Stephen J Smoogen.
5 years
