hardware information screen on clients boot is blocked

Hi,

This message appear because the thin client mac address is in the root container of the control center.

If you create a container and move your thin client into it, you shouldn't see this windows again.

Ok, that's right.
But it has been hard to do this (not really intuitive, this interface), is there a doc somewhere about using ltsp-control-center ui ?

Thanks a lot

Hello,

The control center is being rewritten from scratch including this interface.
Preview of the new UI here :
https://ltsp-control01.stgraber.org/loadbalancer/overview
(drag & drop + ajax & co)

In the mean time, a good doc for this particular point is :
http://www.youtube.com/watch?v=7QdYW-NT_sw

Ben

On Fri, Feb 19, 2010 at 8:59 AM, Eric Trezel <
<email address hidden>> wrote:

> Question #101658 on ltsp-cluster changed:
> https://answers.launchpad.net/ltsp-cluster/+question/101658
>
> Status: Answered => Solved
>
> Eric Trezel confirmed that the question is solved:
> Ok, that's right.
> But it has been hard to do this (not really intuitive, this interface), is
> there a doc somewhere about using ltsp-control-center ui ?
>
> Thanks a lot
>
> --
> You received this question notification because you are a member of
> ltsp-cluster-team, which is an answer contact for ltsp-cluster.
>

--
Benoit des Ligneris Ph. D., CEO
Revolution Linux
http://www.rlnx.com/

Ok, the movie is clear !

But : I go on thinking this screen at terminal's boot is not a good thing :
I'll have to boot every terminal one time, and move them in a container before users can work on them (since mouse doesn't work with this screen). Terminals could be registered in the control-center without that.
At least, administrators should have the capacity to disable this function.

It's not a criticism, just a feed back.
Thanks to you all (ltsp team and ltsp-cluster team) for your job !

Back to this question :

When, where and/or how will it be posiible to download or update the new ui ?

Hi Eric, we applied some patches from ltsp-client-core_5.2.1 to get rid of this screen:.

1. Insert new option in ltsp postgres database :
{{{
insert into attributesdef (name,attributetype) values ('LDM_NO_CLUSTER_INFO', 1);
}}}

2. Add option in ltsp-cc web ui: `LDM_NO_CLUSTER_INFO`

3. Patch chroot /opt/ltsp/i386/usr/share/ltsp/xinitrc.d/I00-cluster and rebuild the chroot image:
{{{
--- a/opt/ltsp/i386/usr/share/ltsp/xinitrc.d/I00-cluster
+++ b/opt/ltsp/i386/usr/share/ltsp/xinitrc.d/I00-cluster
@@ -5,8 +5,10 @@ if [ -f /etc/ltsp/getltscfg-cluster.conf ]; then
         login=$(echo "username" | nc -q-1 $LDM_SERVER 8001 | awk '{print $2}')
         export LDM_USERNAME=$login
     fi
- if ! boolean_is_true "$CLUSTER_CONFIGURED" && [ -n "$(which ltsp-cluster-info)" ]; then
- export HOME=/root/
- ltsp-cluster-info
+ if ! boolean_is_true "$LDM_NO_CLUSTER_INFO" ; then
+ if ! boolean_is_true "$CLUSTER_CONFIGURED" && [ -n "$(which ltsp-cluster-info)" ]; then
+ export HOME=/root/
+ ltsp-cluster-info
+ fi
     fi
 fi
}}}

To complete action "1." from "Ronald van Engelen said on 2010-03-27"

# Start Postgres SQL shell
$ sudo su postgres
$ psql

# Add a new attribute:
insert into attributesdef (name,attributetype) values ('LDM_NO_CLUSTER_INFO', 1);

# Define the allowed values for the newly created attribute:
insert into attributesdefdict (attributesdef_id, value) values ((select currval('attributesdef_id_seq')), 'False');
insert into attributesdefdict (attributesdef_id, value) values ((select currval('attributesdef_id_seq')), 'True');

# Leave Postgres SQL shell:
\q
$ exit

Thanks for the clarification on step 1. Can someone provide some more details on step 3

Jeff, we just wrap the existing check (! boolean_is_true "$CLUSTER_CONFIGURED" && [ -n "$(which ltsp-cluster-info)" ]) in an extra check to see if our new config-parameter "$LDM_NO_CLUSTER_INFO" is set.

So, the original code:

 if ! boolean_is_true "$CLUSTER_CONFIGURED" && [ -n "$(which ltsp-cluster-info)" ]; then
   export HOME=/root/
   ltsp-cluster-info
 fi

becomes:

if ! boolean_is_true "$LDM_NO_CLUSTER_INFO" ; then
   if ! boolean_is_true "$CLUSTER_CONFIGURED" && [ -n "$(which ltsp-cluster-info)" ]; then
     export HOME=/root/
     ltsp-cluster-info
   fi
 fi

I hope this clarifies things.