[NeoStats-Devel] [Support] Closed: (NEO-405) HostServ migration setting/option

     [ http://support.my-ho.st/jira/browse/NEO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Hammond closed NEO-405.
------------------------------

    Resolution: Won't Fix

NeoStats has ceased Development

> HostServ migration setting/option
> ---------------------------------
>
>                 Key: NEO-405
>                 URL: http://support.my-ho.st/jira/browse/NEO-405
>             Project: NeoStats
>          Issue Type: New Feature
>          Components: HostServ
>    Affects Versions: 3.0.a3
>            Reporter: Jason
>            Assignee: Justin Hammond
>
> Making an option to convert from HostServ 2.x to 3.x
> Whether this be a command-line option or an option available to HostServ v3.x It would be great to see this option.
> it would allow people like us to convert our database and test the new HostServ, currently we are using 2.x for HostServ & OPSB and 3.x for everything else.
> Ideas:
> command-line feature which links 2.x to 3.x and then reads the HostServ list details and adds them into 3.x
> command-line option that reads the HostServ 2.x database table structure and then uses the internal HostServ 3.x function to add the hosts into the new database format.
> Have an option when both HostServ 2.x is loaded and HostServ 3.x is loaded using different nicknames on the network and have them talk to each other to read from 2.x and add to 3.x
> I think any of the above should be possible and would allow for more of us to test the new HostServ!
> Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://support.my-ho.st/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira