Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

for usage questions) Subject: Re: [openstack-dev] [nova] FYI: Removing default flavors from nova On Wed, Apr 6, 2016 at 9:29 AM, Fox, Kevin M <kevin@pnnl.gov> wrote: > It feels kind of like a defcore issue though. Its harder for app developers > to create stuff like heat templa

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

stack.org/pipermail/user-committee/2016-April/000722.html -Christopher > > Thanks, > Kevin > > From: Sean Dague [s...@dague.net] > Sent: Wednesday, April 06, 2016 3:47 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

> On Apr 6, 2016, at 11:14 AM, Sean Dague wrote: > > On 04/06/2016 01:28 PM, Dean Troyer wrote: >> On Wed, Apr 6, 2016 at 12:10 PM, Tim Bell > > wrote: >> >>I think Heat needs more of an query engine along the lines of “give me a

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On 04/06/2016 01:28 PM, Dean Troyer wrote: > On Wed, Apr 6, 2016 at 12:10 PM, Tim Bell > wrote: > > I think Heat needs more of an query engine along the lines of “give me a > flavor with at least X cores and Y GB RAM” rather than hard coding >

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

> Ops != Cloud App developers. We've really made the latter's job hard, > and are often increasing the difficulty on them. This pushes them > away from OpenStack and eliminates a lot of potential users of > OpenStack, meaning Ops have fewer users then they should. Lets not > continue this trend.

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

questions) Subject: Re: [openstack-dev] [nova] FYI: Removing default flavors from nova On 06/04/16 18:36, "Daniel P. Berrange" <berra...@redhat.com> wrote: >On Wed, Apr 06, 2016 at 04:29:00PM +, Fox, Kevin M wrote: >> It feels kind of like a defcore issue though. Its har

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 6, 2016 at 12:10 PM, Tim Bell wrote: > I think Heat needs more of an query engine along the lines of “give me a > flavor with at least X cores and Y GB RAM” rather than hard coding > m1.large. > Core performance is another parameter that would be interesting to

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

. :/ Thanks, Kevin From: Dan Smith [d...@danplanet.com] Sent: Wednesday, April 06, 2016 10:09 AM To: OpenStack Development Mailing List (not for usage questions); Daniel P. Berrange Subject: Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On 06/04/16 18:36, "Daniel P. Berrange" wrote: >On Wed, Apr 06, 2016 at 04:29:00PM +, Fox, Kevin M wrote: >> It feels kind of like a defcore issue though. Its harder for app >> developers to create stuff like heat templates intended for cross >> cloud that recommend a

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

> It still was more common then not I think? So making it less common > is probably a step on the wrong direction. The responses on the operators mailing list were 100% positive for removal. As Dan said, calling these a standard is really not reasonable. They're just defaults, copied from AWS

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

(not for usage questions) Subject: Re: [openstack-dev] [nova] FYI: Removing default flavors from nova On Wed, Apr 06, 2016 at 04:29:00PM +, Fox, Kevin M wrote: > It feels kind of like a defcore issue though. Its harder for app > developers to create stuff like heat templates intended for

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 06, 2016 at 04:29:00PM +, Fox, Kevin M wrote: > It feels kind of like a defcore issue though. Its harder for app > developers to create stuff like heat templates intended for cross > cloud that recommend a size, m1.small, without a common reference. Even with Nova defining these

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

: Re: [openstack-dev] [nova] FYI: Removing default flavors from nova On 04/06/2016 04:19 AM, Sylvain Bauza wrote: > > > Le 06/04/2016 06:44, Qiming Teng a écrit : >> Not an expert of Nova but I am really shocked by such a change. Because >> I'm not a Nova expert, I don't ha

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 6, 2016 at 7:47 PM, Sean Dague wrote: > On 04/06/2016 04:19 AM, Sylvain Bauza wrote: >> >> >> Le 06/04/2016 06:44, Qiming Teng a écrit : >>> Not an expert of Nova but I am really shocked by such a change. Because >>> I'm not a Nova expert, I don't have a say on the

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On 04/06/2016 04:19 AM, Sylvain Bauza wrote: > > > Le 06/04/2016 06:44, Qiming Teng a écrit : >> Not an expert of Nova but I am really shocked by such a change. Because >> I'm not a Nova expert, I don't have a say on the *huge* efforts in >> maintaining some builtin/default flavors. As a user I

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

Le 06/04/2016 06:44, Qiming Teng a écrit : Not an expert of Nova but I am really shocked by such a change. Because I'm not a Nova expert, I don't have a say on the *huge* efforts in maintaining some builtin/default flavors. As a user I don't care where the data have been stored, but I do care

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 6, 2016 at 1:44 PM, Qiming Teng wrote: > Not an expert of Nova but I am really shocked by such a change. Because > I'm not a Nova expert, I don't have a say on the *huge* efforts in > maintaining some builtin/default flavors. As a user I don't care where >

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

Not an expert of Nova but I am really shocked by such a change. Because I'm not a Nova expert, I don't have a say on the *huge* efforts in maintaining some builtin/default flavors. As a user I don't care where the data have been stored, but I do care that they are gone. They are gone because they