Skip main navigation (Press Enter).
Log in
Toggle navigation
Log in
Community
Topic Groups
Champions
Directory
Program overview
Rising Champions
IBM Champions group
User Groups
Directory
Benefits
Events
Dev Days
Conference
Community events
User Groups events
All TechXchange events
Participate
TechXchange Group
Welcome Corner
Blogging
Member directory
Community leaders
Resources
IBM TechXchange
Community
Conference
Events
IBM Developer
IBM Training
IBM TechXchange
Community
Conference
Events
IBM Developer
IBM Training
Maximo
×
Back to Library
Maximo Scheduler Optimization - Components and Basic recomendation
Like
Share
Share on LinkedIn
Share on X
Share on Facebook
Tue June 08, 2021 09:28 AM
Pedro Spadacini
A good number of Maximo Scheduler Optimization customers come to us and ask about:
Is there any calculation of the RAM or Hard disc space that is recommended by IBM to provision a MOS server?
Is there any recommended OS specification for MOS?
Can we run MOS on VPC( Virtual Private cloud) servers?
Can we run MOS on Any Cloud provisioned infrastructure?
To be able to answer those question is always good to understand the solution:
So for a basic setup at the
Evaluation
phase, our recommendation will be a Docker environment with a minimum of 8GB of Memory RAM, 2 VCPU's, and 100GB of Disk. With that:
- Console will be the small container that will consume fewer resources than the Rest API container, and together 1GB of RAM will be enough to run both together.
- The Execution container is the one where the Demand of Memory can change according to the type of Optimization process (Data, Constraints, and Variables), it is recommended to use as minimum a limit of 8GB of memory RAM and 2 VCPU's with 1 container/pod. End-users will be able to submit 3 parallel Optimization processes at the same time on each Execution Container based on the property
MOFEXEC_QUEUEWORKERS (default with 3)
.
As a container solution, all the parts can be scale up or down depends on the necessity of each customer.
- For the Mongo DB that can be installed with the same docker system running as a container and it will consume more HD space than CPU and Memory, normal we map a dedicated space of 10GB to be able to persist the Optimization Process execution.
Size of the Images:
*Mongo-seed is the one we use to populate the Maximo Optimization framework with the Model and the Project setting. Just run once and stop.
So after this basic description, we can back to the original question:
Is there any calculation of the RAM or Hard disc space that is recommended by IBM to provision a MOS server?
No, we don't have an automatic way to calculate once that needs to be analyzed based on the scenario of Data, Constraints, and Objects. We can affirm with the 2VCPU's 8GB RAM and 100GB HD we are running an Optimization process of thousands of Work Orders (GSLP)
Is there any recommended OS specification for MOS?
The base Images of the Container are Linux so we recommend that the Container orchestrator support Linux Base images. Red Hat, Ubuntu, Windows 10, CentOS are OS we already run the solution without problems.
Can we run MOS on VPC( Virtual Private cloud) servers?
As long it supports the Linux container that will not be a problem.
Can we run MOS on Any Cloud provisioned infrastructure?
Yes, you can run the solution at Any Cloud provider infrastructure. We already deploy at K8s services of IBM Cloud and AWS. That will require some work over the values on the deploy process due to different services for connectivity.
Additional Performance Test results can be found
here
.
#MaximoScheduler
#Maximo
#AssetandFacilitiesManagement
Statistics
0 Favorited
40 Views
0 Files
0 Shares
0 Downloads
Powered by Higher Logic