1 / 17

Infra-SAN: Technical architecture buildup

Infra-SAN: Technical architecture buildup. Technical architecture buildup. Purpose :. Service driven Formalise the test definition and realisation Technical specifications are used to buildup the tests AIV (Assembly, Integration and validation) Is usable by architects and administrators

neal
Download Presentation

Infra-SAN: Technical architecture buildup

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. Infra-SAN: Technical architecture buildup

  2. Technical architecture buildup Purpose : • Service driven • Formalise the test definition and realisation • Technical specifications are used to buildup the tests • AIV (Assembly, Integration and validation) • Is usable by architects and administrators • Is the foundation for • ICDs (Interface Control Document) • Production manuals

  3. Detailed specs Proof of concept forms AIV Validation forms Integration forms Production manuals DRP analysis Technical architecture buildup How does it facilitate the project management ? Phase I Detailed specifications analysis Phase II - Services - Criterions Phase III : Installation Configuration Phase IV : Final Acceptance  Testing path  Proof of concept tests Refined tests Integration

  4. Technical architecture buildup Why should we use a framework?  Technical issues • Compatibility issues : • Internal: Inside an application • External: Outside the application (other applications) • Justify and document the choosen options • Exhaustive

  5. Technical architecture buildup Why should we use a framework?  Project management • Project documentation • Workload planning and schedules made easier • Services are the foundations for ICDs • Project knowledge management

  6. Technical architecture buildup Why should we use a framework?  Transition to production • Intel/ Linux masterisation and deployment • Tuning and performance • Backup procedures • HSM operations • Helps document the DRP procedures

  7. Technical architecture buildup Why should we use a framework?  Change management after project completion • Documents the component changes impacts • Versioned technical architecture

  8. Technical architecture buildup Phases : • Define services • Unitary validation • Internal and external integrations • Others : • ICDs • DRP • Operations

  9. Technical architecture buildup Glossary : • Service : Applications requirements to the infrastructure (Backups, Response Time, Security, etc.) • Component : a service for a particular application. Example : the backup service may have - A SAN snapshot for Application 1 - An Oracle cold backup for Application 2 - A file system backup for Application 3

  10. Technical architecture buildup Phase 1 : Service identification

  11. Technical architecture buildup Phase 1 : Service identification - HSM - Security - Response time - Backups - Linux systems - Availability - Data bases

  12. Technical architecture buildup Phase 2 : Component identification Apps Services

  13. Technical architecture buildup Component unitary validation : • Installation/ migration procedures • Detailed parameters : • Interfaces (Configuration files, paths within a tool, etc.) • Patches identification • Versions • Unitary tests

  14. Technical architecture buildup • Component unitary validation. One document per • service. • Main forms • Description (version, provider, documentation, • etc.) • Linked components for a given application • Validation criterion • Validation test • Anomalies • Non-regression tests

  15. Technical architecture buildup Integration. One document Internal: Inter applications linked components (example : response times) External: Links between the technical architecture and outside elements (example: PKI)

  16. Technical architecture buildup Integration : Main forms • Links identification • Integration tests • Anomalies • Non-regression tests

  17. Technical architecture buildup Conclusion : - Light overhead: formalise tasks that have otherwise to be done - Corner stone for the requested documents

More Related