WO2018179101A1 - Cloud management system and cloud management method - Google Patents

Abstract

This cloud management system manages a cloud system which has computer resources and which provides computer resources and software to a plurality of groups. This cloud management system has a storage device which can store information, and a processor unit which comprises one or more processors connected to the storage device. The storage device stores time-series basic information for calculating an evaluation value for a predetermined evaluation index relating to the development efficiency of each group, and also stores time-series usage information relating to the usage of software by each group. The processor unit extracts one or more software programs contributing to the evaluation for the evaluation index on the basis of the time-series basic information and the time-series usage information stored by the storage device.

Description

Cloud management system and cloud management method

The present invention relates to a cloud management system that manages a cloud system that provides computer resources and software to a plurality of groups.

In recent years, cloud services (hereinafter referred to as “clouds”) that provide IT resources such as virtual servers (VMs), development environments or execution environments, and software as services via networks have been rapidly spreading.

When the cloud is classified according to the provision format, IaaS (Infrastructure as a Service) that provides a virtual server, PaaS (Platform as a Service) that provides a development environment or an execution environment, SaaS (Software as a Service) that provides software Etc.

For example, in PaaS, when there is a request from a cloud user, a provider providing PaaS provides an environment dedicated to the user (also referred to as an instance or the like) and an access path for connecting to the environment. To notify the user. The user who has received the notification is provided via the notified access route using a protocol such as HTTP (Hypertext Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), or SSH (Secure Shell). By connecting to the environment, the environment can be used. By using such a cloud, the user can use as many IT resources as necessary when necessary, and can reduce the time required for environment preparation.

On the other hand, in recent years, agile development and DevOps, which are new software development methods, are attracting attention. In these software development methods, unlike the conventional waterfall type development, a small number of software developers work closely together to repeat development, testing, and release (version upgrade) in a short period of time. The purpose of these development methods is to make it possible to respond quickly to the needs of the software to be developed.

In such new software development methods, PaaS is often used. By using PaaS, a developer who is a user can concentrate on development without taking time to prepare for the environment. Moreover, it is possible to flexibly combine and use tools for supporting development (tool software) in accordance with changes in the development status.

When developing software using PaaS, a development environment and an execution environment are prepared for each development team unit (sometimes called a group, for example, a project, a tenant, etc.). Here, the development environment is, for example, a chat that lubricates communication within the project, an instance of a development support tool for managing a project management that manages the progress / issues of the project, Java (registered trademark), Python, etc. An environment in which an instance of a development language is installed. In the following description, a tool that refers to a tool that supports development is referred to as a tool, and a tool that is installed for a project may be used as an instance.

Developers (users) belonging to a project can construct a development environment for a project by selecting a tool necessary for project development from a list (called a catalog) of tools (instances) that can be used in PaaS. The actual development can be performed by using the developed development environment.

In the development environment constructed in this way, for example, a KPI (Key Performance Indicator) is measured in order to measure whether development is being performed efficiently. The KPI includes, for example, the number of additions / modifications of source code (the number of commits) as an index of development activity and speed, the number of chat posts as an index of communication activity, and the like. According to such KPI, the developer can grasp whether or not the development is performed efficiently.

Such KPIs often depend on the tool being used. This is because there are cases where the intended use, tools with high affinity, and tools with low affinity are different for each tool. For this reason, if an appropriate tool is not selected as a tool to be used in the project, there is a possibility that the development efficiency may not be sufficiently improved or the development efficiency may be hindered.

For example, tools called Source (registered trademark) or Gitlab (registered trademark) are known as tools for managing source code. Gitlab has a function to manage the development process, while Github does not have this function. For this reason, in the case where Github is used, another tool having a function for managing the development process is required for efficient development.

In addition, when DevOps development is adopted, even if you start using the tool once, there is a lack of consideration of necessary functions, it does not match the development style in the project, and new functions are added to other tools that are not used When version upgrades are performed, the tools used are often changed.

For this reason, when building a development environment in PaaS, select an appropriate tool group (software group) to increase development efficiency, taking into account the purpose and purpose of the tool, the proficiency level of developers participating in the project, etc. It is important to do.

For example, Patent Literature 1 collects configuration values of a plurality of software that configures an integrated system from a configuration management database on a network and other software that configures other integrated systems that share a common cooperation mode, and the collected configuration values A technique is disclosed in which a regression model having a highly correlated component value is generated and an optimum value of software component values is calculated using the regression model.

JP 2013-131017 A

For example, according to the technique of Patent Document 1, in order to provide an optimal development environment configuration (for example, a tool group to be used), it is assumed that an appropriate development environment is set in the configuration management database. .

However, when a new software development method such as DevOps is used, the development environment is generally constructed by trial and error, and the development environment is changing daily. For this reason, the configuration of the latest development environment is not necessarily the optimal configuration. Therefore, it is difficult to ensure that an appropriate development environment is set in the configuration management database. In such a case, an optimal development environment configuration cannot be provided.

The present invention has been made in view of the above circumstances, and a purpose thereof is a technique capable of appropriately extracting software that contributes to the evaluation of a predetermined evaluation index from software provided to a plurality of groups. Is to provide.

In order to achieve the above object, a cloud management system according to one aspect has a computer resource and manages a cloud system that provides computer resources and software to a plurality of groups. The cloud management system includes a storage device that can store information, and a processor unit that is one or more processors connected to the storage device.

The storage device stores time-series basic information for calculating an evaluation value of a predetermined evaluation index related to development efficiency in each group, and time-series usage information regarding software usage in each group. .

The processor unit is configured to extract one or more pieces of software that contribute to the evaluation index evaluation based on time-series basic information and time-series usage information stored in the storage device.

According to the present invention, it is possible to appropriately extract one or more softwares that contribute to the evaluation of a predetermined evaluation index.

