Group Details Private

Senior Developers

 
  • RE: Permissions management server side

    I believe you need to add two field into the accesscontrolrule side of things.

    The Type: MAIN_MENU
    The parent: main
    The node (leave blank)
    The value: accesscontrol

    Possibly you will need to do this for site so:
    The Type: MAIN_MENU
    The parent: main
    The node (leave blank)
    The value: site

    On 1.6 it will be two more than those but this should help.

    posted in General Problems
  • RE: Permissions management server side

    @6rilT Let me play around a little bit. Mind you I’m running working-1.6 as @Sebastian-Roth has been doing wonderful keeping the 1.5.5 tree updated. So While some things are a little different, the actions performed should still be relatively similar.

    Essentially, We just need to create the hook that manages the menu access. Without the menu available, with the access control plugin, a non-elevated user cannot access the access control and make changes, even if they know the url.

    posted in General Problems
  • RE: Apache2 error-Won't download-We're DOWN :(

    @Dee Then you may need to put the picture on an image sharing site. Something like imgur could work.

    When you have errors from the GUI (and many backend areas) you can get them from:

    redhat based:
    /var/log/php-fpm/www-error.log
    or
    /var/log/httpd/error_log

    Debian based:
    /var/log/apache2/error.log

    posted in FOG Problems
  • RE: Apache2 error-Won't download-We're DOWN :(

    We need information.

    The picture you uploaded didn’t complete uploading. (Hint, make sure you’re on a full screen browser, paste in the picture. On the right pain is a “preview”. Post/submit the posting when the image has appeared on the right hand window.

    What version of fog?
    What OS?
    What error are you seeing. “Apache 2 error - won’t download -we’re down” doesn’t really tell us anything.

    posted in FOG Problems
  • RE: Compatibility check for X1 Carbon 2018

    Our API on the init side is pretty simple. fog is the command that does all the actions for you. There’s no switches/arguments involved. Maybe in a future version we’ll have stuff like:

    fog -D || fog --deploy
    fog -C || fog --capture
    
    fog -D -d || fog --deploy --debug
    fog -C -d || fog --capture --debug
    

    It’s not there yet and we rely pretty heavily on the web calls to generate the appropriate action.

    posted in Hardware Compatibility
  • RE: 2 questions regarding image capture/creation.

    @salted_cashews
    I think you’re thinking too much into this.

    If you have 1 storage group, the master node replicates its “replicatable” images to all storage nodes in the group.

    If you have 2 storage nodes in one storage group, the images that are set to replicate will replicate from the master node to the other node. The space is not “divied” up. The master node will always be the node images captured are loaded to.

    You could, I suppose, copy specific images from the master node and place it across other nodes so long as those images are not set to be replicated, but again, this does not increase your actual storage space. It just distributes it to the other nodes.

    The simplest method, add more space to your master storage node.

    posted in General
  • RE: 2 questions regarding image capture/creation.

    @salted_cashews Storage node’s can “see” the images, but the images are loaded from the local node in use. Meaning, if you don’t replicate the image across your storage nodes, and a machine uses a node that has NOT had the image replicated to it, it will fail to perform the task. We have some checks and balances of course so hopefully a machine will not load a storage node that does not have the image files available to it.

    I don’t understand what you mean if “that would simply expand the size of your available storage”?

    The storage is reported on the local storage node, not the total of all nodes in a storage group.

    posted in General
  • RE: Help with code: usernotinme list

    Unless, of course, you’re trying to make it core usable? But the only time this would be viable would be if LDAP plugin is in use. Of course other plugins may want to make adjustments here as well. I need to think on this a little bit.

    posted in General
  • RE: Help with code: usernotinme list

    @Fernando-Gietz While I understand and respect that your spanish, might I ask you to use english for the description? We can add gettext to the description fields (which I think is already done). The only other part I might suggest, then, is putting the category as “Plugin: LDAP”. Just makes finding it and knowing what it’s impacting much simpler.

    posted in General
  • RE: Auto Deploy restarts PCs, but boots back into Windows

    As @Sebastian-Roth stated; In order for FOG to perform tasks automatically, your machines MUST be set to PXE Boot First. This is how FOG works, and why FOG does not require a Sneaker-Style Medium (Such as the case with CD’s, DVD’s, or USB Drives.)

    In order to UEFI PXE Boot, your DHCP must be setup to hand out the EFI binaries. We have a few provided such as snponly.efi, snp.efi, ipxe.efi, realtek.efi, and intel.efi. For most cases one or a couple of these will work. I would recommend using ipxe.efi to start with. UEFI is still relatively new and has not been standardized across the board, especially in the case of UEFI PXE Network Stack. So unfortunately there’s no “one ring to rule them all.”

    Hopefully this can help, and we will try to provide help and assistance along the way.

    posted in General Problems