Building Our New Website: A vision for the new site
In the early stages of our process to build a new Internet Society website, we developed a "vision" for what we wanted the new website to be. Last year we spoke with many people throughout the larger Internet Society community. We spoke with staff, with Chapter leaders, with partner organizations, with individual members and many more.
As we launch the "beta" of the new website this week, I want to share with you the vision that emerged out of all of those aspirations:
Dan York
Building Our New Website: Announcing our public “Beta” launch – view the new site today
Today I'm excited to give you a glimpse into our future! As James Wood recently wrote, we have been working on a new website that makes it tremendously easier to find information and take action on issues important to you. I also shared the vision we have for this new site.
The big news is this: we have now released an "early beta" version of the new site that shows the overall design direction and look-and-feel. It is important to note: Most of the site is INCOMPLETE. Most links will not work and many pages are missing.
Dan York
Packet Fabric on Software Gone Wild
Imagine a service provider that allows you to provision 100GE point-to-point circuit between any two of their POPs through a web site and delivers in seconds (assuming you’ve already solved the physical connectivity problem). That’s the whole idea of SDN, right? Only not so many providers got there yet.
Read more ...EVPN Based Data Center Interconnect- Juniper Design Options and Config Guide
1 Data Center Inter-Connect (DCI)
DCI was always a challenge in days of VPLS and other vendor specific layer 2 extension technologies. Main challenge was how and where to integrate layer 2 and layer 3 e.g VPLS does offer layer 2 extension between 2 DCs but main challenge was where to configure layer 3 gateways and how to maintain ARP entry for gateway inside a Virtual Machine (VM) if VM moves from once DC to another DC.
EVPN gives answer to all those questions as we can create MAC-VRF along with Integrated Routing and Bridging (IRB) interface for a VLAN and that IRB interface can also be referred under standard L3 VRF if L3 extension is required between DCs. Thus, EVPN allows to combines L2 and L3 at L3 VTEP layer. Furthermore, we can configure same “virtual-gateway” on all L3 VTEPs for a VLAN. This scenario will allow a VM to maintain the ARP entry for the gateways if it moves from one DC to another DC.
1.1 Option 1
In each Data Center “Collapsed IP CLOS” is recommended to be configured if DCI Option 1 is selected for Layer 2 extension between the DCs. Continue reading
Dell Technologies’ Hyperconverged Systems Saw Triple-Digit Growth in Q1
The company will introduce a Virtustream addition of its enterprise hybrid cloud this year.
Juniper IP-CLOS (EVPN-VxLAN) Data Center – Design Options and Config Guide
1 Overview
IP-CLOS provides scalable option for large scale Data Center for hosting providers or Infrastructure as a Service (Iaas) model. IP-CLOS model consists of spine and leaf layer switches, where leaf layer switches provides direct connectivity to Bare Metal Servers (BMS), hypervisor based servers or other network devices (e.g Firewall, Load balancer) for services layer. Each leaf device is connected to all spine devices through high speed link, connectivity between spine and leaf is IP based thus offering ECMP (equal cost multipath) load balancing over IP links.
The question arises why need IP-CLOS based Date Center, the main and primary reason is to remove the upper limit on maximum number of VLANs. In switching based Data Center (traditional 3-Tier i.e Core, Distribution & Access) or modern Data Center (Spine and Leaf based switching fabric or flat switching fabric e.g Juniper Virtual Chassis Fabric and Juniper QFabric) we still have an upper limit on available VLANs inside single Data Center i.e 4096. In IP-CLOS based Data Center VLAN values are not significant and once traffic received on leaf layer from sever/ external network devices it will be converted into VxLAN packets and will be identified by Continue reading
Sharing Information Is Hard
Seriously hard. We consume a huge amount of information daily. I see metrics like 10,000 to 100,000 words a day being consumed by each of us. Some of that will be subjective, some of it objective. Some of it will be fiction, some will be fact. Some? Who knows. Political propaganda with elements of truth. Some of it will incite emotion and some of it will aid in falling to sleep.
If you blog, do podcasts or write whitepapers for reasons not tied to your employment or cold hard cash income, have you ever asked yourself why you do it? What makes you want to share?
In a society where something is declared fake news because two parties don’t agree and freedom of speech is becoming one way, is it worth it?
Why do I share?
If I need or want to learn something, I’ll go wide in the hunt for knowledge. Thanks to the ‘tinterweb, information is readily available. So much information is out there that we have the problem of validating what we read. Blogs have been a massive help to me over the years, especially when you read aligning and agreeing articles. The validation of “someone else Continue reading
Zenoss and Cisco Build NFV Infrastructure Using OpenStack
The NFVI is targeted to service providers.
Five Questions: Network Automation
Welcome to a new series where we interview Ansible experts on IT automation and ask them to share their direct experiences building automation solutions, as well as any insights they have regarding the state of the industry.
In this post, I’ve asked Peter Sprygada and Eric McLeroy five questions about network automation.
Peter Sprygada is a Senior Principal Engineer at Ansible by Red Hat where he brings over 20 years experience building and operating global network infrastructures. He holds two patents in network configuration automation and currently leads the Ansible network engineering team that focuses on building and integrating network automation capabilities into Ansible. Formerly Peter was responsible for building and leading the Arista EOS+ Extensibility Engineering team where he focused on applying DevOps methodologies to enhancing network operations. Prior to that, he held senior network engineering and operations roles at various organizations including Cisco. You can follow him on twitter at @privateip.
Eric McLeroy is a Senior Solutions Architect for Ansible by Red Hat focused on networking use cases. Eric has over 10 years in networking in large scale environments working with a large variety of systems from routers, switches, load balancers, etc. He holds multiple industry certifications and Continue reading
Worth Reading: Connecting Nepal
The post Worth Reading: Connecting Nepal appeared first on rule 11 reader.
The Future Internet I Want for Me, Myself and AI
Artificial Intelligence has the potential to bring immense opportunities, but it also poses challenges.
Artificial intelligence (AI) is dominating the R&D agenda of the leading Internet industry. The Silicon Valley and other startup hubs are buzzing about artificial intelligence and the issue has come at the top of policymakers’ agenda including the G20, the ITU, and the OECD, where leaders gathered this week in Paris.
Constance Bommelaer de Leusse
Cisco: DDoS Attacks Grew 172% in 2016, Expect 3.1M by 2021
The peak attack size increased 60 percent year-over-year.
Shippable Server Looks to Unify DevOps Work into ‘Assembly Lines’
The server product includes Docker tooling and integrates with all Docker registries.
AWS’ Greengrass Makes Edge Computing Possible for IoT Devices
About a dozen partners have already committed to integrating Greengrass into their platforms.
The 40 hour work week
The 40 hour work week is foremost a result of the physical limits of the human body—but we often fail to take into account the mental limits, as well. Why was working for more than 40 hours a week on a railroad dangerous? It was not just because people were physically tired, but also because they were mentally tired. The resulting discussion among coders has been rampant and widespread (see, for instance, here).
First, the focus on time and the length of the work week may be a little misdirected. We are still a world focused on physical presence as a proxy for accomplishing work. I know a lot of companies prefer to have people in the office—ironically, this is a big deal with most of the companies in the world that aim to bring networks, and network based services, to the masses. Continue reading
Cumulus Steps Into Performance Monitoring with NetQ Launch
This is Cumulus’ first major announcement centered around performance monitoring.