Closed
Bug 1111731
Opened 11 years ago
Closed 11 years ago
Deploy Onyx config change for channels to stage
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Content Services Graveyard
Tiles: Ops
Tracking
(Not tracked)
RESOLVED
FIXED
Iteration:
37.2
People
(Reporter: oyiptong, Assigned: mostlygeek)
References
()
Details
(Whiteboard: .002a)
Update onyx configuration to update tiles from a different S3 location due to the channel changes
| Reporter | ||
Comment 1•11 years ago
|
||
The most important change will be the configuration to the source of the scheduled download that happens using this script:
https://github.com/mozilla/onyx/blob/master/scripts/download_tile_index.py
The url, configured in puppet:
https://github.com/mozilla-services/puppet-config/blob/master/tiles/yaml/type/tiles.webhead.prod.yaml#L1
and
https://github.com/mozilla-services/puppet-config/blob/master/tiles/modules/tiles_webhead/manifests/app.pp#L4
needs to change to: https://tiles-origin-prod.s3.amazonaws.com/desktop_tile_index.json
I would also change:
https://github.com/mozilla-services/puppet-config/blob/master/tiles/yaml/type/tiles.webhead.yaml#L11
and
https://github.com/mozilla-services/puppet-config/blob/master/tiles/modules/tiles_webhead/manifests/app.pp#L6
and call the index file desktop_tile_index.json, so that we still have the context.
Otherwise, when we turn on fetching for other channels, it might be a bit confusing
| Assignee | ||
Updated•11 years ago
|
Summary: Deploy Onyx config change for channels → Deploy Onyx config change for channels to stage
| Assignee | ||
Comment 2•11 years ago
|
||
Changes made to onyx configurations. Waiting for new stage desktop_tile_index.json to be created before deploying this to stage.
new puppet-config version to deploy: https://github.com/mozilla-services/puppet-config/releases/tag/20141216000305-1
| Reporter | ||
Comment 3•11 years ago
|
||
Index file deployed in staging: https://tiles-stage-1-splice-s3-bucket-pzjbo6u0zcaq.s3.amazonaws.com/desktop_tile_index.json
| Assignee | ||
Comment 4•11 years ago
|
||
Onyx deployed with the configuration changes mentioned in comment #2.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•11 years ago
|
||
Fixed stage onyx deployment. Previously we were using hard coded values from the old stage AWS IAM. Now the appropriate values for the environment is passed through CloudFormation via Ansible.
| Assignee | ||
Comment 6•11 years ago
|
||
This has been updated to onyx 1.3.6.
You need to log in
before you can comment on or make changes to this bug.
Description
•