Component services integration with dynamic constraint provisioning

• US 10,025,631 B2
• Filed: 08/28/2015
• Issued: 07/17/2018
• Est. Priority Date: 11/25/2014
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Darji, Mehul H., Foster, II, Clyde T., Kolla, Jhansi R., Kozhaya, Joseph N.
• Primary Examiner(s): GEORGANDELLIS, ANDREW C
• Application Number:
  US14/838,617
• Publication Number:
  US 20160147570A1
• Time in Patent Office: 1,054 Days
• Field of Search: 707E17005, 707737, 707E17089, 709217, 709226, 708 1
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/823 Prediction of resource usage
• CPC Class Codes: H04L 47/83 based on usage prediction

Abstract

Resource provisioning information links to resource provisioning information of at least one reusable component resource that satisfies at least a portion of user-specified resource development constraints of a new resource under development are identified within a resource provisioning-link registry. Using the identified resource provisioning information links, the resource provisioning information of the at least one reusable component resource is programmatically collected from at least one data provider repository that stores reusable resources and that publishes the resource provisioning information links to the resource provisioning-link registry. The programmatically-collected resource provisioning information of the at least one reusable component resource is analyzed. Based upon the analyzed programmatically-collected resource provisioning information of the at least one reusable component resource, a resource integration recommendation is provided that uses the at least one reusable component resource and that satisfies at least the portion of the user-specified resource development constraints of the new resource under development.

Claims

1. A method, comprising:

by a processor operative as part of a distributed resource development architectural platform;

establishing, responsive to receipt of user-specified resource development constraints of a new resource under development, a network connection to a resource provisioning-link registry that hosts resource provisioning information links to resource provisioning information of reusable component resources located within one or more resource repositories, where the resource provisioning information specifies (i) published resource instrumentation options that specify details of different public interfaces to different features provided by the reusable component resources and (ii) technical provisioning details related to reuse of the reusable component resources in newly-developed resources, where the published resource instrumentation options of one or more of the reusable component resources specify different classifications of resource application programming interfaces (APIs) for different classes of use of each of the respective one or more reusable component resources;

programmatically traversing the resource provisioning information links while collecting the resource provisioning information of at least one reusable component resource;

programmatically evaluating the published resource instrumentation options and the technical provisioning details specified within the programmatically-collected resource provisioning information of the at least one reusable component resource against the user-specified resource development constraints of the new resource under development;

providing, based upon the evaluation of the published resource instrumentation options and the technical provisioning details, a resource integration recommendation that details the published resource instrumentation options and the technical provisioning details related to provisioning the at least one reusable component resource and that satisfies at least a portion of the user-specified resource development constraints of the new resource under development;

retrieving, responsive to a user selection within a dynamically-constrained resource provisioning workspace of a reusable component resource and of one of a plurality of available resource APIs specified within the published resource instrumentation options as being provided by the selected reusable component resource, resource API information of the selected resource API from a resource repository that hosts the selected reusable component resource using a resource API information link specific to the selected resource API and hosted by the resource repository;

providing a resource instruction template that comprises user-enterable and available resource API options and parameter value options that facilitate provisioning of the selected resource API of the selected reusable component resource;

detecting user entry of resource API values of the selected resource API; and

applying the selected resource API and the entered resource API values of the selected reusable component resource within a resource processing stream to provision the selected resource API of the selected reusable component resource as part of the new resource under development.

2. The method of claim 1, further comprising the processor:

sending a resource constraint query to the resource provisioning-link registry that comprises the user-specified resource development constraints of the new resource under development; and

receiving a response from the resource provisioning-link registry that identifies one or more of the resource provisioning information links within the resource provisioning-link registry to the resource provisioning information of a respective one or more of the reusable component resources that satisfy at least the portion of the user-specified resource development constraints; and

where the processor programmatically traversing the resource provisioning information links comprises the processor programmatically traversing the one or more of resource provisioning information links identified within the response.

3. The method of claim 1, where the processor programmatically traversing the resource provisioning information links while collecting the resource provisioning information of the at least one reusable component resource, comprises the processor:

programmatically navigating the resource provisioning information links; and

retrieving from at least one resource repository, using the resource provisioning information links, the resource provisioning information of the at least one reusable component resource, where the technical resource provisioning details are selected from a group consisting of resource configuration details, resource utilization details, resource availability details, resource security details, and resource connectivity details of the each of the at least one reusable component resource.

4. The method of claim 1, where a part of the processor programmatically evaluating the published resource instrumentation options and the technical provisioning details specified within the programmatically-collected resource provisioning information of the at least one reusable component resource against the user-specified resource development constraints of the new resource under development comprises the processor:

performing a resource constraint comparison between the published resource instrumentation options specified within the programmatically-collected resource provisioning information of the at least one reusable component resource and the user-specified resource development constraints of the new resource under development; and

determining, based upon the resource constraint comparison, at least the portion of the user-specified resource development constraints of the new resource under development satisfied by at least one of the different features provided by the at least one reusable component resource as specified within the published resource instrumentation options.

5. The method of claim 1, further comprising the processor, responsive to providing the resource integration recommendation, iteratively refining the provided resource integration recommendation responsive to changes to the user-specified resource development constraints by a user.

6. The method of claim 1, further comprising the processor:

storing the new resource under development within one of the one or more resource repositories; and

publishing to the resource provisioning-link registry, responsive to detecting an indication to publish provisioning information about the new resource under development within the resource provisioning-link registry, new resource provisioning information links that specify a resource storage location and resource provisioning information of the new resource under development, where the resource provisioning information of the new resource under development further comprises a different resource application programming interface (API) link for each different resource API provided for different classes of use of the new resource under development, where the new resource under development is reusable as a managed component resource.