moving e government to the cloud
TRANSCRIPT
![Page 2: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/2.jpg)
Open source software
• A license that legally give the right to,
– Run the program for any purpose
– Study and modify the program
– Redistribute the program (in modified and unmodified states)
• Free software, OSS, FOSS, FLOSS
• Many licenses
– http://opensource.org/licenses/alphabetical
![Page 3: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/3.jpg)
Why open source?
• Brings transparency
• Faster security fixes/patches
• Use of open standards
• Broad usage in many verticals
• Commercial support available
• Used in many business critical applications
![Page 4: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/4.jpg)
Why open source in government?
• Transparency – Not at the mercy of a proprietary vendor
• Detailed evaluation before using – Evaluation of different aspects – functionality, security, extensibility
– Open forums for discussion, bug tracking, community
• No vendor lock-in – Use of open standards, many providers of commercial support
![Page 5: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/5.jpg)
Cloud computing
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider
interaction. - National Institute of Standards and Technology (NIST – www.nist.gov)
![Page 6: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/6.jpg)
Cloud computing characteristics
• On-demand self service – CPU, storage, RAM - without an admin
• Broad network access – Accessible over a network
• Resource pooling – Accessibility through a multi-tenant model
• Rapid elasticity
• Measured service
![Page 7: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/7.jpg)
Service models
• Software as a Service (SaaS) – Application running on the cloud
– Accessed from web, mobile, native apps
• Platform as a Service (PaaS) – Deploy applications into the cloud
– Provide libraries/frameworks/tools to build applications
• Infrastructure as a Service (IaaS) – Provision fundamental computing resources; CPU, RAM, storage etc…
– Has control from the operating system to deployed apps
![Page 8: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/8.jpg)
Deployment models
• Private cloud
• Community cloud – Provisioned to be used by a specific community of consumers
• Public cloud
• Hybrid cloud – Combination of two cloud infrastructures
– Technology enables data and application portability
– Used for cloud bursting
![Page 9: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/9.jpg)
Issues – Effective eGovernment
• Collection of massive amounts of data
• Scattered in different data repositories
• Transactions spanning multiple agencies
• Intergovernmental data access
• High capital and operational expenditure
• Provisioning resources become cumbersome
• Ensure data integrity of disparate systems
![Page 10: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/10.jpg)
Data collection
• Citizen data
• Documents needed for a specific function – Loan approval
– Vehicle license renewal etc…
• Importance of having a single consistent set of information about a citizen
![Page 11: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/11.jpg)
Scattered repositories
• A citizen can belong to a single province – The geographical area where he cast his vote
• Can have information scattered in different provinces
• Ability to view information from a central portal
![Page 12: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/12.jpg)
Transactions with multiple agencies
• Refer/executing processes from another local government agency (from another province/state)
• Authorization model that can grant permission to needed local agencies
How to solving these issues with a cloud native middleware platform in an eGovernment solution?
![Page 13: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/13.jpg)
Cloud Native Middleware • Elastic (Uses the cloud efficiently)
– Scales up and down as needed – Works with the underlying IaaS
• Self-service (in the hands of users) – De-centralized creation and management of tenants – Automated Governance across tenants
• Multi-tenant (Only costs when you use it) – Virtual isolated instances with near zero incremental cost – Implies you have a proper identity model
• Granularly Billed and Metered (pay for just what you use) – Allocate costs to exactly who uses them
• Distributed/Dynamically Wired (works properly in the cloud) – Supports deploying in a dynamically sized cluster – Finds services across applications even when they move
• Incrementally Deployed and Tested (seamless live upgrades) – Supports continuous update, side-by-side operation, in-place testing and
incremental production
![Page 14: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/14.jpg)
WSO2 middleware stack
![Page 15: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/15.jpg)
Flexible and agile
![Page 16: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/16.jpg)
WSO2 Carbon
![Page 17: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/17.jpg)
WSO2 Carbon
![Page 18: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/18.jpg)
WSO2 Carbon
![Page 19: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/19.jpg)
WSO2 Carbon
![Page 20: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/20.jpg)
WSO2 Carbon
![Page 21: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/21.jpg)
Cloud Native Middleware
![Page 22: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/22.jpg)
Importance of multi-tenancy
• Every service can support multiple tenants in the same container. A tenant is a local government agency or can be a state. – Higher efficiency, lower resources
– Can be split tenant per-VM using the MT-aware Load Balancer
• Isolation includes classloaders, code signing and Java security policies – Cross-tenant sharing is via the network (REST, SOAP, etc)
22
![Page 23: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/23.jpg)
Importance of multi-tenancy cont.
• Every tenant has all services by default but they can be turned off
• Central government deploying services that are common to all states/local/provincial agencies
• Provincial agencies can have their own services/business processes
• Provincial offices work on their dataset
![Page 24: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/24.jpg)
Importance of multi-tenancy cont.
• Central government can access the portal and can have a holistic view of the entire system
• Can find out detailed statistics about the operation of each local government agency
• If required a privileged user can perform activities of a local agency. Governed by authorization policies defined by the provincial agency
![Page 25: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/25.jpg)
Importance of multi-tenancy cont.
• Data and processes of a local agency is isolated from another. Can grant selective access via authorization policies (XACML)
• Flexibility of multi-tenant architecture – Ability to have a common set of functions across all local agencies and at the same time can have specific services/processes as well
![Page 26: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/26.jpg)
Architecture of the solution
![Page 27: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/27.jpg)
Architecture of the solution
• LG – Local Government Agency – Deployed
• Central operations – Public cloud deployment by the central government
– All local/provincial agencies have a tenant in Stratos (e-LG1, e-LG2 etc)
– eGov apps runs under each tenant
– e-LGs are isolated from each other (both data and execution)
![Page 28: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/28.jpg)
Architecture of the solution
• Some local agencies have good internet connection – e-LGn and e-LG(n-1)
– No local deployments
– Directly connects to central
– Application state and data for e-LG tenant in central cloud reflect the latest state
![Page 29: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/29.jpg)
Architecture of the solution
• Some local agencies does not have good internet connection – e-LG1 and e-LG2
– Applications/business processes deployed locally on-premise
– Applications deployed under the respective tenant in central for e-LG is synced with the local deployment of e-LG when the connection is available
– Application state and data on central reflect the last synced state
– Application state and data on e-LG local deployment always reflect the latest state
![Page 30: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/30.jpg)
References
• NIST cloud computing definition – http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf
• White paper: Moving eGovernment to the Cloud – http://wso2.com/whitepapers/moving-egovernment-to-the-cloud/
![Page 31: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/31.jpg)
Questions?
![Page 32: Moving E Government to the Cloud](https://reader033.vdocuments.net/reader033/viewer/2022060115/5575801fd8b42adb7e8b509c/html5/thumbnails/32.jpg)
Thank you!