W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

RE: Proposal for new Goal: AG007 Management and Provisioning

From: Darran Rolls <Darran.Rolls@waveset.com>
Date: Mon, 29 Jul 2002 09:06:13 -0500
Message-ID: <6244FCD1F88EC14BACDD2A319FD338242DC760@hawaii.waveset.com>
To: "Sedukhin, Igor" <Igor.Sedukhin@ca.com>, "ECKERT,ZULAH (HP-Cupertino,ex1)" <zulah_eckert@hp.com>, "WSA W3C Public (E-mail)" <www-ws-arch@w3c.org>

Igor

I'm happy to champion an AC-YYY for provisioning and a glossary item to
go with it.  The context I would adopt for this is that of "setup".
Provisioning has been defined by the telecom industry for years to mean
service activation/initiation".  IMO provisioning a web service means
this and more, covering any/all elements of the *setup* and life-cycle
of a given service.  Before I draft this CSF/requirement, I would like
you (and the WG) to consider the following elements as being part of our
definition of provisioning:

1 - Management of the initial service-users subscription
2 - Setup of any required data (accounts, configuration, service
settings)
3 - Service-user self-service (changing subscription options etc.)
4 - Management of service revocation

IMO SLA is not directly provisioning, although a provisioning service
could be responsible for setting the service options that make up pat of
the SLA.  I'd rather see the entirety of what is SLA called out
separately.

Regards,

--------------------------------------------------------
Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
(512) 657 8360                    
--------------------------------------------------------


> -----Original Message-----
> From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com]
> Sent: Thursday, July 25, 2002 8:59 AM
> To: Darran Rolls; ECKERT,ZULAH (HP-Cupertino,ex1); WSA W3C Public
(E-mail)
> Subject: RE: Proposal for new Goal: AG007 Management and Provisioning
> 
> Darran,
> 
> Probably AC-YYY will do for provisioning, if you want to champion one.
> Similar to AC-0018 for management.
> 
> The goal should be common though for management and provisioning is
very
> much interrelated and basically fall into a category that is very hard
to
> separate without significant perception differences.
> 
> For example SLAs, are they provisioning or management related... There
> could be plenty of opinions here.
> Same applies to accounting/billing, which commonly falls into
> provisioning. The only way to do the later is to meter the usage, and
that
> is usually management task.
> 
> The intended purpose of AG-0007 was to provide for organization and
> control of the environment in which WSs operate.
> 
> My take on this is that if we can pull AG-0007, then we get a space to
> consolidate all related work. Otherwise there could be too few
supporters
> of each of the separated goals and none would get in.
> 
> -- Igor Sedukhin .. (Igor.Sedukhin@ca.com)
> -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
> 
> 
> 
> -----Original Message-----
> From: Darran Rolls [mailto:Darran.Rolls@waveset.com]
> Sent: Wednesday, July 24, 2002 7:18 PM
> To: ECKERT,ZULAH (HP-Cupertino,ex1); WSA W3C Public (E-mail)
> Subject: RE: Proposal for new Goal: AG007 Management and Provisioning
> 
> 
> 
> Comments:
> 
> -- I fully support the separation of managerial elements of the
> architecture into the separate goal AG007.
> 
> -- As a representative from a provisioning solutions company I'm
obviously
> happy to see the word "Provisioning" so clearly called out ;-).  That
> said, I don't see why we would do this above other mgmt disciplines.
I
> would rather see it identified in a separate sub-goal or requirement
thus:
> 
> 	"AG|R XXXX   The WSA should include a reference model for
> provisioning of all elements of a web service that is consistent with
> emerging WS identity and general service provisioning standards"
> 
> -- I therefore propose the following amendments to the main
description of
> the goal:
> 	AG007 - WS Management
> 	The WSA must provide guidelines on how to manage the
> 	complete life-cycle of an operating web service.
> 
> --------------------------------------------------------
> Darran Rolls                      http://www.waveset.com
> Waveset Technologies Inc          drolls@waveset.com
> (512) 657 8360
> --------------------------------------------------------
> 
> 
> > -----Original Message-----
> > From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com]
> > Sent: Wednesday, July 24, 2002 6:04 PM
> > To: WSA W3C Public (E-mail)
> > Cc: ECKERT,ZULAH (HP-Cupertino,ex1)
> > Subject: Proposal for new Goal: AG007 Management and Provisioning
> >
> >
> >
> >
> > The RTF recommends the addition of a new goal, AG007 below, and
moving
> > AC018 from AG002 (Reliability) to AG007. The reason for this
addition
> > and
> change
> > is that "reliability" does not adequately contain the success
factors
> for
> > management.
> >
> >
> > AG007 Management and Provisioning
> > Web Services Architecture must provide for a manageable, accountable
> and
> > organized environment for Web Services operations.
> >
> > Please comment on this new proposal as I will be asking the team to
> > consider this change at tomorrow's meeting,
> > Zulah
Received on Monday, 29 July 2002 10:06:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:03 GMT