Hey Jirka!
I wasn't aware of the other options available. Basically yes, you now just
need to upload a tarball of the templates to swift. You can see in the
client:
-tarball.tarball_extract_to_swift_container(
-swift_client, tmp_tarball.name, container_name)
+_upload
Hello, thanks for bringing this up.
I am going to try to test this patch with TripleO UI tomorrow. Without
properly looking at the patch, questions I would like to get answers for
are:
How is this going to affect ways to create/update deployment plan?
Currently user is able to create deployment p
Thanks for taking this on Ian! I'm fully on board with the effort. I
like the consolidation and performance improvements. Storing t-h-t
templates in Swift worked okay 3-4 years ago. Now that we have more
templates, many of which need .j2 rendering the storage there has
become quite a bottleneck.
A
On 8/2/18 1:34 AM, Ian Main wrote:
Hey folks!
So I've been working on some patches to speed up plan operations in
TripleO. This was originally driven by the UI needing to be able to
perform a 'plan upload' in something less than several minutes. :)
https://review.openstack.org/#/c/581153/
Hey folks!
So I've been working on some patches to speed up plan operations in
TripleO. This was originally driven by the UI needing to be able to
perform a 'plan upload' in something less than several minutes. :)
https://review.openstack.org/#/c/581153/
https://review.openstack.org/#/c/581141/
