ON.Lab’s ONOS Project noted its eighth SDN platform release expands southbound and northbound protocol, legacy device support.
The telecommunications market’s choice of software-defined networking platforms continues to blossom, with the Open Networking Laboratory’s Open Network Operating System Project releasing its latest SDN platform variant under the “Hummingbird” tag.
The SDN platform, which is the eighth version from the open-source ONOS Project, is claimed to offer high availability and scalability, expanded southbound and northbound protocols, and improved ability to support incremental SDN on legacy devices. (Full details are available here.)
In this talk, Rich, the OpenStack Community Liaison at Red Hat, will walk you through what OpenStack is, as a project, as a Foundation, and as a community of organizations.
Fuzz testing (or fuzzing) is a software testing technique that involves passing invalid or random data to a program and observing the results, such as crashes or other failures. Bamvor Jian Zhang of Huawei, who will be speaking at LinuxCon Europe, realized that existing fuzz testing tools — such as trinity — can generate random or boundary values for syscall parameters and inject them into the kernel, but they don’t validate whether the results of those syscalls are correct.
Bamvor Jian Zhang
In his experience, the correctness of arguments passing between the C library and core kernel code is a common problem. And, in his talk — called “Efficient Unit Test and Fuzz Tools for Kernel/Libc Porting,” Bamvor will share some ways to improve the trinity fuzzing tool. We spoke with him to learn more.
Linux.com: Why are syscall issues so common when bringing up a new architecture for the Linux kernel?
Bamvor Jian Zhang: The new porting must fulfill the requirements of the evolving kernel. Usually, there is no standard porting document/reference design. So, porting is always challenging work.
Linux.com: Why don’t existing fuzz testing tools help validate whether syscalls are correct?
Bamvor: Actually, they could do part of the job. Existing fuzz tools focus on the functionality of the syscall not the wrapper. They are useful if the wrapper of the syscall is correct. The wrapper process is done by the porting of kernel and libc. Incomplete or incorrect porting leads to the useless test results with existing fuzz tools.
Linux.com: How did you discover this problem?
Bamvor: We found that trinity could not find the issue even if there are 20 fails in Linux Test Project (LTP). And, we found other issues even after we fixed all the syscall fails in LTP and glibc testsuite. Theoretically, we could add new test cases to existing tools, but this work needs more developers. In the end, the design of ilp32 is evolving. It is hard to catch up on the changes and add new test cases in the limited amount of time.
Linux.com: How can existing tools be improved to help solve the problem?
Bamvor: Generally speaking, we could improve the situation by adding two things to the existing tools. The first thing is to issue the test case of syscall through C library instead of direct syscall. The second thing is to check the argument passing before we execute the real syscall in the kernel.
You won’t want to miss the stellar lineup of keynotes, 185+ sessions and plenty of extracurricular events for networking at LinuxCon + ContainerCon Europe in Berlin. Secure your spot before it’s too late! Register now.
One of the great strengths of open source is that it provides opportunities for everyone. Regardless of background, age, gender, race, ethnicity, nationality, sexual orientation or religion, everyone can benefit from and contribute to some of the most important technologies ever developed.
Yet we know that many groups remain underrepresented in the open source community, which is why The Linux Foundation engages in efforts such as providing diversity scholarships for our training and events and sponsoring organizations such as Women Who Code, Code.org, Blacks in Technology, All Star Code and more.
As part of this ongoing effort, The Linux Foundation is proud to announce we have entered into a partnership with Girls in Tech, a global non-profit focused on the engagement, education and empowerment of girls and women who are passionate about technology.
This partnership will provide Girls in Tech with free and discounted tickets to a range of Linux Foundation events, free space to exhibit at those events and/or to host hackathons and bootcamps, and more. Our goal is to help more girls and women to become involved in, and contribute back to, the open source community.
The 15 events covered in this partnership include:
• MesosCon Europe 2016 • Cloud Foundry Summit Europe 2016 • OpenDaylight Summit 2016 • ContainerCon/LinuxCon Europe 2016 • Embedded Linux Conference/OpenIoT Summit Europe 2016 • CloudNativeCon/KubeCon 2016 • Apache: Big Data and ApacheCon Europe 2016 • MesosCon China 2016 • Node Interactive North America 2016 • Embedded Linux Conference/OpenIoT Summit North America 2017 • Open Networking Summit 2017 • Apache: Big Data and ApacheCon North America 2017 • Cloud Foundry Summit North America 2017 • OpenDaylight Summit 2017 • Open Source Summit North America 2017 • MesosCon North America 2017
Those interested in participating should follow Girls in Tech on social media for more information and offers.
There’s always more we can do to improve diversity in the open source and technology communities in general. Partnerships such as this one are just one element of that effort, and we encourage everyone in the community to contribute their time, energy and resources to making open source accessible to everyone. Learn more about The Linux Foundation’s community giving initiatives.
This latest release continues the river theme but is sensibly named Colorado: It has other advantages as well, namely support for key features such as security, IPv6, service function chaining (SFC) testing, virtual private networks and more.
In addition, Colorado is laying some key groundwork for what lies ahead as the industry comes to terms with the MANO (management and network orchestration) dilemma, says Heather Kirksey, Open Platform for NFV Project Inc. ‘s executive director.
Regardless of the level at which you’re doing your programming, security is going to get in the way. No amount of application abstraction or modern development process seems capable of shielding developers from the barriers raised by security. It’s pretty hard not to hate security when it doesn’t seem to add any intrinsic value, and often gets in the way of providing a delightful user experience. To top it off products can get hacked anyway, in spite of any and all work you do to make your products secure.
I’m one of the operators of Wonderland, Jimdo’s in-house PaaS for microservices.
Two weeks ago, on September 5, I did something embarrassing at work.
We were debugging a broken deployment of our central API service. This API is nothing less than the entry point for managing all container-based services running on our platform, including most of our own system services (by virtue of dogfooding).
In an attempt to fix the problem we were experiencing — our API service failed to scale to a certain number of replicas — I deleted what I believed to be a duplicate instance of the corresponding ECS service in the AWS Management Console…
Microsegmentation, a method to create secure, virtual connections in software-defined data centers (SDDCs), has already emerged as one of the primary reasons to embrace network virtualization (NV). But some vendors believe that East-West encryption of traffic inside the data center could be the next stop in data-center security.
For example, VMware says it is looking at encrypting East-West traffic inside the data center, adding another layer ofsecurity to the SDDC. Why is that important? Today, most firewalls operate on the perimeter of the data center – either guarding or encrypting data leaving the data center for the WAN. And some security products may encrypt data at rest inside the data center. But encrypting the traffic in motion between servers inside the data center – known in the business as the East-West traffic – is not something that’s typically done.
Earliest mentions of the term “bitcoin” in patent titles and abstracts date back to around 2009, while the term “blockchain” begins to appear in patent titles from around 2011. As of June 22, 2016, there were 492 published patent families directed to the theme of blockchain and 192 relating to bitcoin.
Patent applications filed over the last year and a half would not be visible in these statistics, and it is expected that significant numbers of new patent applications connected to these themes have been filed in that period. The numbers we are seeing likely represent the tip of the iceberg.
It’s tricky to say exactly who’s filing these patents, but, anecdotally, the early-stage business community is out-innovating the incumbent banking organizations by some measure, and are likely to be responsible for much of this innovation.
Even in a time when significant Internet speeds are available throughout the globe, every effort to optimize website load times is welcome with open arms.
In this article, we will discuss a method to increase transfer speeds by reducing the file sizes through compression. This approach brings an extra benefit in that it also reduces the amount of bandwidth used in the process, and makes it cheaper for the website owner who pays for it.
To accomplish the goal stated in the above paragraph, we will use Nginx and its built-in gzip module in this article.
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]
