I’m pretty sure the hostname field is limited to 15 characters as that is the limit for Windows domain names on anything older than Server 2003 (don’t quote me on that, I’m only pretty sure that’s accurate). The remained of the FQDN (localbackhaul.com) needs to be part of the search domain in /etc/resolv.conf.
Posts made by BryceZ
-
RE: How to use long hostnames
-
RE: Copy image from one fog server to a different fog server
You just need to copy the image file(s) over and create the image definition on the new server (making sure to point to the correct location).
-
RE: FOG 0.33 Requirements
As I understand it, 0.32 can handle both scenarios with and without the 100MB partition.
-
RE: FOG 0.33 Requirements
Correct. Resizable images do not use the cloned systems disk geometry and try to replace the MBR with a standard copy; for some reason this is no longer functional.
-
RE: Bugs in FOG 0.33
As this point I’m not really sure. I’ve only been somewhat involved in the development process, so I don’t know where they’re at with the upgrade path from 0.32 to 0.33. The code is the best (only) documentation for that at the moment, so I’d say give it a try on a test machine and let us (the community) know how it goes.
-
RE: Bugs in FOG 0.33
The database schema has changed between 0.32 and 0.33, so you can’t just do a export/import because the tables no longer line up. The devs were working at one point on getting a conversion script together, but I’m not sure if that’s still happening or what state it’s in.
-
RE: FOG 0.33 Requirements
Last time I spoke with any of the devs about it we thought it was an issue with the /bin/fog script in the boot image.
Here is the diff between 0.32 and the latest SVN change for that script: [url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/src/buildroot/package/customize/fog/scripts/bin/fog?view=diff&r1=729&r2=891&diff_format=h[/url]
We’re not 100% sure that it’s a bug in that script, but it seems the most likely.
-
RE: FOG 0.33 Requirements
As it stands right now, sysprep is no longer optional. It says Windows 7 and higher, but I think this will be true for Vista as well. If you can fix this people would be thrilled, but so far the devs haven’t had much luck with it.
-
RE: No Job found for MAC address
It seems like the boot files for those MAC addresses never got cleaned up. You’ll need to browse to /tftpboot/pxelinux.cfg/ on your FOG server and delete the files named 01-<MAC Address> with the MAC addresses of the netbooks that you’re having problems with.
-
RE: Specs
Unless you’re in a very demanding environment I feel like it would be wasted. If it’s just a matter of load balancing then I’d suggest setting up storage nodes. There are very few circumstances in which I would expect 10Gb to be the only option.
In the follow scenario your bottleneck is probably the HDD:
[COLOR=#999999]HDD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#999999]HDD[/COLOR]In the follow scenario your bottleneck is probably the 1Gb:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]In the follow scenario your bottleneck is probably still the 1Gb:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]In the follow scenario your bottleneck is probably the SSD, although you might have reached the 6Gb limit for SATA3:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Swtich[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]Without upgrading the network connections all the way to the client, the only performance increase you would see from using 10Gb on the server side is from concurrent imaging tasks, which you could easily get by using storage nodes to load balance the tasks.
-
RE: FOG worries
0.33 has hit some snags in development, but is mostly functional. I think there are a few pages where the code hasn’t been updated (new list functions that are working on some pages aren’t being called by other pages yet, or something like that). The big issue is that single partition images are not working if the system wasn’t sysprepped before uploading, but if you use sysprep then it’s not a problem.
Due to the new structure of 0.33, and the fact that it was almost completely written by a single developer who is unable to commit time to FOG these days, there hasn’t been any new code submitted in a while.
As far as I’m aware, there hasn’t been much in the way of donations, and what little there has been doesn’t go very far. I think they almost cover the cost of hosting fogproject.org, but I don’t have access to the account so I’m no authority on that.
More developers would be an excellent way to donate! Right now the code is the documentation, so as for a starting point I can’t really help you there. Pull down from SVN and mess around with it until you find something broken is the best advice I have.
Some of us are working to get things into a more organized state so that we can make it easier for the community to become involved, but with the holidays upon us its most likely not going to happen until January.
-
RE: Specs
SSD’s are generally faster than HDD’s, but there will be a point of diminishing return on performance. I believe the max theoretical throughput on a 1Gb NIC is 7.5GB/Min (1Gb/sec = 1000Mb/sec, 8b = 1B, 1000Mb/8 = 125MB, 125MB/sec * 60sec = 7.5GB/min… or something like that). So once your server is able to read the image file at that speed, and your client is able to write the image at that speed, you’ll see the peak performance without upgrading to 10Gb networking, which is pretty rare outside of the data center.
-
RE: Specs
The server consumes most of its CPU and RAM during multicast, because it’s decompressing the image file before pushing it out, which threads pretty nicely and uses a decent amount of buffering. I have dual core VM’s with 4GB of RAM for storage nodes, and they get pretty close to maxing out their resources while they’re multicasting.
-
RE: Server crash - how to get images relisted
If you were unable to restore the database from the old drive then you’ll need to recreate the image definitions in the Web UI and just make sure they’re pointing to the existing image files.
-
RE: Can I image Apple without DeployStudio/NetRestore?
This is something that a lot of people have been asking for, but unfortunately FOG does not currently support. Apple computers don’t have PXE support, and currently nobody has come forward able to successfully chainload from Apple’s Netboot into PXE. I believe there is some documentation on the FOG Wiki about running FOG and DeployStudio side by side if you do want to go that route.
-
RE: Capturing FOG traffic with sniffer
What you’re looking for is NFS traffic. I know Deploy makes it sound like it’s being pushed from the server to the client, but it’s actually a pull.
-
RE: Integrate Windows Authentication in FOG
Fernando, I think there are a lot of people out there using FOG that would really appreciate this sort of functionality.
-
RE: Correction: Why is FOG trashing file systems during partition resize?
So you took out the Recovery partition during install of Windows? I think it’s listed as System Reserved under Disk Management.
I want to say that FOG was written to handle that partition being there or not, but I have a sneaking suspicion that removing that partition could cause problems. I don’t know that it would cause your RAW problems. I’m just thinking out loud.
I recall uploading raw to be a problem for someone a while back, so you might be able to dig through the forums and find some advice, but I don’t remember the resolution.
-
RE: Correction: Why is FOG trashing file systems during partition resize?
First: Which version of FOG are you using?
Second: When you say these are single partition are you saying you didn’t add any extra partitions or that you went into the advanced options when installing Windows and removed the recovery partition? -
RE: Integrate Windows Authentication in FOG
Windows Authentication for FOG has been brought up before, but it will take somebody who is willing to get their hands dirty coding figuring out the best way to implement it, so it hasn’t really gone anywhere.
One alternative that I’ve managed to get implemented where I work is using Shibboleth to process the authentication and then having matching usernames in the FOG database to insure access. Luckily we already had the Shibboleth infrastructure in place, and other people had tied multiple web systems into it already, so adding FOG was a fairly trivial copy and paste of existing code.
I would guess that the easiest way to add Windows authentication to FOG would be to have Apache handle the authentication for accessing the site directory and use LDAP to tie Apache authentication to your Windows AD. But I haven’t tried this myself so I can’t provide any example code.