[one-users] Is the reverse proxy of a VDC set up automatically?

[Tino Vazquez]

Hi Shi Jin,

The .httaccess file should be placed on the root of the directory
where Apache looks when an HTTP request comes. So, say you have a
server "myserver.org", and an apache installed in that server. If the
URLs we want to produce for users are of the form

"myserver.com/MyVDC"

then, if the apache conf is the default one, the .htaccess file should
be placed in /var/www.

About the file permissions, it is true that "oneadmin" should be able
to write the file. One option is to precreate the file as you said,
and change its owner to "oneadmin". I've updated the configuration
accordingly. The ozones-server should always be run as "oneadmin".

Regards,

-Tino


--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org



On Thu, Sep 22, 2011 at 11:51 PM, Shi Jin <jinzishuai at gmail.com> wrote:
> Hi Tino,
> I actually tried to run ozone-server as root and still couldn't get the
> reverse proxy to work automatically and it works if I manually add the
> reverse proxy to httpd.conf. I wonder if the documentation could provide
> more information on how reverse proxy via .htaccess is done.
> Thanks.
> Shi
>
> On Thu, Sep 22, 2011 at 2:24 PM, Shi Jin <jinzishuai at gmail.com> wrote:
>>
>> Hi Tino,
>> Thank you very much.
>> I am running CentOS instead of Ubuntu so I changed the ozones-server.conf
>> to have
>> :htaccess: /var/www/html/.htaccess
>> But this does not seem to be enough. Do we have to create this file ahead
>> of time? Also, if I am running the ozone-server as a regular user, how am I
>> supposed to control Apache2 which is run by root/www-data(on ubuntu) or
>> apache (on CentOS)?
>> Do I have to run ozone-server as root?
>> Thanks.
>> Shi
>> On Wed, Sep 21, 2011 at 4:11 AM, Tino Vazquez <tinova79 at gmail.com> wrote:
>>>
>>> Dear Shi Jin,
>>>
>>> You may want to take a look at the "Configure oZones Server" section of
>>> [1].
>>>
>>> In a nutshell, the oZones server configures the reverse proxy by
>>> rewritting the .htaccess file. The documentation is still at
>>> development state, any feedback on it would be highly appreciated.
>>>
>>> Regards,
>>>
>>> -Tino
>>>
>>> [1] http://opennebula.org/documentation:rel3.0:ozonescfg
>>>
>>> --
>>> Constantino Vázquez Blanco | dsa-research.org/tinova
>>> Virtualization Technology Engineer / Researcher
>>> OpenNebula Toolkit | opennebula.org
>>>
>>>
>>>
>>> On Thu, Sep 15, 2011 at 11:56 PM, Shi Jin <jinzishuai at gmail.com> wrote:
>>> > Hi there,
>>> > I am starting to test ONE-3.0beta2, particularly on the oZones and
>>> > VDCs.
>>> > My question is that do we have to manually set up the reverse proxy on
>>> > Apache for each VDC or this is taken care of by OpenNebula
>>> > automatically? So
>>> > far, I have found that I need to manually add to httpd.conf
>>> > ProxyPass /vdc1 http://192.168.1.52:2633/RPC2
>>> > ProxyPassReverse /vdc1 http://192.168.1.52:2633/RPC2
>>> > In order to use the http://<host>/vdc1 as the end point for the VDC.
>>> > Is this how it is supposed to be?
>>> >
>>> > Also, as the VDC admin, I don't have the permission to run "oneuser
>>> > list".
>>> > But shouldn't I be seeing myself and accounts I created under this
>>> > account?
>>> > Thanks a lot.
>>> > Shi
>>> > --
>>> > Shi Jin, Ph.D.
>>> >
>>> >
>>> > _______________________________________________
>>> > Users mailing list
>>> > Users at lists.opennebula.org
>>> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>> >
>>> >
>>
>>
>>
>> --
>> Shi Jin, Ph.D.
>>
>
>
>
> --
> Shi Jin, Ph.D.
>
>