1 / 14

AppInf overview

jan g. AppInf overview. 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.

schuyler
Télécharger la présentation

AppInf overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. jan g. AppInf overview

  2. What's done • What's left to do (software) • What's left to do (hardware)

  3. 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?

  4. Model: farm of hosts • (diagram here)

  5. 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

  6. Deployment from a central configuration point • (diagram)

  7. Target applications • uPortal • difficulty: SSO • portal channels • difficulty: JNI for calendar • Other tomcat • blackboard, AFID, ISIS, etc. • Non-tomcat • OAS, PHP, ...

  8. Other potential applications • Non-webapp • mail spam filters? • ...?

  9. What's done • Low-level operations webapp: conf dir/ image/ image.war context.xml script/ parameterise-sso container-group front-end-host required-services

  10. 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)

  11. 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)

  12. 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.

  13. 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

  14. Physical networking • (decisions needed: options outlined... diagram)

More Related