Clonezilla intergrate in FOG
-
We have multiple clonezilla images i want to deploy a task where it automatically image the device.
-
@george1421 this is the screenshot that i have strange is we had another Fog Projects server that has the same error now.
-
@kaywokke FOG needs particular parameters to be able to run tasks. As this is not a normal FOG task I am wondering if you don’t simply want to add this to the iPXE menu and image your machines through this.
While I can see the advantage of making this a task I still may ask. If you need this to be a task you’ll need to add parameters like
type=down
and possibly more to make this work. -
@kaywokke Thank you on the image that was able to confirm what I suspected and what Sebastian pointed out. The unknown request type::Null is created because there is no
type
kernel parameter defined. So the FOS engine doesn’t know what to do.Also as Sebastian mentioned and the reason why I asked what your goal is, because there are other ways to pxe boot into a clonezilla setup with FOG than a dedicated task.
What did you create in task type edit plugin? Somewhere you need to pass the
type=
kernel parameter to the FOS engine.If you look in the task type edit plugin on your computer you will see examples to Capture an image the kernel args are
type=up
In your case your type should match what you programmed in the hook. -
@Sebastian-Roth Sebastian what you mean with possibly is there a place where i can find documentatio about the type?
@george1421 i want to boot the device in Clonezilla where it automatically set back the right image of the device.
-
type=down for deploy
type=up for captureSimple as that.
But there are other potential parameters that may be necessary for it to function as expected.
-
@kaywokke said in Clonezilla intergrate in FOG:
i want to boot the device in Clonezilla where it automatically set back the right image of the device.
Isn’t this duplicating the same function that FOG does already? Without any coding?
But back on topic.
I know how hooks are supposed to work as well as I understand how the FOS Engine runs. In a normal FOG deployment the FOG server sends messages to the FOS Engine (the customized version of linux that runs on the target computer) via kernel parameters the FOG server writes into the command that starts the FOS engine. There is a special kernel parameter to the FOS engine called
type
. Thattype
parameter tells the main FOS script what to do on the target computer. See this main script. https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fogWhen the FOS engine prints unknown request type Null, is because the
type
kernel parameter was not set. When you write that hook, I assume that you are creating your own newtype
parameter. You need to pass that parameter to the FOS engine. So as I see it, you need to program the hook (what the code will actually do) as well as configure a matching parameter to send via the task type edit plugin.Now onto what I was mentioning before. I have a tutorial on how to add a FOG iPXE menu to boot different live linux environments using FOG. Understand this is unrelated to imaging. https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images
This is all done without any programming. I’m just creating a new iPXE menu that calls up the different linux kernels. While I haven’t had the need, I assume you could pxe boot into clonezilla this way to. -
@george1421 Hi george thanks for the information, i am new at fog so it is not easy for me to understand. Where can i set this parameter in the Hook? where do i need to put the type parameter?
Because if i do it from the task editor page and i save it and check again the task it is dissapeared.
-
You might want to read through this thread. It talks about creating the hook and then adding in the task type edit plugin that you will need.
https://forums.fogproject.org/topic/10274/creating-task-with-tasktypemanagement
-
@george1421 Thank you George it is working now! also it is booting. Thank you.
-
@kaywokke Great to hear you got this working with the help of @george1421! Well done, as this is definitely not an easy one to setup if you’re still a FOG beginner.
You might want to share your code and steps in this topic to help the community. I am sure someone will find this helpful one day.