Re: [openstack-dev] Sahara Job Binaries Storage

Hi Jerico, we talked about it at Summit in one of the design sessions, but afaik there is no blueprint or spec yet. I don't see why it can't happen in Newton, however. Best, Trevor On Thu, 2016-05-26 at 16:14 +1000, Jerico Revote wrote: > Hi Trevor, > > Just revisiting this, > has there

Re: [openstack-dev] Sahara Job Binaries Storage

Hi Trevor, Just revisiting this, has there been any progress to deprecate sahara jobs -> internal db mechanism? and/or the config option to disable internal db storage? Regards, Jerico > On 18 Mar 2016, at 12:55 AM, Trevor McKay wrote: > > Hi Jerico, > > Internal db

[openstack-dev] Sahara Job Binaries Storage

Hello, When deploying Sahara, Sahara docos suggests to increase max_allowed_packet to 256MB, for internal database storing of job binaries. There could be hundreds of job binaries to be uploaded/created into Sahara, which would then cause the database to grow as well. Does anyone using Sahara

Re: [openstack-dev] Sahara Job Binaries Storage

Hi Jerico, Internal db storage for job binaries was added at the start of EDP as an alternative for sites that do not have swift running. Since then, we've also added integration with manila so that job binaries can be stored in manila shares. You are correct, storing lots of binaries in the

Re: [openstack-dev] Sahara Job Binaries Storage

Hi Jerico, Internal db storage for job binaries was added at the start of EDP as an alternative for sites that do not have swift running. Since then, we've also added integration with manila so that job binaries can be stored in manila shares. You are correct, storing lots of binaries in the

Re: [openstack-dev] Sahara Job Binaries Storage

Hi Trevor, Thanks for the explanation, looking forward to that on/off option and/or internal db deprecation. Regards, Jerico > On 18 Mar 2016, at 12:55 AM, Trevor McKay wrote: > > Hi Jerico, > > Internal db storage for job binaries was added at > the start of EDP as