On 10/10/16 11:11, Spyros Trigazis wrote:
4. Finally, a thought under investigation is replacing the nodes one
by one using a different image. e.g. Upgrade from fedora 24 to 25
with new versions of packages all in a new qcow2 image. How could
we update the stack for this?
This should w
On Mon, Oct 10, 2016 at 05:11:28PM +0200, Spyros Trigazis wrote:
> Hi heat and magnum.
>
> Apart from the scalability issues that have been observed, I'd like to
> add few more subjects to discuss during the summit.
>
> 1. One nested stack per node and linear scale of cluster creation
> time.
>
On 11/10/16 02:24, Rabi Mishra wrote:
1.2
For large stacks, 1000 nodes, the final call to heat to
fetch the
IPs for all nodes takes 3 to 4 minutes. In heat, the stack
has status
CREATE_COMPLETE but magnum's state is updated
Hi Spyros,
Thanks for starting this thread. My initial understanding was that the
planned session would more around
heat performance/scalability issues w/ magnum.
As most of the additional stuff you mentioned are around heat best
practices, I think the specs/reviews
would be a great place to star
Hi Sergey,
I have seen the session, I wanted to add more details to
start the discussion earlier and to be better prepared.
Thanks,
Spyros
On 10 October 2016 at 17:36, Sergey Kraynev wrote:
> Hi Spyros,
>
> AFAIK we already have special session slot related with your topic.
> So thank you for
Hi Spyros,
AFAIK we already have special session slot related with your topic.
So thank you for the providing all items here.
Rabi, can we add link on this mail to etherpad ? (it will save our time
during session :) )
On 10 October 2016 at 18:11, Spyros Trigazis wrote:
> Hi heat and magnum.
>
>
Hi heat and magnum.
Apart from the scalability issues that have been observed, I'd like to
add few more subjects to discuss during the summit.
1. One nested stack per node and linear scale of cluster creation
time.
1.1
For large stacks, the creation of all nested stack scales linearly. We
haven'
