For this week’s #Docker Online Meetup, Sr. Director, Networking at Docker, Madhu Venugopal, joined us to talk about Docker 1.12 Networking and answer questions.
Starting with Docker 1.12, Docker has added features to the core Docker Engine to make multi-host and multi-container orchestration simple to use and accessible to everyone. Docker 1.12 Networking plays a key role in enabling these orchestration features.
In this online meetup, we learned all the new and exciting networking features introduced in Docker 1.12:

Swarm-mode networking
Routing Mesh
Ingress and Internal Load-Balancing
Service Discovery
Encrypted Network Control-Plane and Data-Plane
Multi-host networking without external KV-Store
MACVLAN Driver

The number of questions Madhu got at the end of the online meetup was amazing and because he did not have time to answer all of them, we’ve added the rest of the Q&A below:
Q: Will you address the DNS configuration in Docker? We have two apps created with docker compose and would like to enable communication and DNS resolution from containers in one of the apps to containers in the other app.
Check out the PTAL external network feature in docker compose in the Docker docs to get started. If that does not satisfy your requirement, please raise an issue in docker/docker.
Q: What mechanism is used to register the different docker instances with each other so that they recognize a shared network between hosts, please?
Docker swarm-mode uses Raft and GRPC to communicate between docker instances. That’s how the nodes in the cluster exchange data and recognize shared network. At the data-plane, overlay driver uses VXLAN tunnels to provide per-network multi-host connectivity and isolation.
Q: Does it work with NSX?
This question is related to network plugins and the community has developed OVS & OVN plugins. We are not sure if NSX integration is feasible through that. Typically vendor plugin are created and maintained by the vendor directly.
Q: Is there a way to see all records registered in Docker internal DNS? Is it exposed via API so it can be queried?
The Internal DNS is not exposed but network inspect and service inspect APIs can be used to gather this information.
Q: Has swarm mode created dependency of docker-engine on iptables?
Docker Engines has been using iptables since 1.0 for the bridge driver. Swarm mode merely makes use of iptables to provide functionality like the routing mesh.
Q: Can I have only 2 nodes in swarm and both are managers and node themselves as well?
Docker recommends an odd number of manager nodes as the Raft consensus requires majority consensus and to take full advantage of the fault tolerance features of swarm mode. Please read through https://docs.docker.com/engine/swarm/raft/ for more information.
Q: Wil making ports into a cluster wide resources limit the number of total services whereas using public VIPs is expandable?
Yes. Docker does not control public VIP so it needs to be managed external to the docker cluster. However, only front-end services require port-publishing & only those services that requires port-publishing will be participating in the Routing Mesh. Back-end services do not reserve cluster-wide ports.
Q: Can I plumb more than one IP per container while only using one network?
At the moment, libnetwork supports one routable IP per endpoint (per network). But users can configure many more link-local ip-addresses to the same endpoint. If you are interested in discussing this capability further, please open an enhancement request in docker/docker.
Q: Can you insert records into DNS to cause static IPs to be used?
Docker doesn’t expose embedded DNS APIs externally. Users can provide external DNS using the –dns option and one can insert custom name-lookup entries in the external DNS server which will be used by the containers.
Q: Can you talk more about automatic key rotation for secure networks? How often does it occur and is the interval configurable? What process(es) are responsible for key rotation? How are the keys circulated throughout the cluster?
Please read the Overlay Security Model on the Docker Docs. Currently this is not configurable, but we are working on the configurability of this and other swarm mode features. Key-rotation is entirely handled by manager node process (swarmkit) and is distributed in the secured grpc channel established between the manager and workers.
Q: Regarding front end ports, is there a limitation on the number of port 80&8217;s you can listen on?
Yes. The best way to mitigate that is to run a global nginx or haproxy or other reverse-proxy service and back the backend services by the host-header.
Have a question that wasn’t answered or a specific requirement? Check out the Docker Forums or open an issue on GitHub.

Watch @MadhuVenugopal to learn about the new networking features introduced in docker 1.12Click To Tweet

Want to learn more about Docker 1.12 and networking? Check out these resources:

Docker 1.12 Networking Model Overview by Docker Captain Ajeet Singh Raina
Docker Docs: Understand Docker container network
Docker 1.12 Release Notes
Docker Blog: Docker 1.12: Now With Built-In Orchestration!
Scale a real microservice with Docker 1.12 Swarm Mode by Docker Captain Alex Ellis
Docker 1.12 orchestration built-in by Docker Captain Gianluca Arbezzano

The post Docker Online Meetup #41: Deep Dive into Docker 1.12 Networking appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

24. August 201624. August 2016

da Agency

How does the world consume private clouds?

The post How does the world consume private clouds? appeared first on Mirantis | The Pure Play OpenStack Company.
In my previous blog, why the world needs private clouds, we looked at ten reasons for considering a private cloud. The next logical question is how a company should go about building a private cloud.
In my view, there are four consumption models for OpenStack. Let’s look at each approach and then compare.

Approach #1: DIY
For the most sophisticated users, where OpenStack is super-strategic to the business, a do-it-yourself approach is appealing. Walmart, PayPal, and so on are examples of this approach.
In this approach, the user has to grab upstream OpenStack bits, package the right projects, fix bugs or add features as needed, then deploy and manage the OpenStack lifecycle. The user also has to “self-support” their internal IT/OPS team.
This approach requires recruiting and retaining a very strong engineering team that is adept at python, OpenStack, and working with the upstream open-source community. Because of this, I don’t think more than a handful companies can or would want to pursue this approach. In fact, we know of several users who started out on this path, but had to switch to a different approach because they lost engineers to other companies. Net-net, the DIY approach is not for the faint of heart.
Approach #2: Distro
For large sophisticated users that plan to customize a cloud for their own use and have the skills to manage it, an OpenStack distribution is an attractive approach.
In this approach, no upstream engineering is required. Instead, the company is responsible for deploying a known good distribution from a vendor and managing its lifecycle.
Even though this is simpler than DIY, very few companies can manage a complex, distributed and fast moving piece of software such as OpenStack — a point made by Boris Renski in his recent blog Infrastructure Software is Dead. Therefore, most customers end up utilizing extensive professional services from the distribution vendor.
Approach #3: Managed Services
For customers who don’t want to deal with the hassle of managing OpenStack, but want control over the hardware and datacenter (on-prem or colo), managed services may be a great option.
In this approach, the user is responsible for the hardware, the datacenter, and tenant management; but OpenStack is fully managed by the vendor. Ultimately this may be the most appealing model for a large set of customers.
Approach #4: Hosted Private Cloud
This approach is a variation of the Managed Services approach. In this option, not only is the cloud managed, it is also hosted by the vendor. In other words, the user does not even have to purchase any hardware or manage the datacenter. In terms of look and feel, this approach is analogous to purchasing a public cloud, but without the “noisy neighbor” problems that sometimes arise.
Which approach is best?
Each approach has its pros and cons, of course. For example, each approach has different requirements in terms of engineering resources:

DIY
Distro
Managed Service
Hosted Private Cloud

Need upstream OpenStack engineering team
Yes
No
No
No

Need OpenStack IT architecture team
Yes
Yes
No
No

Need OpenStack IT/ OPS team
Yes
Yes
No
No

Need hardware & datacenter team
Yes
Yes
Yes
No

Which approach you choose should also depend on factors such as the importance of the initiative, relative cost, and so on, such as:

DIY
Distro
Managed Service
Hosted Private Cloud

How important is the private cloud to the company?
The business depends on private cloud
The cloud is extremely strategic to the business
The cloud is very strategic to the business
The cloud is somewhat strategic to the business

Ability to impact the community
Very direct
Somewhat direct
Indirect
Minimal

Cost (relative)
Depends on skills & scale
Low
Medium
High

Ability to own OpenStack operations
Yes
Yes
Depends if the vendor offers a transfer option
No

So as a user of an OpenStack private cloud you have four ways to consume the software.
The cost and convenience of each approach vary as per this simplified chart and need to be traded-off with respect to your strategy and requirements.
OK, so we know why you need a private cloud, and how you can consume one. But there’s still one burning question: who needs it?
The post How does the world consume private clouds? appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

20. August 201620. August 2016

da Agency

What’s new in Mirantis OpenStack 9.0: Webinar Q&A

The post What’s new in Mirantis OpenStack 9.0: Webinar Q&A appeared first on Mirantis | The Pure Play OpenStack Company.
Theres’s never been a better time to adopt Mirantis OpenStack to build your cloud. The newest release, Mirantis OpenStack 9.0, offers improvements in simplicity, flexibility, and performance that make deployment, operations, and management faster and easier.
If you missed the July 14 webinar highlighting the rich new features in Mirantis OpenStack 9.0, we’ve got you covered. The webinar’s panel included three Mirantis experts: Senior Director of Product Marketing Amar Kapadia, Senior Manager of Technical Marketing Joseph Yep, and Senior Product Manager Durgaprasad (a.k.a. DP) Ayyadevara.
They talked about the ways in which MOS 9.0 improves the “Day 2” experience of operating your cloud once you&8217;ve deployed it, as well as easier deployment of workloads, and especially improvements in the management of features related to NFV, such as SR-IOV, software acceleration DPDK and NUMA/CPU pinning.
Here&8217;s a selection of questions and answers from those who attended.
Q: Can any plugin be added after initial deployment without disruption?
A: Not all plugins. However, the plugin framework has added metadata and developer functionality that allow developers to build and test their plugins so they can be added as “hot-pluggable.” This means this capability is specific to the plugins themselves as well as with the settings, which are dependent on the environment and type of change to determine whether there will be disruption. An example is StackLight’s Toolchain, which is hot-pluggable post-deployment.
Q: As far as upgrading from Mirantis OpenStack 8.0 to 9.0, is there documentation available for that?
A: Documentation is readily available and always improving. Because upgrades are challenging for large distributed infrastructure software, Mirantis continually creates tooling to make the process smoother and more automated. Feedback on the documentation is always welcome.
Q: Does the new release support SDN and Contrail?
A: Yes. Currently, the Control field plugin is available for Liberty-compatible release, and Contrail is the Mitaka-compatible version.
Q: The current base OS is Ubuntu 14.04, but are there any plans to upgrade to 16.04?
A: Yes. Operating systems are regularly validated, so 16 is on the roadmap.
Q: With the new release allowing updates to your previously-deployed OpenStack environment, can we also apply a new plugin with Fuel on a deployed environment?
A: Yes, unless it a previous version. For example, with Fuel 9, you can’t deploy a new plugin push deployment to a MOSS 7 environment without having to upgrade the environment itself. However, Fuel can manage multiple versions of Mirantis OpenStack environments.
Q: What is the status on Ironic and VX LAN?
A: Both are supported in 9.0.
Q: Does Murano support deployment of Kubernetes clusters?
A: Yes, absolutely. We do a lot with Kubernetes work, and there’s a new set of announcements coming soon about the work.
Q: What NFV features make Mirantis’ value-add different from others, and how can enterprises benefit from this feature?
A: Mirantis’ value-add is twofold. First, we support all Intel Enhanced Platform Awareness features. Second, we have provisioned for enabling and configuring these features through Fuel. We also support partners like 6WIND, who have DPDK accelerators, and we have Fuel plugins for that. So, we focus on making it easy to operationalize, and that differentiates us.
Q: How can you differentiate Mirantis from services hosted elsewhere, AWS for example?
A: Fundamentally, this compares two different things, a private cloud to a public cloud environment. You will find similarity at the IaaS layer. However, OpenStack is an open system that allows you to choose the components you want. For example, you can add an SDN like Contrail. Thus, in the PaaS, the two deviate considerably. Amazon is prescriptive, choosing the software available to offer customers. Conversely, OpenStack works with a multitude of partners so customers can tailor solutions that work best for them. If they want, for example, Pivotal Cloud Foundry, they can have it. If they want Kubernetes as a container framework, they can have it. If they want a specific database or NoSQL database, they can use Murano and publish that database.
Q: How many nodes are required to deploy OpenStack in Mirantis OpenStack 9.0?
A: Depending on the function, the lower limit is three. If running it virtualized, you could do it all physically on a single machine, but the nodes specifically will be your field master node if you’re using Fuel (you don’t have to use Fuel), which would then deploy to a single controller and a single compute host. This is one of the most minimal deployments if you’re looking at playing with features and practicing deployment, and it means you could conceivably run it on a laptop, though this isn’t advised for running a production deployment. There are instructions for running it in VirtualBox as well.
This is just a tiny fraction of what we covered, of course. Interested in hearing more? You can view the whole presentation online, or download Mirantis OpenStack 9.0 for yourself.
The post What&8217;s new in Mirantis OpenStack 9.0: Webinar Q&038;A appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

20. August 201620. August 2016

da Agency

Your Docker Agenda for LinuxCon North America

