Toc

...

• Speaker info: Beth Cohen and Gergely Csatari Ildiko 
• Select a Track
  • Operationalizing Deployments: Case Studies, Successes, and Challenges

• Type of Submission

  • Panel Discussion ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).):

Theory and use cases are important, but what happens when the rubber hits the road, or in other words, when your edge infrastructure is ready to be deployed and run in production.  During this session we will look at the dependencies and requirements for successfully launching and managing edge architectures in the field. Grouped around the Telecom concept of what happens over the three "days" it takes to take an edge infrastructure from development to deployment and into production. Starting from “Day 0”, the preparation/development phase before the deployment so to speak, and moving into “Day 1”, the actual deployment into the field, followed by “Day 2” or Day N (depending on who you talk to) which includes the management of the systems in production, each step calls for different components that interrelate with each other. 

• • Day-0: "product development". Focus on bootstrapping, develop templates
  • Day-1: "service delivery". Instantiate/customize templates according to customer needs and deploy them. Validation.
  • Day-2: "production/operations"
• Audience (Describe who the audience is and what you expect them to gain from your presentation.)

...

The Open Source community tends to focus  on Day 0 or requirements, but increasingly the telecom industry is looking for community to standardize operations and deployment activities.  While the nomenclature is borrowed from the  telecommunications industry, but the steps are applicable on a much wider scale and many more industries. 

• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

...

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Cultural Transition: Open Source Across Telecom and Hyperscalers

• Speaker info:
  • Primary Speaker Scot Steele
  • Primary Speaker Microsoft
  • Primary Speaker Sr. Program Manager
  • Primary Speaker scotsteele@microsoft.com
  • Primary Speaker USA
  • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
  • Primary Speaker Twitter Handle
  • Primary Speaker www.linkedin.com/in/scotsteele
  • What gender does the primary speaker identify with? Male
  • Does the primary speaker identify as a person of color? No
  • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below. None
• Select a Track
• • Looking Ahead: Emerging Technologies and Business Models

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract Title Cultural Transition: Open Source Across Telecom and Hyperscalers
• Abstract 

  As telecommunications is a backbone service to society the industry has been highly regulated since its inception. Thus Telcos must demonstrate a culture of high levels of operational availability, reliability, and recoverability in performance and cost management. Hyperscalers are relatively new entities in the communications space that leverage a more collaborative/adoptive culture with lesser concern for the operational efficiency. Open-Source specifications/code, and Hyperscaler partnerships can provide new features and greater capacities to their consumers with reduced time to market and lower capital costs. However, deltas between the operational efficiency culture of operators and the collaboration/adoption of hyperscalers could inhibit success on either side of the relationship. We posit that resolving conflict between cultures would allow consumer access to beneficial features that would improve the operator’s bottom line at a time when labor and cost challenges impact the industry’s overall growth and health.

  In this discussion, we ask the question “How can Open-Source impact and affect culture to support telco industry growth and health?” We will explore insights and possible paths through the lens of a significant and multi-faceted telco hyperscaler partnership.

• Audience: anyone Involved with technology selection, deployment, management, and leadership in the telco industry
• Benefits to the Ecosystem Transforming the culture of the industry to a more trusting, collaborative, and adoption mentality will provide numerous benefits to all participants through the improving the speed of development and adoption. This will generally support lower cost of implementation.
• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
• Have you given this presentation before? o
• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement