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
python2 and fedora deployed applications
by Kevin Fenzi
Greetings.
There's discussion on the devel list about how to handle the end of life
of python2 in Fedora. This will most likely happen next year. Of course
our applications still running on rhel7 should continue to be ok, but
anything we now deploy on Fedora we need to figure out what we are going
to do. Ideally we port them to python3 before the deadline and all goes on.
I went and did a quick grep thru ansible to locate any instances running
Fedora running apps we control.
If everyone could look at this and reply (to the list) with what they
know about the python3 status of all the following apps that would be
lovely. :)
builders - need mock and koji supporting bootstrap.
autocloud - ?
bodhi-backend - ?
bodhi-web - ?
certgetter - should be fine?
ci-cc-rdu01 - ?
docker registry - ?
greenwave - ?
koschei - ?
mdapi - YES! python3 already!
modernpaste - ?
notifs-backend - ?
odcs - ?
openqa - ?
osbs - ?
packages - ?
resultsdb - ?
taskotron - ?
mirrorlist containers
sundries - geoip_city?
waiverdb - ?
Thanks,
kevin
5 years, 4 months
Introduction
by seanmottles＠posteo.de
Hi all!
I would like to join the Fedora Infrastructure group.
IRC: se-sm-ca
Skills:
> Bash, and an okay amount of Python. Have written a couple web apps
with Python
> Work as a Linux admin with a few years of experience - more Ops
focused
> RHCSA
> Have had a good amount of interaction with Linux provisioning
(iPXE/Windows DHCP, creating live CDs, kickstarts, automation of iPXE)
and authentication (sssd, Windows AD) as well as maintaining package
mirrors.
What I would like to learn:
> I would like to learn more about how larger scale infrastructure is
set up (traffic, automation, CI, etc)
> Since I'm more ops focused I could start out going through the open
tickets and trying to fix up issues where I can
Thanks!
Sean
5 years, 4 months
Happy SysAdmin Appreciation Day to our Infra Team!
by Justin W. Flory
Hi all,
In case you missed, today, July 27th, is SysAdmin Appreciation Day! I
wanted to say thanks to all of the folks working in Fedora
Infrastructure for their time and effort to keep all of the bits and
pieces that make up our infrastructure going.
I hope you can help yourself to a slice of cake, or a treat of your
choice (stroopwafels?). :-)
Thanks for all of your hard work!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 4 months
Infrastructure Meeting 2018-07-25
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-07-26 at 14: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-07-26)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean
= 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
= 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 smooge is on PTO 2018-08-02->2018-08-07 (need someone to run
meeting next week)
#info tflink is on extended PTO
#info many are unavailable during FLOCK
#info FLOCK in Dresden is 2018-08-08->2018-08-13?
#info visit to PHX2 will be happening 2018-08-15->2018-08-18
= 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 Kevin? is on call from 2018-07-26->2018-08-02
#info ??? is on call from 2018-08-02 ->2018-08-07
#Info Smooge is on call from 2018-08-07->2018-08-14
#info ??? is on call from 2018-08-15->2018-08-23
#info Summary of last week: (from Smooge)
#topic flock 2018 - dresden - kevin
#info who can make the infrafixfest workshop?
#info who can make the infra plan and hackfest?
#topic OSBS multi arch - ppc64le - cverna
#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, 4 months
Migrating from fedimg to ore
by Sayan Chowdhury
Last few days, I spent doing a feasibility analysis on the migrating
from fedimg to ore, a subproject of mantle to release the Fedora cloud
images.
ore/mantle comes from the CoreOS community. mantle is comprised of
multiple utility projects to keep the CL bits together.
The workflow for fedimg right now:
- Downloads the raw.xz image
- Uses the ImportVolume AWS API[1] to create a volume via S3
- Creates the snapshot using the earlier created volume
- Registers the AMI of the snapshot provided
- Copies the AMI to other regions and makes the AMI and the snapshot public.
What if we migrate to Ore?
The process remain more or less the same except for a few changes:
- Downloads the .qcow2 image
* Once we start using the .qcow2 image we don't need releng to
produce two formats i.e. qcow2 & .raw.xz
- Converts the .qcow2 image to .vmdk format image using qemu-img
- Uses the newer supported AWS API i.e. ImportSnapshot which directly
creates the Snapshot uploading the image via S3
- Registers the AMI with the snapshot.
- Copies the AMI to other regions.
- Ore also skips any of the steps already processed which makes it
easier for the AMIs maintainer.
- Ore has a more maintainers than fedimg.
- It's better to focus on a single project than maintaining two.
Two areas where it needs more research
- how do we send out the fedmsg messages when we move to ore
- making the images & the snapshots public.
Thoughts?
--
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
Proud to work at The Open Organization!
5 years, 4 months
