FR3041448A1 - SYSTEM AND METHOD FOR AUTOMATICALLY STARTING AND STOPPING LIMITED LIFETIME SERVICES IN AN OPERATING SYSTEM - Google Patents

Abstract

The present invention relates to a system and a method for automatically launching and stopping services with a limited lifetime in an operating system, according to a deployment schedule of the aforesaid services previously parameterized with an orchestrator, but also for launching deferred from said services, when resources are momentarily insufficient to deploy said service at the scheduled time for deployment. The method also includes the step of sending an error signal in the form of a visual and / or audible alert to the system administrator, when it is verified that the resources available on all the nodes of the system. operating system are insufficient to deploy the service with limited life.

Description

The present invention relates to the technical field of cloud computing services.

In the state of the art, there are methods for programming the execution time of a service on a computer system (computing system).

Normally, these methods also have means to indicate whether a service is pending execution, to indicate an estimate of the length of time necessary to complete the execution of a service, how many resources are required to execute such a service. , among other information.

Still according to these methods, it is necessary to reserve, in the computer system, the amount of resources necessary for a service having a limited life can be executed. This reservation, however, entails the non-use of the resources available during the non-execution of a service of limited lifetime.

Although non-use of resources means a saving of resources, it also means unnecessary immobilization of resources. However, if the system administrator wishes to set up other services with a computer system, he will not be able to take into account the availability of resources during the non-execution of the services of limited lifetime, because in principle these resources are reserved.

To overcome this disadvantage, it is therefore necessary to set up means to ensure the deployment of services with limited life, without the need to reserve resources.

The present invention therefore aims to solve the technical problems mentioned above, by proposing a system and a method for automatically starting and stopping services with a limited lifetime in an operating system, but also to launch to new services, when the resources are momentarily insufficient to deploy said service at the scheduled time for deployment. Thus, when stopping a service, another service can be deployed with the same resources, and in case the schedule of two services coincide, a service will be launched at another time.

In addition, the method also allows the system administrator to avoid a sequence of delayed launches by analyzing a register of application traces, having information on the launch, stopping and / or delayed launch of said services.

Glossary:

The term "operating system" used in the present invention may be understood in a nonlimiting manner as "operating system", "datacenter", "node farm operating system" and / or a set of node (node farm) responding to certain principles and having at least one master and one to several slaves. The operating system, on its minimal form can thus consist of only one node. And it can also be made up of multiple nodes.

The term "limited lifetime services" used in the present invention may be understood in a nonlimiting manner such as "scheduled job scheduler", "job scheduler", "task scheduler", "cron service", "cron service".

The term "node" used in the present invention may be understood in a nonlimiting manner such as "virtual server, on the Internet", "virtual server, on cloud", "virtual server, on a cloud platform", "server on local infrastructure "," server networks "," cluster "," server farm "," nodes farm ".

The term "orchestrator" used in the present invention may be understood in a non-limiting manner such as "network services orchestration module", "content orchestration system", "automatic process of organization, coordination, and complex computer system management "," service management orchestration "or component of a node intended to launch and manage services with a limited lifetime, when ordering the shutdown, start and / or restart of a service, also as intended to control the service facilities, namely the updating of a registry.

The term "interface" used in the present invention may be understood in a nonlimiting manner as "graphical interface", "supervisory console" and / or "console (s) of administration (s)" or any other means of interaction between man and machine.

The term "application traces" used in the present invention may be understood in a nonlimiting manner such as logs or databases of the operating system.

Description of the invention

The present invention relates to a system and a method for automatically launching and stopping services with a limited lifetime in an operating system, according to a schedule for deploying the aforementioned services previously set up with an orchestrator, but also for launching deferred from such services, when the resources are momentarily insufficient to deploy said service at the scheduled time for deployment. The method also includes the step of sending an error signal in the form of a visual and / or audible alert to the system administrator, when it is verified that the resources available on all the nodes of the system. operating system is insufficient to deploy the service with limited lifetime.

Brief description of the drawings

The present invention is illustrated by a non-exhaustive list of examples accompanying figures in which the numerals indicate like elements as follows:

FIG. 1 represents the system for implementing the method for automatically starting and stopping services with a limited lifetime in an operating system (1). It comprises at least one node (2) and one orchestrator (3). The nodes (2) shown comprise various resources (4). This representation is an example and is not limiting in nature.

Figure 2 shows the action diagram illustrated by the parameterization process with the Orchestrator (3).

Figure 3 represents the diagram of action that illustrates the process of calculation of available resources (4) realized by the orchestrator (3).

FIG. 4 shows the sending of the error signals in the form of a visual and / or audible warning (5) to the system administrator. Such an alert (5) is displayed on an interface (6) administrator. This representation is an example and is not limiting in nature.

detailed description

With reference to FIG. 1, the system comprises means adapted for implementing the method for automatically starting and stopping services with a limited lifetime in an operating system (1).

The system according to the invention comprises at least one node (2) having means for deploying services with a limited lifetime, or also called scheduled tasks program. These nodes (2) can be physical and / or virtual.

Ideally, the nodes (2) of the operating system (1) comprise resources (4), namely, at least one random access memory (RAM) and / or at least one central processing unit (CPU) and / or less a hard disk (HDD). This list is an example and is not limiting in nature.

The system also includes an orchestrator (3). The orchestrator (3) can be contained in any node (2). Preferably, the orchestrator (3) is a component of the node (2) that has the most resources and weights. The orchestrator (3) is intended to order the stopping, launching and / or re-launching of a service with a limited lifetime or schedule scheduled tasks.

Commonly, the system comprises means for performing the settings with the orchestrator (3).

As for the method for automatically launching and stopping services with a limited lifetime in an operating system, it comprises several steps.

One of the first steps, illustrated in FIG. 2, consists in the prior parameterization of data and / or information with an orchestrator (3).

Preferably, the following are set up with the orchestrator (3): • information on a schedule for deploying services with a limited lifetime or program of scheduled tasks; Frequency information in that the Orchestrator (3) must perform calculations on the actual availability of the resources (4) on all the nodes (2) of the operating system; • the information on the required amount of resources (4) to deploy, each time, services with a limited lifetime. • Frequency information in that the Orchestrator (3) must perform a check between the actual availability of resources (4) and the required amount of resources (4) available to deploy, in each case, time-based services. life, to certify that there are sufficient resources (4) to deploy the requested service.

This list is an example only and does not have a limiting character: the prior configuration can relate to all of this information or at least one of this information, or other additional information.

The service deployment schedule, according to the invention, indicates the frequency and the periodicity during which the orchestrator (3) must launch and stop the so-called limited lifetime services.

The required amount of resources (4) for deploying, each time, the services with limited lifetime, according to the invention, indicates how many resources (4) [RAM and / or CPU (CPU ) and / or hard disk (HDD) and / or other resources, non-limiting list] each service needs to be deployed, each time, such a service is requested.

Referring to FIG. 3, the action diagram illustrates another step: the process of calculating the resources (4) available on all the nodes (2) of the operating system (1) made by the orchestrator ( 3). This process of calculating resources (4) available indicates the real availability of resources (4): for example, how much RAM is available, and / or how many CPUs available and / or how much hard disk (HDD) available, on all nodes (2) of the operating system (1) at a time T.

Advantageously, this calculation makes it possible to check whether the quantity of available resources (4) is sufficient, on one of the nodes (2) of the operating system (1), to deploy the service with a limited lifetime.

In parallel with the realization of the calculation of the resources (4) available, the orchestrator (3) realizes, according to the frequency previously parameterized, a check between the actual availability of resources (4) on one of the nodes (2) of the system. exploitation (1) and the necessary amount of resources (4) available to deploy, in each case, services with a limited lifetime.

This sub-step therefore indicates whether there are sufficient resources (4) available, on one of the nodes (2) of the operating system (1), to deploy the service with a limited lifetime.

Preferably, the calculations and verifications are performed by the orchestrator (3) each time before the launch of the services with a limited lifetime.

In one embodiment, when the service with limited lifetime will be deployed according to its schedule, the Orchestrator (3) performs, according to the frequency previously set, calculations and checks on resources (4).

If the result of the check indicates that on a node (2) of the operating system (1) there are resources (4) available sufficient to deploy the service with a limited lifetime, the Orchestrator (3) launches the said service. Once the service is deployed and / or executed according to the service deployment schedule, the Orchestrator (3) orders the shutdown.

If the result of the check indicates that on a node (2) of the operating system (1) there are not enough resources (4) available to deploy the service with a limited lifetime, the orchestrator (3) ) orders the deferred launch of the services. The service can be started in x milliseconds, x seconds, x minutes, or x hours, or any desired duration.

Preferably, the Orchestrator (3) orders the delayed launch of the services with a limited lifetime when the available resources (4) are momentarily insufficient to deploy said service at the time planned for the deployment. This is the case when the schedule of two services coincide, one of the two services will be launched at another time.

This mechanism allows the system administrator to configure the deployment of other services to a computer system during the non-execution of a service with a limited lifetime. Thus, when stopping a service, another service can be deployed with the same resources (4).

Ideally, the operating system (1) is also configured to accept the addition of a physical and / or virtual node (2) if the available resources (4) are insufficient to deploy the services with a limited lifetime. This is the case when a node (2) of the system has errors, failures or all the nodes (2) of the operating system (1) or has a number of resources (4) less than the necessary number to deploy all the services with a fixed lifetime set to the system.

