Fuel plugins: Getting Started with Tesora DBaaS Enterprise Edition and Mirantis OpenStack

The post Fuel plugins: Getting Started with Tesora DBaaS Enterprise Edition and Mirantis OpenStack appeared first on Mirantis | The Pure Play OpenStack Company.
The Tesora Database as a Service platform is an enterprise-hardened version of Openstack Trove, offering secure private cloud access to the most popular open source and commercial databases through a single consistent interface.
In this guide we will show you how to install Tesora in a Mirantis Openstack environment.
Prerequisites
In order to deploy Tesora DBaaS, you will need a fuel with the Tesora plugin installed.  Start by making sure you have:

A Fuel server up and running. (See the Quick Start for instructions if necessary.)
Discovered nodes for controllers, compute and storage
A discovered node for the dedicated node for the Tesora controller.

Now let’s go ahead and add the plugin to Fuel.
Step 1 Adding the Tesora Plugin to Fuel
To add the Tesora plugin to Fuel, follow these steps:

Download the tesora plugin from the Mirantis Plugin page, located at:

https://www.mirantis.com/validated-solution-integrations/fuel-plugins/

Once you have downloaded the plugin, copy the plugin file to your Fuel Server using the scp command, as in:
$scp tesora-dbaas-1.7-1.7.7-1.noarch.rpm root@[fuel s:/tmp

After copying the Fuel Plugin to the fuel server, add it to the fuel plugin list. First ssh to the Fuel server:
$ssh root@[fuel server ipi]

Next, add the plugin to Fuel:
[root@fuel ~]# fuel plugins –install tesora-dbaas-1.7-1.7.7-1.noarch.rpm

Finally, verify that the plugin has been added to Fuel:
[root@fuel ~]# fuel plugins
id | name                     | version | package_version
—|————————–|———|—————-
1  | fuel-plugin-tesora-dbaas | 1.7.7   | 4.0.0

If the plugin was successfully added, you should see it listed in the output.
Step 2 Add Tesora DBaaS to an Openstack Environment
From here, it&8217;s a matter of creating an OpenStack cluster that uses the new plugin.  You can do that by following these steps:

Connect to the Fuel UI and log in with the admin credentials using your browser.
Create a new Openstack environment. Follow the prompts and either leave the defaults or alter them to suit your environment.
Before adding new nodes, enter the environment and select the settings tab and then other on the left hand side of the window.
Select Tesora DBaaS Platform and enter the username and password supplied to you by Tesora.  The username and password will be used to download the Database images provided by Tesora to the Tesora DBaaS controller.  Finish by typing “I Agree” to show that you agree to the Terms of Use and click Save Settings.
Now create your Environment by assign nodes to the roles for

Compute
Storage
Controller
Tesora DBaaS Controller

As shown in the image below:

After you have finished adding the roles go ahead and deploy the environment.

Step 3 Importing the Database image files to the Tesora DBaaS Controller
Once the environment is built, it&8217;s time to import the database images.  

From the Fuel Server, SSH to the Tesora DBaaS controller server.  You can find the IP address of the Tesora DBaaS controller by entering the following command:
[root@fuel ~]# sudo fuel node list | grep tesora
9  | ready  | Untitled (61:ef) | 4       | 10.20.0.6 | 08:00:27:a3:61:ef | tesora-dbaas    |               | True   | 4

After identifying the IP address you will need to ssh to the fuel server:
[root@fuel ~]# sudo ssh root@10.20.0.6
Warning: Permanently added ‘10.20.0.6’ (ECDSA) to the list of known hosts.
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-93-generic x86_64)
* Documentation:  https://help.ubuntu.com/
Last login: Wed Aug 10 23:51:29 2016 from 10.20.0.2

Next load the the pre-built Database images.  After logging into the DBaaS Controller, change your working directory to /opt/tesora/dbaas/bin:
root@node-9:~# cd /opt/tesora/dbaas/bin

Now export your tesora variables:
root@node-9:/opt/tesora/dbaas/bin# source openrc.sh

After setting your variables, you can now import your database images with the following command:
root@node-9:/opt/tesora/dbaas/bin# ./add-datastore.sh mysql 5.6
Installing guest ‘tesora-ubuntu-trusty-mysql-5.6-EE-1.7′

