US2016103719A1PendingUtilityA1

Automatic object model generation

Assignee: NETAPP INCPriority: Dec 16, 2013Filed: Dec 17, 2015Published: Apr 14, 2016
Est. expiryDec 16, 2033(~7.4 yrs left)· nominal 20-yr term from priority
G06F 11/3608G06F 9/547H04L 67/1097H04L 67/42H04L 67/01G06F 8/24G06F 11/3684G06F 11/3696
41
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A target device, such as a storage controller, may host an interface that manages objects, such as storage objects (e.g., logical unit numbers (LUNs), volumes, etc.), maintained by the storage controller. Accordingly, an object on the storage controller may be modeled as an object model, such as an object oriented library, based upon modeling information mined from the storage controller. The object model may be automatically generated, such as by discovering the interface to the object using available information in a command line interface (CLI) and/or an XML file (e.g., an XML help file). In this way, the object model may use hosted/exported interfaces to manage the object.

Claims

exact text as granted — not AI-modified
1 - 21 . (canceled) 
     
     
         22 . A method comprising:
 receiving, by a storage server, a command call for an object;   creating, by the storage server, an empty namespace package for the received object based on the command call;   identifying, by the storage server, based on the command call, modeling data associated with the object;   creating, by the storage server, an object model for the object based on the modeling data; and   populating, by the storage server, the empty namespace package with the object model to create a populated namespace package, wherein the populated object model comprises a definition associated with the command call.   
     
     
         23 . The method of  claim 22 , further comprising:
 parsing, by the storage server, an xml file associated with the received object, wherein the identifying the model data is based on the parsed xml file.   
     
     
         24 . The method of  claim 22 , further comprising:
 referencing, by the storage server, source tree data in an application on a target computing device, wherein the identifying the model data is based on the referenced source tree data.   
     
     
         25 . The method of  claim 24 , further comprising:
 receiving, by the storage server, a subsequent command call;   translating, by the storage server, based on the object model, the subsequent command call into a target application programming interface (API) format; and   invoking, by the storage server, the API on the target computing device based on the translated subsequent command call.   
     
     
         26 . The method of  claim 22 , further comprising:
 accessing, by the storage server, a remote computing device, wherein the remote computing device hosts an interface associated with the object and the identifying is further based on the interface associated with the object.   
     
     
         27 . The method of  claim 22 , wherein the object model is dynamically created at runtime. 
     
     
         28 . A computing device comprising:
 a memory containing a machine readable medium comprising machine executable code having stored thereon instructions for performing a method of generating an object model;   a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
 receive a command call for an object; 
 create an empty namespace package for the received object based on the command call; 
 identify, based on the command call, modeling data associated with the object; 
 create an object model for the object based on the modeling data; and 
 populate the empty namespace package with the object model to create a populated namespace package, wherein the populated object model comprises a definition associated with the command call. 
   
     
     
         29 . The device of  claim 28 , wherein the processor is further configured to execute programmed instructions, which comprise the programmed instructions stored in the memory to:
 parse an xml file associated with the received object, wherein the identifying the model data is based on the parsed xml file.   
     
     
         30 . The device of  claim 28 , wherein the processor is further configured to execute programmed instructions, which comprise the programmed instructions stored in the memory to:
 reference source tree data in an application on a target computing device, wherein the identifying the model data is based on the referenced source tree data.   
     
     
         31 . The device of  claim 30 , wherein the processor is further configured to execute programmed instructions, which comprise the programmed instructions stored in the memory to:
 receive a subsequent command call;   translate, based on the object model, the subsequent command call into a target application programming interface (API) format; and   invoke the API on the target computing device based on the translated subsequent command call.   
     
     
         32 . The device of  claim 28 , wherein the processor is further configured to execute programmed instructions, which comprise the programmed instructions stored in the memory to:
 access a remote computing device, wherein the remote computing device hosts an interface associated with the object and the identifying is further based on the interface associated with the object.   
     
     
         33 . The device of  claim 28 , wherein the object model is dynamically created at runtime. 
     
     
         34 . A non-transitory machine readable medium having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine, causes the machine to:
 receive a command call for an object;   create an empty namespace package for the received object based on the command call;   identify, based on the command call, modeling data associated with the object;   create an object model for the object based on the modeling data; and   populate the empty namespace package with the object model to create a populated namespace package, wherein the populated object model comprises a definition associated with the command call.   
     
     
         35 . The medium of  claim 34 , further having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine causes the machine to:
 parse an xml file associated with the received object, wherein the identifying the model data is based on the parsed xml file.   
     
     
         36 . The medium of  claim 34 , further having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine causes the machine to:
 reference source tree data in an application on a target computing device, wherein the identifying the model data is based on the referenced source tree data.   
     
     
         37 . The medium of  claim 36 , further having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine causes the machine to:
 receive a subsequent command call;   translate, based on the object model, the subsequent command call into a target application programming interface (API) format; and   invoke the API on the target computing device based on the translated subsequent command call.   
     
     
         38 . The medium of  claim 34 , further having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine causes the machine to:
 access a remote computing device, wherein the remote computing device hosts an interface associated with the object and the identifying is further based on the interface associated with the object.   
     
     
         39 . The medium of  claim 34 , wherein the object model is dynamically created at runtime.

Join the waitlist — get patent alerts

Track US2016103719A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.