Language Selection

English French German Italian Portuguese Spanish

OSS

Leftovers: OSS

Filed under
OSS

OSS in the Back End

Filed under
OSS
  • Open Source NFV Part Four: Open Source MANO

    Defined in ETSI ISG NFV architecture, MANO (Management and Network Orchestration) is a layer — a combination of multiple functional entities — that manages and orchestrates the cloud infrastructure, resources and services. It is comprised of, mainly, three different entities — NFV Orchestrator, VNF Manager and Virtual Infrastructure Manager (VIM). The figure below highlights the MANO part of the ETSI NFV architecture.

  • After the hype: Where containers make sense for IT organizations

    Container software and its related technologies are on fire, winning the hearts and minds of thousands of developers and catching the attention of hundreds of enterprises, as evidenced by the huge number of attendees at this week’s DockerCon 2016 event.

    The big tech companies are going all in. Google, IBM, Microsoft and many others were out in full force at DockerCon, scrambling to demonstrate how they’re investing in and supporting containers. Recent surveys indicate that container adoption is surging, with legions of users reporting they’re ready to take the next step and move from testing to production. Such is the popularity of containers that SiliconANGLE founder and theCUBE host John Furrier was prompted to proclaim that, thanks to containers, “DevOps is now mainstream.” That will change the game for those who invest in containers while causing “a world of hurt” for those who have yet to adapt, Furrier said.

  • Is Apstra SDN? Same idea, different angle

    The company’s product, called Apstra Operating System (AOS), takes policies based on the enterprise’s intent and automatically translates them into settings on network devices from multiple vendors. When the IT department wants to add a new component to the data center, AOS is designed to figure out what needed changes would flow from that addition and carry them out.

    The distributed OS is vendor-agnostic. It will work with devices from Cisco Systems, Hewlett Packard Enterprise, Juniper Networks, Cumulus Networks, the Open Compute Project and others.

  • MapR Launches New Partner Program for Open Source Data Analytics

    Converged data vendor MapR has launched a new global partner program for resellers and distributors to leverage the company's integrated data storage, processing and analytics platform.

  • A Seamless Monitoring System for Apache Mesos Clusters
  • All Marathons Need a Runner. Introducing Pheidippides

    Activision Publishing, a computer games publisher, uses a Mesos-based platform to manage vast quantities of data collected from players to automate much of the gameplay behavior. To address a critical configuration management problem, James Humphrey and John Dennison built a rather elegant solution that puts all configurations in a single place, and named it Pheidippides.

  • New Tools and Techniques for Managing and Monitoring Mesos

    The platform includes a large number of tools including Logstash, Elasticsearch, InfluxDB, and Kibana.

  • BlueData Can Run Hadoop on AWS, Leave Data on Premises

    We've been watching the Big Data space pick up momentum this year, and Big Data as a Service is one of the most interesting new branches of this trend to follow. In a new development in this space, BlueData, provider of a leading Big-Data-as-a-Service software platform, has announced that the enterprise edition of its BlueData EPIC software will run on Amazon Web Services (AWS) and other public clouds.

    Essentially, users can now run their cloud and computing applications and services in an Amazon Web Services (AWS) instance while keeping data on-premises, which is required for some companies in the European Union.

FOSS in Multimedia

Filed under
Movies
OSS
  • Organize your movie and TV files with tinyMediaManager

    The trouble with video files is that they are not easily parseable. How can your computer tell whether that 8 GB file in your ~/Movies folder is the latest superhero movie, or your daughter's soccer game?

    I consider myself an early adopter of digital content. I prefer a digital format, and since I consume a lot of independent content that doesn't have the budget for physical releases anyway, most of my purchases are digital files. I keep these on an NFS shared drive, and stream to Kodi or ncmpcpp, or whatever media client I happen to be using on any given Linux or Android device.

  • 6 reasons why Guayadeque is a music lover's open source player

    Recently I upgraded my laptop's Linux to the latest release, and I was surprised and saddened to discover that the wonderful music player Guayadeque seems to be considered as dead upstream, at least in Debian and Ubuntu. In a January blog post, the original author Juan Rios (@anonbeat) wrote that he is no longer able to support the code, which relies on outdated version of GStreamer 0.10. (When I asked about the status of Guayadeque on AskUbuntu, someone replied that it can now be built from source using the code on GitHub, so I'm keeping my fingers crossed.)

  • Which open source audio player is your favorite?

Leftovers: OSS

Filed under
OSS
  • twenty years of free software -- part 4 ikiwiki-hosting
  • Joe Colantonio: ‘Why Recreate the Wheel — Use Open Source’

    Joe Colantonio wants to “show you how to succeed with all your testing efforts.” He says, “Automation testing, like all development efforts, is difficult. Most projects don’t succeed.” Frankly, it’s all a little over our heads.

  • Apache Libcloud, Focused on Cloud Interoperability, Reaches 1.0 Milestone

    Are you familiar with Apache Libcloud? It's an important open source project in the cloud interoperability arena, which provides a Python library for interacting with many of the popular cloud service providers using a unified API.

  • PostgreSQL 9.6 Beta 2 Released

    The PostgreSQL Global Development Group announces today that the second beta release of PostgreSQL 9.6 is available for download. This release contains previews of all of the features which will be available in the final release of version 9.6, including fixes to many of the issues found in the first beta. Users are encouraged to begin testing their applications against 9.6 beta 2.

  • PostgreSQL 9.6 Beta 2 Released

    Following last month's PostgreSQL 9.6 Beta 1 release, a second beta is now available for testing.

    As outlined already on Phoronix when looking at the PostgreSQL 9.6 features, this update brings parallel query support, synchronous replication now supports multiple standby servers, full-text search for phrases, support for remote joins/sorts/updates, "substantial" performance improvements (especially for many-core servers), no more repetitive scans of old data by auto vacuum, and much more.

  • LibreOffice 5.1.4 available for download

    The Document Foundation (TDF) announces LibreOffice 5.1.4, the fourth minor release of the LibreOffice 5.1 family, targeted at individual users and enterprise deployments. Users of previous LibreOffice releases should start planning the update to the new version.

  • 6 New Programming Languages You Need To Learn In 2016

    If you are willing to learn a new programming language, you are at the right place. With changing times and the need for more performance, new programming languages like Swift and Go are gaining ground. So, choose your new weapon and start learning one of these in-demand programming languages.

  • Thursday's security advisories

Open Source and Crowdsourcing Are Not Synonyms

Filed under
OSS

OSI Board alumnus Simon Phipps recently provided some clarification to FastCo.Design around common misunderstandings related to "sourcing". We've seen more and more of these, although most often--like this example--innocent enough. However, these do provide great opportunities to remind the public about what open source actually is, and why it is so valuable.

The headline (and resulting slug) of your recent article about Mozilla unfortunately mis-states the nature of the crowdsourcing in which they are engaging by treating "open source" interchangeably with crowdsourcing. Despite sounding the same they are very different; the key difference is the ownership of the outcome.

Read more

Snyk aims to help developers secure use of open source code

Filed under
OSS

Developers relying on open source code (or packages) is pretty much the norm these days. As software eats the world, the world is dining out on open source software.

But, regardless of how much time utilising someone else’s code can save you as a developer, it can also mean outsourcing the security of the code you ship, or spending a serious amount of time staying on top of known or newly discovered open source package vulnerabilities.

Read more

Xen 4.7 Open Source Linux Hypervisor Arrives with Non-Disruptive, Live Patching

Filed under
Linux
Server
OSS

Today, June 23, 2016, the Xen Project has had the great pleasure of announcing the immediate availability for download of the Xen 4.7 open-source Linux hypervisor software for GNU/Linux operating systems.

Read more

Leftovers: OSS

Filed under
OSS
  • ​Apache Libcloud: The open-source cloud library to link all clouds together

    One of the great problems with cloud has always been interoperability. The Apache Software Foundation (ASF) addresses this problem with the release of Apache Libcloud v1.0, the cloud service interoperability library.

  • Why share / why collaborate? - Some useful sources outside Debian

    I consider that the Golden Rule requires that if I like a program I must share it with other people who like it. Software sellers want to divide the users and conquer them, making each user agree not to share with others. I refuse to break solidarity with other users in this way. I cannot in good conscience sign a nondisclosure agreement or a software license agreement. ... "

  • "But I'm a commercial developer / a government employee"

    Your employer may be willing to negotiate / grant you an opt-out clause to protect your FLOSS expertise / accept an additional non-exclusive licence to your FLOSS code / be prepared to sign an assignment...

  • How to share collaboratively

    Always remember in all of this: just because you understand your code and your working practices doesn't mean that anyone else will.

  • twenty years of free software -- part 3 myrepos

    myrepos is kind of just an elaborated foreach (@myrepos) loop, but its configuration and extension in a sort of hybrid between an .ini file and shell script is quite nice and plenty of other people have found it useful.

    I had to write myrepos when I switched from subversion to git, because git's submodules are too limited to meet my needs, and I needed a tool to check out and update many repositories, not necessarily all using the same version control system.

  • Being open to open source and creating a new business category at VMWare

    In the age of developer-defined infrastructure, where developers have decision making power in application and cloud infrastructure technologies, open source has proven to be a powerful go-to-market and distribution method for both startups and enterprises. Developers are always looking for new technologies to improve their productivity.

  • Rust implementation of GNUnet with GSoC - Mid-term progress

7 open source terminal games for Linux

Filed under
OSS
Gaming

Do fancy graphics really make a game better? Can a text-based game for Linux still keep you entertained?

Don't get me wrong, I do occasionally enjoy playing a AAA game release from a major studio. But as I've gotten older, I've found that I really value gameplay (and nostalgia too, admittedly) far more than how photorealistic my gaming experience is.

Read more

Lessons learned for building an open company with transparent collaboration

Filed under
OSS

In the first part of this two-part series, Building a business on a solid open source model, I described how an open source business needs to provide a solid ground for all stakeholders, users, contributors, employees, customers, and of course investors. Foundations, licenses, and trademarks can be helpful in building an open ecosystem. Open source communities need supporting organizations to work transparently, otherwise there are barriers to contribution. Code might be public, but code dumps (like Google tends to do with Android) don't always facilitate collaboration. To encourage collaboration, you must go one step further and be proactive. Development in a place like GitHub or GitLab, and having open feature planning meetings and conferences help toward that goal. But still, open source project leaders can do more.

Read more

Syndicate content

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30