cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Clift" <f...@clift.org>
Subject Re: Review Request 25065: pre-add all RewriteRule entries to metadata htaccess file for system vm routers
Date Tue, 26 Aug 2014 20:24:48 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25065/#review51585
-----------------------------------------------------------


https://reviews.apache.org/r/25023/    and cloudstack bug 7405 https://issues.apache.org/jira/browse/CLOUDSTACK-7405
 have updated this format

I should probably submit a new patch with the new regexs

- Fred Clift


On Aug. 26, 2014, 5:07 p.m., Fred Clift wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25065/
> -----------------------------------------------------------
> 
> (Updated Aug. 26, 2014, 5:07 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> pre-add all RewriteRule entries to metadata htaccess file  for system vm routers- makes
automated router maintanince easier...  The set is static and doesn't ever change after the
initial provision - it is identical for every router... While it is probably good to have
code that can dynamically add new lines (opt/cloud/bin/vmdata.py currently does this, starting
from the stub in git now) there is no reason not to have the full static set of rules in the
initial file.  We (betterservers.com) have some in-house router-fixing scripts that would
like to re-unpack the tarball and not loose the full .htaccess file...
> 
> 
> Diffs
> -----
> 
>   systemvm/patches/debian/config/var/www/html/latest/.htaccess 038a4c9 
> 
> Diff: https://reviews.apache.org/r/25065/diff/
> 
> 
> Testing
> -------
> 
> installed cloudstack, set up networks and provisioned a vm - made sure the router got
the same .htaccess file that it would normally get after the first vm is added to the network
> 
> 
> Thanks,
> 
> Fred Clift
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message