openoss-devel Mailing List for Open Source Operational Support Systems (Page 6)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Related to our platform discussions.

https://github.com/features/projects/wikis

Pierre

Hi,

Thanks for the comments. Will do the changes.

Regrads,
Kumar

On Mon, Oct 1, 2012 at 7:48 PM, Craig Gallen (opennms)
<cg...@op...>wrote:

> Hi,
>
> Just tested work bench installer. Overall it appears to work OK but i
> did find a few problems and changes to address. See below.
>
> Issues and changes found;
> 1. Sample project needs to be replaced with one created using the
> released project creator (i.e.1.1.2 not 1.1.2-SNAPSHOT).  Currently the
> sample project does not build and has Errors such as ReleaseNotes not
> found. This will be fixed with the correct project creator. Get this
> from
>
> https://sourceforge.net/projects/openoss/files/JOSIF/Platform/1.1.2/JOSIF%20Project%20Creator/
>
>
> 2. The tigerstripe-build.properties in the sample project needs to have
> variables which are modified to match the location of the installed
> eclipse and the location of the workspace - both of which can be
> modified during the install process. At a minimum if you can't get the
> installer to change the tigerstripe-build.properties file to match the
> settings, these should match the default locations used by the
> installer. (Currently they are set to D:\\. which is completely wrong)
>
> 3. Both the test dependencies and test model projects have no src
> folder. This causes the project import to fail in eclipse. This is not
> the case with the projects built using the project creator. I suggest
> you delete the current TIP_Test project and use the project creator to
> create a new TIP_Test project in the ws-ts-sample workspace and use this
> in the installer
>
> 4. remove the following files from the top level of the ws-ts-sample
> workspace - they are created by the project Creator but should not be
> included  in the sample project.
> uninstaller (directory)Folding
> .installationinformation
> readme.txt
> ReleaseNotes.txt
>
> 5. in the sample workspace please set the following Preferences as
> defaults ( this matches the Apache best practice); (Also set in default
> workspace if no sample project created)
> Ant>Editor>Folding> UNCHECK 'enable folding'
> Ant>editor>Formatter>indentation Tab size change from 4 to 2 and UNCHECK
> use tab characters instead of spaces. Set maximum line width to 160
> characters
> XML>XML Editor. Set Line width to 160 characters. CHECK indent using
> spaces. Set indentation size to 2
> General>Editors>Text Editors CHECK show line numbers
>
> Other than that, the installer seems to work OK. Well done
>
> Craig
>
>
>
>
>
>
>
>
> On 01/10/2012 13:49, Flauw, Marc wrote:
> > Tina,
> >
> > Kumar has published, through SB,  an installer for team review.
> > I had only time today to validate the generators and SID import have
> same signatures as the ones I am currently using.
> > I would be glad if it can be tested also by others as my availability
> for testing will be limited this week.
> >
> > Best regards
> >
> > Marc
> >
> > -----Original Message-----
> > From: Tina O Sullivan [mailto:tos...@tm...]
> > Sent: Monday, October 01, 2012 2:42 PM
> > To: Craig Gallen (opennms); Flauw, Marc; Pierre Gauthier; SB Mahapatra;
> Manikumar Reddy <ku...@nm...> (ku...@nm...)
> > Subject: RE: Tagging 1.1.2 now complete
> >
> > Is it my understanding that Kumar with assistance from SB and crew will
> start the workbench installer element of this release?
> >
> > If this is correct,  Kumar are you comfortable to proceed?
> >
> > Many thanks,
> > Tina.
> >
> >
> > -----Original Message-----
> > From: Craig Gallen [mailto:gal...@go...] On Behalf Of
> Craig Gallen (opennms)
> > Sent: 30 September 2012 19:48
> > To: openoss-devel; Marc Flauw; Tina O Sullivan; Pierre Gauthier; Craig
> Gallen (OpenNMS)
> > Subject: Tagging 1.1.2 now complete
> >
> > Hi,
> >
> > I have just completed tagging the JOSIF 1.1.2 release and deployed the
> JOSIF  1.1.2 artefacts to maven.
> >
> > These are also available as zip files  in the Sourceforge files release
> system. https://sourceforge.net/projects/openoss/files/JOSIF/
> > All that is needed is for the Workbench installer to be completed for
> the release to be complete.
> >
> > Release Tagging:
> > If you look in the repository, all of Framework and Platform artefacts
> are numbered release 1.1.2 and moved to the RELEASE_1_1_2 tag The RAM, PM
> and MPAC projects have also been tagged as releases at their respective
> point numbers. They use the 1.1.2 Framework and Platform artefacts.
> >
> > Interface Tagging
> > MPAC release 1.0.2 using JOSIF release 1.1.2 can be checked out from
> https://collab.tmforum.org/svn/repos/tip/Features/MaintenanceProtectionAlarmControl/IA/InterfaceModel/tags/RELEASE_1_0_2/
> >
> > PM_Mon release 1.0.0 using JOSIF release 1.1.2 can be checked out from
> https://collab.tmforum.org/svn/repos/tip/Features/PerformanceManagement/IA/InterfaceModel_Collection/tags/RELEASE_1_0_0/TIP_PM_Mon_BaseProject
> >
> > RAM release 1.0.2 using JOSIF release 1.1.2 can be checked out from
> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject
> >
> > Trunk Project Updating:
> > The trunk Framework and Platform artefacts artefacts have all  been
> updated to 1.1.3-SNAPSHOT ready for the next sprint
> >
> > The trunk versions of the RAM, PM and MPAC projects have been updated to
> the next point snapshot. (I will also be updating the test project but some
> work is going on on these projects at present).
> >
> > You should perform a subversion update on the trunk projects in your
> workspace and then do a mvn clean install mvn eclipse:clean mvn
> eclipse:eclipse on each base project  in order to update the dependency
> versions
> >
> > Let me know how you get on
> >
> > Craig
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Openoss-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openoss-devel
>

