Re: The future of loopabull

2020-05-29 Thread Clement Verna
On Thu, 28 May 2020 at 14:27, Pierre-Yves Chibon 
wrote:

> Good Morning Everyone,
>
> I know this question has already been raised a few times, but I think we
> should
> raise it once more: what do we see as future for loopabull?
>
> It is currently triggered on 4 topics (3 from prod and 1 from stg) to do
> basically
> three actions:
> - Flag commit successfully built in koji, in other words it adds these
> flags
>   to dist-git:
>
> https://src.fedoraproject.org/rpms/mingw-filesystem/c/717f2a929bd25b62a0427e8e5c3792a0939dbfce
> - Flag when the Fedora CI start testing a PR
> - Flag when the Fedora CI finished testing a PR (and thus reports
> Pass/Fail)
>
> Upstream released yesterday a 0.0.7 release which brings supports for
> fedora-messaging (contributed by your servitor).
> Looking at the code, it should be python3 compatible, but it doesn't say
> specifically in the setup.py and I honestly don't remember if I've tested
> that
> or not.
> The package has been orphaned in Fedora for over 10 months and has thus
> been
> retired.
>
> I've had a chat with upstream yesterday and they are still interested in
> the
> project but more as a pet project and their time is just like the rest of
> us,
> limited for pet projects these days.
> That being said the code base is really quite small and involves
> technologies
> we're already using in other places (python-pika, celery, rabbitmq,
> ansible...)
> so there isn't really anything new there.
>
> One of its limitation currently is with secrets, how to pass/specify them.
> This is something we could circumvent via ansible-vault or so, but it
> needs a
> little investigation.
>
> I basically see three ways forward with this:
> - We continue with loopabull and we need to check its python3 support, how
> to
>   deal with secrets, if we can get it to run in openshift & so on.
> - We look for something else, similar. The requirements being:
>   - Run a task when seeing a message in our message bus
>   - Handle secrets
>   - Scalable up/down
>   - Runnable in openshift is a bonus
>   - Preferably in a language we can debug (python++, potentially rust)
> - We write something that fits our needs and requirements
>

There is a PR[0] in fedora-messaging to add a 'run' callback that would let
you execute any command, I think that might be a nice solution and I think
it would meet most of the requirements.

[0] - https://github.com/fedora-infra/fedora-messaging/pull/163

>
>
> Would you know something that fits our requirements and that we could just
> run?
> If not, do you have a preferred way between options #1 and #3?
>
>
> Thanks for your thoughts,
>
> Pierre
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: Please help me receive necessary rights to manage resources in AWS

2020-05-29 Thread Andrei Stepanov
Kevin hello,

I should have explained this before. Sorry.
Testing-Farm team and osci are from the same initiative.
However, there is a distinction:
1. Testing-farm: runs actual test, and provides API for scheduling a test.
Testing-farm does not:  interpreters results, monitors new builds, etc. 
Testing-farm runs tests when they asked for.
2. osci part : is monitor and trigger/schedule test for testing-farm.
Currently we have a few OpenShift projects at console.apps.ci.centos.org. That 
is very outdated OpenShift version. 
If possible we would like to host Jenkinses both on os.fedoraproject.org  as 
well as on AWS.
I will be happy to answer other questions if there are.
We do not have strict deadlines, however this would help us move.
Please let me know if there are more questions or how we can proceed further.
Thank you.
___
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