Monat: September 2019

Mirantis to Democratize Connectivity with Magma, a Converged Access Gateway Developed by Facebook

The post Mirantis to Democratize Connectivity with Magma, a Converged Access Gateway Developed by Facebook appeared first on Mirantis | Pure Play Open Cloud.
Open-source Magma is integrated with Mirantis Cloud Platform to give network operators an open, cost effective foundation for next generation mobile networks 
Magma Developer Conference, Menlo Park, CA, September 9, 2019 — Today, Mirantis announced that it is helping to bring the open-source converged access gateway software platform Magma, developed by Facebook, to mobile operators around the world. Mirantis has worked over the last six months to integrate, test and certify Magma with Mirantis’ Kubernetes-based infrastructure edge offering, called MCP Edge.

Unlike the core infrastructure that is generally uniform and centralized, edge infrastructure consists of many points of presence with architecture varying as a function of proximity to the end user and the type of application. MCP Edge integrates OpenStack, Kubernetes and Mirantis’ flexible infrastructure manager, DriveTrain, empowering operators to deploy a combination of container, VM and bare metal points of presence (POPs) connected by a unified management plane.

Magma is an open-source software platform designed to seamlessly integrate with the existing evolved packet core back end of a mobile network operator and extend it with new capabilities at the network edge, such as carrier Wi-Fi or EPC as-a-service. Run Magma’s centralized cloud-based controller on a public or private cloud environment, and start with just a single site.

“New entrants into the mobile operator space like Reliance Jio have been able to quickly capture huge market share by building networks at 20% the cost of traditional players and then passing these savings to the consumers,” said Boris Renski, co-founder and CMO, Mirantis. “Network virtualization and open source building blocks are key to achieving these savings. Mirantis already helped some of the biggest operators virtualize their network infrastructure using open standards. Offering services and support for Magma will help us take this further and help mobile operators launch new edge and 5G services cost effectively.”  

The certified combination of MCP Edge and Magma converged access gateway will:

    Enable operators to manage their networks more efficiently with more automation, less downtime, better predictability, and more agility to add new services and applications
    Enable federation between existing mobile network operators and new infrastructure providers for expanding rural infrastructure
    Allow operators who are constrained with licensed spectrum to add capacity and reach by using Wi-Fi and CBRS

“In order to bring affordable internet access to underserved areas of the world, we work to empower telecom companies and vendors with carrier grade, open source software for building next generation mobile networks,” said Amar Padmanabhan, Magma team lead at Facebook. “Mirantis’ experience and capabilities in building open source-based carrier networks make them an excellent partner to collaborate with on this journey.”

This news comes on the heels of Mirantis’ recent collaboration with core contributors of the Airship community by integrating much of the code into Mirantis Cloud Platform (MCP). Airship takes advantage of Kubernetes to define a unified, declarative and cloud-native way for operators to manage containerized software delivery of cloud infrastructure services.

If you are interested in learning more about Mirantis’ involvement in the Magma project, Mirantis will be hosting a webinar on September 24th at 10am. You can register here.
About Mirantis
Mirantis helps enterprises and telcos address key challenges with running Kubernetes on-premises with pure open source software. The company employs a unique build-operate-transfer delivery model to bring its flagship product, Mirantis Cloud Platform (MCP), to customers. MCP features full-stack enterprise support for Kubernetes and OpenStack and helps companies run optimized hybrid environments supporting traditional and distributed microservices-based applications in production at scale.

To date, Mirantis has helped more than 200 enterprises and service providers build and operate some of the largest open clouds in the world. Its customers include iconic brands such as Adobe, Comcast, Reliance Jio, State Farm, STC, Vodafone, Volkswagen, and Wells Fargo. Learn more at www.mirantis.com.
Contact information:
Joseph Eckert for Mirantis

jeckertflak@gmail.comThe post Mirantis to Democratize Connectivity with Magma, a Converged Access Gateway Developed by Facebook appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

OpenStack vs AWS Total Cost of Ownership: Assumptions behind the TCO Calculator

The post OpenStack vs AWS Total Cost of Ownership: Assumptions behind the TCO Calculator appeared first on Mirantis | Pure Play Open Cloud.
It’s easy to think that the least expensive way to spin up cloud servers is to use a service such as Amazon Web Services. After all, you don’t need to buy hardware or electricity, or even hire people to manage it, right?  Well … not so fast. It’s not as simple as that. While there are lots of situations in which AWS is the least expensive, there are times when it’s less costly to bring your workloads on-prem with an OpenStack deployment.
Here at Mirantis, we’ve created a Total Cost of Ownership calculator that compares the two.  For example, if you have 300 virtual machines, AWS can be more cost-effective, but once you get to 400, OpenStack is the way to go.  But before relying on any TCO calculator, it’s important to know the assumptions behind it so that you can understand how those determinations are made.
In this article, we’ll explain how the TCO calculator comes to its conclusions, and you can feel free to download the full spreadsheet yourself to take a look at how it all fits together.
Common assumptions
Whether you’re using AWS or OpenStack, there are certain things you need to take into consideration.  For example, just because you’re using a cloud doesn’t mean that you don’t need staff, and it doesn’t mean that VMs will always be 100% occupied — and all of that will impact your costs. 
In our case, we’re making the following general assumptions:

