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 <jinzish...@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@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org