Hi, Here is how I think that we should handle this issue (given the discussion that we took on IRC) In order to make sipXsupervisor to run in a distributed environment here is what sipXconfig should offer: 1. Create a fixed URL: https://master:8443/sipxconfig/initial-config/<distributed-hostname> 2. For each <distributed-hostname> should generate a password 3. The password should validate the administrator access to the above URL (The URL is accessed by the administrator from the distributed-hostname) 4. Once the URL is accessed it should download on the distributed hostname a .tar archive that contains: web certificate, sipXsupervisor-config and domain-config. This archive will contain information for the supXsupervisor to make it run on the distributed hostname
Proposed solution (following guidance advice from Damian - thanks) - Create a new Tapestry service that will provide the download URL from above (Will have the same functionality as the existing Download service and, in addition it will create the archive to be downloaded. Also, this service is responsible for password generation in order to validate the access to the fixed URL -Create GUI that will contain text-input field to enter the password, a text-input field to enter the distributed-hostname value, an Apply button to perform the download from the internally generated URL (https://master:8443/sipxconfig/initial-config/<distributed-hostname>) The problem that I have is - what is the relation between the <distributed-hostname> value and the downloaded .tar content. Why should we generate a download URL for each distributed-hostmane? Did I get this right? Please share your thoughts Thanks a lot, Mircea _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
