|
|
|
| Task: | Forrest Hill/South Bridge specific legacy system site issues |
| Group: | johnb, roger, iainr |
| Stage: | 1 |
NB - this document is a bit rough
Yes, it is. Despite the large amounts of work going into the DICE project none of it has much meaning if an initial 2/3rd's of our users are left high and dry.
This is the main area of concern at the moment. The Sun servers will require NIS/DNS information. Currently this will be maintained but will need some thought when this moves to an .inf server. What is actually required to generate what's needed from the DICE world (and what needs to be requested being available from LDAP, eg when it comes to netgroups)?
It looks like netgroups will be the thing requiring most consideration, looking at the plans for LDAP. Interestingly the work being done by the acctech group may be modified for most of the things we need here. Purists might not like it but we could have an external to LDAP src for netgroup info (this is, after all, transitionary - so anything that actually works robustly should be considered fair game).
It seems that the availability of sufficient secondary groups for inf will do the trick for groups (and to some extent netgroups) although we should probably allow for some rationalisation here.
More to the point from the users point of view, should we consider mounting of home directory and structure (with /legacy et. al.) to be consistent with the way dice does things, or just to mount the (ex) dai file space as is now.
We will now be offering the same mount points as from inf machines on legacy boxes.
Similar thought needs to be given to hesiod and printing. But it looks like we can keep the maps anyway. At least in some form.
And it now seems certain there won't be a problem for legacy machines to print to inf printers (except for the usual ones if we take this opportunity to rename the printers - it would be the usual one of users getting used to the new names and altering their configs).
We also support the AIAI and ANC subnets. Support for their platforms (mainly sun support and some digital) and services needs be maintained. Also AIAI need significant Windows Development support, which is currently supplied by a post here. ANC have a 1/2 CO post assigned to them. Presumably this will continue. Note that dai is currently providing diskspace (and UIDs - cheap but needs remembered) for ANC phd students, whereas ANC machines are not considered a stage one task there will need to be thought and consultation given to those whose filespace et al is in (currently) dai but who need to use ANC resources.
This isn't going to be of much interest most compstaff, but seems fairly essential. Basically most of this comes down to "what won't we get that we got before?".
Still uncertain. Depends strongly on a lot of other groups. Hope to have some rough test stuff working in at least some way by end Feb.
This task depends to some extent on the User Apps investigation going on at FH/SB.
It is also dependant on LDAP at some point providing sufficient information to enable NIS etc information being generated.
And the filesystems team.
Also account technology people.
Just about everything...
|
Please contact us with any
comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh |
|