Hi,

Just tested work bench installer. Overall it appears to work OK but i 
did find a few problems and changes to address. See below.

Issues and changes found;
1. Sample project needs to be replaced with one created using the 
released project creator (i.e.1.1.2 not 1.1.2-SNAPSHOT).  Currently the 
sample project does not build and has Errors such as ReleaseNotes not 
found. This will be fixed with the correct project creator. Get this 
from 
https://sourceforge.net/projects/openoss/files/JOSIF/Platform/1.1.2/JOSIF%20Project%20Creator/ 

2. The tigerstripe-build.properties in the sample project needs to have 
variables which are modified to match the location of the installed 
eclipse and the location of the workspace - both of which can be 
modified during the install process. At a minimum if you can't get the 
installer to change the tigerstripe-build.properties file to match the 
settings, these should match the default locations used by the 
installer. (Currently they are set to D:\\. which is completely wrong)

3. Both the test dependencies and test model projects have no src 
folder. This causes the project import to fail in eclipse. This is not 
the case with the projects built using the project creator. I suggest 
you delete the current TIP_Test project and use the project creator to 
create a new TIP_Test project in the ws-ts-sample workspace and use this 
in the installer

4. remove the following files from the top level of the ws-ts-sample 
workspace - they are created by the project Creator but should not be 
included  in the sample project.
uninstaller (directory)Folding
.installationinformation
readme.txt
ReleaseNotes.txt

5. in the sample workspace please set the following Preferences as 
defaults ( this matches the Apache best practice); (Also set in default 
workspace if no sample project created)
Ant>Editor>Folding> UNCHECK 'enable folding'
Ant>editor>Formatter>indentation Tab size change from 4 to 2 and UNCHECK 
use tab characters instead of spaces. Set maximum line width to 160 
characters
XML>XML Editor. Set Line width to 160 characters. CHECK indent using 
spaces. Set indentation size to 2
General>Editors>Text Editors CHECK show line numbers

Other than that, the installer seems to work OK. Well done

Craig

On 01/10/2012 13:49, Flauw, Marc wrote:
> Tina,
>
> Kumar has published, through SB,  an installer for team review.
> I had only time today to validate the generators and SID import have same signatures as the ones I am currently using.
> I would be glad if it can be tested also by others as my availability for testing will be limited this week.
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Tina O Sullivan [mailto:tos...@tm...]
> Sent: Monday, October 01, 2012 2:42 PM
> To: Craig Gallen (opennms); Flauw, Marc; Pierre Gauthier; SB Mahapatra; Manikumar Reddy <ku...@nm...> (ku...@nm...)
> Subject: RE: Tagging 1.1.2 now complete
>
> Is it my understanding that Kumar with assistance from SB and crew will start the workbench installer element of this release?
>
> If this is correct,  Kumar are you comfortable to proceed?
>
> Many thanks,
> Tina.
>
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
> Sent: 30 September 2012 19:48
> To: openoss-devel; Marc Flauw; Tina O Sullivan; Pierre Gauthier; Craig Gallen (OpenNMS)
> Subject: Tagging 1.1.2 now complete
>
> Hi,
>
> I have just completed tagging the JOSIF 1.1.2 release and deployed the JOSIF  1.1.2 artefacts to maven.
>
> These are also available as zip files  in the Sourceforge files release system. https://sourceforge.net/projects/openoss/files/JOSIF/
> All that is needed is for the Workbench installer to be completed for the release to be complete.
>
> Release Tagging:
> If you look in the repository, all of Framework and Platform artefacts are numbered release 1.1.2 and moved to the RELEASE_1_1_2 tag The RAM, PM and MPAC projects have also been tagged as releases at their respective point numbers. They use the 1.1.2 Framework and Platform artefacts.
>
> Interface Tagging
> MPAC release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/MaintenanceProtectionAlarmControl/IA/InterfaceModel/tags/RELEASE_1_0_2/
>
> PM_Mon release 1.0.0 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/PerformanceManagement/IA/InterfaceModel_Collection/tags/RELEASE_1_0_0/TIP_PM_Mon_BaseProject
>
> RAM release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject
>
> Trunk Project Updating:
> The trunk Framework and Platform artefacts artefacts have all  been updated to 1.1.3-SNAPSHOT ready for the next sprint
>
> The trunk versions of the RAM, PM and MPAC projects have been updated to the next point snapshot. (I will also be updating the test project but some work is going on on these projects at present).
>
> You should perform a subversion update on the trunk projects in your workspace and then do a mvn clean install mvn eclipse:clean mvn eclipse:eclipse on each base project  in order to update the dependency versions
>
> Let me know how you get on
>
> Craig
>
>

Thanks Craig and indeed to the whole team for getting us this far!  The last hurdle ahead. 

Thanks
Tina.

-----Original Message-----
From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
Sent: 30 September 2012 19:48
To: openoss-devel; Marc Flauw; Tina O Sullivan; Pierre Gauthier; Craig Gallen (OpenNMS)
Subject: Tagging 1.1.2 now complete

Hi,

I have just completed tagging the JOSIF 1.1.2 release and deployed the JOSIF  1.1.2 artefacts to maven.

These are also available as zip files  in the Sourceforge files release system. https://sourceforge.net/projects/openoss/files/JOSIF/
All that is needed is for the Workbench installer to be completed for the release to be complete.

Release Tagging:
If you look in the repository, all of Framework and Platform artefacts are numbered release 1.1.2 and moved to the RELEASE_1_1_2 tag The RAM, PM and MPAC projects have also been tagged as releases at their respective point numbers. They use the 1.1.2 Framework and Platform artefacts.

Interface Tagging
MPAC release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/MaintenanceProtectionAlarmControl/IA/InterfaceModel/tags/RELEASE_1_0_2/

PM_Mon release 1.0.0 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/PerformanceManagement/IA/InterfaceModel_Collection/tags/RELEASE_1_0_0/TIP_PM_Mon_BaseProject

RAM release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject

Trunk Project Updating:
The trunk Framework and Platform artefacts artefacts have all  been updated to 1.1.3-SNAPSHOT ready for the next sprint

The trunk versions of the RAM, PM and MPAC projects have been updated to the next point snapshot. (I will also be updating the test project but some work is going on on these projects at present).

You should perform a subversion update on the trunk projects in your workspace and then do a mvn clean install mvn eclipse:clean mvn eclipse:eclipse on each base project  in order to update the dependency versions

Let me know how you get on

Craig

SB,

I checked the RN, the generators and the SID import. Generators (Doc and SOAP) are the same as the ones in my environment, same for SID Import.

I don't really have much more time today to run additional tests, but this seems good.

Best regards

Marc

From: SB Mahapatra [mailto:sbm...@tm...]
Sent: Monday, October 01, 2012 4:57 AM
To: Flauw, Marc
Cc: Manikumar Reddy; ope...@li...
Subject: TIP Workbench Installer

Hi Marc,

Kumar has created the TIP Workbench installer and put in the dropbox. Initial sanity check looks Ok. Please provide your feedback on the installer.

We will have to discuss on the testing process and tools to be used for the same.

Thanks and Regds,
SB

Hi Marc,

Kumar has created the TIP Workbench installer and put in the dropbox. Initial sanity check looks Ok. Please provide your feedback on the installer.

We will have to discuss on the testing process and tools to be used for the same.

Thanks and Regds,
SB

Hi,

I have just completed tagging the JOSIF 1.1.2 release and deployed the 
JOSIF  1.1.2 artefacts to maven.

These are also available as zip files  in the Sourceforge files release 
system. https://sourceforge.net/projects/openoss/files/JOSIF/
All that is needed is for the Workbench installer to be completed for 
the release to be complete.

Release Tagging:
If you look in the repository, all of Framework and Platform artefacts 
are numbered release 1.1.2 and moved to the RELEASE_1_1_2 tag
The RAM, PM and MPAC projects have also been tagged as releases at their 
respective point numbers. They use the 1.1.2 Framework and Platform 
artefacts.

Interface Tagging
MPAC release 1.0.2 using JOSIF release 1.1.2 can be checked out from
https://collab.tmforum.org/svn/repos/tip/Features/MaintenanceProtectionAlarmControl/IA/InterfaceModel/tags/RELEASE_1_0_2/

PM_Mon release 1.0.0 using JOSIF release 1.1.2 can be checked out from
https://collab.tmforum.org/svn/repos/tip/Features/PerformanceManagement/IA/InterfaceModel_Collection/tags/RELEASE_1_0_0/TIP_PM_Mon_BaseProject

RAM release 1.0.2 using JOSIF release 1.1.2 can be checked out from
https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject

Trunk Project Updating:
The trunk Framework and Platform artefacts artefacts have all  been 
updated to 1.1.3-SNAPSHOT ready for the next sprint

The trunk versions of the RAM, PM and MPAC projects have been updated to 
the next point snapshot. (I will also be updating the test project but 
some work is going on on these projects at present).

You should perform a subversion update on the trunk projects in your 
workspace and then do a
mvn clean install
mvn eclipse:clean
mvn eclipse:eclipse
on each base project  in order to update the dependency versions

Let me know how you get on

Craig

I can certainly add it to next week’s agenda as it falls in  nicely to our discussion on organising for FX13 and re-charter of the project.   HOWEVER  I do not want the team to forget we still have to deliver R1.1.2 and we will be discussing that as well. Hopefully it will be a matter of final tidy-up before submitting for inclusion into FX12.5

Many thanks,
Tina.

From: Joann O'Brien [mailto:jo...@tm...]
Sent: 27 September 2012 22:36
To: S Fratini; Craig Gallen (opennms)
Cc: openoss-devel; Marc Flauw; Kenneth Dilbeck
Subject: Re: [Openoss-devel] SOAP Gen status

Hi all,
Can we have a discussion on this next week?

I can join the SII team on Wednesday at 2pm.  I have some thoughts regarding how we could reposition the tooling and thereby strengthen the value proposition and improve the support the team gets.   In general this is in the area of formally broadening the scope to include demonstration of relevance to expedited interfaces, network api’s, auto generated B2B exchanges in a multi-vendor, complex value chain scenario, etc.
These may be a stretch too far, but it’s worth discussing to consider the possibilities.

Let me know if this time suits you guys,
Thanks
Joann

From: S Fratini [mailto:sfr...@gm...]<mailto:[mailto:sfr...@gm...]>
Sent: 27 September 2012 19:26
To: Craig Gallen (opennms)
Cc: Marc Flauw; openoss-devel; Joann O'Brien; Kenneth Dilbeck
Subject: Re: [Openoss-devel] SOAP Gen status

Craig

Do you have any thoughts as to the business case for a TM Forum member company to provide resources to help with the maintenance of JOSIF?

The only reason I can imagine is that a company plans to use JOSIF and/or its output with a very high priority and thus wants to make sure the software is well maintained.

Maybe another approach is to have a membership fee for this project (or supply people resources) - doesn't sound so good but I state it anyway.

Is it a matter of a TM Forum member company hiring you (Craig) part-time to do more work on this?

On Thu, Sep 27, 2012 at 1:57 AM, Craig Gallen (opennms) <cg...@op...<mailto:cg...@op...>> wrote:
Hi Pierre,

