Skip to main content

MAS Installation - 4 Steps Process

High Level MAS Installation process



Step 1: Machines ready with required sizing (Jump Host, Bastion VM , Worker Nodes and Master Nodes)

Step 2: Install RHCOS in all Worker and Master Nodes.

Step 3: Cluster Installation Methods 
             Assisted Installer - No Bastion and Boostrap 
             IPI - Automation covers to entire installation 
             UPI - Existing VMs  or Bare metal (Need to Build   Network , Load Balancer , Configure DNS,H/W Provision, OS Installation and Generate Ignition Configuration)

Step 4: MAS Installation (Core and Manage)
            Manual : 
                 IBM passport advantage 
                 Channel Subscription 
                 Operator Hub
           Automatic - Scripts:
                 One Click Method - Ansible 
                 One Click Method - MAS CLI

Note : Starting from MAS 8.9, manual installation is no longer required. The installation process can be automated using either Ansible or MAS CLI.

Comments

Post a Comment

Popular posts from this blog

Maximo vs Maximo Application Suite 8 Vs Maximo Application Suite 9

Maximo 7.6.1.3 vs MAS 8 Vs MAS 9 User Interface Maximo 7.6.1.3 : Classic UI with traditional navigation and layout. MAS 8 : Common user interface with updated navigation, including slide-out menus and quick launch options. MAS 9 : Enhanced user interface with improved navigation, multi-page dashboards, and more intuitive design. Architecture Maximo 7.6.1.3 : Traditional architecture with on-premises deployment. MAS 8 : Transition to Kubernetes container platform for more scalable and flexible deployment. MAS 9 : Improved Kubernetes platform with better resource management and scalability. Licensing Model Maximo 7.6.1.3 : Named license model with fixed user licenses. MAS 8 : Introduction of AppPoints, a flexible licensing model based on application usage. MAS 9 : Enhanced AppPoints model with more flexibility and options for different user roles. Asset Management Products Maximo 7.6.1.3 : Multiple EAM products bundled in one suite. MAS 8 : Expanded EAM products with additional features ...

Kubernetes Core Components and Terminologies

Kubernetes Core Components and Terminologies Kubernetes, as a robust container orchestration platform, offers a rich ecosystem of components to simplify application deployment and management. Below is an expanded overview of the most important Kubernetes terminologies, providing deeper insights into their functionality. 1. Job: Managing Batch Workloads A Job in Kubernetes ensures that a specified number of Pods execute tasks to completion. Once the tasks are completed, the Pods terminate, making Jobs ideal for one-time or batch processing tasks. Key Use Cases : Data processing pipelines. Database migrations. Sending automated emails or notifications. Advanced Features : Parallel Jobs : Distribute tasks across multiple Pods for faster execution. Completion Policies : Define when a Job is considered successfully completed. 2. Namespace: Segregating Resources Namespaces are logical partitions within a Kubernetes cluster, designed to isolate resources among different teams, projects, or e...