Heather Kirksey on Integrating Networking and Cloud Native



  • LF networking

    A lot of the interactions between the LF Networking and cloud native communities focus on how these technologies work together and on connecting people from different projects.

    As highlighted in the recentOpen Source Jobs Report, cloud and networking skills are in high demand. And, if you want to hear about the latest networking developments, there is no one better to talk with than Heather Kirksey, VP, Community and Ecosystem Development, Networking at The Linux Foundation. Kirksey was the Director of OPNFV before the recent consolidation of several networking-related projects under the newLF Networking umbrella, and I spoke with her to learn more about LF Networking (LFN) and how the initiative is working closely with cloud native technologies.

    Kirksey explained the reasoning behind the move and expansion of her role. :undefined:“:undefined:At OPNFV, we were focused on integration and end-to-end testing across the LFN projects. We had interaction with all of those communities. At the same time, we were separate legal entities, and things like that created more barriers to collaboration. Now, it:undefined:’:undefined:s easy to look at them more strategically as a portfolio to facilitate member engagement and deliver solutions to service providers.:undefined:”:undefined:

    Bringing these six networking projects together lowers barriers, reduces friction, and enables the communities to interact with each other.

    LF networkingNetworking Meets Cloud Native

    Kirksey said that at the recent KubeCon + CloudNativeCon Europe 2018, there was a lot of discussion around what cloud native network function virtualization (NFV) looks like with Kubernetes and other technologies. She said that the NFV community has already begun integration around cloud native technologies including Kubernetes, Prometheus, Fluentd, and FD.io. And, LF Networking has been working on Container Network Interface (CNI) plugins.

    A lot of these interactions between the LF Networking and Kubernetes communities focus on education :undefined:—:undefined: how these technologies work together :undefined:—:undefined: and connecting with people from different projects including Istio, CNI networking SIG, and others.

    :undefined:“:undefined:We are just trying to figure out the answers that arise as these projects work together,:undefined:”:undefined: she said. In her new role, Kirksey looks at things from an outwardly facing perspective. :undefined:“:undefined:We are looking at communities that are outside LF Networking :undefined:—:undefined: communities like CNCF :undefined:—:undefined: and figuring out what our engagement model should be. We are trying to identify projects that are of interest to us. We are trying to set up some programs that bring value to the ecosystem; a good example would be a compliance program.:undefined:”:undefined:

    Community is also part of Kirksey:undefined:’:undefined:s new role, and she is working to find out what:undefined:’:undefined:s needed to help the community create opportunities for interaction and involvement. :undefined:“:undefined:We have set up end-user advisory groups, member engagement programs, compliance and certification programs,:undefined:”:undefined: she said. The goal is to serve the entire ecosystem around these projects.

    Challenges

    Looking at some of the cloud native paradigms of how networking works, it:undefined:’:undefined:s simpler for an application developer than it used it be. Initially, these developers took things like interfaces, ports, and subnets and put :undefined:‘:undefined:v:undefined:’:undefined: in front of them and created virtual interfaces, virtual ports, and virtual subnets. But these constructs are not tied to physical ideas anymore, so the approach is different.

    :undefined:“:undefined:There is a lot of stuff at layer two and layer three that is still complicated, but you don:undefined:’:undefined:t want Kubernetes to have to worry about that; you certainly don:undefined:’:undefined:t want a Kubernetes-based application to have to worry about that,:undefined:”:undefined: Kirksey said, :undefined:“:undefined: We are trying to figure out how we deal with some of the complexities of networking, without bringing the physical baggage with it.:undefined:”:undefined:

    It:undefined:’:undefined:s not just technical challenges that these communities need to solve, there are also people challenges. So many new technologies are emerging that it:undefined:’:undefined:s becoming increasingly difficult to find experienced developers, and networking is no exception. According to Kirksey, :undefined:“:undefined:People who understand and can do deep network level programming are fairly rare.:undefined:”:undefined: And, she said, :undefined:“:undefined:The number of people who can program for or contribute to VPP or DPDK is relatively small. They now need to also extend their knowledge to these new technologies.:undefined:”:undefined:

    New Ideas

    Additionally, you can:undefined:’:undefined:t just create training programs and train people. :undefined:“:undefined:The number of people contributing to these projects is relatively small as it:undefined:’:undefined:s new and is still being defined,:undefined:”:undefined: she said, :undefined:“:undefined:That:undefined:’:undefined:s one reality of living at the bleeding edge.:undefined:”:undefined:

    Nonetheless, LF Networking did start some programs to start building the foundation for training as these technologies stabilize and mature. :undefined:“:undefined:We recently launchedONAP and OPNFV training. But other technologies need to reach a certain level of maturity befores we can create courses for them,:undefined:”:undefined: she said. A new :undefined:“:undefined:Introduction to Open Source Networking Technologies:undefined:”:undefined: training course that covers multiple projects is also now available.

    Understanding what:undefined:’:undefined:s going on is the first step in solving a problem. That:undefined:’:undefined:s where events like KubeCon + CloudNativeCon become critical as they bring together people from different communities to learn and solve problems. :undefined:“:undefined:I learned a lot and started to wrap my head around some of these concepts a little bit more,:undefined:”:undefined: Kirksey said.

    A lot of cross-pollination happens at events, too. When you meet people with bright ideas, you can adopt those good ideas and good marketing practices and apply them to your own work.

    :undefined:“:undefined:To be quite blunt, when you see good ideas, you try to harvest them for yourself because, you know, that:undefined:’:undefined:s the point of open source,:undefined:”:undefined: Kirksey said.

    The postHeather Kirksey on Integrating Networking and Cloud Native appeared first onThe Linux Foundation.

    https://www.linuxfoundation.org/blog/heather-kirksey-on-integrating-networking-and-cloud-native/





  • 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
});