Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: gatech experiences - internal discussion

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: gatech experiences - internal discussion


Chronological Thread 
  • From: "Jeff W. Boote" <>
  • To: Loukik Kudarimoti <>
  • Cc: ,
  • Subject: Re: [pS-dev] Re: gatech experiences - internal discussion
  • Date: Fri, 18 Aug 2006 11:13:02 -0600

Loukik Kudarimoti wrote:
Hi Jeff,

<snip>

I am more convinced than before that perl scripts calling on ant is the best way forward.


Summary:

It probably is the best way for a post-install configuration script to be written. It is absolutely NOT the best way to track dependencies and updates of packages.

So, we agree that perl scripts calling on ant targets is the best way for post-install configuration. I haven't heard anybody else disagreeing. So, if you can acknowledge this point, I will add a feature request in bugzilla for this and we drop in from our future discussions.

Yes - I agree.

These are two different topics. It confuses the issue to combine them. In my opinion both of these statements are true:

1) For long-term viability of pS, it will be necessary for pS services to be installable via the normal package management solutions available on each OS. This will allow upgrades and dependency checking to happen in ways consistent with the expectations of system administrators at NOC's.

This is fine for me. It is just one more way of downloading and installing perfSONAR.

A tar ball will still have to be made available on our webpage. So, I would like to focus on the installation of that particular tar ball (and all the dependent software) - I will start a new email thread for that if needed.

I agree with everything except the parenthetical: "(and all the dependent software)".

That is specifically the part we should stay away from.

2) For pS usability, it is necessary to provide configuration applications to help the end-user configure (and test) the installed services.

Absolutely. I believe for configuration and testing, as I mentioned above, we both agree that perl calling on ant targets is the best way forward.

Yes.

It appears we have much to agree upon. Perhaps we can concentrate the work there first and worry about the rest if needed later?

To make our code available via the package management route, we will need to ensure the prerequisites are available that way as well. If that works well, our area of disagreement may become irrelevant.

jeff



Archive powered by MHonArc 2.6.16.

Top of Page