AppInf overview

jan g.

● What's done● What's left to do (software)● What's left to do (hardware)

Questions to bear in mind

● does this meet our requirements?● can commercial software do any of this?

– is there real value there at the moment?

Model: farm of hosts

● (diagram here)

Use cases

● We have a number of groups of users:– SRCT, developers, webmasters, etc.

● Those users perform high-level operations● ...these expressed in terms of low-level operations

– operations on a software+configuration stack– that's a relatively static model– no permanent state on hosts

Deployment from a central configuration point

● (diagram)

Target applications

● uPortal– difficulty: SSO

● portal channels– difficulty: JNI for calendar

● Other tomcat– blackboard, AFID, ISIS, etc.

● Non-tomcat– OAS, PHP, ...

Other potential applications

● Non-webapp– mail spam filters?– ...?

What's done

● Low-level operationswebapp:

conf dir/

image/

image.war

context.xml

script/

parameterise-sso

container-group

front-end-host

required-services

What's done

● Host configuration: conf dir/

callback-sockets

deployment-data/ ssh keys

ip

mac-address

os-image

maint-user

(deployment state: deployed software etc)

What's to do:

● Software– Scripts for physical network topology

● (diagram in a minute)

– Some more tidying-up● pretty ready for testing

– Wrap up low-level operations into high-level scripts● (a few days)

What's to do: longer term

● Expand to push configurations to other software components– Nagios / other monitoring tools

● Other container types– OAS

● Related work– Performance, testing.

What's to do: hardware

● X4100s– waiting on power– physical configuration of network

● PXE/dhcp a constraint (need non-10-subnet ?)● Apache->AJP● Host -> wide world● Host -> oracle● Host -> bobcat/other NAS

Physical networking

● (decisions needed: options outlined... diagram)