Monday Aug 10, 2009

Gran Canaria Desktop Summit Presentation: Considerations for Thin Clients in Desktop Software Design

A few months back I heard about the upcoming 2009 Gran Canaria Desktop Summit, which evolved from GUADEC and KDE community conferences, bringing them together for the first time. Because Thin Clients are outside the experience of most of the Desktop Software Development community, and yet such software is obviously of such great importance to Thin Clients, I felt it would be good to take a "Thin Client" message to the conference. The goal would be to raise awareness of Thin Clients, to convey that they're an interesting and important platform for desktop software, but that they require certain unique design considerations to be factored in. I'm not really a direct participant in the Desktop Software development community so I reached out to a friend and co-worker who is on the Gnome Foundation board, Brian Cameron, with the idea of making a joint presentation at the conference. Brian was enthusiastic, so we worked together on a preso and on July 6, 2009, we presented a talk entitled "Considerations for Thin Clients in Desktop Software Design".

This was a very unusual presentation for me. I'm used to evangelizing the products I work on. In this community, however, our message needed to be broader, in order to convey the entire market of interest. If we created the misimpression that we were only there to ask people to do things for Sun, we'd be wasting everyone's time, lose the audience, and create bad feelings in the community. It was important to stress that we were there to talk about Thin Clients in general, not just Sun Ray, and so in many ways we needed to 'sell the competition' even more strongly than our own product to create a balance. It was very peculiar to be digging up success stories from our competition :). But we want all Thin Clients to be successful in order to create a market we can compete in, since competition makes a market viable. We still believe strongly that Sun Ray is the \*best\* Thin Client in the market, and we hinted at that, but that's really a message for a different audience - potential customers rather than developers. The message for these guys was that you can do some very cool things with Thin Clients, they provide a lot of value to tons of people today, and that we should pay attention to them when designing Desktop Software.

The talk was reasonably well received I think. We had stiff competition from a talk in a parallel track which was of very broad interest to the community, so attendance was lighter than I anticipated (about 50-60 people), but most of the key leaders of the community that we wanted to reach attended.

There was a very interesting twist for us at the conference, and I'm still on the fence about whether it was net positive or negative for us. I had shipped a server and several Sun Rays to the conference, with the intention of setting up a "hacking room" where we could work together with interested developers on Thin-Client related issues. When the conference organizers saw the equipment I guess their eyes lit up, because when we arrived we were informed that the equipment had been diverted and they wanted to use it for on-site conference registration (and 'no, we don't have a back-up plan' :) ). Since we'd only run Sun Ray software over OpenSolaris with perhaps a dozen or two people, on development machines in a friendly Sun-internal environment, the idea of supporting hundreds of 'customers' for a critical function like conference registration was, shall I say, a little daunting (my fingernails may never grow back). But since our goal was to expose the community to Thin Clients it seemed like an opportunity I couldn't say 'no' to. Brian and I scrambled to get everything set up (and big thanks go out to Augustin and Miki and their legions of helpers) and I'm glad to say that over the next few days things went very smoothly, even though the 6 Sun Rays were in almost constant use. Mid-week the conference changed locations, and since registration had completed we managed to set up our "hacking room" and accomplished most of the work I'd hoped to get done. The big downside for me of this whole twist (other than stress) was that I had to support the Sun Rays (just in case anything went wrong, which didn't happen after all) and couldn't attend as many of the talks or network with as many people on-site as I'd hoped, and we didn't in the end have enough time left to accomplish all I'd hoped. The upside was exposure for the community and good will from the conference organizers, who were more willing to help us out with infrastructure issues when they arose. It was great to work and hang out with the Sun Ireland and Beijing teams, to refresh some old contacts and make new ones, and it was great to meet so many good people from the community.

The presentation we gave is here .

Tuesday Nov 06, 2007

AMGH is now supported with SRSS 4.0 Kiosk mode!

I just thought I'd send out a shout that with SRSS 4.0 (SRS 4 09/07) we have a new model for Kiosk, with AMGH fully integrated. So, there's no need any more for my utpamclient which was necessary with CAM/Kiosk mode in previous releases.

Happy AMGH'ing!

Friday Mar 09, 2007

Another AMGH update regarding usernames which can't be overridden

Due to popular demand, I just added this section to the "AMGH HOW-TO Guide":

An unsupported way to make the "username" non-overridable


Today, the username returned by the API can be overridden by the Display Manager (e.g. dtlogin's "Start Over" button).  Some customers would like this setting to be a sort of "security" feature that cannot be overridden by the user, rather than a "convenience" feature as it exists today.  In future, we may add such a feature to the product.  There is an unsupported way to deal with this today, however for non-NSCM logins.  You can edit /etc/pam.conf and remove the clearuser option from the pam_sunray_amgh.so module.  This is not officially supported because it has not been tested by our Quality Assurance team but it has been known to work for some customers. There is no similar recourse for NSCM logins today - the "Start Over" button will clear the preset login name returned by AMGH.

Sun IT's AMGH script available

I've gotten permission from our (very supportive) VP Bill Vass to post the source to the AMGH script used by Sun IT internally. I've posted that script to my "blog references" links. Hopefully with the model/object description in the "AMGH HOW-TO Guide" it should be comprehensible. Thanks, Bill!

Update to the "AMGH HOW-TO" guide

I have added a section to the guide which describes why you probably don't want to create an AMGH script using the SRDS registration database, and some tips if you should decide to do this anyway :). It appears to be a common request.
In the spirit of a proper blog (which this really isn't), here's the new text in case somebody would like to comment:


Why not write an AMGH script utilizing information in the SRDS token registration database?


Initially this may seem attractive but keep in mind that AMGH is intended to work across FOGs, so you really ought to use a single, consistent database which can be shared across FOGs and is not subject to FOG-local typos or errors. Such errors can create inconsistent and hard to diagnose behavior.

If you do go this route, do not be tempted to use the "-c" option to utuser. Although it will restrict the output only to relevant tokens it will have an undesirable performance impact since it involves the Authentication Manager (utauthd) at what can be a critical time (e.g. as a server is first coming up many Sun Rays may be connecting to utauthd simultaneously and creating sessions, all going into the greeter at once so invoking AMGH). "utuser -l" generates more output but does not involve utauthd so will actually scale better in such scenarios.

Monday Mar 06, 2006

Another update to the AMGH HowTo

More requests for info, so I've added a section to the AMGH How-To giving some technical details regarding how AMGH works, and a note about AMGH not being supported with CAM/Kiosk mode.

However, in the interests of helping folks out, I've also provided some tools and a new guide for how to get AMGH working in CAM/Kiosk mode in an unsupported way.

Friday Feb 24, 2006

Update to AMGH HOW-TO

I've made an update to my AMGH HOW-TO Guide to cover the lesser-used aspects of the API. See the section titled "Less commonly used features of the AMGH API".

Monday Nov 28, 2005

Getting Started using AMGH

I've written up this AMGH HOW-TO Guide to help people come up to speed with understanding and using this new, powerful interface available with Sun Ray Server Software 3.1. I'd love to hear reactions from folks using it (or even thinking of using it).

About

bobd

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Bookmarks