Issues in Installation of Director

[FrancoCaffarraAndEsterDiBello]

1. we need to modify file install.sh r11 : apache2 missing in prerequisities
2. we need to modify cpsconf.py r130 : the file created in this directory has to be with .conf extension
3. we need add the following line to the file install.sh r24:

a2enmod wsgi

to avoid

Invalid command 'WSGIDaemonProcess', perhaps misspelled or defined by a module not included in the server configuration

if it is not a problem we can update the ready made version. We think should be great have an unique installation script to guide users, accelerate and simplify the frontend's installation! What do you think about it?

[tcrivat]

If I understand correctly, in this issue you discuss two completely different things: (1) issues in the director installation script and (2) a request for creating an automated script that guides the frontend installation.

About (1): Indeed, the director installation script should be updated the way you describe. Can you, please, commit the updated code? If not, then let me know and I will update the script myself.

About (2): In my opinion, this is a very good idea. Can you, please, add a different issue for this? (this is not related in any way with the director, so it's better to put it in a separate issue)

Thanks, Teodor

[FrancoCaffarraAndEsterDiBello]

the files are updated. Anyway I am suggesting to create script to simplify installation and configuration both director and frontend. In the director setup.sh, for example, we can insert other easy operations as the installation of the DB and other configuration, so that the user can do it quickly. I am only saying that should be great, have a script that allows the installation without read the guide.

[tcrivat]

Hi Franco, thanks for the patch (be20d2a521f232d0ca0462cc1149ce54f4a102f7).

In the case of the director, I discussed adding the database update script with @engbert and we agreed that it is a good idea to include it in the installation, however we should also make sure that we make a backup before updating the database, or else downgrading the ConPaaS version would not be possible. Is there anything else that you think it would be necessary to include in the installation script besides that (I personally cannot think of anything else).

In the case of the frontend, I agree that it would be a good idea to write a similar installation script, however this is a different issue because the frontend and the director are independent: one can install the frontend on a different machine than the director. I will add a different issue with a request for enhancement.

[FrancoCaffarraAndEsterDiBello]

Hi Teodor, I know that conpaas director and frontend are different, and that they can be on two different machine, but I think it could be great have a brief script interactive, which asks what components you want install, and in function of your input it launches the director script, the frontend script, or both the scripts. In addition, I think that it would be a good idea, to ask the configuration parameters during the installation, so that the script sets the configuration file, and not the user by hand. It could be a very interesting feature, because through this, we can simplify extremely the installation process, so that, the installation guide becomes useful only in very particular situations.

[tcrivat]

Hi,

Yes, I understand your point of view and I completely agree. The current ConPaaS installation process is cumbersome, even when following the installation guide. An interactive script that can fill-in the configuration files automatically would make the installation a lot more user-friendly.

What I wanted to point out is that this enhancement request belongs to a separate issue. It's harder to track bugs / enhancement requests etc. if more of them are present in the same issue on GitHub. Here we should be discussing only the specific missing elements from the Director installaltion (the three elements that you mentioned in your first comment on this thread), which are already fixed. Adding a new interactive script that facilitates the installation of the whole system (not just the Director) is not related to that.

Anyway, your suggestion is useful and I will open a new issue for that. Thanks!

[tcrivat]

Hi @FrancoCaffarraAndEsterDiBello,

I reverted one of your changes from commit be20d2a521f232d0ca0462cc1149ce54f4a102f7. The .conf extension should not be present for the conpaas-director sites-available configuration file, or else the conpaas-director must be enabled in apache2 with:

a2ensite conpaas-director.conf

instead of:

a2ensite conpaas-director

(which doesn't make much sense).

I also updated the documentation to reflect the correct name of the configuration file (this incorrect reference created the confusion in the first place).

[FrancoCaffarraAndEsterDiBello]

Hi @tcrivat, on what version of apache are you working? and what OS? Our test is on ubuntu server 14.04 and an apache version 2.4 . If you search on google you will probably find a lot of references to what is changed in the 2.4 version. Now it seems that the .conf extension is mandatory. Look, please, for example at this two pages:

http://httpd.apache.org/docs/2.4/upgrading.html

https://www.linode.com/docs/security/upgrading/updating-virtual-host-settings-from-apache-2-2-to-apache-2-4

[tcrivat]

Hi @FrancoCaffarraAndEsterDiBello,

I am using Apache 2.2 on Debian 6.0 (Squeeze). As far as I know, only Debian versions 6.0 (Squeeze) and 7.0 (Wheezy) are officially supported.

I wasn't aware of this change in Apache 2.4.

In this case, I think the best option would be to add back the .conf extension and enable the site with:

a2ensite conpaas-director.conf

This should work in both Apache 2.2 and 2.4. What do you think?

[FrancoCaffarraAndEsterDiBello]

Hi @tcrivat I think that this is the best choice, in this way we can get both the compatibilities.