Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7057 closed New Membership Request (fixed)

debian version of your shared servers

Reported by: jean-bernard.xxxxx@… Owned by: Daniel Kahn Gillmor
Priority: Medium Component: Tech
Keywords: f2f Cc: support-team@…
Sensitive: no

Description (last modified by Jamie McClelland)

Hi! We are developping a new website in python 2.7, I just wanted to check if debian 7.0 -- python 2.7 already runs on you shared servers ? Do you have a policy for that, like 6 months after it becomes stable or similar ?

Jean-xxxxx xxxxx xxxxéxxxxx xxxxx tickets #7088

Change History (10)

comment:1 Changed 6 years ago by Dana

Cc: support-team@… added
Keywords: f2f added

Hi Jean-xxxxxx,

We don't have a policy in place, but we will discuss at our next meeting this weekend and get back to you.


comment:2 Changed 6 years ago by Daniel Kahn Gillmor

I'm happy that we'll have a discussion about this the upcoming meeting. I can fill in a little bit of background in terms of what we currently have and what has happened in the past.

  • we currently have a few servers that are directly running debian 7.0 (wheezy). I don't think any of them aren the standard shared servers (a.k.a. "moshes" for some unfathomable reason), but we are actively using wheezy elsewhere in our infrastructure.
  • if past experience is any indication, the debian upgrade rollout is likely to be done gradually and cautiously, to try to avoid breakage and incompatibility for existing installations.
  • one of the first steps of a careful rollout will probably be to create a brand new mosh that is running wheezy from the beginning, and inviting members who are willing to be guinea pigs to place new hosting orders on that server. If you think your group is willing to cope with some of the possible teething pains (and especially if you are happy to report any problems you encounter and help us actively make sure the machine is configured reasonably and working for your purposes and for other members), then you should consider being part of this early process.

comment:3 Changed 6 years ago by Ross

Owner: set to Daniel Kahn Gillmor
Status: newassigned

comment:4 Changed 6 years ago by Daniel Kahn Gillmor

Resolution: fixed
Status: assignedfeedback

We discussed this at the support-team meeting yesterday, and the generxxxxxxplan i outlined in comment:2 sounded like it had consensus. We will probably make the first wheezy mosh in the next week or two (see #7077).

Jean-xxxxxx, if your team is willing to be an experimentxxxxxxsubject, please let us know if you want that set up sooner, or if you have other concerns or plans.

comment:5 Changed 6 years ago by https://jean-xxxxxx-xxxxxx/

Resolution: fixed
Status: feedbackassigned

I have to consult my coworkers about exactly when we will need it. As it is for a new software for organization website, an experimentxxxxxxplateform is fine. We will need python-django and other debian packages. We will need some debian unpackaged python modules. Our plan is to work on debian packages for them at some point. We may also publish the code for the application in open source, we may have to make a website for the application, if it make sense. We may consider using a ticketing system at some point for the new software, even if at some point a very simple one could be included in it. For the hosting I am not sure how a big issue it is to have a dedicated python worker for this application? (It is a Django recommendation but not a need, as I understand) We had some experience with gunicorn hosting for previous projects, so we will have to adapt to Apache wsgi.

comment:6 Changed 6 years ago by Daniel Kahn Gillmor

Resolution: fixed
Status: assignedclosed

If you need unpackaged python modules, have you filed an RFP to get them packaged? debian's python-modules team is pretty decent and has a good workflow for this sort of thing.

At MF/PL, we have python-django on all of our MOSHes. We are generally fine with installing debian-packaged python modules, and have even been known to backport python modules if they aren't in the distribution we're running and our members need them. We don't need you to decide to publish your own code as free software, although as free software users and contributors we're always happy to see the ecosystem expand with new useful tools.

I'm closing this ticket now because i think all the outstanding questions have been answered. When y'all are ready to move forward with the project, please let us know, either by re-opening this ticket and re-titling it with what you need specifically, or by opening a new ticket to track the new request.

comment:7 Changed 6 years ago by https://jean-xxxxxx-xxxxxx/

Description: modified (diff)

comment:8 Changed 6 years ago by https://jean-xxxxxx-xxxxxx/

Description: modified (diff)
Summary: debian version of your shared serversDeleted

comment:9 Changed 6 years ago by Jamie McClelland

Description: modified (diff)
Summary: Deleteddebian version of your shared servers

I'm putting back the originxxxxxxdescription and title because I don't see any reason to change them (and keeping them makes it easier for us to refer back to this ticket). If you have a reason for deleting them, please note it in a comment so nobody puts it back.

I'm also following up on your question on #7319 which seems related.

comment:10 Changed 6 years ago by Jamie McClelland

After email conversation with the author, I've removed all references to the original author, but left the rest of the ticket intact.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.