FIG. 1 is a diagram illustrating an outline of the first embodiment. FIG. 2 is an overall configuration diagram of the computer system according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of the tool management information according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of KPI acquisition method management information according to the first embodiment. FIG. 5 is a diagram illustrating a configuration example of project management information according to the first embodiment. FIG. 6 is a diagram illustrating a configuration example of configuration change history information according to the first embodiment. FIG. 7 is a diagram illustrating a configuration example of the KPI history information according to the first embodiment. FIG. 8 is a diagram illustrating a configuration example of access history information according to the first embodiment. FIG. 9 is a diagram illustrating a configuration example of KPI conversion method management information according to the first embodiment. FIG. 10 is a flowchart of the information acquisition process according to the first embodiment. FIG. 11 is a flowchart of the extraction process according to the first embodiment. FIG. 12 is a diagram illustrating an example of the environment construction screen according to the first embodiment. FIG. 13 is a diagram illustrating an example of a best practice display screen according to the first embodiment. FIG. 14 is a diagram illustrating a configuration example of KPI acquisition method management information according to the second embodiment. FIG. 15 is a flowchart of extraction processing according to the fourth embodiment.

Several embodiments will be described with reference to the drawings. The embodiments described below do not limit the invention according to the claims, and all the elements and combinations described in the embodiments are essential for the solution of the invention. Is not limited.

In the following description, AAA information is described as a table configuration, but AAA information may be expressed in any data structure.

In the following description, the “processor unit” includes one or more processors. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit). Each of the one or more processors may be a single core or a multi-core. The processor may include a hardware circuit that performs part or all of the processing.

Also, in the following description, “time” is expressed in units of year, month, day, hour, but the unit of time may be coarser or finer than that, or may be a different unit.

Hereinafter, Example 1 will be described.

First, an outline of the first embodiment will be described.

FIG. 1 is a diagram showing an outline of the first embodiment.

The computer system 1 according to the first embodiment acquires information from an execution system (PaaS) 300 in which a development environment (hereinafter simply referred to as a project) 310 of each project (group) operates, and each project 310 of the execution system 300, A best practice extraction system 500 that extracts best practices and a terminal 10 that displays a best practice display screen G300 (GUI) for presenting the best practices extracted by the best practice extraction system 500 to a user are provided.

The best practice extraction system 500 includes an information storage DB (database) 520 that stores information about each project 310, an information acquisition processing unit 510 that acquires information from the execution system 300 and stores the information in the information storage DB 520, and an information storage DB 520 And an extraction processing unit 530 that extracts a configuration (for example, a tool (software)) of a development environment appropriate for the requirement of the evaluation index using the information.

The information storage DB 520 stores KPI history information T500 acquired from an instance of each project 310, configuration change history information T600 of each project, and access history information T700 for each instance. The KPI history information T500, the configuration change history information T600, and the access history information T700 are all time series data.

Here, examples of KPI (basic information) stored in the KPI history information T500 include the number of commits (the number of user source code uploads to the instance that manages the source code), the number of posts to chat, or on the tool. The number of registered assignments and the number of closed tasks. Examples of information stored in the configuration change history information T600 include addition, deletion, and change of tool instances. An example of access to be stored in the access history information T700 is an HTTP or HTTPS request to a tool instance.

When the user designates an evaluation index for the evaluation index selection area G310 of the best practice display screen G300 at the terminal 10, the extraction processing unit 530 uses the data stored in the information storage DB 520 to configure an optimal configuration for the evaluation index. When one of the existing projects is searched and extracted and the best evaluation index is recorded, one or more tools estimated to be actually used in this project are extracted. Then, the extraction processing unit 530 displays the extraction result in the configuration display selection area G400 of the best practice display screen G300.

The extraction processing unit 530 includes, for example, KPI time-series data G531 related to a specified evaluation index and access history of one or more tools (tool A and tool B) used (used) in this project. The time series data G532 and G533 are compared. Then, for example, the extraction processing unit 530 determines that the tool (tool A) used (accessed in FIG. 1) was used when the best KPI was recorded, and was not accessed. A process of determining that the tool (tool B) is not used is performed, and a best practice display screen G300 having a configuration display selection area G400 including a list of tools determined to be used is displayed on the terminal 10 of the user.

The execution system 300 that provides an environment to each project allows the business operator to obtain the consent of the user in advance, so that the business operator can obtain information on the environment of each project 310 (for example, access history information and resource Since it is relatively easy to obtain information on use) across the board, the configuration is based on PaaS. The execution system 300 may be realized in other forms (IaaS, SaaS, etc.) as long as the information of each project can be acquired.

Next, Example 1 will be described in detail.

FIG. 2 is an overall configuration diagram of the computer system according to the first embodiment.

The computer system 1 includes a cloud system 100 that provides a cloud service, and a user terminal 10 that uses a project 310. A cloud system (hereinafter referred to as a cloud) 100 and a terminal 10 are connected via a network 20. The network 20 may be a LAN or a WAN.

The cloud 100 includes an execution system 300 that provides a project 310 that is an environment for operating an instance that is actually used by a user, and a management system 200 that provides a system for managing the project 310 to the user and the administrator. (An example of a cloud management system).

The management system 200 includes a plurality of servers 400 that are physical hardware. The plurality of servers 400 are connected via a network (not shown) in the management system 200. The server 400 includes a CPU 401 as an example of a processor, a memory 402 as an example of a storage device, an auxiliary storage device 403 as an example of a storage device, and a communication I / F 404. The communication I / F 404 is, for example, an interface such as a wired LAN card or a wireless LAN card, and another device (for example, the terminal 10 or another server 400 via the communication path (not shown) in the management system 200 or the network 20. ). The CPU 401 executes various processes according to programs stored in the memory 402 and / or the auxiliary storage device 403. The memory 402 is, for example, a RAM (RANDOM ACCESS MEMORY), and stores programs executed by the CPU 401 and necessary information. The auxiliary storage device 403 is, for example, a hard disk or a flash memory, and stores a program executed by the CPU 401 and data used by the CPU 401.

The management system 200 includes an I / F system 210, a best practice extraction system 500, and a configuration management system 220. The I / F system 210, the best practice extraction system 500, and the configuration management system 220 are realized using computer resources of a plurality of servers 400. That is, the CPU 401 of the plurality of servers 400 executes a program such as the memory 402, thereby realizing the I / F system 210, the best practice extraction system 500, and the configuration management system 220. Each of the I / F system 210, the best practice extraction system 500, and the configuration management system 220 may be realized by a plurality of servers 400 or may be realized by a single server 400, and server virtualization. It may be realized by a virtual server virtualized by technology.

The I / F system 210 provides a GUI or API for presenting information about the use of the cloud 100 to the user's terminal 10 or accepting a request from the user, or an operator's terminal (not shown). On the other hand, a GUI and an API for managing the cloud 100 are provided.

