Project

General

Profile

tickets #30316

move fontinfo to a new VM

Added by tampakrap over 2 years ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Servers hosted in NBG
Start date:
2018-01-14
Due date:
% Done:

60%

Estimated time:
Duration:

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 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)

History

#1 Updated by tampakrap over 2 years ago

  • Private changed from Yes to No

#2 Updated by tampakrap over 2 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

#3 Updated by tampakrap almost 2 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

#4 Updated by tampakrap about 1 year ago

  • Assignee deleted (tampakrap)

ticket is now up for grabs

#5 Updated by lrupp 5 months ago

  • Status changed from New to Rejected
  • % Done changed from 0 to 100

Machine / service does not exist any longer -> Closing old ticket

#6 Updated by cboltz 5 months 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.

#7 Updated by lrupp 5 months 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 ;-)

#8 Updated by lrupp 5 months ago

  • Checklist set 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

#9 Updated by cboltz 4 months ago

  • Checklist 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

#10 Updated by lrupp 4 months 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 ...

#11 Updated by lrupp 4 months ago

  • Checklist 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

#12 Updated by lrupp 4 months ago

  • Checklist set to [x] add vdb to narwals

#13 Updated by lrupp 4 months ago

  • Checklist set to [x] provide a way to update content

#14 Updated by lrupp 4 months 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).

#15 Updated by lrupp 4 months ago

  • Status changed from Workable to In Progress

#16 Updated by lrupp 4 months ago

  • Checklist set to [x] update weburls in pillar/id/narwal5

#17 Updated by lrupp 4 months 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 ;-)

#18 Updated by cboltz 4 months 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.

#19 Updated by lrupp 4 months ago

  • Checklist 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.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.

Agreed - and enhanced checklist.

#20 Updated by cboltz 4 months ago

  • Checklist 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 ;-)

Also available in: Atom PDF