When the service is launched later by the orchestrator (3), the process of calculation and verification is put in place. If this time, there are resources (4) available sufficient to deploy the limited lifetime service requested, the Orchestrator (3) starts the service. Once the service is deployed and / or executed according to the service deployment schedule, the Orchestrator (3) orders the shutdown.

In parallel with the delayed launch, with reference to FIG. 4, an error signal in the form of a visual and / or audible warning (5) is sent to the system administrator, in order to indicate the operating state thereof. of the system and find out if the system has errors and / or faults, and know what resources are available to schedule other executions at the same time.

Advantageously, this signal is generated when it is verified that the resources (4) available on a node (2) of the operating system (1) are insufficient to deploy the service with a limited lifetime.

Such an error signal in the form of an alert (5) is displayed on an interface (6). The interface (6) is also the means by which a system administrator realizes these settings and accesses a register of application traces, including but not limited to logs or databases of the operating system.

This mechanism allows the system administrator to avoid a sequence of delayed launches by the analysis of the generated alerts (5) but also by the analysis of the application traces register, having information on the launching, stopping and / or delayed launching of said services.

Application traces are the writing of a list of application events. These application traces, allow to know which service was postponed (delayed launch), and to see the history of launching and stopping of all services with limited lifespan.

As a consequence, the system administrator can rely on the analysis of alerts and application traces to set up with the Orchestrator (3) the information on a schedule of deployment of services with a limited lifetime or program of scheduled tasks.

Thus, the method according to the invention includes the step of traceability of the events, in order to list the stop orders, launch and / or delayed launch of the orchestrator (3).

Preferably, the limited lifetime service launched indicates traceability of events by means of storing execution traces.

The application traces of the launched service are presented and archived, through the aggregation, in a register of application traces, understood in a non-limiting way as logs or databases of the operating system (1).

The logs or databases of the operating system (1) present a final return code and system states at launch, during and at the end of execution.

Thus, the system and method according to the invention are particularly intended to set up means to ensure the deployment of services with a limited lifetime, without the need to reserve resources (4), so the resources are constantly used by the deployment of services, without needing to remain useless until the next launch.

Claims (9)

A method of automatically starting and stopping services with a limited lifetime in an operating system (1), characterized in that it comprises the following steps: a. Prior configuration with an orchestrator (3): i. a roll-out schedule for limited-life services or a schedule of scheduled tasks; ii. a frequency for performing a check and resource calculations (4) available on all nodes (2) of the operating system (1); iii. a necessary amount of resources (4) available to deploy, each time, services with limited life. b. Calculation of the resources (4) available by the Orchestrator to verify if there are sufficient resources (4) available to deploy the service with a limited lifetime; vs. Launching and stopping services with limited lifespan by the Orchestrator (3), according to the calendar set. 2. Method according to claim 1, characterized in that the service deployment schedule indicates the frequency and periodicity during which the Orchestrator (3) must perform the launch and stop of said services with limited life. 3. Method according to claim 1, characterized in that are carried out by the orchestrator (3) each time before the launch of the services with limited lifetime: a. the calculation of available resources (4) b. the verification of available resources (4) sufficient to deploy the said service. 4. Method according to claim 1, characterized in that an error signal in the form of alert (5) visual and / or sound is sent to the system administrator when it is verified that the resources (4) available on all nodes (2) of the operating system (1) are insufficient to deploy the service with limited lifetime. 5. Method according to claim 1, characterized in that the Orchestrator (3) launches the delayed launch of the services with limited lifetime when the resources (4) available are momentarily insufficient to deploy said service at the time planned for the deployment. 6. Method according to claim 1, characterized in that the limited lifetime service launched indicates traceability of events by means of storing execution traces. 7. Method according to claims 1 and 6, characterized in that the application traces of the launched service are presented and archived, through the aggregation, in a register of application traces, understood in a non-limiting manner as logs or bases operating system data (1). 8. Method according to claims 1, 6 and 7, characterized in that the logs or databases of the operating system (1) have a final return code and system states, at launch, during and at the end of execution. 9. Operating system for carrying out the method according to claim 1, characterized in that it comprises: a. at least one node (2) having means for deploying services with a limited lifetime or schedule scheduled tasks; b. an orchestrator (3) component of the node (2) which has the most resources (4) and weight and intended to order the stopping, launching and / or delayed launching of a service with a limited lifetime, or schedule of planned tasks; vs. means for carrying out the settings with the orchestrator (3); d. at least one interface (6) for displaying the error signals in the form of a visual and / or audible alert (5) sent to the system administrator when it is verified that the resources (4) available on the the set of nodes (2) of the operating system (1) is insufficient to deploy the service with a limited lifetime.