Weekly Wrap: NSA Ranks Cloud Security Risks
SDxCentral Weekly Wrap for Feb. 7, 2020: Supply chain security flaws are expected to increase;...
SDxCentral Weekly Wrap for Feb. 7, 2020: Supply chain security flaws are expected to increase;...
After introducing the fallacies of distributed computing in the How Networks Really Work webinar, I focused on the first one: the network is (not) reliable.
While that might be understood by most networking professionals (and ignored by many developers), here’s an interesting shocker: even TCP is not always reliable (see also: Joel Spolsky’s take on Leaky Abstractions).
Cloudburst: stateful functions-as-a-service, Sreekanti et al., arXiv 2020
Today’s paper choice is a fresh-from-the-arXivs take on serverless computing from the RISELab at Berkeley, addressing some of the limitations outlined in last year’s ‘Berkeley view on serverless computing.’ Stateless is fine until you need state, at which point the coarse-grained solutions offered by current platforms limit the kinds of application designs that work well. Last week we looked at a function shipping solution to the problem; Cloudburst uses the more common data shipping to bring data to caches next to function runtimes (though you could also make a case that the scheduling algorithm placing function execution in locations where the data is cached a flavour of function-shipping too).
Given the simplicity and economic appeal of FaaS, it is interesting to explore designs that preserve the autoscaling and operational benefits of current offerings, while adding performant, cost-efficient and consistent shared state and communication.
The key ingredients of Cloudburst are a highly-scalable key-value store for persistent state (Anna), local caches co-located with function execution environments, and cache-consistency protocols to preserve developer sanity while data is moved in and out of those caches. Oh, and there’s a scheduler Continue reading
Prior to my current job, I enjoyed the time I invested in the community. I spent quite a bit of time on The Cisco Learning Network helping those that were early in career. I also blogged here regularly (typically weekly) and spent time in the Twitterverse and on Slack. From this perspective, taking a job with a vendor was more different than I expected. It was like someone flipped a switch and I was completely spent at the end of each and every day.
On a few occasions, I have tried to get back what I would have previously considered some level of normalcy with regards to the community. I have decided that this year is my year to make some major changes. I must do a better job prioritizing things I care about and realize that some [read many] things just aren’t going to get done. That is one thing I’ve learned over the past few years. Even though I have always felt that my workload was significant, there is nothing like having a job in which you can only get a small portion of the overall work completed. It just doesn’t feel good.
The community and the relationships Continue reading
Fortinet celebrated a strong fourth quarter by announcing a partnership with colocation provider...
There are two major opposing forces in the datacenter that create tension in IT budgets. …
The Fundamental Disconnect Between Software Pricing And Moore’s Law was written by Jeffrey Burt at The Next Platform.
Irrespective of the merger’s outcome, the final quarter of 2019 was arguably its most...
Nokia's earnings flatline; Verizon called Huawei lawsuit a ‘PR stunt’; and Cisco liked...
Dell Technologies recently announced rollouts of their 5G-enabled laptop, enabling the key benefits...
The vulnerability allows an attacker to activate the affected device's Telnet service over an open...
The best way to learn IPv6 is to get it into the lab and play with it. On today's IPv6 Buzz podcast, we share advice, learnings, and tips on building a lab and getting your hands dirty with this protocol.
The post IPv6 Buzz 044: Building An IPv6 Lab appeared first on Packet Pushers.


Last Wednesday, the CNCF released the KubeCon Europe 2020 schedule. There are so many talks at KubeCon it can be daunting even to decide what to go to see! Here are some talks by the team at Docker, and some others we think will be particularly interesting. Looking forward to seeing you in Amsterdam!
Chris is an engineer in our Paris office and is also co-executive director of the CNAB project. CNAB (Cloud Native Application Bundle) is a specification for bundling up cloud-native applications, which can consist of multiple containers, into a single object that can be pushed to a registry. Open source projects using CNAB, like Docker App or Porter allow you to package apps that would normally require multiple tools like Terraform, Helm, and shell to deploy, into a single tooling agnostic packaging format. These packages can then be shared using existing container registries and used with other CNAB compliant tools. This can really simplify cloud-native development.
Did you know that you can store anything into a container registry? Continue reading
A journey of a thousand miles begins with one step they say… but what should that first step be if you want to start a network automation journey (and have no idea how to do it)?
Anne Baretta sent me a detailed description of his journey, which (as is often the case) started with the standardized configuration templates.