s ago. Now that we have more
>> templates, many of which need .j2 rendering the storage there has
>> become quite a bottleneck.
>>
>> Additionally, since we'd be sending commands to Heat via local
>> filesystem template storage we could consider using softlinks again
>>
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/
Wesley Hayutin wrote:
> Greetings,
>
> I wanted to send a status update on the quickstart based containerized
> compute ci.
>
> The work is here:
> https://review.openstack.org/#/c/393348/
>
> I had two passes on the morning of Nov 30 in a row, then later that day the
> deployment started to
Fox, Kevin M wrote:
> +1 for TripleO taking a look at Kolla.
>
> Some random thoughts:
>
> I'm in the middle of deploying a new cloud and I couldn't use either TripleO
> or Kolla for various reasons. A few reasons for each:
> * TripeO - worries me for ever having to do a major upgrade of the
Sean Dague wrote:
On 12/04/2014 05:38 PM, Matt Riedemann wrote:
On 12/4/2014 4:06 PM, Michael Still wrote:
+Eric and Ian
On Fri, Dec 5, 2014 at 8:31 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
This came up in the nova meeting today, I've opened a bug [1] for it.
Since
Angus Lees wrote:
I've been reading a bunch of the existing Dockerfiles, and I have two humble
requests:
1. It would be good if the interesting code came from python sdist/bdists
rather than rpms.
This will make it possible to rebuild the containers using code from a
private
