# glpi

Glpi Deployment on Kubernetes with persistent volumes and SSL certificate

Glpi Prerequisites - WebServer, PHP, Mysql/Mariadb Database.

Glpi Key Directories - /var/www/html/glpi/{config, plugins, marketplace.Files}.

MariadDB - /var/lib/mysql

Prerequisites for deploying GLPI:-

Kubernetes Cluster

Shared Storage for PV (You may also use local storage, but it is not recommended.)

1. Clone above repo - https://github.com/Dineshk1205/glpi.git

$ git clone https://github.com/Dineshk1205/glpi.git

2. Crate MariaDB root password as secret –

$ kubectl create secret generic mariadb --from-literal=mariadb-root-password=xxxxx

3. Create a glpi namespace.

$ Kubectl create ns glpi

4. Extract controller-v1.9.0.tar.gz file

$ tar -xvf controller-v1.9.0.tar.gz

6. Installing the Nginx controller helm is required.

Helm installation –

$curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3

$ chmod 700 get_helm.sh

$ ./get_helm.sh

6. Nginx deployment: -

Switch to ingress-controller directory.

$ cd ingress-nginx-controller-v1.9.0/charts/ingress-controller

7. Create a ingress-controller namespace

$ kubectl create namespace ingress-nginx

8. Run the following command to install the nginx ingress –

$ helm install -n ingress-nginx ingress-nginx -f values.yaml.

9. SSL Certificate Configuration –

Generate a self-signed certificate or use ca certified certificate.

Crate Secret using Certificate key and cert file in glpi namespace

$ kubectl create secret tls glpi-tls --key xx.key --cert xx.crt -n glpi

10. Update the IP address Range in metallb-pool.yaml file based on your network

11. Update host name in ingress.yaml based on your requiremnts

12. Finally, Install MariaDB And glpi

Switch to cloned Directory glpi and run the below command

$ kubectl apply -f .

Check pod status

$ kubectl get pods -A

Once pods are up, check glpi IP to access the GLPI GUI.

$ kubectl get ingress -n glpi

Create DNS records for the above IP ( IP is above ingress IP, and Hostname will be matched with ingress.yaml file hostname).Access GLPU using FQDN.

DB for Configuring the GLPI

In the Kubernetes cluster, check MariaDB IP

$ kubectl get svc

Note down above mariadbsv cluster IP; use IP for connected Glpi.SQL user use root as user and enter a password. (Password created as secret in previous steps)

Hello, dear GLPI-comminity! I wonder, is it possible to make a dark-mode right on the menu up-right, or somewhere else on main screen to easily change it in the evening? Thanks!

it would be great if in project tasks and projects when you assign the status Closed and this is indicated as Finished State, that percentage of the respective task goes to 100%.

We would need a function with which one can select and add several assets at once in the ticket creation. The best thing would be to be able to select several assets in the asset view via mass editing and to create a ticket with the selected ones right away.

If we want to force the User to fill out the Ticket-Type and therefore make it mandatory, there should be an empty value preselected, the same way as it is in Category. As in default GLPI the Type is already prefilled with request or incident.

Is it possible to create additional remote types in GLPI?

The programs included in GLPI such as TeamViewer, LiteManager, Anydesk, etc. are unfortunately too few for us in the company, and we would like to have the option to add more.

Regards.

When merging tickets, I think it could be useful to have a check box that, if flagged, could stop the sending of an email to all actors in the new merged ticket.

Thanks. 

ca serait bien de faire un pont ou une liaison entre les tickets issus des tâches des projets pour que à chaque fois que le ticket soit cloturé que le pourcentage de la tâche correspondante passe à 100%

Hi all,

I think can be usefull add some fields when I see the item under task (glpi/front/ticket.form.php?id=xxx) on this view; could be usefull that user can customize this view with filed he needs (like model etc)

Could be useful also add much criteria to search the exact item to add

Kind Regards

Stefano

Please consider moving the cartridges to the location of the warehouse location. Deleting from one object and adding to another object is very difficult.

Do the move action:

Also, the history of adding and removing cartridges is not recorded in the history. An unscrupulous administrator can delete it and not track it in any way. (there is a possibility that he will be able to take the cartridges for personal purposes).
If it is possible to implement the process of notifying the Super-Admin about the action of technical personnel over cartridges.