Home Blog Page 861

Resizing MySQL Instances and Volumes using OpenStack Trove Database as a Service

Anyone with experience managing databases knows that they often grow over time – requiring additional resources on the machine where the database is running. A common practice is over-provisioning machine resources right from the start though, of course, that could be wasteful.

Here, we’ll show you just how easy it is to re-size a MySQL database running in private cloud DBaaS using the Tesora Database as a Service Platform, which is based on OpenStack Trove.

Step 1: To use OpenStack Trove, first you will need to have Guest Images for each datastore. These images are loaded to OpenStack Glance (where virtual machine images are stored) and registered with Trove. Some guest images for development and testing are available for download from OpenStack at http://tarballs.openstack.org/trove/images/ubuntu. If you’re looking for more information, check out this article, Building a database guest image for OpenStack Trove.

Step 2: Next, using the Tesora DBaaS platform dashboard, log in as the admin user. In our example, let’s say that the MySQL database instance you need to re-size is currently allocated 3 gigabytes. Use the “Actions” pulldown on your database instance and select “Resize Volume”. Simply specify the new amount, for example, let’s say 4 gigabytes and that is it.

Step 3: Next, you can scale up the instance by going back to the “Actions” pulldown on the database instance and this time selecting “Resize Instance”. Use the pulldown to select a larger size. In our example, let’s say the existing database was specified as “Trove Medium” so now we select “Trove Medium Resize”. This automatically changes the memory allocation from 1 gigabyte to 1.3 gigabytes.

To see this in action, we’ve created this “Configuring & Managing MySQL Instances: Resizing Instances and Volumes” video so you can see for yourself how easy it is to re-size existing MySQL database instances using the Tesora DBaaS platform — database as a service based on OpenStack Trove.

Configuring and Managing MySQL Instances using OpenStack Trove Database as a Service

If you have a database or two, that is one thing, but as an organization if you have a number of databases running, you may have a mandate to make sure they are all created with specific configurations to meet your organizationalstandards. This article will discuss how to use the Tesora Database as a Service Platform, which is based on OpenStack Trove, to set up a configuration group where you have access to all of the parameters of the database, in this case, MySQL running in an OpenStack cloud.

You can pick and choose the property or properties that you want to manage and then can attach this configuration group to database instances. Let’s see how we can do that.

Step 1: To use OpenStack Trove, first you will need to have Guest Images for each datastore. These images are loaded to OpenStack Glance (where virtual machine images are stored) and registered with Trove. Some guest images for development and testing are available for download from OpenStack at http://tarballs.openstack.org/trove/images/ubuntu. If you’re looking for more information, check out this article, Building a database guest image for OpenStack Trove.

Step 2: Next, using the Tesora DBaaS platform dashboard, you log in as the admin user. Start by choosing “Configuration Groups” from the menu and then select “Create Configuration Group”. Next, name the group, for example, “myconfig” and add a description, like “MySQL Configuration Group”. Then, select the datastore type and version.

In this example, we specify that we are creating a MySQL 5.6 configuration group, and the Tesora DBaaS platform automatically provides all the parameters that apply to MySQL databases. Now, to add parameters select this newly created configuration group, and then “Add Parameter”. Use the pulldown to add a parameter like the maximum number of connections (“max_connections”). Go ahead and specify a value of 255. Once we have done that, we can also add many more properties to this configuration group. Once you are done, choose “Apply Changes” and the configuration group is set.

Step 3: Now, go back to the databases that we created by selecting “Instances” and we can apply the configuration group. Use the “Actions” pulldown on one of the database instances and select “Attach Configuration Group”. Select the group that you just created and choose “Attach Configuration”. This adds the configuration group to that database instance. Now, the number of connections that are allowed for this database instance is 255, as we had specified.

That’s it, you’re done. We’ve created this “Configuring & Managing MySQL Instances: Configuration Groups” video demonstration so you can see for yourself how easy it is to set up a configuration group and apply it to MySQL database instances using the Tesora DBaaS platform — database as a service based on OpenStack Trove.

SUSE Targets Simplification with OpenStack Cloud 6 Release

German open source vendor SUSE claims its new OpenStack Cloud 6 is designed to overcome the fear of commitment that is putting IT buyers off engagement with the cloud. SUSE claims its new private cloud offering is a solution to the buying objections that potential customers have outlined.

According to SUSE’s own feedback, many companies want the cloud but think it’s too much hassle to install applications and can’t risk the disruption to their business. A recent study commissioned by SUSE found that more than 90% of large companies say they’ve already got at least one private cloud within their business, can see the advantages and would, in theory, use cloud computing for more business-critical workloads.

Read more at BCN

Linux Usage on Steam Continues to Fall

Despite Valve’s push, less than 1 percent of Steam gamers use Linux or SteamOS.

Valve’s considerable efforts on behalf of Linux-based gaming just aren’t paying off. Valve and its hardware partners released the first Steam machines running the Linux-based SteamOS about four months ago. And there are now more than 1,900 games available for Linux on the Steam store. But Linux usage on Steam just keeps falling. The evidence comes from Valve’s Steam Hardware Survey. It reveals that machines running Linux—including SteamOS—were at 0.91 percent in February 2016, a drop of 0.04 percent from January.

Read more at PCWorld

Linux Kernel 4.5 to Land Next Week as Linus Torvalds Announces the Last RC Build

Linus Torvalds has made his usual announcement for the next Release Candidate (RC) build of the upcoming Linux 4.5 kernel branch, which might just land next week.

Linux kernel 4.5 RC7 (Release Candidate 7) is now available for download to early adopters, especially Linux kernel-based operating system vendors, as well as to those who want to test and report bugs, and according to Mr. Torvalds things have finally calmed down this past week.

Artist Creates Astonishing Ubuntu Wallpapers for Phones and Tablets

artist-creates-ubuntu-wallpapersDeviantart artist Sylvia Ritter has recently started a new project to create wallpapers for Ubuntu phone and tablet devices, inspired by all the Ubuntu Linux releases.

The wallpapers, which we have to admit that are pure masterpieces, are in fact inspired by the codenames of the Ubuntu operating system, most of which are real animals, and made with the powerful and open-source Krita digital painting software.

 

Sonar GNU/Linux OS for People with Impairments Gets Its First Release in 2016

sonar-gnu-linuxThe Sonar GNU/Linux team was proud to announce the release and immediate availability for download of the first release of the open-source operating system in 2016.

We’ve introduced you guys to the Sonar OS back in 2014, but no other news have been published on Softpedia about the accessible GNU/Linux distribution targeted at people with impairments and focused on assistive technology, despite the fact that it received a couple of updates last year.

This Is How Much Hotter The Raspberry Pi 3 Gets Than The Raspberry Pi 2

As part of the numerous Raspberry Pi 3 benchmarks published this weekend, I had an article devoted to how the Raspberry Pi 3 gets rather warm under load. For those interested, here are some follow-up tests showing just how warm the RPi3 gets in comparison to the Raspberry Pi 2. 

The result here is an extension of yesterday’s Raspberry Pi 3 thermal SoC testing with adding the Raspberry Pi 2 results with monitoring its SoC temperature via the Phoronix Test Suite

Read more at Phoronix

Elementary OS: A Distro that Dreams of Disrupting the Linux Desktop

elementaryOS-image-elementaryioPMElementary OS has been making waves for quite some time, and the distro has already created a loyal fan following that’s helping it become a self-sustaining product. I am not an elementary OS user; I am more of an Arch Linux or openSUSE guy, but I do run it in a VM, to keep an eye on what’s going on with this promising distribution.

Elementary OS is trying to disrupt the desktop Linux world in a couple of ways. It’s aim is to create a distribution that approaches the desktop from a design point of view instead of the crude “there-is-a-command-for-everything” approach that’s popular in the Linux world.

So far, the company has been successful in achieving this goal. The latest release of elementary OS, Freya, is one of the most polished and good-looking distributions I’ve seen. One reason behind such this design-centric focus is that the founder of the project comes from a design background.

From Windows to Linux

Daniel Foré, the founder of the project was originally a Windows XP user — like many people. But, he was dissatisfied with it. “I was doing a lot of modifications on Windows XP, doing things like adding shadow to windows and stuff,” said Foré.

He dipped his toes into Linux with Korora Linux when it first came out in 2006, with the XGL live demo. All that shiny Compiz stuff got him excited about Linux. Foré said that initially he didn’t know how to dual boot, so he was using two hard drives and would boot from either of the two drives to go to Linux or Windows. Korora, however, introduced him to the open source development model. “I came to Linux with a potential of what things you can do with it. I started working on icons. I was using Inkscape on Windows so I was already familiar with open source software,” he said.

DanielForeAnd, once he began using Korora, he started doing all his development work on Linux. “I started learning about iconography and then started developing the elementary icon theme.”

Then, he went to Gentoo, and that’s when he got deeper into the open source world. He began uploading his work to DeviantArt and GNOME-Look.org. “I started hacking around a bit with PyGTK on Gentoo, but I didn’t get very far or make anything terribly useful. I wanted to build an updater app for Gentoo!” Foré said.

For the first couple of years, Foré stayed purely on the theming side. Then, he got involved with Gnome Do and Docky, and that’s when he started doing more interaction design. He got exposed to the idea of designing software and not just themes. He began getting interested in finding out what other applications he could apply this new learned skill to.

The Beginning of elementary OS

Foré came across a developer — known by the name ammonkey — who was working on Gloobus preview, which was a Gnome application based on Apple’s Quicklook. ammonkey had maintained a fork of Nautilus to build this quick view function. “We started talking about it. We already have a Nautilus fork, what else can we do to it? And we came out with Nautilus elementary,” said Foré.

The project was mentioned by OMG! Ubuntu, which has a huge following in the Ubuntu world. That coverage gave them some much-needed exposure, and other developers started inquiring about how could they get involved. That’s when the project took off – they made a cool app and then they wanted to make a complete desktop environment that was full of such cool apps. That was the foundation of elementary OS: a clear and very tight focus on user experience, polished and easy-to-use, with fast yet simple applications.

