Nodes, Groups and Mirroring, oh my!
-
I have an svn3077 Fog server with three HDD setup. 1=OS+Fog, 2=PublishedImages, 3=Sandbox&WorkImages
2 and 3 are on their own separate HDD.
2 is Storage Node “DefaultMember”, Master, attached to storage group “Default” with image path “/images”
3 is Storage Node “other”, not master, attached to storage group “Other” with image path “/other”I have several other Fog servers, each on their own subnet; each with their own PXE, DHCP etc, to be set up identically.
I want to keep a live mirror of the master server’s 2=PublishedImages and the associated image file definitions on all the other servers.
I’m not sure Fog can do this or how to do it if it can. According to a thread from August 2014 my best bet is to cron or manually rsync, then manually alter the image definitions on each server.
Am I wrong? Can Fog do what I want?
-
[quote=“sudburr, post: 43309, member: 4706”]I have an svn3077 Fog server with three HDD setup. 1=OS+Fog, 2=PublishedImages, 3=Sandbox&WorkImages
2 and 3 are on their own separate HDD.
2 is Storage Node “DefaultMember”, Master, attached to storage group “Default” with image path “/images”
3 is Storage Node “other”, not master, attached to storage group “Other” with image path “/other”I have several other Fog servers, each on their own subnet; each with their own PXE, DHCP etc, to be set up identically.
I want to keep a live mirror of the master server’s 2=PublishedImages and the associated image file definitions on all the other servers.
I’m not sure Fog can do this or how to do it if it can. According to a thread from August 2014 my best bet is to cron or manually rsync, then manually alter the image definitions on each server.
Am I wrong? Can Fog do what I want?[/quote]
Hyper-V replication ?
That’d be a live mirror, but it’d be in the off state till the main server became unresponsive. Others may have better solutions, but that’s my solution. My FOG server is in Hyper-V and is replicating to another server in case things go south… I’m pretty big on safety and fault tolerance.
-
It is running in Hyper-V, but I’m not replicating the Hyper-V Server or the machine. Neither of which would perform what I want.
Mirroring the images is easy in so many ways, it’s having to manually remove/add/edit the image definitions on each subsequent downstream fog server that is the problem.
I want to replicate that specific image repository only AND alter the image definitions on the destination server without affecting anything stored on any destination server’s 3 drive and its associated image definitions.
eg:
Master Server
2= 12 images (newly changed)
3= 20 images
image definitions total= 32Destination Server
2= 16 images (old)
3= 2 images
image definitions total= 18Mirroring/Sync occurs …
Destination Server
2= 12 images (newly changed)
3= 2 images
image definitions total= 14 -
Or you can use the fog built it feature that does this for you?
-
Please enlighten me. I’m not having a good day rtfm on this one.
-
It’s fairly new.
It’s probably not 100% but should do what you’re requiring.
You simple set the image you want replicated to both groups on both groups.
That’s it.
-
This is only in theory right now, but it’s what I’m hoping to be the next server deployment, should the pilot work first of course.
As I read the user guide, I interpret it to mean that it can only be done on the same subnet, which is not what I intend.
Concurrently, the instructions are for downstream nodes to simply be local repositories but management and deployment commands are still carried out at the master. This I do not want.
Each server must be master of its own domain. All resources for FOG to operate on their own private subnet, including the management webpage for that server for the technician at that site to use. We don’t want them accessing the master server, but we still want them to be able to make their own images on their Fog server (saving them to their own 3=other drive/group/node)
-
This can be done, in such a way as you describe, using the Location plugin.
-
So Location plugin, multiple Groups and Nodes, and choosing which images you want mirrored across different groups would be done by setting the Group to Group (multi groups per image)
-
Thanks. This gives me something to chew on.
-
Hello,
First post so bare with me!
I’m successfully running Fog 1.2.0 on Ubuntu.
I’m using one AD domain, one DHCP server and I can only image on the same subnet as my dhcp server. My other locations which are all on the same domain and using the same DHCP server but do not reside in the same subnet cannot image.
I want: To use one fog server and simply image from all of my sites.
From what I am reading, I can use the location plugin to achieve this? Is their some good documentation out there to help me set this up? I basically just need something to add all of my ip scopes too. I read something about storage nodes as well but can’t quite catch the grasp on what that means to my particular fog environment. I’d like to keep all of my images stored in this one single location which is the fog server running in hyper V. So hopefully I can just use the locations plugin? help
-
[quote=“George Stewart, post: 47210, member: 29650”]Hello,
First post so bare with me!
I’m successfully running Fog 1.2.0 on Ubuntu.
I’m using one AD domain, one DHCP server and I can only image on the same subnet as my dhcp server. My other locations which are all on the same domain and using the same DHCP server but do not reside in the same subnet cannot image.
I want: To use one fog server and simply image from all of my sites.
From what I am reading, I can use the location plugin to achieve this? Is their some good documentation out there to help me set this up? I basically just need something to add all of my ip scopes too. I read something about storage nodes as well but can’t quite catch the grasp on what that means to my particular fog environment. I’d like to keep all of my images stored in this one single location which is the fog server running in hyper V. So hopefully I can just use the locations plugin? help :)[/quote]
The location plugin is how you achieve this.
You’ll find better documentation here in the forums about it than on the WiKi. From what I’m told, it’s really easy to configure.I’m in the process of creating rich documentation for the location plugin - it’ll probably be sometime next week before I get to it.
-
If your bandwidth between sites is adequate then you just need to set up the broadcast domain to all your vlans and it should work fine.
-
Thank you for the responses.
I am using the location plugin, but I have only one location. I’ve named this “main”. I have a dedicated 10 gig connection between my sites ( fiber ). One site can see the fog menu, register a device but fails (just reboots) once the image starts to pull down. My other site can’t boot to the fog system at all. I’ve ruled out the patch cables or switches being a problem as they are the same at all of my locations (gigabit switches). Should I setup additional locations at these other two sites and push the location\replicate the images down to these other sites? Just don’t want to go that route if my dedicated fog server here at the main location can handle this for me already.
-
[quote=“George Stewart, post: 47485, member: 29650”]Thank you for the responses.
I am using the location plugin, but I have only one location. I’ve named this “main”. I have a dedicated 10 gig connection between my sites ( fiber ). One site can see the fog menu, register a device but fails (just reboots) once the image starts to pull down. My other site can’t boot to the fog system at all. I’ve ruled out the patch cables or switches being a problem as they are the same at all of my locations (gigabit switches). Should I setup additional locations at these other two sites and push the location\replicate the images down to these other sites? Just don’t want to go that route if my dedicated fog server here at the main location can handle this for me already.[/quote]
You only have one PHYSICAL location, but do you have V-Lans, or seperate broadcast domains configured? Is your location sub-netted?
The location plugin only needs to be used if you have logically separated networks segments.
If everything in your organization is all in one nice-simple network and on the same broadcast domain, you can just configure storage nodes if you like, or just have 1 FOG server, and nothing more.
