fp7mplane / protocol-ri

mPlane protocol reference implementation
4 stars 9 forks source link

Is it possible to query Repository Components for data in the past. #52

Open netvisor opened 9 years ago

netvisor commented 9 years ago

We cannot execute a specification with "when" parameter that sepcifies a period in the past (ie. which ends before now).

We believe a repository should support such specifications.


Moreover, it would be nice, if "When" parameters like "now - 3600 ... now" would be supported.

Regards: Árpad

iliasl commented 9 years ago

If the capability/specification is “query” then you should be able.

From: netvisor notifications@github.com Reply-To: fp7mplane/protocol-ri <reply+004a3f3b834f3f3e8cfed45638152704ad309b2dcdef262e92cf0000000111b644259 2a169ce059b429c@reply.github.com> Date: Thursday 9 July 2015 16:16 To: fp7mplane/protocol-ri protocol-ri@noreply.github.com Subject: [protocol-ri] Is it possible to query Repository Components for data in the past. (#52)

We cannot execute a specification with "when" parameter that sepcifies a period in the past (ie. which ends before now).

We believe a repository should support such specifications.

Moreover, it would be nice, if "When" parameters like "now - 3600 ... now" would be supported.

Regards: Árpad

— Reply to this email directly or view it on GitHub https://github.com/fp7mplane/protocol-ri/issues/52 .

britram commented 9 years ago

The scheduler uses the verb to determine whether it should schedule running a job based on the temporal scope, or to pass control immediately to the service. Currently, the verb "query" means to pass control immediately.

The design intent of the protocol is that all queries for the past be absolute -- in terms of absolute start and end timestamps. The "now + duration" form is intended only for measurements when the start time is unimportant, though in the rather direct interface that mpcli gives to components, it can also be used for convenience.

We could add a convenience feature to mpcli that would translate relative negative temporal scopes into absolute temporal scopes on the client side, though this would only have effect within mpcli, not within all clients using the client.py module.