FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR INSTALLATION OF CONTAINERIZATION PLATFORM”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR INSTALLATION OF CONTAINERIZATION
PLATFORM
FIELD OF THE INVENTION
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to a method and system for installation of containerization platform.
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. Further, reducing call drops and latency is of paramount importance in the telecommunications industry. Call drops can be frustrating for users, and they can also result in lost revenue for service providers. Latency, on the other hand, refers to the time it takes for data to travel from one device to another and can cause delays and disruptions in communication. The introduction of 5G technology promises to address these issues by delivering ultra-low

latency and high-speed data transmission. With 5G, call drops are going to be minimized, and users are going to experience seamless, uninterrupted communication. Additionally, 5G technology may enable the development of new applications and services that require high-speed, low-latency communication, such as remote surgeries, autonomous vehicles, and virtual reality. The reduction of call drops, and latency is crucial in ensuring that users have access to reliable and efficient communication services, and the 5G technology is a significant step towards achieving this goal.
[0004] In the 5G communication system, a number of network functional (NF) modules are provided, for example an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Manager Function UDM), a Network Slice Selection Function (NSSF), and/or a Network Repository Function (NRF), etc., one or more of which interact with each other to implement multiple operations of the 5G communication system. These network functions are either configured over a distributed virtual network or a distributed cloud-based network. In case of distributed virtual network, the network setup process comprises installation of an operating system on one or more target nodes; installation of containerization platform or docker on the one or more target nodes; configuration of network on the one or more target nodes; configuration of network functions (NFs) on the one or more target nodes.
[0005] Accordingly, installation of the containerization platform or docker on the plurality of target nodes is a vital step in network setup process. Conventionally, a method of installing the containerization platform or docker on the one or more target nodes includes: manually logging-in, by an application centric Interface, into one of a plurality of target nodes; manually running, by a user, an installation execution engine on the one of the plurality of target nodes for installing the containerization platform or docker on the one of the plurality of target nodes; and repeating the steps of manually logging-in, and the manually running of the installation execution engine, for installation of the containerization platform or docker on each of the plurality of target nodes. However, the step of repeatedly performing the steps of manually logging-in, and the manually running of the installation execution engine, for installation of the containerization platform or docker on each of the plurality of target nodes, is an effort consuming step. Particularly, such conventional methods for installation of the containerization platform or docker on

each of the plurality of target nodes, is a labour-intensive process, and may require high valued time of skilled people. This is not a productive technique.
[0006] Thus, there exists an imperative need in the art to provide an automated system and method for installation of a containerization platform or docker on a plurality of target nodes.
SUMMARY
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for installation of containerization platform. The method includes receiving, at an automated cloud installer (ACI) controller unit, a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI. The method further includes validating, by the automated cloud installer (ACI) controller unit, a connection with each of the one or more target nodes using the login credentials. The method further includes automatically logging-in, by the automated cloud installer (ACI) controller unit, to the one or more target nodes. Finally, the method includes automatically executing, by the automated cloud installer (ACI) controller unit, the installation script for installation of the containerization platform on the one or more target nodes.
[0009] In an exemplary aspect of the present disclosure, the method further comprises receiving, at the automated cloud installer (ACI) UI, a virtual machine identifier and a login credential for one or more target nodes. The method further comprises creating, by the automated cloud installer (ACI) UI, an installation script for the one or more target nodes based on the virtual machine identifier and the login credential. The method further comprises validating, by the automated cloud installer (ACI) UI, reachability of the one or more target nodes and the login credentials of the one or more target nodes. The method further comprises initiating, by the automated cloud installer (ACI) UI, installation of containerization platform on the one or more target nodes.

[0010] In an exemplary aspect of the present disclosure, the automated cloud installer (ACI) controller unit concurrently executes the installation script for installation of the containerization platform on the one or more target nodes.
[0011] In an exemplary aspect of the present disclosure, method further comprises verifying, by the automated cloud installer (ACI) controller unit, a progress status of the installation of docker on the one or more target nodes.
[0012] In an exemplary aspect of the present disclosure, the method further comprises retrieving, by the one or more nodes, installer package from internet. The method further comprises executing, by the automated cloud installer (ACI) controller unit, pre-configured scripts for application-specific configuration on the one or more nodes. The method further comprises displaying, by the automated cloud installer (ACI) UI, the status of the execution of the pre-configured scripts on the one or more nodes.
[0013] Another aspect of the present disclosure may relate to a system for installation of containerization platform. The system comprises a receiving unit configured to receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI. The system further comprises a validating unit configured to validate a connection with each of the one or more target nodes using the login credentials. The system further comprises a processing unit configured to automatically logging-in to the one or more target nodes. Finally, the system further comprises the processing unit configured to automatically execute the installation script for installation of the containerization platform on the one or more target nodes.
[0014] Yet another aspect of the present disclosure may relate to a user equipment (UE) for installation of containerization platform. The UE comprises a processor, configured to receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI for installation of a containerization platforms, wherein installation of the containerization platform is based on: validating a connection with each of the one or more target nodes using the login credentials; automatically logging-in to the one or more target nodes; and automatically execute the installation script for installation of the containerization platform on the one or more target nodes.

