latest xenia virtual server(vmware) release

[Jeremy Cothran]

Hi all,

Put out the latest server image(VMware ESXi 4.0, 2 partitioned files each at 2 Gb or less) of our main production server(data aggregation feeds, postgresql database, output products,formats,services detailed at http://code.google.com/p/xenia/wiki/VMwareInstallShort ) here at http://code.google.com/p/xenia/wiki/VMwareDownload with install instructions at http://code.google.com/p/xenia/wiki/VMwareInstallShort

This version automatically starts gathering a few sample NDBC/NOS data feeds to the database on startup and includes:

  * Dan Ramage's browser-based javascript/JSON/GIS work with Openlayers,ExtJS,GeoExt similar to http://secoora.org/maps found under /var/xenia/maps and documented some at http://code.google.com/p/xenia/wiki/InteractiveMap

  * Xiaoyan Qi's work with platform/sensor status/update webpages http://code.google.com/p/xenia/wiki/StatusPages

  

Working to see that the code on the server is also represented in the project SVN http://code.google.com/p/xenia/source/browse/#svn%2Ftrunk and documented better.

Any questions or comments about setup,use,documentation,contribution are welcome.

Thanks

Jeremy

[Jeremy Cothran]

link correction, products detailed at http://code.google.com/p/xenia/wiki/VMwareProducts

[Emilio Mayorga]

Hi Jeremy (and Xiaoyan),

Thanks for being so proactive about sharing SECOORA's advances! I
wanted to comment only on this item:

>> * Xiaoyan Qi's work with platform/sensor status/update webpages
>> http://code.google.com/p/xenia/wiki/StatusPages

That's terrific! We in NANOOS have been moving exactly in that
direction as well, though not yet as comprehensively. We implemented
into NVS an asset/platform history (status updates) logging last year
and we've integrated this information in at three relevant
views/components of NVS. Here are two samples:
A listing of the most recent entries for NVS as a whole:
http://nvs.nanoos.org/
The pop-up window for a specific asset, showing its history:
http://www.nanoos.org/nvs/nvs.php?path=NVS-Assets&infoWindow=action::auto_open||asset_class::grid||tab::details||asset_id::NAM

We've also had discussions about setting up more fine-grained status
flags and implementing both automatic and manual flagging; totally
along the lines of your "status codes". Recently I started looking
into setting up GeoRSS feeds for these asset status/history entries as
well. I'm hoping to make more progress over the next month or so.

I suspect other RA's are making progress on this issue as well. It'd
be nice to gage what sort of interest there is out there, and what
strategies others are pursuing. As we all make progress, it might even
be possible to document a minimalist, unofficial standard for status
information -- a wiki page like the one Xiaoyan has set up, but much
smaller and narrower in scope.

Other entities record and provide access to this status information.
NDBC has some, but I haven't seen a real history log. CDIP has a very
nice listing -- here's an example, "CDIP Activity Log: Station 098":
http://cdip.ucsd.edu/?nav=historic&sub=data&units=metric&tz=UTC&pub=public&map_stati=1,2,3&stn=098&stream=p1&xyrmo=201104&xitem=activity_log

Maybe something to talk about a bit at the upcoming IOOS DMAC meeting,
either officially or over beer? And I look forward to meeting you in
person!

Cheers,
-Emilio

-Emilio Mayorga, Ph.D.
Applied Physics Laboratory
University of Washington
Box 355640
Seattle, WA 98105-6698 USA
Tel: 1-206-543-6431 FAX: 1-206-543-6785
may...@apl.washington.edu

[Jeremy Cothran]

Hi Emilio and Jim,

Thanks for the feedback - the status codes we have probably are the same or overlap with other status code type lookups, especially with reference to participation in earlier/ongoing catalog efforts.  There are probably a list of common description field lookups like 'buoy deployed',etc that we could add to further simplify.  The concept of 'platform' is being extended to a 'resource' in some of the status functionality, so that a system like a hf radar array or a web service like WMS(or OPeNDAP) can also be kept track of.

Thanks for the NVS and CDIP examples, good to have existing designs to copy or borrow from.  Although when something is 'down' we can provide an email link to the operator to provide a short status,author and description - some things are so frequently up and down its difficult to corresponding manual status/reason -or- so infrequently up and down that operators aren't in the practice of supplying that minimal info to us without prodding.  So much of it comes back to us from a centralized perspective being able to sort out our assets for display or reporting purposes and letting the operators participate/correct as willing or able. 

Cheers,

Jeremy

On Wed, Apr 6, 2011 at 2:43 AM, James T. Potemra <ji...@hawaii.edu> wrote:

Emilio et al:

I agree with your comments below.  I would add that we are
attempting the same type of thing here in PacIOOS with an
additional status check on our services, i.e., we're trying to
check not only on sensor status but whether our OPeNDAP/SOS
are presently running.  If there is interest John Maurer can
give the details at the meeting later this month.

Jim

--

You received this message because you are subscribed to the Google Groups "ioos_tech" group.
To post to this group, send email to ioos...@googlegroups.com.
To unsubscribe from this group, send email to ioos_tech+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ioos_tech?hl=en.