It is often the case that demands or requirements arise in which there is a need to implement a service on a target platform with resource pre-requisites. A problem often encountered in connection therewith is determining a feasible set of components, software and/or hardware, that are either present or are required to be present on the target platform to implement the requirement. Conventional efforts involve considerable manual effort. The time and effort involved is tremendous and tends to be highly error-prone for complex environments.
Broadly contemplated herein, in accordance with at least one presently preferred embodiment of the present invention, are systems and methods for resource identification. Preferably, this can be undertaken via modeling in which primary constraints include requirements and availability.
In summary, one aspect of the invention provides a system comprising: a resource identification tool having one or more processors and one or more modules executable by the one or more processors, the one or more modules comprising: computer program code configured to identify resources of a target platform which meet a predetermined functional requirement, via: modeling resource constraints relating to the functional requirement and the target platform; assigning the resource constraints into resource categories; determining additional resource constraints; and developing a resource map of resource alternatives for the functional requirement.
Another aspect of the invention provides a method comprising: identifying resources of a target platform which meet a predetermined functional requirement; said identifying comprising: modeling resource constraints relating to the functional requirement and the target platform; assigning the resource constraints into resource categories; determining additional resource constraints; and developing a resource map of resource alternatives for the functional requirement.
A further aspect of the invention provides a computer program product comprising: a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer program code configured to identify resources of a target platform which meet a predetermined functional requirement, via:
modeling resource constraints relating to the functional requirement and the target platform;
assigning the resource constraints into resource categories;
determining additional resource constraints; and
developing a resource map of resource alternatives for the functional requirement.
For a better understanding of exemplary embodiments of the invention, together with other and further features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying drawings, and the scope of the claimed embodiments of the invention will be pointed out in the appended claims.
It will be readily understood that the components of the embodiments of the invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations in addition to the described presently preferred embodiments. Thus, the following more detailed description of the embodiments of the invention, as represented in the figures, is not intended to limit the scope of the embodiments of the invention, as claimed, but is merely representative of selected presently preferred embodiments of the invention.
Reference throughout this specification to “one embodiment” or “an embodiment” (or the like) means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” or the like in various places throughout this specification are not necessarily all referring to the same embodiment.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the various embodiments of the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The illustrated embodiments of the invention will be best understood by reference to the drawings/figures. The following description is intended only by way of example and simply illustrates certain selected presently preferred embodiments of the invention as claimed herein.
Regarding the figures, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The description now turns to the figures and select, presently preferred embodiments of the invention will be described. The following description of various embodiments of the invention is presented to highlight certain aspects of the invention, and the scope of the claimed embodiments of the invention will be pointed out in the appended claims.
Referring now to
As shown in
PCI local bus 50 supports the attachment of a number of devices, including adapters and bridges. Among these devices is network adapter 66, which interfaces computer system 100 to a LAN, and graphics adapter 68, which interfaces computer system 100 to display 69. Communication on PCI local bus 50 is governed by local PCI controller 52, which is in turn coupled to non-volatile random access memory (NVRAM) 56 via memory bus 54. Local PCI controller 52 can be coupled to additional buses and devices via a second host bridge 60.
Computer system 100 further includes Industry Standard Architecture (ISA) bus 62, which is coupled to PCI local bus 50 by ISA bridge 64. Coupled to ISA bus 62 is an input/output (I/O) controller 70, which controls communication between computer system 100 and attached peripheral devices such as a as a keyboard, mouse, serial and parallel ports, etc. A disk controller 72 connects a disk drive 99 with PCI local bus 50. The USB Bus and USB Controller (not shown) are part of the Local PCI controller (52).
Preferably, there are broadly contemplated herein, in accordance with at least one presently preferred embodiment of the present invention, methods and arrangements for identifying a set of components (software and/or hardware) on a target platform which meets a given requirement, preferably subject to constraints on resource prerequisites, availability and alternatives. Such methods and arrangements can be implemented essentially on any suitable computer system, such as the one indicated at 100 in
By way of an illustrative and non-restrictive example, there may be a requirement to implement a web service wherein the resource requirements might be: webserver (Apache or Tomcat if Java is used; IIS if C++ is used), database (DB2 V9.1 or Oracle 10), XML Parser (xerces), complier and run-time environment (JVM for Java) etc. At the same time, resource availability on the target platform might be: no JVM, Apache available, DB2 V8.1 available, etc.
It can be appreciated that if an effort is made to manually find a feasible set of components which satisfy a requirement (such as that just specified), a great deal of time and effort could be expended, and also be error-prone for complex environments. Accordingly, there is broadly contemplated herein a systematic approach with automation that reduces such time and effort, while the possibility of performing a feasibility check up-front is also accommodated.
Turning to
Constraints filter 214 will preferably act to pick up from database 206 solely those constraints which are applicable to the given target environment 208. A resource map builder 216, on the other hand, will preferably act to develop alternatives for a given requirement if not specified in the functional requirement input 202. (In other words, it is typically the case that there exist choices in terms of resources and/or implementations required for realization of the intended function. Thus, inasmuch as the functional requirement input 202 can typically represent a functional requirement desired by an end user, the resource map builder 216 can determine functional alternatives to that requirement. Sometimes if the end user requires certain resources of choice, such choices can be provided directly as input along with the functional requirement[s]). For example, the actual implementation of a web-service can be in the form of C code or Java code, and resource map builder 216 can preferably act to ascertain those alternatives.
Preferably, a resource resolution engine 218 will act to apply constraints (from filter 214) on the resource map builder 216 as would be applicable for target environment 208. For instance, if the target environment has “Java Runtime”, this availability can expressed as resource constraint and the resource resolution engine 218 will determine all Java-based resources for execution.
Finally, output from the resource resolution engine 218 could indicate whether the requirement(s) in question (202) for the target environment 208 indeed can be met (220) or will output a set of components 222 that would be needed in order for the target environment 208 to meet the requirement(s) 202.
With respect to the target environment 208, a target resource discovery adapter 210 will preferably act to determine what would be the specific resources that can either represent a subset or whole set of the requirements available on the target machine. The availability and non-availability of resources on the target machines can thusly be modeled as constraints. This will assist a target platform resource analyzer 212 with determining which resources already exist at the target environment 208, which information can be provided to the resource map builder 216 to carry out its function as discussed above.
To review and further elaborate upon various aspects of at least one presently preferred embodiment of the present invention, first it will be appreciated that a functional requirement 202 may be gathered from an end user. This may simply be as abstract as specifying an end requirement without details of implementation or of resources required for realization.
Therefore, a functional decomposition module 204 preferably acts to break the function into requirements in terms of resources or usable implementation platforms. The requirements can thus be a toolkit or platform and therefore a functional classifier inherent in the module 204 preferably is employed to identify the domain or category into which each requirement would fall. For instance, a run time might be required for execution of certain components.
For a certain resource, there might exist several constraints that would have an impact on deployment issues. For instance, a simple constraint could be as follows “Db2 version 5 cannot co-exist with Web Server 3.2”. This preferably will represent prior knowledge, in the form of constraint information, that is available from and included in the repository (or database) 206. In similar manner, knowledge of specific categorization (or classification) of resources can be preestablished to assist in determining which resources belongs to which categories. Thus, such information again can be made available in repository 206.
Preferably, resource map builder 216 will act to provide or determine information about which resources are available for which functions. On the other hand, the target environment 208 may preferably be scanned for available resources via target resource discovery adapter 210. For its part, target platform resource analyzer 212 may preferably act to analyze, from resources as indicated and input by adapter 210, the categories to which different resources belong (analogously to the function of the functional classifier of module 204 as discussed hereinabove).
As can be seen, target machine resources and information on functional requirements are preferably fed as separate streams of information into a “core” or “hub” that includes constraints filter 214, resource map builder 216 and resource resolution engine 218. The resource map builder 216 may build a resource map. The resultant resource map preferably will indicate which (if any) components, falling under which categories, can be used for realizing the implementation of requested functional requirements on the target platform. While the target machine might not have the exact components that would be required by the implementation, the resource resolution engine 218 preferably resolves to apply a best fit of resources on the target environment (or machine) 208 machine that can be employed while taking the resource map into account. The output of this resolution by resource resolution engine 218 preferably will either be an indication that the function can be realized (220) or an indication of one or more components that the target machine 208 would need to take on for implementation.
As will be appreciated by one skilled in the art, aspects of the invention may be embodied as a system, method or computer program product. Accordingly, aspects of the invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer (device), partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
This disclosure has been presented for purposes of illustration and description but is not intended to be exhaustive or limiting. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments were chosen and described in order to explain principles and practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Although illustrative embodiments of the invention have been described herein with reference to the accompanying drawings, it is to be understood that the embodiments of the invention are not limited to those precise embodiments, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the disclosure.
Number | Name | Date | Kind |
---|---|---|---|
6249882 | Testardi | Jun 2001 | B1 |
6529950 | Lumelsky et al. | Mar 2003 | B1 |
6968533 | Ueda et al. | Nov 2005 | B1 |
7137100 | Iborra et al. | Nov 2006 | B2 |
7233956 | Balducci et al. | Jun 2007 | B2 |
7448022 | Ram | Nov 2008 | B1 |
7509610 | New | Mar 2009 | B1 |
7546577 | Do et al. | Jun 2009 | B2 |
7606250 | Shoham et al. | Oct 2009 | B2 |
7676552 | Eilam et al. | Mar 2010 | B2 |
7693983 | Gupta | Apr 2010 | B1 |
7702779 | Gupta et al. | Apr 2010 | B1 |
7849459 | Burkhart et al. | Dec 2010 | B2 |
7899694 | Marshall et al. | Mar 2011 | B1 |
7992031 | Chavda et al. | Aug 2011 | B2 |
8042098 | Do et al. | Oct 2011 | B2 |
8073799 | Baldwin et al. | Dec 2011 | B2 |
8151248 | Butler et al. | Apr 2012 | B1 |
8209211 | Engle et al. | Jun 2012 | B2 |
9734228 | Barrett | Aug 2017 | B2 |
20020046394 | Do et al. | Apr 2002 | A1 |
20020170042 | Do et al. | Nov 2002 | A1 |
20030084135 | Narain | May 2003 | A1 |
20030216951 | Ginis et al. | Nov 2003 | A1 |
20040139088 | Mandato | Jul 2004 | A1 |
20040158567 | Dettinger et al. | Aug 2004 | A1 |
20040158577 | Chu et al. | Aug 2004 | A1 |
20050021847 | Rothman et al. | Jan 2005 | A1 |
20050120344 | Asare et al. | Jun 2005 | A1 |
20050120347 | Asare et al. | Jun 2005 | A1 |
20050136939 | Mountain et al. | Jun 2005 | A1 |
20050177600 | Eilam et al. | Aug 2005 | A1 |
20050198244 | Eilam et al. | Sep 2005 | A1 |
20050261884 | Sakamoto et al. | Nov 2005 | A1 |
20050278718 | Griffith et al. | Dec 2005 | A1 |
20060101453 | Burkhart et al. | May 2006 | A1 |
20060106585 | Brown et al. | May 2006 | A1 |
20060161910 | Bonsteel et al. | Jul 2006 | A1 |
20060212540 | Chon et al. | Sep 2006 | A1 |
20060221823 | Shoham et al. | Oct 2006 | A1 |
20070006281 | Abhinkar et al. | Jan 2007 | A1 |
20070100987 | Aggarwal | May 2007 | A1 |
20070220241 | Rothman et al. | Sep 2007 | A1 |
20080126406 | Endabetla et al. | May 2008 | A1 |
20080172263 | Heyman | Jul 2008 | A1 |
20080201701 | Hofhansl et al. | Aug 2008 | A1 |
20080228503 | Buchheit | Sep 2008 | A1 |
20080244600 | Wong et al. | Oct 2008 | A1 |
20090031277 | McElvain | Jan 2009 | A1 |
20090086577 | Ledeczi et al. | Apr 2009 | A1 |
20090122706 | Alfano et al. | May 2009 | A1 |
20090249281 | Fritzsche et al. | Oct 2009 | A1 |
20090259682 | Baldwin et al. | Oct 2009 | A1 |
20090265206 | Friedlander et al. | Oct 2009 | A1 |
20090281770 | Yatko et al. | Nov 2009 | A1 |
20090307308 | Siegemund et al. | Dec 2009 | A1 |
20100070449 | Arnold et al. | Mar 2010 | A1 |
20100083212 | Fritzsche et al. | Apr 2010 | A1 |
20100122238 | Kannan et al. | May 2010 | A1 |
20100250316 | Channabasavaiah et al. | Sep 2010 | A1 |
20100333102 | Balasubramanian | Dec 2010 | A1 |
20110022879 | Chavda et al. | Jan 2011 | A1 |
20110099548 | Shen et al. | Apr 2011 | A1 |
20110138374 | Pal | Jun 2011 | A1 |
20110191748 | Kannan et al. | Aug 2011 | A1 |
20120166771 | Ringseth | Jun 2012 | A1 |
20140075357 | Flores | Mar 2014 | A1 |
20140130014 | Jensen | May 2014 | A1 |
Number | Date | Country | |
---|---|---|---|
20110106515 A1 | May 2011 | US |