1257882 - Please deploy add kinto-attachment configuration to Kinto Stage

Status: RESOLVED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Rémy Hubscher (:natim)]

Once Bug 1255776 is closed Kinto stage will be ready for OneCRL and AMO Blocklist.

However for Fennec OTA we would need to configure kinto-attachment with the following configuration:


kinto.includes = kinto_attachment # You may already have a kinto.includes rule
kinto.attachment.base_url =       # Stays empty
kinto.attachment.folder = {bucket_id}/{collection_id}
kinto.attachment.keep_old_files = true

kinto.attachment.aws.access_key = <AWS access key>
kinto.attachment.aws.secret_key = <AWS secret key>
kinto.attachment.aws.bucket = <bucket name>
kinto.attachment.aws.acl = <AWS ACL permissions|public-read>

Comment 1

[Rémy Hubscher (:natim)]

Sebastian I was wondering how you will get the base_url to configure Fennec with it? Should we send it by email?

I was wondering if we could consider having it in the /v1/ page in the attachment capability description so that easily have we can have the different ones with regards to deployment stack. What do you think?

Comment 2

[Sebastian Kaspari (:sebastian; :pocmo)]

(In reply to Rémy Hubscher (:natim) from comment #1)
> Sebastian I was wondering how you will get the base_url to configure Fennec
> with it? Should we send it by email?

Um, yeah, or post it in bug 1201059 and I'll update the patches. :)

> I was wondering if we could consider having it in the /v1/ page in the
> attachment capability description so that easily have we can have the
> different ones with regards to deployment stack. What do you think?

This is a nice idea! For now I'll probably still hard-code it in the code for two reasons:
* I want to avoid doing a separate request to get the URL
* One of the reasons for having it separated was that if someone tampers with the Kinto installation then it still wouldn't be possible to download files from arbitary locations.

But I think at least for documentation it would be nice to have it returned when querying the root path.

Comment 3

[Daniel Maher [:phrawzty]]

Have the issues raised in the above comments been resolved?  I'd like to move forward with this and bug 1255776 (in concert).

Comment 4

[Rémy Hubscher (:natim)]

Yes for know we will deploy and configure as explain in Comment 1 and give write the base URL in Sebastian bug.

Comment 5

[Daniel Maher [:phrawzty]]

(In reply to Rémy Hubscher (:natim) from comment #0)
> kinto.attachment.aws.access_key = <AWS access key>
> kinto.attachment.aws.secret_key = <AWS secret key>

We doesn't use shared-key access to S3 - it's all handled by IAM tokens behind the scenes - so I will not include these options (commented out).

09:07:47 <@tarek> comment them out. the lib reading them should set them to None
09:08:09 <@tarek> access_key and secret_key


(In reply to Rémy Hubscher (:natim) from comment #4)
> Yes for know we will deploy and configure as explain in Comment 1 and give
> write the base URL in Sebastian bug.

08:22:00 <@tarek> don't worry about that base url, leave it blank
08:22:18 <@tarek> sebastian will be able to recompose the full URL on the
                  client side

Comment 6

[Daniel Maher [:phrawzty]]

Kinto-attachment has deployed to Stage (see https://bugzilla.mozilla.org/show_bug.cgi?id=1255776#c10).

Comment 7

[Daniel Maher [:phrawzty]]

> kinto.attachment.aws.bucket = <bucket name>

Turns out this is actually `kinto.attachment.aws.bucket_name`, which is an easy enough fix. :)
                                                       ^^^^^

Comment 8

[Daniel Maher [:phrawzty]]

As noted in bug 1255776[0], this has been deployed. Please let me know what needs to be done in order to verify this deployment so that we can resolve this bug (and, hopefully, move in to Prod).

Thank you.


[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1255776#c11

Comment 9

[Mathieu Leplatre [:leplatrem]]

Again, as for bug 1255776 I don't how what plans Sebastian has to populate the server with initial data.

What I can suggest is to upload some files and check that they can be downloaded (that's the minimum, of course we should check S3 permissions etc.).

We made some helper scripts, that's probably the easiest path for you.
Get a Python3 venv with kinto-client:


    virtualenv env --python=python3
    source env/bin/activate
    pip install kinto-client

Download helper scripts:

    wget https://raw.githubusercontent.com/Kinto/kinto-attachment/master/scripts/download.py
    wget https://raw.githubusercontent.com/Kinto/kinto-attachment/master/scripts/upload.py


Upload some files:

    BUCKET=test-upload
    COLLECTION=test-collection
    FILES=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf /etc/issue

    python3 upload.py --gzip --server=$SERVER_URL --bucket=$BUCKET --collection=$COLLECTION --auth "token:mysecret" $FILES

Download them and see that everything is fine:

    python3 download.py --server=$SERVER_URL --bucket=$BUCKET --collection=$COLLECTION --auth "token:mysecret"


Please let me know on IRC

Comment 10

[Tarek Ziadé (:tarek)]

the attachement feature has been verified

Comment 11

[Daniel Maher [:phrawzty]]

Clearing :natim needinfo