Language Selection

English French German Italian Portuguese Spanish

Legal

FOSS Licensing Debates at OSI and New Open Data From Recursion

Filed under
OSS
Legal
  • April 2019 License-Discuss Summary

    Antoine Thomas asks whether a contributor would be able to revoke/remove their contributions from a project, and how this would affect old versions of a project.

    Kevin Fleming responds that legitimately provided open source licenses are not revocable, but that a project might honor a request out of courtesy.

    Brendan Hickey points out that copyright law may provide special revocation rights, e.g. 17 USC §203. And even without revocation, a contributor could make life difficult for users.

  • April 2019 License-Review Summary

    Van Lindberg submits his Cryptographic Autonomy License (CAL) to the review process. This is a network copyleft license, but with a broader scope than the AGPL. The CAL is motivated by ensuring user autonomy in blockchain-based applications. Lindberg has also written an in-depth blog post that serves as a rationale document. Last month, there had already been preliminary discussion about the license on the license-discuss list (see the summary).

    [...]

    Pamela Chestek provides a careful analysis of unclear language in the license.

    Henrik Ingo is concerned that the anti-DRM provision might not be effective, which leads to some comparisons with the GPLv3 [1,2,3,4].

  • Recursion Releases Open-Source Data from Largest Ever Dataset of Biological Images, Inviting Data Science Community to Develop New and Improved Machine Learning Algorithms for the Life Sciences Industry

Licensing/Legal Facets of FOSS

Filed under
OSS
Legal
  • 5 Best Drag and Drop Builders For WordPress of 2019 [Ed: And proprietary software with "free bait".]

    Depends on your requirements, really. One thing that you need to keep in mind is that the prices are different for different packages, so money is a factor you need to consider before making the decision. For example, Elementor could as well have been the best for beginners had their license not been so restrictive. Also, their Pro version is not GPL.

    Other such drawbacks for other builders make Beaver Builder and Divi clearly the most preferred WordPress page builders. Visual Composer comes very close to these two. So, while there may be a bit of a pocket pinch, you can go for any of these if you want to be on safe hands. Also, while the recent Gutenberg editor holds a lot of promise, it is still going to be a while before it comes anywhere close to any of these powerful builders.

  • Upstream First

    This talk was mostly aimed at managers of engineering teams and projects with fairly little experience in shipping open source, and much less experience in shipping open source through upstream cross vendor projects like the kernel. It goes through all the usual failings and missteps and explains why an upstream first strategy is the right one, but with a twist: Instead of technical reasons, it’s all based on economical considerations of why open source is succeeding. Fundamentally it’s not about the better software, or the cheaper prize, or that the software freedoms are a good thing worth supporting.

    Instead open source is eating the world because it enables a much more competitive software market. And all the best practices around open development are just to enable that highly competitive market. Instead of arguing that open source has open development and strongly favours public discussions because that results in better collaboration and better software we put on the economic lens, and private discussions become insider trading and collusions. And that’s just not considered cool in a competitive market. Similar arguments can be made with everything else going on in open source projects.

  • The sustainability of open source for the long term

    The problem of "sustainability" for open-source software is a common topic of conversation in our community these days. We covered a talk by Bradley Kuhn on sustainability a month ago. Another longtime community member, Luis Villa, gave his take on the problem of making open-source projects sustainable at the 2019 Legal and Licensing Workshop (LLW) in Barcelona. Villa is one of the co-founders of Tidelift, which is a company dedicated to helping close the gap so that the maintainers of open-source projects get paid in order to continue their work.

  • On technological liberty

    In his keynote at the 2019 Legal and Licensing Workshop (LLW), longtime workshop participant Andrew Wilson looked at the past, but he went much further back than, say, the history of free software—or even computers. His talk looked at technological liberty in the context of classical liberal philosophic thinking. He mapped some of that thinking to the world of free and open-source software (FOSS) and to some other areas where our liberties are under attack.

    He began by showing a video of the band "Tears for Fears" playing their 1985 hit song "Everybody wants to rule the world", though audio problems made it impossible to actually hear the song; calls for Wilson to sing it himself were shot down, perhaps sadly, though he and the audience did give the chorus a whirl. In 1985, the band members were young and so was open source, he said. But there were new digital synthesizers available, with an open standard (MIDI) that allowed these instruments to talk to one another. It freed musicians from the need for expensive studio time, since they could write and polish their music anywhere: a great example of technological freedom.

Crowdsourcing license compliance with ClearlyDefined

Filed under
OSS
Legal

Open source use continues to skyrocket, not just in use cases and scenarios but also in volume. It is trivial for a developer to depend on a 1,000 JavaScript packages from a single run of npm install or have thousands of packages in a Docker image. At the same time, there is increased interest in ensuring license compliance.

Without the right license you may not be able to legally use a software component in the way you intend or may have obligations that run counter to your business model. For instance, a JavaScript package could be marked as MIT license, which allows commercial reuse, while one of its dependencies is licensed has a copyleft license that requires you give your software away under the same license. Complying means finding the applicable license(s), and assessing and adhering to the terms, which is not too bad for individual components adn can be daunting for large initiatives.

Read more

GNU and GPL Picks

Filed under
GNU
Legal
  • The decade long wait for Bash 5

    It's a coincidence that the Linux kernel and Bash jumped to version 5.0 at about the same time. While Linus assigns the numbers as he sees fit, Bash changes its version when major adjustments are made. Here's what users can expect in Bash 5.

    My last article about a Bash version change is 10 years old [1]. Version 4 was in the starting blocks at that time, but it took some time for all distributions to switch to this version. Nobody puts their production system at risk without good reason.

    Nevertheless, the change was very attractive for developers of complex scripts, because – thanks to associative arrays – a completely new data structure was introduced. The advantages were more elegant, simpler programs that were also easier to maintain. Other important changes included the coproc command (which supports parallelization) and redirection operators.

  • Stack Clash mitigation in GCC: Why -fstack-check is not the answer

    In our previous article about Stack Clash, we covered the basics of the Stack Clash vulnerability. To summarize, an attacker first uses various means to bring the heap and stack close together. A large stack allocation is then used to “jump the stack guard.” Subsequent stores into the stack may modify objects in the heap or vice versa. This, in turn, can be used by attackers to gain control over applications.

  • Cooperation and freedom for all

    The GPL's "freedom zero" can be applied to more than just open-source software.

    Recently, a discussion came up on one of the mailing lists for a GNU/Linux distribution, on which I feel it is necessary to comment. Because this discussion has a place in world politics today, I am bringing my input to this column.

    I started working for Digital Equipment Corporation (DEC) in 1983. At that time, I had traveled only domestically in the USA, never internationally.

  • Software Freedom Conservancy Announces End to VMware Lawsuit

    Linux developer Christoph Hellwig has announced that he is discontinuing his lawsuit against VMware for non-compliance with the terms of the GPL. Hellwig and the Software Freedom Conservancy accused VMware of including GPLed code associated with vmklinux into VMware's proprietary vSphere product. A German appeals court dismissed the case on February 28. Hellwig and the Software Freedom Conservancy have decided they will not appeal the case further in German courts.

The mysterious history of the MIT License

Filed under
Legal

I say "seemingly straightforward" because the MIT License is one of the most popular licenses used by open source software. The MIT License, Apache License, and BSD license are the main permissive licenses, a term that contrasts with reciprocal licenses like the GPL, which require source code to be made available when software is redistributed.

Given its popularity, you'd think the license's inception would be well-documented. I found various clues that added up to a date in the late 1980s but nothing definitive. However, Keith Packard and Jim Gettys jumped on the thread to offer first-hand accounts of the license's creation. In addition to providing early examples of the license, their help also gave me the context to better understand how the license evolved over time.

Read more

What the new EU copyright law means for open source

Filed under
OSS
Legal

The global open source community was able to breathe a small sigh of relief as the controversial and, at times, bitterly opposed European Union's (EU's) Copyright Directive was finally approved last week. Some last-minute amendments a few weeks before the vote resulted in open source software development being left relatively, but not wholly, unscathed.

In its earlier iterations, the EU copyright proposal, specifically Article 13, made content-sharing platforms directly liable for copyrighted content that users upload. This, in effect, made it mandatory for software code sharing platforms to monitor all content that users upload for potential copyright infringement. The proposal was primarily aimed at music and video streaming platforms rather than software code but the wording was so broad that software code, and developing and sharing platforms like GitHub, Software Heritage, GitLab, GNU Savannah and SourceForge, would be caught in the net.

With the whole premise of open source software being the free and open sharing of code, the open source community was appalled. Several campaigns were launched to push back. The Free Software Foundation Europe and OpenForumEurope joined forces on a campaign, Savecodeshare.eu, to garner support for opposition to the proposed directive.

Read more

Licensing Tricks and Traps in Fake 'FOSS'

Filed under
OSS
Legal

Linux developer abandons VMware lawsuit

Filed under
Linux
Legal

In August 2006, well-known Linux developer Christopher Helwig spotted Linux source code being used illegally in the VMware ESX bare-metal virtual machine (VM) hypervisor. Helwig, with the aid of the Software Freedom Conservancy, eventually sued VMware, Now, after the German Hamburg Higher Regional Court dismissed Helwig's appeal, he has decided that it would be pointless to appeal the decision.

The heart of the lawsuit had been that Hypervisor vSphere VMware ESXi 5.5.0 violated Linux's copyright. That's because VMware had not licensed a derivative work from Linux under the GNU General Public License (GPL). True, VMware had disclosed the vmklinux component under the GPL, but not the associated hypervisor components.

Read more

James Bottomley: A Roadmap for Eliminating Patents in Open Source

Filed under
OSS
Legal

The realm of Software Patents is often considered to be a fairly new field which isn’t really influenced by anything else that goes on in the legal lansdcape. In particular there’s a very old field of patent law called exhaustion which had, up until a few years ago, never been applied to software patents. This lack of application means that exhaustion is rarely raised as a defence against infringement and thus it is regarded as an untested strategy. Van Lindberg recently did a FOSDEM presentation containing interesting ideas about how exhaustion might apply to software patents in the light of recent court decisions. The intriguing possibility this offers us is that we may be close to an enforceable court decision (at least in the US) that would render all patents in open source owned by community members exhausted and thus unenforceable. The purpose of this blog post is to explain the current landscape and how we might be able to get the necessary missing court decisions to make this hope a reality.

What is Patent Exhaustion?

Patent law is ancient, going back to Greece in around 500BC. However, every legal system has been concerned that patent holders, being an effective monopoly with the legal right to exclude others, did not abuse that monopoly position. This lead to the concept that if you used your monopoly power to profit, you should only be able to do it once for the same item so that absolute property rights couldn’t be clouded by patents. This leads to something called the exhaustion doctrine: so if Alice holds a patent on some item which she sells to Bob and Bob later sells the same item to Charlie, Alice can’t force Bob or Charlie to give her a part of their sale proceeds in exchange for her allowing Charlie to practise the patent on the item. The patent rights are said to be exhausted with the sale from Alice to Bob, so there are no patent rights left to enforce on Charlie. The exhaustion doctrine has since been expanded to any authorized transfer, even if no money changes hands (so if Alice simply gave Bob the item instead of selling it, the patent still exhausts at that transaction and Bob is still free to give or sell the item to Charlie without interference from Alice).

Of course, modern US patent rights have been around now for two centuries and in that time manufacturers have tried many ingenious schemes to get around the exhaustion doctrine profitably, all of which have so far failed in the courts, leading to quite a wealth of case law on the subject. The most interesting recent example (Lexmark v Impression) was over whether a patent holder could use their patent power to enforce any onward conditions at all for which the US Supreme Court came to the conclusive finding: they can’t and goes on to say that all patent rights in the item terminate in the first authorized transfer. That doesn’t mean no post sale conditions can be imposed, they can by contract or licence or other means, it just means post sale conditions can’t be enforced by patent actions. This is the bind for Lexmark: their sales contracts did specify that empty cartridges couldn’t be resold, so their customers violated that contract by selling the cartridges to Impression to refill and resell. However, that contract was between Lexmark and the customer not Lexmark and Impression, so absent patent remedies Lexmark has no contractual case against Impression, only against its own customers.

Read more

Copyright Threats to FOSS: Copyrights on APIs and Upload Filter (for Code Also)

Filed under
OSS
Legal
  • No Allies for Oracle’s Win Against Google

    The Supreme Court of the United States (SCOTUS) has received over a dozen amicus briefs in support of Google against Oracle in a long-lasting battle for Java API (software interface) usage. Among others, the Electronic Frontier Foundation, Microsoft, Red Hat, Mozilla, Python Software Foundation, Developers Alliance, along with IP scholars, computer scientists, software innovators, start-ups, and investors raised their concerns about the rulings of the Federal Court of Appeals in 2014and 2018.

  • Support for Google mounts as its Oracle petition is considered

    Google’s argument that it used Oracle’s copyright fairly – with $8.8 billion in the balance – finds support as it hopes for US Supreme Court review

    Google’s petition for certiorari at the Supreme Court represents its last effort in a protracted copyright battle with software company Oracle. The near-decade-long conflict centres on Oracle’s Java programming application, which Google admitted to using...

  • Copyright reform: it’s the final countdown

    This Tuesday MEPs will cast the final vote in a long running process to reform the EU’s copyright law. Their decision will define whether consumers will be able to continue enjoying the internet as a place where they can easily share content with friends and family or be at risk of seeing their uploads systematically blocked by automated filters.

  • Swedish MEPs Announce Support For Article 13, Demonstrate Near Total Ignorance Of What It Actually Entails

    As MEPs get ready to vote on the EU Copyright Directive -- and specific amendments concerning Articles 11 and 13 -- many have not yet said how they are going to vote. However, two Swedish MEPs, Jytte Guteland and Marita Ulvskog, who many had believed would vote against the plan, have suddenly switched sides and say they plan to vote for it. In a rather astounding interview with reporter Emanuel Karlsten the MEPs reveal their near total ignorance of what Article 13 does and what it would require.

    Guteland spoke to Karlsten by phone, and he asked all the right questions. It's worth reading the entire conversation, but here are a few snippets with my commentary.

  • New Report: Germany Caved To France On Copyright In A Deal For Russian Gas

    In the hours leading up to the vote in the EU Parliament on the EU Copyright Directive, the German publication FAZ (which has been generally supportive of the Directive) has released quite a bombshell (in German), suggesting that the reason Germany caved to France on its terrible demands concerning copyright was in order to get France's approval of the controversial Nord Stream 2 gas pipeline from Russia.

    If you don't recall, the German delegation had actually pushed back on the more extreme versions of Article 13 -- and, in particular, had demanded that a final version have a clear carve-out for smaller companies, so as not to have them forced out of business by the onerous demands of the law. However, after some back and forth, Germany caved in to France's demands, with many left scratching their heads as to why. However, some noted the "coincidence" in timing, that right after this, France also withdrew its objections to the pipeline which is very controversial in the EU (and the US, which is threatening sanctions).

  • EU Copyright Directive Vote, GNU nano 4.0 Released, Redox OS 0.5.0 Announced, Sailfish OS 3.0.2 "Oulanka" Now Available and Linux Kernel 5.1-rc2 Released

    Members of the European Parliament vote tomorrow on the Directive on Copyright. Those in the EU can go to SaveYourInternet to ask their representatives to vote against Article 17 (previously Article 13). See this Creative Commons blog post for more information. From the post: "The dramatic negative effects of upload filters would be disastrous to the vision Creative Commons cares about as an organisation and global community."

    [...]

    Sailfish OS 3.0.2 "Oulanka" is now available. Named after the Oulanka national park in Lapland and the Northern Ostrobothnia regions of Finland, this new version fixes more than 44 bugs. In addition, "With this new update you will find that the Top Menu has a new switch for silencing ringtones and there's a new battery saving mode to make the most out of low battery in those moments you need to stretch productivity. Email app supports now sending read receipts to inform that you have read the senders' email. Connectivity was improved in terms of firewall and global proxy. As for the user interface, home screen had memory optimizations for handling wallpapers, freeing memory for running other apps."

  • Inside GitHub’s fight to protect devs from EU’s disastrous Copyright Reform [Ed: Microsoft is a patent and copyright maximalist, this time it just doesn't suit one site.]
  • European Parliament to vote on EU Copyright Directive
  • How #Article13 is like the Inquisition: John Milton Against the EU #CopyrightDirective

    Fundamentally, policing of speech can happen at one of two points: before content disseminates, or after. Policing content after it disseminates involves human agents seeing and reporting content and taking action or requesting action. This can happen on a huge scale or a tiny one: Facebook’s content flagging system, obscenity law in much of the EU and USA, parents who object to books assigned in schools, and China’s 50 Cent Army of two million internet censors, all these act to silence content after it disseminates.

  • The EU votes on a confusing new copyright law Tuesday

    Both provisions are maddeningly vague—laying out broad goals without providing much detail about how those goals can be achieved. This is partly because the EU's lawmaking system occurs in two stages. First, EU-wide institutions pass a broad directive indicating how the law should be changed. Then each of the EU's member nations translates the directive into specific laws. This process leaves EU-wide legislators significant latitude to declare general policy goals and leave the details to individual countries.

    Still, if the legislation's goals are incoherent or contradictory, then something is going to have to give. And critics warn that the package could wind up damaging the Internet's openness by forcing the adoption of upload filters and new limits on linking to news stories.

  • Music Labels Forgot Their ‘Secret’ Article 13 Weapon, So Dan Bull Used it Against Them

    Music is widely acknowledged as one of the most potent and emotive ways to tell a story and send a message. Yet, inexplicably, no major artists in favor of Article 13 have used their talent to tell the world why it should pass. In that silence, UK rapper Dan Bull (with support from Grandayy and PewDiePie) has now seized the day - to explain why it shouldn't.

  • EU backs controversial copyright law

    The European parliament has backed controversial copyright laws which critics say could change the nature of the internet.

  • Even after today's EU Parliament vote, we can still kill Article 13 through pressure on German government to prevent formal adoption by EU Council

    Under normal circumstances, today's outcome of the European Parliament's plenary vote would mean we lost the fight against Article 13 ("upload filters") definitively because a 348-274 majority adopted the bill without amendments after an incredibly narrow 317-312 majority disallowed votes on individual amendments. The latter result indicates a majority against Article 13 was in striking distance, given that no amendment had nearly as much as momentum as the one that would have deleted Article 13 (now named Article 17). Some folks may have given up prematurely, but that's another story.

    If we organize another and even bigger round of street protests in Germany, work with opposition parties, and put maximum pressure on Merkel's junior partner (the Social Democratic Party of Germany, SPD), we may be able to prevent Germany from allowing the directive to pass into law. But we only have two weeks to make it happen. Let me explain step by step.

  • EU’s Parliament Signs Off on Disastrous Internet Law: What Happens Next?

    In a stunning rejection of the will five million online petitioners, and over 100,000 protestors this weekend, the European Parliament has abandoned common-sense and the advice of academics, technologists, and UN human rights experts, and approved the Copyright in the Digital Single Market Directive in its entirety.

    There’s now little that can stop these provisions from becoming the law of the land across Europe. It’s theoretically possible that the final text will fail to gain a majority of member states’ approval when the European Council meets later this month, but this would require at least one key country to change its mind. Toward that end, German and Polish activists are already re-doubling their efforts to shift their government’s key votes.

    If that attempt fails, the results will be drawn-out, and chaotic. Unlike EU Regulations like the GDPR, which become law on passage by the central EU institutions, EU Directives have to be transposed: written into each member country’s national law. Countries have until 2021 to transpose the Copyright Directive, but EU rarely keeps its members to that deadline, so it could take even longer.

Syndicate content

More in Tux Machines

Android Leftovers

Kernel Articles at LWN (Paywall Just Expired)

  • Filesystem sandboxing with eBPF

    Bijlani is focused on a specific type of sandbox: a filesystem sandbox. The idea is to restrict access to sensitive data when running these untrusted programs. The rules would need to be dynamic as the restrictions might need to change based on the program being run. Some examples he gave were to restrict access to the ~/.ssh/id_rsa* files or to only allow access to files of a specific type (e.g. only *.pdf for a PDF reader). He went through some of the existing solutions to show why they did not solve his problem, comparing them on five attributes: allowing dynamic policies, usable by unprivileged users, providing fine-grained control, meeting the security needs for running untrusted code, and avoiding excessive performance overhead. Unix discretionary access control (DAC)—file permissions, essentially—is available to unprivileged users, but fails most of the other measures. Most importantly, it does not suffice to keep untrusted code from accessing files owned by the user running the code. SELinux mandatory access control (MAC) does check most of the boxes (as can be seen in the talk slides [PDF]), but is not available to unprivileged users. Namespaces (or chroot()) can be used to isolate filesystems and parts of filesystems, but cannot enforce security policies, he said. Using LD_PRELOAD to intercept calls to filesystem operations (e.g. open() or write()) is a way for unprivileged users to enforce dynamic policies, but it can be bypassed fairly easily. System calls can be invoked directly, rather than going through the library calls, or files can be mapped with mmap(), which will allow I/O to the files without making system calls. Similarly, ptrace() can be used, but it suffers from time-of-check-to-time-of-use (TOCTTOU) races, which would allow the security protections to be bypassed.

  • Generalizing address-space isolation

    Linux systems have traditionally run with a single address space that is shared by user and kernel space. That changed with the advent of the Meltdown vulnerability, which forced the merging of kernel page-table isolation (KPTI) at the end of 2017. But, Mike Rapoport said during his 2019 Open Source Summit Europe talk, that may not be the end of the story for address-space isolation. There is a good case to be made for increasing the separation of address spaces, but implementing that may require some fundamental changes in how kernel memory management works. Currently, Linux systems still use a single address space, at least when they are running in kernel mode. It is efficient and convenient to have everything visible, but there are security benefits to be had from splitting the address space apart. Memory that is not actually mapped is a lot harder for an attacker to get at. The first step in that direction was KPTI. It has performance costs, especially around transitions between user and kernel space, but there was no other option that would address the Meltdown problem. For many, that's all the address-space isolation they would like to see, but that hasn't stopped Rapoport from working to expand its use.

  • Identifying buggy patches with machine learning

    The stable kernel releases are meant to contain as many important fixes as possible; to that end, the stable maintainers have been making use of a machine-learning system to identify patches that should be considered for a stable update. This exercise has had some success but, at the 2019 Open Source Summit Europe, Sasha Levin asked whether this process could be improved further. Might it be possible for a machine-learning system to identify patches that create bugs and intercept them, so that the fixes never become necessary? Any kernel patch that fixes a bug, Levin began, should include a tag marking it for the stable updates. Relying on that tag turns out to miss a lot of important fixes, though. About 3-4% of the mainline patch stream was being marked, but the number of patches that should be put into the stable releases is closer to 20% of the total. Rather than try to get developers to mark more patches, he developed his machine-learning system to identify fixes in the mainline patch stream automatically and queue them for manual review. This system uses a number of heuristics, he said. If the changelog contains language like "fixes" or "causes a panic", it's likely to be an important fix. Shorter patches tend to be candidates.

  • Next steps for kernel workflow improvement

    The kernel project's email-based development process is well established and has some strong defenders, but it is also showing its age. At the 2019 Kernel Maintainers Summit, it became clear that the kernel's processes are much in need of updating, and that the maintainers are beginning to understand that. It is one thing, though, to establish goals for an improved process; it is another to actually implement that process and convince developers to use it. At the 2019 Open Source Summit Europe, a group of 20 or so maintainers and developers met in the corner of a noisy exhibition hall to try to work out what some of the first steps in that direction might be. The meeting was organized and led by Konstantin Ryabitsev, who is in charge of kernel.org (among other responsibilities) at the Linux Foundation (LF). Developing the kernel by emailing patches is suboptimal, he said, especially when it comes to dovetailing with continuous-integration (CI) processes, but it still works well for many kernel developers. Any new processes will have to coexist with the old, or they will not be adopted. There are, it seems, some resources at the LF that can be directed toward improving the kernel's development processes, especially if it is clear that this work is something that the community wants.

Server Leftovers

  • Knative at 1: New Changes, New Opportunities

    This summer marked the one-year anniversary of Knative, an open-source project that provides the fundamental building blocks for serverless workloads in Kubernetes. In its relatively short life (so far), Knative is already delivering on its promise to boost organizations’ ability to leverage serverless and FaaS (functions as a service). Knative isn’t the only serverless offering for Kubernetes, but it has become a de-facto standard because it arguably has a richer set of features and can be integrated more smoothly than the competition. And the Knative project continues to evolve to address businesses’ changing needs. In the last year alone, the platform has seen many improvements, giving organizations looking to expand their use of Kubernetes through serverless new choices, new considerations and new opportunities.

  • Redis Labs Leverages Kubernetes to Automate Database Recovery

    Redis Labs today announced it has enhanced the Operator software for deploying its database on Kubernetes clusters to include an automatic cluster recovery that enables customers to manage a stateful service as if it were stateless. Announced at Redis Day, the latest version of Kubernetes Operator for Redis Enterprise makes it possible to spin up a new instance of a Redis database in minutes. Howard Ting, chief marketing officer for Redis Labs, says as Kubernetes has continued to gain traction, it became apparent that IT organizations need tools to provision Redis Enterprise for Kubernetes clusters. That requirement led Redis Labs to embrace Operator software for Kubernetes developed by CoreOS, which has since been acquired by Red Hat. IT teams can either opt to recover databases manually using Kubernetes Operator or configure the tool to recover databases automatically anytime a database goes offline. In either case, he says, all datasets are loaded and balanced across the cluster without any need for manual workflows.

  • Dare to Transform IT with SUSE Global Services

Audiocasts/Shows: FLOSS Weekly and Linux Headlines

  • FLOSS Weekly 555: Emissions API

    Emissions API is easy to access satellite-based emission data for everyone. The project strives to create an application interface that lowers the barrier to use the data for visualization and/or analysis.

  • 2019-11-13 | Linux Headlines

    It’s time to update your kernel again as yet more Intel security issues come to light, good news for container management and self-hosted collaboration, and Brave is finally ready for production.