[0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for installation of containerization platform, the instructions include executable code which, when executed by one or more units of a system, causes: a receiving unit configured to receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI. The instructions when executed further causes a validating unit configured to validate a connection with each of the one or more target nodes using the login credentials. The instructions when executed further causes a processing unit configured to automatically logging-in to the one or more target nodes. The instructions when executed further causes the processing unit configured to automatically execute the installation script for installation of the containerization platform on the one or more target nodes.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] It is an object of the present disclosure to provide an automated system and method for installation of a containerization platform on a plurality of target nodes in a parallel manner, as part of network setup process.
[0018] It is another object of the present disclosure to provide an automated system for installation of a containerization platform on a plurality of target nodes. The system comprises: an Automated Cloud Installer User Interface (ACI UI), an Automated Cloud Installer controller unit (ACI CU), and an internet node. The ACI CU manages programmable interpreter and installation execution engine that includes dynamic shell script execution engine, dynamic programming rules and pluggable automation procedures. The ACI CU is capable of communicating with each of the ACI UI and the plurality of target nodes. Each of the plurality of target nodes are further capable of communicating with the Internet node, for retrieval of installer packages therefrom. The ACI CU is further adapted to run the installation execution engine on each of the plurality of target nodes, to install the containerization platform thereon. The nature of installation execution engine is dynamic, user can modify programmable interface, configuration on the go without shutting down its running processes.

[0019] It is yet another object of the present disclosure to provide an automated method for installation of a containerization platform or docker on a plurality of target nodes.
[0020] It is yet another object of the invention automatic to perform containerization platform or docker installation on multiple target nodes in a parallel manner which speeds up the deployment process.
DESCRIPTION OF THE DRAWINGS
[0021] 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.
[0022] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0023] FIG. 2 illustrates an exemplary block diagram of a system for installation of containerization platform, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 3 illustrates a method flow diagram for installation of containerization platform in accordance with exemplary implementations of the present disclosure.

[0025] FIG. 4 illustrates an exemplary block diagram of a system architecture for installation of containerization platform, in accordance with exemplary implementations of the present disclosure.
[0026] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0027] 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.
[0028] 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 be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0029] 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.
[0030] 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.
5 [0031] 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
10 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.
15
[0032] 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
20 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
25 disclosure. More specifically, the processor or processing unit is a hardware processor.
[0033] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless
communication device”, “a mobile communication device”, “a communication device”
30 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.
9

Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure. 5
[0034] 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,
10 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.
[0035] As used herein “interface” or “user interface refers to a shared boundary across
15 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.
20 [0036] 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),
25 Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0037] 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
30 connected with the system.
[0038] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other
10

