<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Hi Jake<br>
<br>
These are great questions. Forwarding to our ome-users list so everyone can benefit from the discussion.<br>
<br>
Cheers,<br>
<br>
Jason<br>
<br>
Centre for Gene Regulation & Expression | Open Microscopy Environment | University of Dundee <br>
<br>
Jake Carroll <jake.carroll@uq.edu.au> wrote:<br>
<br>
<font size="2"><span style="font-size:10pt">
<div class="PlainText">Hey OME guys. <br>
<br>
Hope you're well.<br>
<br>
We've made a little bit of progress down here, with Omero 5.0.0-beta1 now<br>
up and running on our test kit. We've witnessed OmeroFS working, in terms<br>
of preservation of path names, file structures and otherwise. We've<br>
watched a successful importation of IMS files, which is nice, too. Dan's<br>
dealing with some other formats that aren't happily importing, also.<br>
<br>
A couple of things have come up - as we intend to get this thing into<br>
production one of these days soon. I have questions:<br>
<br>
1. How far out do you see a "Stable" build of Omero5, with FS inclusive<br>
being pushed out to the public?<br>
<br>
2. I've read all the "Scaling Omero" threads - and it doesn't really<br>
resolve my concerns. I need to present Omero to a whole institute of<br>
people who are pathological nightmares in terms of imaging. I am picturing<br>
5 people all sitting there from acquisition hosts uploading 20GB+ IMS or<br>
ZVI images, all at once. Now, on a 1GbE pipe from each computer, that<br>
probably represents a few hundred megabits per second of IO,<br>
realistically. Can the OME/bioformats importer, Ice, Xmx + Java actually<br>
cope with that kind of concurrent IO in your experience?<br>
<br>
3. I want to make it a single sign on environment. Have you seen OME work<br>
successfully when tied to an organisation-wide LDAP or ActiveDirectory<br>
before?<br>
<br>
4. Backing up the OME environment. How do you do it? I like and am happy<br>
with the data structures that OmeroFS presents now, which is consistent<br>
and maintainable, but what of the "front end". If I blew up a front end<br>
host that "hosted" the OME database tomorrow, how might I rebuild it such<br>
that the data underneath can be "pointed at" to regenerate where we were?<br>
<br>
Plenty more questions to follow..<br>
<br>
<br>
--j <br>
----------<br>
Jake <span style="background-color:#ffff00">Carrol</span>l<br>
Senior Information Technology Manager Division of Research , The<br>
Queensland Brain Institute, The University of Queensland, Australia<br>
Chair, UQ Information Technology Consultative Group.<br>
E: jake.<span style="background-color:#ffff00">carrol</span>l@uq.edu.au<br>
P: +61 7 334 66407<br>
M: 0402739157<br>
<br>
<br>
</div>
</span></font><br>
<span style="font-size:10pt">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>