Line 71: |
Line 71: |
| {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" | | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| |- | | |- |
− | |<b>Session 1: Is your Cloud Centre of Excellence Breaking Cloud? </b> ([https://youtu.be/krFvmSFS7fA Join session]) | + | |<b>Session 1: Whitelist App: First to the Cloud </b> (Join session) |
| |- | | |- |
− | |June 11th, 2:30 - 3:00 | + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Jayson McIntosh, Omar Nasr |
| + | |- |
| + | |Employment and Social Development Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Coming soon <br> |
| + | Blog: https://sara-sabr.github.io/ITStrategy/2020/05/20/Team-Topologies-Whitelisting-app.html <br> |
| + | Presentation: https://sara-sabr.github.io/ITStrategy/presentation.html?markdown=en/2020-06-03-Whitelist-Showcase.md <br> |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 2: Journey to the Cloud on Boats, Automobiles, Trains, and Planes - Part 2: We have lift-off! </b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Kofi Arthiabah, Joyce Lee |
| + | |- |
| + | |Transport Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Part two of our movie themed story of TC's Journey to the Cloud : The lift off phase. We discuss Cloud Adoption, Workload Migration, Launching a protected-B application (before SCED), partnerships, taking risks, automation and sharing Microsoft 365 and Teams. COVID as a driver - it's got it all. Join us for some edge of your seat stuff! |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 3: High Performance Computing in the Cloud</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Greg Cormier |
| + | |- |
| + | |Department of Fisheries and Oceans |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |High Performance Computing is powering scientific research that informs public policy and impacts the lives of Canadians. Scientists are seeking every growing compute and storage capacity for analysis and modeling. Learn from the Department of Fisheries and Oceans’ experience with HPC on Azure. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 4: TBS adoption of Agile, DevOps, and Cloud</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Paul Girard, Sevac Eskibashian |
| + | |- |
| + | |Treasury Board of Canada Secretariat |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |How did the IT organization at TBS shift from being behind on technology to leading the way? This session will tell the story and how other government departments can leverage the some of the lessons learned of TBS. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 5: Cloud Service Offerings and Workload Migration at ISED</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |PHouda Hamdane, Artur Przybylo |
| + | |- |
| + | |Innovation, Science, and Economic Development |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |ISED has initiated a Work Load Migration (WLM) and transformation initiative to modernize its workloads and move to the Cloud. The initiative is big and the impact on the way ISED delivers IT services is huge which requires a clear Cloud Strategy and a solid understanding of what Cloud Service offerings and practices are going to be used for the migrations. The presentation focuses on how ISED is organizing its Cloud Service offerings to execute efficiently its work load migrations to the Cloud |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 6: Integrating custom applications into Microsoft Teams platform for interoperability with on-premise systems</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Chang Shu |
| + | |- |
| + | |Public Services and Procurement Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Microsoft Teams has quickly become the ultimate collaboration and teamwork application. Users can add, customize, and find everything they need in one place without the need to navigate to different places. Custom applications hosted in a cloud environment can interact with on-premise systems through APIs. The custom applications can be further integrated into Teams or other M365 components to expose the data and functionalities of the on-premise systems. Integrating custom applications and services into Teams platform can improve the productivity, provide focus and enhance collaboration. The presentation will go through the following parts: |
| + | |
| + | 1. Interoperability between SaaS-based solutions and GC internal resources in accordance with the security standard; |
| + | 2. Exposing on-premise data and business logic through APIs; |
| + | 3. Hosting a custom application in Azure; |
| + | 4. Integrating a custom application with Teams; |
| + | 5. Live demonstration to show how it works. |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 7: “Hello Pro-B World”</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Gray O'Byrne |
| + | |- |
| + | |Treasury Board of Canada Secretariat |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Thought experiment: How much would it cost you to stand up a bare-bones web page in government that was “approved” to collect personal information. In other words, what’s the price tag for a government site that only says: “Hello world” but had gone through all the paperwork, infrastructure setup and approvals for collecting “Protected B” information. For our small project we estimate it's been over $500,000... and we're not there yet. This is unfortunately a near insurmountable burden for experimental projects that will greatly limit innovation in the GoC if it persist. |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 8: Building for Automation</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Mike Williamson |
| + | |- |
| + | |Treasury Board of Canada Secretariat |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |TBS Cyber's Tracker project will scan web and email security settings to automate compliance. Automating compliance more broadly will require more than TLS and DNS settings to be observable. Everything from workflow to infrastructure to the running system needs to be programmatically inspectable. This talk will center on work TBS Cyber is doing to build systems in a way that enables automated analysis and lay the foundation for automated compliance. |
| + | |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 9: Can a ‘horizontal cloud’ approach leveraging leading edge geospatial technology revolutionize the way departments and agencies respond to future emergencies?</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Janice Sharpe, Executive Director, FGP. & Chris Melnick-MacDonald, Enterprise Architect, COVID-19 Cloud, FGP |
| + | |- |
| + | |Natural Resources Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |The sudden onset of the COVID-19 pandemic in Canada, and the crucial need for public situational awareness, brought several departments together with an urgent and shared requirement for a means to create and deliver key data and information to decision-makers and the public. Within 72 hours of the ask for a shared cloud environment, Natural Resources Canada’s Federal Geospatial Platform team deployed a horizontal, multi-jurisdictional, geospatially enabled cloud that provided Public Health Agency Canada, Statistics Canada and NRCan, as well as provincial, territorial and private sector partners, with a shared environment for the rapid consolidation of key data, which was used to create online data visualizations and situational dashboards to inform on the unfolding crisis. Updated every 12 hours, the online maps and dashboards are publically available on the PHAC web site and are used in daily briefings with Canada’s Chief Public Health Officer, Dr. Tam. |
| + | <br> |
| + | The quick and agile deployment and marked success of the COVID-19 horizontal cloud has shown the true potential of an open, horizontal, cloud-based platform when working across jurisdictions. From the geospatial perspective, the COVID-19 cloud clearly demonstrates how the federal government can work effectively, across departmental and jurisdictional boundaries, and respond to crises in a timely manner. In this presentation, we will explain how a horizontal cloud approach that leverages leading edge geospatial information could revolutionize the way departments and agencies respond to future emergencies: how the collaboration was formed and governed, what technology was put into place, how the data was shaped and presented, and the key outcomes of this highly successful collaboration. |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 10: From communications systems research to public health: pivoting in the cloud to address Covid-19</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Neil O'Brien, Sarah Dumoulin |
| + | |- |
| + | |Communications Research Centre |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |The Communications Research Centre’s (CRC’s) Virtual Research Domain (VRD) is a cloud-based data processing and research environment. CRC’s data science team works in the VRD on big data problems relating to wireless telecommunications. When the pandemic hit, CRC was able to quickly pivot, repurposing existing research and data sets to study and measure mobility metrics for the Public Health Agency of Canada (PHAC). Learn how the VRD and access to hundreds of terabytes of anonymous telecommunications data allowed the CRC to help PHAC understand how Canadians were self-isolating. |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 11: DAaaS: Data Analytics as a Service using CNCF technologies</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |William Hearn, Zachary Seguin |
| + | |- |
| + | |Statistics Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |In response to COVID-19, Statistics Canada quickly developed it's Data Analytics as a Service platform using Kubernetes, CNCF, Kubeflow and other cloud native technologies to quicky empower the department's data scientists in an isolated section of our public cloud infrastructure. Developed entirely in the open on GitHub, this talk focues on the technologies, the processes and the lessons learned in quickly responding to a challenge. The environment is fully automated using Terraform for Infrastructure as Code, and GitHub Actions for CI/CD. (https://github.com/StatCan/daaas) |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 12: Learning from failure while innovating</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |William Hearn, Zachary Seguin |
| + | |- |
| + | |Statistics Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Cloud technology is quicky advancing, and with it comes larger opportunities for failure whether human led, system led or both. This talk covers some of the different failures that the Cloud Native Platform team at Statistics Canada has encountered while building a platform based on Kubernetes, CNCF and other open source technologies and growing as a team. On the human front, we'll focus on how errors can easily happen and how we can learn from them to prevent them from occurring again. On the system front, we'll walk through how to identify the problem and working with the community to find a resolution. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 13: Advanced Analytics Workspace: Rapidly Deploying Data Science Capabilities in the Cloud</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Brendan Gadd, Christian Ritter |
| + | |- |
| + | |Statistics Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |We would like to share our story of how we rapidly deployed a modern and open analytics platform in the face of the COVID-19 pandemic. Using a combination of Azure platform-as-a-service and open-source technology, we were able to deliver core analysis and collaboration capabilities to our data scientists – accessible from home equipment – within fifteen business days. |
| + | We will cover topics such as: |
| + | * Partnership: Creating a multidisciplinary team across the organization to contribute directly to the platform. |
| + | * Azure Services: How we leveraged core cloud services to enable authentication for internal and external users across loosely coupled components. |
| + | * Process: Lightweight agile methodology, working in the open, and leveraging GitHub for repository management and CI/CD. |
| + | * Tooling: Some of the open tools and services we set up that give scientists quick access to auto-scaling compute, storage, and specialized hardware (e.g. GPUs). |
| + | * Example use case: Demonstrate an actual data science product created using our Advanced Analytics Workspace. |
| + | |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 14: Fold The North - How the GC public servants mobilized. Grass roots style</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |John Bain |
| + | |- |
| + | |Shared Services Canada |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |How the group formed using cloud apps. |
| + | How we self organized and collaborated using cloud apps. |
| + | How we used social media platforms to get our message out. |
| + | How we selfserved purchased our own infrastructure. |
| + | What we're trying to do related to Protein Folding and our recruitment message. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 15: Cloud adoption: accomplishments and lessons learned</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Ari Rizvi, Scott Levac |
| + | |- |
| + | |Shared Services Canada & Treasury Board of Canada Secretariat |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |Discuss the accomplishments on cloud adoption across the GC (brokerage, intake, auditing, accelerators, etc.) and the lessons learned. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 16: Azure Landing Zone and Guardrails Compliance Testing</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| + | |- |
| + | |Gerald Hill, Tarek Ali |
| + | |- |
| + | |Shared Services Canada & Treasury Board of Canada Secretariat |
| + | |- |
| + | |Level 100 - Beginner |
| + | |- |
| + | |The first part would be to present Azure Landing Zone developed by SSC to the GC. What was done, what were the needs, the challenges, and the avenues to explore. The second part will be focused on demonstrating the guardrails compliance tool. |
| + | |} |
| + | <br> |
| + | |} |
| + | |
| + | |
| + | |
| + | |
| + | {|style="width: 70%; background-color:#fff3d9; border-left: 10px solid #392F41; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);" |
| + | |- |
| + | |<b>Session 17: Evaluating Technical Lock-in</b> (Join session) |
| + | |- |
| + | |October 6th ?h00 to ?h00 |
| |- | | |- |
| |Scott Levac | | |Scott Levac |
Line 81: |
Line 422: |
| |Level 100 - Beginner | | |Level 100 - Beginner |
| |- | | |- |
− | |Departments are turning to Cloud Centres of Excellence (CCoE) to lead their cloud adoption. CCoEs should avoid traditional governance and operations structures in place if they want to maximize the agility of cloud. | + | |With increased reliance on commercial cloud services comes increased fears of risking technical lock-in. This fear, however, can unjustly lead organisations to ?? the opportuntity gained from platforms services that offer a lower operational burden, increase cost control, and short lead times. ??? |
| + | |
| |} | | |} |
| <br> | | <br> |
| |} | | |} |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| | | |
| | | |