actions missing attribute definitions

[Boris Parak]

Some actions served in the OOI model are missing attribute definitions for `method` or other applicable attributes, e.g. 'http://schemas.ogf.org/occi/infrastructure/compute/action#suspend'

Example:

    {
      "attributes": {
        "method": {
          "default": "suspend",
          "description": "Suspend method",
          "mutable": true,
          "pattern": "(?-mix:^(hibernate|suspend)$)",
          "required": false,
          "type": "string"
        }
      },
      "scheme": "http://schemas.ogf.org/occi/infrastructure/compute/action#",
      "term": "suspend",
      "title": "Change compute status to suspended"
    }

vs.

    {
      "scheme": "http://schemas.ogf.org/occi/infrastructure/compute/action#",
      "term": "suspend",
      "title": "suspend compute instance"
    }

[Alvaro Lopez (aloga)]

Hi Boris,

is the "method" attribute mandatory? I have reviewed the OCCI spec and I only could found the following (OCCI core): "An Action instance MAY identify Attributes which correspond to parameters of the invocable operation."

In this particular case OpenStack does not allow any method to be specified, therefore I guess not having any attributes here is ok.

[Boris Parak (araxxxx)]

Hi Alvaro,

this is another ambiguity in the standard. IMO, Action instance MAY identify attributes when it is defined. For INFRA, that is the GFD.224 document where `suspend` has an attribute. The ambiguity here is in "standard" vs. "implementation". Can implementation omit an attribute defined in the standard? It is not clearly stated anywhere ... of course.

I would say that this is not a high-priority issue. Requests specifying an undeclared attribute will simply be rejected by the server. I can live with that.

[Launchpad Janitor (janitor)]

[Expired for ooi because there has been no activity for 60 days.]