Re: Introduce my self [futur member]
This is helpful, thanks for sharing -- Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: https://tutanota.com Jul 3, 2020, 15:33 by dkir...@redhat.com: > I've a few links saved in my notes related to this Seddik, check the top one, > it has information about the infrastructure apprentice group. I'm new myself, > just getting started here too :D > > SOPS: > > https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/index.html > Issues list: > https://pagure.io/fedora-infrastructure/issues > easy fixes: > https://fedoraproject.org/easyfix/#fedora-infrastructure > Infra-docs: > https://pagure.io/infra-docs/ > Infrastructure Howtos: > https://pagure.io/Fedora-Infra/howtos > Weekly meeting agenda: > https://board.net/p/fedora-infra > > > On Fri, 3 Jul 2020 at 13:23, seddik alaoui ismaili <> > seddikalaouiisma...@gmail.com> > wrote: > >> Hello David , >> >> Is there any method to join Infrastructure Apprentice team ? >> >> Many thanks >> Seddik >> >> Le jeu. 2 juil. 2020 à 17:52, David Kirwan <>> dkir...@redhat.com>> > a >> écrit : >> >>> Welcome Seddik! >>> >>> On Thu, 2 Jul 2020 at 16:45, seddik alaoui ismaili <>>> >>> seddikalaouiisma...@gmail.com>>> > wrote: >>> Hello team I am very pleased to write you this email, to let you know my motivation and my situation. - Name : alaoui ismaili seddik - Time zone / country : GMT +2 / France I will start with an introduction of my experiences and skills, So I was a GNU/LINUX administrator for 2 years, the first year was with a software editor (competitive intelligence), during this period I was able to develop my skills on different subjects including system administration (Centos os ), maintenance in operational condition, the implementation of basic tools/services, scripting (python/bash), db (mysql), C compilation. I also managed to develop the sense of sharing and collaborative work. Also for the second job at the company (numberly) as administrator/devops, I took care of the DNS platform (powerdns), automatic deployment of the conf via ansible, mainly the industrialization of the IT. And then on different projects, for example on the cloud (hosting dns on route_53 AWS), centreon, grafana, elk stack, also managing the resolution of incidents raised from the production servers. I was system operator at capgemini for 1 year and 9 months more precisely, the production piloting for two linux/unix (AIX, HP-UX, REDHAT) and Mainframe (MVS) spells. Currently I am an IT consultant at orange (telecom operator), I work in an application environment (tomcat), os linux (REDHAT), and my main missions are, the maintenance of the ELK stack, system administration, installation of application instances in automatic way (ansible), continuous deployment, migration of code on GITLAB. I'm always interested in the linux operating system because it's an opportunity to be closer to the machine, with it we can understand how a system works, and react in case of bugs, it also allows to have a support through a community that contributes behind it. For this I will be happy to contribute on projects/tasks related to GNU/LINUX system administration, bug analysis. I will be able to give my time to the community, about 10 hours a week. I hope I wasn't too long on my presentation. Kind regards Seddik ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >>> >>> >>> -- >>> David Kirwan >>> Software Engineer >>> >>> Community Platform Engineering @ Red Hat >>> >>> >>> >>> T: +(353) 86-8624108 >>> IM: >>> @dkirwan >>> >>> ___ >>> infrastructure mailing list -- >>> infrastructure@lists.fedoraproject.org >>> To unsubscribe send an email to >>> >>> infrastructure-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: >>> >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: >>> https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >>> > > > -- > David Kirwan > Software Engineer > > Community Platform Engineering @ Red Hat > > > > T: +(353) 86-8624108 > IM: > @dkirwan > > ___
Re: What is our technical debt?
Yeah makes sense Kevin, Hmm just threw a little POC together to show some of the basics of the Openshift monitoring stack. - Sample configuration for the User Workload monitoring stack which is in tech preview, eg data retention, and persistent storage claim size etc. - small ruby app that has a /metrics endpoint, and 2 gauge metrics being exported - Prometheus ServiceMonitor to monitor the service - Prometheus PrometheusRule to fire based on those alerts - WIP, but I'll add example Grafana GrafanaDashboards which graph the metrics at some future point https://github.com/davidkirwan/crypto_monitoring On Wed, 1 Jul 2020 at 17:13, Kevin Fenzi wrote: > On Sun, Jun 28, 2020 at 01:01:31AM +0100, David Kirwan wrote: > > > > Hmm the (prometheus, grafana, alertmanager) stack itself is pretty > simple I > > would have said, but I agree it is certainly complex when > > installed/integrated on Openshift.. (most things are needlessly complex > on > > Openshift tbh, and its an order of magnitude worse on Openshift 4 with > > these operators added to the mix). > > Well, they may not be that complex... like I said, I haven't used them > much, so I might be missing how they work. > > > It would be the obvious choice for me anyway considering this stack is > > available by default on a fresh Openshift install. We could make use of > > this cluster monitoring stack, especially if we're also deploying our > > services on Openshift. I might throw a POC/demo together to show how > "easy" > > it is to get your app hooked into the Openshift cluster monitoring stack, > > or the UserWorkload tech preview monitoring stack[1]. > > I agree it makes sense to use this for openshift apps. > I am not sure at all we should use it for non openshift apps. > > > If we did use this stack it would add a little extra pain with regards to > > monitoring storage maintenance/pruning. But maybe far less than > > running/maintaining a whole separate monitoring stack outside the > Openshift > > cluster. There are also efficiencies to be made when developers are > already > > in the Openshift/Kubernetes mindset, creating an extra Service and > > ServiceMonitor is a minor thing etc. > > Sure, but we have a lot of legacy stuff we want to monitor/review logs > for too. > > The right answer might be to just seperate those two use cases with > different solutions, but then we have 2 things to maintain. > It's probibly going to take some investigation and some proof of concept > working. > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > -- David Kirwan Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 IM: @dkirwan ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Introduce my self [futur member]
I've a few links saved in my notes related to this Seddik, check the top one, it has information about the infrastructure apprentice group. I'm new myself, just getting started here too :D SOPS: https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/index.html Issues list: https://pagure.io/fedora-infrastructure/issues easy fixes: https://fedoraproject.org/easyfix/#fedora-infrastructure Infra-docs: https://pagure.io/infra-docs/ Infrastructure Howtos: https://pagure.io/Fedora-Infra/howtos Weekly meeting agenda: https://board.net/p/fedora-infra On Fri, 3 Jul 2020 at 13:23, seddik alaoui ismaili < seddikalaouiisma...@gmail.com> wrote: > Hello David , > > Is there any method to join Infrastructure Apprentice team ? > > Many thanks > Seddik > > > Le jeu. 2 juil. 2020 à 17:52, David Kirwan a écrit : > >> Welcome Seddik! >> >> On Thu, 2 Jul 2020 at 16:45, seddik alaoui ismaili < >> seddikalaouiisma...@gmail.com> wrote: >> >>> Hello team >>> >>> I am very pleased to write you this email, to let you know my motivation >>> and my situation. >>> - Name : alaoui ismaili seddik >>> - Time zone / country : GMT +2 / France >>> >>> I will start with an introduction of my experiences and skills, >>> So I was a GNU/LINUX administrator for 2 years, the first year was with >>> a software editor (competitive intelligence), during this period I was able >>> to develop my skills on different subjects including system administration >>> (Centos os ), maintenance in operational condition, the implementation of >>> basic tools/services, scripting (python/bash), db (mysql), C compilation. >>> I also managed to develop the sense of sharing and collaborative work. >>> Also for the second job at the company (numberly) as >>> administrator/devops, I took care of the DNS platform (powerdns), automatic >>> deployment of the conf via ansible, mainly the industrialization of the IT. >>> And then on different projects, for example on the cloud (hosting dns on >>> route_53 AWS), centreon, grafana, elk stack, also managing the resolution >>> of incidents raised from the production servers. >>> I was system operator at capgemini for 1 year and 9 months more >>> precisely, the production piloting for two linux/unix (AIX, HP-UX, REDHAT) >>> and Mainframe (MVS) spells. >>> Currently I am an IT consultant at orange (telecom operator), I work in >>> an application environment (tomcat), os linux (REDHAT), and my main >>> missions are, the maintenance of the ELK stack, system administration, >>> installation of application instances in automatic way (ansible), >>> continuous deployment, migration of code on GITLAB. >>> >>> I'm always interested in the linux operating system because it's an >>> opportunity to be closer to the machine, with it we can understand how a >>> system works, and react in case of bugs, it also allows to have a support >>> through a community that contributes behind it. For this I will be happy to >>> contribute on projects/tasks related to GNU/LINUX system administration, >>> bug analysis. >>> >>> I will be able to give my time to the community, about 10 hours a week. >>> >>> I hope I wasn't too long on my presentation. >>> >>> Kind regards >>> >>> Seddik >>> ___ >>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >>> To unsubscribe send an email to >>> infrastructure-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >>> >> >> >> -- >> David Kirwan >> Software Engineer >> >> Community Platform Engineering @ Red Hat >> >> T: +(353) 86-8624108 IM: @dkirwan >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> > -- David Kirwan Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 IM: @dkirwan ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Introduce my self [futur member]
Hello David , Is there any method to join Infrastructure Apprentice team ? Many thanks Seddik Le jeu. 2 juil. 2020 à 17:52, David Kirwan a écrit : > Welcome Seddik! > > On Thu, 2 Jul 2020 at 16:45, seddik alaoui ismaili < > seddikalaouiisma...@gmail.com> wrote: > >> Hello team >> >> I am very pleased to write you this email, to let you know my motivation >> and my situation. >> - Name : alaoui ismaili seddik >> - Time zone / country : GMT +2 / France >> >> I will start with an introduction of my experiences and skills, >> So I was a GNU/LINUX administrator for 2 years, the first year was with a >> software editor (competitive intelligence), during this period I was able >> to develop my skills on different subjects including system administration >> (Centos os ), maintenance in operational condition, the implementation of >> basic tools/services, scripting (python/bash), db (mysql), C compilation. >> I also managed to develop the sense of sharing and collaborative work. >> Also for the second job at the company (numberly) as >> administrator/devops, I took care of the DNS platform (powerdns), automatic >> deployment of the conf via ansible, mainly the industrialization of the IT. >> And then on different projects, for example on the cloud (hosting dns on >> route_53 AWS), centreon, grafana, elk stack, also managing the resolution >> of incidents raised from the production servers. >> I was system operator at capgemini for 1 year and 9 months more >> precisely, the production piloting for two linux/unix (AIX, HP-UX, REDHAT) >> and Mainframe (MVS) spells. >> Currently I am an IT consultant at orange (telecom operator), I work in >> an application environment (tomcat), os linux (REDHAT), and my main >> missions are, the maintenance of the ELK stack, system administration, >> installation of application instances in automatic way (ansible), >> continuous deployment, migration of code on GITLAB. >> >> I'm always interested in the linux operating system because it's an >> opportunity to be closer to the machine, with it we can understand how a >> system works, and react in case of bugs, it also allows to have a support >> through a community that contributes behind it. For this I will be happy to >> contribute on projects/tasks related to GNU/LINUX system administration, >> bug analysis. >> >> I will be able to give my time to the community, about 10 hours a week. >> >> I hope I wasn't too long on my presentation. >> >> Kind regards >> >> Seddik >> ___ >> infrastructure mailing list -- infrastructure@lists.fedoraproject.org >> To unsubscribe send an email to >> infrastructure-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org >> > > > -- > David Kirwan > Software Engineer > > Community Platform Engineering @ Red Hat > > T: +(353) 86-8624108 IM: @dkirwan > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: Another Rust MirrorManager experiment
On Fri, Jul 03, 2020 at 08:03:16AM +0200, Adrian Reber wrote: > On Thu, Jul 02, 2020 at 09:44:10AM +0200, Pierre-Yves Chibon wrote: > > On Wed, Jul 01, 2020 at 06:25:47PM +0200, Adrian Reber wrote: > > > On Wed, Jul 01, 2020 at 09:16:05AM -0700, Kevin Fenzi wrote: > > > > On Tue, Jun 30, 2020 at 02:17:30PM +0200, Adrian Reber wrote: > > > > > On Mon, Jun 15, 2020 at 03:36:23PM -0700, Kevin Fenzi wrote: > > > > > > On Wed, Jun 10, 2020 at 11:09:49AM +0200, Adrian Reber wrote: > > > > > > > > > > > > > > Then I just have to wait a bit. No problem. > > > > > > > > > > > > > > > > Having the possibility to generate the mirrorlist input data > > > > > > > > > in about a > > > > > > > > > minute would significantly reduce the load on the database > > > > > > > > > server and > > > > > > > > > enable us to react much faster if broken protobuf data has > > > > > > > > > been synced > > > > > > > > > to the mirrorlist servers on the proxies. > > > > > > > > > > > > > > > > Yeah, and I wonder if it would let us revisit the entire > > > > > > > > sequence from > > > > > > > > 'update push finished' to updated mirrorlist server. > > > > > > > > > > > > This would help us with the case of: > > > > > > - updates push/rawhide finishes, master mirror is updated. > > > > > > - openqa/other internal thing tries to get images or updates in that > > > > > > change and gets a metalink with the old checksum so it can't get > > > > > > the > > > > > > new stuff. > > > > > > - mm-backend01 generates and pushes out a new protobuf. > > > > > > > > > > > > > > Probably. As the new code will not run on the current RHEL 7 based > > > > > > > mm-backend01 would it make sense to run a short running service > > > > > > > like > > > > > > > this on Fedora's OpenShift? We could also create a new read-only > > > > > > > (SELECT > > > > > > > only) database account for this. > > > > > > > > > > > > We could, or as smooge suggests make a mm-backend02? > > > > > > > > > > > > But I guess now mm-backend02 just generates new proobuf files and > > > > > > copies > > > > > > them to mirrorlists? If thats all it's doing, perhaps we could > > > > > > indeed > > > > > > replace it with an openshift project. > > > > > > > > > > We need a system to run the tool and copy the data to all proxies. > > > > > > > > > > I would like to see a new MirrorManager database user who can only do > > > > > selects as that is all we need. > > > > > > > > > > Currently we copy the files via SSH to the proxies, if we continue > > > > > doing > > > > > it that way, then we would also need the existing SSH key to copy the > > > > > data to the proxies. > > > > > > > > > > Easiest would probably be a small Fedora 32 based VM with 2GB of > > > > > memory. > > > > > > > > I'm not sure f32 will work with 2gb memory anymore. I dont think it > > > > installs at any rate. > > > > > > > > I do like the idea of just making it an openshift pod. Perhaps this > > > > could even fit with pingous 'toddlers' setup. ie: > > > > > > > > * listen for message saying a repo has updated > > > > * update the db > > > > * create the protobuf > > > > * push out to proxies > > > > > > > > The only weird part of putting it in openshift is that we would need to > > > > have fedora_ftp (ro) there available as a volume, but that is doable... > > > > > > No, this part only needs to talk read-only to the database. This is not > > > touching anything on the disk besides writing the output. I guess you > > > were thinking about the umdl (update-master-directory-listing) part. > > > That would need ro access to the file-system. > > > > > > The part I am talking about just reads the database and creates a > > > protobuf snapshot of the database which is then used by the mirrorlist > > > servers on the proxies. > > > > > > Currently it runs once every hour. Which works pretty good so far. > > > Triggering it on a message makes only limited sense as it depends on the > > > results of the crawler. We could run it twice an hour to have newer > > > database snapshots on the proxies. > > > > > > How can I prepare it for running in openshift. Can I use the > > > configuration for toddlers? Where can I find that? > > > > Toddlers has recently gained the possibility to trigger at certain time. > > Well > > we're actually sort of abusing it, we've added a script (playtime) that will > > send a fedora-messaging message and that should be called from a cron job. > > That > > message should then trigger the corresponding toddler. > > > > This (playtime) is not yet deployed in production so I can't point you to an > > example, but the project itself is at: > > https://pagure.io/fedora-infra/toddlers > > and the openshift config is at: > > https://pagure.io/fedora-infra/ansible/blob/master/f/playbooks/openshift-apps/toddlers.yml > > Thanks for the pointer. I had a look at it, but I do not think I > understand it. So many sections where I have no idea what they do > > I
Re: Another Rust MirrorManager experiment
On Thu, Jul 02, 2020 at 09:44:10AM +0200, Pierre-Yves Chibon wrote: > On Wed, Jul 01, 2020 at 06:25:47PM +0200, Adrian Reber wrote: > > On Wed, Jul 01, 2020 at 09:16:05AM -0700, Kevin Fenzi wrote: > > > On Tue, Jun 30, 2020 at 02:17:30PM +0200, Adrian Reber wrote: > > > > On Mon, Jun 15, 2020 at 03:36:23PM -0700, Kevin Fenzi wrote: > > > > > On Wed, Jun 10, 2020 at 11:09:49AM +0200, Adrian Reber wrote: > > > > > > > > > > > > Then I just have to wait a bit. No problem. > > > > > > > > > > > > > > Having the possibility to generate the mirrorlist input data in > > > > > > > > about a > > > > > > > > minute would significantly reduce the load on the database > > > > > > > > server and > > > > > > > > enable us to react much faster if broken protobuf data has been > > > > > > > > synced > > > > > > > > to the mirrorlist servers on the proxies. > > > > > > > > > > > > > > Yeah, and I wonder if it would let us revisit the entire sequence > > > > > > > from > > > > > > > 'update push finished' to updated mirrorlist server. > > > > > > > > > > This would help us with the case of: > > > > > - updates push/rawhide finishes, master mirror is updated. > > > > > - openqa/other internal thing tries to get images or updates in that > > > > > change and gets a metalink with the old checksum so it can't get the > > > > > new stuff. > > > > > - mm-backend01 generates and pushes out a new protobuf. > > > > > > > > > > > > Probably. As the new code will not run on the current RHEL 7 based > > > > > > mm-backend01 would it make sense to run a short running service like > > > > > > this on Fedora's OpenShift? We could also create a new read-only > > > > > > (SELECT > > > > > > only) database account for this. > > > > > > > > > > We could, or as smooge suggests make a mm-backend02? > > > > > > > > > > But I guess now mm-backend02 just generates new proobuf files and > > > > > copies > > > > > them to mirrorlists? If thats all it's doing, perhaps we could indeed > > > > > replace it with an openshift project. > > > > > > > > We need a system to run the tool and copy the data to all proxies. > > > > > > > > I would like to see a new MirrorManager database user who can only do > > > > selects as that is all we need. > > > > > > > > Currently we copy the files via SSH to the proxies, if we continue doing > > > > it that way, then we would also need the existing SSH key to copy the > > > > data to the proxies. > > > > > > > > Easiest would probably be a small Fedora 32 based VM with 2GB of memory. > > > > > > I'm not sure f32 will work with 2gb memory anymore. I dont think it > > > installs at any rate. > > > > > > I do like the idea of just making it an openshift pod. Perhaps this > > > could even fit with pingous 'toddlers' setup. ie: > > > > > > * listen for message saying a repo has updated > > > * update the db > > > * create the protobuf > > > * push out to proxies > > > > > > The only weird part of putting it in openshift is that we would need to > > > have fedora_ftp (ro) there available as a volume, but that is doable... > > > > No, this part only needs to talk read-only to the database. This is not > > touching anything on the disk besides writing the output. I guess you > > were thinking about the umdl (update-master-directory-listing) part. > > That would need ro access to the file-system. > > > > The part I am talking about just reads the database and creates a > > protobuf snapshot of the database which is then used by the mirrorlist > > servers on the proxies. > > > > Currently it runs once every hour. Which works pretty good so far. > > Triggering it on a message makes only limited sense as it depends on the > > results of the crawler. We could run it twice an hour to have newer > > database snapshots on the proxies. > > > > How can I prepare it for running in openshift. Can I use the > > configuration for toddlers? Where can I find that? > > Toddlers has recently gained the possibility to trigger at certain time. Well > we're actually sort of abusing it, we've added a script (playtime) that will > send a fedora-messaging message and that should be called from a cron job. > That > message should then trigger the corresponding toddler. > > This (playtime) is not yet deployed in production so I can't point you to an > example, but the project itself is at: > https://pagure.io/fedora-infra/toddlers > and the openshift config is at: > https://pagure.io/fedora-infra/ansible/blob/master/f/playbooks/openshift-apps/toddlers.yml Thanks for the pointer. I had a look at it, but I do not think I understand it. So many sections where I have no idea what they do I would need some help setting this up. Adrian ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct:
