[jbosstools-dev] Question on data virtualization runtimes and where downloadRuntime support belongs

[Ramesh Reddy]

The usecase you are going after is download the Teiid runtime based on the Designer? Or you want to download the Teiid runtime based on the EAP? If it is former, Designer has strong preferences as to which Teiid runtime it works with, but in a given major release it work more seamless. If it is later 

EAP 5.1 is used with Teiid 7.x 
EAP 6.1 Alpha, up to Teiid 8.8 
EAP 6.3 Alpha, Teiid 8.9, 8.10 

We are planning for 

EAP 6.4.Alpha for Teiid 8.11 

No WildFly support yet. If you think a marker file like in the MANIFEST.MF makes it easier, we are open to add such file. 

Ramesh.. 

----- Original Message -----

> Rob,

> Paul gave you the rundown on Teiid Designer's discovery of Teiid runtime
> versions after server start-up and that we contribute providers & actions to
> the Server View. Designer is designed to be backwards compatible (7.7 > 9.x)
> in terms of working with Teiid runtime admin and jdbc API. So in a sense,
> Designer doesn't care what Teiid runtime is installed. If it makes it easier
> on the user for server-set-up if JBT discovers/downloads/installs Teiid
> runtimes I'm in favor of it.

> Teiid Teiid
> Designer
> 7.7 7.7
> 8.0 8.2
> 8.1 8.3
> 8.2 - 8.4 8.4
> 8.5 - 8.6 8.7
> 9.0 8.8
> 9.1 8.9 (planned)
> 9.2 8.11 (planned)

> I've cc'd Ramesh Reddy on the Teiid project team and Van Halber, the DV build
> guy. They would know the version mappings between AS and Teiid runtimes.

> You are correct that Teiid 7.x was based on JBoss 5, while the 8.x stream is
> for AS7. Note also that Teiid 8.x community releases were compatible with
> EAP 6.x Alpha releases, not Final. Those are reserved for DV/Product
> releases.

> So my understanding is that the server configurations are fairly different
> between project and product.

> Barry

> ----- Original Message -----

> > From: "Max Rydahl Andersen" <manderse at redhat.com>
> 
> > To: "Rob Stryker" <rstryker at redhat.com>
> 
> > Cc: "phantomjinx" <p.g.richardson at phantomjinx.co.uk>, "jbosstools-dev
> > jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Barry Lafond"
> > <blafond at redhat.com>
> 
> > Sent: Monday, April 13, 2015 5:45:48 AM
> 
> > Subject: Re: [jbosstools-dev] Question on data virtualization runtimes and
> > where downloadRuntime support belongs
> 

> > I'm still not following/seeing why Teiid Designer needs runtime
> 
> > detection if it detects it at runtime ?
> 

> > /max
> 

> > > After some discussion with PGR, we think it makes more sense for the
> 
> > > detection to live in the Teiid Designer repository.
> 
> > >
> 
> > > Teiid Designer currently only has code for detecting teiid in
> 
> > > *running* servers, with no support for identifying a Teiid
> 
> > > installation in servers that aren't running. This makes sense for
> 
> > > their use case (server may be remote) but is not useful for runtime
> 
> > > detection at all.
> 
> > >
> 
> > > TD currently is not involved in the server creation at all, but rather
> 
> > > just adds listeners so that once a server is added, or started, they
> 
> > > can begin their configuration / build up their model. They also
> 
> > > provide editor extensions that allow setting fields on the
> 
> > > IServerWorkingCopy.
> 
> > >
> 
> > > *Barry*: One thing that would help tremendously with identifying
> 
> > > installations in non-running local servers is if I could have a map of
> 
> > > Teiid / DV releases and what underlying JBoss / Wildfly / EAP versions
> 
> > > they correspond to. What I've heard so far is that Teiid 7.x was based
> 
> > > on JBoss 5, while the 8.x stream is for AS7. It's pretty important to
> 
> > > get a full mapping of supported releases to their underlying JBoss
> 
> > > version, though. This way I can properly implement the Server Bean
> 
> > > Loaders / Runtime detection.
> 
> > >
> 
> > > One final thing to note, which I think we should bring up to the Teiid
> 
> > > runtime team directly, is that DV product properly uses the layer
> 
> > > system in JBoss 7. It has the expected
> 
> > > org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file, with the
> 
> > > expected attribute JBoss-Product-Release-Version: 6.1.0...
> 
> > >
> 
> > > But the community releases of Teiid *do not*. They simply put
> 
> > > everything in modules/system/layers/base, with no clear way of
> 
> > > identifying a version. If I wanted to look at the version here, I'd
> 
> > > need to introspect
> 
> > > teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar
> 
> > > and look at it's manifest.mf for the Bundle-Version, which so far
> 
> > > seems accurate.
> 
> > >
> 
> > > With all this in mind, it should be relatively painless (once I get
> 
> > > that version mapping from Barry) to get runtime detection +
> 
> > > downloading supported for Teiid Runtime / DV. There may be some
> 
> > > issues in stacks.yaml (since I'm not too familiar with all the bom
> 
> > > stuff) but I expect the version mapping will help me to properly pull
> 
> > > from other parts of stacks.yaml without issue.
> 
> > >
> 
> > > - Rob Stryker
> 
> > >
> 
> > > - Rob Stryker
> 

> > /max
> 
> > http://about.me/maxandersen
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150414/d7460c88/attachment.html