Re: [openstack-dev] Enabling an Open Cloud with OpenStack
Hi Orran, We also have a project called Tricircle that aim to solve similar problem, but with a different approach with Mercador. You and your team are more than welcome to join the discussion we will hold in Tricircle Meeting. See the details at https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg54861.html, and https://github.com/stackforge/tricircle , and also our PoC results http://www.slideshare.net/JoeHuang7/test-report-for-open-stack-cascading-solution-to-support-1-million-v-ms-in-100-data-centers :) Hope you guys find it helpful. On Wed, Jun 10, 2015 at 9:37 PM, Orran Krieger okr...@gmail.com wrote: Dear OpenStack community, The short version: We are proposing a new set of use cases for OpenStack and a set of changes to enable a multi-landlord cloud model, where multiple service providers can cooperate (and compete) to stand up services in a single cloud. We had great feedback from the community in the summit, and came away with two strong messages: 1) this is a radical enough change that we should do an end-to-end proof of concept, and 2) we should post to this list what we are doing to make it visible to the broader developer community; fully solving the problems of a multi-landlord cloud will impact more projects than we understand today. We hope to have available prototypes of the key enabling changes by the keystone mid-cycle and an end-to-end demo by the Tokyo summit. Two additional points: 1. Solving the problems of landlords that don't trust each other also brings defense in depth for a single provider cloud; potentially preventing an exploit of one service from compromising an entire cloud. 2. This work strongly relates to resource federation work that is ongoing in OpenStack, and is complementary to, and being persued in the context of the recently annouced Mercador project. We, of course, welcome participating by other developers interested in working with us on this through the Mercador project or by contacting us as per info below. The long version: -- All current clouds are stood up by a single company or organization, creating a vertically integrated monopoly. Any competition is between entire clouds and is limited by the customer's ability to move their data over the connectivity between clouds. We think an alternative model is possible, where different organizations can stand up individual services in the same data centers, and the customer (or intermediaries acting on their behalf) can pick and choose between them. We call this model of having multiple landlords in a cloud an Open Cloud eXchange (OCX) (http://www.cs.bu.edu/fac/best/res/papers/ic14.pdf). The OCX model would enable more innovation by technology companies, enable cloud research and provide more choice to cloud consumers. We are developing this model in a new public cloud, the Massachusetts Open Cloud (MOC), that is just being started in the MGHPCC data center (http://www.mghpcc.org) shared between Boston University, Harvard University, the Massachusetts Institute of Technology, Northeastern University, and the University of Massachusetts. Some use cases being explored in the context of the MOC illustrate the potential of this model: o Harvard and MIT both stand up their own OpenStack cloud for students, but provide resources on-demand to the MOC that can be used by researchers that collaborate between the universities and by external users. o A storage company stands up a new innovative block storage service on a few racks in the MGHPCC, operates it themselves, and makes it available to users of the MOC and/or the individual university clouds. The storage company is in total control of price, automation, and SLA for the service, and users can choose if they want to use the service. o A company stands up a new compute service with innovative hardware (e.g., FPGAs, crypto accellerator) or pricing model. A customer with a two Petabyte disk volume can switch to using that compute without having to move the data. o A research group at Boston University and Northeastern develops a highly elastic compute service that can checkpoint 1000s of servers in seconds into SSD, and broadcast provision a distributed application to allow an interactive medical imaging application that wants 1000s of servers for a few seconds. o A security sensitive life sciences company exploits software from the MACS project (http://www.bu.edu/hic/research/macs/) to distribute their data across two storage services from non-colluding providers. The data is accessed from a Nova compute service running on a trusted compute platform developed collaboratively with Intel. Since all services are deployed in the same datacenter, the computation is efficient. o Students in a cloud computing course offered by Northeastern and Boston University faculty
[openstack-dev] Enabling an Open Cloud with OpenStack
Dear OpenStack community, The short version: We are proposing a new set of use cases for OpenStack and a set of changes to enable a multi-landlord cloud model, where multiple service providers can cooperate (and compete) to stand up services in a single cloud. We had great feedback from the community in the summit, and came away with two strong messages: 1) this is a radical enough change that we should do an end-to-end proof of concept, and 2) we should post to this list what we are doing to make it visible to the broader developer community; fully solving the problems of a multi-landlord cloud will impact more projects than we understand today. We hope to have available prototypes of the key enabling changes by the keystone mid-cycle and an end-to-end demo by the Tokyo summit. Two additional points: 1. Solving the problems of landlords that don't trust each other also brings defense in depth for a single provider cloud; potentially preventing an exploit of one service from compromising an entire cloud. 2. This work strongly relates to resource federation work that is ongoing in OpenStack, and is complementary to, and being persued in the context of the recently annouced Mercador project. We, of course, welcome participating by other developers interested in working with us on this through the Mercador project or by contacting us as per info below. The long version: -- All current clouds are stood up by a single company or organization, creating a vertically integrated monopoly. Any competition is between entire clouds and is limited by the customer's ability to move their data over the connectivity between clouds. We think an alternative model is possible, where different organizations can stand up individual services in the same data centers, and the customer (or intermediaries acting on their behalf) can pick and choose between them. We call this model of having multiple landlords in a cloud an Open Cloud eXchange (OCX) (http://www.cs.bu.edu/fac/best/res/papers/ic14.pdf http://www.cs.bu.edu/fac/best/res/papers/ic14.pdf). The OCX model would enable more innovation by technology companies, enable cloud research and provide more choice to cloud consumers. We are developing this model in a new public cloud, the Massachusetts Open Cloud (MOC), that is just being started in the MGHPCC data center (http://www.mghpcc.org http://www.mghpcc.org/) shared between Boston University, Harvard University, the Massachusetts Institute of Technology, Northeastern University, and the University of Massachusetts. Some use cases being explored in the context of the MOC illustrate the potential of this model: o Harvard and MIT both stand up their own OpenStack cloud for students, but provide resources on-demand to the MOC that can be used by researchers that collaborate between the universities and by external users. o A storage company stands up a new innovative block storage service on a few racks in the MGHPCC, operates it themselves, and makes it available to users of the MOC and/or the individual university clouds. The storage company is in total control of price, automation, and SLA for the service, and users can choose if they want to use the service. o A company stands up a new compute service with innovative hardware (e.g., FPGAs, crypto accellerator) or pricing model. A customer with a two Petabyte disk volume can switch to using that compute without having to move the data. o A research group at Boston University and Northeastern develops a highly elastic compute service that can checkpoint 1000s of servers in seconds into SSD, and broadcast provision a distributed application to allow an interactive medical imaging application that wants 1000s of servers for a few seconds. o A security sensitive life sciences company exploits software from the MACS project (http://www.bu.edu/hic/research/macs/ http://www.bu.edu/hic/research/macs/) to distribute their data across two storage services from non-colluding providers. The data is accessed from a Nova compute service running on a trusted compute platform developed collaboratively with Intel. Since all services are deployed in the same datacenter, the computation is efficient. o Students in a cloud computing course offered by Northeastern and Boston University faculty (https://okrieg.github.io/EC500/index.html https://okrieg.github.io/EC500/index.html) develop and stand up an experimental proxy service for open stack services that provides users of the MOC a Swift service that combines the inventory of multiple underlying Swift services. While no existing cloud stack can support the OCX model out of the box, OpenStack is much closer than anything else, and we have been exploring what changes will be required to enable this model (http://open.bu.edu/handle/2144/11214 http://open.bu.edu/handle/2144/11214) and worked with our partners in the community to submit a number of
