phpipam / phpipam

phpipam development repository
https://phpipam.net
2.24k stars 737 forks source link

[bugs][feature request] A few bugs and feature requests for phpIPAM #1816

Open Genluck opened 6 years ago

Genluck commented 6 years ago

Hello to everyone who is supporting and developing phpIPAM.

I’m very glad for this project active developing. And I’m hoping there is a big future for this project.

I’m very bad with PHP scripting so there wouldn’t be much help from me with code commits, so I could help only with testing, reporting bugs that I have found and providing information about features that would be good to see at this project.

About bugs that has been found so far:

Features that would be good to see:

zombah commented 6 years ago

You can export with rest api in any output format you wish.

Genluck commented 6 years ago

Hello, zombah. Thank you very much for you comment regarding API. Yes, I could do so and I could write a script for exporting in whatever way I need it but it wouldn't be a part of phpIPAM interfaces. And if it is not a part of the interfaces:

So native support of exporting inside of phpIPAM interface would be much better.

zombah commented 6 years ago

Hello @Genluck, I use api alot and didn't noticed any system resources impact. I don't quite understand what you mean with "native support of exporting" imo api is the most native export method, but there is also some import/export in admin section, maybe export into csv is native one.

Genluck commented 6 years ago

Hello, zombah. Thank you very much for your comment and sorry for a long response.

what you mean with "native support of exporting"

I did mean it in a way of native support from a web interface. You as a programmer (and I as system administrator) could easily create request to API or create a little script to get what we need. But managers couldn't do it. So they should ask responsible team to export necessary info for them. Yes, we could create scripts for exporting info that we need. But those scripts couldn't be integrated to phpIPAM interface (we should add them to web servers and add links to info pages). Also those scripts wouldn't be using access rights of phpIPAM groups, so managers could export any data even if they don't has access to it inside phpIPAM.

I use api alot and didn't noticed any system resources impact.

If there is only phpIPAM on the server then it would be hard to see any impact of the service on server. In case when it works on the server with another services on it it could be noticed. But in fact it's a double work for the server resources: first phpIPAM should calculate data for API request and after this the script itself should do an additional calculations. If export would be a part of phpIPAM then calculation should be done only by phpIPAM without preparing JSON data as additional step.

But, yes, I could agree about small impact for resources. But this is the last point in pluses. The support of function from phpIPAM interfaces and groups limitations is a primary reasons for having it in phpIPAM.

import/export in admin section, maybe export into csv is native one

Yes, there do exist this method. But it is exporting all networks (for example I could ask in exporting "export for me all networks of this subnet") and without supporting of tree view (need to do it manually by data in Master Network column). So each export we should edit some data (for example if I need all networks of specified vlan I should export all data, filter out vlan that I need and delete all not necessary data)..

zombah commented 6 years ago

Hello @Genluck, There is existing plans to refactor web ui import-export check #1566