You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "jan iversen (JIRA)" <ji...@apache.org> on 2014/06/18 22:42:24 UTC

[jira] [Updated] (INFRA-7898) roller-vm cleanup issues.

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

jan iversen updated INFRA-7898:
-------------------------------

    Assignee:     (was: jan iversen)

> roller-vm cleanup issues.
> -------------------------
>
>                 Key: INFRA-7898
>                 URL: https://issues.apache.org/jira/browse/INFRA-7898
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: VMWare
>         Environment: ubuntu 12.04
>            Reporter: jan iversen
>            Priority: Critical
>
> Brett recently did work on roller-vm and noticed some defecits. This ticket serve the purpose of not forgetting the work that needs to be done:
> > - MySQL is still running locally, even though it's using the shared database
> Should be deinstalled.
> > - It's using the Ubuntu packaged Tomcat, which is very old (7.0.26), so it couldn't use Tomcat's current pooling configuration (copy saved in /var/lib/tomcat7/conf/Catalina/localhost/ROOT.xml.tcdbcp in case need to switch)
> We have on a couple of vms used the newest tomcat release, should we upgrade ?
> > - I couldn't find those config files in SVN or Puppet somewhere to update them
> That might be because roller-vm, was made as a copy of an old zone.
> I can see puppet is as I left it. and there are no directory trunk/machines/vms/roller-vm, anybody against that we create it ?
> Update runbook to reflect the above changes.



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