 Good afternoon everyone. My name is Marcin Kierdolevich. I'm a director at Canonical responsible for channel business development worldwide. During the track today there are a lot of technical sessions. You learn a lot about you know the great technologies that we're building and I'm sure you're all very excited about that. Now for this one what we want to do we want to bring you a little bit of the real solutions that we built together with partners in order to solve real problems for our customers. That's presentation. I'll share a couple of slides with you tell you about what we do and we'll also be presenting a customer case study here. Can you imagine we can we still get this question asked about you know who is Canonical. I just want to you're now but I want to confirm Canonical is a company behind Ubuntu. We bring you all those great technologies all the software all the tools for you to be able to build the solutions to solve the customer problems in a kind of pretty simple way. Now each time we build it those technologies the proposition we bring to the market is not only about the technology. We wouldn't we wouldn't be able to build others great systems without without the partners that we have and we this is just an example of a couple of technology partnerships that we have. We partner with large companies like IBM like Microsoft like Cisco but for you to know we also partner with small medium sized organizations companies like Plumgrid or Big Switch. Now all of that helps us in creating a best offer available on the market. We give a customer a choice to decide about how deep they would like to go with our technologies. How much of Ubuntu technologies and solutions they would like to use and again this is a representation of a couple of customers that we have and some of them use Ubuntu as the Linux OS only. Some of them build open stack clouds on Ubuntu. Some of them are using our tools to build open stack. That's something what we call the canonical open stack. More there are customers who want to have a fully managed service that we call boot stack just so it's in order to have actually a cloud deployed and managed by us so they can focus on building solutions on top of the cloud. It is a best offer on the market and it's not that we're saying that. The recent survey from OpenStack Foundation confirms that there is a vast majority of OpenStack platforms built on top of Ubuntu. Now all these builds wouldn't happen without resources available on the market to actually bring and help you building the solutions to solve those problems. For that reason we're building a network of implementation partners. We have a global network partners available in all the countries where OpenStack deployments are happening. If you're interested in talking to us about technologies, tools, solutions, but also local resources available, feel free to do that. One of our implementation partners is InterCloud Systems. I would like to introduce Akhil Asim who is VP of cloud services for InterCloud, our partner. Akhil? Hello everyone, this is Akhil Asim. I'm vice president of cloud services at InterCloud Systems. Thanks for joining the session. I have almost 20-25 minutes of presentation just going over the real-life challenge which is to how to move your workloads from VMware-based environments to OpenStack. First, a quick introduction of InterCloud Systems. We are a New Jersey-based company listed on NASDAQ. We have three pillars of excellence. First being our software automation and orchestration. We have written hundreds of thousands of lines of code, and our real focus is towards cloud-based services. Our entire software is born in cloud, so there is no legacy, there is no background. Everything is built from scratch for cloud-based environments. Besides software development, we do a lot of professional services. We have hundreds of consultants across US, and our focus is not only legacy-based but professional services. We are building strong teams around emerging technologies, and our focus is really on SDN and OpenStack-based deployments. The third one is managed hosting. We are in seven data centers across US, and our focus is again private cloud-based services, and we have some limited version of public cloud as well, but the real focus is we enable our customers to adapt cutting-edge technologies with a hybrid approach, where they can have in-house resources, and they can have access to our public-slash-private clouds. First, I would like to thank Marcin for inviting us for this important event. We have a strong partnership with Canonical, and the real focus is that we are an implementation partner. We have teams around Ubuntu's OS and OpenStack, so we help our mutual customers to go quickly adopt newer and latest and greatest OpenStack platforms. We are a certified BootStack provider, so for any deployments where we take the ownership of the entire cloud deployment, and we help our customers to quickly adopt and operationalize the entire OpenStack for them. We are contributing on JuJu's marketplace. We think that is a great tool, and it can help our customers to automate the deployments on OpenStack-based platforms. Just to give you an example, we have deployed OpenStack-based projects, literally less than 20 minutes, so it's a great tool, and we think there's an entire great future of this tool, and we've been actively participating and contributing on this platform. We are also in Canonical's certified training partner to train our customers on this cutting edge platform. In the last but not least, we have developed our own convert solution, which is entirely based on Ubuntu's OpenStack distribution, and I have some slides to go over it. So we've been talking about a lot of industry trends. What we believe in, they are no longer trends. These are the real requirements. Increased agility. So our customers, what we are seeing that customers are looking for rapid deployment of apps. There should be no longer need for days and weeks of time for them to just to roll out a new app. Introduce cost, enhance experience, and risk. What we are hearing is that the customers they are looking for agility, lower cost points, enhance experience, but not at the cost of security. So security is really important. So we really focus on all these four parameters, and we've been successfully delivering it for our customers. So from today's existing IT infrastructure perspective, we all know that with a user they request for a change, or they want to roll out new apps, whether in DevOps environment or Greenfield, it's not about minutes or hours, it's about days and weeks. That's where most of the big enterprise service providers stand today, and that's where they want to be. It shouldn't be, there shouldn't be any human intervention involved. It should be click and operate model where users should be able to go into an internal portal and they should be able to get whatever they want to do. But this all comes with a lot of complexities, and the complexities are SDN, orchestration, security, protocols, intelligence and support. So we are here to solve all these problems and make it easier for our customers so we can take care of entire of these challenges and become a single point, one stop shop for all of these challenges they face today. So based on these requirements, what we just mentioned, we have built three solutions. Simplified OEM, which is operations and management, integration of VMware and OpenStack, because the reality is that most of the deployments are today for Fortune 500 companies, it's all based on VMware. So it should be very simple and inoperatable model where our customers, they can feel comfortable moving towards OpenStack. It has to be an operationalized model. Meta orchestration should be a single dashboard where they can manage their entire workloads and their different applications, whether they are multi-tenant or single-ten. They have to be one pane of glass where they can manage the entire infrastructure. And the last one is seamless integration of OSS and BSS with this OpenStack-based environment. So we are going to answer three things today. What is why, what and how? What is the motivation behind moving from VMware to OpenStack? So I like this quote by Jack Walsett, change before you have to. So it's not about an option anymore. You have to go as a CIO or IT administrator, you have to look OpenStack really seriously and see how it fits into your existing environment. So the motivation, we have listed few points that what could be the motivation behind for any CIO or IT administrator to adapt OpenStack. What the trends we are seeing in the market, most of these IT decisions are no longer made just by the CIO, CFOs, and they are being really involved into these decisions. And they make these decisions as well because cost and speed and it's becoming really important for their IT infrastructure. So your platform should be business-aware. Your business should not be built around IT. It should be the other ways. Like IT should be built around your business. So the first and most important thing is open architecture. You have a keynote speech. For yesterday, there are more than 27,000 developers actively contributing on OpenStack. So it's a really decent ecosystem and it's really important. Really for production. So open architecture is a really important point for any CIO to make that decision. Reduce cost. Of course, cost is an important factor when you make a decision to migrate from VMware to OpenStack because there are no more licensing involved. APIs, compatibility of APIs, that's really important. Now again, you want to build your IT around your business. So regardless, if you're going through an M&A process, acquiring multiple business and merging them together, openness and APIs, they're really important. So OpenStack is really important. You can write your APIs. You can put a couple of developers. They can write APIs and you can seamlessly integrate any system into your infrastructure. SDN solutions, overlay networking is also getting really important as you grow and you build multiple data centers. You really don't want to touch your physical infrastructure to launch new web servers, database servers. So SDN is part of the strategy and OpenStack becomes the foundation and platform for any SDN-based deployments. Non-vendor locking. So you don't want to get locked in with any vendor and OpenStack provides you that platform where you don't get hosed by any vendor for any future plans you have for your IT infrastructure. So with this, we'll get into reality and challenges. The reality is that VMware is going to stay. VMware has all these applications and most of the vendors, they only support applications on ESXi. So KVM or Zen, these are fairly new from the application vendor perspective. So even though we have successfully deployed applications on KVM-based hypervisors, but still from vendor perspective, from OEM, they support only on ESXi. So that is the reason we believe that for now, for the short term next two to five years, it's going to be a coexistence between VMware and OpenStack. In-house teams to support VMware. So there's already teams built around VMware-based solutions, so it's hard to make and bring a change. So it has to coexist with OpenStack. In-curve and legacy infrastructure, those are also very important factors when you think and decide to have a hybrid infrastructure running OpenStack and VMware. Fortune 500, they have already built their infrastructure around VMware-based software. And again, as the community gets bigger, we will see more and more KVM-based certified, validated design into the Fortune 500 companies. So what we believe in that future IT architectures will have three components. Public SaaS-based architecture, which is like Salesforce, Office 365, SAP, HANA, you have public cloud. And then what we think is the most optimized solution for large enterprise is going to be private cloud or private slash hybrid cloud. Now, the next thing is strategy for migration. So once you have made the decision that OpenStack is going to be an essential component of your infrastructure, what is the strategy? How do we go from point A to point B? The first step is identification of critical and less critical workloads. You have to go through entire infrastructure, your applications. And what we do is we go in and we put our entire application into four buckets. It's productivity apps, business apps, DevOps, and then you have Greenfield. What we have learned through our experience that the easiest part is to go with DevOps and Greenfield applications to move because usually it's not really into production. So to build the confidence and trust level, we start from there. And then the next thing is that you cannot forklift your entire infrastructure, so you need the resources. And that's where private cloud comes into the picture. So you want something fully baked, ready to take the workloads in. So you don't have to go through a six-month or year time frame of procurement, design and data center, space and power, all that, those parameters which are involved to make those resources available for infrastructure. And after you have the resources, then, of course, you need to look into each one of those apps and see what are the drivers and what is their OS requirements. You need to make sure that all of that is the environment is available on your OpenStack infrastructure to migrate to the infrastructure. And once we go through that validation process, certification process, we want to make sure that we launch those apps into OpenStack-based environment and make sure that it can take the load and they can easily launch through Horizon and NOVA. And you have your customers and you have your customers and you have your customers and you have your customers and they can access whatever the key business requirements are available. They should be available on the new platform as well. So with this, we get into the steps for migration or slash coexistence. So the first step, like I said, you go through discovery and audit process. Then you go into validation and certification process. And inter-cloud is the first step. And then you go through the process and inter-cloud has a service we launched almost a year back. We call it POC as a service, proof of concept as a service. And then after that, once we validate certify applications on OpenStack, then we get into resources. So private and hybrid cloud comes into the picture that you should have enough resources so you can move those workloads into OpenStack. And of course, last one is orchestration and you integrate the entire new environment with OSS and VSS. So POC as a service, so that's after you get done with your audit and discovery phase, POC as a service as we call it technology validation. So what we found out after talking to more than 100 CIOs and TCTOs and different verticals and enterprise and service providers, there are major challenges when it comes to SDN and OpenStack deployments. And the challenges are infrastructure resources. So if you want to validate hundreds of applications, you really need to build millions of dollars of worth of environment to test and validate. And it's not like a workshop where you come in and you show that, okay, this application can work on KVM or OpenStack. Customers, they want to see real deployment, a replica of their production environment into the lab, which is always multi-vendor and everything should be gelling into each other and it should be seamless integration and because you don't want to hurt your business while you're going through this migration process. OPEX model, they don't want to spend millions of dollars just to validate and certify things. So what we do is that we have huge resources available for our customers so they can come in and we can, so we package it together. We have infrastructure resources, human resources because even in any organization, the teams are not really designed in a way which are meeting with the new, matching with the new platform where you need to have network engineers who can code as well. You need application engineers who can understand storage as well. So we think a different kind of human resources are also needed when you go with this new platform. So human resources are also a challenge when you migrate from a VMware-based or legacy infrastructure to private cloud or OpenStack-based infrastructure. So we fill up those gaps. We have created packages where you have infrastructure resources. You can go and get hundreds of nodes from us. We provide a team, network engineers, OpenStack administrators, and since having a relationship with Ubuntu and Chronicle, we have resources where even for customized deployments, we have access to Chronicles teams as well. And the third one is the use cases. They need a starting point that, okay, now you have made a decision, how do we start? What is the first step? So we actually built, we did a big POC, the case study for a large media company of New York, and the objective, I know there's a lot of stuff, you're probably not able to see it, but the objective was that how do you manage your VMware existing infrastructure through OpenStack? How do you do interoperability testing? Management of VMware clusters into OpenStack. And how do you move your workloads from ESXi-based hypervisor to KVM? So what we did with the case study, we built three parts for our customer. One was VMware 5.0, 6.0, and KVM. And what we did, we basically deployed OpenStack. We managed both parts, 5.0 and 6.0 through OpenStack, and we successfully pushed Contrail across the three parts. So you can actually build overlay tunnels connecting all three different hypervisors. And after that, we successfully demonstrated service chaining concept, cloud mobility, high availability, and performance. And after we got done with all those steps, we wrote a deployment guide for our customer so they can just take that document and give it to their existing operations teams. Okay, go from page one to 100 and just follow these instructions. You will be able to migrate your apps successfully on OpenStack. So just to give you a low-level design, how it looked like, so you can see 5.0 running, 6.0, and KVM. And this is all in our data center out of Manhattan, New York. And we give access to our customers through a private point-to-point circuit or through a VPN tunnel. So this is the physical portion of it, but from hypervisor management perspective, you can see you have KVM hypervisor running on the top, and then you have two hypervisors running on ESXi, two parts. So on your left, this is a physical component, on your right, you can see that we built two virtual networks VNs, green and red. And in green virtual network, those VMs you see G1, G2, and G3, they are all across different hypervisors. So that is the power of SDN contrail running on top of OpenStack, which you can build your virtual network across multiple hypervisors. And then you connect them through service chaining, there's a firewall in between connecting red and green. So without making any changes on your underlying networking physical infrastructure, you can create these topologies. So this is just a view of OpenStack horizon you can see on your screen, like you can see VMVIR and KVM-based host nodes showing up on the screen. So you can easily manage your VMVIR-based environment, ESXi-based host nodes through OpenStack. Again, availability zones running ESXi and KVM managed through one single dashboard. So once you are done with the nodes management through OpenStack, the next thing is the SDN. How do you create those virtual networks across multiple hypervisors and then do service chaining to connect them and to enforce your security policies between virtual networks? So this is an example where you can see that there are two virtual networks, 10.10 and 20.20, and they are across multiple hypervisors on different versions of ESXi and KVM connected through a virtual SRX from Juniper. So that was the technology validation, POC as a service. Now we get into private cloud and what we believe in that if you really compare that in-house ID with public cloud, these are the two major options available today. What are the issues or what are the challenges when you have in-house ID infrastructure? You have high-cap acts. You got to refresh your technology infrastructure every three to five years. You get locked in with the vendors, lead times, you want to roll out new applications, you have resources requirements, you're talking about if not months, weeks of lead times to get new hardware in. IT staff. IT is we believe in becoming a utility just like you pay bills for your electricity and gas. IT is really becoming a utility for the organization, so you shouldn't be having hundreds of people just managing their servers and applications. Space and power. Where do you host your environment if it's on premises? Then you compare it with the public cloud, which doesn't have all these problems, but they have their own problems, which is non-deterministic costs. You really don't know when it comes to budgeting that how do you forecast and allocate budgets? What we see in large enterprise, they're different business units having different, their own individual relationship with public cloud providers. It's really hard to combine and have one assessment of the entire utilization on public cloud platforms. Lack of control. It's like more of a one-size-fits-all. When you have customized requirements and you want to have your own requirements around certain applications or usage, you're really locked in and you need to go and follow your public cloud providers buckets that they have designed. When you're locked in, we also see when you're locked in with those public cloud, when you put your data, it's free to push the data in, but when you take it out, it becomes really expensive. And sometimes it's built on their own hypervisor, so it's really hard to move your apps running from one public cloud provider to another. Data security and compliance, it's another key factor for most of large enterprise and service providers where you need SSA 16, 17 SOC, or HIPAA-based compliance. You cannot be in a shared environment. So the solution, what we believe in, is private cloud. It's not shared, but again, the perception to our customers and large user base is that private cloud is really expensive. It's going back to the same place where you were when you had in-house ID infrastructure. But between our partnership with Canonical InterCloud, we have solved that problem. And what we have successfully shown, that with our private cloud, we call Depod, you can see the cost price points are really attractive. As your requirements for resources grow larger, our Depod private cloud becomes really attractive. So the blue line you see here is for Depod, our private cloud, and you compare it with, we haven't named those other lines on the graph, but these are the major public cloud providers and the cost you can see is really, it makes a lot of sense to go towards private cloud-based environments. So with this, I'm going to just have a few slides to go into architecture for private cloud. So InterCloud systems, we have a strong partnership with Juniper and Canonical. So we're using Juniper's platform from physical standpoint. We're using QFX, the top of the rack switch, EX, MX for routing and switching, and their SDN control for overlay networking. Canonical Ubuntu is the leading OpenStack distribution and we're using OpenStack through Canonical and we have optimized the hardware and software and on top of that, we have our own intellectual property, which is the service enablement platform and our network function virtualization orchestration, NFEO. So from architecture perspective, you can see we have an SDN layer, which is the control system. Then we use Ubuntu OpenStack, JuJu for automation for rapid deployments and this becomes really attractive for our customers. And then you have NFE grid, which is InterCloud's product for the orchestration of virtual network functions. Hypervisor, it's all built on KVM and we support mass through Canonical OpenStack distro. From hardware perspective, we are using Juniper switching fabric. We have optimized Ceph distributed storage, which comes with that solution and we use compute from SuperMicro and HP. So with this, the last one slide is just to show different models of our private cloud. We call it D-Pod 100, 200, and 300. D-Pod 100 is literally a quarter cabinet solution. D-Pod 200 is a half cabinet and D-Pod 300 is full cabinet solution. It's highly dense, so you can see that with a very small footprint, it can deliver a lot of resources. Now, the beauty of this entire solution is it's available on OPEX model. From business perspective, you get the same features of public cloud, so it's OPEX model. There is no CAPEX involved to use this platform and you get one single point of contact for an entire support model. You don't have to deal with 10 different vendors. Since we are Canonical's certified boot stack provider, we take the ownership of the entire solution and we provide 24x7 support to our customers. It is scalable model. It can be deployed in our data centers, the seven data centers we have in U.S. and we're expanding, or it can be deployed on premise and customer location. So just from the density perspective, you can see D-Pod 100 is 1TB of RAM in literally 11RU box. D-Pod 200 has almost 3TB of RAM and 300 D-Pod 300 is 8TB of RAM in one cabinet. So it's a really dense solution and as you go scale up from D-Pod 100 to 200, we can help you move from D-Pod 100 to 200 by adding more resources into it. So it's not that you just locked in into one platform, you cannot just do any upgrades. So with this, any questions? And also I would really encourage if you can fill up the feedback form before you guys leave. Thank you very much. Any questions? I'm sorry. There's storage in your D-Pod 100. Right. So 30 terabytes. 30 terabytes of storage, yes. Is the POC as a service your product or is your approach? It's basically our service. It's our service we provide, we have packaged it together. So POC as a service, we have defined the use cases, but if you have any specific use cases we can always add in. But it's our trademark, our service. Yeah. Sorry? Sure. Absolutely. We'll pass on the contacts. Yes. Thank you. All right guys. I think. Thanks, Marcel.