Why does cloudstack-setup-management make /root writable?

2014-05-31 Thread Yoshikazu Nojima
Hi, Does anyone know the reason why cloudstack-setup-management make /root directory mode 777 in ubuntu? https://github.com/apache/cloudstack/blob/master/python/lib/cloudutils/serviceConfig.py#L767 If no one have objection, I will remove this code. Regards, Noji

Re: Why does cloudstack-setup-management make /root writable?

2014-05-31 Thread ilya musayev
I really dont know why. I guess we can figure out who made the commit and ask for rationale on this, but i'm not aware of any reason why /root must be 777. Big security hole in my opinion. I'd say to give it a try in your env first, if your tests pass, commit. On 5/31/14, 12:06 AM, Yoshikazu

Re: [ACS44] Cherry pick CLOUDSTACK-6599

2014-05-31 Thread Daan Hoogland
now your are changing schema in java code! please don't do that. Those are for data migration. If we start 5.0 we want to be able read the sql to find the actual schema. http://stackoverflow.com/questions/972922/add-column-to-mysql-table-if-it-does-not-exist http://stackoverflow.com/questions/1438

Re: Why does cloudstack-setup-management make /root writable?

2014-05-31 Thread Milamber
A related ticket has been open in Jira https://issues.apache.org/jira/browse/CLOUDSTACK-6673 Le 31/05/2014 08:27, ilya musayev a ecrit : I really dont know why. I guess we can figure out who made the commit and ask for rationale on this, but i'm not aware of any reason why /root must be 777

[ACS4.4] Cherry-pick request for CLOUDSTACK-6816

2014-05-31 Thread Yoshikazu Nojima
Daan, Could you cherry-pick the commit 1f7167555d92bc2d5eb964e6de88a052db1388a7 to 4.4 branch? This commit is to fix the bug CLOUDSTACK-6816 . https://issues.apache.org/jira/browse/CLOUDSTACK-6816 http://apache.markmail.org/message/xtk2tcpc4nscukhn Thanks, Noji

Re: [ACS4.4] Cherry-pick request for CLOUDSTACK-6816

2014-05-31 Thread Daan Hoogland
On Sat, May 31, 2014 at 9:13 PM, Yoshikazu Nojima wrote: > 1f7167555d92bc2d5eb964e6de88a052db1388a7 is in -- Daan

[DISCUSS] old forward branches

2014-05-31 Thread Daan Hoogland
The older forward branches are still heavily used, while the release branches are open for bug fixes by all. I think people should no longer use older forward branches and maybe these should even be deleted. The release branches (except for 4.4) are open for all committers. I don't think we have or

Re: [DISCUSS] old forward branches

2014-05-31 Thread Mike Tutkowski
Seems related to this conversation: http://markmail.org/search/list:org.apache.incubator.cloudstack-*?q=%5BPROPOSAL%5D+git+workflow#query:list%3Aorg.apache.incubator.cloudstack-*%20%5BPROPOSAL%5D%20git%20workflow+page:1+mid:dawo4oannrdgpfgs+state:results On Sat, May 31, 2014 at 2:38 PM, Daan Hoo