You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Dave Brondsema (JIRA)" <ji...@apache.org> on 2012/07/11 20:37:33 UTC
[jira] [Created] (INFRA-5039) VM for hosting Allura
Dave Brondsema created INFRA-5039:
-------------------------------------
Summary: VM for hosting Allura
Key: INFRA-5039
URL: https://issues.apache.org/jira/browse/INFRA-5039
Project: Infrastructure
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: Podling Setup
Reporter: Dave Brondsema
The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
* Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
* URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
* Outbound smtp available
* Access to Apache LDAP for authentication (probably)
* Inbound email routing
* readonly access to the Allura git repo (for code browsing, etc)
https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-5039:
-------------------------------------
Status: Waiting for Infra (was: Waiting for user)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415776#comment-13415776 ]
Gavin commented on INFRA-5039:
------------------------------
Ok Done, both should now have access and sudo , please check.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated INFRA-5039:
-------------------------
Status: Waiting for user (was: Waiting for Infra)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415986#comment-13415986 ]
#asfinfra IRC Bot commented on INFRA-5039:
------------------------------------------
<pctony> if you install any packages please let us know, so we can update our docs
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414246#comment-13414246 ]
Gavin commented on INFRA-5039:
------------------------------
I've created allura-vm.a.o , single cpu sorry, but with 60GB HD and 1GB RAM.
Next step is to puppetise it.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412955#comment-13412955 ]
Tony Stevenson commented on INFRA-5039:
---------------------------------------
Yes,
VM specs. Please.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Dave Brondsema
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415023#comment-13415023 ]
Gavin commented on INFRA-5039:
------------------------------
Ok puppetised.
I'll need asf availid list of any that will need access to the machine. And, if different, a list of those that will need sudo.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-5039:
----------------------------
Assignee: Gavin
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416547#comment-13416547 ]
Dave Brondsema edited comment on INFRA-5039 at 7/17/12 8:10 PM:
----------------------------------------------------------------
Pardon, my ignorance, but what do I have to do to login to the VM? If I run `ssh allura-vm.apache.org` I get 'Permission denied (publickey).' I'm not sure where I would put my ssh key .. I tried adding it on my account page at https://id.apache.org/ but that didn't help. Thanks
was (Author: brondsem):
Pardon, my ignorance, but what do I have to do to login to the VM? If I run `ssh allura-vm.apache.org` I get 'Permission denied (publickey).' I'm not sure where I would put my ssh key .. I tried added it on my account page at https://id.apache.org/ but that didn't help. Thanks
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415179#comment-13415179 ]
Dave Brondsema commented on INFRA-5039:
---------------------------------------
Let's start with: brondsem, rbowen
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414079#comment-13414079 ]
Dave Brondsema commented on INFRA-5039:
---------------------------------------
We'd like a minimum of 768M RAM and 20G disk space. Are multiple cores/cpus available? If so, 2 2-Ghz CPUs would be a good start. Thanks.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Dave Brondsema
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-5039.
------------------------------------
Resolution: Fixed
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated INFRA-5039:
-------------------------
Status: Waiting for user (was: Waiting for Infra)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416723#comment-13416723 ]
Gavin commented on INFRA-5039:
------------------------------
id.apache.org is the right place for ldap-aware VMs, which allura-vm is.
I cant see why it fails for you Dave, try again and give me a timestamp so I can check logs. (or jump on #asfinfra and go through it live)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411867#comment-13411867 ]
Dave Brondsema commented on INFRA-5039:
---------------------------------------
What sort of specs? Like RAM/CPU/disk usage?
We haven't discussed yet what sort of authentication we'll set up for Allura, but it seems very likely that we'd want HTTPS in any case. Lets plan on that.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Dave Brondsema
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417652#comment-13417652 ]
Dave Brondsema commented on INFRA-5039:
---------------------------------------
Turned out to be a client issue. pctony helped in #asfinfra and I'm set now.
Will follow up later regarding packages.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415984#comment-13415984 ]
#asfinfra IRC Bot commented on INFRA-5039:
------------------------------------------
<pctony> Please note that this VM is managed by puppet, and as such it will revert changes made to system files that it manages. It also configures, and sets up the PAM+LDAP, SUDO+LDAP integration and much more. It also controls iptables, and the packages that are installed.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Daniel Gruno (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416564#comment-13416564 ]
Daniel Gruno commented on INFRA-5039:
-------------------------------------
keys should be added to https://svn.apache.org/repos/infra/infrastructure/trunk/ssh_keys/people/ IIRC
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "Dave Brondsema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416547#comment-13416547 ]
Dave Brondsema commented on INFRA-5039:
---------------------------------------
Pardon, my ignorance, but what do I have to do to login to the VM? If I run `ssh allura-vm.apache.org` I get 'Permission denied (publickey).' I'm not sure where I would put my ssh key .. I tried added it on my account page at https://id.apache.org/ but that didn't help. Thanks
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-5039:
-------------------------------------
Status: Waiting for Infra (was: Waiting for user)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson updated INFRA-5039:
----------------------------------
Status: Waiting for Infra (was: Open)
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417654#comment-13417654 ]
#asfinfra IRC Bot commented on INFRA-5039:
------------------------------------------
<pctony> Wooho! Thanks.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5039) VM for hosting Allura
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated INFRA-5039:
-------------------------
Component/s: VMWare
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup, VMWare
> Reporter: Dave Brondsema
> Assignee: Gavin
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5039) VM for hosting Allura
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411833#comment-13411833 ]
#asfinfra IRC Bot commented on INFRA-5039:
------------------------------------------
<pctony> Dave, we will need more details as to the spec of the VM. Also, if you require any logins, we require that they are only taken via HTTPS, and if that is the case we will proxy HTTP[S] request to your VM from a VM managed by root@ so we can preserve integrity of the SSL cert.
> VM for hosting Allura
> ---------------------
>
> Key: INFRA-5039
> URL: https://issues.apache.org/jira/browse/INFRA-5039
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Podling Setup
> Reporter: Dave Brondsema
>
> The Allura podling would like to self-host Allura to provide ticket management, wiki, etc. I don't know what standard options for a VM are available, so here's our ideal requirements. We can be flexible.
> * Ubuntu 12.04 (or 11.10). Main packages we would install within it: solr, python, mongodb, git, httpd/mod_wsgi
> * URL to the VM at a subdomain (as opposed to a subdirectory on a shared subdomain)
> * Outbound smtp available
> * Access to Apache LDAP for authentication (probably)
> * Inbound email routing
> * readonly access to the Allura git repo (for code browsing, etc)
> https://sourceforge.net/p/allura/git/#readme describes our installation process in more detail.
> It will take us some time to get everything in this Allura instance functioning, so requests like LDAP, inbound email and access to the git repo files can be deferred & discussed in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira