Freeze break request: add zabbix_agent role to logger systems
Hi all. I want to add the Zabbix agent to the systems in the ansible group: `logger`. Requesting a freeze break, to make this change and then run the playbook: `groups/logserver.yml` Its not urgent, so if you'd prefer to wait till after freeze thats ok! cheers, David -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS cleanup - what to delete next?
Thanks for taking that on Miroslav! On Thu, 8 Feb 2024 at 16:24, Miroslav Suchý wrote: > Dne 08. 02. 24 v 17:09 Miroslav Suchý napsal(a): > > Where I can continue witht the cleanup? There is several dozen thousand > of AMIs. At the end of this email I will give > > random sample from the list. > > For the record, here is complete list containing 150k lines [9MB] > > https://k00.fr/s7xl2itj > > -- > > Miroslav Suchy, RHCA > Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys > -- > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: congrats to another new sysadmin-mainer
Congrats Pavel! On Fri, 1 Dec 2023 at 18:04, Stephen Smoogen wrote: > > Congrats! Pavel has been a great help over he years > > On Fri, 1 Dec 2023 at 12:53, Kevin Fenzi wrote: > >> I'm happy to announce that We have approved a new member in our >> sysadmin-main group: >> >> praiskup >> >> This is the core group of trusted folks that high level access to most >> everything in fedora infrastructure. >> >> As many of you know, he's wrangled copr for quite some time, as well as >> taking on other critical projects like maintaining mock and it's various >> configs. >> >> Adding him to sysadmin-main will help the copr team to more quickly >> change items that need that level of access, as well as hopefully >> allowing him to help out in other places around infrastructure as his >> time permits. >> >> Congrats! >> >> Use your powers for good! :) >> >> 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 >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > > > -- > Stephen Smoogen, Red Hat Automotive > Let us be kind to one another, for most of us are fighting a hard battle. > -- Ian MacClaren > -- > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: congrats to our new sysadmin-mainer
congrats darknao! On Mon, 24 Jul 2023 at 21:20, Kevin Fenzi wrote: > I'm happy to announce that We have approved a new member in our > sysadmin-main group: > > darknao - Francois Andrieu > > This is the core group of trusted folks that high level access to most > everything in fedora infrastructure. > > Francois has done of ton of things around Fedora infrastructure. From > helping manage our OpenShift clusters, to revamping how our docs and > websites are built and deployed, to just helping anyone with issues all > around. > > He has proved his dedication, trustworthiness, and ability. > > Congrats! > > Use your powers for good! :) > > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fi-apprentice introduction : Fabian Arrotin
Hi Fabian welcome ! The next step seems to be to introduce yourself at the weekly meetings see [3], "Meetings are held each Thursday at 15:00 UTC (16:00 UTC during Daylight Savings Time). In #fedora-meeting-3 on Libera Chat." - [1] https://fedoraproject.org/wiki/Infrastructure - [2] https://fedoraproject.org/wiki/Infrastructure/GettingStarted - [3] https://fedoraproject.org/wiki/Infrastructure/Meetings On Mon, 27 Mar 2023 at 10:28, Fabian Arrotin wrote: > hi, > > My name is Fabian Arrotin and working as a sysadmin for some time, > mainly on the CentOS Infrastructure. > My FAS username is 'arrfab' and I'd like to follow the fedora-apprentice > process for sysadmin tasks at the Fedora side (so any pointer is welcome). > > "Amusingly" I can already add myself to the 'fi-apprentice' group but I > don't want to bypass any process, so I'll just wait for someone else to > sponsor/add me and then we can see about next steps :) > > Depending on (free) time, I can try helping with infra tasks , so happy > to see and interact with some of you in a near future ! > > -- > Fabian Arrotin > gpg key: 17F3B7A1 > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: OpenShift: alerting heads up (attention appowners!)
Ooo sounds really cool, good stuff darknao!! On Fri, 10 Feb 2023 at 18:40, Michal Konecny wrote: > This is really great to hear. Waiting on this till I got maintainership > over release-monitoring.org. Good work darknao! > > Michal > > On 09. 02. 23 19:10, Kevin Fenzi wrote: > > Greeting everyone > > > > Thanks to darknao, we have just enabled monitoring by default for our > > OpenShift applications. Note that it will not be active until the next > > run of the playbook pushes it out. I will look at running playbooks over > > the next few days for most projects, but if you are an appowner and want > > it sooner, just run your playbook (and let me know I don't need to). > > > > Some notes: > > > > By default it alerts on the things in > > ./roles/openshift/project/templates/prometheusRules.yml > > Which includes cronjobs failing, pods crashing for various reasons, etc. > > We can look at expanding this if there's other things that are generally > > good to monitor. > > > > Alerts trigger and by default send email to appowners. > > You can optionally set alert_users list in your playbook if you like and > > it will only send to those users (not to appowners). > > > > If for some reason you do not want any of this monitoring on your > > application you can set: alerting: False to avoid it. I'd really like to > > know why if you plan on doing that however. > > > > Hopefully this will help us see when things aren't working right before > > we get user reports about it. :) > > > > Many thanks again to darknao for setting this up. :) > > > > 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 > > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: State of Flask-OIDC
Merged the changes in the PyJWT PR into the fedora-infra fork, tagged a release 1.5.0, and sent in a PR against the RPM to now point at this fork + new version: https://src.fedoraproject.org/rpms/python-flask-oidc/pull-request/2 On Mon, 19 Dec 2022 at 11:19, David Kirwan wrote: > > > On Thu, 15 Dec 2022 at 08:30, Frantisek Zatloukal > wrote: > >> >> >> On Wed, Dec 7, 2022 at 3:25 AM David Kirwan wrote: >> >>> >>> >>> Thanks for the update, David! >> >> Would it be possible to cut a new release with the pyJWT PR included at >> least once you have time/mood to re-focus? Or would that be wasted effort >> before porting to authlib? >> > > I think it might be wasted effort, as this functionality is > replaced/handled in authlib iirc, but then again, I don't think this > authlib implementation is ready either so if we do cut a release of the > pyJWT PR at least we'll have a working version flask-oidc! > > If upstream is too busy to review, should we use our fork: > https://github.com/fedora-infra/flask-oidc ? Maybe get the pyJWT code PR > merged there, and then point our RPM at this fork? Will take urgency off > then, I can take more time then to focus on the authlib implementation? > > cheers, > David > > > >> >> Thanks a lot! >> >> > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: State of Flask-OIDC
On Thu, 15 Dec 2022 at 08:30, Frantisek Zatloukal wrote: > > > On Wed, Dec 7, 2022 at 3:25 AM David Kirwan wrote: > >> >> >> Thanks for the update, David! > > Would it be possible to cut a new release with the pyJWT PR included at > least once you have time/mood to re-focus? Or would that be wasted effort > before porting to authlib? > I think it might be wasted effort, as this functionality is replaced/handled in authlib iirc, but then again, I don't think this authlib implementation is ready either so if we do cut a release of the pyJWT PR at least we'll have a working version flask-oidc! If upstream is too busy to review, should we use our fork: https://github.com/fedora-infra/flask-oidc ? Maybe get the pyJWT code PR merged there, and then point our RPM at this fork? Will take urgency off then, I can take more time then to focus on the authlib implementation? cheers, David > > Thanks a lot! > > ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: State of Flask-OIDC
On Tue, 6 Dec 2022 at 03:05, Neal Gompa wrote: > On Mon, Dec 5, 2022 at 12:48 PM Frantisek Zatloukal > wrote: > > > > \o/, > > > > I'd like to ask if there is anybody familiar with the state of > flask-oidc? It's been long-time broken with the latest itsdangerous, which > was recently bumped in Rawhide, which broke all the applications using > flask-oidc from Fedora repositories ( > https://bugzilla.redhat.com/show_bug.cgi?id=2150955 ). > > > > There is an upstream PR against flask-oidc changing itsdangerous to > pyJWT: https://github.com/puiterwijk/flask-oidc/pull/144 (which, > according to my previous testing, makes the trouble go away). Can somebody > take a look at it, and merge/release a new fixed version? I can handle > pyJWT packaging in Fedora if this is the way forward. > > > > On a similar note, is the flask-oidc library the way to connect to FAS > login for python applications? I had an impression that apps should migrate > to this from plain openid (and I am planning to handle the transition of > remaining Fedora QA apps). It seems abandoned upstream, so should the devs > of python/flask apps use some other lib/way? > > > > Thanks a lot upfront! > > > > There was an attempt to do something about this: > https://github.com/fedora-infra/flask-oidc > > But it also seemingly died. > Not dead yet, just on life support! Hit a few issues as this is an attempt at replacing oauth2client behind the scenes with authlib. Let me share how far I've gotten with this.. - I've a somewhat functional POC which has implemented enough of the original functionality to get a basic login flow working, but it doesn't quite have every feature in the current released version of flask-oidc, may require further functionality be developed, I need to examine some of the locations where we currently use it, and see if this new version offers enough functionality to replace. - Currently hit blocker updating the tests, having to upskill as I know next to nothing about ipsilon, so having to go learn to figure out what I'm trying to mock out to test, slow progress here! authlib implementation PR: https://github.com/fedora-infra/flask-oidc/pull/8 Testing App focusing only on the OIDC login etc: https://github.com/fedora-infra/test-auth/tree/authlib_dev I should get time to re-focus on this over the next few weeks. > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Meeting Agenda Item: Introduction Erol Keskin
Hi Erol! On Thu, 22 Sept 2022 at 19:58, Kevin Fenzi wrote: > Welcome! > > I'm sure you have seen the gettingstarted doc, but if not: > > https://fedoraproject.org/wiki/Infrastructure/GettingStarted > > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: congrats to our new sysadmin-mainers
Congrats Nils, Michal and Ryan! [image: width=] <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, 5 Aug 2022 at 11:34, Mark O'Brien wrote: > A trio very deserving of the responsibility. I have no doubt you will use > it wisely > > On Wed, Aug 3, 2022 at 3:56 PM Kevin Fenzi wrote: > >> I'm happy to announce that We have approved several folks into the >> sysadmin-main group: >> >> nphilipp - Nils Philippsen >> zlopez - Michal Konečný >> ryanlerch - Ryan Lerch >> >> This is the core group of trusted folks that high level access to most >> everything in fedora infrastructure. >> >> Nils is a long time contributor who has worked on a bunch of things, >> including our ipa sudo/ssh permissions setup. >> >> Michal has worked on many of our applications and is also serving to >> help keep us on plan for planned work over the quarters. >> >> Ryan has been around for a long time working on many things, including >> our revamped status application, FMN, gitlab permissions and more. >> >> They have both proved their dedication, trustworthiness, and ability. >> >> Congrats to them all! >> >> Use your powers for good! :) >> >> 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 >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- David Kirwan Senior Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora OCP 3.11 -> 4.10 Data Migration Proposal
I've added Prakash https://accounts.stg.fedoraproject.org/user/prakashmishra1598/ to the `sysadmin-openshift`, I'm not a sponsor for `sysadmin`, Kevin would you mind adding him there on staging please! On Mon, 4 Jul 2022 at 09:02, David Kirwan wrote: > > > On Fri, 1 Jul 2022 at 17:14, Kevin Fenzi wrote: > >> On Fri, Jul 01, 2022 at 03:10:17PM +0100, David Kirwan wrote: >> > haha looks like we've been living under a rock the pair of us.. the >> > migration is fully complete, including the data? aha! >> >> Yes, we are all done now. ;) >> >> I even scaled fas2 / old accounts down to 0 yesterday and so far nothing >> as blown up. ;) >> >> It might have been easier with velero, but 90+% of our apps had no >> persistent storage, so basically it was just scale down in old cluster, >> deploy to new, change proxies to point to new cluster. The few that did >> have storage, it was NFS, so that just added a 'chown data to new uid' >> step. >> >> Anyhow, I'm +1 to adding Prakash in stg for sure... >> >> > Thanks Kevin! Not to worry we learned a lot we'll write up what we learned > anyway, from speaking to Mark O'Brien about it, this might come in handy in > a future CentOS CI migration. > > I'll add Prakash to those two groups on stg. > > > >> kevin >> -- >> > >> > On Fri, 1 Jul 2022 at 14:49, David Kirwan wrote: >> > >> > > Hi all, >> > > >> > > I'd like to propose Prakash be added to the `sysadmin` and >> > > `sysadmin-openshift` groups on Staging. Prakash has lead the >> investigation >> > > into Velero as a potential solution for our data migration, and also >> helped >> > > with the Asknot app migration to Openshift 4. It would be nice to have >> > > another person with experience in Openshift 4 in the community to >> help out! >> > > >> > > On Fri, 1 Jul 2022 at 14:27, Prakash Mishra < >> prakashmishra1...@gmail.com> >> > > wrote: >> > > >> > >> Hi all, >> > >> >> > >> Over the last number of weeks we have been investigating a number of >> outstanding issues related to the Openshift 3/4 clusters managed by Fedora >> infrastructure. A large outstanding issue has been data migration. We've >> been investigating various solutions, and have come up with something which >> is relatively painless, and have verified it works with a proof of concept. >> So here is our proposal: >> > >> >> > >> ## Proposal >> > >> >> > >> - Using `Velero` https://velero.io/docs/main/migration-case/ >> > >> - From 3.11, plan to migrate only PV/PVC data >> > >> - Velero will migrate multiple things, but the only thing we are >> interested is the PV data. So there might be a little clean up in a >> namespace once a migration has completed. >> > >> - Once completed we can run our Fedora ansible playbooks as normal, >> the PVs/PVCs will be in place. >> > >> >> > >> If it sounds like a reasonable course of action we'll put a SOP >> together to describe how to carry out this work, and can either take it on >> ourselves or allow Infra and Releng in CPE to carry it out. >> > >> >> > >> Cheers, >> > >> Prakash Mishra & David Kirwan. >> > >> >> > >> _______ >> > >> 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 >> > >> Do not reply to spam on the list, report it: >> > >> https://pagure.io/fedora-infrastructure >> > >> >> > > >> > > >> > > -- >> > > David Kirwan >> > > Software Engineer >> > > >> > > Community Platform Engineering @ Red Hat >> > > >> > > T: +(353) 86-8624108 IM: @dkirwan >> > > >> > >> > >> > -- >> > David Kirwan >> > Software Engineer >> > >>
Re: Fedora OCP 3.11 -> 4.10 Data Migration Proposal
On Fri, 1 Jul 2022 at 17:14, Kevin Fenzi wrote: > On Fri, Jul 01, 2022 at 03:10:17PM +0100, David Kirwan wrote: > > haha looks like we've been living under a rock the pair of us.. the > > migration is fully complete, including the data? aha! > > Yes, we are all done now. ;) > > I even scaled fas2 / old accounts down to 0 yesterday and so far nothing > as blown up. ;) > > It might have been easier with velero, but 90+% of our apps had no > persistent storage, so basically it was just scale down in old cluster, > deploy to new, change proxies to point to new cluster. The few that did > have storage, it was NFS, so that just added a 'chown data to new uid' > step. > > Anyhow, I'm +1 to adding Prakash in stg for sure... > > Thanks Kevin! Not to worry we learned a lot we'll write up what we learned anyway, from speaking to Mark O'Brien about it, this might come in handy in a future CentOS CI migration. I'll add Prakash to those two groups on stg. > kevin > -- > > > > On Fri, 1 Jul 2022 at 14:49, David Kirwan wrote: > > > > > Hi all, > > > > > > I'd like to propose Prakash be added to the `sysadmin` and > > > `sysadmin-openshift` groups on Staging. Prakash has lead the > investigation > > > into Velero as a potential solution for our data migration, and also > helped > > > with the Asknot app migration to Openshift 4. It would be nice to have > > > another person with experience in Openshift 4 in the community to help > out! > > > > > > On Fri, 1 Jul 2022 at 14:27, Prakash Mishra < > prakashmishra1...@gmail.com> > > > wrote: > > > > > >> Hi all, > > >> > > >> Over the last number of weeks we have been investigating a number of > outstanding issues related to the Openshift 3/4 clusters managed by Fedora > infrastructure. A large outstanding issue has been data migration. We've > been investigating various solutions, and have come up with something which > is relatively painless, and have verified it works with a proof of concept. > So here is our proposal: > > >> > > >> ## Proposal > > >> > > >> - Using `Velero` https://velero.io/docs/main/migration-case/ > > >> - From 3.11, plan to migrate only PV/PVC data > > >> - Velero will migrate multiple things, but the only thing we are > interested is the PV data. So there might be a little clean up in a > namespace once a migration has completed. > > >> - Once completed we can run our Fedora ansible playbooks as normal, > the PVs/PVCs will be in place. > > >> > > >> If it sounds like a reasonable course of action we'll put a SOP > together to describe how to carry out this work, and can either take it on > ourselves or allow Infra and Releng in CPE to carry it out. > > >> > > >> Cheers, > > >> Prakash Mishra & David Kirwan. > > >> > > >> ___ > > >> 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 > > >> Do not reply to spam on the list, report it: > > >> https://pagure.io/fedora-infrastructure > > >> > > > > > > > > > -- > > > David Kirwan > > > Software Engineer > > > > > > Community Platform Engineering @ Red Hat > > > > > > T: +(353) 86-8624108 IM: @dkirwan > > > > > > > > > -- > > 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 > > Do not reply to spam on the list, report it: > https:
Re: Fedora OCP 3.11 -> 4.10 Data Migration Proposal
haha looks like we've been living under a rock the pair of us.. the migration is fully complete, including the data? aha! On Fri, 1 Jul 2022 at 14:49, David Kirwan wrote: > Hi all, > > I'd like to propose Prakash be added to the `sysadmin` and > `sysadmin-openshift` groups on Staging. Prakash has lead the investigation > into Velero as a potential solution for our data migration, and also helped > with the Asknot app migration to Openshift 4. It would be nice to have > another person with experience in Openshift 4 in the community to help out! > > On Fri, 1 Jul 2022 at 14:27, Prakash Mishra > wrote: > >> Hi all, >> >> Over the last number of weeks we have been investigating a number of >> outstanding issues related to the Openshift 3/4 clusters managed by Fedora >> infrastructure. A large outstanding issue has been data migration. We've >> been investigating various solutions, and have come up with something which >> is relatively painless, and have verified it works with a proof of concept. >> So here is our proposal: >> >> ## Proposal >> >> - Using `Velero` https://velero.io/docs/main/migration-case/ >> - From 3.11, plan to migrate only PV/PVC data >> - Velero will migrate multiple things, but the only thing we are interested >> is the PV data. So there might be a little clean up in a namespace once a >> migration has completed. >> - Once completed we can run our Fedora ansible playbooks as normal, the >> PVs/PVCs will be in place. >> >> If it sounds like a reasonable course of action we'll put a SOP together to >> describe how to carry out this work, and can either take it on ourselves or >> allow Infra and Releng in CPE to carry it out. >> >> Cheers, >> Prakash Mishra & David Kirwan. >> >> ___ >> 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 >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > > > -- > David Kirwan > Software Engineer > > Community Platform Engineering @ Red Hat > > T: +(353) 86-8624108 IM: @dkirwan > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora OCP 3.11 -> 4.10 Data Migration Proposal
Hi all, I'd like to propose Prakash be added to the `sysadmin` and `sysadmin-openshift` groups on Staging. Prakash has lead the investigation into Velero as a potential solution for our data migration, and also helped with the Asknot app migration to Openshift 4. It would be nice to have another person with experience in Openshift 4 in the community to help out! On Fri, 1 Jul 2022 at 14:27, Prakash Mishra wrote: > Hi all, > > Over the last number of weeks we have been investigating a number of > outstanding issues related to the Openshift 3/4 clusters managed by Fedora > infrastructure. A large outstanding issue has been data migration. We've been > investigating various solutions, and have come up with something which is > relatively painless, and have verified it works with a proof of concept. So > here is our proposal: > > ## Proposal > > - Using `Velero` https://velero.io/docs/main/migration-case/ > - From 3.11, plan to migrate only PV/PVC data > - Velero will migrate multiple things, but the only thing we are interested > is the PV data. So there might be a little clean up in a namespace once a > migration has completed. > - Once completed we can run our Fedora ansible playbooks as normal, the > PVs/PVCs will be in place. > > If it sounds like a reasonable course of action we'll put a SOP together to > describe how to carry out this work, and can either take it on ourselves or > allow Infra and Releng in CPE to carry it out. > > Cheers, > Prakash Mishra & David Kirwan. > > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Self Introduction: Prakash Mishra
Welcome Prakash! On Fri, 15 Apr 2022 at 16:09, Prakash Mishra wrote: > Hello everyone, > > I'm Prakash from Bangalore in India. I currently work as a Golang > developer working mainly with Kubernetes Operators and multi cluster > Kubernetes management. I've used Fedora as my daily driver for large parts > in the past. > > I started my contribution journey with Vipul(Vipul SIddharth) back in 2016 > by contributing to Fedora QA when we were attending university. My career > took me down a different path later as I got more involved with the > Kubernetes community here in India. > > I recently got involved with Fedora Infrastructure and the KubeDev SIG > where David(Dkirwan) and Leo(Lrossett) have helped me immensely in getting > started. David and I spent a couple of hours today migrating > https://stg.whatcanidoforfedora.org to OCP4. The changes can be viewed > here: > https://pagure.io/fedora-infra/ansible/c/46b773c87a1dc6edd1c19425c6ef2fa169720420?branch=main. > I look forward to working with you and I hope you have a great weekend > ahead. > > Cheers, > Prakash Mishra. > > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Sysadmin - main group
Cheers all! On Mon, 29 Nov 2021 at 13:34, Vipul Siddharth wrote: > On Mon, Nov 29, 2021 at 6:06 PM Mark O'Brien wrote: > > > > I'm happy to announce that We have added a new member to the > > sysadmin-main group: > > > > Saffronique - David Kirwan > Congratulations David > After working with you on multiple projects, I can definitely say that > this is a well deserved trust! > Thank you for working on all things Infra and thank you to the Infra > team for onboarding more sysadmin-mains > > > > > This is the core group of trusted folks that have high level access to > > almost everything in fedora infrastructure. > > > > David has been working on Fedora infra for about a year now and > > has been involved in some fairly big pieces of work including adding > > an aarch64 cluster to osbs as well as bringing up the new ocp4 > > cluster in Fedora. > > > > He has proved trustworthiness, and ability and I'd like to be the first > > to wish him congratulations > > > > Mark > > ___ > > 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 > > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > > > > -- > Vipul Siddharth > He/His/Him > Fedora | CentOS CI Infrastructure Team > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Infrastructure and release engineering Documentation
t; >>> > > > >>> Thanks for working on this! > > > >>> > > > >>> 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 > > > >> Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Openshift 4 SOP PR review
Cheers folks, this is merged now. On Wed, 29 Sept 2021 at 10:35, David Kirwan wrote: > > > On Wed, 29 Sept 2021 at 02:28, Kevin Fenzi wrote: > >> >> So, as far as migrating over to the new cluster...how do we want to >> handle that? Obviously we want to do staging first and sort out any >> issues. Should that be a task that infra and releng takes on this next >> quater? Or something you all are going to keep working on? >> > > I hope this is something we can continue to work on as we shift back into > the infra & releng. Might be good to catch you for a few minutes for a chat > this week to bounce a few ideas about how we could do it, we were > considering adding new roles for each individual app, it could allow us to > deploy them with any new ocp4 required changes without affecting the > existing 3.11 cluster versions. > > > >> Also, I will have 2 more compute nodes we can add (one to stg and one to >> prod) in a bit (need to get vlans sorted, etc). Perhaps it's worth >> adding a sop to add new nodes I can just do it? Or hand off the machines >> when they are ready for you all. >> > > Nice! Yep we have a SOP from the CentOS CI infra we can use, it would be > great if you wanted to follow it to add these new nodes! > > > -- > David Kirwan > Software Engineer > > Community Platform Engineering @ Red Hat > > T: +(353) 86-8624108 IM: @dkirwan > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Openshift 4 SOP PR review
On Wed, 29 Sept 2021 at 02:28, Kevin Fenzi wrote: > > So, as far as migrating over to the new cluster...how do we want to > handle that? Obviously we want to do staging first and sort out any > issues. Should that be a task that infra and releng takes on this next > quater? Or something you all are going to keep working on? > I hope this is something we can continue to work on as we shift back into the infra & releng. Might be good to catch you for a few minutes for a chat this week to bounce a few ideas about how we could do it, we were considering adding new roles for each individual app, it could allow us to deploy them with any new ocp4 required changes without affecting the existing 3.11 cluster versions. > Also, I will have 2 more compute nodes we can add (one to stg and one to > prod) in a bit (need to get vlans sorted, etc). Perhaps it's worth > adding a sop to add new nodes I can just do it? Or hand off the machines > when they are ready for you all. > Nice! Yep we have a SOP from the CentOS CI infra we can use, it would be great if you wanted to follow it to add these new nodes! -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Openshift 4 SOP PR review
We've updated a number of SOPs since e.g. upgrades, if you could take another look, and +1 the PR if we're happy! We've installed and tested Openshift Virtualization on the staging cluster, it's working good, currently need cluster-admin to use, In the coming days we'll continue to work on the remaining tasks such as quotas and permissions to easily hand out to users etc. On Sat, 25 Sept 2021 at 00:55, Kevin Fenzi wrote: > On Fri, Sep 24, 2021 at 12:01:27PM +0900, David Kirwan wrote: > > > On the storage, are we ok if a node goes down? ie, does it spread it > > > over all the storage nodes/raid? Or is it just in one place and you are > > > dead if that node dies? > > For storage, we maintain 3 replicas for data, spread across 3 nodes. > > However, not all nodes are equally resourced, we have 2 large nodes and 1 > > much smaller, therefore, more replicas will be spread over these 2 larger > > nodes. We can likely afford to lose one of the large physical nodes while > > still maintaining data integrity. > > ok. Fair enough. > > > > Is there any way to backup volumes? > > There are ways to clone, extend, take snapshots etc of these volumes. > We've > > never done it, so it'll be a learning process for us all ;). We should > sync > > to get a better handle on the requirements for backups. In CentOS CI > we've > > set up backups to S3, we can certainly use some of that, eg: backup of > > etcd, but may need further investigation to backup the volumes managed by > > OCS. Will need to do some research here. > > Yeah, backups of etcd would be nice, but mostly I was thinking of > applications that have persistent data. Right now we have those on > netapp NFS volumes, where it keeps snapshots and mirrors to another > site. I suppose we could just keep using NFS for data that has to > persist and just use local for other things, but it's sure nice to have > it dynamically provisioned. ;) > > > > should we make a playbooks/manual/ocp.yml playbook for things like > > > - list of clusteradmins > > > - list of clustermoniting > > > - anything else we want to manage post install > > Sure yep, as we're finishing up soonish, I'd imagine the next few weeks > > we'll all be back focused on the Infra/Releng tasks and will be focusing > on > > tying up any loose ends like this, and starting migration of apps. > > ok. > > > > Have we tried a upgrade of the clusters yet? Did everything go ok? > > > Do we need any docs on upgrades? > > Yes, we've already completed a number of upgrades, latest is to 4.8.11. > We > > have SOPs for upgrades which we can copy over from the CentOS CI infra, > and > > will make any updates required in the process. > > Great. > > > > Since the control plane are vm's I assume we need to drain them one at > > > a time to reboot the virthosts they are on? > > If we are rebooting a single vmhost/control plane VM at a time, yes that > > should be good. If we are doing more than 1 at the same time, we should > do > > a full graceful cluster shutdown, and then a graceful cluster startup. We > > have SOPs for this in CentOS CI also, we'll get those added here and any > > content updates made. > > > > > * Should we now delete the kubeadmin user? In 3.x I know they advise to > > > do that after auth is setup. > > We can delete it, as we have system:admin available from the os-control01 > > node. Best practices might suggest we do. We can also give cluster-admin > > role to all users in the sysadmin-main and sysadmin-openshift groups. > > Yeah, we should put this in the playbook so it's very clear who has this > and when it was added, etc. > > > I'm in two minds about deleting it, I was hoping to wait until we get a > > solution that syncs IPA groups/users to Openshift. There is an official > > supported solution for syncing LDAP (think that will work?). > > Yeah, needs investigation. > > > > * Right now the api is only internal. Is it worth getting a forward > > > setup to allow folks to use oc locally on their machines? It would > > > expose that api to the world, but of course it would still need auth. > > We'd love to expose it, but.. all interaction with the clusters upto this > > point have also only been done via Ansible, so if it turns out we can't > > expose the API like this we're ok with that. With minor changes to the > > playbook we should be able to at least replicate the current 3.11 > > experience. > > Sure, but currently app owners can use oc on their local machines to > view logs, debug, etc. I think thats a nice thing to keep working. >
Re: Openshift 4 SOP PR review
> I believe the Hyperscale SIG is using it. Or if they're not, it's > because they don't know it's there. It might also be they don't have permission to create the kubevirt api objects on the CentOS CI cluster. If they are actively interested in this, we can sync up and figure out exactly what permissions are required to make use of it! On Fri, 24 Sept 2021 at 12:08, Neal Gompa wrote: > On Thu, Sep 23, 2021 at 11:02 PM David Kirwan wrote: > > > > > On the storage, are we ok if a node goes down? ie, does it spread it > > > over all the storage nodes/raid? Or is it just in one place and you are > > > dead if that node dies? > > For storage, we maintain 3 replicas for data, spread across 3 nodes. > However, not all nodes are equally resourced, we have 2 large nodes and 1 > much smaller, therefore, more replicas will be spread over these 2 larger > nodes. We can likely afford to lose one of the large physical nodes while > still maintaining data integrity. > > > > > Is there any way to backup volumes? > > There are ways to clone, extend, take snapshots etc of these volumes. > We've never done it, so it'll be a learning process for us all ;). We > should sync to get a better handle on the requirements for backups. In > CentOS CI we've set up backups to S3, we can certainly use some of that, > eg: backup of etcd, but may need further investigation to backup the > volumes managed by OCS. Will need to do some research here. > > > > > should we make a playbooks/manual/ocp.yml playbook for things like > > > - list of clusteradmins > > > - list of clustermoniting > > > - anything else we want to manage post install > > Sure yep, as we're finishing up soonish, I'd imagine the next few weeks > we'll all be back focused on the Infra/Releng tasks and will be focusing on > tying up any loose ends like this, and starting migration of apps. > > > > > Have we tried a upgrade of the clusters yet? Did everything go ok? > > > Do we need any docs on upgrades? > > Yes, we've already completed a number of upgrades, latest is to 4.8.11. > We have SOPs for upgrades which we can copy over from the CentOS CI infra, > and will make any updates required in the process. > > > > > > > Since the control plane are vm's I assume we need to drain them one at > > > a time to reboot the virthosts they are on? > > If we are rebooting a single vmhost/control plane VM at a time, yes that > should be good. If we are doing more than 1 at the same time, we should do > a full graceful cluster shutdown, and then a graceful cluster startup. We > have SOPs for this in CentOS CI also, we'll get those added here and any > content updates made. > > > > > * Should we now delete the kubeadmin user? In 3.x I know they advise to > > > do that after auth is setup. > > We can delete it, as we have system:admin available from the > os-control01 node. Best practices might suggest we do. We can also give > cluster-admin role to all users in the sysadmin-main and sysadmin-openshift > groups. > > I'm in two minds about deleting it, I was hoping to wait until we get a > solution that syncs IPA groups/users to Openshift. There is an official > supported solution for syncing LDAP (think that will work?). > > > > > * Right now the api is only internal. Is it worth getting a forward > > > setup to allow folks to use oc locally on their machines? It would > > > expose that api to the world, but of course it would still need auth. > > We'd love to expose it, but.. all interaction with the clusters upto > this point have also only been done via Ansible, so if it turns out we > can't expose the API like this we're ok with that. With minor changes to > the playbook we should be able to at least replicate the current 3.11 > experience. > > > > >> That's what we decided to do for the CentOS CI ocp setup, and so CI > > >> tenants can use oc from their laptop/infra. As long as cert exposed > for > > >> default ingress has it added in the SAN, it works fine : > > >> > > >> X509v3 Subject Alternative Name: > > >> DNS:*.apps.ocp.ci.centos.org, DNS: > api.ocp.ci.centos.org, > > >> DNS:apps.ocp.ci.centos.org > > > > > Yeah, thats all fine, but to make it work for our setup, I would need > to > > > get RHIT to nat in port 6443 to proxy01/10 from the internet. At least > I > > > think thats the case. Openshift 3 could just use https, but alas, I > fear > > > OCP4 needs that 6443 port. > > Yep think you're right on that. > > > > > > >Do we want to try and enable http/
Re: Openshift 4 SOP PR review
assume we need to drain them one > at > > >> a time to reboot the virthosts they are on? > > > > Correct > > > > >> > > >> * Should we now delete the kubeadmin user? In 3.x I know they advise > to > > >> do that after auth is setup. > > >> > > > > > > I'm not sure that's a good idea. I'm not even certain that was a good > > > idea in the OCP 3.x days, because eliminating the kubeadmin user means > > > you lose your failsafe login if all else fails. > > > > +1 here : the reason why we decided to still keep kubeadmin on the other > > OCP clusters used for CentOS CI and Stream is exactly for that reason : > > still be able to login, if there is a problem with the oauth setup, and > > troubleshoot issues if (for example) ipsilon or IPA have troubles ... > :-) > > We can keep it if folks like. I'd really prefer we don't use it except > for emergency though. Having people do things as their user will make it > way easier to see who did what. ;) > > > >> * Right now the api is only internal. Is it worth getting a forward > > >> setup to allow folks to use oc locally on their machines? It would > > >> expose that api to the world, but of course it would still need auth. > > > > That's what we decided to do for the CentOS CI ocp setup, and so CI > > tenants can use oc from their laptop/infra. As long as cert exposed for > > default ingress has it added in the SAN, it works fine : > > > > X509v3 Subject Alternative Name: > > DNS:*.apps.ocp.ci.centos.org, DNS:api.ocp.ci.centos.org, > > DNS:apps.ocp.ci.centos.org > > Yeah, thats all fine, but to make it work for our setup, I would need to > get RHIT to nat in port 6443 to proxy01/10 from the internet. At least I > think thats the case. Openshift 3 could just use https, but alas, I fear > OCP4 needs that 6443 port. > > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Openshift 4 SOP PR review
Hi all, We have put a number of SOPs together, related to Openshift 4, installation and configuration on Fedora Infra, we are hoping to get some feedback! If you get a minute please check the following: https://pagure.io/infra-docs-fpo/pull-request/8 -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: metrics-for-apps: DNS patch for two prod workers of OCP cluster
Oops, fixed that error on lines 48-51 now. On Wed, 1 Sept 2021 at 02:25, kevin wrote: > On Tue, Aug 31, 2021 at 01:35:05PM +0200, Michal Konecny wrote: > > This patch should be probably marked as freeze break request. > > Well, it's content, not configuration, so usually we allow dns changes. > > But I agree it's good to review. > > > On 31. 08. 21 12:18, David Kirwan wrote: > > > Thanks Kevin, we think we've addressed this in the latest version at > > > https://gist.github.com/davidkirwan/bd2b84f05a67123a9254e055d336f1e7 > > > <https://gist.github.com/davidkirwan/bd2b84f05a67123a9254e055d336f1e7> > > > > > > Can you take another look please > > So, it looks mostly good, but not sure about lines 48-51. > You shouldn't need to change that there? Leave the stg one pointing to > stg wildcard and don't add another copy pointing to prod wildcard? > > ie, I think that change doesn't need to be in there. ;) > > Otherwise looks good. > > kevin > -- > > > > > > On Mon, 30 Aug 2021 at 23:57, Kevin Fenzi > > <mailto:ke...@scrye.com>> wrote: > > > > > > On Mon, Aug 30, 2021 at 07:49:54AM -0700, Kevin Fenzi wrote: > > > > On Mon, Aug 30, 2021 at 07:38:04AM +0530, Akashdeep Dhar wrote: > > > > > Hello, > > > > > > > > > > A small change - "metric-for-apps: DNS patch for prod nodes of > > > OCP cluster" > > > > > is to be the commit messages. > > > > > > > > > > Mark and Kevin, > > > > > > > > > > Could you please update the LetsEncrypt ACME challenge? > > > > > > > > Just leave those commented out. We get that when we ask for the > > > cert(s). > > > > > > > > Aside that, looks good to me. +1 to push anytime... > > > > > > Oh wait. There's another issue here. > > > > > > Right now with the 3.11 cluster, we run a vpn connection on all the > > > compute nodes. This allows non IAD2 proxies to reach them. > > > > > > For theis 4 cluster are we going to: > > > > > > 1. Somehow run openvpn clients on the nodes > > > > > > or > > > > > > 2. Not going to do that. > > > > > > Of course not running vpn on them is easier configuration wise, > but it > > > means that we don't want to have dns resolve the cluster as > 'wildcard' > > > (all proxies), but instead just want to resolve to the IAD2 proxies > > > directly. For example, koji is like this: > > > > > > kojiINA 38.145.60.20 > > > kojiINA 38.145.60.21 > > > > > > Sorry I didn't think of this, need more coffee. ;) > > > > > > kevin > > > ___ > > > infrastructure mailing list -- > > > infrastructure@lists.fedoraproject.org > > > <mailto:infrastructure@lists.fedoraproject.org> > > > To unsubscribe send an email to > > > infrastructure-le...@lists.fedoraproject.org > > > <mailto:infrastructure-le...@lists.fedoraproject.org> > > > Fedora Code of Conduct: > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> > > > List Guidelines: > > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > <https://fedoraproject.org/wiki/Mailing_list_guidelines> > > > List Archives: > > > > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > > < > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > > > > Do not reply to spam on the list, report it: > > > https://pagure.io/fedora-infrastructure > > > <https://pagure.io/fedora-infrastructure> > > > > > > > > > > > > -- > > > 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
Re: metrics-for-apps: DNS patch for two prod workers of OCP cluster
Thanks Kevin, we think we've addressed this in the latest version at https://gist.github.com/davidkirwan/bd2b84f05a67123a9254e055d336f1e7 Can you take another look please On Mon, 30 Aug 2021 at 23:57, Kevin Fenzi wrote: > On Mon, Aug 30, 2021 at 07:49:54AM -0700, Kevin Fenzi wrote: > > On Mon, Aug 30, 2021 at 07:38:04AM +0530, Akashdeep Dhar wrote: > > > Hello, > > > > > > A small change - "metric-for-apps: DNS patch for prod nodes of OCP > cluster" > > > is to be the commit messages. > > > > > > Mark and Kevin, > > > > > > Could you please update the LetsEncrypt ACME challenge? > > > > Just leave those commented out. We get that when we ask for the cert(s). > > > > Aside that, looks good to me. +1 to push anytime... > > Oh wait. There's another issue here. > > Right now with the 3.11 cluster, we run a vpn connection on all the > compute nodes. This allows non IAD2 proxies to reach them. > > For theis 4 cluster are we going to: > > 1. Somehow run openvpn clients on the nodes > > or > > 2. Not going to do that. > > Of course not running vpn on them is easier configuration wise, but it > means that we don't want to have dns resolve the cluster as 'wildcard' > (all proxies), but instead just want to resolve to the IAD2 proxies > directly. For example, koji is like this: > > kojiINA 38.145.60.20 > kojiINA 38.145.60.21 > > Sorry I didn't think of this, need more coffee. ;) > > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
DNS patch request to enable ocp staging worker01-03
https://gist.github.com/davidkirwan/ae4038fa101dea3e8e1318ce3330970b Hi infra, can I please get a review on the patch above, we are configuring the ocpstaging worker machines to boot via dhcp. cheers -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNS patch to rename ocp4 clusters, and revert vhmost-ocp changes
okie dokie, ill update that gist now thanks Stephen! On Thu, 15 Jul 2021 at 10:18, Stephen John Smoogen wrote: > On Thu, 15 Jul 2021 at 04:53, David Kirwan wrote: > > > > The previous changes to those management hosts, were a name change so I > think we should probably leave those as they where so they are still > accessible on the management network. The hosts themselves are older > hardware Kevin was suggesting that we might throw out or retire soon. > > > > Think the idea is instead of using those, is to use the existing > vmhost-x86-05/06/07/11 staging as all free capacity/newer boxes. > > > > OK as long as the hosts ping/respond on that network, they should have > ip addresses in DNS. Otherwise the following happens: > 1. We try to use those ips for a new box and both systems go dead. > [That usually needs someone to go onto the hardware via a KVM and > fix.] > 2. We get a scan/audit from RH and they want to know what hardware is > on that address and is it an attacker/etc. > 3. The box gets turned off and then comes back on somehow. Then we may > have an ip conflict. > > So until the hardware is physically removed from the racks.. keep its > mgmt ip in DNS. Maybe change the name to oldhost or retired .. but > keep it there until then. > > > On Thu, 15 Jul 2021 at 09:22, Stephen John Smoogen > wrote: > >> > >> On Thu, 15 Jul 2021 at 04:18, David Kirwan wrote: > >> > > >> > https://gist.github.com/davidkirwan/ecc1c135b6f2c82b1ef337ebdcd8414b > >> > > >> > Hi folks if someone would be so kind as to take a look over our > changes here, we want to revert some vhmost-ocp4 changes and rename the ocp > hosts. > >> > > >> > Just two things to be aware: > >> > > >> > This is commented out line is intentional, as we wish to reuse the > bootstrap.ocp node to become the worker01.ocp node after the control plane > has been installed. > >> > +;worker01.ocp IN A 10.3.166.118 > >> > > >> > Second question, we've removed the vmhost-ocp nodes from the 160. > management network, not sure if we should have done that. > >> > > >> > >> Where are the management ports for these boxes going to be? Is > >> 10.3.160.40 really unused? > >> > >> > >> > cheers, > >> > David > >> > > >> > > >> > > >> > -- > >> > 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 > >> > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > >> > >> > >> > >> -- > >> Stephen J Smoogen. > >> I've seen things you people wouldn't believe. Flame wars in > >> sci.astro.orion. I have seen SPAM filters overload because of Godwin's > >> Law. All those moments will be lost in time... like posts on BBS... > >> time to reboot. > >> ___ > >> 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 > >> Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > > > > > > > > -- > > 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 >
Re: DNS patch to rename ocp4 clusters, and revert vhmost-ocp changes
The previous changes to those management hosts, were a name change so I think we should probably leave those as they where so they are still accessible on the management network. The hosts themselves are older hardware Kevin was suggesting that we might throw out or retire soon. Think the idea is instead of using those, is to use the existing vmhost-x86-05/06/07/11 staging as all free capacity/newer boxes. On Thu, 15 Jul 2021 at 09:22, Stephen John Smoogen wrote: > On Thu, 15 Jul 2021 at 04:18, David Kirwan wrote: > > > > https://gist.github.com/davidkirwan/ecc1c135b6f2c82b1ef337ebdcd8414b > > > > Hi folks if someone would be so kind as to take a look over our changes > here, we want to revert some vhmost-ocp4 changes and rename the ocp hosts. > > > > Just two things to be aware: > > > > This is commented out line is intentional, as we wish to reuse the > bootstrap.ocp node to become the worker01.ocp node after the control plane > has been installed. > > +;worker01.ocp IN A 10.3.166.118 > > > > Second question, we've removed the vmhost-ocp nodes from the 160. > management network, not sure if we should have done that. > > > > Where are the management ports for these boxes going to be? Is > 10.3.160.40 really unused? > > > > cheers, > > David > > > > > > > > -- > > 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 > > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > > > > -- > Stephen J Smoogen. > I've seen things you people wouldn't believe. Flame wars in > sci.astro.orion. I have seen SPAM filters overload because of Godwin's > Law. All those moments will be lost in time... like posts on BBS... > time to reboot. > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
DNS patch to rename ocp4 clusters, and revert vhmost-ocp changes
https://gist.github.com/davidkirwan/ecc1c135b6f2c82b1ef337ebdcd8414b Hi folks if someone would be so kind as to take a look over our changes here, we want to revert some vhmost-ocp4 changes and rename the ocp hosts. Just two things to be aware: This is commented out line is intentional, as we wish to reuse the bootstrap.ocp node to become the worker01.ocp node after the control plane has been installed. +;worker01.ocp IN A 10.3.166.118 Second question, we've removed the vmhost-ocp nodes from the 160. management network, not sure if we should have done that. cheers, David -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNS patch to enable OCP 4 staging cluster deploy
Cheers for the feedback folks, we've made the suggested edits to the gist, and hopefully this is correct now, if you could take another look when you get a chance! On Tue, 13 Jul 2021 at 07:52, darknao wrote: > > On 2021-07-13 02:33, Kevin Fenzi wrote: > > ocp -> console "app" > > .apps.ocp -> each application... > > > > So, I think both are needed. > > > Oh ok, that make senses. > On OCP4, by default, console is also behind apps (something like > console-openshift-console.apps) but I get why you would want to change > that :) > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
DNS patch to enable OCP 4 staging cluster deploy
Hi folks, We're hoping to get the following patch merged to the Fedora infra DNS repo to allow us to begin deploying the OCP4 cluster for staging. https://gist.github.com/davidkirwan/11b7165778e7f252ae4fe14fc69fb60d I think this is enough to get started, but would be good to get some feedback as we might have missed something. cheers, David -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Congrats to Tomáš Hrčka
Nice one Tomáš! On Wed, 17 Mar 2021 at 20:06, Damian Tometzki wrote: > Hello, > > great, goog luck :-) > > Best regards > Damian > > On Tue, 16. Mar 14:06, Kevin Fenzi wrote: > > Greetings. > > > > I'm happy to announce that Tomáš Hrčka (fas: humaton, irc: jednorozec) > > has been added to our sysadmin-main group. > > > > This is the core group of trusted folks that high level access to most > > everything in fedora infrastructure. > > > > Tomáš has been doing a great job working on releng tasks as well as > > releng apps and scripting and the like. > > > > He's proved his dedication, trustworthiness, and ability. > > > > Congrats! > > > > Use your powers for good! :) > > > > 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 > > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Potential service degradation - containers and flatpaks builds (OSBS) - 2020-11-26 09:30 UTC
There will be potential service degradation for OSBS starting at 2020-11-26 09:30 UTC Work is being carried out to add an aarch64 build cluster to production OSBS. While this work is being carried out you may experience some containers or flatpaks build failures. Please follow the outage ticket https://pagure.io/fedora-infrastructure/issue/9489 to keep track of its status. Thanks, Fedora OSBS Initiative -- 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: Congrats to our new sysadmin-mainers
hehe congrats Aurelien/Mark On Mon, 17 Aug 2020 at 08:46, Aurelien Bompard wrote: > > I'm happy to announce that We have approved several folks into the >>> sysadmin-main group: >>> >>> mobrien - Mark O'Brien >>> abompard - Aurelien Bompard >>> >>> This is the core group of trusted folks that high level access to most >>> everything in fedora infrastructure. >>> >>> > Thanks everyone! > I'm just back from holidays and my unencrypted laptop with my passwordless > SSH key was stolen. > JUST KIDDING! Haha, very funny, no? No? Okay. > /me goes update his mail filters. > > A. > ___ > 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: Meeting Agenda Item: Introduction Mohammed Tayeh
Welcome Mohammed! Few links to help get you started: 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 Wed, 8 Jul 2020 at 18:42, Mohammed Tayeh wrote: > Hi All, > I'm a Systems Administrator, I have more than 4 years Experiences at > Orange Palestine co. (ISP Company) > I'm using Fedora on my main laptop over 5 years and I'm looking to > contribute to the Fedora community > > my IRC nickname is "Tayeh" > I'm a certified Linux System Admin (LFCSA), and I'm worked on a lot of > projects > I want to join the fedora system admin team if possible > and I need to learn more from the fedora team and improve my skills > > I need some help from the team to help me to get started with fedora > sysadmin team > > Best Regards > > > [image: Sent from Mailspring] > ___ > 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: What is our technical debt?
Sure, I'm not an expert by any means, but I'm happy to share what little I do know! :P wanna hop on a hangouts/bluejeans call some day ? I have the POC example currently running on the ocp.stg.ci.centos.org, can use that to give a quick demo. On Sat, 4 Jul 2020 at 19:55, Kevin Fenzi wrote: > On Sat, Jul 04, 2020 at 01:14:42AM +0100, David Kirwan wrote: > > 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 > > Cool! > > I'd love to have you go through this and describe how it works/looks? > > I'm sure others would be interested as well... > > 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: 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]
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
Re: What is our technical debt?
On Fri, 26 Jun 2020 at 17:53, Kevin Fenzi wrote: > On Fri, Jun 26, 2020 at 10:32:14AM +0100, David Kirwan wrote: > > Hi all, > > > > If we are moving towards openshift/kubernetes backed services, we should > > probably be sticking with containers rather than Vagrant. We can use CRC > > [1] (Code Ready Containers) or minikube [2] for most local dev work. > > > > I'd be very much in favour of having an Infra managed Prometheus instance > > (+ grafana and alertmanager on Openshift), its something I hoped to work > on > > within CPE sustaining infact. > > You know, I'm not in love with that stack. It could well be that I just > haven't used it enough or know enough about it, but it seems just > needlessly complex. ;( > 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). 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]. 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. - [1] https://docs.openshift.com/container-platform/4.4/monitoring/monitoring-your-own-services.html -- 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: What is our technical debt?
Hi all, If we are moving towards openshift/kubernetes backed services, we should probably be sticking with containers rather than Vagrant. We can use CRC [1] (Code Ready Containers) or minikube [2] for most local dev work. I'd be very much in favour of having an Infra managed Prometheus instance (+ grafana and alertmanager on Openshift), its something I hoped to work on within CPE sustaining infact. - [1] https://github.com/code-ready/crc - [2] https://minikube.sigs.k8s.io/docs/ On Fri, 26 Jun 2020 at 10:23, Luca BRUNO wrote: > On Thu, 25 Jun 2020 15:59:44 -0700 > Kevin Fenzi wrote: > > > > What else would we want in there? > > > > Monitoring - we will likely get our nagios setup again soon just > > because it's mostly easy, but it's also not ideal. > > On this one (or more broadly "observability") I'd still like to see an > infra-managed Prometheus to internally cover and sanity-check the > "openshift-apps" services. > I remember this was on the "backlog" dashboard at Flock'19 but I don't > know if it got translated to an actual action item/ticket in the end. > > Ciao, Luca > ___ > 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: Introduction Jens Maucher 'jmaucher'
Welcome Jens o/ On Sat, 25 Apr 2020 at 22:19, Jens Maucher wrote: > Hi, > > my name is Jens and i'm from Germany. I am 47y old/young and I'm > working as an Bachelor Professional of Electrical Technology and > Management. In my sparetime i am currently learning for the LPIC > certification, why? Well... i'm working with Linux since 2000, beginning > with SuSE 6.4 and debian. Since 2009 i'm using Fedora. > > I have a lot of fun with Linux, learning every day new things. So i > decided to take a exam for myself, not for my company. > > On IRC in freenode i am now 15 years. Generally i want to learn more > about basic system-administration to get more experience to pass my > exam, and i would be happy to get the chance to to that :) > > ~ > Jens > > ___ > 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 Red Hat Cloud Services Communications House Cork Road, Waterford dkir...@redhat.comT: +(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: Meeting Agenda Item: Introduction Keerthi Chinthaguntla (Keerthi)
Welcome Keerthi o/ On Tue, 28 Apr 2020 at 18:04, wrote: > > > Hello all, > Hope youre doing well, My name is Keerthi, I am currently working as a > Systems Tech, I am located in the US (CST). As part of my job I primarliy > work with windows (both servers and desktops), I started learning Linux > couple of years ago and now I use Linux (Fedora) as my daily driver. > > *What skills you have to offer and which you would like to learn : * > > I am familier with Python, HTML, CSS, Ansible, Linux administration, Basic > knowledge on MariaDB, MySQL DB, and Containers, familier with AWS (Learning > and preparing for certs), currently I hold AWS Could Practioner Cert. These > are not something that I use everyday at my work but something I picked up > and started learning on my down time, I've joined RedHat's #EnableSysadmin > community, started wirting articles on various sysadmin topics. > > I would like to lean more about the Fedora-Infrastructure team, get > familier with tha workflow and pickup easyfixes and build upon as i go. > > *IRC handle :* iamkc > > Looking forward to Learn, contribute and share, > > Thanks for your time, > > > ___ > 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 Red Hat Cloud Services Communications House Cork Road, Waterford dkir...@redhat.comT: +(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: Meeting Agenda Item: Introduction Mark O'Brien
Welcome Mark :) On Fri, 17 Apr 2020 at 07:50, Clement Verna wrote: > > > On Thu, 16 Apr 2020 at 13:43, Mark O'Brien wrote: > >> Hello, >> >> May name is mark, I have just started as a software engineer at redhat, I >> have worked as a DevOps for 3 years previously and am familiar with tooling >> such as ansible and scripting languages such as python and bash. >> > > > Welcome Mark, looking forward to work with you :-) > > >> >> My irc handle: mjobrien >> ___ >> 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 > -- David Kirwan SOFTWARE ENGINEER Red Hat Cloud Services Communications House Cork Road, Waterford dkir...@redhat.comT: +(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: Hello world!
Hi Vit, I'm going to start reading the howto get involved in the packaging process for Fedora over the weekend and start to get my access to the various systems, if I run into any issues I'll reach out to folks on IRC! Looking forward to helping out (in some minor fashion! :D) cheers, David On Wed, 8 Apr 2020 at 08:33, Vít Ondruch wrote: > Welcome! > > Should you have any Ruby packaging question, please don't hesitate and > contact me :) > > > Vít > > > Dne 07. 04. 20 v 17:42 David Kirwan napsal(a): > > Hello all, > > My name is David Kirwan, I'm originally from Kilkenny, Ireland, now living > in Waterford, Ireland. I've recently transferred to the CPE team at Red > Hat, where I'll likely be working on CentOS and Fedora infrastructure in a > devops capacity. I also hope to get involved in some of the packaging work > for the Ruby/ML SIGs, although that might be in my spare time! > > To share a little background about me, I spent a few years as a software > researcher, working on projects in the energy sector, security and software > defined networking. In my previous role at Red Hat, I worked as a > devops/releng engineer on an operations team responsible for maintaining a > hosted SaaS product. Most recently, I've been working as a regular software > engineer on a team developing and improving Red Hat's middleware products > to work on Openshift 3/4 using Kubernetes "Operators" (Custom resource > controllers). > > When I'm not working, I try to spend as much time as possible getting > involved in the local Makerspace (South East Makerspace), working on > personal art, astronomy, amateur radio, diy, electronics and woodworking > projects. I'm delighted to be here, and I'm looking forward to working with > everyone! > > -- > > David Kirwan > > SOFTWARE ENGINEER > > Red Hat Cloud Services > > Communications House > > Cork Road, Waterford > > dkir...@redhat.comT: +(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 > -- David Kirwan SOFTWARE ENGINEER Red Hat Cloud Services Communications House Cork Road, Waterford dkir...@redhat.comT: +(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
Hello world!
Hello all, My name is David Kirwan, I'm originally from Kilkenny, Ireland, now living in Waterford, Ireland. I've recently transferred to the CPE team at Red Hat, where I'll likely be working on CentOS and Fedora infrastructure in a devops capacity. I also hope to get involved in some of the packaging work for the Ruby/ML SIGs, although that might be in my spare time! To share a little background about me, I spent a few years as a software researcher, working on projects in the energy sector, security and software defined networking. In my previous role at Red Hat, I worked as a devops/releng engineer on an operations team responsible for maintaining a hosted SaaS product. Most recently, I've been working as a regular software engineer on a team developing and improving Red Hat's middleware products to work on Openshift 3/4 using Kubernetes "Operators" (Custom resource controllers). When I'm not working, I try to spend as much time as possible getting involved in the local Makerspace (South East Makerspace), working on personal art, astronomy, amateur radio, diy, electronics and woodworking projects. I'm delighted to be here, and I'm looking forward to working with everyone! -- David Kirwan SOFTWARE ENGINEER Red Hat Cloud Services Communications House Cork Road, Waterford dkir...@redhat.comT: +(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
