Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should network resources' occi.core.id contain "/network/" part? #33

Open
bhagemeier opened this issue Feb 28, 2013 · 5 comments
Open

Comments

@bhagemeier
Copy link
Contributor

Hi,

I've been pointed to this issue about the occi.core.id. @arax is of the opinion that it should not, but I cannot see anything in the core OCCI spec that would restrict the id. After all, it is a URI w/o semantics. Let's clarify this.

Björn

@dizz
Copy link
Collaborator

dizz commented Feb 28, 2013

occi.core.id's structure is opaque, so long as it is unique within the domain of the service provider, so I'd agree with what you say @bhagemeier. If it is unclear from the spec then I'd suggest we continue the conversation on the OCCI ML.

@arax
Copy link

arax commented Feb 28, 2013

You are, of course, right. There are almost no restrictions on occi.core.id's structure in the specification but it would be nice if the same approach was used for all resources at least within one implementation.

At the moment occi.core.id in /network/ contains /network/ and a human-readable name from OS but in /compute/ it's only a hash, e.g. 183b4a73-8310-4920-8351-d07c16da58bc.

It's difficult to implement a reasonably human-readable output formatting (or provide a user-friendly interface) when there are structure changes not only from implementation to implementation but also from resource to resource in one implementation.

This, of course, has no effect on functionality but it's not always easy to explain to users why sometimes they can write

... --action describe --resource /compute/183b4a73-8310-4920-8351-d07c16da58bc

and see the last part of the location matching the ID and sometimes have an ID and not be able to write

... --action describe --resource /network//network/public

to get some more information about the resource.

Am I completely wrong?

@dizz
Copy link
Collaborator

dizz commented Feb 28, 2013

IMO, from an implementation consistency point of view you're correct.

@bhagemeier
Copy link
Contributor Author

@dizz, should we resolve this issue somehow? A dangling question is never a good idea. Should this become a feature request? I had a brief look at the code, but I'm not quite sure whether I would get it right.

@dizz
Copy link
Collaborator

dizz commented Mar 6, 2013

Have set it as an enhancement. If you could suggest a pull request that would be highly appreciated. Likely that at this point is a good start

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants