ONS 2018: Networking Reimagined



  • For the past seven years, Open Networking Summit (ONS) has brought together the networking industry’s ecosystem of network operators, vendors, open source projects, leading researchers, and investors to discuss the latest SDN and NFV developments that will shape the future of the networking industry. With this year’s event, taking place March 26-29, 2018 in Los Angeles, ONS will evolve its approach as the premier open source networking event. We’re excited to share three new aspects of this year’s ONS that you won’t want to miss:

    • Present Less, Engage More

    Sometimes it’s good to break the traditional mold. As ONS is an open source event, we hope to foster more collaboration with fewer formal presentations and more discussion within our keynotes. Attendees can expect more time to ask questions and explore demos while attending keynotes. This year’s sessions will cover forward-looking vision, disruption and strategy with an enterprise, cloud and server provider focus. Keynote presenters for this year include industry leaders from AT&T Labs, Arm, Ericsson, Google, Uber and many more. Learn more about ONS 2018 keynotes here.

    • Networking: Reimagined for Future Networks

    Open source networking deployments are now expanding beyond the carrier world. Hear from industry visionaries and leaders on the future of networking beyond SDN/NFV, including 5G & IoT; cloud networking (Kubernetes); AI & ML applied to networks; and the use of networking technologies within other industry verticals such as FinTech and automotive. Whether you are new to these emerging technologies or want to deepen your technical understanding, our agenda will connect you with many organizations deploying open source networking solutions. Full agenda can be found here.

    • Welcome to Los Angeles!

    We’re excited to feature ONS 2018 in a new location this year: Los Angeles! Unofficially known as the City of Dreams, we hope attendees will be inspired by the innovation and creativity of the area. The change of scenery brings us to the heart of Los Angeles, at the InterContinental Los Angeles Downtown, and will provide opportunities for networking (in every sense of the word).

    Sign up to get the latest updates on ONS NA 2018!

    Registration for ONS 2018 is quickly filling up and we hope you’ll join us this March! Save 15% on your registration with the code ONSLCR15. To reserve your spot or learn more about the event, visit here.

    The post ONS 2018: Networking Reimagined appeared first on The Linux Foundation.

    https://www.linuxfoundation.org/blog/ons-2018-networking-reimagined/


 



Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:

    lsblk

    Output:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s

    Fin!

    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more
});