Method and system for managing a microservice based on command line interface (CLI)

Abstract

The present disclosure relates to a method and a system for managing a microservice based on a Command Line Interface (CLI) The present disclosure encompasses receiving, by a transceiver unit [302], a set of commands related to one or more operations associated with a microservice; receiving, by a transceiver unit [302], a request for performing at least a modification in the set of commands; updating, by a processing unit [304], the set of commands based at least on processing of the request; and executing, by the processing unit [304], the one or more operations for managing the microservice based on execution of the updated set of commands.

Description

METHOD AND SYSTEM FOR MANAGING A MICROSERVICE BASED ON COMMAND LINE INTERFACE (CLI)FIELD OF DISCLOSURE

[0001] The present disclosure generally relates to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for managing a microservice based on Command Line Interface (CLI).BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] On a regular basis, a multitude of requests originate from a user interface to a Capacity Management Platform (CMP) or Capacity Manager microservice. Such requests encompass tasks, such as design, deployment, instantiation, and termination operations associated with a microservice. In general, such requests are initiated from a user interface (e.g., a Graphical User Interface (GUI)). For example, in case of any fault in the system, the requirement of random-access memory (RAM) may need to be changed, or the usage percentage of the central processing unit(CPU) may need to be changed. However, the GUI can sometimes encounter a failure in critical situations, leading to significant time and effort wastage.

[0005] Thus, there exists an imperative need in the art to provide a method and a system for managing a microservice based on a Command Line Interface (CLI), which the present disclosure aims to address.SUMMARY

[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for managing a microservice based on a Command Line Interface (CLI). The method includes receiving, by a transceiver unit, a set of commands related to one or more operations associated with a microservice. The method further includes receiving, by the transceiver unit, a request for performing at least a modification in the set of commands. Furthermore, the method includes updating, by a processing unit, the set of commands based at least on processing of the request. The method also includes executing, by the processing unit, the one or more operations for managing the microservice based on execution of the updated set of commands.

[0008] In an exemplary aspect of the present disclosure, the method comprises launching, by the processing unit, the CLI; and receiving, by the processing unit, the set of commands. The set of commands relate to one of modifying a query builder or fetching alarm, counter, configuration data, and information associated with the microservice.

[0009] In an exemplary aspect of the present disclosure, the method comprises updating, by the processing unit, in an elastic search (ES) database, a log file comprising details associated with the one or more operations.

[0010] Another aspect of the present disclosure may relate to a system to manage a microservice based on a Command Line Interface (CLI). The system comprises a transceiver unit configured to receive a set of commands related to one or more operations associated with a microservice. The transceiver unit is also configured to receive a request to perform at least a modification in the set of commands. The system further comprises a processing unit connected to at least the transceiver unit. The processing unit is configured to update the set of commands based at least on processingof the request. The processing unit is further configured to execute the one or more operations to manage the microservice based on execution of the updated set of commands.

[0011] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing a microservice based on a Command Line Interface (CLI), the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive a set of commands related to one or more operations associated with a microservice. The executable code when executed further causes the transceiver unit to receive a request to perform at least a modification in the set of commands. The executable code when executed further causes a processing unit to update the set of commands based at least on processing of the request. The executable code when executed further causes the processing unit to execute the one or more operations to manage the microservice based on execution of the updated set of commands.OBJECTS OF THE DISCLOSURE

[0012] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0013] It is an object of the present disclosure to provide a system and a method for serving commands for capacity manager through a command line interface (CLI) that saves time and efforts in triggering events.

[0014] It is an object of the present disclosure to provide a solution to handle microservice requests via command line interface (CLI) in case GUI encounters failure, resulting in substantial time and effort saving.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0016] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture, in accordance with exemplary implementations of the present disclosure.

[0017] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementations of the present disclosure.

[0018] FIG. 3 illustrates an exemplary block diagram of a system for managing a microservice based on a Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure.

[0019] FIG. 4 illustrates a method flow diagram for managing a microservice based on a Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure.

[0020] FIG. 5 illustrates an exemplary block diagram of a system architecture for managing a microservice based on a Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure.

[0021] FIG. 6 illustrates an exemplary process flow diagram for managing the microservice based on the Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure.

[0022] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0023] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0024] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may bemade in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0025] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0026] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0027] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0028] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0029] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0030] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0031] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0032] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0033] As used herein, the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0034] As used herein, a Command Line Interface (CLI) is a text based interface that enables users to communicate directly with a computer system or application by imputing commands into a terminal window.

[0035] As used herein, microservices are applications that are built as independent services that run each application process as a service. These services communicate using a well-defined interface using application programming interfaces (APIs).

[0036] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system for managing a microservice based on a Command Line Interface (CLI).

[0037] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture, in accordance with exemplary implementations of the present disclosure. As shown in Fig. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , and a data network (DN)

[0130] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0038] Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects user equipment (UE)

[0102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0039] Access and Mobility Management Function (AMF)

[0106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0040] Session Management Function (SMF)

[0108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. Itcoordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.

[0041] Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0042] Authentication Server Function (AUSF)

[0112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0043] Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0044] Network Slice Selection Function (NSSF)

[0116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0045] Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0046] Network Repository Function (NRF)

[0120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0047] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0048] Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0049] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0050] User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0051] Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0052] FIG. 2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementations of the present disclosure. In an implementation, the computing device

[0200] may also implement a method for managing a microservice based on the Command Line Interface (CLI) utilising the system

[0300] . In another implementation, the computing device

[0200] itself implements the method for managing the microservice based on the Command Line Interface (CLI) using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0053] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] . The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] . Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] .

[0054] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] . Another type of userinput device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] . The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0055] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] . Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] . Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0056] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] . The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] . For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0057] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] . In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , a host

[0224] and the communication interface

[0218] . The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0058] The computing device

