There was a brief, unplanned outage of Tigris.Org this morning, around 05:00 Pacific time. The immediate cause was connection overload. We are further investigating the cause, to find ways to prevent recurrences.
Archive for the 'Uncategorized' Category
Brief unplanned outage, 05:00 10 October
Published October 10, 2012 Uncategorized ClosedTags: Uptime
On Friday, May 18, the normal maintenance window (17:00 Pacific time) will be extended for data center maintenance until 23:00 Pacific. No extended down-time is planned, but brief delays and interruptions are possible throughout the period.
From the hosting provider:
CollabNet regularly performs system-wide changes to maintain and upgrade common infrastructure components such as power, network, and storage. This is a message to remind you that our scheduled quarterly maintenance window is coming up on Friday May 18th.
Schedule
Start: Friday May 18th at 7:00PM Pacific
Finish: Friday May 18th at 11:00PM Pacific
Duration 4 hours
Purpose
Install upgraded firewalls to handle additional capacity.
Impact to Customers
CollabNet has a redundant network architecture and as such there should be little to no impact to customer connectivity. Customers might notice an few seconds of network latency as we failover our circuits
We apologize for any inconvenience this may cause. For more information about this maintenance window, or to report other unrelated issues, please contact CollabNet Support. The times listed are in the US/Pacific time zone and we have our list of all maintenance windows outlined here:
Google just announced their new plusone button. When people google their way to your Tigris project, a PlusOne button allows them to tell Google that your page is the best answer to the search they used—all without leaving your site.
The core Tigris page framework has been extended to load Google’s JavaScript. All you need to do is plant your plusone button wherever you think it looks best.
Loads more documentation on all this at the Google PlusOne Button web site.
Mark Phippard, one of the CollabNet team of Subversion committers, has developed some benchmarks to guide the performance improvements going into the up-coming Subversion release 1.7. Over in the CollabNet blogs:
Subversion 1.7 Performance Benchmarks CollabNet Subversion Blog.
… he’s asking for help collecting baseline data, using as many current releases, platforms, and configuration variations as possible.
It’s a pretty good packaging; your only real requirement is that you need Java and Subversion installed. If you meet those qualifications, your help would help!
Check the blog (linked above) for full details.
Tigris by the Numbers – 187k Users Strong! CollabNet Subversion Blog
Published February 25, 2011 Uncategorized ClosedHey, check out the new CollabNet blog about us!
Tigris by the Numbers – 187k Users Strong! CollabNet Subversion Blog.
CollabNet regularly performs system-wide changes to maintain and upgrade common infrastructure components such as power, network, and storage. Traditionally, CollabNet has scheduled these maintenance windows on an “as-needed” bases. This is a message to remind you that our Q1 maintenance window is Scheduled
Start: Friday February 18th at 7:00PM
Finish: Saturday February 19th at 7:00AM Duration 12 hours
Times listed are in the US/Pacific time zone and we have our yearly maintenance windows outlined here:http://www.collab.net/support/maintenance.html
Does not Include Codesion infrastructure & will affect all of our hosted instances including Tigris, Open. Collab.net,Forge.collab.net & Extranet.
If you have questions or feedback, please contact feedback@tigris.org.
Update: The CollabNet Maintenance window has been completed successfully. Your site accessibility has been restored & has been tested for login & home page access
If you have questions or feedback, please contact feedback@tigris.org.
In order to add larger and more reliable disk storage, the regularly scheduled Tigris maintenance window will be extended this Friday (February 4), for an additional hour. The system will be unavailable for approximately 90 minutes, beginning 19:00 Pacific Time.
[Update: 7 Feb] The move to the new disk farm was completed without incident, and everything seems to be functioning normally. (If you think otherwise, let us know at feedback at tigris dot org.)
Tigris was down for about half an hour, but is now back in service. We’re investigating the cause.
All right, I warned you this was a trick question. The answer is: all of the above! Every one of the projects listed (and all the write-ins too, for that matter) have good basis for claiming to be the “first” project on Tigris.Org:
ArgoUML, the leading open source UML modeling tool, sits at the top of a family of dozens of component projects, translations, and extensions. The core project was started in 1998, two years before there even was a Tigris.Org! It was already established as an open source project when it moved into Tigris.
www, a write-in, is the project where the web pages of the generic Tigris.Org site are stored. It’s created automatically by the CollabNet Enterprise Edition software that powers Tigris, and so it was the first project created within the Tigris site itself.
gef is a graph editing library that can be used to construct many, high-quality graph editing applications. This project was created within Tigris in February of 2000, making it the first still-active project created within Tigris.
Although the projects above now all use Subversion, they were all originally created using CVS. This begs a new question: what about the first project created within Tigris and also in Subversion? It wasn’t Subversion itself: Subversion boot-strapped fairly early, but it was born as a CVS project. Naturally, of course: Subversion (the software) didn’t exist at the time Subversion (the project) was being created.
But there is a project whose files were first created within Subversion (the software), and in fact within Subversion (the project), then later moved out to become its own project. Since those files were created in September of 2000, arguably this qualifies
cvs2svn as the first project created within Subversion on Tigris.Org.
But finally, what’s the first project created, as itself, using Subversion (the software), on Tigris.Org? This is a bit hard to trace down, as the early versions of import didn’t always preserve all the key information, but I believe this trophy goes to
argouml-stats, which was created on Tigris.Org, as a Subversion project, in April of 2005. (There’s that ArgoUML family again!) This project serves the build/test status for the project family as a whole, an extension of the automated build facilities.
Well, that was too easy, wasn’t it? Everyone got the right answers: Subversion, TortoiseSVN, ArgoUML, Restlet, and cvs2svn. (I skipped argouml-stats because its commits are only automated build results.)
But given the list of candidates, all you really had to do was look into each Subversion repository to find the HEAD revision. OK, hands, now: how many of you actually did that?
So how about this one: what’s the oldest project on Tigris? And I’ll give you some hints: looking at the date of Subversion revision 0 isn’t going to get you the right answer. In fact, looking into the site tables (which, by the way, you can’t do;-) doesn’t get you the result you want, either. And since I’m so sneaky, I’ve even left open your chance to nominate some project I haven’t listed—though if you do, please also provide a comment as to why you picked that project.
Let the games resume!
