IBM Cloud Back Online After Mass Outage
Outage tracking services reported a surge in errors beginning shortly before 6 p.m. in the Eastern...
The Pursuit Of Storage That Spans The Clouds
Every IT supplier has cloudy envy. And not just because utility-style pricing has become normalized by the big public clouds, but because they want to have a more regular, annuity-like revenue stream rather than always chasing the next deal. …
The Pursuit Of Storage That Spans The Clouds was written by Jeffrey Burt at The Next Platform.
Coronavirus Claims 200 Jobs at GSMA
Massive job cuts, which impacted about a fifth of the association’s workforce, hit four months...
How To Manage Docker Hub Organizations and Teams
Docker Hub has two major constructs to help with managing users access to your repository images. Organizations and Teams. Organizations are a collection of Teams and Teams are a collection of DockerIDs.
There are a variety of ways of configuring your Teams within your Organization. In this blog post we’ll use a fictitious software company named Stark Industries which has a couple of development teams. One which works on the front-end of the application and the other that works on the back-end of the application. They also have a QA team and a DevOps team.
We’ll want to set up our Teams so that each engineering team can push and pull the images that they create. We’ll give the DevOps team access privileges to pull images from the dev teams repos and the ability to push images to the repos that they own. We’ll also give the QA team read-only access to all the repos.
Organizations
In Docker Hub, an organization is a collection of teams. Image repositories can be created at the organization level. We are also able to configure notifications and link to source code repositories.
Let’s set up our Organization.
Open your favorite browser and navigate Continue reading
Day Two Cloud 052: Moving Back Home From The Cloud
Today's Day Two Cloud episode is a frank conversation about cloud migration, multicloud, cloud repatriation, and more. If you're here for rainbows and unicorns, prepare for disappointment. We talk about what's real, how expensive it can be to move to cloud, why people bring workloads back on premises, and more. Our guest is Bobby Allen, CTO at CloudGenera.Day Two Cloud 052: Moving Back Home From The Cloud
Today's Day Two Cloud episode is a frank conversation about cloud migration, multicloud, cloud repatriation, and more. If you're here for rainbows and unicorns, prepare for disappointment. We talk about what's real, how expensive it can be to move to cloud, why people bring workloads back on premises, and more. Our guest is Bobby Allen, CTO at CloudGenera.
The post Day Two Cloud 052: Moving Back Home From The Cloud appeared first on Packet Pushers.
NTC – Security and Networking
The increased rate of change in networking isn’t just impacting the operational models used to run networks. Network security posture, infrastructure, and operations are having to adapt quickly as well. In this episode we sit down with Henry Jiang, CISO of Diligent Corporation, to talk about how security is adapting to current infrastructure trends.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post NTC – Security and Networking appeared first on Network Collective.
High Availability Load Balancers with Maglev
Background
We run many backend services that power our customer dashboard, APIs, and features available at our edge. We own and operate physical infrastructure for our backend services. We need an effective way to route arbitrary TCP and UDP traffic between services and also from outside these data centers.
Previously, all traffic for these backend services would pass through several layers of stateful TCP proxies and NATs before reaching an available instance. This solution worked for several years, but as we grew it caused our service and operations teams many issues. Our service teams needed to deal with drops of availability, and our operations teams had much toil when needing to do maintenance on load balancer servers.
Goals
With the experience with our stateful TCP proxy and NAT solutions in mind, we had several goals for a replacement load balancing service, while remaining on our own infrastructure:
- Preserve source IPs through routing decisions to destination servers. This allows us to support servers that require client IP addresses as part of their operation, without workarounds such as X-Forwarded-For headers or the PROXY TCP extension.
- Support an architecture where backends are located across many racks and subnets. This prevents solutions that cannot Continue reading
How Should Network Architects Deal with Network Automation
A network architect friend of mine sent me a series of questions trying to figure out how he should approach network automation, and how deep he should go.
There is so much focus right now on network automation, but it’s difficult for me to know how to apply it, and how it all makes sense from an Architect’s PoV.
A network architect should be the bridge between the customer requirements and the underlying technologies, which (in my opinion) means he has to have a good grasp of both as opposed to fluffy opinions glanced from vendor white papers, or brushed off so-called thought leaders.
MANRS Fellowship Program Now Open
The first-ever MANRS (Mutually Agreed Norms for Routing Security) Fellowship Program is now accepting applications. If you are an emerging leader eager to improve the well-being of the Internet’s global routing system, apply now.
The program gives highly motivated individuals the chance to work alongside MANRS ambassadors, who are industry leaders participating in the Ambassador Program. Together, they will train diverse communities on good routing practices, analyze routing incidents, research into ways to secure routing, and survey the global policy landscape.
Fellows will improve their skills and bring new perspectives and ideas to MANRS. They will also gain valuable insights and networking opportunities from well-respected professionals called MANRS Ambassadors under the MANRS Ambassadors Program. The selection process for this program is currently underway.
The Internet Society supports this program as part of its work to reduce common routing threats and establish norms for network operations.
You can apply for a fellowship in three different areas: training, research, and policy. Each fellow will receive a stipend of $750 a month. There is no age requirement and you can apply for more than one category but will only be selected for one of them.
Online training
Responsible for: Conducting MANRS online tutorial Continue reading
Aruba Assembles SDN Tech for Edge Services Platform
Aruba Edge Services Platform is comprised of 35 services, including a dozen new insights that were...
Daily Roundup: IBM Quits Facial Recognition Biz
IBM quit the facial recognition business; A10, Dell teamed up on application delivery; and Alibaba...
Creating a Multi-AZ NAT Gateway with Pulumi
I recently had a need to test a configuration involving the use of a single NAT Gateway servicing multiple private subnets across multiple availability zones (AZs) within a single VPC. While there are notable caveats with such a design (see the “Caveats” section at the bottom of this article), it could make sense in some use cases. In this post, I’ll show you how I used TypeScript with Pulumi to automate the creation of this design.
For the most part, if you’re familiar with Pulumi and using TypeScript with Pulumi, this will be pretty straightforward. The code I’ll show you makes a couple assumptions:
- It assumes you’ve already created the VPC and the subnets earlier in the code. I’ll reference the VPC object as
vpc. - I’ll assume you’ve already created subnets in said VPC, and that the subnet-to-AZ ratio is 1:1 (exactly one subnet of each type—public or private—in each AZ). The code will reference the subnet IDs as
pubSubnetIds(for public subnets) orprivSubnetIds(for private subnets). (How to create the subnets and capture the list of IDs is left as an exercise for the reader. If you’d be interested in seeing how I do it, let me know. Continue reading
7 Layers: IoT Part 2 — IoT Devices are Dangerously Insecure
This week is the second in a two-part series on the Internet of Things. We cover IoT security...
The History of Networking: Ivan Pepelnjak and the Internet Behind the Iron Curtain
Ivan Pepelnjak was a founding member of the first IX in Slovenia twenty-five years ago. He joins us to describe the origins of the Internet, from the first dial-up circuits to the founding of the first IX and local DNS services here on the History of Networking. Ivan is an independent consultant and trainer; his work can be found at https://ipspace.net.
TSMC Secures US Subsidies for Arizona Fab
The announcement comes weeks after the Taiwanese chipmaker announced plans to build the facility.
IBM Stops Facial Recognition Support for Surveillance Activity
CEO Arvind Krishna made the pledge in a letter to the U.S. Congress. It’s one of three policy...
A10 Bundles App Delivery, Security on Dell Hardware
Both bundles can use A10’s Harmony Controller for application management and integration into...
Alibaba Cloud Kicks Off Hiring Surge
The company is recruiting IT professionals with expertise in networking, database management,...