existing problems in this field of technology by providing method and system for installation of containerization platform.
[0039] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (also
5 referred to herein as a computer system [100]) upon which the features of the present
disclosure may be implemented in accordance with exemplary implementation of the
present disclosure. In an implementation, the computing device [100] may also implement
a method for installation of containerization platform utilising the system. In another
implementation, the computing device [100] itself implements the method for installation
10 of containerization platform using one or more units configured within the computing
device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0040] The computing device [100] may include a bus [102] or other communication
15 mechanism for communicating information, and a processor [104] coupled with bus [102]
for processing information. The processor [104] may be, for example, a general-purpose
microprocessor. The computing device [100] may also include a main memory [106], such
as a random-access memory (RAM), or other dynamic storage device, coupled to the bus
[102] for storing information and instructions to be executed by the processor [104]. The
20 main memory [106] also may be used for storing temporary variables or other intermediate
information during execution of the instructions to be executed by the processor [104].
Such instructions, when stored in non-transitory storage media accessible to the processor
[104], render the computing device [100] into a special-purpose machine that is customized
to perform the operations specified in the instructions. The computing device [100] further
25 includes a read only memory (ROM) [108] or other static storage device coupled to the bus
[102] for storing static information and instructions for the processor [104].
[0041] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [102] for storing information and instructions. The
30 computing device [100] may be coupled via the bus [102] to a display [112], 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 [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command
11

selections to the processor [104]. Another type of user input device may be a cursor
controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating
direction information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees of
5 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.
[0042] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program
10 logic which in combination with the computing device [100] causes or programs the
computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the
15 main memory [106] from another storage medium, such as the storage device [110].
Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] 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.
20
[0043] The computing device [100] also may include a communication interface [118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital
25 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 [118] 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 [118] sends and
30 receives electrical, electromagnetic, or optical signals that carry digital data streams
representing various types of information.
[0044] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication
12

interface [118]. In the Internet example, a server [130] might transmit a requested code for
an application program through the Internet [128], the ISP [126], the local network [122],
host [124] and the communication interface [118]. The received code may be executed by
the processor [104] as it is received, and/or stored in the storage device [110], or other non-
5 volatile storage for later execution.
[0045] The computing device [100] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [100] include, but are not limited only to, personal computers, laptops, tablets,
10 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 [100] 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.
15
[0046] Referring to FIG. 2, an exemplary block diagram of a system [200] for installation of containerization platform, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least automated cloud installer (ACI) controller unit [200a], at least one receiving unit [202], at least one automated cloud
20 installer (ACI) user interface UI [204], at least one validating unit [206], at least one
processing unit [208], at least one creating unit [210], at least one verifying unit [212], at least one retrieving unit [214], at least one executing unit [216], and at least one displaying unit [218]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units
25 shown within the system should also be assumed to be connected to each other. Also, in
FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device to implement the features of the present disclosure.
30 The system [200] may be a part of the user device / or may be independent of but in
communication with the user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
13

[0047] The system [200] is configured for installation of containerization platform or
docker, with the help of the interconnection between the components/units of the system
[200].
5
[0048] The system comprises an automated cloud installer (ACI) controller unit [200a].
The ACI controller unit [200a] further comprises a receiving unit [202] which is configured
to receive a login credential for one or more target nodes and an installation script from an
automated cloud installer (ACI) UI [204]. As used herein, automated cloud installer (ACI)
10 is a platform that ensures end-to-end automation in the 5G carrier network which results in
reducing the time taken for installation and deployment of 5G network functions or applications. As used herein, the one or more target nodes may be network nodes such as such as but not limited only routers, switches, hubs, gateways, load balancers, wireless base stations servers or network devices etc. In an exemplary aspect, one or more target nodes
15 may be associated with the network such as, 5G network. In an implementation, the one or
more target nodes may be associated with AMF , SMF. In an exemplary aspect, one or more target nodes may be associated with the network other than 5G network, such as 6G network. As used herein, installation script is a sequence of instructions with several commands within a file capable of being executed without being compiled.
20
[0049] The receiving unit [202] receives for one or more target nodes, the login credentials which is a set of unique identifiers–such as a username and password.
[0050] In an exemplary aspect, the ACI UI [204] may refer to a graphical user interface
25 (GUI). The displaying unit [218] may associated with ACI UI [204].
[0051] The receiving unit [202] at the ACI controller unit [200a] receives login credential
from user via ACI UI [204] for one or more target nodes and an installation script. The
installation script may have commands for configurations and parameters updates for
30 containerization platform or docker or supported application based on operating system
(OS) version or network requirements of target nodes. In an exemplary aspect, the ACI controller unit [200a] may receive via the receiving unit [202] from the ACI UI [204] a deployment plan for installation of containerization platform or docker for the target nodes. The deployment plan may comprise installation of containerization platform or docker in
14

one or more target nodes in a parallel manner. In an exemplary aspect, containerization platform fully automates the cloud deployments using open-source platforms such as but not limited to docker, Openshift, Openstack etc.
5 [0052] The receiving unit [202] is further configured to receive a virtual machine identifier
and a login credential for one or more target nodes. As used herein, a virtual machine (VM) is a compute resource that uses software instead of a physical computer to run programs and deploy apps. One or more virtual “guest” machines run on a physical “host” machine.
10 [0053] The receiving unit [202] may receive via ACI UI [204], such as, but not limited to,
CVIM_ID and input login credentials for all the manager and network nodes such as worker nodes. As used herein, a worker node is a node that runs the application in a cluster and reports to a control plane. The main responsibilities of a worker node are to process data stored in the cluster and handle networking to ensure traffic between the application across
15 the cluster and outside of the cluster are properly facilitated.
[0054] The ACI controller unit [200a] further comprises a creating unit [210] which is
configured to create an installation script for the one or more target nodes based on the
virtual machine identifier and the login credential. In an exemplary aspect, the creating unit
20 [210] is communicatively coupled to the receiving unit [202]. The creating unit [210] at the
ACI controller unit [200a] may create deployment plan for installing the installation script for one or more target nodes based on VM identifier and login credential details.
[0055] The ACI controller unit [200a] further comprises a validating unit [206] which is
25 configured to validate a connection with each of the one or more target nodes using the
login credentials. In an exemplary aspect, the validating unit [206] is communicatively
coupled to the receiving unit [202]. The validating unit [206] at ACI controller unit [200a]
checks the connection between target nodes and ACI controller unit [200a] and validates
target nodes are in connection with ACI controller unit [200a], which are mentioned or
30 required for containerization platform or docker installation as per user configuration
files/commands.
[0056] The validating unit [206] is further configured to validate reachability of the one or more target nodes and the login credentials of the one or more target nodes. The
15

validating unit [206] at the ACI controller unit [200a] validates login credentials for
authorising the access for target nodes. The validating unit [206] validates username and
password for allowing the access of the target nodes. Further, the validating unit [206]
validates the reachability of the target nodes for performing installations. The validating
5 reachability refers herein, checking the target nodes are connected in the network and
available for providing service in the network. The validating unit [206] at the ACI
controller unit [200a] may send one of method such as, but not limited to sending ping
message to the target nodes and tracing route of the target nodes for checking the
reachability of the target node, so that network setup or installation of containerization
10 platform or docker can be performed.
[0057] The ACI controller unit [200a] comprises a processing unit [208] configured to automatically logging-in to the one or more target nodes. In an exemplary aspect, the processing unit [208] is communicatively coupled to the validating unit [206]. After
15 validating the reachability of the one or more target nodes, the processing unit [208] at the
ACI controller unit [200a] automatically logs-in to the one or more target nodes for configuring the parameters or attributes as per mentioned/required commands or files. The processing unit [208] is further configured to automatically execute the installation script for installation of the containerization platform on the one or more target nodes. In an
20 exemplary aspect, the processing unit [208] executes installation script automatically for
installation of the docker on the one or more target nodes. For example, the processing unit [208] may run installation script on such as, but not limited to, sever or server associated with AMF for installing containerization platform or docker based on the virtual machine identifier for implementing new functions, updates, capability for enhancing the service
25 requirement of the network.
[0058] The processing unit configured to initiate installation of containerization platform
on the one or more target nodes. The processing unit [208] is further configured to
concurrently execute the installation script for installation of the containerization platform
30 or docker on the one or more target nodes. The processing unit [208] executes the
installation script for the installation of containerization platform or docker simultaneously on one or more target nodes. The concurrent/simultaneous installation of the script reduces the processing time for the containerization platform or docker on one or more target nodes which makes the system [200] efficient.
16

[0059] The ACI controller unit [200a] further comprises a verifying unit [212] which is
configured to verify a progress status of the installation of containerization platform or
docker on the one or more target nodes. The verifying unit [212] may verify that installation
5 scripts run successfully on the one or more target nodes. The verifying unit [212] may
check installation progress of containerization platform or docker on the one or more target
nodes. In an exemplary aspect, the progress status may verify how much installation as per
deployment plan on the one or more target nodes has been achieved or running stage. The
progress status may also provide on how many target nodes completion of the installation
10 of the containerization platform or docker are pending.
[0060] The ACI controller unit [200a] further comprises a retrieving unit [214] which is
configured to retrieve, by the one or more target nodes, installer package from internet. As
used herein, installer packages incorporate all the information needed to install, uninstall,
15 and run setup for applications and products. The retrieving unit [214] at the ACI controller
unit [200a] retrieves by the one or more target nodes, the installer package from the internet based on a type of operating system (OS) installed in the one or more target nodes. The installation package may have information for OS version and functionalities.
20 [0061] The ACI controller unit [200a] further comprises an executing unit [216] which is
configured to execute, by the automated cloud installer (ACI) controller unit [200a], pre-configured scripts for application-specific configuration on the one or more target nodes. As used herein, the pre-configured scripts may include pre-check script, backup containerization platform scripts, docker configuration scripts or other related scripts. The
25 pre-check scripts perform all necessary operations and validate system configurations
required for application deployment at a later stage. These operations include configuring firewall settings, IP tables, and Kernel parameters to enable smooth application deployment once the containerization platform is installed. The pre-check scripts, which are a type of pre-configured script validate system configurations before application deployment. For
30 instance, these scripts might configure firewalls to permit necessary network traffic, adjust
IP tables settings to manage packet filtering, and modify kernel parameters to optimize system performance. By automating these tasks, the executing unit [216] helps to streamline the process of configuring the target nodes, reducing the potential for human error, and saving significant time. In addition to pre-check scripts, the executing unit [216]
17

manages other types of pre-configured scripts, such as backup containerization platform
scripts and Docker configuration scripts. Backup containerization platform scripts might
be used to create and store snapshots of the system state such that data and settings can be
restored if needed. Docker configuration scripts, on the other hand, might involve setting
5 up Docker with specific configurations to the application's needs, such as adjusting
resource limits, configuring storage options, or setting up network configurations.
[0062] Moreover, during the Docker installation process, the executing unit [216] utilizes
YUM repository files to install the RPM packages based on the OS and Docker versions of
10 the target nodes. The YUM repository acts as a package manager for RPM files, facilitating
the installation, removal, and upgrade of packages. The executing unit [216] detects the OS
version on each target node and runs the appropriate scripts or commands to install the
required RPM packages using YUM. This capability allows the ACI controller unit [200a]
to perform these installations in a parallel manner across multiple target nodes, thereby
15 accelerating the deployment process. For example, a user might create a deployment plan
and input login credentials for all manager and worker nodes. The ACI controller unit
[200a] then automatically detects the OS version on each target node and uses the executing
unit [216] to run the appropriate installation scripts. This parallel execution of scripts on
multiple target nodes not only speeds up the deployment process but also provides real-
20 time status updates to the user via the ACI UI. The user can monitor the progress of the
installation and configuration tasks, allowing for timely intervention if any issues arise. In
an exemplary aspect, the pre-configured scripts may be fetched from a storage unit or from
the network via internet.
25 [0063] For example, a user creates a deployment plan for installing Docker across multiple
target nodes within a cloud environment. The user inputs the login credentials for these nodes into the automated cloud installer (ACI) UI. The ACI controller unit [200a] then automatically detects the OS version of each node. Based on this information, it retrieves and installs the appropriate RPM packages using the YUM repository, which manages
30 these packages according to the OS and Docker version requirements. During this process,
the ACI concurrently runs the necessary scripts on all target nodes, setting up firewalls, configuring iptables, and adjusting Kernel parameters as part of the pre-check scripts to prepare the system for application deployment. Throughout the installation, the ACI UI displays real-time status updates, indicating whether each step was successful or if there
18

were any issues, thereby providing a comprehensive, automated solution for Docker installation and system configuration.
[0064] In an exemplary aspect, application-specific configuration may contain not only
5 containerization platform or docker related configurations, but also any configuration in
general like firewall, internet protocol (IP) tables rules, etc. which are common for one or more target nodes.
[0065] The executing unit [216] at the ACI controller unit [200a] executes the pre-
10 configured scripts for application-specific configuration on the one more target nodes. In
an exemplary aspect, the execution of the pre-configured scripts for application-specific
configuration corresponds to the usage of the installer package for installation of the
containerization platform like docker thereon. For example, different target nodes may
have different and application-specific configuration, such as server associated with AMF
15 and SMF may have a (MANO), or other similar systems. Pre-check scripts involve
performing application-specific configurations to prepare the system environment on the
target nodes. These configurations might include setting up network parameters, adjusting
system resources, and configuring necessary services to meet the specific requirements of
the application. For example, in the case of a 5G core network service, pre-check scripts
20 might configure network interfaces, apply necessary security settings, and optimize
performance parameters to support high data throughput and low latency. Similarly, for
MANO applications, the scripts might set up orchestration tools, configure management
interfaces, and ensure the appropriate allocation of resources to manage the network
functions effectively.
25
[0066] The ACI controller unit [200a] further comprises a displaying unit [218] which is
configured to display, by the automated cloud installer (ACI) UI [204], the status of the
execution of the pre-configured scripts on the one or more nodes. The displaying unit [218]
displays final status of the execution of the pre-configured scripts on ACI UI [204] to check
30 whether the pre-configured scripts ran successfully or not on the on the one or more target
nodes.
[0067] Referring to FIG. 3, an exemplary method flow diagram [300] for installation of container, in accordance with exemplary implementations of the present disclosure is
19

shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302]. 5
[0068] At step [304], the method [300] comprises receiving, at an automated cloud
installer (ACI) controller unit [200a], a login credential for one or more target nodes and
an installation script from an automated cloud installer (ACI) UI [204]. The receiving unit
[202] at the ACI controller unit [200a] receives login credential from user via ACI UI [204]
10 for one or more target nodes and an installation script. The installation script may have
commands for configurations and parameters updates for containerization platform or docker or supported application based on version or network requirements.
[0069] As used herein, the one or more target nodes may be network nodes such as such
15 as but not limited only routers, switches, hubs, gateways, load balancers, wireless base
stations servers or network devices etc. In an exemplary aspect, one or more target nodes
may be associated with the network such as, 5G network. In an implementation, the one or
more target nodes may be associated with AMF, SMF. In an exemplary aspect, one or more
target nodes may be associated with the network other than 5G network, such as 6G
20 network. As used herein, installation script is a sequence of instructions with
several commands within a file capable of being executed without being compiled.
[0070] The receiving unit [202] may receive for one or more target nodes, the login credentials which is a set of unique identifiers–such as a username and password. 25
[0071] In an exemplary aspect, the ACI UI [204] may refer to a graphical user interface (GUI). The displaying unit [218] may associated with ACI UI [204].
[0072] The receiving unit [202] at the ACI controller unit [200a] may receive login
30 credential from user via ACI UI [204] for one or more target nodes and an installation
script. The installation script may have commands for configurations and parameters updates for containerization platform or docker or supported application based on operating system (OS) version or network requirements of target nodes. In an exemplary aspect, the ACI controller unit [200a] may receive via the receiving unit [202] from the ACI UI [204]
20

a deployment plan for installation of containerization platform or docker for the target
nodes. The deployment plan may comprise installation of containerization platform or
docker in one or more target nodes in a parallel manner. The deployment plan request
comprises target node identifiers, such as name, instance ID, and IP address, along with
5 login credentials and a CVIM_ID. These elements facilitate in identifying and accessing
the target nodes, facilitating the deployment and configuration process by providing the necessary details for the automated cloud installer to perform its tasks efficiently.
[0073] The method [300] further comprises receiving, at the automated cloud installer
10 (ACI) UI [204], a virtual machine identifier and a login credential for one or more target
nodes. The receiving unit [202] may receive at the ACI UI [204], a virtual machine (VM)
identifier and the login credential for one or more target nodes. The ACI UI [204] receives,
such as, but not limited to, CVIM_ID and input login credentials for all the manager and
network nodes such as worker nodes. The CVIM_ID, which can be referred to as a "profile
15 name" or "plan name," is an identifier representing the collection of target nodes, including
managers and workers. This ID is used to track and check the status of all target nodes
within the plan, such as the status of Docker installation or the execution of pre-check
scripts. It allows for efficient management and monitoring of the deployment process
across all associated nodes. As used herein, a worker node is a node that runs the
20 application in a cluster and reports to a control plane. The main responsibilities of a worker
node are to process data stored in the cluster and handle networking to ensure traffic
between the application across the cluster and outside of the cluster are properly facilitated.
[0074] The method [300] further comprises creating, by the automated cloud installer
25 (ACI) UI [204], an installation script for the one or more target nodes based on the virtual
machine identifier and the login credential. The creating unit [210] at the ACI controller unit [200a] creates, using (ACI) UI [204], a deployment plan for installing the installation script by for one or more target nodes based on VM identifier and login credential details.
30 [0075] At step [306], the method [300] comprises validating, by the automated cloud
installer (ACI) controller unit [200a], a connection with each of the one or more target nodes using the login credentials. The validating unit [206] at the ACI controller unit [200a] ensures and validates that required target nodes are reachable or in connection with ACI
21

controller unit [200a] and the login credentials of the one or more target nodes are authorised for accessing at the target nodes.
[0076] The method [300] further comprises validating, by the automated cloud installer
5 (ACI) controller unit [200a], reachability of the one or more target nodes and the login
credentials of the one or more target nodes. The validating unit [206] at the ACI controller unit [200a], validates, using an ACI UI [204], that required target nodes are reachable or in connection with ACI controller unit [200a] and the login credentials of the one or more target nodes. The validating unit [206] at the ACI controller unit [200a] validates login
10 credentials for authorising the access for target nodes. The validating unit [206] validates
username and password for allowing the access of the target nodes. Further, the validating unit [206] validates the reachability of the target nodes for performing installations. The validating reachability refers herein, checking the target nodes are connected in the network and available for providing service in the network. The validating unit [206] at the ACI
15 controller unit [200a] may send one of method such as, but not limited to sending ping
message to the target nodes and tracing route of the target nodes for checking the reachability of the target node, so that network setup or installation of containerization platform or docker can be performed.
20 [0077] At step [308], the method comprises automatically logging-in, by the automated
cloud installer (ACI) controller unit [200a], to the one or more target nodes. After validating the reachability of the one or more target nodes, the processing unit [208] at the ACI controller unit [200a] automatically logs-in to the one or more target nodes for configuring the parameters or attributes as per mentioned/required commands or files. At step [310],
25 the method [300] comprises automatically executing, by the automated cloud installer
(ACI) controller unit [200a], the installation script for installation of the containerization platform or docker on the one or more target nodes.
[0078] In an exemplary aspect, the processing unit [208] executes installation script
30 automatically for installation of the containerization platform or docker on the one or more
target nodes. For example, the processing unit [208] may run installation script on such as, but not limited to, sever or server associated with AMF for installing containerization platform or docker based on the virtual machine identifier for implementing new functions, updates, capability for enhancing the service requirement of the network.
22

[0079] In an exemplary aspect, the automated cloud installer (ACI) controller unit [200a]
concurrently executes the installation script for installation of the containerization platform
or docker on the one or more target nodes. The processing unit [208] may initiate
5 installation of containerization platform on the one or more target nodes. The processing
unit [208] executes the installation script for the installation of containerization platform or docker simultaneously on one or more target nodes. The concurrent/simultaneous installation of the script reduces the processing time for the containerization platform or docker on one or more target nodes which makes the system [200] efficient.
10
[0080] The method [300] further comprises verifying, by the automated cloud installer (ACI) controller unit [200a], a progress status of the installation of containerization platform or docker on the one or more target nodes. The verifying unit [212] may verify final status of the execution of the pre-configured scripts at ACI controller unit [200a] using
15 ACI UI [204] to check whether the pre-configured scripts ran successfully or not on the on
the one or more target nodes. The verifying unit [212] may verify that installation scripts run successfully on the one or more target nodes. The verifying unit [212] may check installation progress of containerization platform or docker on the one or more target nodes. In an exemplary aspect, the progress status may verify how much installation as per
20 deployment plan on the one or more target nodes has been achieved or running stage. The
progress status may also provide on how many target nodes completion of the installation of the containerization platform or docker are pending.
[0081] The method [300] further comprises retrieving, by the one or more nodes, installer
25 package from internet. The retrieving unit [214] at the ACI controller unit [200a] retrieves
by the one or more target nodes, the installer package from the internet based on a type of operating system (OS) installed in the one or more target nodes.
[0082] The method [300] further comprises executing, by the automated cloud installer
30 (ACI) controller unit [200a], pre-configured scripts for application-specific configuration
on the one or more target nodes. The executing unit [216] at the ACI controller unit [200a] executes the pre-configured scripts for application-specific configuration on the one more target nodes. In an exemplary aspect, the execution of the pre-configured scripts for
23