Status: SoapImpl, EJBImpl, JVTSpec generators now generating code which compiles for PM, MPAC and RAM agaist the XML generated by the SOAP generator. All ready to package. I will be tagging 1.1.2 and moving to trunk to 1.1.3-SNAPSHOT this week.

I appreciate and share your concerns. Unfortunately all of the problems you mention are well understood. We just don't have the resources with the dedicated time and skills to deal with them. Most of the recent problems we have had have been because nobody was checking the generated XML until I tried to get the implementation code to work. I'm surprised the PM Catalyst folks hadn't noticed the problems with the generated SOAP long before now. This perhaps is a very strong proof of the value of working on RI CTK implementations at the same time as creating the spec.

Personally my biggest problem is that I am not able to put nearly as much time into the work as I did when I was working full time on it during the first two years. If we could find a sponsor, I could put in more effort.

I will be at management world Orlando. It would be great if we could use the opportunity to do a face to face review of where we are and also go through the inventory code. I know you will be teaching some of the time but I will be there from Sunday through Friday morning.

Apart from a technical review, I would also like to talk through what is realistically required to make a sustainable tool chain. Tina and Ken and Joan may also want to join us for some of this. So far we have tried to do this without a realistic appreciation of the costs which have mostly been hidden. There are real costs of sustaining a project which mostly OpenNMS have  funded to get things started (my time and efforts).

I understand the TM Forum paying for you to do  work but I think that is very much future development work and bringing on new participants. It's not the same as the basic job of infrastructure and release management.  Last year the TM Forum did stump up some cash for me to help write marketing collateral and spend the Christmas holidays tagging a release.  Perhaps this is something we could look at on a more sustained basis.

cheers,
Craig

On 27/09/2012 06:13, Flauw, Marc wrote:
Pierre,

I am sorry you were not able to attend the status meeting yesterday. Yes, Xose fixed it on Monday and I confirmed on Tuesday.

Best regards

Marc

From: Pierre Gauthier [mailto:pga...@tm...]
Sent: Wednesday, September 26, 2012 10:49 PM
To: Flauw, Marc; Craig Gallen (opennms)
Cc: Xose Ramon Sousa Vazquez (xr...@op...<mailto:xr...@op...>); Tina O Sullivan; SB Mahapatra
Subject: Re: SOAP Gen status

Hi All,

Have we fixed the issue with the associations in the dependent model.

We should really think about building a regression test suite to handle these
core infrastructural requirements.

We can't wait at the last moment like we do now to figure out so fundamental problems.

This applies to the RI/CTK generation code which has a large number of issues (i.e String Array, Class Name clashes etc...)

Pierre
On Sep 26, 2012, at 3:28 AM, "Flauw, Marc" <Mar...@hp...<mailto:Mar...@hp...>> wrote:

Hi Xose,

Just checking with you.
Did you made any further update to the SOAP Generator since the version I tested yesterday?

Also, did your update the  TIP_SOAP_Generator_Package project with latest jar ?

Best regards

Marc

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Openoss-devel mailing list
Ope...@li...<mailto:Ope...@li...>
https://lists.sourceforge.net/lists/listinfo/openoss-devel

--
Steve

Joann,

It will be at the next SII call.

Best regards

Marc

From: Joann O'Brien [mailto:jo...@tm...]
Sent: Thursday, September 27, 2012 11:36 PM
To: S Fratini; Craig Gallen (opennms)
Cc: Flauw, Marc; openoss-devel; Kenneth Dilbeck
Subject: RE: [Openoss-devel] SOAP Gen status

Hi all,
Can we have a discussion on this next week?

I can join the SII team on Wednesday at 2pm.  I have some thoughts regarding how we could reposition the tooling and thereby strengthen the value proposition and improve the support the team gets.   In general this is in the area of formally broadening the scope to include demonstration of relevance to expedited interfaces, network api’s, auto generated B2B exchanges in a multi-vendor, complex value chain scenario, etc.
These may be a stretch too far, but it’s worth discussing to consider the possibilities.

Let me know if this time suits you guys,
Thanks
Joann

From: S Fratini [mailto:sfr...@gm...]<mailto:[mailto:sfr...@gm...]>
Sent: 27 September 2012 19:26
To: Craig Gallen (opennms)
Cc: Marc Flauw; openoss-devel; Joann O'Brien; Kenneth Dilbeck
Subject: Re: [Openoss-devel] SOAP Gen status

Craig