question

FranciscoJesusGilSanandres avatar image
0 Votes"
FranciscoJesusGilSanandres asked FranciscoJesusGilSanandres answered

Cloud Service - Why change the IP between Cloud Services on swap??

Hello everyone, I don't know if you can help me with my question.

I have migrated a Cloud Service (classic) to (extended support) and it works correctly. (We will call it CS01)

I have also created a second Cloud Services (extended support) to use it as Stagging Slot. (We will call it CS02)

But I have a problem when I swap between both Cloud Services. The IP of CS01 goes to CS02 and vice versa.

On the other hand, the configuration is kept in each Cloud.

That is, if I make a change in the configuration of CS02, when I make a swap, the Role of CS02 passes to CS01 but the configuration does not.

And this did not happen in the Cloud Services (classic), because when you made a swap between the production slot and the stagging slot, the stagging configuration passed to production, but not the IP, and each slot maintained its IP.

Is there any way to keep this working?

Thank you very much in advance.

azure-cloud-services-extended-support
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I am looking into it and will get back to you shortly. Thanks.

1 Vote 1 ·
karishmatiwari-msft avatar image
0 Votes"
karishmatiwari-msft answered

@FranciscoJesusGilSanandres

The configuration associated with a given deployment never changes as a result of a swap operation: CS01 always has the CS01 config and CS02 always has the CS02 config.

The entire purpose of the operation is to swap the VIP (aka Public IP Address) from one deployment to the other.

I'm not sure what is meant by "each slot maintained its IP". Is this referencing the DIP in classic cloud services? Let me know.

The ip addresses are swapped in Cloud Services Extended Support (CS-ES). As a result, traffic should move to swapped service. If you are using reserved IPs, those values are updated in the cscfgs. However, the configs themselves are not swapped.

Hope that helps. Let me know if you have any further questions.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FranciscoJesusGilSanandres avatar image
0 Votes"
FranciscoJesusGilSanandres answered

Hi Karishma, thanks for your reply!

As far as I had tested in Cloud Services (Classics), the configuration switched between the Production slot and the Stagging slot when swapping, but I could be wrong.

What I am sure of is that the public ip was maintained for each slot.

My English is not very good, so I will try to explain it in another way.

Cloud Services (Classics)
This is how, as far as I know, swap works with CS Classics (correct me if I'm wrong).

Before Swap

After Swap

Cloud Services (Extended support)
This is how swap works with CS Extended support (correct me if I'm wrong).
Before Swap

After Swap

This means that you can't have another process configured to access the IP or URI of the "My Prod Cloud Service", because it will change whenever you make a swap. Something that until now I was able to do with the CS Classics.

I don't see any sense that when you make a swap it changes everything except the configuration.






5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.