Page History

...

1. 1. 1. 1. 1. Proof it works:

               Code Block
               language bash linenumbers true collapse true
               [root@ad-build-container-rocky9-544f5787dc-gl4sq iocBoot]# cd iocGuardianTest/ [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# ls Makefile envPaths st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# vim st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# vim st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# ls Makefile envPaths st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# vim st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# chmod +x st.cmd [root@ad-build-container-rocky9-544f5787dc-gl4sq iocGuardianTest]# ./st.cmd #!../../bin/linux-x86_64/Guardian < envPaths epicsEnvSet("IOC","iocGuardianTest") epicsEnvSet("TOP","/build/Guardian") epicsEnvSet("ASYN","/build/support/asyn") epicsEnvSet("EPICS_BASE","/build/epics-base") cd "/build/Guardian" ## Register all support components dbLoadDatabase "dbd/Guardian.dbd" Guardian_registerRecordDeviceDriver pdbbase ## Load record instances #dbLoadRecords("db/xxx.db","user=GUARDIAN") dbLoadRecords("db/test.db") # PATRICK TODO: Temp here for testing dbLoadRecords("db/guardian_snapshot.db", "BASE=SIOC:B34:GD_PATRICK") # PATRICK TODO: Temp add patrick so its unique dbLoadRecords("db/guardian_device_data.db", "BASE=SIOC:B34:GD_PATRICK") # PATRICK TODO: Temp add patrick so its unique ## Configure Guardian driver # GuardianDriverConfigure( # Port Name, # Name given to this port driver GuardianDriverConfigure("GUARDIAN") cd "/build/Guardian/iocBoot/iocGuardianTest" iocInit Starting iocInit ############################################################################ ## EPICS R7.0.8 ## Rev. R7.0.8 ## Rev. Date Git: 2023-12-14 16:42:10 -0600 ############################################################################ iocRun: All initialization complete ## Start any sequence programs #seq sncxxx,"user=GUARDIAN" epics> status: 0 curVal after get : 1 status: 0 curVal after get : 1 status: 0 curVal after set : 1 status: 0 curVal after get : 1 epics> dbl SIOC:B34:GD_PATRICK:FEL_PULSE_E FBCK:FB02:GN01:S2DES_STORED_RBV FBCK:FB02:GN01:S2DES_TEST FBCK:FB02:GN01:S2DES_STORED SIOC:B34:GD_PATRICK:SNAPSHOT_TRG_RBV SIOC:B34:GD_PATRICK:SNAPSHOT_TRG_EN epics> sstriggerval: 0 sstriggerval: 0 sstriggerval: 0 sstriggerval: 1 1: 0 curVal after get : 5 2: 0 Successfully triggered and resetted

         2. Patrick left off here, now see if we can make our config.yaml (of the steps above) for epics/asyn on the registry, so we can get start_build.py to build ioc automatically. This way we can show this to ernest and see if we can get everything including epics in a container.
            
            1. Get the prebuilt one from afs, and upload to ad-build-test github, and download in registry and use that
            2. Get test-ioc to have the basic ioc in there.
            3. Try to see if we can keep epics the same as much as we can, maybe just change env variables to point to epics on /build or the std directory. like the $EPICS
            4. steps to get a test-ioc with modules going:

            5. TODO: Convert the steps below to a config.yaml for test-ioc, then see if we can get it to build with start_build.py

               Code Block
               language bash
               cp -r /mnt/eed/ad-build/registry/epics-base/R7.0.8/epics-base/ /build/ # If this works add to .bashrc because this'll be dev image export EPICS_BASE=/build/epics-base export EPICS_HOST_ARCH=$(${EPICS_BASE}/startup/EpicsHostArch) export PATH=${EPICS_BASE}/bin/${EPICS_HOST_ARCH}:${PATH} cp -r /mnt/eed/ad-build/registry/asyn/R4.39-1.0.1/asyn/ /build/ # Testing ioc cd /build  git clone -b patrick-dev https://github.com/ad-build-test/test-ioc.git cd Guardian/ # in configure/RELEASE # Update EPICS_BASE to point to /build/epics-base # Update ASYN to point to /build/support/asyn # Update configure/CONFIG_SITE CHECK_RELEASE to WARN (temporary fix - since asyn on registry points to epics on registry) make cd iocBoot/iocGuardianTest/ # in st.cmd # Update the shebang to point to #!../../bin/linux-x86_64/Guardian chmod +x st.cmd ./st.cmd

               Continue modifying test-ioc. push, then we can get end-to-end build test cli connection to backend

            6. caveat - for now we are copying entire component dependencies, which is fine and that allows for minimal changes to existing ioc build structure. But this can be a problem if each component has various environments built (this takes up space in the container /build dir), (may want to separate them into their own folder?)
            7. One problem, how will the iocs in the container be accessed by any other server outside?
               1. Because on lcls-dev3 or prod, the every ioc's host is the server itself. While a container's host is the container itself, not the server the container is running on.
               2. 
               3. 
               4. 
               5. Potential solution - TODO: May not be a problem since we are not deploying on kubernetes clusters, we deploy with the image with all the dependencies yes, but it will still be deployed on a production server. We could just use docker on prod (may want to test running epics using just docker, to see if it takes the host of the server machine, or the container still)
               6. TODO: get rid of rocky9-test since we confirm latest dev image works good
      2. How would channel access work if epics is in container? Can it be accessed from main server?
   2. 2) Or try moving everything (/include (.h), /lib (.so/.a), and /bin (binaries)) to according directories (This will save more space)

...