application-specific configuration corresponds to the usage of the installer package for installation of the containerization platform or docker thereon.
[0083] As used herein, the pre-configured scripts may include pre-check script, backup
5 containerization platform scripts, docker configuration scripts or other related scripts. re-
check scripts perform all necessary operations and validate system configurations required for application deployment at a later stage. These operations include configuring firewall settings, iptables, and Kernel parameters to enable smooth application deployment once the containerization platform is installed. Pre-check scripts, which are a type of pre-configured
10 script validate system configurations before application deployment. For instance, these
scripts might configure firewalls to permit necessary network traffic, adjust iptables settings to manage packet filtering, and modify kernel parameters to optimize system performance. By automating these tasks, the executing unit [216] helps to streamline the process of configuring the target nodes, reducing the potential for human error, and saving
15 significant time. In addition to pre-check scripts, the executing unit [216] manages other
types of pre-configured scripts, such as backup containerization platform scripts and Docker configuration scripts. Backup containerization platform scripts might be used to create and store snapshots of the system state such that data and settings can be restored if needed. Docker configuration scripts, on the other hand, might involve setting up Docker
20 with specific configurations to the application's needs, such as adjusting resource limits,
configuring storage options, or setting up network configurations.
[0084] Moreover, during the Docker installation process, the executing unit [216] utilizes YUM repository files to install the RPM packages based on the OS and Docker versions of
25 the target nodes. The YUM repository acts as a package manager for RPM files, facilitating
the installation, removal, and upgrade of packages. The executing unit [216] detects the OS version on each target node and runs the appropriate scripts or commands to install the required RPM packages using YUM. This capability allows the ACI controller unit [200a] to perform these installations in a parallel manner across multiple target nodes, thereby
30 accelerating the deployment process. For example, a user might create a deployment plan
and input login credentials for all manager and worker nodes. The ACI controller unit [200a] then automatically detects the OS version on each target node and uses the executing unit [216] to run the appropriate installation scripts. This parallel execution of scripts on multiple target nodes not only speeds up the deployment process but also provides real-
24

time status updates to the user via the ACI UI. The user can monitor the progress of the installation and configuration tasks, allowing for timely intervention if any issues arise. In an exemplary aspect, the pre-configured scripts may be fetched from a storage unit or from the network via internet. 5
[0085] In an exemplary aspect, application-specific configuration may contain not only containerization platform or docker related configurations, but also any configuration in general like firewall, internet protocol (IP) tables rules, etc. which are common for one or more target nodes.
10
[0086] The executing unit [216] at the ACI controller unit [200a] executes the pre-configured scripts for application-specific configuration on the one more target nodes. In an exemplary aspect, the execution of the pre-configured scripts for application-specific configuration corresponds to the usage of the installer package for installation of the
15 containerization platform like docker thereon. For example, different target nodes may
have different and application-specific configuration, such as server associated with AMF and SMF may have application-specific configurations.
[0087] The method [300] further comprises displaying, by the automated cloud installer
20 (ACI) UI [204], the status of the execution of the pre-configured scripts on the one or more
nodes. The displaying unit [218] displays final status of the execution of the pre-configured scripts on ACI UI [204] to check whether the pre-configured scripts ran successfully or not on the on the one or more target nodes.
25 [0088] At step [312], the method [300] terminates.
[0089] Referring to FIG. 4, an exemplary block diagram of a system [400] architecture
for installation of containerization platform is shown, in accordance with the exemplary
embodiments of the present invention. The system [400] includes an automated cloud
30 installer (ACI) user interface (UI) [402], automated cloud installer (ACI) [404] and target
nodes [406].
[0090] In an exemplary aspect of the present disclosure, the ACI UI [402] may perform following actions, such as:
25

[0091] Create a deployment plan with CVIM_ID and input login credentials for all the manager and worker nodes and validating by checking for reachability of nodes and the login credentials.
5 [0092] Clicking on “install” on ACI UI [402] which will initiate containerization platform
or docker installation.
[0093] Running pre-check scripts using ACI UI [402] upon successful completion of user
by running pre-configured scripts to make application specific configuration on the target
10 nodes. Once pre-check scripts are initiated, ACI UI [402] runs an ansible scripts on one or
more target nodes parallelly and displays final status on GUI when scripts ran successfully or not.
[0094] Furthermore, the ACI [404] installs containerization platform or docker when a
15 request is received from the ACI UI [402]. The ACI performs the following actions, such
as:
[0095] Handling all the requests related to containerization platform or docker installation
and pre check script. Once user initiates containerization platform or docker installation
20 using ACI UI [402]. ACI [404] login to target nodes [406]. Further, ACI [404] runs all pre-
configured commands to install containerization platform or docker. Further, ACI [404] checks containerization platform or docker status and display status on GUI to check whether installation was success or failure.
25 [0096] Furthermore, the target nodes [406] received commands from the ACI [404] to
install containerization platform or docker. The target nodes [406] installs required packages from the internet. The target nodes [406] performs following steps such as:
• Backing up containerization platform or docker configuration and YUM repo files.
• Running commands to install containerization platform or docker.
30 • Running commands to check containerization platform or docker status.
[0097] In an exemplary aspect, target nodes [406] sends installation status information back to the ACI [404].
26

[0098] The present disclosure further discloses a user equipment (UE) for installation of containerization platform or docker. The UE comprises a processor, configured to receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI for installation of a containerization platforms, wherein installation of the containerization platform is based on: validating a connection with each of the one or more target nodes using the login credentials; automatically logging-in to the one or more target nodes; and automatically execute the installation script for installation of the containerization platform on the one or more target nodes.
[0099] The present disclosure further closes a non-transitory computer readable storage medium storing instructions for installation of containerization platform, the instructions include executable code which, when executed by one or more units of a system, causes a receiving unit [202] configured to receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI [204]. The instructions when executed further causes a validating unit [206] configured to validate a connection with each of the one or more target nodes using the login credentials. The instructions when executed further causes a processing unit [208] configured to automatically logging-in to the one or more target nodes. The instructions when executed further causes the processing unit [208] configured to automatically execute the installation script for installation of the containerization platform or docker on the one or more target nodes.
[0100] As is evident from the above, the present disclosure provides a technically advanced solution for installation of containerization platform or docker. The present solution executes the entire process automatically and parallel, it reduces a processing time for such method of installation of the containerization platform or docker on the one or more target nodes. Additionally, such method and system reduce a need of skilled personnel for implementing such installation of the containerization platform or docker on the one or more nodes. This is also less labour-intensive and more efficient method of such installation of the containerization platform or docker on the one or more target nodes.
[0101] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the 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.
[0102] 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.

We Claim:
1. A method for installation of a containerization platform , the method comprising:
receiving, at an automated cloud installer (ACI) controller unit [200a], a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI [204];
validating, by the automated cloud installer (ACI) controller unit [200a], a connection with each of the one or more target nodes using the login credentials;
automatically logging-in, by the automated cloud installer (ACI) controller unit [200a], to the one or more target nodes; and
automatically executing, by the automated cloud installer (ACI) controller unit [200a], the installation script for installation of the containerization platform on the one or more target nodes.
2. The method as claimed in claim 1, the method further comprising:
- receiving, at the automated cloud installer (ACI) UI [204], a virtual machine identifier and a login credential for one or more target nodes;
- creating, by the automated cloud installer (ACI) controller unit [200a], an installation script for the one or more target nodes based on the virtual machine identifier and the login credential;
- validating, by the automated cloud installer (ACI) controller unit [200a], reachability of the one or more target nodes and the login credentials of the one or more target nodes; and
- initiating, by the automated cloud installer (ACI) controller unit [200a], installation of containerization platform on the one or more target nodes.

3. The method as claimed in claim 1, wherein the automated cloud installer (ACI) controller unit [200a] concurrently executes the installation script for installation of the containerization platform on the one or more target nodes.
4. The method as claimed in claim 1, the method further comprises verifying, by the automated cloud installer (ACI) controller unit [200a], a progress status of the installation of containerization platform on the one or more target nodes.

5. The method as claimed in claim 1, the method further comprising:
- retrieving, by the one or more target nodes, installer package from internet;
- executing, by the automated cloud installer (ACI) controller unit [200a], pre-configured scripts for application-specific configuration on the one or more target nodes; and
- displaying, by the automated cloud installer (ACI) UI [204], status of the execution of the pre-configured scripts on the one or more target nodes.
6. A system [200] for installation of a containerization platform, the system
comprising:
- an automated cloud installer (ACI) controller unit [200a] comprising:
o a receiving unit [202] configured to receive a login credential for one or
more target nodes and an installation script from an automated cloud
installer (ACI) UI [204], o a validating unit [206] configured to validate a connection with each of the
one or more target nodes using the login credentials, o a processing unit [208] configured to automatically logging-in to the one
or more target nodes, and o the processing unit [208] configured to automatically execute the
installation script for installation of the containerization platform on the
one or more target nodes.
7. The system [200] as claimed in claim 6, the system further comprises:
- the receiving unit [202] configured to receive a virtual machine identifier and the login credential for one or more target nodes;
- a creating unit [210] configured to create an installation script for the one or more target nodes based on the virtual machine identifier and the login credential;
- the validating unit [206] configured to validate reachability of the one or more target nodes and the login credentials of the one or more target nodes; and
- the processing unit [208] configured to initiate installation of containerization platform on the one or more target nodes.

8. The system [200] as claimed in claim 6, wherein the processing unit [208] is configured to concurrently execute the installation script for installation of the containerization platform on the one or more target nodes.
9. The system [200] as claimed in claim 6, wherein the automated cloud installer (ACI) controller unit [200a] comprises a verifying unit [212] configured to verify a progress status of the installation of containerization platform on the one or more target nodes.
10. The system as claimed in claim 6, wherein the system comprises:

- a retrieving unit [214] configured to retrieve, by the one or more target nodes, installer package from internet;
- an executing unit [216] configured to execute, by the automated cloud installer (ACI) controller unit [200a], pre-configured scripts for application-specific configuration on the one or more target nodes; and
- a displaying unit [218] configured to display, by the automated cloud installer (ACI) UI [204], status of the execution of the pre-configured scripts on the one or more target nodes.
11. A user equipment (UE) comprises:
a processor, configured to:
- receive a login credential for one or more target nodes and an installation script from an automated cloud installer (ACI) UI for installation of a containerization platform , wherein installation of the containerization platform is based on:
- validating a connection with each of the one or more target nodes using the login credentials;
- automatically logging-in to the one or more target nodes; and
- automatically executing the installation script for installation of a containerization platform on the one or more target nodes.