In response to a user request from the I / F system 210, the configuration management system 220 acquires processing for changing the configuration of the project 310 of the execution system 300 and various types of information of the execution system 300, and sends them to the I / F system 210. Processing, processing for acquiring and storing various information of the execution system 300, and the like are performed.

The best practice extraction system 500 includes an information acquisition processing unit 510, an information storage DB 520, and an extraction processing unit 530. The information acquisition processing unit 510 acquires various types of information from the configuration management system 220. The information storage DB 520 includes, for example, the memory 402 and / or the auxiliary storage device 403, and stores information acquired by the information acquisition processing unit 510. Specifically, the information storage DB 520 includes KPI history information T500, configuration change history information T600 that is an example of usage status information and setting status information, and access history information T700 that is an example of usage status information and operating status information. Is stored. Details of the information stored in the information storage DB 520 will be described later.

The extraction processing unit 530 performs processing for extracting one or more tools (software) contributing to the evaluation of a predetermined evaluation index based on the information stored in the information storage DB 520. For example, the extraction processing unit 530 extracts one or more tools used when the evaluation is the best for a predetermined evaluation index from the project 310. Specific configurations and processes of the information acquisition processing unit 510 and the extraction processing unit 530 will be described later.

FIG. 2 shows an example in which the best practice extraction system 500 is provided in the management system 200 of the cloud 100, but the best practice extraction system 500 is connected to the network 20 outside the management unit system 200. The server may be constructed on a server (not shown), and necessary information may be exchanged by communicating with the I / F system 210 via the network 20.

The execution system 300 includes one or more projects 310 that are environments provided to users. Similar to the management system 200, the execution system 300 includes a plurality of servers 400 that are physical hardware. The configuration of the server 400 is the same as that of the server 400 of the management system 200. In the execution system 300, the projects 310 are logically divided, and access control is performed to block access to the project 310 by users who do not belong to the project 310.

Next, various information related to the present embodiment will be described.

FIG. 3 is a diagram illustrating a configuration example of the tool management information according to the first embodiment.

Tool management information T100 is information for managing a list of tools that can be used in each project 310. The tool management information T100 is information held by the I / F system 210 or the configuration management system 220.

The tool management information T100 stores a record including fields of a tool name T110, an image ID T120, and a function flag T130 for each tool.

The tool name (tool name) is stored in the tool name T110. The tool name includes, for example, Github, Gitlab, which is software (tool) for managing source code, and Rocket. chat, Mattermost (registered trademark), and Redmin for managing the progress of a project. In the description of the present embodiment, not an actual tool name but a tool A, a tool B, or the like for convenience.

In the image ID T120, an ID (image ID) for identifying an image serving as a base for constructing an instance of the tool corresponding to the record is stored. In addition, information such as a path in which an image is stored may be stored in the image ID T120 instead of the image ID. In addition to the image ID, setting information necessary for creating an instance may be stored together with the image ID T120. Here, examples of the image include a set of disks and files, and a virtual server template. This image is managed so as to be identifiable by an image ID.

The function flag T130 is a field for managing the function of the tool, and includes, for example, fields of individual function flags T131, T132, T133,... For each of a plurality of functions. The individual function flag T131 or the like is associated with a function, and “1” is set when the tool corresponding to the record has the function, and when the function does not have the function. Is set to “0”. For example, the individual function flag T131 is associated with the code management function, the individual function flag T132 is associated with the assignment management function, and the individual function flag T133 is associated with the chat function.

For example, according to the second record in FIG. 3, tool B has an image ID of toolB. It can be seen that it has a code management function and a problem management function.

In FIG. 3, the tool management information T100 shows an example of managing a record corresponding to each tool. However, for example, a record corresponding to each version of the tool may be managed.

FIG. 4 is a diagram illustrating a configuration example of KPI acquisition method management information according to the first embodiment.

The KPI acquisition method management information T200 is information for managing the type of KPI and the acquisition method of each KPI. The KPI acquisition method management information T200 is information held by the information acquisition processing unit 510.

The KPI acquisition method management information T200 stores a record including fields of a KPI name T210, a target tool name T220, and an acquisition method T230. The KPI name T210 stores the name of the KPI (KPI name) corresponding to the record. The target tool name T220 stores the name of the tool (tool name) from which the KPI corresponding to the record is acquired. The tool name stored in the target tool name T220 corresponds to the tool name described in the tool name T110 of any record of the tool management information T100. The acquisition method T230 stores a method (acquisition method) for acquiring the KPI corresponding to the record. In the acquisition method T230, for example, the name of the program (program name) to be called to acquire the KPI is stored.

For example, in the top record in FIG. 4, the number of commits as an example of KPI can be acquired from Tool A, and func_toolA. It is shown that it can be acquired by calling a program called sh.

It should be noted that the KPI acquisition method management information T200 may be stored and managed in the information storage DB 520, or may be held by the configuration management system 220. When the configuration management system 220 holds the KPI acquisition method management information T200, the configuration management system 220 acquires KPI information using the acquisition method stored in the acquisition method T230, and the acquired information May be acquired by the information acquisition processing unit 510. In addition, an agent program that acquires KPI information in this tool and transmits it to the information acquisition processing unit 510 may be incorporated in each tool.

FIG. 5 is a diagram illustrating a configuration example of project management information according to the first embodiment.

The project management information T400 manages information on the project 310 existing in the execution system 300. The project management information T400 is information held by the extraction processing unit 530. The project management information T400 stores a record including fields of a project name T410, a usage T420, a start T430, an end T440, and a shared T450 for each project.

The project name T410 stores a project name (identifier). The usage of the project is stored in the usage T420. The usage of the project is the usage selected by the user at the start of the use of the project from the options predefined by the operator. Specific applications include, for example, “Web service development” for developing a Web service, “Analysis” for developing an analysis application, and the like. In addition, the application T420 may store names of development languages such as Java (registered trademark) and Python, and a list of frameworks using them, and development based on a development style such as a conventional waterfall model. Or information indicating whether the development is based on Agile, the development period, the skill level of the developer, or the like, or information freely designated by the user may be stored.

In the start T430, the start time of the project corresponding to the record is stored. In the end T440, the end time of the project corresponding to the record is stored. In the record of the project being used, a null value (Null) is stored at the end T440.

