[quote=“sudburr, post: 33646, member: 4706”]Short of installing, is there a file in the trunk that indicates the svn?[/quote]

Just to note the following command, run from withing the root of the trunk folder, will provide the version number in the system.php of the trunk contained within the folder.

[FONT=arial][COLOR=#222222]grep FOG_VERSION packages/web/commons/system.[/COLOR][/FONT][FONT=arial][COLOR=#222222]php | sed “s/^[ \t]define(.FOG_VERSION., .([0-9.]).);/FOG Version: \1/”[/COLOR][/FONT]

Until at least the coders change how they define the FOG version.

[FONT=arial][COLOR=#222222]FYI[/COLOR][/FONT]

alternately change /var/www/index.html to /var/www/index.old.html.

FOG adds the index.php to the /var/www folder but doesn’t remove the index.html. Unfortunately Apache’s default page entry looks for index.html before it looks for index.php. If index.html (the “It works!” page) exists it shows that regardless if the index.php (the fog redirector) exists or not. renaming it causes the index.php to be shown and for the redirection to happen properly.

Stephen.

Hey,

I found a problem with assigning AD Information to a group in 0.31. the account will not properly add the slash to the Domain Username (e.g. domain\user gets auto entered as domainuser).

To fix this:
edit line 615 of /var/www/fog/management/includes/group.edit.include.php
change getSetting($conn, “FOG_AD_DEFAULT_USER”)
to addslashes(getSetting($conn, “FOG_AD_DEFAULT_USER”))

Note: I know this is fixed in 0.32. However, I am currently required to use FOG 0.31 as I may need to apply the location patch (which is currently 0.31 only) in the future.

Update on the Portable Storage Nodes.

We now have 3 laptops configured as storage nodes across 15 location.

There is however an issue I have encountered with the web interface’s Dashboard on the Home page. What seems to be happening is that the dashboard is trying to gather information the 18 storage nodes (multiple entries for each laptop) that FOG has in it’s database but mostly not connected. This is causing navigation away from the Home page to stall while the information gathering completes/fails. It will get to the other pages but it takes it’s time. All other page changes in the web interface appear run as quickly as with only the master node in place.

With 18 storage nodes defined and a max 4 servers connected at any one point, getting away from the Home page can take up to a minute.

It’s something to look into if the Location patch is going to be integrated into the full version eventually.

FYI

Stephen

[quote=“PatinMT, post: 3976, member: 913”]Thanks for the update Stephen…interested to try it out.

Wondering where to start looking for my issue with this.

Right now I’m working at one of the “remote locations” (it’s summer vacation for the schools). I’ve uploaded a new image from a machine, but what I am finding is that the Upload process is pushing the image files over to the “main location”, however when I try to pull it down to another client with a “deploy”, the target client is looking for it here in the remote location.

In both cases, the hosts are configured to be at the “remote location”, but the image upload is not saving to the remote storage node. I can copy it easy enough, but I would like to save as much time as possible.

Is this by design? Or did I miss a step?

Thanks, Pat[/quote]

Hey Pat,

Because of how the Location patch is coded uploaded images get pushed back to the main storage node. This is because of the Image Replicator service.

As far as I can tell* an image that is added to a secondary storage node is not uploaded back to the master storage node. Transfers are downwards only. So the image needs to be uploaded to the master storage node so that it can then be redistributed throughout the storage group.
[INDENT=1]* I only took a quick look at that part of the code so I may be misinterpreting this.[/INDENT]

You can find the code in /var/www/fog/service/Pre_Stage1.php for this function.

Stephen.

Hey all,

Just wanted to update you. The portable FOG storage nodes work well. They have been tested at 3 remote sites imaging concurrently. All went relatively well. No major hitches.

My next issue is the [URL=‘http://fogproject.org/forum/threads/fog-multi-site-multicast.796/’]Multicast from storage nodes[/URL] for which I have opened a new thread.

Stephen.

Hey all,

I have been using FOG 0.31 with the [URL=‘http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/’]multi-site setup[/URL] modified to allow mobile laptop storage nodes for a couple weeks now. This has worked great so far with three remote sites done concurrently over two days (a logistics issue not a FOG problem).

One feature I would really like, however, is the ability to multicast from the storage nodes. Currently the code causes all multicasts to be initiated from the master node. This occurs in spite of the Location Patch. With multicast broadcast disabled between subnets this means that we cannot multicast at remote locations, only unicast*.

*Which is not really broadcasting btw. It’s just connecting to the images folder as a nfs share on the storage node.

Does anyone know if there is an easy way (i.e. not recoding the whole project) of getting this working? I’ve poked around in the code some and am just hoping it is something relatively simple.

Stephen.

Here’s what I’m doing for Portable Storage Nodes.
[INDENT=1]Install a standard storage node on the laptop. (assume you set the ip address as 192.168.1.2 during setup)[/INDENT]
[INDENT=1]Edit the /var/www/fog/commons/config.php[/INDENT]
[INDENT=1]Replace all “192.168.1.2” entries with getenv(“SERVER_ADDR”)[/INDENT]
[INDENT=1]Register a static DHCP Reservation for each site the laptop will be at.[/INDENT]
[INDENT=1]Enter a storage node entry in the managment console for each location that the laptop will be at using the static reservation set.[/INDENT]

This basically tricks the storage node to use it’s current ip address from the config.php rather than a static IP address. The storage node entries can then be set different locations and the laptop server will only be “on location” when it gets the proper IP address for the subnet it’s on.

I’ve not tested this yet but there is no reason it shouldn’t work.

You can then “Disable” the Primary Storage Node by simply not assigning it a location. If you have not installed the Multi-Location PXE server and group all nodes in the same Storage Group you should be able to even have images automatically push down to the laptop storage nodes

Something to think about.

Stephen.

[quote=“Devlin7, post: 2571, member: 612”]Brilliant. Thanks for this. Just out of interest I have been having issues installing a storage node. [I have posted a support question but it has largely been ignored. I can can’t install FOG storage nodes on Ubuntu 10.04 [32 or 64 bit]. Can anybody confirm that it works/doesn’t work and suggest a work around?[/quote]

I don’t know about Ubuntu 10.04 but I have gotten a working storage node up and running on Ubuntu 11.10.
The main thing I was missing the first couple times I tried is that the username and password that the FOG setup spits out for the storage node needs to be entered into the FOG Managment console while creating the Storage Node Object.

Please note that Line 34 of service/Pre_stage1.php should read:
[INDENT=1][PHP]if ( $location != null || $location != -1 )[/PHP][/INDENT]
It currently reads
[INDENT=1][PHP]if ( $location == null || $location == -1 )[/PHP][/INDENT]
This is causing the execution to stop during the location check and say that there is no location set for the PC.
[edit] only while a location is actually set. I didn’t try it without a location set.

Stephen.