Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
Installation and Upgrades / Re: HowTo: add http-proxy module to zentyal 4.1
« on: August 25, 2015, 12:49:24 pm »
Thank you Julio that did the trick :-)
2
Installation and Upgrades / Re: HowTo: add http-proxy module to zentyal 4.1
« on: August 25, 2015, 12:07:54 pm »
here are the results. thanks
3
Installation and Upgrades / Re: HowTo: add http-proxy module to zentyal 4.1
« on: August 24, 2015, 01:01:45 pm »
after I activate the module I get an error "The following modules failed while saving their changes, their state is unknown: squid"
Afterwards any restarts end with the same "Failed" message saying it could not get a ticket: could not acquire credentials etc.
Afterwards any restarts end with the same "Failed" message saying it could not get a ticket: could not acquire credentials etc.
4
Installation and Upgrades / Re: HowTo: add http-proxy module to zentyal 4.1
« on: August 24, 2015, 11:20:53 am »
A recent Squid update on the server squid3-6.3 seems to have broken this module. Anybody else experiencing this and may a solution?
5
Installation and Upgrades / Re: Package libclamav-xs-perl is not available
« on: March 11, 2014, 03:26:13 pm »
I can confirm I am having the same thing. Today's update seemed to have killed our server, however after removing zentyal packages and re-installing via synaptic brought it back but no antivirus due to the above issue. Any suggestions?
6
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: November 09, 2013, 11:29:14 pm »
Hi BW
I'll be honest I havn't even had a chance to look into this since last time as just been manic at work with other bits I havn't had a chance to play with our server. This should hopefully change over the next week or so, so I should be able to look at it again soon.
I'll be honest I havn't even had a chance to look into this since last time as just been manic at work with other bits I havn't had a chance to play with our server. This should hopefully change over the next week or so, so I should be able to look at it again soon.
7
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 21, 2013, 12:00:24 am »
Oh crap it didnt twig about the changes in Neru's ltsp module, what a brain fart moment. I will try to have a look at it tomorrow. Looking at it I forgot that $fat and $arch values in the image option where replaced with just $name
I didnt do those changes to the dhcp module so when looking for the images it was looking at
"/ltsp/<% ($options{fat}?'fat-':'') %><% $options{architecture} %>"
instead of the new format. Thins needs changing as well as adding a "default image" option as you mention in the form of a drop down to select an image.
Didn't have any time today as I hoped but will try to have a look at it when I can
sorry about that :-)
I didnt do those changes to the dhcp module so when looking for the images it was looking at
"/ltsp/<% ($options{fat}?'fat-':'') %><% $options{architecture} %>"
instead of the new format. Thins needs changing as well as adding a "default image" option as you mention in the form of a drop down to select an image.
Didn't have any time today as I hoped but will try to have a look at it when I can
sorry about that :-)
8
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 19, 2013, 01:50:53 pm »
Hi
Regarding the DHCP module to avoid any confusion I just updated it to restore what was removed for 3.2 so along with Neru's updated module it just bring the standard LTSP functionality that was in 3.0. It allows us to work with 3.2 rather than having to go between 3.2 and 3.0.
I will try to get some real moding done over the weekend if I get some time and try things out.
For a small school environment I am testing it on LTSP Cluster is overkill however posted it as it might have some bits that might be useful of be able to help.
Regarding the DHCP module to avoid any confusion I just updated it to restore what was removed for 3.2 so along with Neru's updated module it just bring the standard LTSP functionality that was in 3.0. It allows us to work with 3.2 rather than having to go between 3.2 and 3.0.
I will try to get some real moding done over the weekend if I get some time and try things out.
For a small school environment I am testing it on LTSP Cluster is overkill however posted it as it might have some bits that might be useful of be able to help.
9
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 17, 2013, 10:15:18 pm »
Just got back in and read your posts and some good thoughts. Sorry to make this post a bit short but two things possibly of interest.
1. I sorted the DHCP module for 3.2 with LTSP integration so along which along with Neru's updated module works fine giving back the original Think client setup that was removed. I have attached the .deb for now (sorry it was a quick mock up so version still set as 3.2)
2. Stumbled across this yesterday it might be of some help https://www.ltsp-cluster.org/
1. I sorted the DHCP module for 3.2 with LTSP integration so along which along with Neru's updated module works fine giving back the original Think client setup that was removed. I have attached the .deb for now (sorry it was a quick mock up so version still set as 3.2)
2. Stumbled across this yesterday it might be of some help https://www.ltsp-cluster.org/
10
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 17, 2013, 12:22:20 am »
Hi BW
It great to see your still looking at the module and ways to improve it. I would like to say in advance that a combination of my work and limited knowledge of zentyal and module development I am probably not as much use as I would like to be but trying to learn as I go along, but hopefully I could help bounce ideas.
I'll start off with the next server and the small issue of recreating the profile. Would restoring a backup of the original server populate the profiles, especially when we have many different clients? Going further and possibly a realistic option may be having advanced backup options allowing you to individually select what modules you want to backup/restore. Going even further would be to have an option to specify secondary server to sync across objects/profiles
Regarding the duplicate object/client would a lookup command like in some other modules be included into the objects module to check if already exists. From what I culd see briefly the variables correspond to the group and members/clients and stord in the likes of objects/conf/ObjectTable/keys/objc$/members/keys/mmb$
As mentioned my knowladge is limited in this area however from other things in the past I would think a lookup that checks all object tables could prevent duplicates.
The downside to doing this would be that the original Object module would be compromised and no longer work as it originally did so one would loose functionality forcing one to use it in one mode or the other. Actually just a thought, one could add an option to enable "LTSP Mode" which could essentially unhash an "if exists" option or equivalent, allowing to choose without the need of resintalling the original module.
Sorry for waffling a bit hopefully you can understand what I was thinking lol.
Finally about the dhcpd.conf file I believe the template that includes the LTSP section is in the usr/share/zentyal/stubs/shared-network.mas. I suppose to identifying the keys/tables required to get the information we need.
It great to see your still looking at the module and ways to improve it. I would like to say in advance that a combination of my work and limited knowledge of zentyal and module development I am probably not as much use as I would like to be but trying to learn as I go along, but hopefully I could help bounce ideas.
I'll start off with the next server and the small issue of recreating the profile. Would restoring a backup of the original server populate the profiles, especially when we have many different clients? Going further and possibly a realistic option may be having advanced backup options allowing you to individually select what modules you want to backup/restore. Going even further would be to have an option to specify secondary server to sync across objects/profiles
Regarding the duplicate object/client would a lookup command like in some other modules be included into the objects module to check if already exists. From what I culd see briefly the variables correspond to the group and members/clients and stord in the likes of objects/conf/ObjectTable/keys/objc$/members/keys/mmb$
As mentioned my knowladge is limited in this area however from other things in the past I would think a lookup that checks all object tables could prevent duplicates.
The downside to doing this would be that the original Object module would be compromised and no longer work as it originally did so one would loose functionality forcing one to use it in one mode or the other. Actually just a thought, one could add an option to enable "LTSP Mode" which could essentially unhash an "if exists" option or equivalent, allowing to choose without the need of resintalling the original module.
Sorry for waffling a bit hopefully you can understand what I was thinking lol.
Finally about the dhcpd.conf file I believe the template that includes the LTSP section is in the usr/share/zentyal/stubs/shared-network.mas. I suppose to identifying the keys/tables required to get the information we need.
11
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 14, 2013, 05:52:58 pm »
I fully understand where your coming from and it would be nice to be able to assign a switch/ports to a specific image, especially when you are dealing with many clients.
What I posted isn't particularly elegant or convenient if many clients are involved however I think it would work as a good starting point to provide some sort of control over image assignment, and that the basic things required are there.
What I posted isn't particularly elegant or convenient if many clients are involved however I think it would work as a good starting point to provide some sort of control over image assignment, and that the basic things required are there.
12
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 14, 2013, 03:42:50 pm »
Basically assigning an image to a clients can be achieved with changes to the dhcpd.conf as described here https://cs.uwaterloo.ca/twiki/view/CF/SettingUpLTSPserver
An example would be
With the recent ltsp module in github we have an option to make multiple images under different names, we also have the option to set ltsp profile which allows to create a group/object and add clients into that group by specifying mac or ip. What I am trying to say is that we have all the info required for the additional lines:
CUSTOMIMAGE = Image name
GROUPNAME = Object Name
HOSTNAMEx = Name of client with group/hostname
MAC/IPADDRESS = Required when adding client to object/group
The profile section in the ltsp module only allows for general settings but would be good to include a "Select Image" dropdown box
As far as I can see we would just require integration of the gui front end info with the dhcpd.conf file
An example would be
Quote
group GROUPNAME
{
use-host-decl-names on;
host HOSTNAME1
{
hardware ethernet MACADDRESS;
fixed-address IPADDRESS;
}
host HOSTNAME2
{
hardware ethernet MACADDRESS;
fixed-address IPADDRESS;
}
if substring( option vendor-class-identifier , 0 , 9 ) = "PXEClient"
{
filename "/ltsp/CUSTOMIMAGE/pxelinux.0";
}
else
{
filename "/ltsp/CUSTOMIMAGE/nbi.img";
}
option root-path "/opt/ltsp/CUSTOMIMAGE/";
}
With the recent ltsp module in github we have an option to make multiple images under different names, we also have the option to set ltsp profile which allows to create a group/object and add clients into that group by specifying mac or ip. What I am trying to say is that we have all the info required for the additional lines:
CUSTOMIMAGE = Image name
GROUPNAME = Object Name
HOSTNAMEx = Name of client with group/hostname
MAC/IPADDRESS = Required when adding client to object/group
The profile section in the ltsp module only allows for general settings but would be good to include a "Select Image" dropdown box
As far as I can see we would just require integration of the gui front end info with the dhcpd.conf file
13
Installation and Upgrades / Re: Maintaining and improving the Thin Clients module
« on: October 12, 2013, 05:31:02 pm »
Thank you for the module, unfortunately the official DHCP module had LTSP integration removed, Im tinkering with reintroducing it back in.
regarding the LTSP module I would love to have a gui to assign images to specific groups. I know this can be done by editing the dhcpd.conf file but some menu gui integration would be great.
regarding the LTSP module I would love to have a gui to assign images to specific groups. I know this can be done by editing the dhcpd.conf file but some menu gui integration would be great.
14
Installation and Upgrades / Re: Error adding zentyal to a Win2003 AD
« on: October 03, 2013, 02:05:53 pm »
I have tried the patch, unfortunately the problem still persists
15
Installation and Upgrades / Re: Error adding zentyal to a Win2003 AD
« on: October 01, 2013, 03:00:38 pm »
I wont be much help as I am experiencing the same issue with the same message however on server 2008. Apart from myself there have been a few posts requesting help about this from other users, most recently http://forum.zentyal.org/index.php/topic,18247.0.html
Also looking recently it would seem the ticket has been finally accepted, hopefully it will get resolved quickly.
Also looking recently it would seem the ticket has been finally accepted, hopefully it will get resolved quickly.
Pages: [1] 2