Open Stack

Hi Moshe! Thank you for your interest in the project. I answered your
questions below.

On Mon, Nov 7, 2016 at 3:13 PM, Elisha, Moshe (Nokia - IL) <
moshe.elisha at nokia.com> wrote:

> Hi,
>
>
>
> My name is Moshe Elisha and I work at CloudBand, Nokia.
>
> I watched "Glare - A Unified Binary Repository for OpenStack[1]" and it
> looks very nice and useful.
>
>
>
> We are considering using Glare as a standalone artifacts repository.
>
> We have two main use cases:
>
> A.     Create a custom artifact_type which basically has one archive file
> (BLOB).
>
> B.     Use "images" artifact type to store images.
>
>
>
> I have a few questions that I couldn't find the answer for and I would
> appreciate it if you could please reply:
>
>
>
> 1.      What dependencies does Glare have on other OpenStack services? Is
> it only a dependency in Keystone?
>
Glare may be a standalone service: for example for App-Catalog we use it
with custom auth middleware without Keystone. Another optional dependency
is Swift.

> 2.      I saw that there is a way to implement a "validate_upload" hook.
> Is there a support for an async validation process (in case validation
> process is long)?
>
For big files uploads we're going to implement integration with OpenStack
Mistral to have them as asynchronous tasks. Currently all uploads are
synchronous.

> 3.      Is there a way to define the "backend" used per artifact_type?
> For example, "heat_templates" will be stored on "File system" and "images"
> will be stored on "Ceph"?
>
For your particular case - yes. You may specify function
"get_default_store" for you artifact type and return desired backend. It's
highly flexible and allows to define your backend dynamically, based on
user's context, current artifact values or blob name. Unfortunately
glance_store doesn't support several backends of one type, like 3 different
cephs. I believe it will be achieved during Ocata cycle and we'll be able
to talk about true multibackendness :)

> 4.      Were there talks about a "Database" backend? Probably only
> relevant for some artifact types.
>
For doing this we will have to add new driver to glance_store and I'm 100%
sure that glance community will be against this initiative. But it's
doable: in the worst case we can get rid of glance_store library and add
all the necessary functionality right in Glare repo.

> 5.      Disregarding the "backend" used – is there anything that prevents
> Glare from running in HA active/active mode?
>
I do not see any obstacles.

> 6.      With regards to "backend" – which of the currently supported
> backends is preferable in order to achieve HA active/active mode?
>
If I understand you correctly - all, except 'file'.

> 7.      I noticed that there is a puppet-glare[2] project. Can you please
> share the status of that project?
>
Frankly speaking I don't know. Some Mirantis folks worked on it a month
ago, but now they don't. All I know - this puppet is good enough for
deploying new App-Catalog with Glare backend.

> 8.      Is there any work being done for creating RPMs for glare?
>
Afaik no. We need a volunteer from RDO community for this.

>
>
> [1] https://www.youtube.com/watch?v=uBtqdXciF4A
>
> [2] https://github.com/openstack/puppet-glare
>
> [3] https://github.com/openstack-packages
>
>
>
>
>
> Thanks!
>
>
>
>
>
> Moshe Elisha,
>
> R&D Director,
>
> CloudBand Network Director, Nokia.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161107/3782940a/attachment.html>