This document provides an overview of KEMP load balancing solutions for Microsoft Lync/Skype for Business. It discusses load balancing of internal and external Lync services, demonstrates using KEMP-developed templates to configure devices, and leaves time for questions. The document includes links to information on KEMP's virtual and hardware load balancers, as well as templates for load balancing common Lync roles like Front End, Director, Edge, and Mediation servers.
More Data, More Problems: Scaling Kafka Mirroring Pipelines at LinkedInCelia Kung
For several years, LinkedIn has been using Kafka MirrorMaker as the mirroring solution for copying data between Kafka clusters across data centers. However, as LinkedIn data continued to grow, mirroring trillions of Kafka messages per day across data centers uncovered the scale limitations and operability challenges of Kafka MirrorMaker. To address these, we have developed a new mirroring solution, built on top our stream ingestion service, Brooklin. Brooklin’s mirroring solution aims to provide improved performance and stability, while facilitating better management via finer control of data pipelines. Through flushless Kafka produce, dynamic management of data pipelines, per-partition error handling and flow control, we are able to increase throughput, better withstand consume and produce failures and reduce overall operating costs. As a result, we have eliminated the major pain points of Kafka MirrorMaker.
In this talk, we will dive deeper into the challenges LinkedIn has faced with Kafka MirrorMaker, how we tackled them with Brooklin and our plans for iterating further on this new mirroring solution.
Next Generation Client APIs in Envoy MobileC4Media
Video and slides synchronized, mp3 and slide download available at URL https://bit.ly/2x0Fav8.
Jose Nino guides the audience through the journey of Mobile APIs at Lyft. He focuses on how the team has reaped the benefits of API generation to experiment with the network transport layer. He also discusses recent developments the team has made with Envoy Mobile and the roadmap ahead. Filmed at qconlondon.com.
Jose Nino works as a Software Engineer at Lyft.
Using Perforce Data in Development at TableauPerforce
Data plays a big role at Tableau—not just for our customers, but also throughout our company. Using our own products is not only one of our fundamental company values, but the analysis and discoveries we make are important to track as they shape our development processes and influence our day-to-day decisions. In this talk, we present and analyze a variety of data visualizations based on Perforce data from our development organization and share how it has influenced our infrastructure and development practices.
More Data, More Problems: Scaling Kafka Mirroring Pipelines at LinkedInCelia Kung
For several years, LinkedIn has been using Kafka MirrorMaker as the mirroring solution for copying data between Kafka clusters across data centers. However, as LinkedIn data continued to grow, mirroring trillions of Kafka messages per day across data centers uncovered the scale limitations and operability challenges of Kafka MirrorMaker. To address these, we have developed a new mirroring solution, built on top our stream ingestion service, Brooklin. Brooklin’s mirroring solution aims to provide improved performance and stability, while facilitating better management via finer control of data pipelines. Through flushless Kafka produce, dynamic management of data pipelines, per-partition error handling and flow control, we are able to increase throughput, better withstand consume and produce failures and reduce overall operating costs. As a result, we have eliminated the major pain points of Kafka MirrorMaker.
In this talk, we will dive deeper into the challenges LinkedIn has faced with Kafka MirrorMaker, how we tackled them with Brooklin and our plans for iterating further on this new mirroring solution.
Next Generation Client APIs in Envoy MobileC4Media
Video and slides synchronized, mp3 and slide download available at URL https://bit.ly/2x0Fav8.
Jose Nino guides the audience through the journey of Mobile APIs at Lyft. He focuses on how the team has reaped the benefits of API generation to experiment with the network transport layer. He also discusses recent developments the team has made with Envoy Mobile and the roadmap ahead. Filmed at qconlondon.com.
Jose Nino works as a Software Engineer at Lyft.
Using Perforce Data in Development at TableauPerforce
Data plays a big role at Tableau—not just for our customers, but also throughout our company. Using our own products is not only one of our fundamental company values, but the analysis and discoveries we make are important to track as they shape our development processes and influence our day-to-day decisions. In this talk, we present and analyze a variety of data visualizations based on Perforce data from our development organization and share how it has influenced our infrastructure and development practices.
Introduction to Data Models & Cisco's NextGen Device Level APIs: an overviewCisco DevNet
A session in the DevNet Zone at Cisco Live, Berlin. The need to automate interactions with the network is ever more obvious. We have a plethora of tools built around legacy technologies, such as SNMP and screen scraping, but these are coming to the end of their useful lives. In this introductory talk we will look at how YANG data models are becoming ever more pervasive across networking, and how they may be used to more efficiently automating network configuration and operational management.
Perforce Helix Never Dies: DevOps at Bandai Namco StudiosPerforce
Traditionally at Bandai Namco Studios, there has been no unified version control system in place and teams could choose to use any VCS system for their game titles—Subversion, Git, AlienBrain, or none at all. I’ll talk about why Bandai Namco Studios chose to standardize on Perforce Helix, show how we develop LiveOps-type mobile applications using the Unity game engine, and the advantages we gain from centrally managing code and assets in Helix.
Le SDN et NFV sont très à la mode en ce moment car en passant des appliance physiques aux équipement réseau massivement logiciel, celà devrait offrir une grande flexibilité et agilité aux entreprises (et telco en particulier). Néanmoins chainer des services réseau est un exercice encore très complexe et ce document vous explique ce qu'il est déjà possible de faire sur OpenStack en couplant par exemple : un load balancer (BigIP), un Firewall (BigIP), un réseau virtuel WAN (RiverBed) ou encore un routeur virtuel (Brocade).
Virtual Flink Forward 2020: Integrate Flink with Kubernetes natively - Yang WangFlink Forward
Currently Flink supports the resource management system YARN and Mesos. However, they were not designed for fast moving cloud native architectures, and they could not support mixed workloads (e.g. batch, streaming, deep learning, web services, etc.) relatively well. At the same time, Kubernetes is evolving very fast to fill those gaps and become the de-facto orchestration framework. So running Flink on Kubernetes is a very basic requirement for many users. In this talk, firstly we will quickly go through Kubernetes architecture and the efforts we have been made to run Flink on Kubernetes. Then we deep dive into the technical details about how to make Flink natively run on Kubernetes. Native means Flink KubernetesResourceManager calls directly the Kubernetes APIs to allocate and release TaskManager pods. Next we will share some practices of application lifecycle management and production optimizations (e.g. high-availability, storage, network, etc.). Finally, we will conclude the talk with advantages for Flink on Kubernetes and a simple demo. This talk is aimed at users and companies who are looking to run Flink on Kubernetes cluster. We assume that the listener has some basic knowledge of cluster orchestration and containers.
Jan Lindblad's presentation at Layer123 SDN and OpenFlow World Congress in Bad Homburg, Germany. Focusing on a multi-vendor SDN deployment at a Tier 1 Service Provider in Asia.
Tail-f Network Control System (NCS) use case:
• Dynamic control of L3-L7 devices using service- oriented network API
• Service chaining using OpenFlow
• Virtualized appliances
Chicago Docker Meetup Presentation - MediaflyMediafly
Bryan Murphy's presentation from the 2nd Chicago Docker meetup on March 12, 2014 at Mediafly HQ. In his presentation, Bryan explains how we use Docker right now at Mediafly in production.
Introduction to Data Models & Cisco's NextGen Device Level APIs: an overviewCisco DevNet
A session in the DevNet Zone at Cisco Live, Berlin. The need to automate interactions with the network is ever more obvious. We have a plethora of tools built around legacy technologies, such as SNMP and screen scraping, but these are coming to the end of their useful lives. In this introductory talk we will look at how YANG data models are becoming ever more pervasive across networking, and how they may be used to more efficiently automating network configuration and operational management.
Perforce Helix Never Dies: DevOps at Bandai Namco StudiosPerforce
Traditionally at Bandai Namco Studios, there has been no unified version control system in place and teams could choose to use any VCS system for their game titles—Subversion, Git, AlienBrain, or none at all. I’ll talk about why Bandai Namco Studios chose to standardize on Perforce Helix, show how we develop LiveOps-type mobile applications using the Unity game engine, and the advantages we gain from centrally managing code and assets in Helix.
Le SDN et NFV sont très à la mode en ce moment car en passant des appliance physiques aux équipement réseau massivement logiciel, celà devrait offrir une grande flexibilité et agilité aux entreprises (et telco en particulier). Néanmoins chainer des services réseau est un exercice encore très complexe et ce document vous explique ce qu'il est déjà possible de faire sur OpenStack en couplant par exemple : un load balancer (BigIP), un Firewall (BigIP), un réseau virtuel WAN (RiverBed) ou encore un routeur virtuel (Brocade).
Virtual Flink Forward 2020: Integrate Flink with Kubernetes natively - Yang WangFlink Forward
Currently Flink supports the resource management system YARN and Mesos. However, they were not designed for fast moving cloud native architectures, and they could not support mixed workloads (e.g. batch, streaming, deep learning, web services, etc.) relatively well. At the same time, Kubernetes is evolving very fast to fill those gaps and become the de-facto orchestration framework. So running Flink on Kubernetes is a very basic requirement for many users. In this talk, firstly we will quickly go through Kubernetes architecture and the efforts we have been made to run Flink on Kubernetes. Then we deep dive into the technical details about how to make Flink natively run on Kubernetes. Native means Flink KubernetesResourceManager calls directly the Kubernetes APIs to allocate and release TaskManager pods. Next we will share some practices of application lifecycle management and production optimizations (e.g. high-availability, storage, network, etc.). Finally, we will conclude the talk with advantages for Flink on Kubernetes and a simple demo. This talk is aimed at users and companies who are looking to run Flink on Kubernetes cluster. We assume that the listener has some basic knowledge of cluster orchestration and containers.
Jan Lindblad's presentation at Layer123 SDN and OpenFlow World Congress in Bad Homburg, Germany. Focusing on a multi-vendor SDN deployment at a Tier 1 Service Provider in Asia.
Tail-f Network Control System (NCS) use case:
• Dynamic control of L3-L7 devices using service- oriented network API
• Service chaining using OpenFlow
• Virtualized appliances
Chicago Docker Meetup Presentation - MediaflyMediafly
Bryan Murphy's presentation from the 2nd Chicago Docker meetup on March 12, 2014 at Mediafly HQ. In his presentation, Bryan explains how we use Docker right now at Mediafly in production.
An overview of project Skyfall. A globally distributed fault tolerant event consumption framework used by AddThis.com to consume billions of events per day.
Lightbend Fast Data Platform - A Technical Overview
Dean Wampler, O’Reilly author and Big Data Strategist in the office of the CTO at Lightbend discusses practical tips for architecting stream-processing applications and explains how you can tame some of the complexity in moving from data at rest to data in motion.
Moderne Serverless-Computing-Plattformen sind in aller Munde und stellen ein Programmiermodell zur Verfügung, wo sich der Nutzer keine Gedanken mehr über die Administration der Server, Storage, Netzwerk, virtuelle Maschinen, Hochverfügbarkeit und Skalierbarkeit machen brauch, sondern sich auf das Schreiben von eigenen Code konzentriert. Der Code bildet die Geschäftsanforderungen modular in Form von kleinen Funktionspaketen (Functions) ab. Functions sind das Herzstück der Serverless-Computing-Plattform. Sie lesen von der (oft Standard-)Eingabe, tätigen ihre Berechnungen und erzeugen eine Ausgabe. Die zu speichernden Ergebnisse von Funktionen werden in einem permanenten Datastore abgelegt, wie z.B. der Autonomous Database gespeichert. Die Autonomous Database besitzt folgende drei Eigenschaften self-driving, self-repairing und self-securing, die für einen modernen Anwendungsentwicklungsansatz benötigt werden.
By: Marianne Eggett, Linux Emerging Technology Practice Mgr, Mainline Information Systems
Are you considering a migration to Linux on IBM System z? The first step is to develop a detailed plan that outlines the short term and long term benefits of your migration.
In this presentation you will learn:
- How to identify the business case to support consolidation with System z Linux
- Examples of cost savings other businesses have experienced
- How to build a Total Cost of Ownership report specific to your environment
To view this presentation with audio, visit: http://go.mainline.com/pages/start/knowledge-center-building-the-case-zlinux-webcast-june-2009/index.html?Campaign_Id=7071&Activity_Id=6131
For other topics, visit: www.mainline.com/kc
Similar to Балансировщики KEMP для Microsoft Lync, Skype for Business (20)
4. Программа
1. Обзор решений KEMP Technologies для Microsoft Lync Server 2013
2. Балансировка внутренних и внешних сервисов Microsoft Lync Server 2013
2.a. Краткая теоретическая часть
2.b. Демонстрация
3. Использование разработанных инженерами KEMP шаблонов для настройки
оборудования
3.a. Краткая теоретическая часть
3.b. Демонстрация
4. Вопросы и ответы
5. 1. Обзор решений KEMP Technologies для
Microsoft Lync Server 2013
https://kemptechnologies.com/products-solutions/
9. Load Balancers for Bare Metal
https://kemptechnologies.com/loadmaster-family-bare-metal-software-load-balancers-application-delivery-controllers/
Hewlett Packard ProLiant DL
Dell R Series
Oracle X4-2
Fujitsu Server PRIMERGY
Cisco UCS C Series
Cisco UCS B Series
18. Microsoft Lync Server Planning Tool 2013
http://www.microsoft.com/ru-RU/download/details.aspx?id=36823
19. 2.b. Демонстрация
• Microsoft Lync Server Planning Tool 2013
• http://www.microsoft.com/ru-RU/download/details.aspx?id=36823
• Построитель топологии Skype для бизнеса Server
• Пулы Lync Server 2010/2013/SfB
• Обзор VLM200
• Настройка VM
• WEB интерфейс/COM порт/USB клавиатура + VGA (bal/1fourall)
• Лицензия
• LAN
• Пример настройки виртуальной службы
20. 3. Использование разработанных инженерами
KEMP шаблонов для настройки оборудования
3.a. Краткая теоретическая часть
https://kemptechnologies.com/files/assets/templates/Lync2013.tmpl
21. Lync Internal
Lync Internal 2013 DNS Handles HTTP/HTTPS traffic for Lync Internal WebSvc traffic. (Version 1.0)
1 AAA.BBB.CCC.DDD:80(+1) tcp Lync Internal WebSvc HTTP L7 round robin
2 AAA.BBB.CCC.DDD:443(+1) tcp Lync Internal WebSvc HTTPS L7 on Real Server round robin
Lync Internal 2013 HLB Only Handles HTTP/HTTPS Services for WebSvc traffic. Includes SIP, sending
requests to Mediation Server, Bandwidth Service Policy, incoming SIP requests, Attendant,
Conferencing Announcement, Call Park, Audio Test, call admission control and DCOM based
operations.(Version 1.0)
1 AAA.BBB.CCC.DDD:80(+1) tcp Lync Internal WebSvc HTTP L7 round robin
2 AAA.BBB.CCC.DDD:135 tcp Lync Internal Front-End DCOM L7 round robin
3 AAA.BBB.CCC.DDD:443(+2) tcp Lync Internal WebSvc HTTPS HLB Only L7 on Real Server round robin
4 AAA.BBB.CCC.DDD:5061(+8) tcp Lync Internal Front-End SIP L7 round robin
22. Lync Director
Lync Director 2013 DNS Handles HTTPS for traffic between Director and
Web farm FQDN. (Version 1.0)
1 AAA.BBB.CCC.DDD:443(+2) tcp Lync Director L7 on Real Server round robin
Lync Director 2013 HLB Only Handles HTTPS for traffic between Director
and Web farm FQDN. Includes internal communication between servers
and clients. (Version 1.0)
1 AAA.BBB.CCC.DDD:443(+2) tcp Lync Director L7 on Real Server round robin
2 AAA.BBB.CCC.DDD:5061 tcp Lync Internal Director SIP L7 round robin
23. Lync Edge
Lync Edge External 2013 HLB Only Handles HTTPS service. Includes communication for federated and public IM
connectivity using SIP and between Edge server XMPP and federated XMPP partners. (Version 1.0)
1 AAA.BBB.CCC.DDD:443 tcp Lync Edge External SIP L7 on Real Server round robin
2 AAA.BBB.CCC.DDD:5061 tcp Lync Edge External SIP Federation L7 round robin
3 AAA.BBB.CCC.DDD:5269 tcp Lync Edge External XMPP L7 round robin
Lync Edge External AV 2013 HLB Only Handles TCP and UDP media services for External A/V sessions. (Version 1.0)
1 AAA.BBB.CCC.DDD:443 tcp Lync Edge External AV Media TCP L7 on Real Server round robin
2 AAA.BBB.CCC.DDD:3478 udp Lync Edge External AV Media UDP L4 round robin
Lync Edge External Conferencing 2013 HLB Only Handles HTTPS traffic for External Web Conferencing Media. (Version 1.0)
1 AAA.BBB.CCC.DDD:443 tcp Lync Edge External Conferencing L7 on Real Server round robin
Lync Edge Internal 2013 HLB Only Handles external access to A/V sessions, media (TCP & UDP) and client to server SIP
traffic. (Version 1.0)
1 AAA.BBB.CCC.DDD:443 tcp Lync Edge Internal AV Media TCP L7 on Real Server round robin
2 AAA.BBB.CCC.DDD:3478 udp Lync Edge Internal AV Media UDP L4 round robin
3 AAA.BBB.CCC.DDD:5061(+1) tcp Lync Edge Internal SIP L7 round robin
24. Lync Mediation
Lync Mediation 2013 HLB Only Handles requests from FE Servers.
(Version 1.0)
1 AAA.BBB.CCC.DDD:5070 tcp Lync Mediation L7 round robin
25. Reverse Proxy
Lync Office Web App Servers 2013 Handles HTTPS Services for Office
Web App traffic. (Version 1.0)
1 AAA.BBB.CCC.DDD:443 tcp Office Web App Servers L7 round robin
Lync Reverse Proxy 2013 Handles HTTP/HTTPS Services for all Reverse
Proxy traffic. (Version 1.0)
1 AAA.BBB.CCC.DDD:80 tcp Lync Reverse Proxy HTTP L7 round robin
2 AAA.BBB.CCC.DDD:443 tcp Lync Reverse Proxy HTTPS L7 round robin
26. 4.b. Демонстрация
• Получение актуальной версии шаблонов Lync2013.tmpl
• https://kemptechnologies.com/loadmaster-documentation/
• Установка шаблонов Lync2013.tmpl
• Обзор 11 шаблонов
• Пример настройки
27. 4. Вопросы и ответы
https://ru.linkedin.com/in/azhure
a.Zhuravlev@beltel.ru
С оборудованием KEMP работаю с 2010 года (LM-2000)
Количество портов
DELL платформа
30 дней
В 2010 много теории
Для SfB многое справедливо
C:\Program Files (x86)\Microsoft Lync Server 2013\Planning Tool
на самом деле дистрибутив один. а в файле конфигурации LyncPlanningTool.exe.config можно указать не ru-ru, а en-us
Шаблоны только для 2013 и не обновлялся с 1.0 (есть для EX2010 и EX2013 и обновляются)
В скомпилированном виде