OW2 IT Infrastructure
OW2 Technology Infrastructure
Tools and infrastructure offered to OW2 projectsdescribes the infrastructure software made available to OW2 projects. Project leaders and contributors should check this page to get information about the version of the tools, and how to use them.
Software Quality Assurance and Trustworthiness (SQuAT)In 2010, OW2 launched a series of actions to improve the perceived quality of the code which is downloaded from OW2. More details can be found on .
Java Test Compatibility Kit (TCK)OW2 open source projects are granted access to the following Java TCKs:
- JavaTM Platform, Enterprise Edition 5 (Java EE 5) Specification (JSR 244)
- JavaTM 2 Platform, Enterprise Edition 1.4 (J2EE 1.4) Specification (JSR 151)
- Java Business Integration (JBI) (JSR 208)
- JavaTM Message Service (JMS) API (JSR 914)
- JavaTM Persistence 2.0 (JSR 317),
- JAX-RS: The Java API for RESTful Web services (JSR 311),
- Java API for XML-Based Web Services (JAX-WS) 2.0 (JSR 224)
- J2EE Connector Architecture 1.5 (JSR 112) Specifications generated pursuant to the Java Community Process. Amendments to the JCP contracts for the above JSRs were signed by OW2 on January 4, 2011, granting us access for the next four years. We eventually received confirmation on April 4, 2011. Our appreciation to Lance Andersen for patiently handling and completing this long process.
Appliance Factory for OW2 ProjectsWe have negotiated a special open source community licence with UShareSoft who offers OW2 projects leaders the ability to make their software available in a package that can be easily installed in customer environments. OW2 project leaders should check .
Atlassian toolsOW2 benefits since 2009 from an open source license from Atlassian. More details about the Atlassian tools at OW2 is available on .
License analysis toolsOW2 hosts the OSLC (Open Source License Checker) project.
See the .
OSLC can be and can be easily used to analyze source code for licenses. Moreover, OW2 has been granted a login to use the Fossology platform (see also the Fossology project at ). Many thanks to the Fossology team and to Hewlett Packard for their support!
You can consult to use the OW2 Fossology access.
Please contact firstname.lastname@example.org for the associated login and password.
OW2 in the social networksOn you will find links to social networks used by OW2 members and management office.
OW2 Forge MigrationWe have started the work on the migration from GForge to NovaForge. With this migration, we will undertake a major upgrade of our technical infrastructure. The Forge migration is currently under way, and the following steps have been realised:
- Migration scripts: 01/03/10 to 18/06/10
- Sympa product integration in NovaForge: 21/06/10 to 16/07/10
- NovaForge installation to adapt to OW2 environment: 19/07/10 to 06/08/10
- Qualification and tests on OW2 platform: 06/09/10 to 30/09/10 The migration of OW2 projects will require the implementation of "Anonymous" access on NovaForge (no estimated date yet).
New hardware (Spring 2012)OW2 is upgrading its technical infrastructure to offer an heterogenous cloud computing platform. Our OW2 projects, starting with CompatibleOne, will be able to leverage this platform to demonstrate cloud interoperability. Please DO NOT PLAN ANY WORK ON OUR MACHINES THIS COMING FRIDAY JUNE 8, 2012 as you may be affected by stoppage on the OW2 infrastructure at the following time:
- UTC: 7:30am and 10:30am
- Paris: 9:30am – 12:30pm
- Beijing: 3:30pm – 6:30pm
- Sao Paulo: 4:30am – 7:30am -* San Francisco: 12:30am – 3:30am
- 10' stoppage of ow2-02 between 7:30am and 8:30am UTC
- 10' stoppage of ow2-01 between 8:00am and 10:30am UTC
- installation of ow2-04 More maintenance is planned during June with no tangible incidence on production.
New hardware (Spring 2010)Most of our applications have migrated onto the new machines on March 19 and April 2, 2010. OW2-02, the machine running the election application, the members database, the mailing lists system and the web sites was also migrated on April 13, 2010. Any question, please email mo at ow2 dot org. The new machines will be configured as follows:
- Dell PowerEdge R710
- CPU: 2 Intel Xeon 5520 (QuadCore Nehalem 2.26 Ghz)
- RAM: 16 Go DDR3
- Hard disks: SAS 4x300 Go 10 000 rpm 2.5' (hot plug)
- Disk controler: PERC 6i with RAID 5 and 6 plus write cache
- Redundant cooling fans
- Network interfaces réseaux: 4 Gigabit Ethernet ports
- Remote control iDRAC6 Enterprise Server (important)
- Redundant power supply Energy Smart (hot plug)
Web site migration completedOn Thursday, November 13, Alessandro Taurelli and Jeremy Casery have migrated the website up to the latest XWiki version. The website was down less than 50 minutes. Superb job, well done!
Chinese websiteOn Thursday, November 13, 2008, while in Europe we were migrating the site, Chinese members launched the Chinese version of the OW2 web site. Check it out at www.ow2.org.cn. Another excellent job.
2008 Infrastructure Migration CompletedThe OW2 Technology infrastructure was migrated in February 2008. More details on the technology migration page, .
Infrastructure Performance Indicators
Availability and response time for 2015-11-30
(For example, Jonas Xwiki)
The OW2 machines
On the picture below, Emmanuel Decaen of hoster Xsalto installing one of the OW2 servers.
The incident of June 24, 2008
On the week-end of June 22, the air conditioning (AC) system in the lights-out room where our machines are hosted started malfunctioning. On Monday June 23 it gradually went down and the temperature went up... Around 10pm UTM, the systems administrator had to shut down the machines.
After 10 hours, out of three AC engines, one was working, one was merely fanning air and the third on was definitely down. We managed however to retarts two servers running our major applications: forge, wiki, mailing lists.
The Xsalto team was on permanent alert. They did an outstanding job. Thank you!
The AC systems have been replaced during the week. On Monday, July 30 we could say the incident was closed.
We are setting up an alternative system to mail the community should anything major happen again. However, we have decided against having an 100% back-up system in a other data center because we evaluate that the chances an incident of this magnitude happens again is negligeable.