SDN will not emerge in a vacuum, however, and with the entire data center turning into a software construct, today’s network manager will find that tomorrow’s enterprise will require skills in storage, server and virtual infrastructure as well. And all the while, new technologies like containers will be coming online that must be integrated into an increasingly dynamic data environment. As linux.com’s Amber Ankerholz points out, Docker utilizes SDN and VXLAN technologies reasonably well, but numerous development projects like Calico and Weaveworks are underway to enable crucial management, integration and orchestration functions. All of this will simply add to the burden of learning the ins and outs of maintaining connectivity across abstract and increasingly distributed infrastructure.
AT&T's (NYSE: T) creation of the Domain 2.0 program, which is driven by the implementation of software-defined networks (SDN) and network functions virtualization (NFV), is causing the telecom equipment industry to rethink how they deliver products and services.
Earlier this year, Facebook led the charge to launch a new open source group – the Telecom Infra Project (TIP) – whose mission is to improve global Internet connections. TIP will employ the same methods Facebook has used to re-design data centers via its Open Compute Project (OCP). Some of TIP’s goals are lofty: such as rethinking network architectures and bringing the Internet to underserved regions of the globe.
In a world where network processors are viewed as a commodity, the assumption is that most innovation will be driven by software. But support is building for the P4 language to boost NFV, as chip specialists point to hardware improvements that will be key for more demanding applications in a virtualized environment.
“Too many people think innovation is all about software,” says Cliff Grossner, an industry analyst with Infonetics. “The pendulum is now swinging back to hardware.”
In the early 1980’s Richard Stallman founded the Free Software Foundation (FSF): a socio-technological movement that revolutionized the software world. In this episode we’ll hear Stallman himself talking about the roots of the movement, and learn of its early struggles.
We are introducing today a new way to enjoy BoilingSteam with our first podcast. It was recorded on the 22nd of May, along with our special guest, ProfessorKaos64, who is pretty well known in the linux gaming community for his work on expanding SteamOS beyond its initial scope of only launching Steam games. You can check his SteamOS-tools page on Git-hub to find out the extent of his work so far.
The DC/OS project is a software platform that’s comprised entirely of open source technologies. It includes some existing technologies like Apache Mesos and Marathon, which were always open source, but also includes newer proprietary components developed by Mesosphere that we’ve donated to the community and which are fully open sourced under an Apache 2.0 license. Features include easy install of DC/OS itself (including all the components), plus push-button, app-store-like installation of complex distributed systems (including Apache Spark, Apache Kafka, Apache Cassandra and more) via our Universe “distributed services app store”. We’re also tightly integrating our popular Marathon container-orchestration technology right into DC/OS, as the default method for managing Docker containers and other long-running services (including traditional non-containerized web applications, as well stateful services such as databases).
To find out more, we interviewed two leaders in this emerging field. Specifically, we wanted to know how Linux and open source software are being used and if they are in fact changing the face of the automotive industry. First, we talk to Alison Chaiken, a software engineer at Peloton Technology and an expert on automotive Linux, cybersecurity, and transparency. She previously worked for Mentor Graphics, Nokia, and the Stanford Linear Accelerator. Then, we chat with Steven Crumb, executive director of GENIVI, who got started in open source in high-performance computing environments (supercomputers and early cloud computing). He says that though he's not a coder anymore, he loves to help organizations solve real business problems with open source software.
Education is an important field for open source software to target. Today’s generation will define the future to come, and the lessons of open source software are important to teach to professors and students, including children, teens, and young adults. There are already several different initiatives to better teach open source, including Fedora, in school. The Fedora Council approved the University Involvement Initiative as an objective for the entire project in early 2014. Its goal is to increase the number of university students who use and contribute to Fedora.
The biggest mistake is bigger than Drupal: They don't consider it at all. This isn't a platform thing, it's a problem that is endemic to the web. Big companies get dragged into accessibility via legal threats. Small companies don't even think about it. Just the act of raising accessibility as an issue, and asking your team to keep it in mind throughout the design and development process is a big deal. You have to start somewhere.
I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3.