Re: [Nfs-ganesha-devel] Proposal: new scripts repo

2017-11-27 Thread Daniel Gryniewicz

On 11/22/2017 08:04 AM, LUCAS Patrice wrote:

On 11/21/17 15:20, Daniel Gryniewicz wrote:

Hi, All.

I would like to propose a new repo on our github for helpful scripts. 
I'd like to have testing/performance scripts there, as a start, but 
maybe other useful things can go there too in the future.


The idea is that this would be a place to share things like setups for 
running dbench/iozone/etc., so that when issues arise, we can point to 
the script that triggers the issue.


My proposal is that the scripts would have a standard header at the 
top, that describes what needs to be installed, how many machines are 
necessary, and how they are connected on networks, and so on, so that 
someone could pick up a script and, with minimal interaction with 
anyone else, be able to run it.


What do people think about this?  Should we discuss it on the next call?

Daniel

-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel



Hi Daniel,

We already have a ganesah github repo dedicated to Continuous 
Integration Tests : https://github.com/nfs-ganesha/ci-tests . Why not 
adding your scripts to this repo instead of creating a new one ?


Best regards,




I thought of that, but that is specifically scripts run by CI, and this 
is intended to be scripts run by hand. I don't have a strong opinion, 
but I feel that ci-tests should be focused on CI.


Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


Re: [Nfs-ganesha-devel] Proposal: new scripts repo

2017-11-22 Thread LUCAS Patrice

On 11/21/17 15:20, Daniel Gryniewicz wrote:

Hi, All.

I would like to propose a new repo on our github for helpful scripts. 
I'd like to have testing/performance scripts there, as a start, but 
maybe other useful things can go there too in the future.


The idea is that this would be a place to share things like setups for 
running dbench/iozone/etc., so that when issues arise, we can point to 
the script that triggers the issue.


My proposal is that the scripts would have a standard header at the 
top, that describes what needs to be installed, how many machines are 
necessary, and how they are connected on networks, and so on, so that 
someone could pick up a script and, with minimal interaction with 
anyone else, be able to run it.


What do people think about this?  Should we discuss it on the next call?

Daniel

-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel



Hi Daniel,

We already have a ganesah github repo dedicated to Continuous 
Integration Tests : https://github.com/nfs-ganesha/ci-tests . Why not 
adding your scripts to this repo instead of creating a new one ?


Best regards,

--
Patrice LUCAS
Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S
tel : +33 (0)1 69 26 47 86
e-mail : patrice.lu...@cea.fr


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


[Nfs-ganesha-devel] Proposal: new scripts repo

2017-11-21 Thread Daniel Gryniewicz

Hi, All.

I would like to propose a new repo on our github for helpful scripts. 
I'd like to have testing/performance scripts there, as a start, but 
maybe other useful things can go there too in the future.


The idea is that this would be a place to share things like setups for 
running dbench/iozone/etc., so that when issues arise, we can point to 
the script that triggers the issue.


My proposal is that the scripts would have a standard header at the top, 
that describes what needs to be installed, how many machines are 
necessary, and how they are connected on networks, and so on, so that 
someone could pick up a script and, with minimal interaction with anyone 
else, be able to run it.


What do people think about this?  Should we discuss it on the next call?

Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel