Category: Random

Hands-on with Intel Co-Packaged Optics and Silicon Photonics Switch – ServeTheHomeVideo

Hands-on with Intel Co-Packaged Optics and Silicon Photonics Switch
Watch this video on YouTube.
We get some hands-on time in the Intel lab with their new switch. Based on the recently acquired Intel Barefoot Tofino 2 switch ASIC, we see the world’s first (publicly shown like this) working set of switches using both silicon photonics as well as co-packaged optics. We also explain why pluggable optics will be going away in future generations of network switches as they will consume too much power in the 51.2Tbps generation of switches.

Git Rebase Interactive

Being new to git. You will inadvertently struggle.

  1. Having opened a pull request (PR), leaving the PR hanging for a while, picking it up Y time later, with several changes have happened in the upstream branch. You will often find yourself in need of using git rebase upstream/master ((https://git-scm.com/docs/git-rebase)).
  2. After having rebased recent commits upon the upstream/master branch. You might want to squash your commits together, to create a cleaner pull request, and to avoid (un)intentionally blotting the git-history with miscellaneous commits, imagine:
    $ git log --graph --pretty=format:'%Cred%h%Creset %s'
* 77464f9 Update 'filename1.txt'
* 2a7894b Update 'File 2.txt'
* 27a44c6 Add 'File 2.txt'
* 4bc179b Add 'filename1.txt'
* 8757b20 Initial commit

    Can be reduced

    pick  = use commit
reword  = use commit, but edit the commit message
edit  = use commit, but stop for amending
squash  = use commit, but meld into previous commit
fixup  = like "squash", but discard this commit's log message
break = stop here (continue rebase later with 'git rebase --continue')
drop  = remove commit
    $ git rebase --interactive 8757b20
reword 4bc179b Add 'filename1.txt'
fixup 27a44c6 Add 'File 2.txt'
fixup 2a7894b Update 'File 2.txt'
fixup 77464f9 Update 'filename1.txt'

    $ git log --graph --pretty=format:'%Cred%h%Creset %s'
* 255c889 Add 'filename1.txt', and 'File 2.txt'
* 8757b20 Initial commit
  3. If in need of deciding which commit to squash together, and were to edit the commit message. Using git rebase --interactive (commit-hash, remote-name/branch-name, or branch-name) is the lifeline.

Remember, the commit hash will change when using git rebase action. Force pushing to the remote branch to replace its contents is necessary.
git push remote-name local-branch-name:remote-branch-name --force
(e.g. git push origin master-squashed-commits:master --force).

But this approach is the recommended way in regards to using git pull-requests. Any existing pull-requests against a branch you have on your fork of the upstream repository. Will automatically use the latest available information in your fork’s branch.

Problems with a IPv6 only network – Ben’s Place

In my last post I talked about running a pure IPv6 network, as part of my ISP building project, but still allowing access to resources on the internet currently only available via IPv4.This works well assuming all the clients on the local network are IPv6 capable, unfortunately this is not always the case. There are legacy devices that do not understand IPv6.This is a real problem with IoT devices that are either no longer being maintained or just that have hardware that is incapable of using anything other than IPv4. There is also a small problem that a IP cam with a IPv6 address is probably available to the world with out some firewall rules or a ACL limiting access to the local /64, but those are problems for another day…Another issue is hard coded IPv4 addresses in legacy applications, this is a problem even if the OS/device supports both IPv4 & IPv6 but is only connected via IPv6.There is are a few of solution to both these problems.

Source: Problems with a IPv6 only network – Ben’s Place

XR7, Not Just Another Release

When IOS XR was first designed, mass-scale networking and its related challenges were not around.  However, we already had a clear vision of building a highly scalable, reliable, available, upgradeable, high-performance NOS for the service provider space that caters all the way from low-end single chassis systems to massive high-end multi-chassis routers. To meet the rigorous SP requirements, a slew of ground-breaking infrastructure and distributed-systems architecture patterns were brought into the system—decoupled plane abstractions, state management, process distribution, high-performance messaging infrastructure, data distribution/access patterns, high availability and upgradeability. These solid foundations and continuous evolutions made IOS XR the industry-leading NOS.I’m thrilled to announce today the availability of IOS XR, Release 7, that brings some noteworthy evolutions. Four key tenets make Release 7 stand out.It is simple, modern, trustworthy, and cloud-enhanced.

Source: XR7, Not Just Another Release – Cisco Blogs