Re: IPAM/DCIM for Fedora Infrastructure
Thanks for the information, Kevin. On 02/09/2020 23:39, Kevin Fenzi wrote: On Tue, Sep 01, 2020 at 06:21:58AM -0400, Stephen John Smoogen wrote: On Tue, 1 Sep 2020 at 02:36, Manu Hernandez wrote: Hi! I was going to suggest NetBox as well. NetBox is also a data center management infrastructure tool (DCIM) too, so it can be used to document racks, circuits, power, etc. https://netbox.readthedocs.io/en/stable/ Another thing: RHIT uses their own DCIM to keep track of things... so if we use our own thats another place to update, etc. RHIT == Red Hat Infrastructure Team? Of course anything we run will be open, while the RHIT one will likely be limited to employees. :( kevin Does Red Hat manage all the Fedora infrastructure? If that's *not* the case, I suppose their DCIM will have only the systems under their control. Who manages/tracks the rest? ___ 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: IPAM/DCIM for Fedora Infrastructure
This is a useful tool and one I could have used during the move.. However I have a couple of concerns. One issue is that we would only be able to use it as a reactive tool. We do not control the physical layout, the network, the power and other items for any of our 'clusters' of systems. For most of our systems in different datacenters I have never seen where they are, how they are laid out, etc. I didn't know that... As someone used to have its servers at hand, this is new to me (and a bit strange, to be honest, but I suppose it's common in large environments) Who does all that? (I mean, the tasks at the DC) Instead I need to rely on different tools at each site to keep that data in place (and for several places that can change regularly). Which tools are those? Are they accessible to the fi-apprentice team? Secondly I don't know how useful this data would be to apprentices if it was kept up to date. The more data in it, the more we would need to lock it down because it would contain non-disclosure data (various sites who lend us systems have different rules for what information they consider public/private.. what limited we have in ansible is generally what is considered what we could share.) So, is that information accesible only to some Fedora infra teams? To Red Hat employees? Do you have to sign some kind of NDA? Other things like serial numbers of systems are considered sensitive because they can be used to defraud our warranty. [Having had parts ordered for a system we had under warranty to a third party for resale is not something I want to deal with again.] I have no words. Faith in humanity -1 Neither of these concerns are end-of-the-world but they need to be dealt with in any plan to install this service somewhere and then populate it with data. ___ 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: Buildsystem indentification
On Thu, Sep 03, 2020 at 02:42:21PM +0200, Miroslav Suchý wrote: > FYI > Mock 2.5 has been just released and contains > https://github.com/rpm-software-management/mock/pull/608 > which set different user agent for DNF when DNF is used by Mock. > This may allow you to differ Mock from users when creating statistics about > downloads from repo. Very nice. Thanks! kevin signature.asc Description: PGP signature ___ 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
[Fedocal] Reminder meeting : Fedora Infra docs Hackfest
Dear all, You are kindly invited to the meeting: Fedora Infra docs Hackfest on 2020-09-04 from 14:00:00 to 17:00:00 Europe/Dublin At fedora-meetin...@freenode.net The meeting will be about: Fedora Infra docs hackfest. See agenda at https://board.net/p/infra-doc-hackfest Video meeting link https://meet.google.com/nxd-yxgb-hyh Source: https://apps.fedoraproject.org/calendar/meeting/9799/ ___ 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
Buildsystem indentification
FYI Mock 2.5 has been just released and contains https://github.com/rpm-software-management/mock/pull/608 which set different user agent for DNF when DNF is used by Mock. This may allow you to differ Mock from users when creating statistics about downloads from repo. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #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
Framework
> Hi, > > I've worked closely with some really great frontend development teams in the > last > couple of > years and I vote for React. > > Warm Regards, > Jessica > https://www.unifiedinfotech.net/ Take a look at this one https://steelkiwi.com/blog/add-an-admin-panel-to-nodejs-project/ ___ 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: About JS framework
Nice article. This one is good too https://steelkiwi.com/blog/add-an-admin-panel-to-nodejs-project/ ___ 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
