Dollar Universe version 7 release and use of node Tags

[Angus Reid]

There is chat on the use of node tags to replace node names in version 7, what does this mean? It would be very useful for migrating OS levels as a node on say 2012 could then co-exist with its equivalent 2019 node of same node name but different tag on the same UVMS. i.e. node1 tag=node12012 and node1 tag=node2019

Is this correct thinking?

Also is there a date for the release of version 7?

[Eric Delawoevre]

Hi,

The tag management has to ways onto V7
* The tag management that allow the automatic Node view composition (V6 & +)
Sample: I have the habit to put a prefix to all my tags
OS_UNIX, OS_W2K12, OS_W2K16, OS_W2k19, OS_2K22
APP_MYAPP1, APP_MYAPP2 etc..
TYP_STANDALONE, TYP_CLUSTER
TEC_SAP, TEC_JEE, etc
ENV_PRD, ENV_VAL, ENV_QUA
VER_V6, VER_V7, VER_V5 (usefull for security to cloisonate the V5)


* That auto deploy (V7)
You can link a tag (like APP_MYAPP1) to a package.
When the tag is updated on the node, the package is auto deployed to the node

Reading you tag, yes it's correct, you can sort you node2012 and node2019 (equ. to my OS tag)

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Angus Reid]

Ok so what you are saying is the currently in version 6 it is possible to have 2 nodes of the same name attached onto the same UVMS?

This is done by the use of a node tag? Are you able to outline how this is done as at install there is a part about verfying a node name when registering the node to a UVMS to ensure the the node name is unique.

[Eric Delawoevre]

Oh no no no.
One Node per UVMS, this is the rule.What I explained is only regading the Node tags management 

The tag is ONLY a tag, "a variable set to a particular value", somewhat
The goal is only the sort all your nodes to your node views by using the tags
... the node keep their name, company etc..
... Also , a tag is only on the UVMS and console side, not into the Node side. The node do not understand the tag meaning.

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Eric Delawoevre]

In version 7

Their is somewhat "an abstraction" of the node and destination af the jobchain to belong to
Imagine the maintenance session, the famous session you need to have on each node to save, arrange your node in a good health.
1. put your Maintenance session into a package (with the task, etc...)
2. attach the tag "EXP_MaintenanceSess" to this package
3. That's all

On any node you set the tag "EXP_MaintenanceSess" , the package will be attomatically deployed the the node(s), whatever their name or company.
That is the new feature for V7



------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Angus Reid]

Ok  1 unique node per UVMS in v6 and by the sounds of it also v7
 
Really there is an opportunity here to allow nodes of same name but with something to distinguish to allow for parallel running, OS upgrades etc.  if even for a short period of time. A tag to further distinguish  nodes could do the trick then things like launch commands would need an optional variable to distinguish. Appreciate UVMS would need work due to nodes communicating with each other.

Thanks anyway

[Eric Delawoevre]

Indeed

But a node name is part of the node instance.... and an instance (COMPANY/NODE) is a unique key
You don't have to bother the node name really because the the name is commonly unknown from your job chains (instead of the MU)

so installing the node NODE1 and NODE2 on the same COMPANY into the same machine (so NODE1 with one baseports and NODE2 with another) is completly possible. You can put exactly the same thing into those node ... so almost identical functionnaly

Here we are talking about Tags. A tag remain its own function (role, definition), and doeas not make a sense to link all of this

You are talking OS Upgrade. Perfect, very good "opportunity" to explain here:
* your server1 OS win2k12 with DUAS 6 NODE1 COMPANY1 and your production
* future server2 OS win2k19

So :
1. Install DUAS NODE2 COMPANY1
2. copy all your job chains from NODE1 to NODE2
3. Finish with simplicity !
NODE1 and NODE2 are only a logical name
and again, no link with a the tag management

If you mandatory want to use exactly the same node name:
1. prepare another UVMS
2. install the new server2 with NODE1 name
3. Finish ! unregister the server1 NODE1 and register server2 NODE1

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------