« Return to Thread: CF Requirements: 2) Identity Vocabulary
Re: [geni-dev] CF Requirements: 2) Identity Vocabulary
by Robert P Ricci
::
Rate this Message:
Thus spake Max Ott on Thu, Mar 19, 2009 at 09:15:26AM +1100:
> Ilia Baldine is using NDL in ORCA and I have been trying to at least
> convert RSpec into an ontology (all my tools fails to parse the
> current spec).
One thing you might try is looking at the working RSpec draft from
ProtoGENI, which is less ambitions that the spec you are looking at, but
is in better shape to see actual use.
> Coming back to relationships mentioned above, there are some
> interesting 'complications'. Let's pick a simple resource, such as a
> computer. That obviously should have a identifier. At some stage we
> replace the disk. Does the resource get a new identifier? It's not the
> same anymore, it's performance and capabilities may have changed. So
> our inventory ontology (or database schema) breaks this down into
> related resources which make up an other one. (Is a computer now an
> aggregate as it aggregates such "atomic" resources as motherboard,
> memory, disk, ...)
I think the main value in giving the computer it own identifier (as
opposed to simply being an aggregate of the identifiers of the resources
that comprise it), besides the obvious convenience factor, is that one
of the key things that these identifiers will be used in, for example,
tickets, and it seems pretty clear that if I have a slice of this
computer, and the disk gets replaced, I still want a persistent
identifier with which to talk about the computer that my slice resides
on.
> Not sure if this fundamentally solves the problem. How do we ensure
> uniqueness of the Suite ID (another UUID) and how do we initially find
> all the entry points to the various suites? If we assume that in
> order to bootstrap the system we need a way to find out about all the
> registries first, or have a hierarchical structure where everyone
> knows THE registry and it knows (indirectly) every available suite,
> then obviously we start with the relevant knowledge.
>
> I guess, if nothing else it limits the number of identifiers we are
> looking for and it's a rather stable set. Any gossiping scheme would
> work very well.
We've been talking about doing something like this with human readable
names (HRNs) that look something like DNS names. (I believe the
PlanetLab cluster is doing something similar as well.) We definitely
think that set of roots will be small enough for a simple centralized
registry of them to handle. We're not using DNS and IPv6 for lookups,
though. :)
--
/-----------------------------------------------------------
| Robert P Ricci <ricci@...> | <ricci@...>
| Research Associate, University of Utah Flux Group
| www.flux.utah.edu | www.emulab.net
\-----------------------------------------------------------
_______________________________________________
control-wg mailing list
control-wg@...
http://lists.geni.net/mailman/listinfo/control-wg
> Ilia Baldine is using NDL in ORCA and I have been trying to at least
> convert RSpec into an ontology (all my tools fails to parse the
> current spec).
One thing you might try is looking at the working RSpec draft from
ProtoGENI, which is less ambitions that the spec you are looking at, but
is in better shape to see actual use.
> Coming back to relationships mentioned above, there are some
> interesting 'complications'. Let's pick a simple resource, such as a
> computer. That obviously should have a identifier. At some stage we
> replace the disk. Does the resource get a new identifier? It's not the
> same anymore, it's performance and capabilities may have changed. So
> our inventory ontology (or database schema) breaks this down into
> related resources which make up an other one. (Is a computer now an
> aggregate as it aggregates such "atomic" resources as motherboard,
> memory, disk, ...)
I think the main value in giving the computer it own identifier (as
opposed to simply being an aggregate of the identifiers of the resources
that comprise it), besides the obvious convenience factor, is that one
of the key things that these identifiers will be used in, for example,
tickets, and it seems pretty clear that if I have a slice of this
computer, and the disk gets replaced, I still want a persistent
identifier with which to talk about the computer that my slice resides
on.
> Not sure if this fundamentally solves the problem. How do we ensure
> uniqueness of the Suite ID (another UUID) and how do we initially find
> all the entry points to the various suites? If we assume that in
> order to bootstrap the system we need a way to find out about all the
> registries first, or have a hierarchical structure where everyone
> knows THE registry and it knows (indirectly) every available suite,
> then obviously we start with the relevant knowledge.
>
> I guess, if nothing else it limits the number of identifiers we are
> looking for and it's a rather stable set. Any gossiping scheme would
> work very well.
We've been talking about doing something like this with human readable
names (HRNs) that look something like DNS names. (I believe the
PlanetLab cluster is doing something similar as well.) We definitely
think that set of roots will be small enough for a simple centralized
registry of them to handle. We're not using DNS and IPv6 for lookups,
though. :)
--
/-----------------------------------------------------------
| Robert P Ricci <ricci@...> | <ricci@...>
| Research Associate, University of Utah Flux Group
| www.flux.utah.edu | www.emulab.net
\-----------------------------------------------------------
_______________________________________________
control-wg mailing list
control-wg@...
http://lists.geni.net/mailman/listinfo/control-wg
« Return to Thread: CF Requirements: 2) Identity Vocabulary
| Free embeddable forum powered by Nabble | Forum Help |
