> -----Original Message-----
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: 22 January 2014 02:01
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds
> On Tue, 2014-01-21 at 14:21 +0000, Khanh-Toan Tran wrote:
> > > Exactly - that's why I wanted to start this debate about the way
> > > forward for the Pcloud Blueprint, which was heading into some kind
> > > of middle ground.  As per my original post, and it sounds like the
> > > three of us are at least aligned I'm proposing to spilt this into
> > > two streams:
> > >
> > > i) A new BP that introduces the equivalent of AWS dedicated instances.
> >
> > Why do you want to transform pCloud into AWS dedicated instances? As I
> > see it, pCloud is for requesting physical hosts (HostFlovors as in
> > pcloud wiki) on which users can create their own instances
> > (theoretically in unlimited number).
> > Therefore it should be charged per physical server (HostFlavor), not
> > by instances. It is completely different from AWS dedicated instances
> > which is charged per instance. IMO, pcloud resembles Godrid Dedicated
> > Server, not AWS Dedicated Instance.
> It resembles managed/dedicated hosting. Not cloud.

I think there is a cross-over point here somewhere - call it "managed cloud" 
where the user doesn't want to run a cloud but does want (and is willing to pay 
for) some guarantee of isolation of hypervisors, but also wants to share other 
aspects of the cloud (images, volumes, VPC networks).   They get a degree of 
controlled Admin (can set up their own flavors for example) - but they are 
still only doing configuration type tasks, not operating the system as such - 
and probably most significantly they can build systems that are a combination 
of instances running on shared and dedicated servers.    That's kind of where 
pCLouds was evolving to - and  I think you can build such a beast more 
effectively by running multiple dedicated Nova's configured to take to a shared 
Glance/Cinder/Neutron.   I.e this belongs on-Nova, not in-Nova

OpenStack-dev mailing list

Reply via email to