Worth Reading: Journey into the hybrid cloud
The post Worth Reading: Journey into the hybrid cloud appeared first on rule 11 reader.
The post Worth Reading: Journey into the hybrid cloud appeared first on rule 11 reader.
Introduce psample, a general way for kernel modules to sample packets, without being tied to any specific subsystem. This netlink channel can be used by tc, iptables, etc. and allow to standardize packet sampling in the kernel commitThe psample netlink channel delivers sampled packet headers along with associated metadata from the Linux kernel to user space. The psample fields map directly into sFlow Version 5 sampled_header export structures:
| netlink psample | sFlow | Description |
|---|---|---|
| PSAMPLE_ATTR_IIFINDEX | input | Interface packet was received on. |
| PSAMPLE_ATTR_OIFINDEX | output | Interface packet was sent on. |
| PSAMPLE_ATTR_SAMPLE_GROUP | data source | The location within network device that generated packet sample. |
| PSAMPLE_ATTR_GROUP_SEQ | drops | Number of times that the sFlow agent detected that a packet marked to be sampled was dropped due to lack of resources. Agent calculates drops by tracking discontinuities in PSAMPLE_ATTR_GROUP_SEQ |
| PSAMPLE_ATTR_SAMPLE_RATE | sampling_rate | The Sampling Rate specifies the ratio of packets observed at the Data Source to the samples generated. For example a sampling rate of 100 specifies that, on Continue reading |
In this post for the Internet Society Rough Guide to IETF 99, I’m reviewing what’ll be happening at IETF 99 in Prague next week.
Learn about the cloud networking service in this excerpt from Packt's "OpenStack: Building a Cloud Environment."
If you’re not old enough to know otherwise, you’d think (based on recent hype) that we discovered network automation a few years ago. Not true. One of my readers sent me a link to excellent Managing IP Networks with Free Software presentation from NANOG26 (October 2002).
I found the presentation awesome, nothing new, and extremely sad… all at the same time.
Read more ...
The company will initially market the service to its existing customers.
The containerized Kubernetes option supports running of different orchestration versions.
The operator got fed up with separate NFV management for different equipment.
At AMD’s Epyc launch few weeks ago, Lisa Su, Mark Papermaster, and the rest of the AMD Epyc team hammered home that AMD designed its new Zen processor core for servers first. This server-first approach has implications for performance, performance per watt, and cost perspectives in both datacenter and consumer markets.
AMD designed Epyc as a modular architecture around its “Zeppelin” processor die with its eight “Zen” architecture cores. To allow multi-die scalability, AMD first reworked its HyperTransport socket-to-socket system I/O architecture for use on a chip, across a multi-chip module (MCM), and for inter-socket connectivity. AMD has named this …
The Heart Of AMD’s Epyc Comeback Is Infinity Fabric was written by Timothy Prickett Morgan at The Next Platform.