openspp-project Mailing List for OpenSPP (Page 3)
Status: Planning
Brought to you by:
deanwillis
Menu
▾
▴
openspp-project — Participants in the OpenSPP Project, including Development Team,Owner, etc.
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(39) |
Jul
(3) |
Aug
(23) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dean W. <dea...@so...> - 2011-06-04 00:32:40
|
For at least the Sprint 1 phase, I believe the tech team is proposing the following components: Commercial: 1) Java 1.6 2) JEE 5 Open Source: 1) Apache CXF 2.4.0 2) Spring Framework 3.1 3) Apache Tomcat 7.0.x 4) MySQL 5.5.13 community edition 5) Apache Log4J 1.2 6) Apache Ant 1.8.2 7) Maven 3.0.3 More details and links to the relevant OSS work are on our Wiki: https://sourceforge.net/apps/mediawiki/openspp/index.php?title=OpenSPP_Server_Simulator_Architecture I believe the project terms require having any OSS approved by CableLab's legal team, so we'll need to get some approvals ASAP. Also, a we start writing code, we need to start putting licensing terms into it. I asked Legal to bless the Apache 2.0 license earlier in the week, and have not seen a response yet. We need to get that squared away before any code hits SourceForge. -- Dean |
|
From: Dean W. <dea...@so...> - 2011-06-04 00:25:50
|
In the interest of getting started ASAP, I've put together a first approximation of a sprint backlog for a first sprint, which I hope we can get going on "right away". There are a couple of process impediments, and I'll send a note out on those under separate cover. See: https://sourceforge.net/apps/mediawiki/openspp/index.php?title=Sprint_1 -- Dean |
|
From: David S. <dsc...@xc...> - 2011-06-02 18:48:35
|
Hi Syed I am fine with REST. :D On Jun 2, 2011, at 8:14 PM, Ali, Syed Wasim wrote: > > Will there be interest in using REST based query engine to fulfill the > role of a "resolver" to test the provisioned data. This method fulfills > the requirement of a "resolver" and it will be faster to implement and > write tests. In fact, the schema can accommodate the querying "rant" > identifier within the request to enable the same end-point to buzz through > a number of use cases without requiring complex authentication > requirements. I can certainly lend a hand putting this together, if that > helps. > > > -Syed > > > On 6/2/11 12:36 PM, "Dean Willis" <dea...@so...> wrote: > >> >> We understand that the stakeholders really want to see OpenSPP resolve >> ENUM queries, as that's the proof that the data model in SPPP works for >> the target audience. >> >> However, ENUM and SPPP are completely different protocols. And ENUM >> implementations, especially performant ones, are very tricky. The use of >> ENUM also raises questions, such as how to test SPPP's requestor-specific >> response capability, when ENUM has no standard way of differentiating >> requestors? >> >> The design team came up with a couple of approaches. >> >> 1) Build ENUM service directly into the OpenSPP server, and build an ENUM >> client using the JavaDNS library for testing. >> >> 2) Build an ENUM server that interacts at the database or Data Access >> Objects layer with the data store behind OpenSPP, and a testing client. >> >> 3) Build an ENUM server that uses the standard SPPP SOAP API to talk to >> OpenSPP, and a testing client. >> >> 4) Build an ENUM-specific web service API into OpenSPPP; such an API >> would have the expressibility of ENUM without the baggage of theDNS >> protocol, and would be a useful interface for adding an ENUM service to >> OpenSPP. This API could be tested/demonstrated using something like >> SoapUI (http://www.soapui.org), reducing the coding effort needed for a >> client in the near term. >> >> I believe the design team favored the last approach given our short >> design/delivery cycle and the available resources. >> >> We could certainly add full ENUM into the mix in a future release, but >> don't think we're going to accomplish it in the next month. >> >> How does this sound? >> >> We're probably going to need help designing the ENUM-specific SOAP API. >> Perhaps a restricted set of functionality would be adequate initially? >> >> -- >> Dean >> >> >> -------------------------------------------------------------------------- >> ---- >> Simplify data backup and recovery for your virtual environment with >> vRanger. >> Installation's a snap, and flexible recovery options mean your data is >> safe, >> secure and there when you need it. Discover what all the cheering's about. >> Get your free trial download today. >> http://p.sf.net/sfu/quest-dev2dev2 >> _______________________________________________ >> OpenSPP-project mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openspp-project > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > OpenSPP-project mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openspp-project |
|
From: Dean W. <dea...@so...> - 2011-06-02 17:51:41
|
See: https://sourceforge.net/apps/mediawiki/openspp/index.php?title=OpenSPP_Server_Simulator_Architecture Jeremy is revising the diagram slightly. We also need to flesh-out the component list a bit more. -- Dean |
|
From: Ali, S. W. <sye...@ne...> - 2011-06-02 17:29:23
|
Will there be interest in using REST based query engine to fulfill the role of a "resolver" to test the provisioned data. This method fulfills the requirement of a "resolver" and it will be faster to implement and write tests. In fact, the schema can accommodate the querying "rant" identifier within the request to enable the same end-point to buzz through a number of use cases without requiring complex authentication requirements. I can certainly lend a hand putting this together, if that helps. -Syed On 6/2/11 12:36 PM, "Dean Willis" <dea...@so...> wrote: > >We understand that the stakeholders really want to see OpenSPP resolve >ENUM queries, as that's the proof that the data model in SPPP works for >the target audience. > >However, ENUM and SPPP are completely different protocols. And ENUM >implementations, especially performant ones, are very tricky. The use of >ENUM also raises questions, such as how to test SPPP's requestor-specific >response capability, when ENUM has no standard way of differentiating >requestors? > >The design team came up with a couple of approaches. > >1) Build ENUM service directly into the OpenSPP server, and build an ENUM >client using the JavaDNS library for testing. > >2) Build an ENUM server that interacts at the database or Data Access >Objects layer with the data store behind OpenSPP, and a testing client. > >3) Build an ENUM server that uses the standard SPPP SOAP API to talk to >OpenSPP, and a testing client. > >4) Build an ENUM-specific web service API into OpenSPPP; such an API >would have the expressibility of ENUM without the baggage of theDNS >protocol, and would be a useful interface for adding an ENUM service to >OpenSPP. This API could be tested/demonstrated using something like >SoapUI (http://www.soapui.org), reducing the coding effort needed for a >client in the near term. > >I believe the design team favored the last approach given our short >design/delivery cycle and the available resources. > >We could certainly add full ENUM into the mix in a future release, but >don't think we're going to accomplish it in the next month. > >How does this sound? > >We're probably going to need help designing the ENUM-specific SOAP API. >Perhaps a restricted set of functionality would be adequate initially? > >-- >Dean > > >-------------------------------------------------------------------------- >---- >Simplify data backup and recovery for your virtual environment with >vRanger. >Installation's a snap, and flexible recovery options mean your data is >safe, >secure and there when you need it. Discover what all the cheering's about. >Get your free trial download today. >http://p.sf.net/sfu/quest-dev2dev2 >_______________________________________________ >OpenSPP-project mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/openspp-project |
|
From: Dean W. <dea...@so...> - 2011-06-02 17:04:27
|
We understand that the stakeholders really want to see OpenSPP resolve ENUM queries, as that's the proof that the data model in SPPP works for the target audience. However, ENUM and SPPP are completely different protocols. And ENUM implementations, especially performant ones, are very tricky. The use of ENUM also raises questions, such as how to test SPPP's requestor-specific response capability, when ENUM has no standard way of differentiating requestors? The design team came up with a couple of approaches. 1) Build ENUM service directly into the OpenSPP server, and build an ENUM client using the JavaDNS library for testing. 2) Build an ENUM server that interacts at the database or Data Access Objects layer with the data store behind OpenSPP, and a testing client. 3) Build an ENUM server that uses the standard SPPP SOAP API to talk to OpenSPP, and a testing client. 4) Build an ENUM-specific web service API into OpenSPPP; such an API would have the expressibility of ENUM without the baggage of theDNS protocol, and would be a useful interface for adding an ENUM service to OpenSPP. This API could be tested/demonstrated using something like SoapUI (http://www.soapui.org), reducing the coding effort needed for a client in the near term. I believe the design team favored the last approach given our short design/delivery cycle and the available resources. We could certainly add full ENUM into the mix in a future release, but don't think we're going to accomplish it in the next month. How does this sound? We're probably going to need help designing the ENUM-specific SOAP API. Perhaps a restricted set of functionality would be adequate initially? -- Dean |
|
From: Jeremy B. \(Digitalshtick\) <je...@di...> - 2011-06-02 12:59:16
|
I've attached a diagram I've been kicking around - keeping Vijay's design and input from David in mind An agenda item for our call - how should we converge on the architecture - especially the components needed to implement the architectural requirements and user stories in the backlog ? Regards Jeremy Jeremy Barkan CTO Digitalshtick Tel: +972 2 6728069 Mobile: +972 54 6321603 Skype: jeremy_barkan www.digitalshtick.com -----Original Message----- From: Jeremy Barkan (Digitalshtick) [mailto:je...@di...] Sent: 30 May 2011 22:39 To: 'joshi vijay kumar' Cc: 'David Schwartz'; 'Jean-Francois Mule'; 'Dean Willis' Subject: RE: OpenSPP Architecture Thoughts Hi Vijay, Here are some thoughts I put into a ppt - hope they captured my thinking after reading through the SPPP draft again and that they are useful. Regards Jeremy Jeremy Barkan CTO Digitalshtick Tel: +972 2 6728069 Mobile: +972 54 6321603 Skype: jeremy_barkan www.digitalshtick.com -----Original Message----- From: joshi vijay kumar [mailto:vij...@ya...] Sent: 28 May 2011 13:32 To: Jean-Francois Mule; Dean Willis; Jeremy Barkan Cc: Mickael MARRACHE; Samuel Melloul; David Schwartz Subject: Re: Access to existing SPPP codebase Sure, I will send a document for our discussion. Thanks Vijay ----- Original Message ---- From: Jean-Francois Mule <jf...@ca...> To: Dean Willis <dea...@so...>; Jeremy Barkan <je...@di...>; Vijay Joshi <vij...@ya...> Cc: Mickael MARRACHE <mic...@gm...>; Samuel Melloul <mel...@gm...>; David Schwartz <dsc...@xc...> Sent: Fri, May 27, 2011 9:53:08 PM Subject: Re: Access to existing SPPP codebase Agree with Dean. Having an architecture proposal by COB Monday would be good. Vijay - do you want to take a first crack for discussion on Monday? As we discussed on the call, I prefer we create an architecture proposal that you feel comfortable with, then map out what Mickael and Samuel have done against it, and do the delta analysis. Jean-Francois. On 05/27/2011 16:12, "Dean Willis" <dea...@so...> wrote: > >On May 27, 2011, at 8:33 AM, Jeremy Barkan (Digitalshtick) wrote: > >> Mickael and Samuel are wrapping up the code - David and I will get >>the code on Sunday morning our time and review with Mickael and >>Samuel - and then pass the code on to the group. > >It seems to me that we're not going to have a solid architectural >proposal on the table until we've digested Mickael and Samuel's current >code base. > >Can we get an architectural plan together by COB Monday? > >-- >Dean > |
|
From: Dean W. <dea...@so...> - 2011-06-02 00:40:09
|
I have a request in to CableLabs legal team to bless the Apache 2.0 license for OpenSPP. Also, I note that we have a requirement to have them bless any OSS component we use in the system. I suppose the thing to do would be to add a table for OSS components to theWiki, with a column showing blessing requested/received dates. So, getting some component-jello frozen hard enough that we can nail it to a tree is probably the Next Thing to Do. -- Dean |
|
From: Dean W. <dea...@so...> - 2011-06-01 23:52:10
|
Please check out our Wiki at: https://sourceforge.net/apps/mediawiki/openspp/index.php?title=Main_Page Under Artifacts, see "Product backlog and User Stories" Also, look at Test Cases. I'm torn on keeping those as User Stories. -- Dean |
|
From: Dean W. <dea...@so...> - 2011-06-01 22:30:10
|
I haven't seen a call announcement from Jean-Francois for an all-project call tomorrow. If we're having one, I presume we'll use the same bridge as the last two Thursdays, at 1300 UTC (which, if my math is right, is 0800 US-CDT). If we don't have an all-project call, I'd like to get the development team (Vijay, Jeremy, Samuel, Mickael) together instead, with Skype probably being the easiest way. My Skype ID is edean_willis. I have Vijay Joshi, Jean-Francois, and David on my current Skype contact list, but not the rest of you guys. So, please Skype-up and send me a friend request. Assuming Skype works as advertised, I can voice-conference the lot of us. -- Dean |
|
From: Dean W. <dea...@so...> - 2011-06-01 20:52:48
|
I've noticed that CableLabs has specified some coding standards: https://community.cablelabs.com/svn/OCAPRI/trunk/common/doc/GeneralCodingStandards.pdf Is this the standard we want to work top on OpenSPP? -- Dean |
|
From: Jeremy B. \(Digitalshtick\) <je...@di...> - 2011-06-01 20:19:43
|
Hi Dean, Apache 2.0 seems fine... It is considered more permissive than the GNU licenses [ Apache does not have "copyleft"] - but it does have a patent license clause. Certainly makes sense for OpenSPP Jeremy -----Original Message----- From: Dean Willis [mailto:dea...@so...] Sent: 01 June 2011 19:02 To: ope...@li... Subject: [OpenSPP-project] Conclude on license: Apache 2.0? We need to nail down which Open Source license we'll use. I initially favored Modified BSD, but it looks like we're using a lot of Apache-licensed code in our architecture. This suggests we use the Apache 2.0 license: http://www.apache.org/licenses/LICENSE-2.0.html Any objections? -- Dean ---------------------------------------------------------------------------- -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ OpenSPP-project mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openspp-project |
|
From: Dean W. <dea...@so...> - 2011-06-01 16:02:35
|
We need to nail down which Open Source license we'll use. I initially favored Modified BSD, but it looks like we're using a lot of Apache-licensed code in our architecture. This suggests we use the Apache 2.0 license: http://www.apache.org/licenses/LICENSE-2.0.html Any objections? -- Dean |
|
From: joshi v. k. <vij...@ya...> - 2011-06-01 02:57:14
|
Yes Thanks Vijay ----- Original Message ---- From: Dean Willis <dea...@so...> To: ope...@li... Sent: Tue, May 31, 2011 8:39:50 PM Subject: [Openspp-project] Test message to the "whole project" mailing list This is a test. Are you guys out there yet? -- Dean ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Openspp-project mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openspp-project |
|
From: Dean W. <dea...@so...> - 2011-06-01 00:39:58
|
This is a test. Are you guys out there yet? -- Dean |
1 message has been excluded from this view by a project administrator.
