perfsonar development work

["Matthias K. Hamm" <>]

Hi Jeff,

from our point of view, CircuitMon doesn`t fit quite well, since we do 
not show real monitoring data for Circuits. E2ELinks are an abstraction.

[And most people already know this service under the name E2E* ;-) ]

Cheers,

M&M

Jeff W. Boote schrieb:
> Michael Enrico wrote:
> > three suggestions spring to mind:
> >
> > CircuitMon
> > ConnectionMon
> > or
> > E2ELinkMon
>
> I'm sitting in an airport here wasting time with Matt Z... Not that we 
> have any voice in this at all (or even care that much). But, since we 
> are wasting time. We both liked CircuitMon. :) I can even envision a 
> mascot stick-figure man drawn out of circuit diagrams...
>
> jeff
>
> > Nicolas Simar wrote:
> > > Any thoughts or suggestion there?
> > >
> > > Nicolas
> > >
> > > Michael Enrico wrote:
> > > > I'm quite happy for us to do some renaming if it removes ambiguity -
> > > > E2Emon is really just a working title at the end of the day.
> > > >
> > > > Mark Yampolskiy wrote:
> > > >
> > > > > Hi Nicolas, all,
> > > > >
> > > > > Nicolas Simar schrieb:
> > > > >
> > > > > > Loukik Kudarimoti wrote:
> > > > > >
> > > > > > > Matthias K. Hamm wrote:
> > > > > > >
> > > > > > >
> > > > > > > > Hi Loukik, Nicolas,
> > > > > > > >
> > > > > > > > is it OK that we use E2Emon as the unique service name for our
> > > > > > > > "JRA4 MP" throughout the perfSONAR release documents?
> > > > > > I think that E2Emon is a bit confusing. All the network services are
> > > > > > end-to-end (or at least edge to edge).
> > > > > > How to name it? Like the others, based on the technology used to
> > > > > > store the data (e.g. XML file MP)?
> > > > > >
> > > > > > But  the service is possibly specialise for circuit information.
> > > > > > (Status for now, and possibly performances at a later stage).
> > > > > > So should we rather highlight what it provides: Circuit 
> > > > > > Monitoring MP?
> > > > > >
> > > > > > But then for a user, it would hide the fact that you could get the
> > > > > > data from another web-service (the SQL MA).
> > > > > >
> > > > > > Hmmm. Difficult question to answer. Any thoughts? (unless it is too
> > > > > > late to change the name).
> > > > > hehe. true - naming is one of the hardest things in life :)
> > > > > what do you think about "E2Emon MP" ? or - similar to SQL MA - "XML
> > > > > MP" ?
> > > > >
> > > > > E2Emon has been established as the name for the _whole_ package
> > > > > developed in JRA4/WI3 - "E2Emon Correlation Tool" (central component
> > > > > with UI) and "E2Emon MP" (at least we call it so internal ;-))
> > > > >
> > > > > Cheers,
> > > > > M&M
> > > > >
> > > > >
> > > > > > Nicolas
> > > > > >
> > > > > >
> > > > > > > It sounds OK to me although I have a question: what exactly is
> > > > > > > E2EMon? Is it your Web Service software only? Is it the name of 
> > > > > > > your
> > > > > > > project which produces Web Service software & analysis tool?
> > > > > > >
> > > > > > >
> > > > > > > > BTW: What is the unique service name for the SQL MA, which acts as
> > > > > > > > MA for E2EMon?
> > > > > > >
> > > > > > > The unique service name is SQL MA (also called SQL Type MA). This
> > > > > > > SQL MA is currently capable of providing access to Utilization data
> > > > > > > as well as status of lightpaths. The deployer can configure it 
> > > > > > > based
> > > > > > > on the metric that he/she wishes to export.
> > > > > > >
> > > > > > > I reckon the name will remain the same in future but the SQL MA 
> > > > > > > will
> > > > > > > be enhanced in future to provide access to more metrics.
> > > > > > >
> > > > > > > Also, I am a bit confused about the phrase 'acts as MA for E2EMon'.
> > > > > > > Maybe because I don't understand what is E2EMon composed of? For 
> > > > > > > us,
> > > > > > > our SQL MA is a measurement archive that can be accessed by any
> > > > > > > client. One such client is the JRA4 analysis tool.
> > > > > > >
> > > > > > > Loukik.
> > > > > > >
> > > > > > >
> > > > > > > > Cheers,
> > > > > > > >
> > > > > > > > M&M
> > > > > > > >
> > > > > > > > Loukik Kudarimoti schrieb:
> > > > > > > >
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > The template for functional specification, which was not attached
> > > > > > > > > in the original email is now attached in this email. It is also
> > > > > > > > > available via the URL present in the Hand over document.
> > > > > > > > >
> > > > > > > > > Loukik.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Loukik Kudarimoti wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > A .pdf document explaining the hand over process for perfSONAR
> > > > > > > > > > 1.1 release is in attachment. The process defined in this
> > > > > > > > > > document will be used for the upcoming pS 1.1 bundle release.
> > > > > > > > > >
> > > > > > > > > > Developers, please note: If your service is shortlisted  to be
> > > > > > > > > > included in the upcoming release, please read this document and
> > > > > > > > > > if you have any questions please raise them during the release
> > > > > > > > > > management conf. calls which are held weekly (the next one is on
> > > > > > > > > > 5th of December 2006). More information (list of services
> > > > > > > > > > included, due dates, etc..) are available here:
> > > > > > > > > > http://wiki.perfsonar.net/jra1-wiki/index.php/Release_Management-perfSONAR-1.1 
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Templates for documents:
> > > > > > > > > > The Hand over process requires some documents to be provided
> > > > > > > > > > along with software and installation scripts. The hand over
> > > > > > > > > > process document gives you a list of necessary documents. URLs
> > > > > > > > > > for these templates are in the annex. They are also attached in
> > > > > > > > > > this email.
> > > > > > > > > >
> > > > > > > > > > Sample documents:
> > > > > > > > > > The intention behind these samples is to be able to help you in
> > > > > > > > > > using the templates easily and effectively. We do not have
> > > > > > > > > > samples for all the document yet. We hope to have these ready
> > > > > > > > > > soon. The sample document for specfication of rrd ma
> > > > > > > > > > configuration file is in attachment.
> > > > > > > > > >
> > > > > > > > > > If you have any questions, please feel free to ask us at any 
> > > > > > > > > > time.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > The Release Management team


--

Matthias Hamm

------------------------------------------------
Leibniz-Rechenzentrum / Leibniz Computing Centre
Raum I.2.107
Boltzmannstrasse 1, 85748 Garching, Germany
Telefon: +49 89 35831-8832
Fax:     +49 89 35831-9700
E-Mail:  

-------------------------------------------------