On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote: [...] > We're also talking about making a new kind of job which can continue to > run after it's "finished" so that you could use it to do something like > host a container registry that's used by other jobs running on the > change. We don't have that feature yet, but if we did, would you prefer > to use that instead of the intermediate swift storage?
If the subsequent jobs depending on that one get nodes allocated from the same provider, that could solve a lot of the potential network performance risks as well. -- Jeremy Stanley
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
