What does ³Flavor sizes² include? Memory, CPU count? Is there a
wide-enough care for other measures of performance or compatibility like:
- virtualization type: none (hardware/metal), xen, kvm, hyperv
- cpu speed, cache or some form of performance index
- volume types: SATA, SSD, iSCSI, and a
On 17 March 2015 at 22:02, Davis, Amos (PaaS-Core) amos.steven.da...@hp.com
wrote:
Ceph/Cinder:
LVM or other?
SCSI-backed?
Any others?
I'm wondering why any of the above matter to an application. The entire
point of cinder is to abstract those details from the application. I'd be
very
What you're proposing quickly becomes an authorization question. What
capabilities can this service provide? is a far less useful question than
what capabilities is the user authorized to consume? More generally, why
would you advertise any capability that the user is going to receive a
4xx/5xx
Here's a possibly relevant use case for this discussion:
1) Running Icehouse OpenStack
2) Keystone reports v3.0 auth capabilities
3) If you actually use the v3.0 auth, then any nova call that gets passed
through to cinder fails due to the code in Icehouse being unable to parse
the 3.0 service
On 18 March 2015 at 03:33, Duncan Thomas duncan.tho...@gmail.com wrote:
On 17 March 2015 at 22:02, Davis, Amos (PaaS-Core)
amos.steven.da...@hp.com wrote:
Ceph/Cinder:
LVM or other?
SCSI-backed?
Any others?
I'm wondering why any of the above matter to an application.
The Neutron
All,
The Application EcoSystem Working Group realized during the mid-cycle meetup in
Philadelphia that there is no way to get the capabilities of an Openstack cloud
so that applications can measure their compatibility against that cloud. In
other words, if we create an Openstack App
On Mar 17, 2015, at 1:02 PM, Davis, Amos (PaaS-Core)
amos.steven.da...@hp.com wrote:
All,
The Application EcoSystem Working Group realized during the mid-cycle meetup
in Philadelphia that there is no way to get the capabilities of an Openstack
cloud so that applications can measure
