ReIp agents
Hi , I am trying to ReIp few TeamCity agents : agents are dynamic (managed by VMware, via TeamCity's VMWare plug-in). We should be able to kill agents.
My question is : where the TC master and agent network configuration file lives (IP address, port and vlans). and what is the best practice to reIP TC agents.
Please sign in to leave a comment.
Hi,
I'm not entirely sure I understand what you want to do. Assign new IPs? Could you describe it in more detail? Can you describe, if you have already tried, which issues you are facing?
Hi Denis,
Thank you for replying. I am trying to Re-IP Master and agents and change the vlan on both.. then verify all connection back online and working.
Is there a config file that hold all the network info on the master that control the agents as well, that I can configure?
Is there one location configuration file that I need to change for all agents ?
I Re-IP the master but I see more agents hanging to finish the build more than usual and some get stuck.
Any help will be appreciated
Hi,
ok, thanks for the description, but I'm afraid that I'm unfamiliar with the way "re-ip" works, so I can't really talk about specifics. All information below is assuming you will perform some sort of IP change. If it isn't, and Re-IP works as a proxy, please refer to setting up teamcity behind a proxy: https://confluence.jetbrains.com/pages/viewpage.action?pageId=74845225#HowTo...-SetUpTeamCitybehindaProxyServer
The server does hold a reference to its own address in the administration - global settings, but this address is usually DNS, not IP. You can change the dns name there if needed. If you change the IP from the server, it might be wise to stop the server and restart it, but it also shouldn't be needed. Communication between server and agent starts from the agents.
Agents don't hold information of their own IP and take it from the system when needed. Agents are configured in their buildAgent.properties file in the conf folder with the parameters pointing at the server, and they are the ones to start the communication, so the server doesn't have the information either until they connect. That way, changing the IPs of your agents should simply be a matter of changing the IP. If something doesn't work, a restart should simply work.
Other than that, teamcity processes will use the java networking stack. We can only recommend that you set up a test environment and try there first before moving production. If you have any specific issues, we can try and help with those.
Thank you Denis, much appreciated.