Re: [openstack-dev] [oslo][nova] how to best deal with default periodic task spacing behavior

2014-05-22 Thread Matthew Gilliard
We (HP Helion) are completely fine with a change that reduces server load
and makes things more predictable.  It would have been very hard to rely
heavily on the old behaviour.  Thanks for adding me to the patch, too, Matt

  Matthew


On Wed, May 21, 2014 at 4:40 PM, Doug Hellmann
wrote:

> On Tue, May 20, 2014 at 10:15 AM, Matt Riedemann
>  wrote:
> > Between patch set 1 and patch set 3 here [1] we have different solutions
> to
> > the same issue, which is if you don't specify a spacing value for
> periodic
> > tasks then they run whenever the periodic task processor runs, which is
> > non-deterministic and can be staggered if some tasks don't complete in a
> > reasonable amount of time.
> >
> > I'm bringing this to the mailing list to see if there are more opinions
> out
> > there, especially from operators, since patch set 1 changes the default
>
> You may get more feedback from operators on the main openstack list.
> I'm still catching up on backlog after the summit, so apologies if
> you've already posted there.
>
> Doug
>
> > behavior to have the spacing value be the DEFAULT_INTERVAL (hard-coded 60
> > seconds) versus patch set 3 which makes that behavior configurable so the
> > admin can set global default spacing for tasks, but defaults to the
> current
> > behavior of running every time if not specified.
> >
> > I don't like a new config option, but I'm also not crazy about changing
> > existing behavior without consensus.
> >
> > [1] https://review.openstack.org/#/c/93767/
> >
> > --
> >
> > Thanks,
> >
> > Matt Riedemann
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][nova] how to best deal with default periodic task spacing behavior

2014-05-21 Thread Doug Hellmann
On Tue, May 20, 2014 at 10:15 AM, Matt Riedemann
 wrote:
> Between patch set 1 and patch set 3 here [1] we have different solutions to
> the same issue, which is if you don't specify a spacing value for periodic
> tasks then they run whenever the periodic task processor runs, which is
> non-deterministic and can be staggered if some tasks don't complete in a
> reasonable amount of time.
>
> I'm bringing this to the mailing list to see if there are more opinions out
> there, especially from operators, since patch set 1 changes the default

You may get more feedback from operators on the main openstack list.
I'm still catching up on backlog after the summit, so apologies if
you've already posted there.

Doug

> behavior to have the spacing value be the DEFAULT_INTERVAL (hard-coded 60
> seconds) versus patch set 3 which makes that behavior configurable so the
> admin can set global default spacing for tasks, but defaults to the current
> behavior of running every time if not specified.
>
> I don't like a new config option, but I'm also not crazy about changing
> existing behavior without consensus.
>
> [1] https://review.openstack.org/#/c/93767/
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][nova] how to best deal with default periodic task spacing behavior

2014-05-20 Thread Joe Gordon
On Tue, May 20, 2014 at 8:00 AM, Davanum Srinivas  wrote:

> @Matt,
>
> Agree, My vote would be to change existing behavior.
>

Same.  I think its reasonable to say the current behavior is not ideal
(otherwise we wouldn't have changed it), and that the new behavior is
better for the vast majority of folks.


>
> -- dims
>
> On Tue, May 20, 2014 at 10:15 AM, Matt Riedemann
>  wrote:
> > Between patch set 1 and patch set 3 here [1] we have different solutions
> to
> > the same issue, which is if you don't specify a spacing value for
> periodic
> > tasks then they run whenever the periodic task processor runs, which is
> > non-deterministic and can be staggered if some tasks don't complete in a
> > reasonable amount of time.
> >
> > I'm bringing this to the mailing list to see if there are more opinions
> out
> > there, especially from operators, since patch set 1 changes the default
> > behavior to have the spacing value be the DEFAULT_INTERVAL (hard-coded 60
> > seconds) versus patch set 3 which makes that behavior configurable so the
> > admin can set global default spacing for tasks, but defaults to the
> current
> > behavior of running every time if not specified.
> >
> > I don't like a new config option, but I'm also not crazy about changing
> > existing behavior without consensus.
> >
> > [1] https://review.openstack.org/#/c/93767/
> >
> > --
> >
> > Thanks,
> >
> > Matt Riedemann
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][nova] how to best deal with default periodic task spacing behavior

2014-05-20 Thread Davanum Srinivas
@Matt,

Agree, My vote would be to change existing behavior.

-- dims

On Tue, May 20, 2014 at 10:15 AM, Matt Riedemann
 wrote:
> Between patch set 1 and patch set 3 here [1] we have different solutions to
> the same issue, which is if you don't specify a spacing value for periodic
> tasks then they run whenever the periodic task processor runs, which is
> non-deterministic and can be staggered if some tasks don't complete in a
> reasonable amount of time.
>
> I'm bringing this to the mailing list to see if there are more opinions out
> there, especially from operators, since patch set 1 changes the default
> behavior to have the spacing value be the DEFAULT_INTERVAL (hard-coded 60
> seconds) versus patch set 3 which makes that behavior configurable so the
> admin can set global default spacing for tasks, but defaults to the current
> behavior of running every time if not specified.
>
> I don't like a new config option, but I'm also not crazy about changing
> existing behavior without consensus.
>
> [1] https://review.openstack.org/#/c/93767/
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: http://davanum.wordpress.com

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [oslo][nova] how to best deal with default periodic task spacing behavior

2014-05-20 Thread Matt Riedemann
Between patch set 1 and patch set 3 here [1] we have different solutions 
to the same issue, which is if you don't specify a spacing value for 
periodic tasks then they run whenever the periodic task processor runs, 
which is non-deterministic and can be staggered if some tasks don't 
complete in a reasonable amount of time.


I'm bringing this to the mailing list to see if there are more opinions 
out there, especially from operators, since patch set 1 changes the 
default behavior to have the spacing value be the DEFAULT_INTERVAL 
(hard-coded 60 seconds) versus patch set 3 which makes that behavior 
configurable so the admin can set global default spacing for tasks, but 
defaults to the current behavior of running every time if not specified.


I don't like a new config option, but I'm also not crazy about changing 
existing behavior without consensus.


[1] https://review.openstack.org/#/c/93767/

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev