SID and the RSpec

[Shane Dempsey-2]

Hi,
During the narrow waist working group discussions on the 10/10/2007 I
mentioned an information modeling standard for telecommunications
equipment. This was in the context of reusing existing work in resource
description from groups such as the TeleManagement Forum (TMForum) and
the Distributed Management Task Force (DMTF).

The standard I mentioned was Shared Information/Data or SID. Its remit
is actually much broader than merely describing equipment resources as
you can see from this primer.
http://www.tmforum.org/browse.aspx?catID=2008 

In particular I'd draw your attention to the "resource view" as
something that RSpec could build on. It's worth considering how this
work relates to describing virtualised slivers, slices and aggregates.

regards,

   ...shane

// Shane Dempsey
// Senior Software Engineer
// TSSG - http://www.tssg.org
// ArcLabs, Carriganore,
// Waterford, Ireland.


_______________________________________________
narrow-waist-wg mailing list
narrow-waist-wg@...
http://lists.geni.net/mailman/listinfo/narrow-waist-wg

[Larry Peterson]

We most certainly need to leverage existing systems/software where
ever it makes
sense. In taking a quick look at the TMForum, I have a couple
questions (beyond the
obvious "does it solve a problem we have"). I think these apply
generally to the issue
of importing technologies into GENI:

1) Is it possible to adopt just the useful pieces (e.g., the SID for
describing resources)
     without having to buy into the whole ball of wax?

2) Are software tools available, and can we have access to them w/out
undue burden?
     (Same goes for documentation.)

3) Are our objectives sufficiently aligned, so we can influence future
directions of the
     system, or  should we view this as a one-time "technology
injection", where we
     subsume responsibility for future evolution?

Do you have any sense of the answers for this particular case?

Larry

On 10/15/07, Shane Dempsey <sdempsey@...> wrote:

> Hi,
> During the narrow waist working group discussions on the 10/10/2007 I
> mentioned an information modeling standard for telecommunications
> equipment. This was in the context of reusing existing work in resource
> description from groups such as the TeleManagement Forum (TMForum) and
> the Distributed Management Task Force (DMTF).
>
> The standard I mentioned was Shared Information/Data or SID. Its remit
> is actually much broader than merely describing equipment resources as
> you can see from this primer.
> http://www.tmforum.org/browse.aspx?catID=2008
>
> In particular I'd draw your attention to the "resource view" as
> something that RSpec could build on. It's worth considering how this
> work relates to describing virtualised slivers, slices and aggregates.
>
> regards,
>
>    ...shane
>
> // Shane Dempsey
> // Senior Software Engineer
> // TSSG - http://www.tssg.org
> // ArcLabs, Carriganore,
> // Waterford, Ireland.
>
>
> _______________________________________________
> narrow-waist-wg mailing list
> narrow-waist-wg@...
> http://lists.geni.net/mailman/listinfo/narrow-waist-wg
>
>

_______________________________________________
narrow-waist-wg mailing list
narrow-waist-wg@...
http://lists.geni.net/mailman/listinfo/narrow-waist-wg

[Shane Dempsey-2]

Hi Larry, all,
Apologies for the delay in responding. We've been discussing this matter
with the Autonomic Communications Forum (ACF) and John Strassner, the
creator of DEN and the SID model. John's a Motorola Fellow and an
associate professor at my institute.

Pending further analysis :)
1) Taking just the bits we want/like shouldn't be a problem.
Dependencies are managed sensitively across the SID. The basic meta
model is very light so we can mix and match models, such as "resource"
which is analogous to RSpec.
2) There are commercial tools available. ACF are developing open tools.
I'll provide more information on these shortly but as far as I
understand these would be suitable for the research community.
3) Based on my institute's work in the ACF we believe there's an
alignment of objectives. Also John has indicated a desire to engage with
the GENI effort.

With this as a baseline, at the minimum a technology injection is
realistic but a longer term collaboration looking at both information
modeling and autonomics would be preferable.  Considering the GENI
Research Plan (v 4.5) this could be a good fit?

Just a note about the ACF. The website refers to a European project that
has been subsumed within a much larger global standardisation effort
with participation from major ICT vendors and academic institutes from
around the world including Motorola, HP and IBM.  A new website and
marketing/scientific collateral will be available soon.

regards,

   ...shane


Larry Peterson wrote:

> We most certainly need to leverage existing systems/software where
> ever it makes
> sense. In taking a quick look at the TMForum, I have a couple
> questions (beyond the
> obvious "does it solve a problem we have"). I think these apply
> generally to the issue
> of importing technologies into GENI:
>
> 1) Is it possible to adopt just the useful pieces (e.g., the SID for
> describing resources)
>      without having to buy into the whole ball of wax?
>
> 2) Are software tools available, and can we have access to them w/out
> undue burden?
>      (Same goes for documentation.)
>
> 3) Are our objectives sufficiently aligned, so we can influence future
> directions of the
>      system, or  should we view this as a one-time "technology
> injection", where we
>      subsume responsibility for future evolution?
>
> Do you have any sense of the answers for this particular case?
>
> Larry
>
> On 10/15/07, Shane Dempsey <sdempsey@...> wrote:
>  
>> Hi,
>> During the narrow waist working group discussions on the 10/10/2007 I
>> mentioned an information modeling standard for telecommunications
>> equipment. This was in the context of reusing existing work in resource
>> description from groups such as the TeleManagement Forum (TMForum) and
>> the Distributed Management Task Force (DMTF).
>>
>> The standard I mentioned was Shared Information/Data or SID. Its remit
>> is actually much broader than merely describing equipment resources as
>> you can see from this primer.
>> http://www.tmforum.org/browse.aspx?catID=2008
>>
>> In particular I'd draw your attention to the "resource view" as
>> something that RSpec could build on. It's worth considering how this
>> work relates to describing virtualised slivers, slices and aggregates.
>>
>> regards,
>>
>>    ...shane
>>
>> // Shane Dempsey
>> // Senior Software Engineer
>> // TSSG - http://www.tssg.org
>> // ArcLabs, Carriganore,
>> // Waterford, Ireland.
>>
>>
>> _______________________________________________
>> narrow-waist-wg mailing list
>> narrow-waist-wg@...
>> http://lists.geni.net/mailman/listinfo/narrow-waist-wg
>>
>>
>>    
>
>  

_______________________________________________
narrow-waist-wg mailing list
narrow-waist-wg@...
http://lists.geni.net/mailman/listinfo/narrow-waist-wg