White dot for spacing only
The Dice Project


DICE Meeting 2002-04-30

Ground Floor Seminar Room, BP, 11am-1pm.

Agenda

  1. Corrections to minutes
  2. Actions Arising from minutes of meeting of 2002-04-16
  3. Roles
  4. Review of Tasks
Apologies: Morna

Decisions

  1. 'staff' roles: there is no need for sub-categories within the 'staff' role (eg visitor).
  2. Privacy: all information required for the purposes of administering systems will be considered public.
  3. default 7.1: the default RedHat release will be 7.1
  4. Pseudo-user UIDs: for 'local' pseudo-users use UIDs in the range 500-999, starting from 999 counting down.

Actions

NB: this section includes: It does not include actions that are routinely part of tasks.
  1. Actions Arising: CEG to discuss machine purchase mechanism. (noted 2002-02-19) Carried forward
    [Alastair/Jeremy/Ken]
  2. Actions Arising: Use of XDM and issues of speeding up deployment of DICE (noted 2002-03-05). Carried forward.
    [CEG]
  3. Actions Arising: Deployment tasks to notify Alison about types of documents (noted 2002-03-05). Ongoing.
    [All deployment tasks 'owners']
  4. Actions Arising: local site deployment publicity required.
    [Alastair/Jeremy/Ken]
  5. Actions Arising: UUNs: Site managers to arrange to contact users who will need to change their username to warn them
    [Alastair/Jeremy/Ken]
  6. MIS feed: check about getting data direct (noted 2002-04-02). Ongoing.
    [Neil]
  7. Applications Teaching staff to be advised of issues relating to provision of software for next year.
    [Ken]
  8. Filesystem Maps: Minor issues to be resolved in list of standard locations (noted 2002-04-02). Ongoing.
    [George/Bill/Alastair]
  9. Common Home Directories: unification of groups to be resolved (noted 2002-04-02). Ongoing.
    [Roger]
  10. Handwaving: Backups the backup task still needs a person responsible to be allocated
    [CEG]
  11. Privacy: check requirements for support information that will be private. (noted 2002-04-30)
    [Neil]
  12. Filesystems: aisubmit: check aisubmit requirements . (noted 2002-04-30)
    [Bill]
  13. Filesystems: LDAP partition table: Ken to do initial populate of table, Simon to provide script. Ken to get partition info from Bill.(noted 2002-04-30)
    [Ken/Simon]
  14. Timetable: update milestones with timetable dates. (noted 2002-04-30)
    [All]

Minutes

  1. Corrections to minutes of 2002-04-16

    None were noted.

  2. Actions arising from minutes of last meeting (2002-04-16)

    1. Actions Arising: CEG to discuss machine purchase mechanism. (noted 2002-02-19) [Alastair/Jeremy/Ken]
      Carried forward
    2. Actions Arising: The issue of software required for next year needs to be raised with members of teaching staff. To be raised at Curriculum/Teaching Committees as appropriate.
      [Ken]
    3. Actions Arising: Use of XDM and issues of speeding up deployment of DICE. [CEG].
      Carried forward
    4. Actions Arising: Deployment tasks need to notify Alison what types of documents they will be producing. [All deployment tasks 'owners'].
      Ongoing
      There are still very few responses so Alison should create a 'name and shame' list
      Done
      'Name and shame' list should circulated on cos@inf.
      [ACTION: Alison]
    5. Actions Arising: DICE deployment publicity: Site managers should make sure that this publicity is provided. [Alastair/Jeremy/Ken]
      Ongoing
    6. Actions Arising: Conversion of accounts to UUN: Site managers should contact those users who will need to change their username to warn them again of the need for the change and should arrange for a list of things to change/look out for. [Alastair/Jeremy/Ken]
      Ongoing
    7. Sponsors: note this task in relevant task document
      Done
    8. UUN queries: check that UUNs really are unique.

      Roger has received a list from EUCS (Christine Rees) and this is being checked

      Done
    9. MIS feed: check about getting data direct.[Neil]

      Neil has liaised with David Lowrie and the feed will be setup in due course.

      Ongoing
    10. Infrastructure: update tasks list for task renamed to infrastructure.
      Done
    11. Quotas: these need to be discussed.
      Neil will be writing a proposal.
      Done
      This raised an issue about privacy---see below.

    12. Timetable:this has been started but needs to be distributed and discussed.
      Ongoing
    13. Filesystem Maps: A proposal was sent out and is in principle acceptable with one or two minor issues remaining to clear up.
      Ongoing
    14. Common Home Directories: unification of groups. [Roger]

      The unification group has met and made a proposal including unifying to using staff=10010 and actively changing group ownership of the associated 'staff' files.

      Done
      Final group list needs to be finalised
      [Roger]
    15. Handwaving: Backups. A person responsible needs to be allocated to the stage 1 task.
      [ACTION: CEG]
  3. Roles

    It was agreed that there are no sub-categories required within the staff category. If they are required they can be provided by additional roles.

  4. Privacy of system-related data

    The issue of privacy with respect to quotas information led to the following proposed general policy:

    all information required for the purposes of administering systems will be considered public.

    This allows all relevant data to be held in LDAP without concerns about privacy.

    However, there have been instances where it is useful to note information that should not be public. Neil will discuss the requirements for this with the support groups.

    [ACTION: Neil]

  5. Pseudo-users

    There is a need for pseudo-users on local machines for occasional sysadmin purposes (eg, bindrun). The auth object can handle creation of these to avoid individual components having to do so. In order to avoid clashes there will be a header file specifying which are used and what UIDs they have allocated. These UIDs should be in the range 500-999.

    There is also a need for pseudo-users for testing purposes. These will be effectively full user accounts with Kerberos principals.

  6. Filesystem issues

    aisubmit
    Bill will liaise with Craig over the requirements for the coursework submission software.
    [ACTION: Bill]
    groups/netgroups
    The issue of groups and netgroups was discussed. Use of nsu (in conjunction with netgroups) for users to share filespace is in principle discouraged, given that it will not be available with future secure filesystem technology. However, in the meantime it has to be used as we don't have time to provide alternatives to current pseudo-user/nsu/netgroup arrangements (such as 'cs1').

    LDAP partition table
    The normal route for populating the LDAP partition table will be via the Account Management task. However, the initial one-off populating will be done by Ken.
    [ACTION: Ken]
    This will be by using a perl script which has already been written by Simon. Simon to send it to Ken.
    [ACTION: Simon]
    Information about the actual partitions required will be obtained from Bill.
    [ACTION: Ken]

  7. Timetable

    Jeremy presented a more detailed timetable for deployment. The dates for internal events were discussed and most accepted. The following were noted:

    The issue of RedHat 7.1 vs 7.2 was raised. It was agreed that the base version would be 7.1 but that there would be instances of full 7.2 systems or some 7.2 applications rebuilt for 7.1. It is anticipated that 7.2 can come in gradually rather than having to be a total changeover.

    Internal events
    ---------------
    * minimal standard client (all relevant rpms ported)  30 May
      - includes standalone minimal laptop
    * local site infrastructure                           30 Jun 
      - transit routers and DICE networks                 30 May
      - ldap/kerberos/print servers at each site          30 May
      - dump facilities for mail/web                      30 Jun
    * central infrastructure			      30 Jun
      - mail					      15 Jun
      - web						      30 Jun
      - mailing lists			              30 Jun
      - account creation possible			      30 May
    * NFS service					      30 May
    * pilot login server(s)                               30 May
    * printing (legacy) via DICE                          30 Jun
    * machines ordered for BP/FH/SB		              30 May
    
    External events
    ---------------
    * common home directories	                      30 May
      - groups unification as appropriate at each site    15 May
      - setting up /legacy				      30 May
      - switching users to primary                        30 May
    * inf accounts ready for all current staff            30 May
      - UUN issues sorted				      30 May
    * legacy mail redirected to @inf                      15 Jul
      - requires mail agents review to be complete        30 May
      - soon after majority of users can use DICE.        
    * remaining students move to SMS mailboxes            30 Jun
      - largely administrative
    * inf accounts ready for all current students         ???
    * support facilities                                  30 Jun
      - web form
      - fault tracking
    * new machines decided/notified/ordered (BP/FH/SB)  30 May
      - groups finalised                                
      - groups notified                                 
    * teaching usage of DICE                            30 Jun
      - which students using DICE			    30 May
      - software availability                           30 Jul
    * associate accounts		                    mail changeover
    
    Everyone was asked to check the dates of external events and add any relevant dates to their section of the Goals/Milestones page.
    [ACTION: all]


 : Deploy : Meetings 

Mini Informatics Logo - Link to Main Informatics Page
Please contact us with any comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh
Spacing Line