The world doesn’t need another public cloud.
Pivotal Container Service, developed with VMware and Google, is initially available.
ZTP stands for Zero Touch Provisioning. And, as a quick google search will quickly reveal, many other things as well.
Back to our ZTP. ZTP is the process by which new network switches can be configured without much human involvement. Notice that I said “much” and not “any”. ZTP is not it’s not truly zero because something (someone!) needs to put the first components of the network together in order for the rest of the network to be built in a ZTP fashion.
Where provisioning many switches could have quite a while through ZTP processes it’s down to a matter of minutes. Switches can also be updated automatically with any need for physical intervention.
The beauty of ZTP is the continued march towards more and more robust automation solutions. Delightfully, once folks aren’t mired in the repetitive manual work they can move onto tasks that bring innovation to businesses and, more importantly, make jobs more enjoyable. We also can’t ignore the fact that it renders moot a lot of the specialized skills that traditionally defined the role of a network engineer. Continue reading
When deploying IPv6, one of the fundamental questions the network engineer needs to ask is: DHCPv6, or SLAAC? As the argument between these two has reached almost political dimensions, perhaps a quick look at the positive and negative attributes of each solution are. Originally, the idea was that IPv6 addresses would be created using stateless configuration (SLAAC). The network parts of the address would be obtained by listening for a Router Advertisement (RA), and the host part would be built using a local (presumably unique) physical (MAC) address. In this way, a host can be connected to the network, and come up and run, without any manual configuration. Of course, there is still the problem of DNS—how should a host discover which server it should contact to resolve domain names? To resolve this part, the DHCPv6 protocol would be used. So in IPv6 configuration, as initially conceived, the information obtained from RA would be combined with DNS information from DHCPv6 to fully configure an IPv6 host when it is attached to the network.
There are several problems with this scheme, as you might expect. The most obvious is that most network operators do not want to deploy two protocols to Continue reading
Barefoot leverages its Tofino programmable switch and the P4 language.
AT&T wants white box routers; VMware swoops on VeloCloud; Cisco Ericsson partnership wavers.
Introducing NSX-T 2.1 with Pivotal Integration Application architectures are evolving. That shouldn’t be news to anyone. Today, emerging app architectures that leverage container-based workloads and microservices are becoming mainstream, moving from science projects in development labs to enterprise production deployments at scale. The benefits are clear. Developers and the application lifecycle, become faster, more productive,... Read more →
Application architectures are evolving. That shouldn’t be news to anyone. Today, emerging app architectures that leverage container-based workloads and microservices are becoming mainstream, moving from science projects in development labs to enterprise production deployments at scale. The benefits are clear. Developers and the application lifecycle, become faster, more productive, more agile, and more responsive to the needs of the business.
Today we’re announcing NSX-T 2.1, which will enable advanced networking and security across these emerging app architectures, just as it does for traditional 3-tier apps. More specifically, NSX-T 2.1 will serve as the networking and security platform for the recently announced VMware Pivotal Container Service (PKS), a Kubernetes solution jointly developed by VMware and Pivotal in collaboration with Google. NSX-T 2.1 will also introduce integration with the latest 2.0 release of Pivotal Cloud Foundry (PCF), serving as the networking and security engine behind PCF. In these environments, NSX-T will provide Layer 3 container networking and advanced networking services such as load balancing, micro-segmentation, and more.
For development teams, these integrations mean that they will be able operate quickly and consume infrastructure as code. Meanwhile, their workflows will remain the same — fast and efficient — because NSX-T will integrate tightly with these application platforms, connecting directly into the Continue reading
The company's vetting process found a flaw in the previous Kubernetes release.
It’s ironic that the one thing most programmers would really rather not have to spend time dealing with is... a computer. When you write code it’s written in your head, transferred to a screen with your fingers and then it has to be run. On. A. Computer. Ugh.
Of course, code has to be run and typed on a computer so programmers spend hours configuring and optimizing shells, window managers, editors, build systems, IDEs, compilation times and more so they can minimize the friction all those things introduce. Optimizing your editor’s macros, fonts or colors is a battle to find the most efficient path to go from idea to running code.
CC BY 2.0 image by Yutaka Tsutano
Once the developer is master of their own universe they can write code at the speed of their mind. But when it comes to putting their code into production (which necessarily requires running their programs on machines that they don’t control) things inevitably go wrong. Production machines are never the same as developer machines.
If you’re not a developer, here’s an analogy. Imagine carefully writing an essay on a subject dear to your heart and then publishing it only to be Continue reading
In order to mix EX switches and QFX switches in the same VCF, you need to enable mixed-mode. This requires all members of the VCF to reboot unfortunately:
{master:1} imtech@sw0-24c> request virtual-chassis mode fabric mixed fpc0: -------------------------------------------------------------------------- Mode set to 'Fabric with mixed devices'. (Reboot required) fpc2: -------------------------------------------------------------------------- Mode set to 'Fabric with mixed devices'. (Reboot required) fpc3: -------------------------------------------------------------------------- Mode set to 'Fabric with mixed devices'. (Reboot required) fpc1: -------------------------------------------------------------------------- WARNING, Virtual Chassis Fabric mode enabled without a valid software license. Please contact Juniper Networks to obtain a valid Virtual Chassis Fabric License. Mode set to 'Fabric with mixed devices'. (Reboot required) {master:1} imtech@sw0-24c>
Once you’ve cabled up your QSFP ports between the EX4300 you are adding and the QFX spines, you need to do the following:
Enable the VCF port on the QFX spine:
request virtual-chassis vc-port set pic-slot 0 port 48
This is VMware’s latest move in its ongoing push to be the “glue of the hybrid cloud.”