That seems like a strange definition. It doesn't incorporate the usual multi-tenancy requirement that traditionally separates private from public clouds. By that definition, Rackspace's Private Cloud offer, where we design, deploy and operate a single-tenant cloud on behalf of customers (in their data-center or ours) would be considered a "public" cloud.
On Fri, Sep 23, 2016 at 3:54 PM, Rochelle Grober <rochelle.gro...@huawei.com > wrote: > Hi Matt, > > > > At considerable risk of heading down a rabbit hole... how are you defining > "public" cloud for these purposes? > > > > Cheers, > > Blair > > > > Any cloud that provides a cloud to a thirdparty in exchange for money. > So, rent a VM, rent a collection of vms, lease a fully operational cloud > spec'ed to your requirements, lease a team and HW with your cloud on > them..... > > > > So any cloud that provides offsite IAAS to lessees > > > > --Rockyy > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- Kenny Johnston | irc:kencjohnston | @kencjohnston
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators