Maximo Open Forum

 View Only
  • 1.  Running MAS in Desktop Docker

    Posted 05-28-2024 18:46

    Has anyone ran MAS in Desktop Docker on a laptop?  I'm wondering how much physical memory is required on the laptop.

    Does it work well, or is a convoluted difficult setup?


    #Administration
    #MaximoApplicationSuite

    ------------------------------
    Jose Nodeland
    JedaWorks
    ------------------------------


  • 2.  RE: Running MAS in Desktop Docker

    Posted 05-29-2024 15:34

    you may reach out to Henrique Faria  as he presented MAS on single node at Go Maximo this year. That may get you close. 



    ------------------------------
    Christopher Winston
    Projetech Inc.
    IBM Champion 2024
    ------------------------------



  • 3.  RE: Running MAS in Desktop Docker

    Posted 05-30-2024 09:37

    Did you get the data you were looking for?   I am interested in the same data.

    Jerry.E.Barnes@nasa.gov



    ------------------------------
    Jerry Barnes
    NASA - KSC
    ------------------------------



  • 4.  RE: Running MAS in Desktop Docker

    Posted 05-30-2024 10:22

    I'm in the process of standing up our POC for MAS as we speak. I have a MacBook Pro with 6 cores, 32GB of RAM and terabyte hard drive and it is not enough to stand up MAS locally using Openshift code ready containers. We have opted to use the on-prem, single node assisted installer for x86 bare metal and it works fine. Our set up is 10 cores, 2 disks, one set at 150GB and the other is set at 100GB with UUID storage set to true. The VM we are using is provided through VMware. The reason we use two disks is for the LVM operator to be installed. (You can check he box using the assisted installer for it to install LVM, or you can do it manually). It take a small bit of reconfiguring for openshift, but the documentation provided by IBM is sound. If you install LVM on your laptop, you essentially get one shot at the install. Because once the LVM writes to the disk, it's next to impossible to get it off. The guide I am using is here. Docker works great, but if you're installing on a laptop use this command to pull the image and use the CLI in your container: docker run -dit --net=host --name sno quay.io/ibmmas/cli:latest bash . This will bind your localhost to the CRC cluster deployed on your laptop. It's a known issue, but this is a solid workaround when it comes to logging into your local cluster and running the MAS playbooks. Once I get past my licensing verification issues, I plan on documenting the entire install process on single node and making it available. Good luck on your journey, I hope you like learning new things, because you're about to.



    ------------------------------
    Brett Coleman
    Georgia Building Authority
    ------------------------------



  • 5.  RE: Running MAS in Desktop Docker

    Posted 05-30-2024 22:46
    Edited by Maycon Belfort 05-30-2024 22:49

    Hi @Jose Nodeland. This might be what you're looking for.

    https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=installing-red-hat-openshift-container-platform-maximo-application-suite-windows-system

    14 vCPU and 30GB of memory.

    Or run only Manage locally on Windows using PodMan.

    https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=administering-local-maximo-manage-development-environments



    ------------------------------
    Maycon Belfort
    BPD Zenith
    IBM Champion 2024
    ------------------------------



  • 6.  RE: Running MAS in Desktop Docker

    Posted 05-31-2024 01:34

    Thanks all for the info.  Yeah, about to learn new things, even though I don't want to.



    ------------------------------
    Jose Nodeland
    JedaWorks
    ------------------------------



  • 7.  RE: Running MAS in Desktop Docker

    Posted 05-31-2024 08:27

    You'll be alright. The best advice I can give is to just get in there and get your hands dirty. It took me about two solid weeks of digging my heels in and figuring it out. Our IBM reps have been great too, lean on them when you get stuck. Also, if I can help at all, please don't hesitate to reach out. 

    Re: my reply yesterday. We actually had to bump our VM up to 16 cores and 64 GB of ram to avoid some latency issues that arose in the openshift console when we were spinning up MAS core.

    We also ran into some issues with entitlement to IBM container library. Hopefully those hurdles are cleared now. I'm about to try and deploy a new install, so finger crossed. I'll let you know how it goes. 



    ------------------------------
    Brett Coleman
    Georgia Building Authority
    ------------------------------