Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-18 Thread Rochelle Grober
From: Duncan Thomas > On 18 May 2017 at 22:26, Rochelle Grober > wrote: > > If you're going to use --distance, then you should have specific values > (standard definitions) rather than operator defined: > > And for that matter, is there something better than distance? Collocated > maybe? > > >

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-18 Thread Duncan Thomas
On 18 May 2017 at 22:26, Rochelle Grober wrote: > If you're going to use --distance, then you should have specific values > (standard definitions) rather than operator defined: > And for that matter, is there something better than distance? Collocated > maybe? > > colocated={local, rack, row, m

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-18 Thread Rochelle Grober
From: Matt Riedemann > On 5/15/2017 2:28 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: > > Hi all, > > > > I'd like to follow up on a few discussions that took place last week > > in Boston, specifically in the Compute Instance/Volume Affinity for > > HPC session > > (https://etherpad.openstack

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-15 Thread Matt Riedemann
On 5/15/2017 5:34 PM, Matt Riedemann wrote: On 5/15/2017 5:23 PM, Eric Fried wrote: How about aggregates? https://www.youtube.com/watch?v=fu6jdGGdYU4&feature=youtu.be&t=1784 Aggregates aren't exposed to the user directly, they are exposed to the user via availability zones. Avoiding the explos

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-15 Thread Matt Riedemann
On 5/15/2017 5:23 PM, Eric Fried wrote: How about aggregates? https://www.youtube.com/watch?v=fu6jdGGdYU4&feature=youtu.be&t=1784 Aggregates aren't exposed to the user directly, they are exposed to the user via availability zones. Avoiding the explosion of 1:1 AZs is what we want to avoid for

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-15 Thread Eric Fried
> If there are alternative ideas on how to design or model this, I'm all > ears. How about aggregates? https://www.youtube.com/watch?v=fu6jdGGdYU4&feature=youtu.be&t=1784 On 05/15/2017 05:04 PM, Matt Riedemann wrote: > On 5/15/2017 2:28 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: >> Hi all, >>

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-15 Thread Matt Riedemann
On 5/15/2017 2:28 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: Hi all, I'd like to follow up on a few discussions that took place last week in Boston, specifically in the Compute Instance/Volume Affinity for HPC session (https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinit

[openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

2017-05-15 Thread Edmund Rhudy (BLOOMBERG/ 120 PARK)
Hi all, I'd like to follow up on a few discussions that took place last week in Boston, specifically in the Compute Instance/Volume Affinity for HPC session (https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc). In this session, the discussions all trended towards ad