Kevin Thorley wrote: > On Fri, 2009-01-23 at 13:25 -0500, Scott Lawrence wrote: >> On Fri, 2009-01-23 at 12:59 -0500, Raymond Dans wrote: >>> In order to test changes XECS-2072, I've had to do upgrades from 3.10.x >>> to 3.11.9. Unfortunately the upgrade to 3.11.9 (r14537) did not go >>> smoothly. I've noticed a number of issues and couldn't find >>> corresponding Jira's for them. In order to ensure that these problems >>> don't slip through the cracks, I'd like to know if they are valid issues >>> (since I've never really done upgrades before) and secondly whether or >>> not the issue has been addressed in some Jira already: >>> > [...] >>> 4. After getting sipxconfig started (by using sipxproc to set the config >>> version and startup status), I was able to log into the Admin. >>> Unfortunately no other services were started. When checking the >>> Services area, I noticed that the IP address of the server was not set >>> and none of the "Roles" were selected. I'm not sure how this could be >>> handled but it looks like the upgrade process will have to somehow >>> examine what services were active before and somehow map that to the new >>> "Roles" mechanism. >> Again, the previous service states need to be imported during the >> upgrade somehow. A job for sipXconfig, I think... > > There is supposed to be code that handles this situation (migrating from > topology.xml to current Location code). If it is not working in the > 3.10.x to 3.11.x upgrade, please open a Jira issue >
I do not think that sipXconfig has any way of importing the list of services that were running before the upgrade. The code that Kevin mentions here (migrating topology) will properly add all the servers/locations that were configured. However it won't add the services (and never did). In 3.10 (and before) sipXconfig did not have any permanent list of services that were running on each server. Every time it needed such list it was asking watchdog (reborn as sipxsupervisor)? Ideally of course we would somehow capture the list of services that are running before the upgrade, upgrade the system, translate the services into roles and enable the specific roles. Any ideas how to do that? If that's not practical to implement - what's the next best thing? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
