Home Blog Page 1636

CFPs Due! ApacheCon, CloudStack, LF Collaboration Summit, Android Builders Summit & ELC

 

Linux Foundation Vice President and creator of LinuxCon and CloudOpen Amanda McPherson recentlyblogged about our 2014 event schedule. New on the calendar this year is the addition of both ApacheCon and the CloudStack Collaboration Conference. The CFP for both of these events closes this Saturday, as does the CFP for The Linux Foundation Collaboration Summit, Android Builders Summit and Embedded Linux Conference.

Here are some highlights for each event:

ApacheCon: April 7-9, 2014 in Denver

  • Doubles its tracks this year, increasing content coverage across many Apache projects. Projects already represented on the forthcoming program include Hadoop, Subversion, Felix, Tomcat, CloudStack, HTTPServer, Lucene, Shiro, Cassandra, Tika, Traffic Server, CXF, and Hive, among at least eight others.

  • Submit a Proposal

CloudStack Collaboration Conference North America: April 9-11, 2014 in Denver

  • Register for ApacheCon and attend CloudStack for free

  • Early-bird registration deadline is this Friday, January 31

  • Submit a Proposal

The Linux Foundation Collaboration Summit: March 26-28, 2014 in Napa

Android Builders Summit & Embedded Linux Conference: April 29 – May 1, 2014 in San Jose

  • Combined event in 2014 offering attendees a greater value with two events at one registration fee.

  • Evening Reception on Wednesday, April 30, at the Tech Museum of Innovation plus the traditional Demo Showcase Happy Hour on Tuesday, Apr 29, which will give attendees multiple ways to network.

  • Submit a Proposal for ELC tracks

  • Submit a Proposal for ABS tracks

There has never been a better time to be a part to the Linux and open source community. Please join us this year in one or more of the event venues we have scheduled; share your work and your ideas; and learn from the best of the best in the industry and community. Linux and open source are how everything is being built today. Don’t miss out.

https://www.youtube.com/watch?v=-WUeelICQ2U?rel=0″ allowfullscreen=”true” frameborder=”0″ width=”425




Distro Review: 60 Days Beating Up openSUSE 13.1

openSUSE fans claim it has the best KDE4 implementation, and is an all-around uber-nice distro. Does it? Is it?

Short story for the impatient: openSUSE is a rock-solid Linux distribution with a nice KDE4 implementation and lots of high-end enterprise goodness.

SUSE tuxMost distro reviews go no deeper than a quick look at a live CD/DVD, or a quick tour in a virtual machine, some commentary on the colors, a few screenshots, and done. Linux distro installers have been the best of any operating system for years now, so there is little point in discussing installation, and colors? Is it a mystery that we can change the colors? openSUSE 13.1 was released in November 2013, and I decided to use it for 30 days before reviewing it. Well, time got away from me and here it is nearly 60 days, so it has had a thorough pummeling at my brutal hands.

Not Too Broken

openSUSE is an independent project that receives support from SUSE. SUSE’s development strategy is first stability, then features, then performance. openSUSE is a little different. As Jos Poortvliet (openSUSE’s community manager) puts it, it ships when it’s not too broken. openSUSE doesn’t try to match SUSE’s dedication to perfection, but follows a timed release schedule of a new release every eight months, and a version upgrade every two years. So we’ll get 13.1, 13.2, and 13.3, and then 14.1.

So what does “not too broken” mean in real life? It translates to a good solid distro that you can use for everything from ARM systems to desktops to notebooks to high-demand high-traffic servers.

Bleeding Edge Goodness

openSUSE is a great distro for trying out new technologies. While everyone else is still telling us that Btrfs is not ready for production systems, SUSE Enterprise Linux has supported it since SLES 11 SP2, and it’s also available (though not default) in openSUSE. The Snapper graphical Btrfs manager is a must-have; it works beautifully and makes managing snapshots as easy as falling over. The openQA automated distro build tester is an amazing tool for any distro. This release adds Android device integration in the Dolphin file manager, which is a very cool thing. Because starting with Android 4.0, Ice Cream Sandwich, most Android devices use the MTP (Media Transfer Protocol) to transfer files to a PC, instead of appearing as a generic USB mass storage device. This causes trouble for Linux users because MTP is not installed in most distros by default, though it is in repos. openSUSE 13.1 includes it by default so when you plug in your Android gadget (tablet, phone, Kindle) it automatically shows up in Dolphin.

We also get MariaDB in place of MySQL, OpenStack Havana, Samba 4.1, which is the Active Directory replacement, an experimental KWin Wayland backend, and VLC integration with Phonon. VLC may replace gstreamer as the Phonon backend in 13.2. Both VLC and gstreamer are excellent multimedia frameworks, and in my perfect world it is Phonon that would go away, because for me it gets in the way and it cannot be removed or disabled.

Glitchy Audio and Video

Audio and video were a little weird at first. I kept getting odd pops in the audio between tracks on Pandora and on music CDs. Video did not scroll or redraw smoothly, but rather it hung to the point that it was getting in the way of doing work. Both issues were cured after an update or two and are now nice and smooth.

sudo is Different

If you’re used to how Ubuntu and its derivatives configure sudo, which is to give the default user full privileges and a locked root user account, openSUSE’s handling of sudo might seem a little weird. The openSUSE default is for sudo and su to behave similarly: both need the root password. This is a pointless way to use sudo, so you’ll need to run visudo to set it up correctly. You’ll still need the root password for YaST.

All Users See Your Stuff

openSUSE uses the ancient convention of stuffing all users into the users group, so everything in all home directories are visible to all users. I’ve always thought this is weird, and while YaST lets you choose a different default group there is no option for user private groups. In fact the dropdown list to select a different default group merely shows you all existing groups, which doesn’t help because you don’t want to use any of these as the fig-2-openSUSE-downloadsdefault for a human user. So you’ll need to use the useraddcommand to set up new users instead to give your users their own private groups.

KDE4 Updates Fun

I’ve been a KDE fan since KDE 1.something, way back in the days of pixely graphics. It’s always been complex, and the current versions are great steaming masses of complexity. KDE4’s configuration options and features are legion, so it’s often difficult to tell where a problem originates– is it KDE wigging out, or the underlying distro? Like notifications.

For some reason notifications became a great big important deal to some of the major Linux projects such as Ubuntu, GNOME, and KDE, so they’ve invested a lot of energy into giving every last little process and task a voice. So we get to enjoy all manner of interruptions, rather like baby birds who want something to eat RIGHT NOW. I’ve given up trying to tame the darned things and just turn them off, which is a long and involved process, and it will give me something to click on when I am too old and senile to do much else. Sort of a forever whack-a-mole game. Occasionally they are a little bit useful, and sometimes they’re just plain mystifying, like update notifications (figure 2). The top pane shows progress. Nowhere did it tell me the total size of the downloads, or give an estimated time to completion. Somehow packages are downloaded even though it says 0KB network transfer. It also says I should review the proposed updates, and restart my system now. Magic 8 Ball says just do it and quit bothering me.

Is this a KDE issue? Something weird with openSUSE? Who knows. As long as the updates work I shall content myself with scowling at it occasionally.

The Rest of the Story

There really isn’t much to say. openSUSE works. I have no problems with dependency conflicts, installing and removing all kinds of software including source builds, playing with mass widgets, running gobs of VMs, doing multi-channel audio recording, and video editing without drama. It’s a nice distro with a good responsive community and good documentation. It’s great for KDE fans, and for server admins who want a rich set of advanced enterprise functionality. It is a solid distro that I recommend without reservation.

Citrix latest XenDesktop, XenApp plug into Amazon Web Services, CloudStack

Citrix is also bundling in mobile device management capabilities at a discount for select XenDesktop and XenApp customers.

10 cool Android apps to start the year

There are so many apps in the Google Play store it can be hard finding those useful gems. We’ve done the work for you with these 10 cool Android apps.

VCollab: Displaying Ansys EKM Simulation Models in a Browser

Over at the Ansys Blog, Thomas Lehnhaeuser writes that VCollab softwares enables users to save time and view simulation models and their results without having to open a corresponding post-processing tool.

 
Read more at insideHPC

Sign up for International Summer School on HPC Challenges

Graduate students and postdoctoral scholars from institutions in Europe, Canada, Japan and the United States are encouraged to apply for the fifth International Summer School on HPC Challenges in Computational Sciences, to be held from 1 to 6 June 2014 in Budapest, Hungary.

 
Read more at insideHPC

OpenDaylight Developer Spotlight: Hugo Trippaers

OpenDaylight is an open source project and open to all. Developers can contribute at the individual level just like any other open source project. This blog series highlights the people who are collaborating to create the future of Software Defined-Networking (SDN) and Network Functions Virtualization (NFV).

Hugo Trippaers currently works as a mission critical engineer for Schuberg Philis with 20 years of IT experience in roles ranging from network architect to software developer. Within every role, Hugo had an eye for open source projects and has often been contributing code and knowledge. In his current position he is spending most of his time writing code for open source projects.

How did you get involved with OpenDaylight? What is your background?

I got involved with SDN when one of my colleagues asked me to look at integrating Nicira NVP with Apache CloudStack (ACS). When I said yes, I got on a rollercoaster ride that took me to the Nicira offices in Palo Alto where I was able to meet with Martin Casado and the other folks at Nicira. That really got me hooked on the whole concept of SDN, and I integrated SDN support into Apache CloudStack. Since that day I’ve been deeply involved with the Apache CloudStack (ACS) community where I am one of the members of the Project Management Committee. My goal for ACS is to make sure that Apache CloudStack supports as many SDN solutions as possible. When I learned of the OpenDaylight Project I knew I wanted to have support for that as well. After e-meeting with Brent Salisbury and Madhu Venugopal on how to do the integration, I got really interested in the internals of OpenDaylight and started to help out where I could.

What projects are you working on for OpenDaylight? Any new developments to share?

My main focus is the Open vSwitch database plugin (OVSDB). This project is instrumental in getting overlay-based network virtualization supported using Open vSwitch, which is what I wanted to support in Apache CloudStack. As a company, we are using this technology on a daily basis, so I have some practical experience that I can use to deal with real world scenarios.

I’ve been simultaneously working on two sides of the project. While working on the OVSDB project to get all the features supported that a cloud management system expects, I’ve also been working on the ACS side to get the integration plugin ready for the main branch. By being involved with the OVSDB project I could immediately discuss my challenges and develop solutions. For somebody writing an integration layer between two products it’s awesome to be able to tackle challenges on both ends at the same time.

Read more at OpenDaylight Blog

Could Samsung Focus Exclusively on Chromebooks?

How focused has Samsung become on Chromebooks–portable computers that run Google’s cloud-centric Chrome OS? According to a report in DigiTimes, after cutting its targets for notebook computer sales, the company may have plans to “no longer launch conventional notebook models except Chromebooks in 2015, according to Taiwan-based supply chain makers.” While there is no official confirmation from Samsung, the move would represent a big shift for Samsung and one of the biggest votes of confidence yet for Chromebooks.

 



 
Read more at Ostatic

Linode’s Command Line Interface Tool Helps Automate Cloud Servers

All over the technology arena, the Command Line Interface (CLI) still commands attention. As a case in point, Linode, a player in the cloud hosting space, today announced availability of the Linode CLI, a tool that provides a way to provision and manage Linode cloud services from the command line. The tool is designed to enable users to easily automate common tasks, such as creating, rebooting, or resizing servers, while also making it possible to manage DNS records and distribute workloads across backend Linodes.

 

 
Read more at Ostatic

Upstart SolidXK Distro Seeks First Business Customers

SolydXK started last March as the unofficial Linux Mint Debian Edition with KDE. Though there had been speculation that an official KDE version of the popular desktop distribution would surface, ZDNet wrote recently, SolydXK co-founders Arjen Balfoort and Amadeu Ferreira took it upon themselves, with the support of other Mint community members, to actually build it.

arjen balfoortNow less than a year later, Balfoort says SolydXK has gained esteem within the Linux community, thanks in part to some early positive reviews. In addition to supporting a home edition aimed at inexperienced users and Debian fans alike, they’re starting to develop professional support and services for business customers who are interested in using SolydXK on the desktop. The home edition will serve as a testbed for features in the business edition.

“The first year was focused on the early adopters, people from within the Linux community interested in what SolydXK has to offer: a stable base, with an attractive desktop, and a well structured update process to keep the system up-to-date,” said Balfoort, a business consultant and former Microsoft developer. “They make the core of our community, and spend a lot of time in making SolydXK better with each release. 

“While development, and interface design is a continuous process, we need to focus on how to jump that (Geoffrey Moore’s) “chasm” in the coming year,” he said. “To accomplish that, we are going to market SolydXK outside the Linux community.”

Here Balfoort discusses how the distribution got started; how he built it; the community support behind it; lessons from starting a new open source project; and his vision for the Linux distribution as an ideal desktop for small and medium sized businesses and nonprofits.

Why did you create SolydXK?

Balfoort: During my working experience I have had many opportunities to see how enterprises manage their business processes with, and often without, the help of IT. When the environment changed for whatever reason, the necessity arose to change these processes. I found it rather surprising that the board of directors did not see the value of IT as being an intrinsic part of the business strategy. IT is considered as inevitable expenses, and not a part that is responsible for the ROI (Return On Investment). I also realized the steel grip of vendor lock-in, that lead to a form of snow-blindness: considering open source solutions as being part of your business IT architecture was not even considered, and licensing fees, maintenance costs, and replacement costs were seen as costly, but inevitable facts of life.

When I asked what was the argument for replacing the desktops, the answer was always that the current Windows version was out of date, and needed to be replaced…with the new Windows version. A quick survey made me realize that a large part of those desktops were used for simple office tasks, and that most specialized tools were browser-based, but still IT management did not consider any alternatives. That moment of astonishment made me want to learn more about what open source had to offer, how open source projects were organized, and what the added value for businesses could be. Being a Microsoft business consultant, I started within my comfort zone: the operating system.

How much experience did you have with Linux before you started the project?

Before I started the unofficial LMDE KDE, I had little to no experience with Linux. I already had a long career as a Microsoft consultant, and before that as a Microsoft developer, but Linux was quite new to me. The day I became a member of the Linux Mint forum (January 18, 2012) was the day I first installed Linux. I was still a Linux newbie when I started my “LMDE Homebrew” thread on the Linux Mint forum in June the same year. SolydXK co-founder, Amadeu Ferreira, was one of the first who started helping. He has a long experience with Linux, and in-depth knowledge of Debian in particular. SolydXK was born on March 1, 2013. So, you might say I had a pretty steep learning curve, and SolydXK wouldn’t have come this far if not for the help we received from our community.

How did you build it?

SolydXK was built with a lot of help from our community, patience, perseverance, and a healthy dose of pigheadedness. However, if you are referring to the technical aspects of the project, I would need to divide the project into the operating system itself, and the update pack process. The operating system is based on a regular live Debian testing ISO without a desktop environment. From there I added the packages that were decided by the community, adapted the configuration for a best out-of-the-box experience, created a design that would appeal to the target public, and developed software to fill in the gaps.

You cannot have a solid distribution without the right support, and one of our main concerns was the update process. How were we going to distribute our custom packages, and how would we be able to ensure a stable update process? Part of that update process is the repositories, from where all packages are distributed to our users. DTP (Development, Testing, Production) environments were set up for each repository, with a total of six repositories. All this is needed to keep the update process maintainable, and to minimize risk of breakage during upgrades.

What is your vision for the distribution now and where does it fit into the Linux ecosystem?

SolydXK’s home editions were primarily created to be a low-maintenance Linux distribution for the inexperienced user. They also serve to attract those important early adopters, the people with in-depth knowledge of the Linux system, and particularly Debian’s inner workings. They make up the core of our community, and they provide us the possibility to deliver a solid, up-to-date system with a unique upgrade system.

This is the perfect environment to find out what works, and what doesn’t. Technical issues are tackled far before Debian stable switches to a new stable version. The chosen software set, is decided within the community, and the same community proposes configuration changes to realize a better out-of-the-box experience.

All this collected knowledge is used to shape the Business Editions, and the coming support, and services. While Red Hat targets enterprises, SolydXK targets small, and medium sized businesses, and non-profit organizations with the Business Editions.

Who is the community behind SolydXK? 

SolydXK was created within the Linux Mint community, and was known at that time as “The unofficial LMDE KDE”. We started SolydXK with just a handful of Linux Mint forum members. It was only because of some very positive reviews by Dedoimedo, Quidsup, and Full Circle Magazine that SolydXK became known within the Linux community.

How has your work in open source software informed your business work and vice versa?

With my experience I’m now able to better inform my customers about the importance of community centered business thinking, and that there are viable alternative open source solutions. It is important to understand that money is not a good motivation to choose an open source solution, and that giving something back to the community does not mean you’re losing control over the chosen open source solution.

Are you working on SolydXK full time now? How will SolydXK develop as a business?

Although I would love to spend all my time on SolydXK, it is unrealistic to do so at the moment. SolydXK is still a very young project. It’s slowly getting more attention within the Linux community, but outside the Linux community, it is blissfully unknown. We are now at the beginning of what is known as Geoffrey Moore’s “chasm”. The first year was focused on the early adopters, people from within the Linux community interested in what SolydXK has to offer: a stable base, with an attractive desktop, and a well structured update process to keep the system up-to-date. They make the core of our community, and spend a lot of time in making SolydXK better with each release.

While development, and interface design is a continuous process, we need to focus on how to jump that “chasm” in the coming year. To accomplish that, we are going to market SolydXK outside the Linux community, develop professional support, and services for businesses, and organizations. We need to find our first middle sized organizations that are contemplating changing their desktops, but don’t know where, and how to start. We also need to find partners to guarantee continuity. We’ll need marketeers, project leaders, developers, knowledge of international law, sponsors, and much, much more.

What have you learned about the Linux community and open source development in your first year?

The community is the heart of any open source project. From the beginning I knew that I had to carefully, and patiently keep working on creating a community where it is safe for beginning Linux users to ask their questions. Communities are fluid entities: individuals come, and go as they please. They bring with them an enormous diversity in experience, knowledge, and personality. An open, and democratic decision process is one of the major tools to encourage people to help shape the project.

Often the open source development process is compared with those of commercial companies where the latter has development focus, and Linux has not. This, in my eyes, is a misconception. Commercial business models focus on profit maximization through competition, where business processes are centered around the organization, and decisions are made by a board of directors. Linux focuses on collaboration, and diversity, where business processes need to add value to the community that gives Linux reason for existence, and decision making is a complex democratic process.

Comparing Linux to commercial companies, or considering these companies as competitors, is focusing on something that is not inherent to the heart of Linux: the community. Open Source projects exist because it has a heart, not a wallet that needs to be filled. It does not mean you cannot make a profit with open source, or Linux. It means that our motivation is not profit maximization, but adding value to the community. If making profit adds more value to the community, then making profit is part of our business strategy.

What advice would you give a developer interested in building their own distribution?

In the estate agency business, the mantra “location, location, location” is used to describe what is important. For any kind of business, but in particular for a starting business when the team is still very small, the mantra “focus, focus, focus” is more adequate. Open source projects often have a technical focus because the founders have a technical background. A single focus on technique will only endanger the continuity of the project on the long run. Make it clear what your motivation is, for whom you started the project, what you want to achieve, and how you plan to realize your stated goals. Only when that is clear, you can decide on the technical aspects of the project, and the processes that support the project.

What is your business pitch to companies outside the Linux community who are looking to change operating systems?

SolydXK is a stable, and secure operating system, and is a viable alternative for small, and medium sized businesses, non-profit organizations, and home users. SolydXK is not hardware intensive, and uses little hardware resources, which makes it suitable for even the older systems in your organization. SolydXK needs to be installed just once throughout the system’s live-cycle, and upgrades are thoroughly tested by our testing team, and made available in quarterly periods thus minimizing the risk of breakage to an absolute minimum. Support is given through our community’s forum, and this year we’ll professionally extend support, and services in the following areas:

  • Extended repositories life cycle, beyond Debian’s stable cycle.

  • Extensive support during stable transitions.

  • Advise on community centered thinking within (parts of) the organization.

  • Advise on, and realize open source middleware solutions, and enterprise integration.