[cosmos-dev] RE: Add variable references to logical resource combination

[Jeff Hamm <Jeff.Hamm@xxxxxxx>]

Thanks Brad -- sorry it fell off my radar before the holidays.

I'm hoping to resync on the runtime today and tomorrow and start to put together a plan for 1.1 i2.

Thanks -
Jeff

-----Original Message-----
From: Beck, Bradley C [mailto:Bradley.Beck@xxxxxx] 
Sent: Monday, January 05, 2009 11:49 AM
To: Jeff Hamm; cosmos-dev@xxxxxxxxxxx
Cc: Jason Losh; Mark Mccraw; Ed Blackman; Josh Hester
Subject: RE: Add variable references to logical resource combinations in Change Analyzer

I didn't see an ER for this issue, so I added one...

https://bugs.eclipse.org/bugs/show_bug.cgi?id=259970

Bradley Beck
CA 
Sr Software Architect
Tel: +1-952-232-1720
Bradley.Beck@xxxxxx
-----Original Message-----
From: Jeff Hamm [mailto:Jeff.Hamm@xxxxxxx] 
Sent: Tuesday, December 16, 2008 8:35 AM
To: Beck, Bradley C; cosmos-dev@xxxxxxxxxxx
Cc: Jason Losh; Mark Mccraw; Ed Blackman; Josh Hester
Subject: RE: Cancelled: COSMOS Runtime Design Discussion

Thanks Brad --

I'll put a ER for the first iteration.

Jeff

-----Original Message-----
From: Beck, Bradley C [mailto:Bradley.Beck@xxxxxx] 
Sent: Monday, December 15, 2008 3:38 PM
To: cosmos-dev@xxxxxxxxxxx; Jeff Hamm
Cc: Jason Losh; Mark Mccraw; Ed Blackman; Josh Hester
Subject: RE: Cancelled: COSMOS Runtime Design Discussion

Jeff,

It looks like item (3) in section 3.5.1 (Flattening the SDD) of the
Change Analyzer Design Document addresses (at least in part) the
information you are looking for. Unfortunately, this item contains a
note that this feature was not implemented due to time constraints. This
looks like a good candidate for an Enhancement Request for the 1.1
version of the Change Analyzer.

Here's the text from the design document...

3.	[Note that due to time constraints, Change Analyzer Version One
did not implement step 3.] 
Evaluate each combination to see which variables are used within the
unique resource definitions that make up the combination. Look in the
constraints, conditions and completion element definitions that apply to
the "install" operation and arguments to the install artifact. Add a
reference to each of the variables found to the combination.
a.	When the variable is a conditioned derived variable, determine
which condition would be true for the particular combination by
comparing the resource constraints in the conditions with the resource
constraints in the combination. Treat each conditioned expression of the
derived variable as a unique variable and add a reference to the version
of the derived variable associated with the condition that evaluates to
true (and has priority if multiple conditions evaluate to true).

-Brad

Bradley Beck
CA 
Sr Software Architect
Tel: +1-952-232-1720
Bradley.Beck@xxxxxx
-----Original Message-----
From: Jeff Hamm [mailto:Jeff.Hamm@xxxxxxx] 
Sent: Monday, December 15, 2008 1:07 PM
To: cosmos-dev@xxxxxxxxxxx; Jason Losh; Beck, Bradley C; Mark Mccraw;
Josh Hester; Ed Blackman
Subject: Cancelled: COSMOS Runtime Design Discussion

All -

Cancelling today's discussion.

Brad, I still owe you some code snippits and I will follow up with
Fridays discussion later -

Thanks -
Jeff