Hi all,
As per our policies: https://wiki.centos.org/SpecialInterestGroup
All code produced within the SIG must be compatible with a FOSS license presently used by CentOS; if a new license is wanted, again, please consult with the Devteam member
I think that it would be valuable that the SIG in charge of the infra releases the source code of Duffy. It works really well and might be used by other people.
I did not find the source code anywhere, sorry if I missed it.
Thanks,
On Nov 29, 2016 3:49 PM, "Julien Pivotto" roidelapluie@inuits.eu wrote:
Hi all,
As per our policies: https://wiki.centos.org/SpecialInterestGroup
All code produced within the SIG must be compatible with a FOSS license presently used by CentOS; if a new license is wanted, again, please consult with the Devteam member
I think that it would be valuable that the SIG in charge of the infra releases the source code of Duffy. It works really well and might be used by other people.
I did not find the source code anywhere, sorry if I missed it.
+1
-- rtnpro
On 29/11/16 10:19, Julien Pivotto wrote:
Hi all,
As per our policies: https://wiki.centos.org/SpecialInterestGroup
All code produced within the SIG must be compatible with a FOSS license presently used by CentOS; if a new license is wanted, again, please consult with the Devteam member
I think that it would be valuable that the SIG in charge of the infra releases the source code of Duffy. It works really well and might be used by other people.
I did not find the source code anywhere, sorry if I missed it.
I dont want to take too much away from Brians announcement in a few months - but the intention is to take where we are, rebase on lessons learnt and propose a duffy2 that is build and executed publicly with a wider potential than just ci.centos.org.
otherwise the only people who can use the present setup are people who still have seamicro hardware, being used for CentOS CI ( and AMD stopped selling seamicro a while back ).
regards,
On Nov 29 13:48, Karanbir Singh wrote:
On 29/11/16 10:19, Julien Pivotto wrote:
Hi all,
As per our policies: https://wiki.centos.org/SpecialInterestGroup
All code produced within the SIG must be compatible with a FOSS license presently used by CentOS; if a new license is wanted, again, please consult with the Devteam member
I think that it would be valuable that the SIG in charge of the infra releases the source code of Duffy. It works really well and might be used by other people.
I did not find the source code anywhere, sorry if I missed it.
I dont want to take too much away from Brians announcement in a few months - but the intention is to take where we are, rebase on lessons learnt and propose a duffy2 that is build and executed publicly with a wider potential than just ci.centos.org.
otherwise the only people who can use the present setup are people who still have seamicro hardware, being used for CentOS CI ( and AMD stopped selling seamicro a while back ).
regards,
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
+1 here.
For now, especially for new projects, it's important to focus as much energy as possible on the test cases and the software under test. A rich set of tests is going to be our biggest asset when we look down the road to realizing more cross-project validation.
Cheers!
--Brian
On 29 Nov 09:52, Brian Stinson wrote:
+1 here.
For now, especially for new projects, it's important to focus as much energy as possible on the test cases and the software under test. A rich set of tests is going to be our biggest asset when we look down the road to realizing more cross-project validation.
Cheers!
--Brian
Well, I do think that the code is relevant for every user. I would have liked to understand a bit better how we provision upfront, how we do the garbage collection, at which point are the nodes killed... With more details than what is available in the wiki.
On 30/11/16 04:55, Julien Pivotto wrote:
Well, I do think that the code is relevant for every user. I would have liked to understand a bit better how we provision upfront, how we do the garbage collection, at which point are the nodes killed... With more details than what is available in the wiki.
the user handoff happens at the point where the duffy call is made, and then again the collection happens when the done call is made, or there is a timeout on the allocation.
What specific details are you looking for beyond this ? and how would it impact your test workers and your use of these nodes ?
Regards
On 05 Dec 11:49, Karanbir Singh wrote:
On 30/11/16 04:55, Julien Pivotto wrote:
Well, I do think that the code is relevant for every user. I would have liked to understand a bit better how we provision upfront, how we do the garbage collection, at which point are the nodes killed... With more details than what is available in the wiki.
the user handoff happens at the point where the duffy call is made, and then again the collection happens when the done call is made, or there is a timeout on the allocation.
What specific details are you looking for beyond this ? and how would it impact your test workers and your use of these nodes ?
I was mainly wondering what happens if I do not release a node. The wiki page is not clear if a garbage collector is actually implemented. I wanted to know if it would have been useful that I create a jenkinsjob running daily that would kill my unreleased nodes.
Regards
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Brian Stinson -
Julien Pivotto -
Karanbir Singh -
Ratnadeep Debnath