Occi resources without titles
Hi, In the current specification, we do not require a resource "title" attribute. However, in the examples, the specification show canonic serialized forms of resources, collections and kinds as a URI using identifiers that I interpret as the occi titles. How should we handle resources created without titles. I have a few suggestions: 1) Allow the provider to assign a resource name. Preferably using a scheme of Resource Identifier (storage, compute, network) plus an number with scheme infinitely incrementing for a specific kind collection. ie Storage01, Storage02, Storage03. If "Storage02" is deleted, the new would be "Storage04". 2) Use the resource identifier until the title attribute is set. 3) Leave the title unset and use to resource kind to identify the resource. 4) Force an occi client to submit a resource title with each create action. This may be impractical if the provider creates resources for you. Number one is my favorite... other suggestion welcome.. cheers, gary
Hey Gary, In our implementation of OCCI we are not mandating the use of "title" nor making any dependencies on its value. I think the most appropriate method to identify the resource is using the kind type (your option 3). This is what we do; we associate the created resource with a kind category always, so making resource type identification relatively straight forward. Andy -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Gary Mazz Sent: Monday, March 29, 2010 4:33 AM To: occi-wg@ogf.org Subject: [occi-wg] Occi resources without titles Hi, In the current specification, we do not require a resource "title" attribute. However, in the examples, the specification show canonic serialized forms of resources, collections and kinds as a URI using identifiers that I interpret as the occi titles. How should we handle resources created without titles. I have a few suggestions: 1) Allow the provider to assign a resource name. Preferably using a scheme of Resource Identifier (storage, compute, network) plus an number with scheme infinitely incrementing for a specific kind collection. ie Storage01, Storage02, Storage03. If "Storage02" is deleted, the new would be "Storage04". 2) Use the resource identifier until the title attribute is set. 3) Leave the title unset and use to resource kind to identify the resource. 4) Force an occi client to submit a resource title with each create action. This may be impractical if the provider creates resources for you. Number one is my favorite... other suggestion welcome.. cheers, gary _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
Hi Andy, Thanks for the tip :) The problem comes in if I have more than one of the same resource without a title and I want to set the attribute or a link on only one of the resources. In this case I have to address the issue at the category with a more complicated update. -g On Mon, Mar 29, 2010 at 1:34 PM, Edmonds, AndrewX <andrewx.edmonds@intel.com
wrote:
Hey Gary, In our implementation of OCCI we are not mandating the use of "title" nor making any dependencies on its value. I think the most appropriate method to identify the resource is using the kind type (your option 3). This is what we do; we associate the created resource with a kind category always, so making resource type identification relatively straight forward.
Andy
-----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Gary Mazz Sent: Monday, March 29, 2010 4:33 AM To: occi-wg@ogf.org Subject: [occi-wg] Occi resources without titles
Hi,
In the current specification, we do not require a resource "title" attribute. However, in the examples, the specification show canonic serialized forms of resources, collections and kinds as a URI using identifiers that I interpret as the occi titles.
How should we handle resources created without titles.
I have a few suggestions:
1) Allow the provider to assign a resource name. Preferably using a scheme of Resource Identifier (storage, compute, network) plus an number with scheme infinitely incrementing for a specific kind collection. ie Storage01, Storage02, Storage03. If "Storage02" is deleted, the new would be "Storage04".
2) Use the resource identifier until the title attribute is set.
3) Leave the title unset and use to resource kind to identify the resource.
4) Force an occi client to submit a resource title with each create action. This may be impractical if the provider creates resources for you.
Number one is my favorite... other suggestion welcome..
cheers, gary
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
If you need to update a particular resource (kind), don't you have a unique URL pointing to that such that you can PUT updated content to it? How do you identify each resource within your implementation? To update a resource's links we would typically send using HTTP (where /compute/node1 is a unique URL): PUT /compute/node1 HTTP/1.1 Host: example.com Authorization: Basic xxxxxxxxxxxxxxxxxxx User-Agent: occi-client/1.0 (linux) libcurl/7.19.4 OCCI/1.0 Link: </storage/san1>; rel="http://purl.org/occi/kind#storage"; title="SAN node 1" device="sda" mountpoint="/home" Link: </networks/dmz>; rel="http://purl.org/occi/kind#network"; title="DMZ Connection"; ip="1.2.3.4/24"; interface="eth0" From: gary mazzaferro [mailto:garymazzaferro@gmail.com] Sent: Monday, March 29, 2010 9:06 PM To: Edmonds, AndrewX Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Occi resources without titles Hi Andy, Thanks for the tip :) The problem comes in if I have more than one of the same resource without a title and I want to set the attribute or a link on only one of the resources. In this case I have to address the issue at the category with a more complicated update. -g On Mon, Mar 29, 2010 at 1:34 PM, Edmonds, AndrewX <andrewx.edmonds@intel.com<mailto:andrewx.edmonds@intel.com>> wrote: Hey Gary, In our implementation of OCCI we are not mandating the use of "title" nor making any dependencies on its value. I think the most appropriate method to identify the resource is using the kind type (your option 3). This is what we do; we associate the created resource with a kind category always, so making resource type identification relatively straight forward. Andy -----Original Message----- From: occi-wg-bounces@ogf.org<mailto:occi-wg-bounces@ogf.org> [mailto:occi-wg-bounces@ogf.org<mailto:occi-wg-bounces@ogf.org>] On Behalf Of Gary Mazz Sent: Monday, March 29, 2010 4:33 AM To: occi-wg@ogf.org<mailto:occi-wg@ogf.org> Subject: [occi-wg] Occi resources without titles Hi, In the current specification, we do not require a resource "title" attribute. However, in the examples, the specification show canonic serialized forms of resources, collections and kinds as a URI using identifiers that I interpret as the occi titles. How should we handle resources created without titles. I have a few suggestions: 1) Allow the provider to assign a resource name. Preferably using a scheme of Resource Identifier (storage, compute, network) plus an number with scheme infinitely incrementing for a specific kind collection. ie Storage01, Storage02, Storage03. If "Storage02" is deleted, the new would be "Storage04". 2) Use the resource identifier until the title attribute is set. 3) Leave the title unset and use to resource kind to identify the resource. 4) Force an occi client to submit a resource title with each create action. This may be impractical if the provider creates resources for you. Number one is my favorite... other suggestion welcome.. cheers, gary _______________________________________________ occi-wg mailing list occi-wg@ogf.org<mailto:occi-wg@ogf.org> http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
participants (3)
-
Edmonds, AndrewX -
Gary Mazz -
gary mazzaferro