Hey Dockers! We’re excited to be back at #LinuxCon this year in Toronto and hope you are, too! We’ve a got a round-up of many of our awesome #Docker speakers, as well as a booth. Come visit us in between the sessions at booth #41 inside “The Hub”. You may even be able to score yourself some Docker swag.

Monday:
11:45am – Curious about the Cloud Native Computing Foundation, Open Container Initiative, Cloud Foundry Foundation and their role in the cloud ecosystem? Docker’s Stephen Walli joins other panelists to deliver So CFF, CNCF, and OCI Walk into a Room (or ‘Demystifying the Confusion: CFF, CNCF, OCI).
3:00pm &8211; Docker Captain Phil Estes will describe and demonstrate the use of the new schema format’s capabilities for multiple platform-specific image references in his More than x86_64: Docker Images for Multi-Platform session.
4:20 pm &8211; Join Docker’s Mike Coleman for Containers, Physical, and virtual, Oh My! insight on what points businesses need to consider as they decide how and where to run their Docker containers.

Tuesday:
2:00pm &8211; Docker Captain Phil Estes is back with Runc: The Little (Container) Engine that Could where he will 1) give an overview of runc, 2) explain how to take existing Docker Containers and migrate them to runc bundles and 3) demonstrate how modern container isolation features can be exploited via runc container configuration.
2:00pm &8211; Docker’s Amir Chaudhry will explain Unikernels: When you Should and When you Shouldn’t to help you weigh the pros and cons of using unikernels and help you decide when when it may be appropriate to consider a library OS for your next project.

Wednesday:
10:55am &8211; Mike Goelzer and Victor Vieux rom Docker’s Core team will walk the audience through the new orchestration features added to Docker this summer: secure clustering, declarative service specification, load balancing, service discovery and more in their session From 1 to N Docker Hosts: Getting Started with Docker Clustering.
11:55am &8211; Kendrick Coleman, Docker Captain will talk about Highly Available & Distributed Containers. Learn how to deploy stateless and stateful services all completely load balanced in a Docker 1.12 swarm cluster
2:15pm &8211; Docker’s Paul Novarese will dive into User namespace and Seccomp support in Docker Engine, covering new features that respectively allow users to run Containers as without elevated privileges and provide a method of containment for containers.
4:35pm &8211; Docker’s Riyaz Faizullabhoy will deliver When The Going Gets Tough, Get TUF Going!
The Update Framework (TUF) helps developers secure new or existing software update systems. Join Docker’s Riyaz Faizullabhoy’s When The Going Gets Tough, Get TUF Going! to learn the attacks that TUF protects against and how it actually does so in a usable manner.

Thursday:
9:00am &8211; In this all day tutorial, Jerome Petazzoni will teach attendees how to Orchestrate Containers in Production at Scale with Docker Swarm.
In addition to our Docker talks, we have two amazing Docker Toronto meetups lined up just for you. Check them out:
On August 23rd, we’re joining together with Toronto NATS Cloud Native and IoT Group at Lighthouse Labs to feature Diogo Monteiro on “Implementing Microservices with NATS” and our own Riyaz Faizullabhoy on “Docker Security and the Update Framework (TUF)”.
Come August 24th we’ll be at the Mozilla Community Space. Gou Rao, CTO and co-founder of Portworx will be touching on “Radically Simple Storage for Docker”, while Drew Erny from Docker will discuss “High Availability using Docker Swarm”.

Going to linuxcon next week? here is the list of docker sessions we recommend cc…Click To Tweet

The post Your Docker Agenda for LinuxCon North America appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

18. August 201618. August 2016

da Agency

Apply for a Docker Scholarship and learn how to code!

Today, Docker is proud to announce the launch of the Docker Scholarship Program in partnership with Reactor Core to improve opportunities for underrepresented groups in the tech industry! With the help of the community, we surpassed our goal for the DockerCon 2016 Bump Up Challenge unlocking $50,000 to fund three full tuition scholarships.

The Docker Scholarship Program is part of our continued work to improve opportunities for women and underrepresented groups throughout the global Docker ecosystem and encourage inclusivity in the larger tech community.
Docker’s Goal
The goal of the Docker scholarship program is to strengthen the broader tech community by making it more diverse and inclusive to traditionally underrepresented groups. We aim to achieve that goal by providing financial support and mentorship to three students at Reactor Core’s partner schools, Hack Reactor and Telegraph Academy.
Our Partnership with Hack Reactor and Telegraph Academy
Docker believes in the power of innovation and pushing our current technological boundaries. As a driver of innovation, we embrace our role in advancing opportunities for underrepresented groups in the tech industry. Hack Reactor and Telegraph Academy share in our vision of empowering people and creating more opportunities for every member of our community. We are inspired by their commitment to improving the status quo for underrepresented groups in the tech industry.
Available Scholarships:
2016 Scholarships:
Telegraph Academy November Cohort
Complete the Docker Scholarship application and apply to Telegraph Academy’s bootcamp. Applications will be reviewed and applicants who are accepted into the Telegraph Academy program and meet Docker’s criteria will be invited to Docker HQ for a panel interview with Docker team members. Scholarships will be awarded based on acceptance to Telegraph Academy program, demonstration of personal financial need and quality of the responses to the Docker Scholarship application.
Apply here
Hack Reactor October Cohort
Complete the Docker Scholarship application and apply to Hack Reactor’s bootcamp. Applications will be reviewed and applicants who are accepted into the Hack Reactor program and meet Docker’s criteria will be invited to Docker HQ for a panel interview with Docker team members. Scholarships will be awarded based on acceptance to Hack Reactor program, demonstration of personal financial need and quality of the responses to the Docker Scholarship application.
As women in the tech industry are traditionally underrepresented, we have a strong preference to award this scholarship to a self identified woman. However, we encourage all to apply as there may be additional opportunities available.
Apply here

2017 Scholarships:
Telegraph Academy February Cohort
Stay tuned for Telegraph’s February 2017 cohort application.
Visit the Docker Scholarship page to learn more about each scholarship and the partner programs.

Want to help Docker with these initiatives?
We’re always happy to connect with other folks or companies who want to improve opportunities for women and underrepresented groups throughout the global Docker ecosystem and promote diversity in the larger tech community.
If you or your organization are interested in getting more involved, please contact us at events@docker.com. With your help, we are excited to take these initiatives to the next level!
The post Apply for a Docker Scholarship and learn how to code! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

17. August 201617. August 2016

da Agency

I Dropped Samsung's New Phone In A Lake And It's Totally Fine

A review of the Galaxy Note 7, the ultimate phone for anyone who’s still obsessed with their stylus.

Ellie Sunakawa / BuzzFeed

There’s a big new Android phone on campus: Samsung’s Galaxy Note 7.

This month, Samsung will unveil the sixth iteration of its Note series but is calling it, confusingly, the Galaxy Note 7 (because its current flagship phone is the Galaxy S7, but whatever).

The new 5.7-inch Note is one of the best Android phablets you can buy right now – and, if you don't mind Samsung&039;s continually-improving-but-still-annoying TouchWiz interface, it is the best. I know, because Samsung lent me a Note 7 review unit ahead of its August 19 release date and I&039;ve been fumbling with its tiny little stylus ever since. And yes, phablet is the second worst name for a tech thing (next to ~dongle~).

I have always preferred “pure” Android devices like the Nexus 6P. In other words, phones developed in partnership with Google that run the latest version of the Android operating system. These phones, which you buy directly from Google&039;s online store, typically get the latest and greatest software updates first.

Galaxy phones are anything BUT “pure” Android devices (Samsung usually pre-loads a bunch of their own extra, Samsung-y stuff on them). And yet, it was impossible to deny just how good the Note is. The phone has a gorgeous new display with curved edges and is jam-packed with new features. Most of all, the Note 7 exceeds expectations where it matters most – battery life, speed, photo quality, and general lifeproof-ness.

Intrigued? More words ahead.

Nicole Nguyen / BuzzFeed

We’ll start with my favorite part: the unboxing.

The Note 7 comes with a pair of earbuds and a charging plug, per usual. There&039;s a schmancy new quick-charging USB C cable and a USB C-to-micro USB adapter, which can be used to connect your phone to pre-existing accessories.

Nicole Nguyen / BuzzFeed

Now with me, slowly: yessssssssssssss.

#1 job perk = peeling off new screen protectors.

Nicole Nguyen / BuzzFeed

View Entire List ›

Quelle: <a href="I Dropped Samsung&039;s New Phone In A Lake And It&039;s Totally Fine“>BuzzFeed

16. August 201616. August 2016

da Agency

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

16. August 201616. August 2016

da Agency

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