4 simple steps to cloud adoption

It has become vitally important for organizations to be cloud players. They must be innovative with their IT transformation approaches in building flexible and agile business systems such as Customer Resource Management (CRM) systems, storage systems, complex process automation and for leveraging social media and mobile technologies.
The post 4 simple steps to cloud adoption appeared first on Thoughts On Cloud.
Quelle: Thoughts on Cloud

Using an Ansible Job Template in a CloudForms Service Bundle

This is part 5, the last post of our series on Ansible Tower Integration in Red Hat CloudForms.
As you saw from previous articles, Job Templates can be launched from CloudForms via Ansible Tower to run playbooks on targeted hosts. In particular we have looked at launching them from a button on a VM and from the CloudForms Service Catalog. In this last article, we examine how to expose Job Templates as Service Items to utilize them as part of a Service Bundle.
In this example, we reuse our ‘Deploy PostgreSQL’ Job Template to automate the installation and configuration of a PostgreSQL database on a newly provisioned VM. Our service bundle will deploy a new RHEL7 instance on Amazon EC2 and launch our Ansible Job Template to configure the database on this host.
 
The Ansible Job Template can only run once the AWS instance is created. To ensure the ordering, we add an initial ‘pre0’ state with a value of /Service/Provisioning/StateMachines/Methods/GroupSequenceCheck to the state machine schema used to launch our Ansible Type service item /ManageIQ/ConfigurationManagement/AnsibleTower/Service/Provisioning/StateMachines/Provision.
 

 
Now we create a simple provisioning service item called ‘Deploy RHEL7 instance’ based on an Amazon RHEL7 AMI. The ‘Provisioning Entry Point State Machine’ for this Service Item is set to ‘/Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization’ as we will use it in our Service Bundle.
 

 
Similarly, we create a Service Item of type ‘Ansible Type’ for the launch of our Job Template. ‘Provisioning Entry Point State Machine’ for this Service Item is set to ‘/ConfigurationManagement/AnsibleTower/Service/Provisioning/StateMachines/Provision/provision_from_bundle’.
 

 
Note that none of these Service Items have a Dialog set or are displayed in a catalog. We will simply use them as part of our Service Bundle.
Next, we create a Service Dialog which will prompt the user for some details. We create a new dialog from ‘Automate > Customization > Service Dialogs’. As you can see, our ‘RHEL7 with PostgreSQL’ dialog contains two tabs and elements specifying the instance name and the database details.
 

 
Here is a summary of each elements as configured in our example:
 

( function() {
var func = function() {
var iframe_form = document.getElementById(‘wpcom-iframe-form-83dbadf1accad8d5bceaf156135c7368-57b48b476c6f6′);
var iframe = document.getElementById(‘wpcom-iframe-83dbadf1accad8d5bceaf156135c7368-57b48b476c6f6′);
if ( iframe_form && iframe ) {
iframe_form.submit();
iframe.onload = function() {
iframe.contentWindow.postMessage( {
‘msg_type': ‘poll_size’,
‘frame_id': ‘wpcom-iframe-83dbadf1accad8d5bceaf156135c7368-57b48b476c6f6′
}, window.location.protocol + ‘//wpcomwidgets.com’ );
}
}

// Autosize iframe
var funcSizeResponse = function( e ) {
var origin = document.createElement( ‘a’ );
origin.href = e.origin;

// Verify message origin
if ( ‘wpcomwidgets.com’ !== origin.host )
return;

// Verify message is in a format we expect
if ( ‘object’ !== typeof e.data || undefined === e.data.msg_type )
return;

switch ( e.data.msg_type ) {
case ‘poll_size:response':
var iframe = document.getElementById( e.data._request.frame_id );

if ( iframe && ” === iframe.width )
iframe.width = ‘100%';
if ( iframe && ” === iframe.height )
iframe.height = parseInt( e.data.height );

return;
default:
return;
}
}

if ( ‘function’ === typeof window.addEventListener ) {
window.addEventListener( ‘message’, funcSizeResponse, false );
} else if ( ‘function’ === typeof window.attachEvent ) {
window.attachEvent( ‘onmessage’, funcSizeResponse );
}
}
if (document.readyState === ‘complete’) { func.apply(); /* compat for infinite scroll */ }
else if ( document.addEventListener ) { document.addEventListener( ‘DOMContentLoaded’, func, false ); }
else if ( document.attachEvent ) { document.attachEvent( ‘onreadystatechange’, func ); }
} )();

 
By now, you should recognize most of these fields:

‘vm_name’ is used to specify the name of the newly provisioned instance. It is automatically handled by CatalogItemInitialization to propagate the specified name as part of the provisioning process. We set the ‘Auto Refresh other fields when modified’ option to trigger the population of the ‘limit’ element.
‘limit’ is used by Ansible Tower to filter on which host the Job Template must run. In our example, we set the ‘auto-refresh’ option and specify ‘Get_VM_Name’ instance as ‘Entry Point’. The associate ‘get_vm_name’ simply replicates the value from ‘vm_name’ element.

 

 

‘param_postgresql_databases’ and ‘param_postgresql_users’ elements allow the user to override the default extra variables set on the Ansible Job Template.

Now that the Service Dialog is defined we can create a new Service Bundle. We specify the ‘RHEL7 with PostgreSQL’ dialog and the ‘CatalogBundleInitialization’ Provisioning Entry Point State Machine.
 

 
In the ‘Resources’ section, we add our two Service Items and specify their order of provisioning.
 

 
That’s it. Our new service is now available as part of our service catalog. We can go ahead and order it to provision a new instance on Amazon and run an Ansible playbook on it. If configured properly, a fully configured PostgreSQL database is deployed and configured on a new Amazon instance.
The code base for this example can be found on GitHub.
 
This concludes this series of articles on Ansible Tower integration introduced in Red Hat CloudForms 4.1. We have seen how the two management tools integrate and we explored examples on how to leverage Ansible automation within CloudForms. Additional documentation on Red Hat CloudForms and Red Hat Ansible Tower can be found on the Red Hat Customer Portal.
Quelle: CloudForms

Workday taps IBM SoftLayer for development and testing

Workday, which specializes in human resources and finance software, announced this week that it has signed a 7-year agreement with IBM to use the SoftLayer cloud platform for developing and testing new products. Workday CEO Aneel Bhusri said the platform will enable his company to scale development and testing faster. Previously, the firm used its [&;]
The post Workday taps IBM SoftLayer for development and testing appeared first on Thoughts On Cloud.
Quelle: Thoughts on Cloud

4 key design considerations for a multi-tenant cloud

Cloud uses multi-tenancy to share IT resources, software and services in a cost efficient and secure way. Ever wondered what it takes to achieve multi-tenancy in a hybrid cloud? This intrigued me until I was involved in designing multi-tenant cloud solutions. Multi-tenancy is not new. We have been using it in various forms, one common [&;]
The post 4 key design considerations for a multi-tenant cloud appeared first on Thoughts On Cloud.
Quelle: Thoughts on Cloud

HPE loses Bill Hilf, gains SGI, among buyout rumors

The post HPE loses Bill Hilf, gains SGI, among buyout rumors appeared first on Mirantis | The Pure Play OpenStack Company.
Yes, you read that right, HPE is also the subject of rumors of a private equity buyout.  In this case, Reuters reports that several firms, including Apollo Global Management, which is also said to be looking at Rackspace, are looking at buying either all of HPE, or just its software businesses such as Autonomy.   
The company announced August 1 that it will be reorganizing (again), this time moving the HP Helion OpenStack product under the Enterprise Group, as part of the Software-Defined & Cloud Group (SDCG), led by Ric Lewis.  As part of this restructuring, senior vice president and general manager of HP Cloud Bill Hilf will be leaving the company &;to pursue other opportunities&;.  
According to a classy farewell email reprinted in GeekWire, Hilf said &8220;“Like many other companies, there comes a time where you naturally mainstream specific technologies into the broader product strategies, and now is the right time to integrate our Helion software assets more deeply into HPE SW and EG.  In 2016, Cloud is now part of every product strategy at HPE, so this makes good sense to integrate, versus maintain a stand-alone division.
“For me personally, when I joined, I made a commitment to build the cloud business here at HP for three years, and I’m now 3 years and one month in, and we have had very strong growth – just this past June HPE Helion was recognized as a leader in the private cloud market for the third year in a row.  So this is the right time for me to help move the technologies and teams more deeply into the company, and to pursue new opportunities.”
Meanwhile, in other news, HP has bought big data analytics firm SGI for $275 million to shore up its position in high performance computing (HPC) and data analytics. According to SDN Central, &8220;HPE says the SGI acquisition helps it expand its presence in key verticals such as government, research, and life sciences.&8221;
Resources

HPE cloud boss Bill Hilf departs the company
Private equity firms eye HPE’s software business for acquisition
Hewlett Packard Enterprise shakes up its cloud business, cloud leader Bill Hilf leaving company
HPE loses its cloud and storage heads: No Goel, Vrij packs up, Fink runs
Silicon Graphics (SGI) Stock Up After-Hours on HP Enterprise Deal
HPE Buys Big Data Analytics Company SGI for $275M

The post HPE loses Bill Hilf, gains SGI, among buyout rumors appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

Mirantis supports SUSE with Mirantis OpenStack, SUSE supports Mirantis OpenStack with RHEL

The post Mirantis supports SUSE with Mirantis OpenStack, SUSE supports Mirantis OpenStack with RHEL appeared first on Mirantis | The Pure Play OpenStack Company.
Events often include product or company announcements, and OpenStack Days Silicon Valley was no exception, with Mirantis following up its recent announcement that it would work with Intel and Google to rearchitect OpenStack for containers and continuous delivery with the news that it would partner with SUSE to ensure that Mirantis OpenStack can run on that distribution — and a couple of other important ones.
Mirantis CMO and Co-Founder Boris Renski joked that as MOS has always supported Ubuntu and had agreements for Oracle Linux support, the addition of SUSE meant that there was just one major Linux distribution missing, but one that was about to be resolved.
SUSE, you see, in addition to providing SUSE Linux Enterprise Server (SLES), provides support for customers running Red Hat Enterprise Linux (RHEL) — and now they would do the same for Mirantis customers.
As you might imagine, Red Hat, which used to be an investor in Mirantis but had a falling out in recent years, was none-too-thrilled with the announcement.  &;We aren&;t clear what kind of support Mirantis and SUSE can claim to provide for another company&8217;s offerings,&; Margaret Dawson, senior director of product marketing at Red Hat told CRN. &8220;but this makes no sense to us, and it would certainly be confusing and potentially dangerous for customers.&8221;
Red Hat has always maintained that the best way to create a solution such as OpenStack is through &8220;co-engineering&8221;, in which the operating system and OpenStack distribution are provided by the same vendor and that it&8217;s &8220;unheard of&8221; for one vendor to support another vendor&8217;s product.
&8220;Enterprise support agreements have often seen vendors willing to take on the support of other vendors’ products,&8221; wrote Ian Murphy in EnterpriseTimes. &8220;This is nothing new, and in many cases, those agreements are not subject to any agreement between vendors. In the Open Source market where access to the source code is part of the deal, companies are often willing to do whatever it takes to ensure software runs smoothly.&8221;
The issue here, of course, is that some companies take exception to the notion of being locked into a single vendor&8217;s products and want flexibility.  That is, in fact, how SUSE wound up supporting RHEL in the first place — it&8217;s a part of their offer for customers who are ready to move off RHEL onto SUSE but need support during the transition.
Mark Smith, a Global Products and Solutions Manager from SUSE, was quick to point out that the announcement in no way signals a pullback from OpenStack for the company. &8220;There is no change in our commitment to OpenStack. This is just about allowing customers to choose which OpenStack they want to run on SUSE Enterprise Linux.”
According to the arrangement, Mirantis will offer Level 1 and Level 2 support for any RHEL-related issues and will call on SUSE for any Level 3 issues that arise with customers.  Mirantis offers packages that include 1-year and 3-year subscriptions, with up to 24x7x365 email and phone support, with a one-hour guaranteed response time.
Resources

Mirantis and SUSE: Creating a One-Stop Shop for OpenStack Support on Major Linux Distros
Mirantis Partners with SUSE to Deliver Complete Enterprise Linux Support
Mirantis Sidesteps Red Hat Resistance To Rival OpenStack Software Running On Its Dominant Linux, Red Hat Calls Foul
SUSE and Mirantis to collaborate on OpenStack
Remember that RHEL/Mirantis storm? SUSE helps to sidestep the issue
Mirantis and SUSE support multiple Linux OpenStack clouds

The post Mirantis supports SUSE with Mirantis OpenStack, SUSE supports Mirantis OpenStack with RHEL appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

Rackspace said to be close to private equity buyout

The post Rackspace said to be close to private equity buyout appeared first on Mirantis | The Pure Play OpenStack Company.
Rackspace, one of the founding companies behind OpenStack, is said to be close to a deal with Apollo Global Management to bring the company private at a value of between $3.4 billion and $4 billion. Rumors swirled around the company in 2014, but the company reportedly couldn&;t get the price it was looking for, said to be in the neighborhood of $6 billion.
Since then, Rackspace has changed its market strategy, exiting the commodity cloud business and focusing on &;managed services&;, in which customers pay for resources and for the &8220;fanatical support&8221; the company is known for. That &8220;fanatical support&8221; is now also offered for AWS and Azure. This week Rackspace also sold its Cloud Sites premium hosting business, which is separate from its cloud services and involves sites that start at $150/month, to Liquid Web for an undisclosed sum.
Resources

Is Cloud Provider Rackspace Going Private?
Is the Sale of Rackspace a Done Deal?
Rackspace Nears a Private Equity Buyout, Report says
Rackspace nears buyout; Going private could boost cloud managed services effort
Rackspace on the verge of private equity buyout | SiliconANGLE
Apollo Is Negotiating a Deal to Buy Cloud Company Rackspace
Rackspace warns of hit to UK business in H2 | TechMarketView
Rackspace Q2 report; Cloud Sites business sold to Liquid Web, no other strategic news
Rackspace sells Cloud Sites business to Liquid Web
Rackspace expands its managed security services to Microsoft’s Azure cloud
Rackspace manages security across clouds
Come Hear What We&8217;ve Learned at OpenStack Days: Silicon Valley
4 Winners and 3 Losers in Gartner’s Magic Quadrant for IaaS
Rackspace Reaches OpenStack Leadership Milestone, Six Years and One Billion Server Hours
Why OpenStack is Best as a Service

The post Rackspace said to be close to private equity buyout appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis