DICE development projects - compexec

Manager:

gdmr

Unit:

Summary:

Pseudo-project to track effort going to the decant from AT 6/7/8 to somewhere

What:

We're going to be decanting out of AT 6/7/8 to somewhere as-yet-unspecified in 2015. This project is a procedural thing to allow us to track effort.

Why:

AT recladding will happen, which requires us to move out for the duration.

Other:

Dependencies:

Risks:

AT 3/4/5 decant to Forrest Hill

gdmr — Thu, 13 Mar 2014 10:30:41 +0000

Project ID:

303

Current stage:

Manager:

gdmr

Unit:

Summary:

Pseudo-project to track effort going to the decant from AT 3/4/5 to Forrest Hill

What:

We're going to be decanting out of AT 3/4/5 to Forrest Hill in 2015. This project is a procedural thing to allow us to track effort.

Why:

AT recladding will happen, which requires us to move out for the duration.

Other:

Dependencies:

Risks:

Computing help site enhancements

ascobie — Wed, 04 Dec 2013 16:09:48 +0000

Project ID:

298

Current stage:

Manager:

Unit:

Summary:

Implement various enhancements to the computing.help.inf.ed.ac.uk web site

What:

The existing computing support form is still hosted on the old CVS based computing support web site. This form needs to be implemented in the new drupal service.
The mechanism for editing and displaying system status was a quick and dirty solution so as to not hold back delivery of the new help site. It needs implemented properly, ideally deriving some of its data from Nagios
A user must click on the printer icon to display a printer-friendly version of a page. It would be nicer if this was automatic, using a printer specific stylesheet.

When:

Not time critical

Other:

CEG internal documentation review

alisond — Thu, 22 Aug 2013 09:53:57 +0000

Project ID:

286

Current stage:

Unit:

Summary:

Review of CEG internal documentation

Other:

Dependencies: project 280

Risks:

Redevelop School Equipment inventory

boss — Fri, 25 Jan 2013 15:46:29 +0000

Project ID:

269

Current stage:

3s_Stalled

Manager:

Unit:

What:

Description: Design and implement a new School equipment inventory.

Deliverables:

Why:

Customer:

Case statement: The current inventory system does not meet all our requirements and there is concern that tracking machines has now become unreliable. This is particularly the case for self-managed machines. We are not able to easily answer fundamental inventory questions - this is a particular problem for planning expenditure and machine allocation.

A previous project reviewed the existing system. It had been hoped that this project would identify some simple fixes to the existing system, but unfortunately the conclusion was that the base inventory schema was sufficiently flawed that many problems could simply not be fixed. Basically, the system was not designed to cater for self-managed machines.

It is widely accepted that a complete redesign is required. It may well be possible to re-use some components of the existing system.

When:

Status:

Timescales:

Priority:

Time:

How:

Proposal:

Resources: 9 weeks effort in total.

Plan:

Check what other schools are using to inventory equipment
Design (2 weeks)
1. Sketch architecture
2. Design schema
3. Decide on information flow between information sources/sinks
4. Consider whether software inventory could be easily added as a later project
5. Consult
6. Determine how much of Theon can be used (querying/editing/reports)
7. Sketch design of :
  1. inventory editing/querying tools (invedit/invquery)
  2. order editing (rfe orders)
  3. MAC loading
  4. LCFG conduits
  5. client machine conduit (clientreport)
  6. switchdb conduit (switchtoinfdb)
  7. Web reports
8. Consider which existing data to migrate, and how.
9. Consult
Implement (4 weeks)
1. Add schema to Theon and create tables
2. Create test data and load into tables
3. Implement inventory query tool
4. Implement order editing code
5. Implement MAC loading conduit
6. Implement client machine conduit
7. Implement switchdb conduit
8. Implement LCFG conduits
9. Implement inventory edit tool
10. Implement web reports
11. Test against test data
Documentation and training (1 week)
Migrate data (2 weeks)

Other:

Home page:
home page on wiki

Dependencies:

Risks:

Milestones

Proposed date	Achieved date	Name	Description

VM / cloud options survey

boss — Fri, 25 Jan 2013 15:46:26 +0000

Project ID:

256

Current stage:

Manager:

iainr

Unit:

What:

Description: A survey of options for providing a local virtual machine hosting / cloud type services.

Deliverables: A document listing options and known requirements.

Why:

Customer: Primarily computing team to decide whether producing a service is worth doing and, if so, what technology to use.

Case statement:

When:

Status:

Timescales: This should be done between now and Christmas

Priority:

Time:

How:

Proposal:

Resources: One week

Plan: Look at cloud technologies and generate a list of those we could deliver
Look at technologies Currently available in the university.
Look at any current provision within the school.

Formulate a list of questions
generate an online survey and submit to staff/phd students

Other:

Dependencies: None

Risks: None

Milestones

Achieved date	Name	Description
2013-01-03	results	Collate results of survey
2012-12-03	Publish	Publish the survery to general staff
2012-11-25	pilot	Generate a pilot survey and pass to cos for comments
2012-11-10	survey	Decide on survey provider and familiarise with it's use.
2012-11-22	review	Review current tech and finalise possible platforms.

Laptop support - produce platform specific documentation for DICE services

boss — Fri, 25 Jan 2013 15:46:26 +0000

Project ID:

253

Current stage:

Manager:

Unit:

What:

Description: Project 147, "Implement strategy for self-supported machines", identified that

"Our current systems documentation has, in recent years, become somewhat disorganised and hard to navigate. It was originally targeted at DICE desktop users and pays only lip service to providing information and advice to users of self managed machines."

Project 161 also identified documentation as being important.

This project will add the following documentation :-

instructions on how to configure the major platforms (Windows, MacOS, Linux) for each of our services (e.g. AFS, printing, backups, OpenVPN, kerberos)
notes on suggested modes of working. For example, staff use a variety of different schemes managing their files, and it is felt that this would be useful to document these to provide guidance to others.
recommendations for different software to use for common tasks.
HOWTOs, e.g. on how to encrypt your data

Deliverables:

Why:

Customer:

Case statement:

When:

Status:

Timescales:

Priority:

Time:

How:

Proposal:

Resources:

Plan:

Other:

Dependencies:

Risks:

Milestones

Proposed date	Achieved date	Name	Description

Documentation update - head of computing

boss — Fri, 25 Jan 2013 15:46:25 +0000

Project ID:

249

Current stage:

Manager:

Unit:

What:

Description: Review and update end-user documentation. Includes porting across any remaining documentation not already on new drupal based site.

Deliverables:

Why:

Customer:

Case statement:

When:

Status:

Timescales:

Priority:

Time:

How:

Proposal:

Resources: 0.5 week effort

Plan:

Other:

Dependencies:

Risks:

Milestones

Proposed date	Achieved date	Name	Description

Windows 7 upgrade

boss — Fri, 25 Jan 2013 15:46:21 +0000

Project ID:

229

Current stage:

5_Completed

Manager:

alisond

Unit:

What:

Description: All our Managed Desktops need to be upgraded to Windows 7.

Deliverables: Upgrade to all current MDP machines to Windows 7 along with training for CSOs and end-users.

Why:

Customer: All our MDP users

Case statement:

When:

Status:

Timescales: Dependant on IS, ISS and testing of kerberos and openAFS.

Priority: High

Time:

How:

Proposal:

Resources: This will require some Windows 7 and Office 2010 training.

Plan:

Meeting with IS in early January
Install test machine for kerberos and OpenAFS
Purchase software licenses
Liaise with ISS
Resolve Firefox version issue
Resolve printer installation
Arrange training for CSOs
Identify training for end users
Schedule upgrades with end users

Other:

Dependencies:

IS timetable for updates.
CSO training in installation of MDP (Windows 7) and software
Testing of kerberos and openAFS, including Toby's time.
Purchase of appropriate licenses (Windows 7, Office 2010 and Acrobat)

Risks:

Milestones

Proposed date	Achieved date	Name	Description
2012-01-10	2012-01-15	IS Meeting	To meet with Myles Ewen to discuss implementation and setting up of test machine including advice on how to install kerberos and openAFS.
2012-01-11	2012-01-31	Test Machine	Install test machine to allow us to test kerberos and openAFS
2012-02-29	2012-02-15	software	Test kerberos and openAFS
	2012-03-31	CSO training	Training in MDP installation.
	2012-03-31	ISS Meeting	Meet with ISS to discuss scheduling of upgrades. Dependent on solution for AFS/kerberos.
	2012-03-31	Purchases	Purchase all necessary upgrade licenses.
	2012-03-31	User testing	Ask competent end-user to help test. Dependent on AFS/kerberos solution.
2012-01-20	2012-01-20	List of upgrade	Identify complete list of machine upgrades.
	2012-03-15	Timetable	Create timetable of user upgrades
	2012-04-16	Upgrades	Start upgrades
	2012-03-31	firefox	Work out best options for firefox versions for theon/e-financials. Possibly use Google Chrome ?
	2012-04-30	printers	review way printers are installed - could/should they be IS queues?

Provide support for REF 2012

boss — Fri, 25 Jan 2013 15:46:21 +0000

Project ID:

232

Current stage:

Manager:

Unit: