RE: DataMapper support for CIMI attributes

2012-11-15 Thread Koper, Dies
ials, so the stored property > is now identified by entity 'id', driver and provider. > > http://tracker.deltacloud.org/set/130 > > > -- Michal > > > > > > Regards, > > Dies Koper > > > > > >> -Original Message- &

Re: DataMapper support for CIMI attributes

2012-11-15 Thread Michal Fojtik
--- >> From: Michal Fojtik [mailto:mfoj...@redhat.com] >> Sent: Tuesday, 13 November 2012 11:37 PM >> To: dev@deltacloud.apache.org >> Subject: Re: DataMapper support for CIMI attributes >> >> On 11/13/2012 01:10 PM, Koper, Dies wrote: >>> Hi Michal,

RE: DataMapper support for CIMI attributes

2012-11-14 Thread Koper, Dies
egards, Dies Koper > -Original Message- > From: Michal Fojtik [mailto:mfoj...@redhat.com] > Sent: Tuesday, 13 November 2012 11:37 PM > To: dev@deltacloud.apache.org > Subject: Re: DataMapper support for CIMI attributes > > On 11/13/2012 01:10 PM, Koper, Dies wrote: >

Re: DataMapper support for CIMI attributes

2012-11-13 Thread Michal Fojtik
On 11/13/2012 01:10 PM, Koper, Dies wrote: Hi Michal, The horrible looking 'uuid' field is SHA1 hash composed from credentials, driver name and provider string, so different clients will not override their properties. This is something I've been wondering about, should these properties be s

RE: DataMapper support for CIMI attributes

2012-11-13 Thread Koper, Dies
Hi Michal, > The horrible looking 'uuid' field is SHA1 hash composed from > credentials, driver name and provider string, so different clients will > not override their properties. This is something I've been wondering about, should these properties be stored per user or per resource? I mean, if