On 14 Nov 2013, at 21:46, Zane Bitter wrote:
> If you have a service that is stateless and only responds to user requests,
> then scaling it out is easy (just stick it behind a load balancer). If it has
> state (i.e. a database), things become a whole lot more complicated to
> maintain consis
On Thu, Nov 14, 2013 at 4:29 AM, Renat Akhmerov wrote:
> As for EventScheduler proposal, I think it actually fits Mistral model
> very well. What described in EvenScheduler is basically the ability to
> configure webhooks to be called periodically or at a certain time. First of
> all, from the ver
On 14/11/13 12:26, Renat Akhmerov wrote:
On 14 Nov 2013, at 18:03, Zane Bitter mailto:zbit...@redhat.com>> wrote:
What might be a downside is that sharing a back-end may not be
technically convenient - one thing we have been reminded of in Heat is
that a service with timed tasks has to be scal
On 14 Nov 2013, at 18:03, Zane Bitter wrote:
> What might be a downside is that sharing a back-end may not be technically
> convenient - one thing we have been reminded of in Heat is that a service
> with timed tasks has to be scaled out in a completely different way to a
> service that avoid
On 14/11/13 11:29, Renat Akhmerov wrote:
As for EventScheduler proposal, I think it actually fits Mistral model
very well. What described in EvenScheduler is basically the ability to
configure webhooks to be called periodically or at a certain time. First
of all, from the very beginning the conce
As for EventScheduler proposal, I think it actually fits Mistral model very
well. What described in EvenScheduler is basically the ability to configure
webhooks to be called periodically or at a certain time. First of all, from the
very beginning the concept of scheduling has been considered a v
On 13 нояб. 2013 г., at 6:39, Angus Salkeld wrote:
> Your work mates;) https://github.com/rackerlabs/qonos
>
> how about merge qonos into mistral, or at lest put it into stack forge?
Just got to looking at qonos. It actually looks similar in some ways to Mistral
but with some differences: no
On 13 нояб. 2013 г., at 18:12, Renat Akhmerov wrote:
>
> On 13 нояб. 2013 г., at 6:39, Angus Salkeld wrote:
>
>>> Second question: if the proposed "EventScheduler" becomes a real project,
>>> which OpenStack Program should it live under?
>>>
>>> Third question: Is anyone actively working on
On 13 нояб. 2013 г., at 6:39, Angus Salkeld wrote:
> On 12/11/13 15:13 -0800, Christopher Armstrong wrote:
>> Given the recent discussion of scheduled autoscaling at the summit session
>> on autoscaling, I looked into the state of scheduling-as-a-service in and
>> around OpenStack. I found two r
On 12/11/13 15:13 -0800, Christopher Armstrong wrote:
Given the recent discussion of scheduled autoscaling at the summit session
on autoscaling, I looked into the state of scheduling-as-a-service in and
around OpenStack. I found two relevant wiki pages:
https://wiki.openstack.org/wiki/EventSched
Given the recent discussion of scheduled autoscaling at the summit session
on autoscaling, I looked into the state of scheduling-as-a-service in and
around OpenStack. I found two relevant wiki pages:
https://wiki.openstack.org/wiki/EventScheduler
https://wiki.openstack.org/wiki/Mistral/Cloud_Cron
11 matches
Mail list logo
