Managing an ISCSI LUN in the proxmox gui.

L

LoganISU

New Member
Proxmox Subscriber
May 6, 2024
2
0
1
I'm new to proxmox, and new to enterprise hypervisors in general. Running 8.3.2

I'm hoping this is a very basic question, and I've just somehow missed the answer in the documentation.

We have dedicated SAN units that share out storage. I can see, and use the assigned LUN from the SAN in proxmox. I can see and use that storage as is, from both the individual node, and the datacenter storage tabs.

The part I am missing, is being able to further manage/carve up that LUN so that I can make smaller VM's within that storage.

Hoping someone can point me at the documentation on how to setup the systems to allow this.

I have been able to manually setup LVM on a LUN and then subdivide it from the command line, but half my team is windows* people, and they've made it abundantly clear that if it cannot be done in the GUI, they won't be touching the command line, ever. This led to management saying we need to be able to do it in the GUI or we'll need another virtualization platform.

So, if anyone can point me at how to setup the proxmox gui to allow for this, I'd really appreciate that.

Also, if there is more information I can give to make this post better, please let me know.



*Note that I'm not saying all windows people are like this, just the ones I work with.
 
Hi @LoganISU , welcome to the forum.

LoganISU said:
Hoping someone can point me at the documentation on how to setup the systems to allow this.
Click to expand...
Our KB article may be helpful for you here: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
Additional resources are listed at the end of the article.

Note, while you can do some things from UI, there are certain steps (Multipath) that must be done from CLI. However, your server team does not need to be involved in this. The tasks are more suitable for Storage team.

LoganISU said:
I have been able to manually setup LVM on a LUN and then subdivide it from the command line, but half my team is windows* people, and they've made it abundantly clear that if it cannot be done in the GUI, they won't be touching the command line, ever.
Click to expand...
There is very little you need to do in CLI as prep work. It is a one time configuration and does not, generally, require ongoing CLI maintenance.
However, you should prepare yourself and your team that there may be other situations where you will need to get familiar with Linux and PVE CLI.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Kingneutron
> half my team is windows* people, and they've made it abundantly clear that if it cannot be done in the GUI, they won't be touching the command line, ever

Powershell is a big part of Windows admin, as well. If you have people refusing to learn commandline, get rid of them and hire better / more flexible admins. There's no excuse for actively refusing to learn commandline if you're in a support role, that's dinosaur mentality. Srsly, talk to your boss and start giving them subpar reviews.

Hell, I learned how to parallelize Windows-based Amazon Cloud jobs with powershell a couple years back, and I'm a Linux / Mac admin. My job was on the line, so yeah - I freakin' learned. Brought the job run times down from an hour-plus to ~15-20 min running from a developer laptop.
 
Ok, clearly mentioning the backstory of my situation was a mistake. I don't have the power to change the windows team, but the requirement that storage management be doable in the gui persists.

Thanks for the KB link @bbgeek17
@Kingneutron and @alexskysilk , I agree, good systems people use the best tools for the job, and windows has powershell, and openssh, and ansible. Sadly, none of those things are going to happen until the clickycrew moves on.
 
You must log in or register to reply here.
Top Bottom