You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Tim Ruppert (JIRA)" <ji...@apache.org> on 2010/02/06 18:13:27 UTC
[jira] Created: (INFRA-2482) ofbiz-vm subdomains, the IPs and certs
associated with them, and updating them using buildbot
ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
---------------------------------------------------------------------------------------------
Key: INFRA-2482
URL: https://issues.apache.org/jira/browse/INFRA-2482
Project: Infrastructure
Issue Type: New Feature
Security Level: public (Regular issues)
Components: VMWare
Reporter: Tim Ruppert
Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
# We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
## As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
## demo.ofbiz.apache.org
##* This would be the current trunk and would be showing the latest and greatest features the project has to offer.
##* alternate names could be (in no particular order):
##** ofbizdemo.apache.org
##** ofbizdemo-trunk.apache.org
## demo904.ofbiz.apache.org
##* This would the current branch that we're working on. When we add another branch this would be updated to the new name.
##* alternate names could be (in no particular order):
##** 904.ofbiz.apache.org
##** ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
##** etc
# I believe that since both will be using SSL, that they will likely need separate IPs.
## This is how we do all of our setups on our staging servers.
## Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
# Buildbot updating these nightly
## Currently buildbot is doing this close to what we want on the snapshot level found here:
##* http://ci.apache.org/projects/ofbiz/snapshots/
##* http://ci.apache.org/projects/ofbiz/archive/snapshots/
## We will need to fix some of this, but let's wait until this gets resolved.
I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2482) ofbiz-vm subdomains, the IPs and
certs associated with them, and updating them using buildbot
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865516#action_12865516 ]
Gavin commented on INFRA-2482:
------------------------------
Jacques, I have reset the trunk demo to being run by the 'ofbiz' user. I have left instructions in the /home/ofbiz/README file on how to do this plus some other notes.
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2482) ofbiz-vm subdomains, the IPs and certs
associated with them, and updating them using buildbot
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-2482:
-------------------------------------
Assignee: Philip M. Gollucci
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
> Assignee: Philip M. Gollucci
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2482) ofbiz-vm subdomains, the IPs and certs
associated with them, and updating them using buildbot
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-2482.
------------------------
Assignee: (was: Philip M. Gollucci)
Resolution: Fixed
All sub-tasks complete.
one thing to note, please if you ever need to restart the demos, do so as the ofbiz user only, not root, thanks.
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2482) ofbiz-vm subdomains, the IPs and certs
associated with them, and updating them using buildbot
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ruppert updated INFRA-2482:
-------------------------------
Description:
Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
-- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
-- demo.ofbiz.apache.org
-- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
-- -- alternate names could be (in no particular order):
-- -- -- ofbizdemo.apache.org
-- -- -- ofbizdemo-trunk.apache.org
-- demo904.ofbiz.apache.org
-- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
-- -- alternate names could be (in no particular order):
-- -- -- 904.ofbiz.apache.org
-- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
-- -- etc - whatever you guys want :)
2. I believe that since both will be using SSL, that they will likely need separate IPs.
-- This is how we do all of our setups on our staging servers.
-- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
3. Buildbot updating these nightly
-- Currently buildbot is doing this close to what we want on the snapshot level found here:
-- -- http://ci.apache.org/projects/ofbiz/snapshots/
-- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
-- We will need to fix some of this, but let's wait until this gets resolved.
I think that lays it out. Subtasks below in case they're helpful.
was:
Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
# We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
## As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
## demo.ofbiz.apache.org
##* This would be the current trunk and would be showing the latest and greatest features the project has to offer.
##* alternate names could be (in no particular order):
##** ofbizdemo.apache.org
##** ofbizdemo-trunk.apache.org
## demo904.ofbiz.apache.org
##* This would the current branch that we're working on. When we add another branch this would be updated to the new name.
##* alternate names could be (in no particular order):
##** 904.ofbiz.apache.org
##** ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
##** etc
# I believe that since both will be using SSL, that they will likely need separate IPs.
## This is how we do all of our setups on our staging servers.
## Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
# Buildbot updating these nightly
## Currently buildbot is doing this close to what we want on the snapshot level found here:
##* http://ci.apache.org/projects/ofbiz/snapshots/
##* http://ci.apache.org/projects/ofbiz/archive/snapshots/
## We will need to fix some of this, but let's wait until this gets resolved.
I think that lays it out. Subtasks below in case they're helpful.
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2482) ofbiz-vm subdomains, the IPs and certs
associated with them, and updating them using buildbot
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ruppert updated INFRA-2482:
-------------------------------
Component/s: Nagios
HTTP Server
DNS
Buildbot
Description:
Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
-- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
-- demo.ofbiz.apache.org
-- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
-- -- alternate names could be (in no particular order):
-- -- -- ofbizdemo.apache.org
-- -- -- ofbizdemo-trunk.apache.org
-- demo904.ofbiz.apache.org
-- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
-- -- alternate names could be (in no particular order):
-- -- -- 904.ofbiz.apache.org
-- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
-- -- etc - whatever you guys want :)
2. I believe that since both will be using SSL, that they will likely need separate IPs.
-- This is how we do all of our setups on our staging servers.
-- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
3. We will need monitoring on these demos in case they go down.
-- We'll be happy to help bringing them back up - but being notified is most helpful.
4. Buildbot updating these nightly
-- Currently buildbot is doing this close to what we want on the snapshot level found here:
-- -- http://ci.apache.org/projects/ofbiz/snapshots/
-- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
-- We will need to fix some of this, but let's wait until this gets resolved.
I think that lays it out. Subtasks below in case they're helpful.
was:
Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
-- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
-- demo.ofbiz.apache.org
-- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
-- -- alternate names could be (in no particular order):
-- -- -- ofbizdemo.apache.org
-- -- -- ofbizdemo-trunk.apache.org
-- demo904.ofbiz.apache.org
-- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
-- -- alternate names could be (in no particular order):
-- -- -- 904.ofbiz.apache.org
-- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
-- -- etc - whatever you guys want :)
2. I believe that since both will be using SSL, that they will likely need separate IPs.
-- This is how we do all of our setups on our staging servers.
-- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
3. Buildbot updating these nightly
-- Currently buildbot is doing this close to what we want on the snapshot level found here:
-- -- http://ci.apache.org/projects/ofbiz/snapshots/
-- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
-- We will need to fix some of this, but let's wait until this gets resolved.
I think that lays it out. Subtasks below in case they're helpful.
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2482) ofbiz-vm subdomains, the IPs and
certs associated with them, and updating them using buildbot
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865578#action_12865578 ]
Jacques Le Roux commented on INFRA-2482:
----------------------------------------
Hi Gavin,
I'm not quite sure why but we have a problem with the trunk for 5 hours, stable is ok. Though it looks like running
ofbiz 13332 2.8 32.1 1950792 826436 ? Sl 02:28 14:43 java -Xms128M -Xmx1024M -XX:MaxPermSize=512m -Dofbiz.admin.port=10523 -Dofbiz.admin.key=so3du5kasd5dn -jar ofbiz.jar
Anyway now I will reload manually and update the check-svn-update.sh file
Thanks
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2482) ofbiz-vm subdomains, the IPs and
certs associated with them, and updating them using buildbot
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830875#action_12830875 ]
Tim Ruppert commented on INFRA-2482:
------------------------------------
>From Paul Querna on the infra list:
i would much prefer something like:
demo-stable.ofbiz.apache.org
demo-trunk.ofbiz.apache.org
just so we don't need to be mucking with dns every 6 months at least :-)
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2482) ofbiz-vm subdomains, the IPs and
certs associated with them, and updating them using buildbot
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865501#action_12865501 ]
Jacques Le Roux commented on INFRA-2482:
----------------------------------------
I did not know and just did it with my login, could it be an issue?
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2482) ofbiz-vm subdomains, the IPs and
certs associated with them, and updating them using buildbot
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865584#action_12865584 ]
Gavin commented on INFRA-2482:
------------------------------
you havent read the README file, your running the demo as root again, I will reset it.
> ofbiz-vm subdomains, the IPs and certs associated with them, and updating them using buildbot
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-2482
> URL: https://issues.apache.org/jira/browse/INFRA-2482
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Buildbot, DNS, HTTP Server, Nagios, VMWare
> Reporter: Tim Ruppert
>
> Currently we have a single subdomain and instance located here - ofbiz-vm.apache.org (140.211.11.41). We would like to have two OFBiz instances running on this same machine and to be appropriately named based upon the ASF guidelines. Since I don't know what that is, I'll lay it all out here:
> 1. We would like there to be two subdomains available for the trunk demo and the current branch demo (9.04)
> -- As I said previously, I'm not sure of the naming conventions, so please correct any of the ideas below.
> -- demo.ofbiz.apache.org
> -- -- This would be the current trunk and would be showing the latest and greatest features the project has to offer.
> -- -- alternate names could be (in no particular order):
> -- -- -- ofbizdemo.apache.org
> -- -- -- ofbizdemo-trunk.apache.org
> -- demo904.ofbiz.apache.org
> -- -- This would the current branch that we're working on. When we add another branch this would be updated to the new name.
> -- -- alternate names could be (in no particular order):
> -- -- -- 904.ofbiz.apache.org
> -- -- -- ofbizdemo-lastversion.ofbiz.apache.org - this one seems confusing to me.
> -- -- etc - whatever you guys want :)
> 2. I believe that since both will be using SSL, that they will likely need separate IPs.
> -- This is how we do all of our setups on our staging servers.
> -- Let us know. I'm not sure if you have a wildcard cert for apache.org, but if not, we really should get one - I'll pay for it as I have been for ofbiz.org. The rep at Thawte said that he thought this could be something they could help with as well.
> 3. We will need monitoring on these demos in case they go down.
> -- We'll be happy to help bringing them back up - but being notified is most helpful.
> 4. Buildbot updating these nightly
> -- Currently buildbot is doing this close to what we want on the snapshot level found here:
> -- -- http://ci.apache.org/projects/ofbiz/snapshots/
> -- -- http://ci.apache.org/projects/ofbiz/archive/snapshots/
> -- We will need to fix some of this, but let's wait until this gets resolved.
> I think that lays it out. Subtasks below in case they're helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.