Above is an  example of loading mysql version 5.6.  The format of the command is:
add-datastore.sh DBtype version

To get a list of Database that are available and version please see the link below:

https://tesoradocs.atlassian.net/wiki/display/EE17CE16/Import+Datastore

Once you have imported your Database images, it&8217;s time to go to Horizon.
Step 4 Create and Access a Database Instance
Now you can go ahead and create the actual database. Log into your Horizon dashboard from within Fuel. On the lefthand side, click Tesora Databases.  

From here, you have the following options:

Instances: This option enables you to create, delete and display any database instances that are current running.
Clusters: This option enables you to create and manage a cluster Database environment.
Backups: Create or view backups of any current running Database Images.
Datastores: List all Databases that have been imported
Configuration Groups: This option enables you to manage database configuration tasks by using configuration groups, which make it possible to set configuration parameters, in bulk, on one or more databases.

At this point Tesora DBaaS should be up and running, enabling you to deploy, configure and manage databases in your environment.
The post Fuel plugins: Getting Started with Tesora DBaaS Enterprise Edition and Mirantis OpenStack appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

3 challenges businesses must overcome to reap the benefits of a hybrid cloud environment

The question “Why should businesses migrate to the cloud?” has long been answered. The tangible benefits are well documented.
Organizations are now forced to assess what type of cloud deployment best suits their needs. Be it the agility and affordability of a public cloud or the control and security of a private environment, there’s no one-size-fits-all answer, which is why it’s no surprise that 80 percent of enterprises are expected to commit to hybrid cloud architectures by 2017. But the route to hybrid cloud environment success is not without challenges. There are three steps to getting it right:
1. Select the right provider
The demand for flexibility, scalability and security hasn’t gone unheeded by hybrid cloud providers. A host of companies offer hosted and on-premises environments that enable businesses to leverage all the benefits of a public cloud service in a hosted or on-premises private cloud environment. But selecting the right provider is just one of the challenges that organizations need to overcome. Whether your business is looking to add cloud capability to its existing virtualized IT environment or its looking to bring private cloud elements to its existing public cloud set-up, compatibility with existing software and services is key. IBM Blue Box runs on the open-source cloud software platform OpenStack, which means that organizations can integrate Blue Box with their existing infrastructure without the need for translation and with no downtime.
2. Clearly identify your needs
The key to successfully deploying a hybrid cloud environment is aligning the cloud strategy with the desired business outcomes. Security remains a core consideration. If an organization’s data is subject to compliance regulations, it faces heavy fines if it fails to meet them. IBM Blue Box offers robust security features including authentication and identity management. Blue Box can integrate with existing, third-party customer IdP systems to ensure control of users and two-factor authentication. That means businesses can operate safe in the knowledge that their data is safe and complies with industry regulations and data sovereignty. Data can reside in-country, or wherever you need it; Blue Box has data centers throughout the world and can deploy hosted or on-premises solutions, providing a truly hybrid model.
3. Seamlessly manage your hybrid environment
For some businesses, the thought of IT teams having to juggle the management of both a private and public cloud infrastructure is perhaps the most daunting element of adopting a hybrid environment. IBM Blue Box provisions and manages organizations’ private clouds for them, leaving them to focus more on business-critical operations.
The benefits of a hybrid cloud environment are manifold: reduced costs, scalability to meet changing business needs, the ability to shift workloads between private and public environments and being able to isolate and protect business-critical data quickly and easily being just four examples. The choice to migrate is simple and with IBM Blue Box, so is navigating the challenges.
To find out more about IBM Blue Box, the OpenStack platform and learn how to ensure your business can reap the benefits of a hybrid cloud, watch our free webinar.
A version of this post originally appeared on LinkedIn.
The post 3 challenges businesses must overcome to reap the benefits of a hybrid cloud environment appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud

Tieto’s path to containerized OpenStack, or How I learned to stop worrying and love containers

The post Tieto’s path to containerized OpenStack, or How I learned to stop worrying and love containers appeared first on Mirantis | The Pure Play OpenStack Company.
Tieto is the #1 cloud service provider in Northern Europe, with over 150 cloud customers in the region and revenues in the neighborhood of €1.5 billion (with a “b”). So when the company decided to take the leap into OpenStack, it was a decision that wasn&8217;t taken lightly — or without very strict requirements.
Now, we&8217;ve been talking a lot about containerized OpenStack here at Mirantis lately, and at the OpenStack Summit in Barcelona, our Director of Product Engineering will get with Tieto&8217;s Cloud Architect  Lukáš Kubín to explain the company&8217;s journey from a traditional architecture to a fully adaptable cloud infrastructure, so we wanted to take a moment and ask the question:
How does a company decide that containerized OpenStack is a good idea?
What Tieto wanted
At its heart, Tieto wanted to deliver a bimodal multicloud solution that would help customers digitize their businesses. In order to do that, it needed an infrastructure in which it could have confidence, and OpenStack was chosen as the platform for cloud native applications delivery.  The company had the following goals:

Remove vendor lock-in
Achieve the elasticity of a seamless on-demand capacity fulfillment
Rely on robust automation and orchestration
Adopt innovative open source solutions
Implement Infrastructure as Code

It was this last item, implementing Infrastructure as Code, that was perhaps the biggest challenge from an OpenStack standpoint.
Where we started
In fact, Tieto had been working with OpenStack since 2013, creating internal projects to evaluate OpenStack Havana and Icehouse using internal software development projects; at that time, the target architecture included Neutron and Open vSwitch. 
By 2015, the company was providing scale-up focused IaaS cloud offerings and unique application-focused PaaS services, but what was lacking was a shared platform with full API controlled infrastructure for horizontally scalable workload.
Finally, this year, the company announced its OpenStack Cloud offering, based on the OpenStack distribution of tcp cloud (now part of Mirantis), and OpenContrail rather than Open vSwitch.
Why OpenContrail? The company cited several reasons:

Licensing: OpenContrail is an open source solution, but commercial support is available from vendors such as Mirantis.
High Availability: OpenContrail includes native HA support.
Cloud gateway routing: North-South traffic must be routed on physical edge routers  instead of software gateways to work with existing solutions
Performance: OpenContrail provides excellent pps, bandwidth, scalability, and so on (up to 9.6 Gbps)
Interconnection between SDN and Fabric: OpenContrail supports the dynamic legacy connections through EVPN or ToR switches
Containers: OpenContrail includes support for containers, making it possible to use one networking framework for multiple environments.

Once completed, the Tieto Proof of Concept cloud included;

OpenContrail 2.21
20 compute nodes
Glance and Cinder running on Ceph
Heat orchestration

Tieto had achieved Infrastructure as Code, in that deployment and operations were controlled through OpenStack Salt formulas. This architecture enabled the company to use DevOps principles, in that they could use declarative configurations that could be stored in a repository and re-used as necessary.
What&8217;s more, the company had an architecture that worked, and that included commercial support for OpenContrail (through Mirantis).
But there was still something missing.
What was missing
With operations support and Infrastructure as Code, Tieto&8217;s OpenStack Cloud was already beyond what many deployments ever achieve, but it still wasn&8217;t as straightforward as the company would have liked.  
As designed, the OpenStack architecture consisted of almost two dozen VMs on at least 3 physical KVM nodes &8212; and that was just the control plane!

As you might imagine, trying to keep all of those VMs up to date through operating system updates and other changes made operations more complex that it needed to be.  Any time an update needed to be applied, it had to be applied to each and every VM. Sure, that process was easier because of the DevOps advantages introduced by the OpenStack-Salt formulas that were already in the repository, but that was still an awful lot of moving parts.
There had to be a better way.
How to meet that challenge
That &8220;better way&8221; involves treating OpenStack as a containerized application in order to take advantage of the efficiencies this architecture enables, including:

Easier operations, because each service no longer has its own VM, with it own operating system to worry about
Better reliability and easier manageability, because containers and docker files can be tested as part of a CI/CD workflow
Easier upgrades, because once OpenStack has been converted to a microservices architecture, it&8217;s much easier to simply replace one service
Better performance and scalability, because the containerized OpenStack services can be orchestrated by a tool such as Kubernetes.

So that&8217;s the &8220;why&8221;.  But what about the &8220;how&8221;?  Well, that&8217;s a tale for another day, but if you&8217;ll be in Barcelona, join us at 12:15pm on Wednesday to get the full story and maybe even see a demo of the new system in action!
The post Tieto&8217;s path to containerized OpenStack, or How I learned to stop worrying and love containers appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis