Re: packages app

2020-07-27 Thread Brendan Early 
On 7/27/20 9:40 AM, Miroslav Suchý wrote:
> Dne 16. 07. 20 v 21:56 Brendan Early napsal(a):
>> and would time out if an external service took too long to respond.
> Only if you wanted to list builds, bugs the overview page is more or less 
> static (i.e. it is rendered just from
> local DB). 

I was basing that statement off of a quick skim of old fedora packages
source. I may be mistaken as I'm still new to python, but I was under
the impression that it always queried koji when it was given a request.

https://github.com/fedora-infra/fedora-packages/blob/master/fedoracommunity/widgets/package/overview.py#L50-L57

> Fedora-packages-static does not list them at all. This is ok when we agree 
> that this is what people find
> sufficient.

This is intentional, I can easily write some client-side JS to add that
functionality if it is needed.

https://pagure.io/fedora-packages-static/pull-request/1#comment-0

> What I am curious about fedora-packages-static - how long it takes to 
> generate all those pages? When I tried to retrieve
> initial data fedora-packages-ng, it took several hours. Which may be too much 
> for daily job.
How are you getting the data in ng?! From a clean state on my computer,
it takes packages-static around 140 seconds to get the package metadata
into the db and about 195 seconds to generate all the static pages.
>   How much data it consumes?
Not anything monumental, just ~6.3G.
> What is yacysearchserver-pkgs-playground.apps.os.fedorainfracloud.org?

A staging YaCy server that Timothée had on communishift.

https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/4PE4YQ4SGRCA3JIMFKRBMLR7CXDC45GT/
>  Or when we delegate search to Google, how long it
> takes to refresh the search index?
I have code to generate sitemaps, which can be used to tell Google how
often we want to be crawled and it will make sure every page is indexed.
This should improve discoverability, I don't know how well the old one
was indexed.
>  Will be people ok with the speed?
I don't understand exactly what you are referring to here. If you mean
the speed of search, I don't specifically know about the speed of Solr.
In the event hosting something ourselves does not work out we could
always go with Algolia, which is near-instant.



signature.asc
Description: OpenPGP digital 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

Re: s390x for EPEL

2020-07-27 Thread Kevin Fenzi 
On Mon, Jul 27, 2020 at 04:45:58PM +0200, Miroslav Suchý wrote:
> What is using Koji to build EPEL builds for s390x.

We are using 2 LPARS on a z13 mainframe in a Red Hat lab in Westford, MA.

> We want to enable s390x in Copr. It is without problem for Fedora, but we 
> cannot do that for EPEL, because there is no

Can you explain how you plan to do Fedora s390x builds? Emulation?

> CentOS for s390x. Do we have entitlements for RHEL I can use? Or we have some 
> local repo? Something completely different?

We have local repo synced from RHN with our Fedora Org. 

I don't think we can give external access to that repo. 

It might also be weird to have just one arch of something be against
RHEL instead of Centos. Is there no Centos port in progress?

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

Re: packages app

2020-07-27 Thread Kevin Fenzi 
On Tue, Jul 21, 2020 at 04:14:39PM -0500, Brendan Early wrote:
> 
> I didn't realize at the time that there were two solutions being
> developed. Timothée was giving lots of status updates and you and
> Clement were active in those discussions, so it wasn't very obvious from
> my point of view as a fairly new contributor here. I don't know if it's
> possible to merge the two. I don't see the point of spitting the
> functionality as they mostly do the same thing.

Right. I'm happy for any good solution...I wasn't aware that msuchy was
working on a replacement (other than just saying he would if he found
time) until he appeared with the initial project. ;) 