Average data-out from the cloud per VM is 1 TB/month, or 385,802 bytes/sec
Each compute node hosts an average of 28 VMs
Each VM needs an average of 20 GB of block storage (or 560 GB per server)
Storage is provided with a ratio of raw:usable space of 3.3, allowing for redundancy, and so on

Efficiencies
It’s important to understand that whether you run in the private cloud/on-prem or in the public cloud, there is going to be some level of inefficiency.  For example, we’re assuming that at any given time, only 60% of your OpenStack cloud hardware is in use, but because it’s private cloud/on-premise, you’re still paying for it.  
You don’t have this problem with AWS, because you can always just stop instances you’re not using, but that doesn’t mean you will always run at 100% efficiency. The TCO calculator assumes 80% efficiency for AWS instances, taking into account that there will be times instances are simply too big for the workloads running on them (but you still pay full price for the VM).
Personnel
Staffing may not seem like an issue common to both on- and off-prem clouds, but it is.
For OpenStack clouds, we’re assuming that you will need an OpenStack admin team with a minimum of two persons, because your cloud has to be up 24/7.  We’re also assuming that one admin can handle up to 50 individual servers. Once you get over 200 servers, we’re assuming that allowing for “fractional” staff is acceptable.
For AWS, you’ll still need at least one AWS internal administrator to support users who are in the cloud.
We’re assuming a full-time admin costs $140,000/year. Now let’s look at some assumptions that are specific to each platform.  
OpenStack-specific assumptions
Let’s start with OpenStack.  If you’re running an on-prem OpenStack cloud, you’ll have expenses that won’t exist for the public cloud, such as hardware and electricity.
Hardware and software:
The TCO calculator assumes that each physical server consists of:

System: Intel 2U R2312WT Wildcat-pass Server System
Dual Intel® Xeon® E5-2690v4 14 Core 2.60GHz 35MB Cache
256GB LRDIMM DDR4 2400
2.5TB SSD (5 x Micron M600 512GB SATA 2.5″ SSD)
2 x GE
3-year warranty

For storage we’re assuming each server consists of the following:

SuperStorage Server 6028R-E1CR12L
Single Intel® Xeon® processor E5-2620 v3, 6-Core 2.4G 20M 8GT/s QPI
64GB RAM
Storage: Chipset 12x 3.5″ 6TB SATA3 HDDs + 1x 800GB NVMe SSD (in rear 2.5″ Hot-swap OS drives (mirrored 80GB SSD))
Dual-port 10G SFP+ via AOC-STGN-I2S
2U w/ redundant Hot-swap 920W power supplies
3-year warranty

We’re also assuming a 30% discount off hardware list prices. We’ll depreciate the hardware over 3 years, and assume it needs to be replaced after 4 years.
We also need to take into consideration a number of other factors, including:

Bandwidth costs in and out of the datacenter
$19.00 per Mbps/year

H/W & bandwidth price degradation/decline year over year
10%

Admin cost reduction due to automation year over year
5%

Ratio of compute nodes to OpenStack Controller nodes
25

Power cost ($/kWh)
$0.10

Networking overhead (End of Row switches, WAN connectivity) as a % of server hardware acquisition cost
10%

Networking annual maintenance/support as a % of network hardware and software costs
15%

Networking admin cost as a % of total IT admin effort
8%

Rack annual maintenance/support as % of Rack costs
15%

Average power/rack
10.0 kW

2 x 10 GB Top of the Rack(ToR)  switches + 2 x power distribution unit (PDU) + Rack  chassis + 6 x fiber optic cables + 42 x Cat5 cables
(https://www.fs.com/c/10g-switches-3256 has cheaper switches)
$16,698

Monthly cost to operate a rack
$1,500

Install cost per rack
$2,000

Lab overhead per node (for testing/staging) / year
$50

Storage server raw storage
72,000 GB => (12 x 6 TB)

 
AWS-specific assumptions
Similarly, there are costs that are specific to an AWS implementation. Some, such as Enterprise Support, have corresponding costs on the OpenStack side.  Others, such as cost differentials for reserved instances, are specific to AWS. The TOC calculator assumes the following:

AWS machine selected (2 vCPU, 8 GB memory)
m4.large

AWS price  & inter-datacenter pipe costs degradation/decline year over year
3%

Number of LBaaS
1

% of AWS VMs using reserved instances
30%

% Discount on reserved instances (Typical range [31 –  60]%)
47%

Direct links to AWS
$24,000 per year

Inter-region data transfer/month in terms of the data xfer out
1

Enterprise support as a % of spend on AWS services
4%

AWS support team (internal)
1.00 Full-Time Equivalent

AWS Discount Tier
14%

 
So what’s best?
OK, so what does the TCO analysis tell us?  Which is a better choice from a financial standpoint? As with so many things, it depends on your situation.  For example, AWS is generally less expensive if you need multiple data centers — unless you have a large number of VMs, in which case OpenStack is less expensive. So do yourself a favor and plug your information into the TCO calculator and find out. Please let us know what you find!
The post OpenStack vs AWS Total Cost of Ownership: Assumptions behind the TCO Calculator appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis