Latest FOG 0.33b

Tom Elliott

r1348 released.

Add’s hooking to the Storage Management Page. Finally, only one more page left.

Tom Elliott

r1349 released.

All Management pages are now rid of excessive php tags and table information is all hooking able.

warp

[quote=“Tom Elliott, post: 24344, member: 7271”]This is expected. The reason for it to “I don’t appear to the be group manager.” Is the IP of your fog server is not the same as the IP of the NAS. So it is NOT the group manager for that particular node. For everything else, however, it should be perfectly fine.[/quote]
Hello Tom,

Can you then tell me the proper way to set FOG knowing that:

[U][B]FOG server:[/B][/U]
[LIST]
[]CentOS 6.5
[]5 GB disk
[*]FOG 0.33B
[/LIST]
(No backup on the server that has a 5GB disk)

[U][B]The NAS server:[/B][/U]
[LIST]
[]SYNOLOGY
[]8TB disk
[/LIST]
NFS share as many NAS trade is prefixed to the volume name, for it is SYNOLOGY / volume1 / for IOMEGA is “/ nethdd /” which gives for SYNOLOGY “/ volume1/images” and IOMEGA "/ nethdd / images "

I also want to keep the timer function.

Tom Elliott

r1350 released.

Major changes with this. (Sort of).

functions.includes.php is no more. I went through and made the necessary changes where needed and was able to remove the need for this file entirely.

Removes the management/includes directory and files as everything is now class based.

Removes the mobile/includes directory and files.

Moves the mobile files to class files.

Sounds like it’s not much, but believe me it should have quite a large impact on overall number of files.

Thank you!

warp

[quote=“warp, post: 24403, member: 22860”]Hello Tom,

Can you then tell me the proper way to set FOG knowing that:

[U][B]FOG server:[/B][/U]
[LIST]
[]CentOS 6.5
[]5 GB disk
[*]FOG 0.33B
[/LIST]
(No backup on the server that has a 5GB disk)

[U][B]The NAS server:[/B][/U]
[LIST]
[]SYNOLOGY
[]8TB disk
[/LIST]
NFS share as many NAS trade is prefixed to the volume name, for it is SYNOLOGY “/volume1/” for IOMEGA is “/nethdd/” which gives for SYNOLOGY “/volume1/images” and IOMEGA “/nethdd/images”

I also want to keep the scheduler function.[/quote]
I like to continue to help you to “debug” the 0.33b version, but without an answer to my question, I can go further, because my architecture is that.

[COLOR=#00ccff][B]Can you help me ?[/B][/COLOR]

warp

on r1350 there is no page on url “report” : [url]http://srvfog/fog/management/index.php?node=report[/url]

Tom Elliott

[quote=“warp, post: 24465, member: 22860”]on r1350 there is no page on url “report” : [url]http://srvfog/fog/management/index.php?node=report[/url][/quote]

This was because there was a function call that didn’t exist anymore. Corrected and you should now see a display of the files and such.

[quote=“warp, post: 24463, member: 22860”]I like to continue to help you to “debug” the 0.33b version, but without an answer to my question, I can go further, because my architecture is that.

[COLOR=#00ccff][B]Can you help me ?[/B][/COLOR] :)[/quote]

The answer to the question, as I understand it, is if you want to manage information on the NAS node, the IP information needs to be different from the FOG Server when in another group. The only issue with this is you won’t be able to Replicate images to this node because it’s no longer a part of that group. For that same reason, putting the node into the group itself won’t work, because the Management of that node is done from a totally different IP. What I’d recommend is to mount the NAS as /images on the local FOG Server. Or under another name if you need (/images) and when you create the node on the Server, you’d still use the FOG Server’s IP address.

So,
Add the NAS to mount on bootup in your fstab file. How you do it is up to you. I’m not going to write a tutorial on how to do this as there’s plenty of howto’s all over the place.

Reboot your FOG Server and verify the NAS is now mounted like a local storage place on your FOG Server.

Add the new folder as a node. The IP address for this node will then be the same as your FOG Server, not the NAS’s IP.

The Management User and Password will also be the same as your Default node.

Make your NAS the Master for that group. (If you have images on the original master, before checking that the NAS volume is master, copy the original to the NAS storage location.)

Tom Elliott

r1351 released.

Fixes the report node issue warp reported earlier.

Tom Elliott

r1352 released.

Fixes mobile display issues on first load. If you specificed ?node=homes you’d be fine, but if you just went to the link it was trying to display the normal web gui’s home page. This is now corrected. Also fixes the search bar on the hosts node in the mobile page so it’s not a button.

Thank you,

warp

[quote=“Tom Elliott, post: 24466, member: 7271”]This was because there was a function call that didn’t exist anymore. Corrected and you should now see a display of the files and such.

The answer to the question, as I understand it, is if you want to manage information on the NAS node, the IP information needs to be different from the FOG Server when in another group. The only issue with this is you won’t be able to Replicate images to this node because it’s no longer a part of that group. For that same reason, putting the node into the group itself won’t work, because the Management of that node is done from a totally different IP. What I’d recommend is to mount the NAS as /images on the local FOG Server. Or under another name if you need (/images) and when you create the node on the Server, you’d still use the FOG Server’s IP address.

So,
Add the NAS to mount on bootup in your fstab file. How you do it is up to you. I’m not going to write a tutorial on how to do this as there’s plenty of howto’s all over the place.

Reboot your FOG Server and verify the NAS is now mounted like a local storage place on your FOG Server.

Add the new folder as a node. The IP address for this node will then be the same as your FOG Server, not the NAS’s IP.

The Management User and Password will also be the same as your Default node.

Make your NAS the Master for that group. (If you have images on the original master, before checking that the NAS volume is master, copy the original to the NAS storage location.)[/quote]
Thank you for the reply,

I actually read all the tutorial for several weeks.

But at the system level, it is impossible to mount a share “NFS” on “/ images” folder which is itself already shared by NFS “exports” file.
[CODE][B]etc/fstab[/B]
172.16.8.43:/volume1/images /images nfs rsize=8192,wsize=8192,timeo=14,intr
[/CODE]

[CODE][B]etc/exports[/B]
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
[/CODE]

[CODE]
[B]sudo service nfs restart[/B]
ArrÃªt du dÃmon NFSÂ : [ OK ]
ArrÃªt de NFS mountdÂ : [ OK ]
ArrÃªt des services NFSÂ : [ OK ]
Shutting down RPC idmapd: [ OK ]
DÃmarrage des services NFSÂ : exportfs: /images/dev does not support NFS export
exportfs: /images does not support NFS export
[ OK ]
DÃmarrage de NFS mountdÂ : [ OK ]
DÃmarrage du dÃmon NFSÂ : [ OK ]
DÃmarrage de RPC idmapdÂ : [ OK ]
[/CODE]

Tom Elliott

Can you mount as a Samba/CIFS share to the FOG Server? This way NFS isn’t trying to double back on itself?

warp

[quote=“Tom Elliott, post: 24471, member: 7271”]Can you mount as a Samba/CIFS share to the FOG Server? This way NFS isn’t trying to double back on itself?[/quote]
This is the same problem with samba/CIFS … but how did the other??
[CODE]/etc/fstab
//172.16.8.43/images /images cifs username=fog,password=password,ro,uid=fog,gid=root,file_mode=0775,dir_mode=0775,rsize=64k 0 0
[/CODE]

[CODE]
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 4554672 1674300 2649000 39% /
tmpfs 961132 0 961132 0% /dev/shm
/dev/sda1 396672 49160 327032 14% /boot
//172.16.8.43/images 3839533064 1532899724 2306471424 40% /images
[/CODE]

[CODE]sudo service nfs restart
ArrÃªt du dÃmon NFSÂ : [ OK ]
ArrÃªt de NFS mountdÂ : [ OK ]
ArrÃªt des services NFSÂ : [ OK ]
Shutting down RPC idmapd: [ OK ]
DÃmarrage des services NFSÂ : exportfs: /images/dev does not support NFS export
exportfs: /images does not support NFS export
[ OK ]
DÃmarrage de NFS mountdÂ : [ OK ]
DÃmarrage du dÃmon NFSÂ : [ OK ]
DÃmarrage de RPC idmapdÂ : [ OK ]
[/CODE]

Tom Elliott

Sick of searching and trying to walk you through it.

Try following these instructions.
[url]http://fogproject.org/forum/threads/request-fog-nas-tutorial.419/#post-11178[/url]

warp

[quote=“Tom Elliott, post: 24473, member: 7271”]Sick of searching and trying to walk you through it.

Try following these instructions.
[url]http://fogproject.org/forum/threads/request-fog-nas-tutorial.419/#post-11178[/url][/quote]
I agree that this method works very well, this is the one I use from the beginning, because I had realized that we could not share a NFS sharing !

But we return to the beginning of our problem so! The Sheduled Tasks do not work in this configuration !

Tom Elliott

Well,

I’m going to be rewriting the FOG Service scripts over the weekend. It may not be fully complete but I am going to see what I can do to fix this. there’s no guarantee’s though okay?

warp

[quote=“Tom Elliott, post: 24479, member: 7271”]Well,

I’m going to be rewriting the FOG Service scripts over the weekend. It may not be fully complete but I am going to see what I can do to fix this. there’s no guarantee’s though okay?[/quote]

Very good !
It may be a button when creating a “Storage node” to indicate that it is a NAS other than “FOG Storage Node” and therefore the “scheduler” remains active in the "FOG Normal server. "
it’s just an example.

You are really doing a good job, I will continue testing the r1352

warp

Or create a “Storage Group” special for NAS ! :rolleyes:

warp

There is a small problem with the page “Report Management-> host list”
[CODE]/var/log/httpd/error_log
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: array_unique() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 119, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: rsort() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 120, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/fog/management/reports/Imaging Log.php on line 121, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[/CODE]

[url=“/_imported_xf_attachments/0/605_Capture.JPG?:”]Capture.JPG[/url]

Tom Elliott

Once again, set your image and os id records on your hosts.

warp

[quote=“Tom Elliott, post: 24487, member: 7271”]Once again, set your image and os id records on your hosts.[/quote]
Yes maybe but it is a “csv” import of hosts, and it may be that all is not specified, but I still think these messages should not be there.

Latest FOG 0.33b

172

11.6k

17.1k

154.5k