kevin
--
> 
> 
> Brendan Early
> 
> >
> > kevin
> > --
> >> Pagure: https://pagure.io/fedora-packages-static
> >>
> >> --
> >>
> >> Brendan Early
> >>
> >> On 7/16/20 12:06 PM, Kevin Fenzi wrote:
> >>> So, I think we have two groups approaching a replacement app for
> >>> packages?
> >>>
> >>> Can we perhaps decide which way we want to go and look at deploying
> >>> something soon? This has been more important since we didn't move the
> >>> old broken packages app from the old datacenter and people keep asking
> >>> about it.
> >>>
> >>> We could wait until we have staging back, but I don't think we need to
> >>> wait for that to decide what we want to do here?
> >>>
> >>> Thoughts?
> >>>
> >>> 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
> >> ___
> >> 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
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCAAdFiEEEuO7QAvcjGvjf8zLJc9/feL/WqkFAl8XWqsACgkQJc9/feL/
> WqmQgA/+Lki6d5XZjItBp9k8jtapnaaCPQkClYbZ+j1WE51onGhktD89x9LE/GtJ
> WAqdbEdMRcgJPMAtOiYAQzlWXwny6qvODw+XoOqFf0Zp5VyAeOkxyhczdLDguP7N
> NYoWUj86S0QK+SFZyKMin8ExD9tnICIX/e9J9UCKNmDGxvMADtm3A5iO3LRxOaN4
> 8Ko+S3EE4FujBDpIN/+WMZbCSXKU4j1N2KD2tPXaeimzyKCShFXXggGc4kAsJI0/
> xsCJNl8WO7gZ/8kw/hjZU17q+l68LR4e01+/OBEsHZhCVbxG/RGkNsXIA2UBYF4A
> sH7mibpgFcULJr+5fhPjgyRTeTl5dFK6Wy2ikneNzDH3v44DT34Y1OaWyvdnaSuE
> gz0+ouZ9UOYKNPxi3kysDZkPj9A+n/Oq0Hze2c5CP1gtkROUzjpQdDeO/0Qy9upu
> Kt3VjkqMB320OVCdHrbLhhiirazePWxOoQnFBwIrkyRGVKrIrYhQQmpVwxcIwp3Y
> MW2xlPphqRkpzaVkblkTBQ5rQdFJc4B3X04q3u2+su48TMztFoEzQRC0U1DTRK2Q
> c+Q8crkE9Tvt25Y2OyIADPABUnVwhtXFxRZCrVemWy87kGxNY0Uf7lHJ+RQyZjst
> B69+We2MlU47Vw0KWMeIPbKn65J3YYG7jzlKY2Qe/1aH8/VUUzY=
> =hbr0
> -END 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



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

Re: s390x for EPEL

2020-07-27 Thread Miroslav Suchý 
Dne 27. 07. 20 v 16:50 Stephen John Smoogen napsal(a):
> Can you use CleFOS for s390x?

This?
https://hub.docker.com/_/clefos/

I will try to rather use RHEL directly. I will see if I can get the 
entitlements.
-- 
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

Re: s390x for EPEL

2020-07-27 Thread Stephen John Smoogen 
On Mon, 27 Jul 2020 at 10:46, Miroslav Suchý  wrote:
>
> What is using Koji to build EPEL builds for s390x.
>

EPEL uses RHEL for all its builds. The problem is that the license we
have for RHEL is meant just for this and we have not been able to
extend it to COPR in the past. The issues are legal, accounting and a
couple of other ones. Can you use CleFOS for s390x?


> We want to enable s390x in Copr. It is without problem for Fedora, but we 
> cannot do that for EPEL, because there is no
> CentOS for s390x. Do we have entitlements for RHEL I can use? Or we have some 
> local repo? Something completely different?
> --
> 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



-- 
Stephen J Smoogen.
___
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

s390x for EPEL

2020-07-27 Thread Miroslav Suchý 
What is using Koji to build EPEL builds for s390x.

We want to enable s390x in Copr. It is without problem for Fedora, but we 
cannot do that for EPEL, because there is no
CentOS for s390x. Do we have entitlements for RHEL I can use? Or we have some 
local repo? Something completely different?
-- 
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

Re: packages app

2020-07-27 Thread Miroslav Suchý 
Dne 16. 07. 20 v 21:56 Brendan Early napsal(a):
> and would time out if an external service took too long to respond.

Only if you wanted to list builds, bugs the overview page is more or less 
static (i.e. it is rendered just from
local DB). Fedora-packages-static does not list them at all. This is ok when we 
agree that this is what people find
sufficient.

What I am curious about fedora-packages-static - how long it takes to generate 
all those pages? When I tried to retrieve
initial data fedora-packages-ng, it took several hours. Which may be too much 
for daily job. How much data it consumes?
What is yacysearchserver-pkgs-playground.apps.os.fedorainfracloud.org? Or when 
we delegate search to Google, how long it
takes to refresh the search index? Will be people ok with the speed?

-- 
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

Re: Tech debt analysis tool

2020-07-27 Thread Nasir Hussain 
We've been using SonarCloud at work for quite some time and the experience
is pretty good, +1 for it.

I hope others are better too, Although I haven't tried any of them yet.

Regards,

Nasir Hussain (nasirhm)

On Mon, Jul 27, 2020 at 4:29 PM James Richardson 
wrote:

