Migrating python.org to OSL
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough. --Noah
On Mar 18, 2013, at 03:17 PM, Noah Kantrowitz wrote:
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough.
Not that I'm aware of. As Benjamin noted, all RMs will need upload access and it would be great to get a CNAME that won't change (anything will do) since we'll need to update PEP 101 and probably the release script. -Barry
Noah Kantrowitz wrote:
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough.
The repos with public interfaces: http://svn.python.org/view/ will need to remain available to keep old links in e.g. bug reports working. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
On Mar 18, 2013, at 4:23 PM, M.-A. Lemburg wrote:
Noah Kantrowitz wrote:
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough.
The repos with public interfaces:
will need to remain available to keep old links in e.g. bug reports working.
Okay, thats just a single repo ("projects") which is the default one. The packages repo is also visible but I'm okay with breaking that given how most code has been removed in the current trunk and links are rare (thats the old home for the PyPI code and related stuffs). Are we okay with that projects repo being full read-only? --Noah
On 19.03.2013 00:27, Noah Kantrowitz wrote:
On Mar 18, 2013, at 4:23 PM, M.-A. Lemburg wrote:
Noah Kantrowitz wrote:
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough.
The repos with public interfaces:
will need to remain available to keep old links in e.g. bug reports working.
Okay, thats just a single repo ("projects") which is the default one. The packages repo is also visible but I'm okay with breaking that given how most code has been removed in the current trunk and links are rare (thats the old home for the PyPI code and related stuffs). Are we okay with that projects repo being full read-only?
Looking at the page, there are some checkins which are only a few months old, so I'm not sure whether those can be made read-only, e.g. external/ or sandbox/ Releases for older Python versions are still done from SVN, but those should be rare nowadays. It's probably better to ask on python-dev or the lists used by the projects. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 19 2013)
Python Projects, Consulting and Support ... http://www.egenix.com/ mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
Le mardi 19 mars 2013 à 08:44 +0100, M.-A. Lemburg a écrit :
On 19.03.2013 00:27, Noah Kantrowitz wrote:
On Mar 18, 2013, at 4:23 PM, M.-A. Lemburg wrote:
Noah Kantrowitz wrote:
As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough.
The repos with public interfaces:
will need to remain available to keep old links in e.g. bug reports working.
Okay, thats just a single repo ("projects") which is the default one. The packages repo is also visible but I'm okay with breaking that given how most code has been removed in the current trunk and links are rare (thats the old home for the PyPI code and related stuffs). Are we okay with that projects repo being full read-only?
Looking at the page, there are some checkins which are only a few months old, so I'm not sure whether those can be made read-only, e.g. external/ or sandbox/
external/ holds snapshots of 3rd-party libs (OpenSSL, etc.) that are used for e.g. Windows builds and doc builds. OTOH, "old links in bug reports" don't need SVN to work, they are mapped onto a conversion Web service in hg.python.org: e.g. http://hg.python.org/lookup/r12345 Regards Antoine.
participants (4)
-
Antoine Pitrou -
Barry Warsaw -
M.-A. Lemburg -
Noah Kantrowitz