This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.occi-wg/wiki/Issues at Thu, 03 Nov 2022 00:09:58 GMT SourceForge : View Wiki Page: Issues

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin

Web Site
Search Wiki Pages Project: occi-wg     Wiki > Issues > View Wiki Page
wiki2450: Issues

Please remove fixed issues and add a statement to the Changelog of the corresponding Wiki page

Open Issues

  • (Infrastructure) Network needs to be defined in more detail
  • (Infrastructure) Storage needs to refined
  • (Rendering) in URLs some characters need to be URI encoded (e.g. '#' -> %23). Need to note in the rendering section something like "URLs supplied to an implementation must be URI encoded"
  • (Collections) Some topics not covered in the document. ... 1) Can a collection exist at the consumer's root point of presence ? 2) How do you define a parent occi element as a collection parent ? 3) Can any occi element (compute, network, storage) be defined as a parent for a collection ? 4) Are recursive graphs permitted ?

Fixed issues - but need documentation

  • (Core) add version string 1.1 somewhere...
  • Currently there is little content returned in the response of many requests. We should by default return a representation of the resource (to be) created, otherwise there is potential unnecessary network traffic overhead. Otherwise HTTP codes 203 and 204 should be used where appropriate. (Action item: andy/add note: do expect content in the body)
  • (Infra) Link is not sufficient to represent Network Links from compute to Network. Same for storage 2010-09-04: The new Core model definition allow Links to by subtyped for provider extension. The above issue is thus considered fixed. (Action item: ??)

Fixed - to be reviewed

  • (Rendering/Core) Versioning
  • REST needs to be added to render doc (Action item: tmet)
  • Document actions in more detail (especially regarding: long running jobs) (Action item: tmet)
  • How to document and register OCCI extensions should be defined (Action item: tmet)
  • Query interface (Action item: tmet)
  • Query Interface - e.g. how to query for all compute types that have another category type or how to query a category with a particular attribute value. 2010-09-21: Fixed, not documented. (Action item: tmet)
  • More examples (fat-links, creation of res with links etc, actions - collections etc.) (Action item: Andy, Ralf)
  • HTTP Header rendering text/plain fallback to HTTP body to circumvent Header size restrictions. Fixed but not documented yet. (Action item: Ralf)
  • (Core) How can we added/removed tags if categories is immutable? Suggestion: added a mutable attribute to Kind called 'tags'. Specify their semantics as: "tags should be implemented. these tags should be non-executive and may be executive. to be non-executive means that no direct changes to the target Kind will be performed and assigning a non-executive tag is only an act of adding additional metadata. to be executive means that direct changes to the target Kind will be performed (e.g. assigning a location tag will move a Compute Kind) as well as adding the associated metadata. executive tags are akin to mix-ins in programming languages. TODO specify a scheme/term for simple non-exe tags. See: Categories & Collections
  • Collections (Action item: Andy) - Documented See: Categories & Collections
  • Collections and their relationship to Categories (Action item: Andy) - Documented' 'See: Categories & Collections
  • Multi-request submission. Fixed for HTTP rendering using multipart. Fixed, example present but documentation lacking.(Action item: Andy) See: Categories & Collections
  • OS Template & Categories - e.g. how to specify ubuntu 9.10 x64 using categories, how to specify parameters to a OS (boot params etc). Fixed, partly documented in Core. (Action item: Andy, Ralf) See: InfrastructureTemplates
  • Add Console I/O attributes... (Action item: Gary) See: Consoles
  • Add credentials to storage (Guests, Remote, Third Party, direct access)... Use a common scheme to console, maybe adopt kmip ? (Action Item: Gary)
  • A generalized security specification for OCCI to incorporate consoles, storage, vpn, etc.. (Action Item: Gary)
  • (Rendering) How to discover authentication methods of a provider (AR: andy) See Authentication Mechanism Discovery
  • (Core) It must be noted in the specification that Links MUST be uniquely identified. To do this the 'id' attribute will be moved from Resource to Kind (AR: Ralf)

Issues which will be resolved in Extensions

  • Credential definition and management
  • OVF/JSON/XML support in the body?
  • If Long Running Jobs is defined as a Resource extension it should not be documented in Core.
  • HTTP 200 "Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action."

Regarding long running jobs:

  • Add notification URI as a may
  • Make state as an enumeration
  • Supply state diagram
  • Find better name for intermediate_resource
  • Update core model diagram
  • blocking long-running jobs?

Postponed issues

  • Not clear how to create a public facing network or a private network
  • Semantics of provisioning a compute in relation to networking is undecided - does every new compute instance automatically get a private and public ip (in the case of EC2) or none at all?
  • Definition of "Network" - is it a client device or switch-like device?
 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.occi-wg/wiki/Issues at Thu, 03 Nov 2022 00:09:58 GMT