cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chiradeep Vittal (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-139) Can we remove patches/systemvm/debian/config/etc/apache2/[vhostexmaple.conf, sites-available/default, sites-available/default-ssl]
Date Fri, 21 Sep 2012 22:52:07 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chiradeep Vittal closed CLOUDSTACK-139.
---------------------------------------

    Resolution: Fixed
      Assignee: Chiradeep Vittal  (was: Pradeep Soundararajan)

The files in sites-available are manipulated by  secondary storage vm since it offers SSL-based
services (ref: console-proxy//bin/scripts/config_ssl.sh). The vhostexmaple.conf is also needed
as an example to replicate on each vpc interface.
All files are derived from Apache HTTPD which is ASL
                
> Can we remove patches/systemvm/debian/config/etc/apache2/[vhostexmaple.conf, sites-available/default,
sites-available/default-ssl]
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-139
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-139
>             Project: CloudStack
>          Issue Type: Bug
>    Affects Versions: pre-4.0.0
>            Reporter: Chip Childers
>            Assignee: Chiradeep Vittal
>            Priority: Blocker
>              Labels: licensing
>             Fix For: 4.0.0
>
>
> In reviewing the contents of the patches folder, David and I are wondering if the following
files can be removed:
> patches/systemvm/debian/config/etc/apache2/sites-available/default
> patches/systemvm/debian/config/etc/apache2/vhostexmaple.conf
> patches/systemvm/debian/config/etc/apache2/sites-available/default-ssl
> If not, we need to establish the original source of these files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message