Skip to main content

Hi All,

I’m having one of those days where you ask 5 people the same question and you get 5 different answers back!

I have IFS Cloud 21.1.6 ( Artefacts 2.3.1, Binaries 2.1.1 ) installed , I have 3 deliveries in the build place to apply:

22.1.0 ( Artefacts 2.4.0, Binaries 2.2.0 ) 

22.1.2 ( Artefacts 2.4.0, Binaries 2.2.0 )

22.1.4 ( Artefacts 2.4.2, Binaries 2.2.1 )

To make this question useful to all readers, I have 2 questions:

  1. What is the most efficient way to apply ALL 3 deliveries?
  2. What is the most efficient way to apply 1 delivery?

Only detailed step by step answers allowed, screenshots are always worth extra points, and NO links to tech docs allowed (that will make me grumpy).
Once we have an accepted answer I’ll send it to IFS to update the documentation with.

The only semi-useful information I could find was here:

https://docs.ifs.com/techdocs/22r1/070_remote_deploy/040_upgrading_system/010_preparing_server/50_windows_managementserver/

https://docs.ifs.com/techdocs/22r1/070_remote_deploy/030_patching_system/

https://docs.ifs.com/techdocs/22r1/070_remote_deploy/030_patching_system/020_deploy_delivery/

I assume in a production environment taking backups is always prudent, DB/RMAN backups are sensible but what about MT backups?

Thanks in advance!

Pete, 

It looks like you asked three questions below, please see my answers below.

  1. What is the most efficient way to apply ALL 3 deliveries?
    1. Answer: IFS has a process to consolidate multiple deliveries to one to reduce downtime. It is explained in the technical documentation. Since it is already documented, I am not going to do that. If the tech doc is not clear, we must report that to R&D.  https://docs.ifs.com/techdocs/22r1/070_remote_deploy/500_building_manually/040_multiple_delivery/ However, this process involves preparing a new delivery copying files form individual deliveries, I would recommend doing this whenever you have a large number of deliveries to deploy. 
  2. What is the most efficient way to apply 1 delivery?
    1. Answer:  For the IFS Cloud customers who has installed IFS Cloud in “remote” or “Self-Managed” mode may need additional instructions to deploy deliveries. It is very difficult to provide a generic delivery deployment instructions to “Self-Managed” customers because deployment models can be very different from one Kubernetes orchestration from another. Because of that reason, I am not going to make an attempt to give you generic deployment instructions. for the “Self-Managed” deployments. However,  delivery deployment in the “remote” deployment model can be generalized because we always use Windows Management Server to deploy deliveries. I will try to step by instructions within next couple of weeks.
  3.  Assume in a production environment taking backups is always prudent, DB/RMAN backups are sensible but what about MT backups?
    1. Answer: Now that IFS Cloud MT is fully containerized, the Kubernetes deployment process deletes and recreates pods and Jobs whenever you deploy a delivery. Pods (Containers) and Jobs are short-lived and they don’t persist data so there is no point of taking backups. 

For 2. remote deployment:
https://docs.ifs.com/techdocs/23r1/070_remote_deploy/030_patching_system/020_deploy_delivery/

(ie. on a correctly configured system just run the installer of the delivery, included with the delivery folder)

Reply


Terms & ConditionsCookie settings