By vdiozguy on Dec 22, 2010
The simplest AMGH setup will have two Sun Ray servers (or potentially two Sun Ray Failover Groups, aka FOGs).
In my scenario, there is a "landing" Sun Ray server, which in fact happens to be a OVDI 3.2 host, which is, of course, Solaris x64. This host is used primarily for presenting VDI desktops (Windows and Solaris) from a couple of different pools, and there is an allowance for Solaris desktops on the server itself, only for administration purposes. Let's call this server "OVDI".
The second server in use for the AMGH group, is an OEL 5.5 host, running Sun Ray Software 5.1 for Linux (but it can be Solaris just as well.) A completely different beast from the above. Let's call this server "OELSR".
The purpose is to be able to present "Sun Ray" native Solaris, Windows and Linux desktops onto the same Sun Ray(s), which of course makes for a rocking demo.
Let's start with the work on the first server, the landing server, OVDI:
1. Create the text file DB for tokens, stock standard so that the exsiting scripts don't need customising:
2. Add a test token to the above file - if you are reading this blog entry, I'm sure you know how to get one! insert_token is the preferred vehicle as it covers registered token policies.
insert_token=Payflex.500db85200230100 username=daniel host=OELSR
3. Enable redirection on OVDI, using the stock standard demo script supplied with the software
/opt/SUNWut/sbin/utamghadm -s /opt/SUNWutref/amgh/utamghref_allkeys_script
4. Add other tokens as required. This is a demo after all.
Believe it or not, that's it for this server.
Now the second member of the RH group, OELSR:
For OELSR, The job is actually easier, since no Sun Rays should "land" on it by default, so all we want is to redirect any Sun Ray that lands on it to return to its original server when the token is pulled out of the Sun Ray.
1. Create a return script file, need to make it executable
chmod +x /opt/SUNWutref/amgh/utamghref_return
2. Edit the file and copy the code below:
3. Enable the above script as the redirection script:
/opt/SUNWut/sbin/utamghadm -s /opt/SUNWutref/amgh/utamghref_return
And that's it! Now you have two FOGs and one cool flexible platform.
This has been useful to me in the past in particular for these scenarios:
- There is a single strategy for Sun Ray server lookup (say DNS, by using sunray-servers) but multiple separate Sun Ray servers
- Upgrading customers from an older Sun Ray (or VDI for that matter) platform to a newer one, on different hardware, while keeping a backup strategy in place
- Sitting at one desk but needing instant access to multiple (very) different desktops on different infrastructure
Thanks go to Bob Doolittle and his "Getting Started with AMGH" How-to.