Bugzilla – Full Text Bug Listing
| Summary: | PDE requests update site space | ||
|---|---|---|---|
| Product: | Community | Reporter: | Chris Aniszczyk <caniszczyk> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | caniszczyk, denis.roy, irbull, jeffmcaffer, kim.moir, platform-releng-inbox |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Chris Aniszczyk
Jeff, as part of the PMC, you approve of this? Great idea. We have a download area for Equinox and put our incubator stuff there. Makes sense for PDE to have he same. I've created the directory(eclipse/pde) and the group(pdeadmin). Currently only Jeff and Chris are members. -M. Reopening, and adding platform releng, as they might need to exclude directories from their RSYNC. Kim & Sonia, if nothing needs to be done, feel free to close. Can I request to become a member as I would like to put my Dependency Visualization stuff there? (it is ready for early public consumption) http://www.eclipse.org/pde/incubator/dependency-visualization/index.php Should this be done through the mailing list? Interesting question, how to most projects manage their download space? By virtue of the fact that there is a special group it seems that access to the download area is somewhat restricted. Can you (webmaster) give some guidance as to who typically has access? Given the potential rsync impacts etc it may be that the space should be managed but, as a project lead, I am not sure how all this works so would not be able to say who should or should not have access. It would be great if there were some guidelines on the wiki or somewhere that could help. Jeff, I agree that some guidelines would be nice and I can appreciate the problems associated with giving everyone access to the download space. However, I think our project is in a somewhat unique position. Unlike the platform, or even the tools projects (Mylyn, GEF, etc...) where a number of developers work towards a single schedule (integration builds, milestones, releases, etc...), we have a number of developers, each working on their own schedules. To some degree, the modeling project has this problem, since many of their products have a number of individually managed components, however, they have a single release engineer who co-ordinates this. Of course we could have a standard release of the incubating tools possibly coordinated by the platform release engineering(s)? (Not sure this is the best approach for incubating components though). Maybe we should look at how the Nebula project is structured, since (I think) each component is controlled by its developer. Just to be clear, I have no problem with everyone having access but do want to make sure that everyone (including myself) understands the ramifications of putting something in the download space. I have had two requests for access to the downloads server in the past week. If we extrapolate over all the projects and components in Eclipse and everyone puts up just a bit of stuff, what would the impact on the mirrors be? how much is too much? Again, I am fine with wide access but uncomfortable with people putting stuff up and not understanding what it means. The concerns from the webmaster's chair are - that projects keep their downloads area clean by deleting stale or old files. Any project using under 2GB of disk space is of little consequence to us, however we must consider our mirror sites, which do not have terabytes of "free" storage. - that projects make the efforts so that they use the mirrors by specifying a mirrorsURL in site.xml, or by using the Find A mirror Script. Both are explained in the How Do I? page of committer tools (https://dev.eclipse.org/committers/help/howdoi.php) Denis, can you expand on the space thinking? 2GB is ok for you but not for mirrors? what is the number? also, I see that the Eclipse project is currently over its quota. Here we are talking about adding more stuff to Eclipse (PDE is part of the Eclipse TLP) and in another bug we are looking at adding more for Equinox. So does the quota get increased? Is there a way of seeing the quota/usage on a per project basis? (other than ssh and du) finally, any one who is added to the group that has write permission to the download area should be given a link to the download section on the howdoi page. (BTW, have you considered moving that to the wiki? it has some whacky formatting that makes it hard to read in FireFox) Anyway, lets get the ball rolling here. The 2GB number is arbitrary; projects should use what they need in the downloads area (emphasis on *need*). I just want to make sure that a) files in the download area are mirrored, so folks must use the mirroring system b) projects should keep the house clean to avoid wasting bandwidth/disk space everywhere Disk quotas are typically applied to the project level, and can be viewed in Committer Tools/Disk Quotas: https://dev.eclipse.org/committers/committertools/diskspace.php Note that disk quotas are not hard limits like they were before -- nothing will stop anyone from exceeding the quota. We'll simply SPAM-bomb you until you act :-) If needed, we can break the eclipse TLP into smaller chunks so that sub-projects can have different quotas (one for platform, one for PDE, one for JDT and one for equinox). ok, I understand this all now. thanks for your patience in explaining it. I don't see any reason to do the finer-grained quotas right now. Better that the projects "fly under the radar" for a while :-) Get Kim and Sonia wondering where all their disk space is going :-) Eventually I supsect we will need/want to do this but its not urgent or blocking for this request. So Jeff, how would you like to structure the download space for the PDE incubator? It is easier if just a few people have access and we co-ordinate our releases with them? Aside from the quota, we should probably have a few guidelines if we do give access to everyone. - When should old releases be removed? - What naming conventions should we use? - Does each project get its own directory or are all the releases in the same directory? - should each project have its own update site? feels like that should be up to the community. The PDE incubator workareas seem to run relatively independently so perhaps separate dirs is best? I was more concerned with the macro issues so that access and management was consistent across the projects. Regarding comment#4, we need a new rsync stanza for this directory currently there are ones called eclipseDownloads for eclipse/downloads/ eclipseEquinox eclipse/equinox/ we'll need one for the new eclipse/pde so we can pull down the content from eclipse.org to our local mirrors... Kim, can you let me know when you're ready so I can put stuff there? I think Ian will die if the plug-in visualization stuff isn't available somewhere for public consumption. clarification. Is it the case that new dirs are or are not automatically mirrored. This is part of the guidance that projects need to properly manage their download space. Kim, are you & Sonia going to be pushing the uploads for the PDE team, or are Chris & Ian going to do that themselves via SFTP/SSH/etc? My understanding is that these update sites will not be constructed as part of the build, so it would make sense for Chris and Ian to update download.eclipse.org directly. We would have to update our rsync scripts to pull a copy of the eclipse/pde directory to our local mirror. That's correct, Ian and I will be responsible for manually updating these sites which is fine. Kim's so smart :) From what I can tell, Chris, you can start putting your content up. Please read this document for some download.eclipse.org how-to's: https://dev.eclipse.org/committers/help/howdoi.php#downloads.put I'll close this as fixed as I don't think there's anything left to do. Please reopen if that's not the case. Moving all these to Servers. |