ct: Re: [openstack-dev] [Magnum] Next auto-scaling feature design?
We have had numerous discussion on this topic, including a presentation and a
design session
in Tokyo, but we have not really arrived at a consensus yet. Part of the
problem is that auto-scaling
at the container level is still
ailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 08/18/2016 12:26 PM
Subject: Re: [openstack-dev] [Magnum] Next auto-scaling feature design?
> -Original Message-
> From: hie...@vn.fujitsu.com [mailto:hie...@vn.fujitsu
> -Original Message-
> From: hie...@vn.fujitsu.com [mailto:hie...@vn.fujitsu.com]
> Sent: August-18-16 3:57 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [Magnum] Next auto-scaling feature design?
>
> Hi Magnum folks,
>
> I have
iginal Message-
From: Tim Bell [mailto:tim.b...@cern.ch]
Sent: Thursday, August 18, 2016 3:19 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Magnum] Next auto-scaling feature design?
> On 18 Aug
> On 18 Aug 2016, at 09:56, hie...@vn.fujitsu.com wrote:
>
> Hi Magnum folks,
>
> I have some interests in our auto scaling features and currently testing with
> some container monitoring solutions such as heapster, telegraf and
> prometheus. I have seen the PoC session corporate with Senlin
Hi Magnum folks,
I have some interests in our auto scaling features and currently testing with
some container monitoring solutions such as heapster, telegraf and prometheus.
I have seen the PoC session corporate with Senlin in Austin and have some
questions regarding of this design:
- We have
