Context Navigation

← Previous Ticket
Next Ticket →

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Requirement #814 (assigned)

Opened 17 years ago

Last modified 14 years ago

Improve install/deploy experience — at Version 6

Reported by:	jamoore	Owned by:	jmoore
Priority:	major	Milestone:	OMERO-Beta4.2
Component:	Deployment	Keywords:	n.a.
Cc:		Business Value:	n.a.
Total Story Points:	n.a.	Roif:	n.a.
Mandatory Story Points:	n.a.

Description (last modified by jmoore)

In order to more quickly provide features and bug fixes to users, the entire installation and deployment workflow should be significantly simplied. Ideally, the server would automatically detect changes to its own components or to the clients, download the changes, and silently upgrade. New client versions would be downloaded to the client machines on the next launch. In other cases, a one-click installer/upgrader would also be useful.

Various issues

Start up checks

Currently there are several situations and warnings which are only printed after start up.
These could be performed during "bin/omero admin start" or install:

check for omero.data.dir (/OMERO)
check dbpatch level
check Java version
on failure, run "bin/omero server stop"
on failure, print common things to look into

This might should be just large warnings or possibly errors to prevent startup.

See: #1037 (bin/omero db install)

References

References:

→ User Story (#2629): bin/omero admin rewrites .cfg and grid/.xml files → User Story (#6665): Virtual Machine :: additional core functionality → User Story (#6673): Virtual Machine :: Minimise download size of appliance → User Story (#6818): Virtual Machine :: Make User-facing support scripts cross platform → User Story (#2678): Virtual Machine :: Initial Development ( Keywords: VM, Hudson, Install, paris2011 ) → User Story (#3670): Strategy for OMERO updates → User Story (#6649): Rationalise the various Linux install scripts → User Story (#937): Provide distro packages for server builds ( Keywords: paris2008 ) → User Story (#6372): OMERO.VM Application → User Story (#2626): Launch clients via webstart link on OMERO.web → User Story (#1611): Implement service dependencies → User Story (#6650): Explore approaches to creating a more straightforward OS X install experience → User Story (#6811): DemoVM: Self-contained VM with GUI incorporating server & clients → User Story (#2814): Create OMERO dmg for Mac install → User Story (#2625): Auto-update server components → User Story (#3692): Allow launching heavy servers processes on the grid → User Story (#1780): Add server up/down notifier interface → User Story (#1270): Add read-only global state for server → User Story (#3160): Add automatic db upgrade hook → User Story (#1268): Add ClusterNode. or IAdmin.shutdownIn(long milliseconds) → User Story (#2132): 4.2 deployment fixes

Change History (6)

comment:1 Changed 16 years ago by jmoore

Milestone changed from 3.0-Beta3 to 3.0-Beta4
Status changed from new to assigned

Still very true, but pushing to next milestone.

comment:2 Changed 15 years ago by jmoore

Description modified (diff)
Priority changed from minor to major

comment:3 Changed 15 years ago by jmoore

Milestone changed from OMERO-Beta4 to OMERO-Beta4.1

Much of this is done, though we don't perform checks yet on startup. This will have to come in the next milestone.

comment:4 Changed 14 years ago by jmoore

Type changed from Task to Requirement

comment:5 Changed 14 years ago by jmoore

Description modified (diff)
Milestone changed from Unscheduled to OMERO-Beta4.2

comment:6 Changed 14 years ago by jmoore

Description modified (diff)

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

Download in other formats: