Cloud bursting methodology
•Download as PPTX, PDF•
1 like•1,029 views
A methodology I developed a while back, for more of a military application, that I'm not revamping to fit a consumer model. I thought I would share the presentation, in the hopes that it will spark some interest in conversations, and maybe educate the public, not only on cloud computing as a whole, but also that bursting as it is portrayed, is not only a public cloud resource.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Cloud bursting methodology
Similar to Cloud bursting methodology (20)
Recently uploaded
Recently uploaded (20)
Cloud bursting methodology
- 1. Accolades Firstly, I’d like to thank everyone attending, taking the time out of their day, and allowing me to present… This methodology was developed for military application, and therefore this presentation is the theory of applying this same methodology to a more consumer based model…
- 2. Cloud Burst Methodology • Methodology • Explanations of Cloud Burst Methods • Network Access Methodologies – Inclusive of Cloud Bursting • Identity Management Methodologies, inclusive of Cloud Bursting • Special Purpose Computing – Cloud Bursting • Business and Use Cases Applied to Special Purpose Computing • High Level Architecture Walkthrough • Q & A
- 3. Cloud Burst Methodology Cloud Burst Methodology is the practical theory, and application of, the formation of an autonomous cloud computing fabric, intended for the creation of dedicated fabrics, established for single use, to officiate a process/mission/directive, after which that fabrics contents are then warehoused, and the core destroyed, eliminating any access structure and/or access to the data. The data is warehoused in a separate environment, with exclusionary access rights, different from and in contrast to the rights assessed within the special purpose fabric.
- 4. Cloud Burst Methodologies - Explained The concept of ‘Cloud Burst Methodology’ came from a project named ‘MVII’ Vehicle Intelligence Initiative for Mobility, and the use of a technology terms Ad-Hoc VPN spawning. Ad-Hoc VPN spawning would occur, as one MVII equipped car approached another, creating an Ad-Hoc network VPN, via a spontaneously created network access key, then piggybacking to the POP (Point of Presence). The process in which, was spontaneously created, made the chance of penetration, or intrusion almost negligible.
- 5. Network Access Methodologies – Explained The key purpose of Network, or Systems security is to create an environment where security ‘remediation’ was osmotic, establishing a healthy environment where CISO’s could rectify issues. The key issue here is the word remediate, meaning to cure a defect, and/or issue. Even with the current behavioral ‘AI’ technology being implemented within standardized Network Security platforms, we are still ‘remediating’ network penetration issues rather then proactively avoiding them.
- 6. Security Implications Such as, in any network access structure, the more perpetual time, users, and traffic in/out of even a contained network unit increases the possibility of penetration and/or intrusion, either by an internal, or external entities.
- 7. Access Management Solutions Cloud Burst methodologies can, by proxy, mitigate possible penetrations/intrusions, not by instantiating new network protocols, but by limiting access, to single use fabrics, disallowing perpetual access by utilizing these units for special purpose computing procedures…
- 8. Special Purpose Computing Solutions • Special Purpose (Use) Computing – Using special purpose fabrics, for single use computing instances • Such as transactional processing during high traffic periods • Limit Network Accessibility – By limited access • Access Control – By instantiating spontaneous user controls • Identity Management
- 9. Access Management Architecture Special purpose computing reduces the chances of intrusion by establishing access rights, via 1024 bit encrypted keys, spontaneously created at instantiation. These key pairs have a half life, that of the users access capabilities and or accessibility, and are tied to that specific fabric.
- 10. Cloud Burst Methodology • Practical Applications – Business Cases – Use Cases • Best Practices – Methodology – Architecture
- 11. Practical Applications of a Cloud Burst Methodology • Originally designed surrounding a military application – Other potential applications • High traffic, high volume shopping seasons – PCI, and SOX compliancy packages • Compliancy driven arenas, such as health care, specifically in disaster situations – HIPAA, PCI, and SOX compliancy packages • Mergers and Acquisitions – SOX, and other compliancy packages
- 12. Business Case – Retail Problem: Majority of credit, checking account, and identity theft occurs during high traffic seasonal shopping periods • Christmas, Thanksgiving, Easter, New Release, other applications Solution: Using a derivative of a Cloud Burst Methodology, onboarding compliancy packages, you can process transactions, utilize CRM packages, create management protocols, and destroy the fabric after use, thereby eliminating all access control assigned to that fabric, and any other associations…
- 13. Business Case – Medical HIPAA Problem: In 2014 the clinical application, of the new HIPAA laws, will come into effect. HIPAA will now not only govern patient care, but also the application of new laws surrounding DLP, Network Security, and systems hardening… • Patient file storage • Patient demographic storage • Medical records storage • Patient care applications Solution: Using a derivative of a Cloud Burst Methodology, onboarding compliancy packages, you can establish special purpose cloud to officiate disaster initiatives, such as Hurricane Katrina, or Sandy, for the soul purpose of medical care, storage of documents, patients data, morgue and autopsy data. This would allow that facility to bring a fully functioning, prebuilt fabric, up in minutes. This in turn would allow unfettered access, limited by the half-life of the assessors credentials, for a certain time period, and/or until that fabrics life has expired; in turn allowing life saving medical information to be shared, safely and in a secure environment, for the time allotted.
- 14. Business Case – Financial Problem: XXX Solution: XXX
- 15. Introduction to the Stack • Intro to hardware and support infrastructure • Hardware – Vendor Blade Servers • HP, IBM, Cisco choices, the original theory was to utilize HP equipment, i.e. 25 ‘C’ series HP Blade Servers • Software
- 16. Stack Architecture • Hardware – Vendor Blade Servers • HP, IBM, Cisco choices, the original theory was to utilize HP equipment, i.e. 3 pools, consisting of, 24 (8 per chassis per pool) ‘C’ series HP Blade Servers, in a (3) NetApp 500 TB Flexpod Configurations • Software – Orchestration and Server Automation – Access Management, Identity Management – Management Portal – User Authentication Portal – User Environment
- 17. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 18. Management Environment • Administration Portal – Controls Orchestration • Creation of Flows • Delivery of Special Purpose Infrastructure – Access Control • Management of Access Control – Identity Management • Control and input of Identity Management Environment
- 19. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Admin Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 20. Special Purpose Computing Environment Instantiation • Request would be initialized by internal ticket – Flow would be built • Providing the functionality, and in this case compliancy packages, were pre-built, would then be injected into the flow – Package retrieval • Golden (or Root) images, originally a mission protocol, built into image form, with precise locations, mission status, mission scope, so on – Package Instantiation • Flow would be initialized and executed, based on predetermined requirements • Authentication keys are generated, based on prerequisites
- 21. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Admin Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 22. Identity Management • Access Rights – Keys would then be assigned to mission handlers, i.e. mission stakeholders, or in this case project stakeholders • Identity Management – Keys would then be assigned to mission executors, i.e. operatives, in this case project managers
- 23. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 24. Pass-through or pass-off • Administrators would then be reassigned, and ownership passed off to the mission, or in this case project, stakeholders – Although the pass-off has take place, administrators still have some authority for break/fix scenarios
- 25. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 26. Authentication Process • Mission, or in this case project, stakeholders take control of the Special Purpose Computing environment
- 27. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 28. Next Steps – Authentication Process • Mission, or in this case project, stakeholders assign operators • Verify requirements • Identify key processes • In this case, execute compliancy packages At this point the half life of the authentication process has been initiated
- 29. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 30. Access Rights • Mission (project) stakeholders initiate operators requested identities – Access is granted to operators
- 31. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 32. Contained User Authentication Portal • Mission (project) operators take control of the user environment, and execute requested protocols – This pertains to mission, or project status, mission, or project objectives
- 33. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Fabric Instance 2 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 34. Repetition • The same protocols and procedures would be executed, in order, subsequent to further instantiations… • After each mission, or in this case project, concludes, the fabrics’ data is warehoused, and the core destroyed, taking with it all keys associated, as well as access rights granted… – Pass-off is then given back to the administrators, to access raw data collected • Event correlation, data mining, so on, is initiated • Depending on the department and/or organization, internal handling of the data will differ…
- 35. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Fabric Instance 2 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure User Owner Instance Control Users POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 36. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Fabric Instance 2 Fabric Instance 3 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure User Owner Instance Control Users POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 37. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Fabric Instance 2 Fabric Instance 3 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure User Owner Instance Control Users User Owner Instance Control Users POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 38. OPEN API LAYER Identity Management Access Control Process Management Service Oriented Architecture Application Servers/Middleware Orchestration Provisioning Element Management Event Correlation Storage Management Data Warehousing Access Layer Contained User Portal Environment Fabric Instance 1 Fabric Instance 2 Fabric Instance 3 Shared Components (Access Management) Cloud Bursting Methodology – High Level Reference Architecture Distributed Fabrics Management Control Environment Middleware Clients API Access Layers Data Warehouse User Owner Admin Instance Control Users Fabric Administrators Physical Infrstructure User Owner Instance Control Users User Owner Instance Control Users POOLS NAS NAS NAS Storage Network Provisioning Compute Provisioning Pool 1 Pool 2 Pool 3 Round Robin Load Balancing Algorithms
- 39. Conclusion As stated, at the beginning, of this presentation, originally this methodology was created for purely military application… However I have seen the necessity to carry it forward to more of a consumer application, such as fabrics that further more of a compliancy driven model. This being said, there would be a need for business and use cases to determine sustainability within that model, and subsequent configuration changes, if need be.
- 40. Presentation End Q & A Ladies and Gentlemen, thank you for your time and consideration… I look forward to working with you all, in the near future. Please feel free to contact me, with any questions… Jonathan Spindel Email: jspindel@ieee.org Phone: (954) 299-2132
Editor's Notes
- Firstly, I’d like to thank everyone attending, taking the time out of their day, and allowing me to present, I hope computing theory doesn’t bore you too much… What is cloud computing? Really an old idea, (spanning from the AS 400 series Mainframe days, which touted the early use of ‘Virtualization’, and ‘VDI’, Virtual Desktop Infrastructure), officiated with new technology. The reason I bring this up, is not to go into the typical NIST definition of cloud, as I’m sure we call know and understand the terminology, but to preface this presentation with a little bit of my personal career path, as it applies to this methodology. From the beginning of my career, I have been greatly interested, in what was originally termed ‘Distributed Networking and Computing’, as we know now, to be ‘Cloud’. My first introduction to ‘Cloud’ was in my early institutional years, and a project termed “Planet Lab’, which was created to serve as be a virtual lab, containing virtual slices, hosted by virtualized, light weight, Linux kernels. From there on out, I have pretty much focused on Cloud Computing, and the theory based research of distributed computing… The concept of a Cloud Burst methodology, as I’ll later explain more in depth, was originally applied to the Israeli Military, on my sabbatical in Israel, in reference to reconnaissance drone missions. Now there is only so much I can digress into the actual military model, however the presentation surrounds the application of this methodology in more of consumer based model. My intention is not to challenge current network or systems security methodologies, rather introduce a new application of those methodologies, in an innovative format.
- During this presentation I’d like to touch on several points, to bring across the overall definition of a Cloud Burst Methodology. Firstly I’d like to touch on the Methodology itself, then delve into a brief explanation of the methods, surrounding the methodology itself. After that brief overview, I’ll go into the network access, and identity management methodologies that go into the overall architect, then segue into, what I like to term, Special Purpose, or use, computing… Once we cover the overall methodology, I’ll digress into the business and use cases I felt to be an appropriate vehicle into the consumer marketplace, after which we’ll take a small dive into the high level architecture of the technology viewpoint of cloud bursting. I’ll end the presentation with a short Q & A session, however my objective is to cohesively tie this together, to avoid wasting too much of your valuable time.
- An introduction to Cloud Burst Methodology. The purpose of this application is the instantiation, in practical theory, is the formation of an autonomous unit, or special purpose, computing fabric. This fabrics’ creation hinges upon the application of a single use process, to officiate a mission, or in this case project objective, and to create a platform for those operators to work on, for a limited time period, in a safe/secure environment. After the mission/project has been executed and the process has been completed, the fabrics core then is destroyed, storing the raw data in a centralized warehouse, eliminating the access structure created, and or overall access to the data, by the original operators. The data, ultimately stored, in a different environment, with exclusionary access rights, different from, and in contract to, those issued to mission/project stake holders and/or operators.
- The idea, I coined a Cloud Burst Methodology, originally came from a DOT (Department of Transportation) project, I work on over a decade ago, named MVII (Vehicle Intelligence Initiative for Mobility. A project designed to use specially equipped vehicles, in more of a MESH network environment, using themselves as bouncing, or repeating points, for perpetual connectivity of the smart highway system. The idea, specifically came from, what is termed an ‘Ad-Hoc VPN, a spontaneous Virtual Private Network created for vehicles, in range, to bounce or repeat their signals, connecting to its’ parent a POP (Point of Presence) located along the freeways. This project was created in theory, and was a research grant, leading to an eventual design, but was before technology was able to support the magnanimity of this design. Nevertheless, I derived the idea, from the theoretical creation of that ‘Ad-Hoc’ VPN…
- The purpose of this slide, isn’t to argue the merits of a network/systems security platform, as they are a direct necessity to any secured environment. My main point is to highlight that regardless what protocols we set forth, or precautions we take, we still find ourselves trailing behind individuals who thoughts are to do harm with malice… Whether is be for recreation, the intention of syphoning funds from an account, or the unauthorized access of proprietary data, there will always be elements that intend to breach a network, we still find ourselves remediating those issues, rather then proactively avoiding them. By no means does this mean the parents network should not be protected, only that the fabric itself, since it’s inherent structure is one of spontaneity, simply reduces the risk of potential penetration, yet does not eliminate such risk, ergo that being said, a comprehensive support structure is certainly necessary.
- In reference to the last slide, again noting this methodology does not replace a comprehensive security support environment, it does however add to the efficiency, and reduce the chances of infiltration, corruption, or theft of data. Simply put, the more time we perpetually allow the same users, regardless of forced password or username changes, we by proxy, increase the chances of such an event transpiring… This methodology denotes that fact, and allows for the creation of a dynamic accessibility structure, with access rights assigned at instantiation, and after completion those rights are as if they never existed.
- The methodology itself was designed to utilize stealth tactics, such as spontaneous instantiation, access rights assigned at creation, utilizing a strong support structure, and destruction of the core, thereby destroying any access rights that were assigned at the flow level.
- Special purpose, or use, computing was a term coined in the early 1980’s, much like ‘Distributed Computing’, or ‘Cloud’, I’ve repurposed the term, (A LITTLE TANGENT) originally used for SUN Microsystems DEC VAX computers, in the study of lattice quantum chromodynamics (QCD), essentially the particles, specifically Quarks and Gluons, not to delve too far into particle physics, and truly make this already boring presentation much worse… loosely translated how particles, precisely related to the exchange proton particulates in an electromagnetically changed field. The term seemed to be a perfect fit, considering its’ course, and how this methodology, designed for military use, functioned to assess and execute a single task, such as a mission, project so on…
- Special purpose computing reduces the chances of intrusion by establishing access rights, via 1024 bit encrypted keys, spontaneously created at instantiation. These key pairs have a half life, that of the users access capabilities and or accessibility, and are tied to that specific fabric. Not to delve to far into encryption and access related to cryptography, as I don’t want to veer from the overall methodology, as currently the technology has changed, especially with VMware instituting 2048 bit encrypted keys…
- The application, or use, in other arenas is a practice I’ve only just started to address. Through some research, and common knowledge, associated with some of the assumptions I’ve made, I opted on three arenas, mentioned on the next slide. In theory, be at as it may, this methodology was originally designed specifically for military application, however as of late, some of the security procedures, being implemented in these three groups have adopted some of the same processes and procedures, making it a prime choice to hypothesize computing theory.
- As I’ve explained in the previous slides, Cloud Burst Methodology, was though of, and implemented in a military application. I’ve taken a few different private and public sector business cases, and put them to pen and paper, localizing their potential, as candidates, and categorizing the results based on necessity .
- Problem: Majority of credit, checking account, and identity theft occurs during high traffic seasonal shopping periods - Christmas, Thanksgiving, Easter, New Release, other applications Solution: Using a derivative of a Cloud Burst Methodology, onboarding compliancy packages, you can process transactions, utilize CRM packages, create management protocols, and destroy the fabric after use, thereby eliminating all access control assigned to that fabric, and any other associations…
- Problem: In 2014 the clinical application, of the new HIPAA laws, will come into effect. HIPAA will now not only govern patient care, but also the application of new laws surrounding DLP, Network Security, and systems hardening… - Patient file storage - Patient demographic storage - Medical records storage - Patient care applications Solution: Using a derivative of a Cloud Burst Methodology, onboarding compliancy packages, you can establish special purpose cloud to officiate disaster initiatives, such as Hurricane Katrina, or Sandy, for the soul purpose of medical care, storage of documents, patients data, morgue and autopsy data. This would allow that facility to bring a fully functioning, prebuilt fabric, up in minutes. This in turn would allow unfettered access, limited by the half-life of the assessors credentials, for a certain time period, and/or until that fabrics life has expired; in turn allowing life saving medical information to be shared, safely and in a secure environment, for the time allotted.
- I was going to write this amazing business case, for the financial sector, however with the IRS scandal, and every other god forsaken scandal out there, no one seems to be paying too much attention to them anymore anyway, so I thought we would just skip this section. No, truthfully, I just didn’t have enough time to do the due diligence necessary…
- Intro to hardware and support infrastructure Hardware Vendor Blade Servers HP, IBM, Cisco choices, the original theory was to utilize HP equipment, i.e. 25 ‘C’ series HP Blade Servers Software
- Hardware Vendor Blade Servers HP, IBM, Cisco choices, the original theory was to utilize HP equipment, i.e. 3 pools, consisting of, 24 (8 per chassis per pool) ‘C’ series HP Blade Servers, in a (3) NetApp 500 TB Flexpod Configurations Software Orchestration and Server Automation Access Management, Identity Management Management Portal User Authentication Portal User Environment
- This is a representation of a full stack, consisting of an several components mentioned before, namely the SOA backbone, infrastructure as a service model, orchestration, automation fabrics, as well as access control, identity management, and other shared components
- Administration Portal Controls Orchestration Creation of Flows Delivery of Special Purpose Infrastructure Access Control Management of Access Control Identity Management Control and input of Identity Management Environment
- Request would be initialized by internal ticket Flow would be built Providing the functionality, and in this case compliancy packages, were pre-built, would then be injected into the flow Package retrieval Golden (or Root) images, originally a mission protocol, built into image form, with precise locations, mission status, mission scope, so on Package Instantiation Flow would be initialized and executed, based on predetermined requirements Authentication keys are generated, based on prerequisites
- Access Rights Keys would then be assigned to mission handlers, i.e. mission stakeholders, or in this case project stakeholders Identity Management Keys would then be assigned to mission executors, i.e. operatives, in this case project managers
- Administrators would then be reassigned, and ownership passed off to the mission, or in this case project, stakeholders Although the pass-off has take place, administrators still have some authority for break/fix scenarios
- Mission, or in this case project, stakeholders take control of the Special Purpose Computing environment
- Mission, or in this case project, stakeholders assign operators Verify requirements Identify key processes In this case, execute compliancy packages At this point the half life of the authentication process has been initiated
- Mission (project) stakeholders initiate operators requested identities Access is granted to operators
- Mission (project) operators take control of the user environment, and execute requested protocols This pertains to mission, or project status, mission, or project objectives
- The same protocols and procedures would be executed, in order, subsequent to further instantiations… After each mission, or in this case project, concludes, the fabrics’ data is warehoused, and the core destroyed, taking with it all keys associated, as well as access rights granted… Pass-off is then given back to the administrators, to access raw data collected Event correlation, data mining, so on, is initiated Depending on the department and/or organization, internal handling of the data will differ…
- As stated, at the beginning, of this presentation, originally this methodology was created for purely military application… However I have seen the necessity to carry it forward to more of a consumer application, such as fabrics that further more of a compliancy driven model. This being said, there would be a need for business and use cases to determine sustainability within that model, and subsequent configuration changes, if need be.
- Ladies and Gentlemen, thank you so much for your time and consideration… I look forward to working with you all, in the near future. Please feel free to contact me, with any questions…