Server

• FOG Version: 1.4.0
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: Windows 7

Description

I have a host with two snapin associated. Then I create a single snapin task. I go to the active task page and I see, in all active task, my single snapin task, but in Active Snapin Tasks appears two snapin tasks

Then, is a normal behaviour?
I would like not cancel the multicast task.

Server

• FOG Version: 1.4.0
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: windows 7

Description

I created one multicast task with three hosts, one of them was powered off and I deleted his task from the active task list and … surprise!! the multicast tasks was cancelled by the daemon

From multicast.log file:

[05-18-17 7:47:47 pm]  | Task (197) Multi-Cast Task is already running with pid: 17556.
[05-18-17 7:47:57 pm]  | Task (197) Multi-Cast Task is no longer running.
[05-18-17 7:47:57 pm]  | Task (197) Multi-Cast Task has been cancelled.
[05-18-17 7:48:07 pm]  * No tasks found!

the udp-sender command in the server was killed and the two host powered on are waiting forever

I have the same problem with multicast wheen I send a task between different subnet.

I use RedHat 7.3 in my test server and with the 1.3.4 FOG version the multicasts worked fine, but I update it to 1.4.0 and surprise… The multicast doesn’t work.

I solved it changing the init.xz of 1.4.0 version with the init.xz of 1.3.4 version.

Well , I find a little bug XD in the plugin. I have fixed it and in the new version will be fixed.

BUG: When you try to install the plugin, the install process give an error and the installation doesn’t finish.

Status: Bug fixed

Hi falco,

sorry for my late answer, I don’t see this message until now.

With the new version of FOG 1.4.0-RC-12 I don’t have problems when I add a new rule.

Well I have finished the beta version, you can test it from the last RC version (1.4.0-RC12).

What does the site plugin do?
The site plugin allows you to restrict/control the access and the searches of hosts to one or more sites. When you associate one user to a site, this user only can see the hosts which are linked/located to this site. This plugin restricts the access to hosts in the task menu too, the user only can see the tasks of his hosts.

Brief operation instructions

1. Install the plugin
2. Go to Site Manager Menu
3. Create a New Site
   3.1) Enter the site name and his description
4. Link the hosts to the site. You can do it from the host menu or from group menu
   4.1) From host menu: Enter in the host General tab and select the site from “Associate Host to a site” dropbox
   4.2) From group menu: with this option you can link multiple hosts to one site. Go to the “Site Association” tab and select the site from the dropbox.
5. Link users to one site
   5.1) Go to Site Manager menu.
   5.2) Search or list the Sites. Choose the site.
   5.3) Go to membership tab
   5.4) Check the checkbox to show the user list
   5.5) Select the users which you want to link to the Site
   5.6) click the “Add User to Site” button
6. Restrict the access to the users
   6.1) Go to User Menu
   6.2) Search the user and select it. In the list you can see the sites that are inked to the user and if is a restrinc user.
   6.3) Go to General tab
   6.4) If you want to restrict the user, check the “Is restricted user” checkbox
   6.5) Click “Update” button

@Wayne-Workman said in Site Plugin:

@Fernando-Gietz Ok then - but perhaps a different name then? How about “Site Control” similarly named after “Access Control”.

Yes, is a good idea. I need change somethings in the code … rename all clases XD

@Wayne-Workman I agree with you, and it is a little confusing.

But the philosophy of Location plugin is different.
From https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin:

The location plugin is for use in multi-node fog setups that have a large distance or limited amount of bandwidth between each node’s network. The location plugin allows you to restrict a host’s storage node selection when imaging or other tasks occur.

At first I tried to use Location plugin to do the filters in the searches, and worked well but the Locations have limitations. The big one is that you can only define one location per storage node And I need more granularity. In my case I have one storage node to manage 7000 hosts in 50 buildings with 60 technicians. I don’t need the Location plugin but I need the Site plugin.

We could extend the scope of Location plugin and rewrite the plugin

It is easy
AccessControl Plugin -> add new rule

Rule Type: MAIN_MENU
Parent: main
Node: (empty)
Rule Value: pushbullet

After do this, you need associate this rule to the role.

Hi!!!

I am developing a new plugin, after AccessControl plugin, now Site plugin
With AccessControl Plugin we can control the access to the items of the webUI using roles. Now, with the Site Plugin we can control the access to the hosts by user using his physical location.

Site is not Location

With Location plugin we can manage the storage nodes from the hosts will download the images, snapins, … With Site plugin we can have more granularity, we can define as Sites as we need (IT room, labs, …) and associate the host to these sites. We can associate one user to one or more sites, in this way, the user only will see the hosts which are in his sites and not the others.

Good news!!!
I finished the beta version of Access Control Plugin.

When you install the plugin, the installation will create two default roles: Administrator and Technician.

The installation process will create a big number of default rules (38).

Actually the rules have two types: MAIN_MENU and SUB_MENULINK. The first ones are the top tool bar icons, and the second ones are the lateral menus. In the second case, sub_menulink, if you don’t define the node value, the rule will apply to all pages (nodes). If you define the node, the rule will apply only to this node.

From this page you can link a multiple rules to one role.
And, finally, the installation process will associate the Administrator role to fog user.

From the principal Access Control plugin page you can see the role list, add new role, list all rule and add new rule. In the role menu you can edit it, delete it, see the membership and see the rule that are associated to this role.

Membership page:

Rule association:

In these last images we can see that the “user5” has the Technician role and this role have 7 rule associated (5 main menu and 2 sub_menulink)

In this screenshot you can see the rules that are being applied for “user5”:

And in this one you can see that the sub_menulink rules (in the image page doesn’t appear the multicast and the list option) in action:

@Tom-Elliott said in Add the name field in Users table:

I just separated the “change password” and “edit fields” elements. Hopefully this doesn’t mean much recoding on your part for the Access control plugin you’re working on @Fernando-Gietz

I insert the role selectbox after username

It’s a little barter XD
He added a field in the database and I developed the access control plugin. Personally I think I’m losing

Exactly
Actually I have 60 technicians using FOG and I want to identify the technician to know who is doing tasks in the server.

@george1421 said in Add the name field in Users table:

So what you really want is a friendly name field (or display name in AD terms) in the user management table.

Yes

I know But this field is the username, and not the name of the user
Example:
Username: Wworkman001
Name: Wayne Workman

Usually the username, for example in my university, is unreadble or a number, you can not identify the user. We can call it friendly “username”.

I know that is a silly feature but … Is possible add a field called name in the Users table?
I would like know who is under the username In addition, the username can not have any blank space.

I don’t do it but if you change the CSS file, you can change the look of the webUI.

The CSS file is in management/css/default/fog.css

Thanks Wayne!!
Actually I am having problems with the edit rule option and the logic is not developed yet, but the initial idea is not render the elements.