The shared T450 stores a flag indicating whether the project information (in this embodiment, the tool setting value, etc.) may be shared with users who do not belong to this project. For example, in the sharing T450, “Yes” is stored when information sharing with a user who does not belong to the project is possible, and “No” is stored when information sharing is impossible. The

For example, according to the first record of FIG. 5, the project whose project name T410 is Project-A is a project for the purpose of developing a Web service (value of usage T420), and the start of use is November 30, 2016. The date is 9 o'clock (value of start T430), and the end is 17:00 on December 31, 2016 (value of end T440). The contents of the project may be disclosed to other users who do not belong to the project (shared) It can be seen that the value of T450.

Note that the project management information T400 may be stored and managed in the information storage DB 520.

FIG. 6 is a diagram illustrating a configuration example of configuration change history information according to the first embodiment.

The configuration change history information T600 is information for managing a tool configuration change history for each project. The configuration change history information T600 is information held by the information storage DB 520. The configuration change history information T600 manages one or more records for each project. The record of the configuration change history information T600 includes fields of a project name T610, an instance ID T620, a tool name T630, a type T640, a time T650, and a setting value T660.

The project name is stored in the project name T610. The instance ID T620 stores an identifier (instance ID) for uniquely identifying the tool instance used in the project corresponding to the record in the execution system 300. The tool name T630 stores the name of the tool used in the project corresponding to the record. The type T640 stores the type of change related to the tool instance in the project corresponding to the record. Here, the types of changes related to the instance include, for example, use start (Start) indicating that the use of the tool instance is started, change (Change) indicating that the tool instance is changed, and use of the tool instance. There is an end (Stop) indicating that the process is ended.

In time T650, the time when the change occurred is stored. The setting value T660 stores information related to the setting value used at the time of change. In the setting value T660, for example, a path of a setting file in which the setting value is described in a predetermined format (for example, a format called yml) is stored. The setting file stores, for example, a list of variable names (key values) and their values. The information related to the setting stored in the setting value T660 may be a format other than a file, for example, a format in which a list of variable names and values is directly stored in each field of the setting value.

According to the configuration change history information T600, for example, in a project whose project name T610 is Project-A, tool A (instance ID is tool AA) and tool C (instance ID is tool CA) are set to 2016. It can be seen that the use started at 9 o'clock on December 1, and the use of the tool C (instance ID is tool CA) has ended at 17:00 on December 15, 2016. Also, the settings used by each tool are stored in the set value T660, toolA-a1. yml, toolC-a1. This can be grasped by referring to yml. Further, according to the configuration change history information T600, in the project that is Project-A, the use of the tool D (instance ID is the tool DA) is started on December 15, 2016 at 9:00 on December 15, 2016. Sometimes it can be seen that the settings have been changed.

FIG. 7 is a diagram illustrating a configuration example of the KPI history information according to the first embodiment.

The KPI history information T500 is information for managing one or more KPI values in each project in time series. The KPI history information T500 is information held in the information storage DB 520. The record of KPI history information T500 includes fields of project name T510, KPI name T520, instance ID T530, time T540, and value T550.

The project name is stored in the project name T510. The KPI name T520 stores the KPI name. The instance ID T530 stores the instance ID of the tool used in the project corresponding to the record. In time T540, the time when the value of KPI was acquired is stored. The value T550 stores the acquired KPI value.

According to the KPI history information T500, for example, in a project whose project name T510 is Project-A, a KPI (commit number) acquired from a tool whose instance ID is tool AA, and a tool whose instance ID is tool CA The time-series data (the time T540 and the value T550) regarding the KPI (number of chat posts) acquired from the above can be found. For example, in the project whose project name T510 is Project-A, the number of commits in the tool whose instance ID is tool AA is 10 times in one hour (value at time T540) from 9:00 on December 1, 2016 ( It can be seen that the value T550). In the example of the KPI history information T500 in FIG. 7, the KPI acquisition interval (sampling interval) is 1 hour, but the sampling interval may not be 1 hour. By referring to the configuration change history information T600, the tool name of the tool corresponding to the instance ID T530 of the KPI history information T500 can be grasped.

FIG. 8 is a diagram illustrating a configuration example of access history information according to the first embodiment.

The access history information T700 is information for managing information related to the history of access to each tool instance for each project, and is information stored in the information storage DB 520. In the access history information T700, one record is added for each access to one instance of the project. Here, the access means that an acquisition or setting request for information from a user or another tool is made to a certain tool instance by a predetermined communication protocol (HTTP or HTTPS). Therefore, when there is an access, it can be seen that an instance of the tool was used at that time. The information stored in the access history information T700 may be obtained from a router (not shown) provided in the execution system 300, or an agent is embedded in each tool instance and obtained from the agent. May be.

The record of the access history information T700 includes fields of a project name T710, an access destination instance ID T720, a time T730, and an access source T740. A project name is stored in the project name T710. The access destination instance ID T720 stores the instance ID of the access destination tool instance. The instance ID stored in the access destination instance ID T720 is one of the instance IDs stored in the instance ID T620 of the configuration change history information T600. Accessed time is stored in time T730. The access source T740 stores information (for example, user ID, instance ID, etc.) for identifying the access source that performed the access. In the present embodiment, for example, in the case of access from a user, the access source T740 stores information in which a user ID is added to the “USER:” tag, and the access from the tool instance. In this case, information in which an instance ID is added to the “TOOL:” tag is stored.

For example, according to the record in the first line, at a project whose project name T710 is Project-A, an instance whose access destination instance ID T720 is tool AA is at 0:05 on December 1, 2016 It can be seen that there is access from the user A1. Also, according to the record in the third line, in the project whose project name T710 is Project-A, another instance at 10:00 on December 1, 2016 for the instance whose access destination instance ID T720 is Tool AA It can be seen that (instance ID is tool CA) has been accessed. In the access history information T700, information regarding the communication protocol and communication contents in each access may be further held.

FIG. 9 is a diagram illustrating a configuration example of KPI conversion method management information according to the first embodiment.

The KPI conversion method management information T300 is information for managing the KPI corresponding to the evaluation index, the process for calculating the evaluation index, and the process for extracting the instance of the tool used. The KPI change method management information T300 is information held in a program that configures the extraction processing unit 530. The information storage DB 520 may hold the KPI change method management information T300.

The KPI conversion method management information T300 stores a record for each type of evaluation index. The record of the KPI conversion method management information T300 includes fields of an evaluation index T310, a reference KPI T320, a calculation process T330, and a relationship extraction process T340.

