tickets #30316
closedmove fontinfo to a new VM
Added by tampakrap over 6 years ago. Updated over 1 year ago.
100%
Description
fontinfo.o.o is currently installed locally on commnunity.o.o. It should be moved to a git repository and deployed either to static.o.o (if it is a static page) or to a new VM (if it is dynamic)
Checklist
- provide a way to update content
- update weburls in pillar/id/narwal5
- add vdb to narwals
- copy the content to /home/web_static/git/fontinfo.opensuse.org on narwal5
-
add fontinfo to
websitesin pillar/role/web_static.sls` - document in salt that fontinfo is manually updated
-
add
location = /check.txtsection in nginx to salt - add proxy section (set_real_ip_from, proxy_set_header) in nginx to salt
- Salt the deployment to all static machines (? tbd)
Updated by tampakrap over 6 years ago
- Subject changed from move fontinfo to a git repository to move fontinfo to a git repository and away from community.i.o.o
Updated by tampakrap almost 6 years ago
- Subject changed from move fontinfo to a git repository and away from community.i.o.o to move fontinfo to a new VM
- Assignee set to tampakrap
it can't be transfered to a git repository and behind static.o.o. The content is generated on community.i.o.o at the moment, which takes a lot of time. Petr Gajdos agreed to just move the service to a new VM running leap
Updated by lrupp over 4 years ago
- Status changed from New to Rejected
- % Done changed from 0 to 100
Machine / service does not exist any longer -> Closing old ticket
Updated by cboltz over 4 years ago
- Status changed from Rejected to New
Reopening - you might have got a wrong result thanks to the network issues that started yesterday, and are getting worse in the last hours (affecting everything served via anna/elsa).
fontinfo.o.o is still running on community.o.o, and still needs to be moved.
Updated by lrupp over 4 years ago
- Status changed from New to Workable
- Assignee set to lrupp
- % Done changed from 100 to 10
cboltz wrote:
fontinfo.o.o is still running on community.o.o, and still needs to be moved.
Oh, sorry. In that case let me take over. The sooner, the better ;-)
Updated by lrupp over 4 years ago
- Checklist item changed from to [ ] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd)
- % Done changed from 10 to 50
Moved manually to narwal5 at the moment. Everything seems to work as expected.
Todo: see checklist
Updated by cboltz over 4 years ago
- Checklist item changed from [ ] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd) to [ ] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd), [ ] update weburls in pillar/id/narwal5
Updated by lrupp over 4 years ago
If we put more static content on the narwal machines, I think it's a good idea to add additional storage to them as well ...
Updated by lrupp over 4 years ago
- Checklist item changed from [ ] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd), [ ] update weburls in pillar/id/narwal5 to [ ] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd), [ ] update weburls in pillar/id/narwal5, [ ] add vdb to narwals
Updated by lrupp over 4 years ago
- Checklist item changed from to [x] add vdb to narwals
Updated by lrupp over 4 years ago
- Checklist item changed from to [x] provide a way to update content
Updated by lrupp over 4 years ago
Content updated on narwal machines. As pgajdos expects not more content updates than twice a year, we decided not to setup any special sync mechanism.
The content is/should be transferred manually into the heroes network. We used my workstation as "transfer host" (via rsync) this time, which went fine and took only some minutes for the initial sync to my machine and from there to the narwal machines.
I plan to move the content to the salt master and sync from there (as normal files).
Updated by lrupp over 4 years ago
- Checklist item changed from to [x] update weburls in pillar/id/narwal5
Updated by lrupp over 4 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
Main parts done.
As the content is not planned to change often, let's close this here and be happy ;-)
Updated by cboltz over 4 years ago
- Status changed from Closed to In Progress
(reopening to ensure you see this comment, feel free to close again)
I plan to move the content to the salt master and sync from there (as normal files).
I have a better idea ;-) - move the content to /home/web_static/git/fontinfo.opensuse.org on narwal5, and add fontinfo to websites in pillar/role/web_static.sls`. With this, salt will generate the nginx config for fontinfo.o.o, and the script that already rsyncs the git-managed content to narwal* will also sync the fontinfo content.
I know that the .../git/... part in the path looks a bit out of place - using a different directory should be doable without too many changes to the sync script ;-)
As a sidenote: having it documented somewhere in salt that fontinfo is manually updated is probably a good idea.
Another sidenote: the location = /check.txt section in the nginx config looks like something we should have in salt in the web_static role for all vhosts, not only for fontinfo.
Updated by lrupp over 4 years ago
- Checklist item changed from [x] provide a way to update content, [ ] Salt the deployment to all static machines (? tbd), [x] update weburls in pillar/id/narwal5, [x] add vdb to narwals to [x] provide a way to update content, [x] update weburls in pillar/id/narwal5, [x] add vdb to narwals, [ ] move the content to `/home/web_static/git/fontinfo.opensuse.org` on narwal5, [ ] add fontinfo to `websites` in pillar/role/web_static.sls`, [ ] document in salt that fontinfo is manually updated, [ ] add `location = /check.txt` section in nginx to salt, [ ] add proxy section (set_real_ip_from, proxy_set_header) in nginx to salt, [ ] Salt the deployment to all static machines (? tbd)
- % Done changed from 100 to 60
cboltz wrote:
(reopening to ensure you see this comment, feel free to close again)
I plan to move the content to the salt master and sync from there (as normal files).
I have a better idea ;-) - move the content to
/home/web_static/git/fontinfo.opensuse.orgon narwal5, and add fontinfo towebsitesin pillar/role/web_static.sls`. With this, salt will generate the nginx config for fontinfo.o.o, and the script that already rsyncs the git-managed content to narwal* will also sync the fontinfo content.I know that the
.../git/...part in the path looks a bit out of place - using a different directory should be doable without too many changes to the sync script ;-)As a sidenote: having it documented somewhere in salt that fontinfo is manually updated is probably a good idea.
Another sidenote: the
location = /check.txtsection in the nginx config looks like something we should have in salt in theweb_staticrole for all vhosts, not only for fontinfo.
Agreed - and enhanced checklist.
Updated by cboltz over 4 years ago
- Checklist item changed from [x] provide a way to update content, [x] update weburls in pillar/id/narwal5, [x] add vdb to narwals, [ ] move the content to `/home/web_static/git/fontinfo.opensuse.org` on narwal5, [ ] add fontinfo to `websites` in pillar/role/web_static.sls`, [ ] document in salt that fontinfo is manually updated, [ ] add `location = /check.txt` section in nginx to salt, [ ] add proxy section (set_real_ip_from, proxy_set_header) in nginx to salt, [ ] Salt the deployment to all static machines (? tbd) to [x] provide a way to update content, [x] update weburls in pillar/id/narwal5, [x] add vdb to narwals, [ ] copy the content to /home/web_static/git/fontinfo.opensuse.org on narwal5, [ ] add fontinfo to `websites` in pillar/role/web_static.sls`, [ ] document in salt that fontinfo is manually updated, [ ] add `location = /check.txt` section in nginx to salt, [ ] add proxy section (set_real_ip_from, proxy_set_header) in nginx to salt, [ ] Salt the deployment to all static machines (? tbd)
Minor addition: better copy the content to /home/web_static/git/fontinfo.opensuse.org on narwal5 (checklist updated accordingly). It will be deployed to /srv/www/vhosts/fontinfo.opensuse.org by the script that also updates all the other vhosts. In theory you should get the deployment "for free" with adding fontinfo to websites in pillar/role/web_static.sls` + running highstate ;-)
Updated by lrupp over 1 year ago
- Checklist item copy the content to /home/web_static/git/fontinfo.opensuse.org on narwal5 set to Done
- Checklist item add fontinfo to `websites` in pillar/role/web_static.sls` set to Done
- Checklist item document in salt that fontinfo is manually updated set to Done
- Checklist item add `location = /check.txt` section in nginx to salt set to Done
- Checklist item add proxy section (set_real_ip_from, proxy_set_header) in nginx to salt set to Done
- Checklist item Salt the deployment to all static machines (? tbd) set to Done
Updated by lrupp over 1 year ago
- Status changed from In Progress to Closed
- % Done changed from 60 to 100