[jira] [Resolved] (CLOUDSTACK-6903) Allow use of simulator hypervisor from client gui

2014-12-08 Thread Leo Simons (JIRA)

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

Leo Simons resolved CLOUDSTACK-6903.

Resolution: Incomplete

see reviewboard for details

> Allow use of simulator hypervisor from client gui
> -
>
> Key: CLOUDSTACK-6903
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6903
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Simulator
>Affects Versions: 4.4.0
> Environment: simulation
>Reporter: Leo Simons
>Priority: Minor
> Fix For: 4.5.0
>
>
> The simulator VM can _almost_ be used properly out of the box from the UI, 
> but it
> * doesn't show in the drop down lists to select
> * doesn't have any possible storage provisioning if you do select it
> I have a patch :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7476) centos cloudstack-usage script does not always pass along $JAVA_HOME

2014-09-04 Thread Leo Simons (JIRA)

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

Leo Simons resolved CLOUDSTACK-7476.

Resolution: Fixed

https://github.com/apache/cloudstack/pull/15

> centos cloudstack-usage script does not always pass along $JAVA_HOME
> 
>
> Key: CLOUDSTACK-7476
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7476
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Usage
>Affects Versions: 4.5.0
> Environment: secured centos/redhat
>Reporter: Leo Simons
> Fix For: 4.5.0
>
>
> /etc/init.d/cloudstack-usage finds a $JAVA_HOME and makes sure the 
> environment variable is set, then assumes this variable will be picked up by 
> JSVC.
> However, on a secured environment (selinux w/ env_reset enabled in sudoers), 
> the runuser command that is invoked by the daemon() function does not pass 
> along environment variables, so $JAVA_HOME is empty, and JSVC falls back to 
> its default behavior, which may not find java or may not find the intended 
> java.
> The simple solution is to pass -home to JSVC, passing it on the command line 
> instead of as an environment variable.
> I'll provide a patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7476) centos cloudstack-usage script does not always pass along $JAVA_HOME

2014-09-03 Thread Leo Simons (JIRA)
Leo Simons created CLOUDSTACK-7476:
--

 Summary: centos cloudstack-usage script does not always pass along 
$JAVA_HOME
 Key: CLOUDSTACK-7476
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7476
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Usage
Affects Versions: 4.5.0
 Environment: secured centos/redhat
Reporter: Leo Simons
 Fix For: 4.5.0


/etc/init.d/cloudstack-usage finds a $JAVA_HOME and makes sure the environment 
variable is set, then assumes this variable will be picked up by JSVC.

However, on a secured environment (selinux w/ env_reset enabled in sudoers), 
the runuser command that is invoked by the daemon() function does not pass 
along environment variables, so $JAVA_HOME is empty, and JSVC falls back to its 
default behavior, which may not find java or may not find the intended java.

The simple solution is to pass -home to JSVC, passing it on the command line 
instead of as an environment variable.

I'll provide a patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7143) Refactor systemvm build scripts to be easier to test

2014-07-21 Thread Leo Simons (JIRA)
Leo Simons created CLOUDSTACK-7143:
--

 Summary: Refactor systemvm build scripts to be easier to test
 Key: CLOUDSTACK-7143
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7143
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: SystemVM
Reporter: Leo Simons
 Fix For: Future


The veewee-wrapping build code could do with some love.

E-mail thread: 
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201407.mbox/%3C7A6CF878-7A28-4D4A-BCD2-0C264F8C90B7%40schubergphilis.com%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6903) Allow use of simulator hypervisor from client gui

2014-06-12 Thread Leo Simons (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029106#comment-14029106
 ] 

Leo Simons commented on CLOUDSTACK-6903:


patch @ https://reviews.apache.org/r/22511/

> Allow use of simulator hypervisor from client gui
> -
>
> Key: CLOUDSTACK-6903
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6903
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Simulator
>Affects Versions: 4.4.0
> Environment: simulation
>Reporter: Leo Simons
>Priority: Minor
> Fix For: 4.5.0
>
>
> The simulator VM can _almost_ be used properly out of the box from the UI, 
> but it
> * doesn't show in the drop down lists to select
> * doesn't have any possible storage provisioning if you do select it
> I have a patch :-)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6903) Allow use of simulator hypervisor from client gui

2014-06-12 Thread Leo Simons (JIRA)
Leo Simons created CLOUDSTACK-6903:
--

 Summary: Allow use of simulator hypervisor from client gui
 Key: CLOUDSTACK-6903
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6903
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Simulator
Affects Versions: 4.4.0
 Environment: simulation
Reporter: Leo Simons
Priority: Minor
 Fix For: 4.5.0


The simulator VM can _almost_ be used properly out of the box from the UI, but 
it
* doesn't show in the drop down lists to select
* doesn't have any possible storage provisioning if you do select it

I have a patch :-)



--
This message was sent by Atlassian JIRA
(v6.2#6252)