Evaluation index T310 stores an evaluation index as a requirement for evaluating the system. The reference KPI T320 stores an identifier of a KPI that is referred to in order to calculate an evaluation index corresponding to the record. The calculation process T330 stores information indicating the process for calculating the evaluation value of the evaluation index corresponding to the record (for example, the program name of the process for calculating the evaluation value). The program having the program name stored in the calculation process T330 is a program that realizes a part of the processing executed by the extraction processing unit 530. In the relationship extraction process T340, information (for example, the program name of the process to be extracted) indicating the process of extracting the tool actually used at the time corresponding to the evaluation value is stored. The program having the program name stored in the relationship extraction process T340 is a program that realizes a part of the process executed by the extraction processing unit 530.

One type of evaluation index stored in the evaluation index T310 is a total value of KPIs in a certain period. As such an evaluation index, there is a daily commit number that is a total value of the number of daily commits of a certain project, and a daily chat number of posts that is the total of the number of daily chat posts of a certain project. .

Day_commit. Stored in the calculation processing T330 of the record in the first row of the KPI conversion method management information T300. sh receives the input of the project name and the number of commits, refers to the record corresponding to the project name and the number of commits in the KPI history information T500, and calculates the number of daily commits from the start to the end of this project. This is the name of the program that outputs the best value (here, the value with the maximum number of daily commits) as the evaluation value.

Also, eval_day_commit. Stored in the relationship extraction process T340. sh is the name of a program that extracts a tool that contributed to the evaluation of the project calculated by the program stored in the calculation process T330 (that is, estimated to have been used). This eval_day_commit. The program indicated by sh is a list of tools that are determined to be used / unused by inputting the project name, KPI history information T500, configuration change history information T600, and access history information T700, and determining whether or not the tool is used. To output. By this processing, the tools actually used in the project can be appropriately extracted. As a result, it is possible to prevent the extraction of tools that are usable but not used.

Eval_day_commit. As an example of processing executed by the program indicated by sh, whether or not each tool has been accessed at the timing when the evaluation value (here, the maximum number of daily commits) is recorded (that is, the tool is added to the access history information T700). There is a process for determining whether or not the tool is used on the basis of whether or not a record indicating access is stored.

Also, eval_day_commit. As another example of the processing executed by the program indicated by sh, there is a tool having an evaluation function f (x, t) represented by the following expression (1) that is equal to or higher than a predetermined threshold or an evaluation function at the upper level. There is a process for determining that a tool is being used.

Here, t0 is the timing when the evaluation value is recorded, and A (x) (t) is the number of accesses at the time t of the instance whose instance ID is x.

Further, as another type of evaluation index T310, there are a total value and an average value of a period from the start to the end of the project. Examples of this kind of evaluation index include the total number of commits, the total number of chat posts, the average number of commits, and the average number of chat posts. The total number of commits is the total number of commits from the start to the end of the project, and the average number of commits is the total number of commits of the project divided by the period from the start to the end of the project.

The record on the second line of the KPI conversion method management information T300 is a record when the evaluation index is the average commit count. In this record calculation process T330, ave_commit. The program indicated by sh implements a process of inputting a project name and KPI history information T500 and outputting an average value of the number of commits from the start to the end of the project as an evaluation value.

関係 eval_ave_commit. Of the relationship extraction processing T340 of this record. The program indicated by sh is a program that realizes a process of extracting a tool that contributed to the evaluation. The project name, KPI history information T500, configuration change history information T600, and access history information T700 are input to the KPI. It is determined that a tool having a positive correlation between the change in the tool and the access history of the tool (instance) is used, and processing for outputting a list of tools of the instance determined to be used is performed.

Also, eval_ave_commit. As another process executed by the program indicated by sh, a tool for an instance in which the average number of accesses is a certain value or more, an instance in which the total number of accesses is more than a certain value, or an instance that is regularly accessed There is a process to output a list of tools determined to be used.

In the case of such an evaluation index, a project that has not been completed may be excluded from the target, or the process may be performed using values up to the time when the process is performed. .

Next, processing operations in the computer system 1 will be described.

First, information acquisition processing by the information acquisition processing unit 510 will be described.

FIG. 10 is a flowchart of the information acquisition process according to the first embodiment.

The information acquisition process is executed at regular intervals, for example. The information acquisition process may be executed in response to a change from the configuration management system 220 or an event occurrence notification.

