So, I have FOG 0.33 running. Now I’m uploading image (because I accidentally deleted previous one). Tomorrow will test multicast - should I test something concrete regarding multicast?

[quote=“Tom Elliott, post: 21567, member: 7271”]The only issue I foresee is [B]the storage[/B] of the “2nd” interface would have to be either group and/or host related. This is because in 0.33, you can create individual multicast jobs to a host. I haven’t, yet, figured out how to kill a previously generated task and recreate a new one (while also changing the task and pxe files) to reflect the new change. The port would still work as the original task would have been used.[/QUOTE]

Are you talking about storage node? Or?

[quote=“Tom Elliott, post: 21567, member: 7271”]
I believe the issue you were initially running into was because the ports were all the same. It wouldn’t matter, as far as I can tell, if two interfaces were using the same port, which is why you had to create different ports. The same port was causing your issue, not the interface.

I Imagine that you’d only need two interfaces, or more, if you’re trying to separate different segments of the network for testing or some real major need. However, it’d be easier (and you could use the same ports, though it may confuse systems trying to communicate on that/those ports) to setup two separate server rather than trying to make your server perform all the work.
[/quote]

What do you mean by this issue? I don’t have problems with ports, just wanted to get fog running on 2 or more ifaces.

Hi, my colleague found this regarding 10 Mbit mode: h ttps://communities.intel.com/thread/11355?start=15&tstart=0

Hi Tom, yes, I can. I have no special reason to change 0.32 code, just had it installed and didn’t know how usable is 0.33. So, I try it. I’m not sure with some of your sentences, but maybe I should first take look at the changes and then I ask.
How far are you from proper release of 0.33 (I don’t know the right name, is it beta?, but hope you understand)?

Can you pleas tell me which svn link should I use? I found these 3:
[url]https://svn.mastacontrola.com/svn/freeghost[/url]/ but it says it’s revision 1
[url]https://svn.mastacontrola.com/p/freeghost/code/trunk/[/url] says revision 1117
[url]https://svn.code.sf.net/p/freeghost/code/trunk[/url] says 1118

So, small progress. I was able to change FOG to create 2 simultaneous multicast tasks with different interfaces and base ports (but didn’t test it yet). I changed FOGMulticastManager to query interface from db (added column groupInterface to groups table and updated my groups with interface) instead of from /opt/fog/service/etc/config.php. And changed /var/www/fog/commons/functions.include.php (added function getGroupsInterface( $conn, $taskName )) and /var/www/fog/management/includes/tasks.confirm.include.php (lines for getting groups interface and adding this interface to function createMulticastJob).

Just wanted to know if my initial idea would work. If somebody is interested, feel free to comment. No time today, will continue next week.

I started to explore FOG’s code and now I think I understand which parts are involved in creating multicast task. So I decided to try it. My idea is to associate groups with interfaces (probably by adding new column to table groups, called say “interface”) and then use existing code - function createMulticastJob used in /var/www/management/includes/tasks.confirm.include.php, which has now (in FOG 0.32) set parameter $eth to “null” (change this that the parameter would be set according to group’s interface). And updating /opt/fog/service/common/lib/MulticastTask.class.php accordingly.

What do you think? Do you see better/easier way? Or do you see any problems doing this? I would like to make it as simple as possible (because of time constraints) and change as little as is needed to have FOG be able to run multiple (ideally simultaneous) multicast tasks. But would like to see opinions/thoughts of anybody who is interested - to make the changes as widely usable as possible. But bear in mind that I’m not as much experienced in php and mysql and have just 1 or 2 weeks.

Does anybody see problems with simultaneous multicast session (sitting on different interfaces and perhaps different ports(?))? Or with any other part (processes) involved?

What about new FOG version (0.33)? Are there any changes in code affecting multicast tasks?

Thanks.

I would like to reopen this as I think it’s better than creating new topic (if not, feel free to move it).

As far as I understood from reading this forum, there are 2 ways for FOG supporting multiple subnets:
[LIST=1]
[]1 FOG server and allowing traffic to it from other subnets
[]1 master FOG server and several nodes per subnet
[/LIST]
Suppose I can’t go (I’m not saying that I can’t, but say I can’t) or don’t want to go either of them. So there is this 3rd way - making FOG able to work for multiple nics (virtual or physical). How much work and how hard would it be to accomplish this? I know a bit of php, mysql, shell scripting, so I would help or try to make it myself if it’s not too much of remaking of FOG. I will have maybe 1 or 2 weeks for this.

Hi,

[quote=“Tom Elliott, post: 21321, member: 7271”]
It is possible, though if you’re not wanting the clients to stop their imaging when you’ve killed the task in the FOG GUI, it wouldn’t be recommended. If you kill the udp-sender item, it will stop sending the data to the clients as I understand it, which would break all the systems being imaged at the time.
Glad to be of assistance then!
[/quote]

Yes, but, isn’t this what you imagine under “kill” button? Or maybe I don’t understand what is it intended for.

[quote=“Tom Elliott, post: 21321, member: 7271”]
FOGSTATS is usually defined in the init.gz file under bin/fog

Inside of this file, is how the FOG System actually performs the tasks. There are other fog scripts within the init.gz’s bin directory, but fog is the primary one. For 0.32, FOGSTATS is not defined except for on the Single Disk (Resizable) imaging types. I can re-take a look at the code base for MC imaging to see if FOGSTATS is set, the other part of the fog script is it needs to redirect to a file called /tmp/status.fog on the client side. This data is sent by the fog.statusreport script within the init.gz bin directory as well. However, if the file’s not obtaining any data, the progress bar will not be updated. Again, I’d have to take a look at the FOG Script to give you more detailed information.
[/quote]
OK, thanks for explanation, I somehow understand, for now it’s not so important. Does this work in FOG 0.33?

[quote=“Tom Elliott, post: 21321, member: 7271”]
Did this work?
[/quote]

Yes - in the end the problem was with our clients in classroom (MSI DC 100). When shut down they probably set their ethernet card to 10 Mbit mode. When powered on or unplugged from switch speed of deploying immediately grew to cca 100 Mbit/s. This didn’t happen with our other platform.

Thanks,

[quote=“Tom Elliott, post: 21286, member: 7271”]Try a newer kernel. My kernels don’t have modeset enabled at all so should work cross platform.[/quote]

sorry, I’m not sure if I understood: “your kernels” are those in Other Information -> Kernel Updates? I am using the latest - 3.8.8 from there. Or “your kernels” are these?:
[quote=“Tom Elliott, post: 21286, member: 7271”]1) [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url] (Also, in FOG 0.33b you can do this, by editing the PXEFileGenerator.class.php file, but you will have to update the password on the FOG Settings page.)[/quote]

[quote=“Tom Elliott, post: 21286, member: 7271”]2) Sort of. The way multicast works, it has to sync all systems to pick up the information at the right times. If you cancel the task while it’s in progress, it doesn’t know what to do anymore. So yes, it will hang and probably need to be killed.[/quote]

So to be sure - it’s not possible to write FOG the way it -KILLs (or better -TERMs) udp-sender (and other associated processes) when clicking “kill” button in FOG management (in Active Multicast Tasks)? Maybe you misunderstood me (or maybe I misunderstood you), but I’m not talking about cancelling multicast on client side but on server side.

[quote=“Tom Elliott, post: 21286, member: 7271”]3) Group Management is a means of individually adjusting a “group” of hosts. So the reason you don’t see the args in the group page is because it’s too complicated to read the information. It affects the hosts through a looping process rather than just adjusting the group and adding the information there. Trust me, it’s pretty complicated to try to add a per group recognition. Initially it’s simple, but to guess all the actions somebody wants becomes far too much to handle.[/quote]

OK, I think I understand - I thought there is a database table for groups where these (and other) settings is stored per group, but now I looked at fog database and code (/var/www/fog/management/includes/groups.edit.include.php) and now it makes sense.

[quote=“Tom Elliott, post: 21286, member: 7271”]4) I don’t know, but I don’t think it will work. FOGSTAT’s (in 0.32) isn’t set for Multicast tasks, unless you added the functionality.[/quote] Sorry, I don’t know what FOGSTAT is, but do you say it’s (the progressbar) working only for unicast?

[quote=“Tom Elliott, post: 21286, member: 7271”]5) There isn’t a speed setting for multicast on fog. This is because multicast works on UDP. Speed shouldn’t be an issue, except in multicast items have to sync to be on the same level. If two systems are really slow, it will slow the rest of them down as well. This is normal, no matter what adjustments you make.[/quote]

I think there shouldn’t be speed problems with my clients - I am imaging only two clients and unicast on these two clients went on approx 2 GB/s.

I have one other question - I set up group in FOG which contains only one host and when I tried to multicast it and looked at the traffic (using iftop) there was no multicast address and the traffic was going directly to host’s ip address. Is it OK?

I try to test it on separate switch (with only server and 2 hosts). And also other test - to make multicast session manualy starting udp-sender and udp-receivers from commandline.

Hi all, first of all, thanks authors for FOG, but I have few problems using it.

1. Is it possible to add kernel parameters to default pxe file via FOG? I thought that adding parameters to FOG_KERNEL_ARGS in Other Information -> FOG Settings is the way, but as I understood it, it adds those parameters to database and they are then used only when generating pxe files for concrete machines, not default file. I need nomodeset in default for some clients. Or am I supposed to do it manually?

2. When I kill multicast task (for whole group in Active Multicast Tasks or per machine in Active Tasks - no matter in which order) udp-sender and gzip keep hanging and I must -TERM them. Is it expected behaviour?

And now some minor problems:
3) Why don’t Kernel Arguments in Group Management persist in input box while in Host Management they do?

4. In Active Multicast Tasks, there is a progress bar which keeps on 0% while imaging. Should it work, or have I some problems in configuration?

5. And one more question (just to be sure) - I have problems with multicasting (new kernel 3.8.8 on clients, my colleague says igmp is set up on for this vlan, unicast goes well ~2GB/min), but it could be some other devices on switch which are slowing it down (I haven’t opportunity to test it on separate switch) - what I want to ask is if there isn’t some speed setting for multicast somewhere in FOG? Because I’m constantly getting 1MB/s (according to FOG graph) and when unicasting it jumps up and down around say 40 MB/s. Just to be sure

Thanks for replies.