Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Peter Amstutz
@tetron
since Arvados 2.0 it's all in /etc/arvados/config.yml
George Baxopoulos
@georgebax
Thanks. So there is now no need for the nginx config files? Because I am following the 2.1 guides and the nginx configuration parts are still there. I installed it using salt and now I am trying to install the composer, for context.
Peter Amstutz
@tetron
ah, you do still need nginx
George Baxopoulos
@georgebax
So for the composer I will still need to update the workbench's nginx configuration, but I can't find it!
Peter Amstutz
@tetron
let me see
https://doc.arvados.org/v2.1/install/install-workbench-app.html says to go to /etc/nginx/conf.d/arvados-workbench.conf you're saying that's not there?
it is possible the Salt install puts it somewhere else
@javierbertoli ?
I should also mention we don't really support the Composer any more. it still technically exists and should work but we don't have the resources to maintain it. I'm currently working on a new, lighter weight development environment for CWL workflows based on vscode
George Baxopoulos
@georgebax
The file is not there, no
Ah, I see
Peter Amstutz
@tetron
I think you want https://github.com/arvados/arvados-formula/tree/master/test/salt/pillar/examples
or https://github.com/arvados/arvados/tree/master/tools/salt-install
George Baxopoulos
@georgebax
But these don't contain the nginx conf files. I see that the contents are there for the installation, but does salt interfere with how nginx runs ?
there is a /etc/nginx/conf.d/mod-http-passenger.conf file
which says 'this file is managed by salt', but nothing else in this directory
Peter Amstutz
@tetron
https://github.com/arvados/arvados/blob/master/tools/salt-install/single_host/nginx_workbench_configuration.sls is a salt pillar which gets turned into a nginx configuration file by the nginx salt formula
George Baxopoulos
@georgebax
at runtime?
what happens after the installation?
Peter Amstutz
@tetron
no, by running salt
back up, where did you start from
George Baxopoulos
@georgebax
I started with the guide for the single host salt installation. Everything worked with no issues, salt installed it
Workbench runs as well
Peter Amstutz
@tetron
ok, great
George Baxopoulos
@georgebax
Also I installed the arvados dispatcher and a compute node, which run the sample workflow
ran*
Now I want to add the composer
Peter Amstutz
@tetron
I see
George Baxopoulos
@georgebax
But, according to its guide, I need to modify the nginx conf file. Which, as I understand, is created by salt according to the formula
Peter Amstutz
@tetron
yea. ok. so because we stopped supporting composer the salt formula doesn't include it.
but you should be able to add it
George Baxopoulos
@georgebax
Yes, I don't intend to add it using salt, I just want to follow the guide
Peter Amstutz
@tetron
yea, you need to do that in a way that doesn't conflict with salt managing the other config files. or you can just never run salt again.
George Baxopoulos
@georgebax
I am just looking for the workbench config file, which should have been at /etc/nginx/conf.d/arvados-workbench.conf according to the guide (I also can't find it doing a system wide find), so that I can edit it.
Isn't salt used just for the installation?
Peter Amstutz
@tetron
it's a configuration management system, it can be used for installation, update, rolling out configuration changes, etc
similar to puppet, ansible, etc
ok, so it looks like the nginx salt formula probably does something different from what our manually install docs say to do
George Baxopoulos
@georgebax
I understand that salt creates the configuration files (for nginx and arvados components). But where is the configuration file that it creates?
Peter Amstutz
@tetron
I'm trying to figure that out myself. the answer is probably in the nginx salt formula
Javier Bértoli
@javierbertoli
georgebax: give me a second, reading all you both discussed
George Baxopoulos
@georgebax
Ok Javier
Javier Bértoli
@javierbertoli
the salt installer uses the existing formulas for the different applications, so nginx's creates the configuration files under the default OS paths:
/etc/nginx/sites-available/*
then, enables them using links under /etc/nginx/sites-enabled/
George Baxopoulos
@georgebax
Oh, thank you very much Javier!
Javier Bértoli
@javierbertoli
which is Debian's family way of managing nginx's configuration
George Baxopoulos
@georgebax
Never figured they wouldn't have a .conf extension
Javier Bértoli
@javierbertoli
ah, right. It's not required (as any file under /etc/nginx/site-enabled/ is read in the way the nginx's formula manages the config), and I didn't realize of adding it. Perhaps it'd be good to add it, just to keep things clearer
George Baxopoulos
@georgebax
FYI, eventually composer was installed, and I added the necessary parts to the configuration. Now when I navigate to the /composer endpoint, I get a page consisting of just a Log in button, which prompts for a login and then it just gets me back to the same page with the Log in button