Hi All,
When I update services by importing the Service Template CSV, and one of the changes is a different element to the original that is hosted on a different DMA, the routing stops working because the service is hosted on a different DMA to the element as the element has changed.
Is there a reason why this happens?
As a work around we have to delete the services and re-import as a new service to the service template.
Hope that makes sense
Regards
Hi Jeeva, apologies should have confirmed, they are in a cluster together
I see that this question has been inactive for some time. Have you found a solution for this yet? If so, could you select the answer (using the ✓ icon)? If not, could you answer the questions Wouter asks below?
As this question has now been open for a long time and there has been no further reaction from you, I will now close it. If you do wish to investigate this further, feel free to post a new question or contact techsupport@skyline.be for assistance.
As I understand, the scenario you are describing is as follows:
- Use a service template to generate a service SVC1 that includes element EL1
- All of these are hosted on DMA1
- Now re-apply the service template so that the existing SVC1 ends up with a different element EL2 (with EL2 hosted on DMA2)
- SVC1 is still hosted on DMA1 but now has element EL2 from DMA2
All of this should really be fine. A service should still show the correct state and data even if the element is not hosted on the same DMA as where the service is.
Is the description above accurate? From your description, I read that when you tried this, the service stopped working as expected?
Hello Ryan, could you please let me know if these DMAs are not in a cluster?