[0200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device

[0200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device

[0200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.

[0059] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for managing the microservice based on the Command Line Interface (CLI), in accordance with the exemplary implementations of the present disclosure is shown. The system

[0300] comprises at least one transceiver unit

[0302] and at least one processing unit

[0304] . Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3, only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device / user equipment

[0102] to implement the features of the present disclosure. The system

[0300] may be a part of the user device

[0102] / or may be independent of but in communication with the user device

[0102] (may also referred herein as a UE). In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0060] The system

[0300] is configured for managing the microservice based on a Command Line Interface (CLI), with the help of the interconnection between the components / units of the system

[0300] ,

[0061] The system

[0300] comprises the transceiver unit

[0302] configured to receive a set of commands related to one or more operations associated with a microservice. In some examples, the set of commands may include, such as but not limited to, design, deployment, instantiation, and termination operations associated with the microservice.

[0062] In an implementation, the transceiver unit

[0302] may receive the set of commands from a graphical user interface (GUI). In another implementation, the transceiver unit

[0302] may receive the set of commands from the command line interface (CLI) terminal.

[0063] The transceiver unit

[0302] receives the set of commands that are entered by a user using the CLI. The set of commands may relate to various services that the microservice platform needs to perform. In one implementation, the transceiver unit

[0302] is configured to receive a file. The file includes the set of commands.

[0064] The transceiver unit

[0302] is further configured to receive a request to perform at least a modification in the set of commands. For example, the modification may include adding or deleting terms from the set of commands to perform operations such as implement a new service, modify an existing service, terminate an existing service, and the like.

[0065] The system

[0300] further comprises the processing unit

[0304] connected to at least the transceiver unit

[0302] . The processing unit

[0304] is configured to update the set of commands based at least on processing of the request.

[0066] In one implementation, the processing unit

[0304] is initially configured to launch the command line interface (CLI). In addition, the transceiver unit

[0302] is configured to receive the set of commands. In one example, the transceiver unit is configured to receive an Excel spreadsheet including the set of commands. In particular, an Excel file is imported into the system

[0300] . The CLI serves as a medium through which the set of commands are processed by the processing unit

[0304] ,

[0067] In one implementation, the set of commands relate to one of modifying a query builder or fetching alarm, counter, configuration data, and information associated with the microservice.

[0068] In particular, the set of commands may relate to one of modifying the query builder. In particular, the query builder allows users to input commands to create, modify, and execute queries without needing to write complex instructions related to the set of commands. The term “alarm” may represent alerts in case there is any error in the system

[0300] , The term “configuration data” may represent data which is used to modify the set of commands.

[0069] The processing unit

[0304] is further configured to update, in an elastic search (ES) database

[0306] , a log file comprising details associated with the one or more operations. The log files are updated in order to ensure that the system

[0300] has an easy access to the updated set of commands as and when required.

[0070] The processing unit

[0304] is further configured to execute the one or more operations to manage the microservice based on execution of the updated set of commands. In particular, the processing unit

[0304] is configured to execute the one or more operations to ensure that themicroservice platform reflects the latest commands and modifications. The execution of the one or more operations may include, but not limited to, design operation, deployment operation, instantiation operation, and termination operation related to the microservice.

[0071] Referring to FIG. 4, an exemplary method flow diagram

[0400] for managing the microservice based on the Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure is shown. In an implementation, the method

[0400] is performed by the system

[0300] . Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method

[0400] starts at step

[0402] .

[0072] Prior to step

[0404] , the method

[0400] comprises launching, by the processing unit

[0304] , the CLI.

[0073] At step

[0404] , the method

[0400] comprises receiving, by the transceiver unit

[0302] , the set of commands related to one or more operations associated with the microservice. In one implementation, the set of commands relate to one of modifying a query builder or fetching alarm, counter, configuration data, and information associated with the microservice. In one example, the set of commands may include, but not limited to, design request, deployment request, instantiation request, and termination request.

[0074] In an implementation, the transceiver unit

[0302] is configured to receive the set of commands from the command line interface (CLI).

[0075] At step

[0406] , the method

[0400] comprises receiving, by the transceiver unit

[0302] , the request for performing at least the modification in the set of commands.

[0076] At step

[0408] , the method

[0400] comprises updating, by the processing unit

[0304] , the set of commands based at least on processing of the request.

[0077] At step

[0410] , the method

[0400] comprises executing, by the processing unit

[0304] , the one or more operations for managing the microservice based on execution of the updated set of commands.

[0078] The processing unit

[0304] executes the one or more operations to manage the microservice based on execution of the updated set of commands.

[0079] The method

[0400] further comprises updating, by the processing unit

[0304] , in the elastic search (ES) database

[0306] , the log file comprising details associated with the one or more operations.

[0080] Thereafter, at step

[0412] , the method

[0400] is terminated.

[0081] Referring to FIG. 5, an exemplary block diagram of a system architecture

[0500] for managing a microservice based on a Command Line Interface (CLI) is shown, in accordance with the exemplary implementations of the present disclosure.

[0082] The system comprises a server

[0502] . In one implementation, the file including the command lines is uploaded by the user using the CLI. In an exemplary aspect, the set of commands may include, but not limited to, design, deployment, instantiation, and termination operations associated with the microservice.

[0083] In an exemplary aspect, the Command Line Interface (CLI)

[0504] is used to import the Excel file into the system

[0300] . The CLI serves as the medium through which the set of commands are processed by the processing unit

[0304] .

[0084] The CLI

[0504] then routes the set of commands to the microservice (i.e., capacity management platform (CMP)

[0506] ). In an exemplary aspect, the set of commands may relate to one of modifying query builder that allows users to input commands to create, modify, and execute queries without needing to write complex instructions related to the set of commands.

[0085] The CMP

[0506] microservice then uploads the details associated with the one or more operations in the ES database

[0306] . In an exemplary aspect, the processing unit

[0304] updates the ES database

[0306] with the log files including the details associated with the one or more operations ensuring that the system

[0300] has an easy access to the updated set of commands as and when required.

[0086] Referring to FIG. 6, an exemplary process flow diagram

[0600] for managing the microservice based on the Command Line Interface (CLI), in accordance with exemplary implementations of the present disclosure is shown. Also, as shown in FIG. 6, the process

[0600] starts at step

[0602] .

[0087] At step

[0604] , the process

[0600] comprises launching of the CLI

[0504] . In an exemplary aspect, the processing unit

[0304] launches the CLI.

[0088] At step

[0606] , the process

[0600] comprises loading the excel sheet in the CLI

[0504] . In an exemplary aspect, the Command Line Interface (CLI)

[0504] is used to import the Excel file into the system

[0300] . The CLI serves as the medium through which the set of commands are processed by the processing unit

[0304] .

[0089] In one implementation, the transceiver unit

[0302] receives the request for performing at least the modification in the set of commands. Further, the processing unit

[0304] updates the set of commands based at least on processing of the request.

[0090] At step

[0608] , the process

[0600] comprises executing the updated set of commands. In an exemplary aspect, the processing unit

[0304] executes the one or more operations to manage the microservice based on execution of the updated set of commands. In particular, the processing unit

[0304] may execute the updated set of commands to ensure that the microservice platform reflects the latest commands and modifications.

[0091] At step

[0610] , the process

[0600] terminates.

[0092] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing a microservice based on a Command Line Interface (CLI), the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit

[0302] to receive a set of commands related to one or more operations associated with a microservice. The executable code when executed further causes the transceiver unit

[0302] to receive a request to perform at least a modification in the set of commands. The executable code when executed causes a processing unit

[0304] to update the set of commands based at least on processing of the request. The executable code when executed further causes the processing unit

[0304] to execute the one or more operations to manage the microservice based on execution of the updated set of commands.

[0093] As is evident from the above, the present disclosure provides a technically advanced solution for managing a microservice based on a Command Line Interface (CLI). The present solution a comprehensive range of command line arguments that encompass the entire spectrum, spanning from the design phase to the instantiation phase. These arguments encompass retrieving counters / alarms information for any scenario that encounters failure, including database-related issues. The solution ensures the microservice's integrity is effectively upheld and preserved. The solution also prevents the loss of unrelated data while addressing the specific issue that was disrupting the desired workflow. By implementing the features of the present invention, one is above to trigger events both through the user interface (UI) and the command line interface (CLI).This duality ensures significant time and effort savings during critical scenarios, where UI requests or intermediary requests might falter, allowing all such scenarios to be seamlessly executed using the CLI.

[0094] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably.While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

[0095] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

We Claim:

1. A method for managing a microservice based on a Command Line Interface (CLI), the method comprising:- receiving, by a transceiver unit [302], a set of commands related to one or more operations associated with a microservice;- receiving, by the transceiver unit [302], a request for performing at least a modification in the set of commands;- updating, by a processing unit [304], the set of commands based at least on processing of the request; and- executing, by the processing unit [304], the one or more operations for managing the microservice based on execution of the updated set of commands.

2. The method as claimed in claim 1, comprising:- launching, by the processing unit [304], the CLI; and- receiving, by the transceiver unit [302], the set of commands, wherein the set of commands relate to one of modifying a query builder or fetching alarm, counter, configuration data, and information associated with the microservice.

3. The method as claimed in claim 1, wherein the method comprises updating, by the processing unit [304], in an elastic search (ES) database [306], a log file comprising details associated with the one or more operations.

4. A system to manage a microservice platform based on a Command Line Interface (CLI), the system comprising:- a transceiver unit [302] configured to:- receive a set of commands related to one or more operations associated with a microservice; and- receive a request to perform at least a modification in the set of commands; and- a processing unit [304] connected to at least the transceiver unit, the processing unit is configured to:- update the set of commands based at least on processing of the request; and- execute the one or more operations to manage the microservice based on execution of the updated set of commands.

5. The system as claimed in claim 4, wherein the processing unit [304] is configured to:- launch the CLI; and- the transceiver unit [302] is configured to receive the set of commands, wherein the set of commands relate to one of modifying a query builder or fetching alarm, counter, configuration data, and information associated with the microservice.

6. The system as claimed in claim 4, wherein the processing unit [304] is configured to update, in an elastic search (ES) database [306], a log file comprising details associated with the one or more operations.

7. A non-transitory computer readable storage medium storing instructions for managing a microservice based on a Command Line Interface (CLI), the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit to receive a set of commands related to one or more operations associated with a microservice; the transceiver unit to receive a request to perform at least a modification in the set of commands; a processing unit to update the set of commands based at least on processing of the request; and the processing unit to execute the one or more operations to manage the microservice based on execution of the updated set of commands.

Images