> Thank you for the replies everyone!
>
> Vipul and I will meet this week to look at the tools suggested in greater
> detail.
>
> Regards,
>
> James
>
> On Tue, Jul 21, 2020 at 9:31 AM Clement Verna 
> wrote:
>
>>
>>
>> On Thu, 16 Jul 2020 at 17:14, Michal Konecny  wrote:
>>
>>> Hi James,
>>>
>>> I'm using the LGTM tool on Anitya and I'm pretty happy with it. It scans
>>> both javascript and python code.
>>>
>>
>>
>> We are also using LGTM on Bodhi and I am also pretty happy with it. It
>> currently runs on every PRs and add some comments about the new "code
>> smells" found in the PR, it is also possible to have a global view of the
>> project https://lgtm.com/projects/g/fedora-infra/bodhi/
>>
>>
>>
>>>
>>> Didn't tried the other two.
>>>
>>> Michal
>>>
>>> On 16/07/2020 15:31, James Richardson wrote:
>>>
>>> Hi All,
>>>
>>> Vipul and I are looking into several different tools that will allow us
>>> to better analyze our tech debt with any new code that is merged into apps
>>> in http://github.com/fedora-infra.
>>>
>>> Currently, we have looked at the tools below, but we would love any and
>>> all input from the team and community on this.
>>>
>>> SonarCloud
>>> LGTM
>>> ShiftLeft
>>>
>>> Our goal is to find an open source tool that is easy to integrate as
>>> well as providing useful and timely feedback.
>>> So far, SonarCloud has proved to be the one that looks best, but again,
>>> we are very open to any and all suggestions, and at this early stage, a
>>> good conversation to arrive at the best solution.
>>>
>>> Regards,
>>>
>>> James
>>>
>>>
>>> --
>>>
>>> James Richardson
>>>
>>> Engineering Intern
>>>
>>> He | Him | His
>>>
>>> Red Hat Waterford 
>>>
>>> Communications House
>>>
>>> Cork Road, Waterford City
>>>
>>> jamri...@redhat.com 
>>> M: +353851970521 <+353877545162> IM: jamricha
>>> @redhatjobs    redhatjobs
>>>  @redhatjobs
>>> 
>>> 
>>>
>>> ___
>>> 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
>>>
>>>
>>> --
>>> Role: Fedora CPE Team - Software Engineer
>>> IRC: mkonecny
>>> FAS: zlopez
>>>
>>> ___
>>> 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
>>
>
>
> --
>
> James Richardson
>
> Engineering Intern
>
> He | Him | His
>
> Red Hat Waterford 
>
> Communications House
>
> Cork Road, Waterford City
>
> jamri...@redhat.com 
> M: +353851970521 <+353877545162> IM: jamricha
> @redhatjobs    redhatjobs
>  @redhatjobs
> 
> 
> ___
> 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:

Re: Tech debt analysis tool

2020-07-27 Thread James Richardson 
Thank you for the replies everyone!

Vipul and I will meet this week to look at the tools suggested in greater
detail.

Regards,

James

On Tue, Jul 21, 2020 at 9:31 AM Clement Verna 
wrote:

>
>
> On Thu, 16 Jul 2020 at 17:14, Michal Konecny  wrote:
>
>> Hi James,
>>
>> I'm using the LGTM tool on Anitya and I'm pretty happy with it. It scans
>> both javascript and python code.
>>
>
>
> We are also using LGTM on Bodhi and I am also pretty happy with it. It
> currently runs on every PRs and add some comments about the new "code
> smells" found in the PR, it is also possible to have a global view of the
> project https://lgtm.com/projects/g/fedora-infra/bodhi/
>
>
>
>>
>> Didn't tried the other two.
>>
>> Michal
>>
>> On 16/07/2020 15:31, James Richardson wrote:
>>
>> Hi All,
>>
>> Vipul and I are looking into several different tools that will allow us
>> to better analyze our tech debt with any new code that is merged into apps
>> in http://github.com/fedora-infra.
>>
>> Currently, we have looked at the tools below, but we would love any and
>> all input from the team and community on this.
>>
>> SonarCloud
>> LGTM
>> ShiftLeft
>>
>> Our goal is to find an open source tool that is easy to integrate as well
>> as providing useful and timely feedback.
>> So far, SonarCloud has proved to be the one that looks best, but again,
>> we are very open to any and all suggestions, and at this early stage, a
>> good conversation to arrive at the best solution.
>>
>> Regards,
>>
>> James
>>
>>
>> --
>>
>> James Richardson
>>
>> Engineering Intern
>>
>> He | Him | His
>>
>> Red Hat Waterford 
>>
>> Communications House
>>
>> Cork Road, Waterford City
>>
>> jamri...@redhat.com 
>> M: +353851970521 <+353877545162> IM: jamricha
>> @redhatjobs    redhatjobs
>>  @redhatjobs
>> 
>> 
>>
>> ___
>> 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
>>
>>
>> --
>> Role: Fedora CPE Team - Software Engineer
>> IRC: mkonecny
>> FAS: zlopez
>>
>> ___
>> 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
>


-- 

James Richardson

Engineering Intern

He | Him | His

Red Hat Waterford 

Communications House

Cork Road, Waterford City

jamri...@redhat.com 
M: +353851970521 <+353877545162> IM: jamricha
@redhatjobs    redhatjobs
 @redhatjobs


___
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