The information acquisition processing unit 510 receives various information required from the configuration management system 220 (information stored in each field of the project management information T400, information stored in each field of the KPI history information T500, and each field of the configuration change history information T600. (Information stored in each field of the access history information T700, etc.) are acquired (S100). Here, when acquiring information related to the KPI, the information can be acquired by calling and executing a program stored in the acquisition method T230 of the KPI acquisition method management information T200. In addition, without acquiring information from the configuration management system 220, for example, the information acquisition processing unit 510 may acquire necessary information by directly accessing an instance of the project 310. Necessary information may be acquired from an agent program incorporated in the instance in advance.

Next, the information acquisition processing unit 510 stores the KPI history information T500, the configuration change history information T600, and the access history information T700 in the information storage DB 520 based on the acquired information (S110). In step S100, when only the information of the difference from the information acquired in the past is acquired, the information acquisition processing unit 510, based on the acquired difference information, the KPI history of the information storage DB 520 Records corresponding to difference information are added to information T500, configuration change history information T600, and access history information T700, respectively.

Next, extraction processing by the extraction processing unit 530 will be described.

FIG. 11 is a flowchart of the extraction process according to the first embodiment.

The extraction process is executed at regular intervals, for example.

First, the extraction processing unit 530 refers to the project management information T400 and classifies the projects for each usage of the usage T420 (S200). Note that step S200 may be omitted if it is not necessary to classify the project by application.

Next, the extraction processing unit 530 performs the processing of loop A (loop B, S210 to S230) with each usage of each usage classified in step S200 as a processing target. Hereinafter, in the description of the extraction process, the usage to be processed is referred to as a target usage.

In the process of Loop A, the extraction processing unit 530 performs processing for each evaluation index of each evaluation index stored in the evaluation index T310 of the KPI conversion method management information T300 as a processing target for the target usage project group. The processes (S210 to S230) are performed. Hereinafter, in the description of the extraction process, the evaluation index to be processed is referred to as a target evaluation index.

In the process of loop B, the extraction processing unit 530 receives each record of the KPI history information T500 as an input and receives the program name stored in the calculation process T330 of the record corresponding to the target evaluation index of the KPI conversion method management information T300. By executing the program processing, the evaluation value (for example, the maximum number of daily commits, the average number of commits, etc.) of each project is calculated (S210).

Next, the extraction processing unit 530 has the highest evaluation index evaluation among a plurality of projects (for example, if the evaluation value is higher as the value is higher, the project having the highest evaluation value: high efficiency group). Is selected (S220).

Next, the extraction processing unit 530 receives the selected project, the KPI history information T500, the configuration change history information T600, and the access history information T700, and stores them in the record relation extraction processing T340 corresponding to the target evaluation index. List of tools that contributed to the evaluation in this project by executing the program processing of the program name (a tool that has a strong influence on the improvement of the evaluation value if the evaluation value indicates that the higher the value, the higher the evaluation) And the extraction result is stored in the memory 402, the auxiliary storage device 403, etc. (S230). Here, the extraction result may include a usage, an evaluation index, an evaluation value in the evaluation index, a path name of a setting value of the tool, and the like together with the extracted tool.

Then, the extraction processing unit 530 executes the processing of the loop B with all the evaluation indexes as processing targets, ends the processing with all the evaluation indexes as processing targets, and then exits the loop B. Next, the extraction processing unit 530 executes the process of Loop A with a project for an unprocessed application as a processing target, and finishes the processing with a project for all the applications as a processing target, and then performs extraction processing by exiting the loop A. finish.

Note that the above-described extraction process may be executed when a processing request is received from a user, that is, when a processing request from the terminal 10 is received. In this case, when an evaluation index is specified by the requester in the processing request, only the specified evaluation index may be processed in the loop B. Further, when processing is performed upon receiving a processing request from the user, the extracted tool is displayed in the configuration display selection area G400 of the best practice display screen G300 shown in FIG. You may make it perform the process which displays the list of.

In addition, the above-described extraction process is executed once at a certain timing, and after that, when a situation that may affect the processing result occurs (for example, when a project configuration change occurs or a calculation is performed) In the case where there is a possibility that the project having the best evaluation value calculated by the program of the process T330 may be changed, the process of only the affected part may be executed.

In the above-described example, in step S220, a list of tools used is acquired for one project having the best evaluation. However, the present invention is not limited to this. You may make it acquire the list of the tools currently used for each of these projects. In addition, when the evaluation of the tool (instance) can be calculated numerically as shown in the evaluation function f (x, t), for example, a list in which the numerical values calculated for each tool are normalized is associated. You may make it acquire.

Next, screens used in the computer system 1 will be described.

FIG. 12 is a diagram illustrating an example of an environment construction screen according to the first embodiment.

The environment construction screen G100 is a GUI used by the user when constructing a project development environment in the execution system 300. The environment construction screen G100 is a screen provided to the user terminal 10 by the I / F system 210, for example.

The environment construction screen G100 displays a list of tools that can be used, a table selection area G200 for displaying a table for accepting selection of a tool to be used, a use selection area G110 for selecting a use of a project, An agreement check box G120 for inputting whether or not to agree to share the development environment information of the constructed project with other users, and an instruction to construct a development environment corresponding to the current input An Apply button G130 for canceling, and a cancel button G140 for canceling an application for building a development environment corresponding to the current input.

In the table selection area G200, a tool name area G220 in which a list of selectable tool names is displayed, a check box G210 for specifying whether to use a tool with a tool name, and a classification of each tool are displayed. The classification display area G230 to be displayed is displayed. In the tool name area G220, the tool name stored in the tool name T110 of the tool management information T100 is displayed.

In this environment construction screen G100, the usage selected in the usage selection area G110 is reflected in the usage stored in the usage T420 of the project management information T400, and the check result for the consent check box G120 is reflected in the value of the shared T450. The Rukoto.

Note that the usage input area G110 and the consent check box G120 may not be displayed on the environment construction screen G100. In this case, the usage may be a default value, and the sharing selection may be a default value (uniformly agree to share or disagree to share).

FIG. 13 is a diagram illustrating an example of a best practice display screen according to the first embodiment.

The best practice display screen G300 is a GUI for receiving a request from a user and providing a configuration (best practice) most suitable for the project development environment. The best practice display screen G300 is a screen provided to the user's terminal 10 via the I / F system 210, for example.

The best practice display screen G300 displays an evaluation index selection area G310 that accepts selection of an evaluation index, and displays the best configuration in the table format in the evaluation index selected in the evaluation index selection area G310, and selects a configuration to be constructed Configuration display selection area G400, a construction button G320 that accepts an instruction to construct a system of the project 310, and a Close button G330 that accepts an instruction to close the best practice display screen G300.

The evaluation index selection area G310 is displayed so that each evaluation index stored in the evaluation index T310 of the KPI conversion method management information T300 can be selected in the form of a combo box. When an evaluation index is selected in the evaluation index selection area G310, information on the selected evaluation index is transmitted to the extraction processing unit 530 of the best practice extraction system 500 via the I / F system 210.

In the configuration display selection area G400, the configuration candidates of the development environment that gives the highest evaluation of the evaluation index selected in the evaluation index selection area G310 are displayed for each use. If no evaluation index is selected in the evaluation index selection area G310, nothing is displayed.

In the configuration display selection area G400, a usage display area G420, an evaluation value display area G430, a tool display area G440, a set value display area G450, and a radio button G410 are displayed.

The usage is displayed in the usage display area G420. In the tool display area G440, a tool name with a high evaluation is displayed. In the evaluation value display area G430, evaluation values for the tools displayed in the tool display area G440 are displayed. The setting value display area G450 displays a path name of a setting file in which setting values for tools by other users are stored. If other users have not agreed to share the setting values for the tool, no path name is displayed in the setting value display area G450. The setting content may be displayed when the path name in the setting value display area G450 is selected by the user.

The radio button G410 is a button for selecting a configuration to be constructed from the configuration display selection area G400.

When the configuration to be constructed is selected by the radio button G410, when the construction button G320 is pressed, the selected configuration content (use, selected tool name, etc.) is executed via the I / F system 210. Sent to system 300. The execution system 300 constructs an environment for a new project 310 based on the transmitted configuration contents. At this time, if the other user has agreed to share the setting file of another user corresponding to the tool included in the configuration content, the execution system 300 stores the setting file of the other user. Duplicate and set the tools for the project 310.

Here, an evaluation index is selected in the evaluation index selection area G310, and information on the selected evaluation index is transmitted to the extraction processing unit 530 of the best practice extraction system 500 via the I / F system 210, and then the configuration display is performed. A process until the candidate for the configuration of the development environment that gives the highest evaluation of the evaluation index selected in the evaluation index selection area G310 is displayed for each use in the selection area G400 will be described.

Upon receiving the information on the selected evaluation index, the extraction processing unit 530 selects tool information corresponding to the received evaluation index from the processing results of the extraction process stored in the memory 402 or the auxiliary storage device 403. The usage, evaluation value and setting value corresponding to the selected tool are specified, the specified usage is displayed in the usage display area G420, the tool name is displayed in the tool display area G440, and the setting value is displayed in the setting value display area. An instruction is transmitted to the I / F system 210 so as to be displayed on the G450 and to display the evaluation value in the evaluation value display area G430. As a result, the I / F system 210 displays the usage display area G420, the tool display area G440, the setting value display area G450, and the evaluation value display area G430 in the configuration display selection area G400 on the best practice display screen G300 to be displayed on the terminal 10. Display the contents according to the instructions.

In the best practice display screen G300 shown in FIG. 13, the configuration of one project is displayed for each application. However, the present invention is not limited to this, and a plurality of configurations with higher evaluations for one application are displayed. You may make it display. Further, in the best practice display screen G300, only the tools determined to be used are displayed. However, when the relationship extraction processing unit 530 calculates the evaluation numerically, For all tools used in the project, the evaluation values may be displayed in association with the normalized values.

Next, Example 2 will be described.

In the second embodiment, the tool, the function of the tool, and the evaluation index are managed, and the function of the tool that contributes to the evaluation index evaluation can be provided to the user.

FIG. 14 is a diagram illustrating a configuration example of KPI acquisition method management information according to the second embodiment. In addition, the same code | symbol is attached | subjected to the structure similar to FIG.

The best practice extraction system 500 according to the second embodiment includes KPI acquisition management information T800 instead of the KPI acquisition method management information T200 according to the first embodiment illustrated in FIG.

The record of KPI acquisition management information T800 is a record in which the field of function T810 is added to the record of KPI acquisition method management information T200. The function T810 stores a function of a tool that can acquire a KPI corresponding to a record. With such a configuration, it is possible to grasp from which function of the tool the KPI with the KPI name T210 can be acquired.

Here, the problem management function is possessed by Tool A, Tool B, and Tool E as set in the function flag T130 of the tool management information T100. According to this KPI acquisition method management information T800, the number of closed issues of the KPI name T210 can be acquired from the issue management function (value of function T810), and the tool having the issue management function is stored in the target tool name T220. It can be seen that Tool A, Tool B, and Tool E are present.

In such a configuration, the extraction processing unit 530 stores an extraction result in which the function of the tool is associated with the extracted tool in S230 of the extraction processing illustrated in FIG. Then, the extraction processing unit 530 instructs the I / F system 210 to display the function of the tool in the configuration display selection area G400 of the best practice display screen G300 illustrated in FIG. Thereby, the user can grasp | ascertain also the function of the tool which contributes to evaluation of an evaluation parameter | index with reference to the best practice display screen G300.

Next, Example 3 will be described.

In the first embodiment, an example in which the access history information T700 is used to determine the use / non-use of the tool is shown. However, in the third embodiment, use / non-use of the tool is performed using information different from the access history information T700. The use is determined.

In this embodiment, the information acquisition processing unit 510 uses the computer resources (at least one of CPU usage and memory usage) allocated to each tool in the execution system 300 when this tool is not used. (Usage when not in use) is acquired and stored in advance. When determining whether the project instance is used or not used, the extraction processing unit 530 acquires the usage amount (current usage amount) of the computer resource allocated to the instance at that time from the execution system 300 or the like. When the difference between the current usage amount and the usage amount when not in use is equal to or less than a predetermined value, the tool is determined not to be used, and when the difference exceeds a predetermined value, the tool is determined to be used. Thereby, it is possible to appropriately determine whether the tool is used or not, regardless of the access history information T700.

Instead of the above, the use / non-use of the tool may be determined as follows. That is, the information acquisition processing unit 510 acquires the contents of the log and the amount of log output in the execution system 300 when each tool is not used. When the extraction processing unit 530 determines use / non-use of a project instance, the extraction processing unit 530 collects a log of the instance at that time, and outputs a log having contents different from the log when the project is not used. And the difference between the number of logs output and the amount of log output when not in use, based on one of these, the use / non-use of an instance (tool) is determined.

Next, Example 4 will be described. The description will focus on differences from the first to third embodiments.

In Examples 1 to 3 described above, the extraction of the relationship between the evaluation index and the use / non-use of the tool in the project was determined using only the information in the project. In the fourth embodiment, the relationship between the evaluation index and the contribution of the tool is learned based on various information of a plurality of projects operated in the execution system 300, and the learning result is used.

The extraction processing unit 530 of this embodiment includes a learning module inside. The learning module is a module that performs machine learning using past history information as teacher information and performs processing according to the learning result. As a module for performing such machine learning, there are a module constituted by a neural network, a support vector machine, and the like.

In the fourth embodiment, the extraction processing unit 530 replaces the processing of the program stored in the calculation processing T330 of the KPI conversion method management information T300 and the relationship extraction processing T340 with the processing by the learning module. It is.

FIG. 15 is a flowchart of extraction processing according to the fourth embodiment. In addition, about the process similar to FIG. 11, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

Extraction processing unit 530 performs processing of loop C (loops D and S250) for each usage of each usage classified in step S200. Hereinafter, in the description of the extraction process, the usage to be processed is referred to as a target usage.

In the processing of loop C, the extraction processing unit 530 performs processing for each evaluation index of each evaluation index stored in the evaluation index T310 of the KPI conversion method management information T300 for the target usage project group. The process (S240) is performed. Hereinafter, in the description of the extraction process, the evaluation index to be processed is referred to as a target evaluation index.

In the process of loop D, the extraction processing unit 530 learns information of a plurality of fields among all fields of the KPI history information T500, the configuration change history information T600, and the access history information T700 of each project as teacher information. Input into the module, and learn the relationship between the change in the project configuration, access to the tool, and the change in KPI (S240). Here, with respect to the KPI history information T500, only the record information related to the KPI related to the target evaluation index (reference KPI T320 of the KPI conversion method management information T300 corresponding to the target evaluation index) is set as an input target. Note that the input unit for the configuration change history information T600 includes the variable name of the setting value (setting value T660) and its value (for example, addition of variables) in addition to the information about the start / end of the use of the tool (type T640 and time T650). Or deletion or value change).

Then, the extraction processing unit 530 executes the processing of the loop D with all the evaluation indexes as processing targets, ends the processing with all the evaluation indexes as processing targets, and then exits the loop D.

Next, the extraction processing unit 530 acquires a tool that contributes to the target evaluation index by the learning module, and includes a result including the tool name of the acquired tool (for example, a use, an evaluation index, a path name of a setting value of the tool, and the like). (May be included) in the memory 402, the auxiliary storage device 403, etc. (S250).

Next, the extraction processing unit 530 executes the process of loop C with a project for an unprocessed application as a processing target, finishes the processing with all projects for a usage as a processing target, and then exits the loop C and performs an extraction process. finish. Note that the extraction processing unit 530 immediately after the extraction processing. The result stored in step S250 may be displayed in the configuration display selection area G400 of the best practice display screen G300.

Note that the learning module may be trained by inputting only the fields of the KPI history information T500 and the configuration change history information T600 without inputting the fields of the access history information T700.

By performing such processing, in the execution system 300 in which a plurality of projects operate, a certain setting or configuration change Y is performed for a certain evaluation index X in many projects, and then the evaluation index X is calculated. It is also possible for the learning module to catch an event where the value of the KPI Z used is increasing. For this reason, the information that the setting or configuration change Y contributes to the evaluation index X can be presented to the user.

