Thanks to all who joined us for the Huawei 2017 Infrastructure Security Report Webinar: Paving a Trusted Way for Cloud-based Transformation. During the webinar, Huawei discussed a fresh approach when it comes to your cloud journey that is characterized by the transition to cloud computing, mobile Internet, Big Data, and virtual networks. After the webinar, we... Read more →
It’s becoming clear that web-scale networking is the future of networking, and companies need the technology in order to remain competitive against cloud giants like Amazon. So, how do organizations looking to move on from traditional networking start to get their feet wet and bring web-scale efficiencies like automation and scalability to their operations?
That’s where NetQ steps in to save the day. NetQ is a telemetry-based fabric validation system that enables organizations to deploy & operate data center networks with the speed and agility of web-scale giants. Where network configuration used to be slow, require manual intervention, and cause network downtime, NetQ automates configuration and ensures that your network is behaving as intended. It’s preventative, proactive, and diagnostic, and should be the next product you incorporate into your data center.
Here are the top five benefits of NetQ:
New vendors like Nokia and Huawei don’t have a CCAP business to protect.
The Oracle Dyn team behind this blog have frequently covered ‘network availability’ in our blog posts and Twitter updates, and it has become a common topic of discussion after natural disasters (like hurricanes), man-made problems (including fiber cuts), and political instability (such as the Arab Spring protests). But what does it really mean for the Internet to be “available”? Since the Internet is defined as a network of networks, there are various levels of availability that need to be considered. How does the (un)availability of various networks impact an end user’s experience, and their ability to access the content or applications that they are interested in? How can this availability be measured and monitored?
Many Tweets from @DynResearch feature graphs similar to this one, which was included in a September 20 post that noted “Internet connectivity in #PuertoRico hangs by a thread due to effects of #HurricaneMaria.”
There are two graphs shown — “Unstable Networks” and “Number of Available Networks”, and the underlying source of information for those graphs is noted to be BGP Data. The Internet analysis team at Oracle Dyn collects routing information in over 700 locations around the world, giving us Continue reading
The company's security revenue jumped 51 percent from the same quarter a year earlier.
IoT may play a role in how Cisco melds AppDynamics' technology into the rest of its business.
The edge intelligence and industrial IoT company is backed by GE, Saudi Aramco, Intel Capital, Bosch, Dell, and more.
 |
| Fig 1.1- Cisco Meraki MX Security Appliances |
In a return to our routing protocol series, Russ White and Nick Russo join Network Collective to talk about some of the intricacies of the IS-IS routing protocol. While not usually found in enterprises, Service Providers have used IS-IS as the underlay to their MPLS networks and it is starting to make an appearance as the underlay to several newer enterprise technologies. If you’ve been curious about how it works, and how it is different than what you use today, this show is for you.
Show Links
https://www.iso.org/standard/30932.html
https://tools.ietf.org/html/rfc1142
https://en.wikipedia.org/wiki/Dijkstra%27s_algorithm
Show Notes
In a return to our routing protocol series, Russ White and Nick Russo join Network Collective to talk about some of the intricacies of the IS-IS routing protocol. While not usually found in enterprises, Service Providers have used IS-IS as the underlay to their MPLS networks and it is starting to make an appearance as the underlay to several newer enterprise technologies. If you’ve been curious about how it works, and how it is different than what you use today, this show is for you.
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 Episode 14 – Digging Deep into the IS-IS Routing Protocol appeared first on Network Collective.
A new Enea white paper discusses how the proliferation of cloud-based business applications is driving a need for a next-level NFV.
Docker claims to have migrated an app developed in 2005 to Azure.
The post Worth Reading: Responsible Encryption Fallacies appeared first on rule 11 reader.
This is a liveblog of the session titled “Looking Under the Hood: containerD”, presented by Scott Coulton with Puppet (and also a Docker Captain). It’s part of the Edge track here at DockerCon EU 2017, where I’m attending and liveblogging as many sessions as I’m able.
Coulton starts out by explaining the session (it will focus a bit more on how to consume containerD in your own software projects), and provides a brief background on himself. Then he reviews the agenda, and dives right into the content.
Up first, Coulton starts by providing a bit of explanation around what containerD is and does. He notes that there is a CLI tool for containerD (the ctr tool), and that containerD uses a gRPC API listening on a local UNIX socket. Coulton also discusses ctr, but points out that ctr is, currently, an unstable tool (changing too quickly). Next, Coulton talks about how containerD provides support for the OCI Image Spec and the OCI Runtime Spec (of which runC is an implementation), image push/pull support, and management of namespaces.
Coulton moves into a demo showing off some of containerD’s functionality, using the ctr tool.
After the demo, Coulton talks about some Continue reading
This is a liveblog of the session titled “Building a Secure Supply Chain,” part of the Using Docker track at DockerCon EU 2017 in Copenhagen. The speakers are Ashwini Oruganti (@ashfall on Twitter) and Andy Clemenko (@aclemenko on Twitter), both from Docker. This session was recommended in the Docker EE deep dive (see the liveblog for that session) as a way to get more information on Docker Content Trust (image signing). The Docker EE deep dive presenter only briefly discussed Content Trust, so I thought I’d drop into this session to get more information.
Oruganti starts the session by reviewing some of the steps in the software lifecycle: planning, development, testing, packaging/distribution, support/maintenance. From a security perspective, there are some additional concepts as well: code origins, automated builds, application signing, security scanning, and promotion/deployment. Within Docker EE, there are three features that help with the security aspects of the lifecycle: signing, scanning, and promotion. (Note that scanning and promotion were also discussed in the Docker EE deep dive, which I liveblogged; link is in the first paragraph).
Before getting into the Docker EE features, Clemenko reminds attendees how not to do it: manually. This approach doesn’t Continue reading