Dear OGSA WG, I have an action from the OGSA Dqta WG to ask you about service creation. When creating services in OGSA, how does the client specify the following properties: - Lifetime of Service - (Storage) Size - Default QoS requirements - Default (security) policies - Service Location (on which Server say) - Provisioning Do you have a common pattern for service creation, or common definitions of the above items? Currently we are assuming the existence of factory services that can create shorter-term services. E.g. in data transport, the long-lived service will create a short-lived service that manages the actual data transfer. Clients will send control messages to the shorter-lived service. This seems similar to the pattern originally encoded in OGSI. Is it still the OGSA-approved way to manage service creation? Best wishes, Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre, 15 South College Street Edinburgh, EH8 9AA +44 131 651 4039
Dave, A very good question. We are working on just this problem at uva - but think a broader discussion is in order. A _____ From: ogsa-wg-bounces@ogf.org [mailto:ogsa-wg-bounces@ogf.org] On Behalf Of Dave Berry Sent: Monday, December 04, 2006 12:41 PM To: ogsa-wg Cc: ogsa-d-wg@ogf.org Subject: [ogsa-wg] Service creation in OGSA? Dear OGSA WG, I have an action from the OGSA Dqta WG to ask you about service creation. When creating services in OGSA, how does the client specify the following properties: - Lifetime of Service - (Storage) Size - Default QoS requirements - Default (security) policies - Service Location (on which Server say) - Provisioning Do you have a common pattern for service creation, or common definitions of the above items? Currently we are assuming the existence of factory services that can create shorter-term services. E.g. in data transport, the long-lived service will create a short-lived service that manages the actual data transfer. Clients will send control messages to the shorter-lived service. This seems similar to the pattern originally encoded in OGSI. Is it still the OGSA-approved way to manage service creation? Best wishes, Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre, 15 South College Street Edinburgh, EH8 9AA +44 131 651 4039
In terms of QoS I don't think there is a statement yet from OGSA - though we will hopefully be holding an ad-hoc BoF at OGF19 to discuss this issue. steve.. Andrew Grimshaw wrote:
Dave,
A very good question. We are working on just this problem at uva -- but think a broader discussion is in order.
A
------------------------------------------------------------------------
*From:* ogsa-wg-bounces@ogf.org [mailto:ogsa-wg-bounces@ogf.org] *On Behalf Of *Dave Berry *Sent:* Monday, December 04, 2006 12:41 PM *To:* ogsa-wg *Cc:* ogsa-d-wg@ogf.org *Subject:* [ogsa-wg] Service creation in OGSA?
Dear OGSA WG,
I have an action from the OGSA Dqta WG to ask you about service creation. When creating services in OGSA, how does the client specify the following properties:
- Lifetime of Service - (Storage) Size - Default QoS requirements - Default (security) policies - Service Location (on which Server say) - Provisioning
Do you have a common pattern for service creation, or common definitions of the above items?
Currently we are assuming the existence of factory services that can create shorter-term services. E.g. in data transport, the long-lived service will create a short-lived service that manages the actual data transfer. Clients will send control messages to the shorter-lived service.
This seems similar to the pattern originally encoded in OGSI. Is it still the OGSA-approved way to manage service creation?
Best wishes,
Dave Berry
Deputy Director, Research & E-infrastructure Development
National e-Science Centre, 15 South College Street
Edinburgh, EH8 9AA +44 131 651 4039
------------------------------------------------------------------------
-- ogsa-wg mailing list ogsa-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg
-- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------
participants (3)
-
A.S.McGough -
Andrew Grimshaw -
Dave Berry