It should be noted that the present invention is not limited to the above-described embodiments, and can be appropriately modified and implemented without departing from the spirit of the present invention.

For example, in the above-described embodiment, an example in which the management system 200 is configured in the cloud system 100 has been shown. However, the present invention is not limited to this, and at least a part of the functions of the management system 200 is provided outside the cloud system 100. You may make it comprise with an apparatus (server etc.).

In the above embodiment, part or all of the processing performed by the CPU may be performed by a hardware circuit. Moreover, the program in the said Example may be installed from a program source. The program source may be a program distribution server or a storage medium (for example, a portable storage medium).

DESCRIPTION OF SYMBOLS 1 ... Computer system, 10 ... Terminal, 100 ... Cloud system, 200 ... Management system, 300 ... Execution system, 400 ... Server, 401 ... CPU, 402 ... Memory, 403 ... Auxiliary storage device, 404 ... Communication I / F

Claims (15)

1. A cloud management system for managing a cloud system having computer resources and providing the computer resources and software to a plurality of groups,
   A storage device capable of storing information, and a processor unit that is one or more processors connected to the storage device,
   The storage device is
   Storing time-series basic information for calculating an evaluation value of a predetermined evaluation index relating to development efficiency in each of the groups, and time-series usage information regarding software usage in each of the groups,
   The processor unit is
   A cloud management system configured to extract one or more software that contributes to the evaluation of the evaluation index based on the time-series basic information and the time-series usage status information stored in the storage device.
2. The processor unit is
   Based on the basic information in time series, calculate the evaluation value for the evaluation index in each group, identify one or more highly efficient groups with high evaluation,
   The cloud management system according to claim 1, wherein one or more pieces of software that contribute to the evaluation are extracted from the high efficiency group based on the time-series use status information.
3. The processor unit is
   Accept selection of target metrics from multiple metrics,
   The cloud management system according to claim 2, wherein one or more software contributing to the evaluation is extracted for the received evaluation index.
4. The cloud management system according to claim 2, wherein the predetermined evaluation index includes a plurality of evaluation indices, and the processor unit extracts one or more pieces of software that contribute to the evaluation for each of the plurality of evaluation indices. .
5. 5. The usage status information includes time-series operating state information relating to the operating state of the software and time-series setting state information relating to creation, deletion, and change of the software in the group. The cloud management system according to any one of the above.
6. The cloud management system according to claim 5, wherein the operating state information is information related to an external access to the software.
7. The cloud management system according to claim 5, wherein the operating state information is information relating to a usage amount of a computer resource allocated to the software.
8. The cloud management system according to claim 5, wherein the operating state information is information relating to a log output by the software.
9. The evaluation value of the evaluation index includes a total value of the basic information in a predetermined time range,
   The processor unit is
   The cloud management system according to any one of claims 1 to 8, wherein a group having the maximum total value of the basic information in the predetermined time range is specified as a highly efficient group with high evaluation.
10. The processor unit is
    The one or more software used in the high efficiency group is extracted as one or more software contributing to the evaluation in a time range in which the total value of basic information in the predetermined time range is maximum. Cloud management system.
11. The cloud management system according to any one of claims 1 to 10, wherein the processor unit and the storage device are the computer resources provided by the cloud system.
12. The processor unit is
    The cloud management system according to any one of claims 1 to 11, wherein information regarding the extracted one or more pieces of software is displayed.
13. The processor unit is
    Display a screen that accepts the designation of whether or not to share the software settings for the group with other users, accept the designation,
    13. The setting information related to the software is displayed when the display request for the setting value information related to the software is received when the designation that the software can be shared is accepted. The cloud management system described in 1.
14. The processor unit is
    Contributing to the evaluation of the evaluation index by executing a learning module in which machine learning is performed using the time-series basic information in a predetermined learning target group and the time-series information regarding the usage status of software as teacher information The cloud management system according to any one of claims 1 to 13, wherein one or more pieces of the software are extracted.
15. A cloud management method by a cloud management system for managing a cloud system having computer resources and providing the computer resources and software to a plurality of groups,
    Obtain basic time-series information for calculating the evaluation value of a predetermined evaluation index related to development efficiency in each of the groups,
    Obtain time series information about software usage in each of the groups,
    Based on the time-series basic information held by the basic information acquisition unit, calculate an evaluation value for the evaluation index in each group, identify the high-efficiency group with the highest evaluation,
    A cloud management method for extracting one or more software that contributed to the evaluation in the high-efficiency group based on time-series information about the usage status of the usage status information acquisition unit.

Images