Regulating migration and recall actions for high latency media (hlm) on objects or group of objects through metadata locking attributes

Patent metadata

Field	Value
Publication number	US-2019197144-A1
Application number	US-201715851546-A
Country	US
Kind code	A1
Filing date	Dec 21, 2017
Priority date	Dec 21, 2017
Publication date	Jun 27, 2019
Grant date	—

Abstract

A computer-implemented method according to one embodiment includes receiving a request to perform a high-latency media (HLM) action on an object or a group of objects, identifying metadata associated with the object or group of objects, and conditionally allowing the HLM action to be performed on the object or group of objects, based on the HLM action and the metadata associated with the object.

First claim

What is claimed is:

1 . A computer-implemented method, comprising:
receiving a request to perform a high-latency media (HLM) action on an object or a group of objects; identifying metadata associated with the object or group of objects; and conditionally allowing the HLM action to be performed on the object or group of objects, based on the HLM action and the metadata associated with the object.

2 . The computer-implemented method of claim 1 , wherein the HLM action includes a migration action including a movement of the object or group of objects from an object store to the HLM.

3 . The computer-implemented method of claim 1 , wherein the HLM action includes a recall action including a movement of the object or group of objects from the HLM to an object store.

4 . The computer-implemented method of claim 1 , wherein the request is received using an application programming interface (API).

5 . The computer-implemented method of claim 1 , wherein the metadata includes a lock status indicator that indicates whether a lock is currently being held on the object or group of objects for one or multiple HLM operations.

6 . The computer-implemented method of claim 1 , wherein the metadata is selected from a group consisting of:
a timestamp indicating when a lock was acquired; an identifier of an entity that acquired the lock; a start timestamp indicating a time and date when the lock is to be acquired for the object or group of objects; a flag indicating that the lock for the object or group of objects needs to be acquired at a next possible non-conflicting time; a timespan for which the lock should be acquired; an end timestamp indicating a time and date when the lock is to be released for the object or group of objects; an indication of one or more actions to be performed on the object or group of objects during the lock; an indication of one or more actions to be prevented on the object or group of objects during the lock; and a user-defined comment section.

7 . The computer-implemented method of claim 1 , wherein the metadata associated with the object or group of objects is identified from extended attributes of a file representation of the object or group of objects.

8 . The computer-implemented method of claim 1 , further comprising comparing the HLM action to the metadata in order to determine whether a lock or a conflict exists that prevents accepting or currently executing the request.

9 . The computer-implemented method of claim 1 , further comprising identifying a lock or a conflict, and cancelling or postponing the HLM action, in response to determining that:
the HLM action includes a requested migration action to be performed at a predetermined time and date, and the metadata associated with the object or group of objects indicates that a lock is currently held on the object or group of objects, such that no migration actions are be performed during the predetermined time and date of the requested migration action.

10 . The computer-implemented method of claim 1 , further comprising identifying a conflict, and cancelling or postponing the HLM action, in response to determining that:
the HLM action includes a requested migration action to be performed at a predetermined time and date, and the metadata associated with the object or group of objects indicates that a recall action or a object data access action are to be performed during the predetermined time and date of the requested migration action.

11 . The computer-implemented method of claim 1 , further comprising allowing the HLM action, in response to determining that:
the HLM action includes a requested migration action to be performed at a predetermined time and date, and the metadata associated with the object or group of objects does not indicate any conflicting or prohibited actions during the predetermined time and date of the requested migration action.

12 . The computer-implemented method of claim 1 , further comprising identifying a conflict, and cancelling or postponing the HLM action, in response to determining that:
the HLM action includes a requested recall action to be performed at a predetermined time and date, and the metadata associated with the object or group of objects indicates that a lock is currently held on the object or group of objects, such that no recall actions are be performed during the predetermined time and date of the requested recall action.

13 . A computer program product for controlling a high-latency media (HLM) action on an object or group of objects, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program instructions executable by a processor to cause the processor to perform a method comprising:
receiving a request to perform the HLM action on the object or group of objects, utilizing the processor; identifying metadata associated with the object or group of objects, utilizing the processor; and conditionally allowing the HLM action to be performed on the object or group of objects, based on the HLM action and the metadata associated with the object or group of objects, utilizing the processor.

14 . The computer program product of claim 13 , wherein the HLM action includes a migration action including a movement of the object or group of objects from an object store to the HLM.

15 . The computer program product of claim 13 , wherein the HLM action includes a recall action including a movement of the object or group of objects from the HLM to an object store.

16 . The computer program product of claim 13 , wherein the request is received using an application programming interface (API).

17 . The computer program product of claim 13 , wherein the metadata includes a lock status indicator that indicates whether a lock is currently being held on the object or group of objects.

18 . The computer program product of claim 13 , wherein the metadata is selected from a group consisting of:
a timestamp indicating when a lock was acquired; an identifier of an entity that acquired the lock; a start timestamp indicating a time and date when the lock is to be acquired for the object or group of objects; a flag indicating that the lock for the object or group of objects needs to be acquired at a next possible non-conflicting time; a timespan for which the lock should be acquired; an end timestamp indicating a time and date when the lock is to be released for the object or group of objects; an indication of one or more actions to be performed on the object or group of objects during the lock; an indication of one or more actions to be prevented on the object or group of objects during the lock; and a user-defined comment section.

19 . The computer program product of claim 13 , wherein the metadata associated with the object or group of objects is identified from extended attributes of a file representation of the object or group of objects.

20 . A system, comprising:
a processor; and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor, the logic being configured to: receive a request to perform a high-latency media (HLM) action on an object or group of objects; identify metadata associated with the object or group of objects; and conditionally allow the HLM action to be performed on the object or group of objects, based o

Assignees

• IBM

Inventors

• Ngo Khanh V
• Lorenz Simon
• Mueller-Wicke Dominic
• Sarafijanovic Slavisa
• Seipp Harald
• Ishimoto Takeshi

Classifications

• G06F3/0649

  Lifecycle management · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F16/214

  Database migration support · CPC title

• G06F3/0685

  Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays · CPC title

• G06F3/0611

  in relation to response time · CPC title