-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
After some internal discussion and previous consultation with users, we have decided to standardise on Solaris for the login and web servers. We will therefore be converting nightshade from Linux to Solaris at some point in the future.
There is no fixed time frame for this at moment, but it won't happen sooner than a month from now, and we won't do anything until we are satisfied that all tools (and users) are ready for the migration.
To start with, we want to identify and fix any issues which prevent users from moving their tools to Solaris. This will mainly include:
* Software which needs to be installed or updated * Behaviour differences between Linux and Solaris where the Linux behaviour is more correct or preferable.
Please take a moment to test your tools on willow, the existing Solaris login server. If you find any issues, please open a ticket in JIRA, and include [solaris] in the subject line so we can easily identify them.
Software on Solaris is often newer than the software on the Linux login server. This isn't a problem that can be fixed (since the software will eventually be updated anyway), but during the migration period, we can install more recent versions on Linux as well to allow interoperability.
The easiest way for users to migrate is probably to ensure your tools work on both systems; you can then continue to run them on Linux for now (if you want), and there will be no work required once the conversion is done.
Some differences between the two operating systems are documented on the wiki at https://wiki.toolserver.org/view/Solaris.
- river.
On Mon, Sep 13, 2010 at 4:51 PM, River Tarnell river.tarnell@wikimedia.de wrote:
- Behaviour differences between Linux and Solaris where the Linux behaviour is
more correct or preferable.
I really like the crontab syntax of vixie cron, especially @reboot and /. Would it be possible to use vixie on Solaris?
Bryan
-----Original Message----- From: toolserver-l-bounces@lists.wikimedia.org [mailto:toolserver-l-bounces@lists.wikimedia.org] On Behalf Of Bryan Tong Minh
I really like the crontab syntax of vixie cron, especially @reboot and /. Would it be possible to use vixie on Solaris?
Bryan _______________________________________________
Or the jobserver to be sorted out for scheduling tasks maybe? I notice that per-month scheduling, and every n minutes, or every n hours is still impossible according to the manual pages for the job scheduling, and the jobserver bug list [2]. If this is not the case, please do correct me (and the man page :P ).
Simon (stwalkerster)
[1] man job_schedule [2] https://wiki.toolserver.org/view/Jobserver#TODO_.2F_feature_requests
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Simon Walker:
Bryan Tong Minh:
I really like the crontab syntax of vixie cron, especially @reboot and /. Would it be possible to use vixie on Solaris?
Or the jobserver to be sorted out for scheduling tasks maybe? I notice that per-month scheduling, and every n minutes, or every n hours is still impossible
Eventually I would like to see the jobserver supplant cron entirely. As well as offering a nicer interface (IMO), it is quite a bit more featureful. In particular, a future extension is the 'distributed jobserver', where jobs are started on any of a number of hosts according to load. That would mean that if we rebooted one login server, for example, jobs would be automatically re-started on the other, effectively meaning no downtime.
But this is all something for the future, and in particular depends on whether WM-DE is willing to fund the work to develop it.
In the meantime, I don't think replacing Sun cron with Vixie cron is feasible. Changing out a core part of the system (which other parts of the system rely on) for a completely different implementation is likely to cause all kinds of problems, and of course would be completely unsupported.
- river.
Simon Walker wrote:
Or the jobserver to be sorted out for scheduling tasks maybe? I notice that per-month scheduling, and every n minutes, or every n hours is still impossible according to the manual pages for the job scheduling, and the jobserver bug list [2]. If this is not the case, please do correct me (and the man page :P ).
Simon (stwalkerster)
That would be quite nice.
And perhaps not too hard. A naive implementation could just store requests into a vixie cron that sent its processes into the jobserver (by changing its shell maybe?).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Platonides:
And perhaps not too hard. A naive implementation could just store requests into a vixie cron that sent its processes into the jobserver (by changing its shell maybe?).
Adding support for "every 2 hours" is not difficult at all, and it doesn't require any kind of external cron service. The jobserver already supports scheduling, the only change would be to extend "every hour" to understand "every N hours" (and similarly for minutes, days, etc).
I think this is already on the feature request list, so I'll get around to it the next time I look at the jobserver.
- river.
toolserver-l@lists.wikimedia.org