The company could have chosen the path of other desktop environments where users could have used this new desktop environment on any distro of their choice. Instead, they chose to create their own distro.

“The primary motivation was from the user experience point of view. It is a lot easier for someone to download a single file, a complete operating system, instead of downloading different components and then trying to figure out how to build it. Still, today, we have this problem where people want to install Pantheon (the desktop environment of elementary OS) on Ubuntu and they run into all kinds of problems because it’s not configured correctly underneath; they have overlap of settings from Unity, Gnome, or other desktop environments. So, by providing them a full ISO, we can give them the experience that we developed all the way through, instead of having them try to fumble through it and try to make it work,” said Foré.

It’s not just the design principle that sets elementary OS apart from other distributions. Foré believes that what sets them apart are the applications. He said, “If you look at pretty much any other Linux distribution, you are going to get a bundle of popular Linux apps, but these apps are not built by similar teams. They are not using the same toolkit or same design language. So, you are going to get a package that’s not very cohesive. With elementary OS, you get a desktop environment and a suite of applications that were all purpose built to work together. These applications are using the same design language, throughout. When you get used to how one thing works in one app, you won’t have to relearn that when you open another app, because the design language is same. So, it’s a lot easier to jump into the system, get on groove, kind of go on autopilot, and it just works instead of constantly hunting where the functions are.”

Developing for elementary OS

Foré believes that the idea of “Linux” apps will go away, and application developers will target distributions as platforms. Instead of writing applications for Linux, which could run on all distributions — from Arch Linux to Zorin OS — they will write apps for a particular distribution.

Foré thinks this approach gives developers a deeper integration with the operating system. There are a few developers who don’t see much traction in the general Linux world and now they have started to develop their apps exclusively for elementary OS. The developers of Vocal and Birdie are two such examples. This approach makes life easier for the developer, because instead of working with the internals of KDE or Gnome or whatever, plus the operating system, they can target one platform. It helps users, because they know the end-to-end experience they will get is the experience that the app developer had in mind. And elementary OS is not the only one doing this. Canonical is also doing something similar — albeit with a totally different approach — with its Snappy apps.

There is a flip side here; the rest of the Linux world won’t be able to use such apps. At the same time, it may be challenging for the elementary OS team, with their comparatively smaller user-base to get developers of big apps like Gimp, LibreOffice, Chrome, etc. to write apps for elementary OS. So, elementary OS won’t get an “elementary-fied” version of these major apps, and the rest of the Linux world won’t be able to use elementary OS apps. But, given the diversity of Linux – there are hundreds of distributions out there – this is a risk elementary OS can afford. This risk also becomes their unique selling point and sets them apart from the crowd.

Despite this radical approach, the project seems to be doing well. Unlike other distributions that get money through a foundation or commercial vendor, elementary gets financial support from users. They have adopted a “pay-what-you-like’ model where users can pay a desired amount when they download the operating system. It has been working so well that they have two full-time developers and one part-time web developer.

Foré has considered other revenue generation models — something similar to a subscription-based model where there are additional features or exclusive updates for paid users — but has rejected this idea, stating that he would want all features to be available to all users. He is also exploring the possibility of the “pay-what-you-want” model for apps on elementary OS.

I asked about the possibility of generating revenue from hardware — working with select hardware vendors and getting a share from the sales. In that way, elementary OS team could help in designing the hardware itself that gives users an Apple-like experience — all the way from the hardware to software. Foré said that they have been talking to some vendors, but admitted that hardware is a really tough business. “Apple benefits from the economy of scale. They can maintain a thick margin on hardware. I have spoken to different hardware vendors including System76, and the margin on hardware is really thin so there is no possibility of generating revenue from hardware. However, there is a lot of interest from users who want to get hardware with elementary OS pre-installed on it. ”

Getting their own dedicated hardware would also allow elementary OS to bake in features that they can’t offer on “install it yourself” hardware. Foré said they are trying to find a good hardware partner or develop a hardware certification program so when you buy elementary OS hardware, you know everything will work out of the box, with additional features.

Conclusion

I see a new face, a new phase, of Linux in elementary OS. They are executing some radical ideas that may not sit very well with the Linux world, but we have reached a standstill in desktop Linux. We need someone to shake things up; we need someone to disrupt it. The approach may work, or it may not, but it’s something that desktop Linux needs. Ubuntu is trying it, Steam OS is trying it, and now elementary OS is joining the race. As long as it runs the Linux kernel, and it’s open source, I am all for it!

Wayland Will Not Be the Default of Fedora 24

While many developers worked very hard in trying to make GNOME 3.20 default to using Wayland rather than an X.Org Server for Fedora 24, this isn’t going to happen.

The Fedora Workstation Working Group has decided that Wayland simply isn’t ready yet to replace an X.Org/X11 Server by default, although much progress was made on getting Wayland to feature parity with the X.Org-based stack, they didn’t cross the finish line. Fedora defaulting to Wayland will now be deferred to Fedora 25 later in the year. 

Read more at Phoronix