Proxmox and FOSSBilling

m_pahlevanzadeh

Hello everyone,

Does FOSSBilling support the following actoins of proxmox:

suspend

unsuspend

play

power off

power up

restart

and some many actions?

By the way, Suppoerted hypervisor by fossbilling are which? KVM and so on?

BelleNottelling

Regarding the supported hypervisors, FOSSBilling has modules for both Proxmox and SolusVM.
The Proxmox module is mostly broken and we don't know if the SolusVM one works correctly or not.
For the Proxmox module specifically, you can check the open issues on the repository to get an idea what status it's currently in. Even if it does connect and create servers for you, you should still not use it outside of development.

https://github.com/FOSSBilling/Proxmox
https://github.com/FOSSBilling/SolusVM

Anuril

Yes, the Proxmox Module is sadly not in a great state. I'm looking into improving it.

To me it's clear that every customer needs to have their own pool and permissions that can only touch their vms, while the admin account should only be able to manage users.

Imho, Fossbilling should not interfere with any existing proxmox configuration, and should be able to be enabled or disabled without having to fear something is going to break.

I'm currently playing around with the code and would love some input when I feel it's in a more fleshed out state.

Some thoughts:
- Currently, available resources are managed in "slots", and I think that should be more fine grained. As we can get information about the server, we should be able to manage it's more detailed.
- Configuration of the VM should be able to be defined flexibly, not having to create a product per "type". Sure, "Small VM" with defined cpu cores, RAM and storage would be fine, but I think it should be more like "shared vps", "dedicated vps", "container" and then configuring additional resources.
- Storage capabilities should also be read from the server and we should be able to classify it. (F.ex ssd & hdd storage, etc.)

Anuril

Okay, I've made some progress.

One issue is that pve2_api.class.php doesn't support API Tokens yet, so I'll have to patch that and get the PR approved upstream.

I've implemented API Token authentication for the user that shall create the client users. I've also added some functionality to query the server's hardware information (CPU & RAM works, storage is WIP). Currently, it doesn't calculate anything, but next steps would be to summarize each hosts' used resources and modify find_empty.

I see four areas to focus on for a 0.1.0 Release Candidate:

Authentication per client
Provisioning based on "real" resources, instead of "slots"
Data handling of the extension (Products, Options etc.)
Install & Uninstall process - Focus on Data retention. ("DROP TABLE IF EXISTS" isn't the way to go imho)

I will now clean up the code and link to my repo if anyone wants to look in and give feedback, I'd be very happy.

BelleNottelling

Anuril

Hey there, it sounds like you're putting in some great work towards the Proxmox module which is appreciated!

Anuril One issue is that pve2_api.class.php doesn't support API Tokens yet, so I'll have to patch that and get the PR approved upstream.

Just FYI, there's already a fork of it that implements that.
(Two, actually)
https://github.com/notbasetwo/pve2-api-php-client
https://github.com/BelleNottelling/pve2-api-php-clien (Based on notbasetwo's version, but rebased on the original repo and with a couple of minor patches to the code. This one is untested, but should function just fine)

Anuril

BelleNottelling Just FYI, there's already a fork of it that implements that.
(Two, actually)

Thanks! I hope to get the token access upstream so we can profit from their updates without having to redo part of the work.

The only way I see this happening is if I implement it so it doesn't break backwards-compatibility (by keeping the login system).

BelleNottelling

Anuril Sounds like a great idea!

Anuril

I've sent the PR for pve2_api to upstream and worked on the FOSSBilling side.

So far, I've got the code for creating a fossbilling user on pve with the root password, adding the permissions to proxmox, creating a new token, and deleting the root password from the database.

Also, I'm testing the code to create a pool for the client.

I'll post more details tomorrow 🙂

S4-John

@Anuril Some great thoughts in here, do keep us up to date with your progress 🙂

Anuril

You can also follow the progress here: https://github.com/Anuril/Proxmox

Here's the current state:

Manage pools of Proxmox servers (orders can be allocated to servers automatically based on their capacity)

Complete Privilege Separation (each client can only see their own VMs),
Admin can't see inside client's VMs (Only the VM ID, Name, Status, IP, RAM, CPU, Disk, Bandwidth, etc.)
Provision LXC containers (not tested / might not yet work)
Provision QEMU KVM machines (tested, but needs very specific product setup)
Clients can start, shutdown and reboot their VMs (online console not working right now)
Proxmox Servers do not have to be reachable from the Internet (only the FOSSBilling server needs to be able to reach the Proxmox server)

Here's whats next:

Prevent disaster by "just" deleting x,y,z
Better Error Handling when creating unexpected things happen & get returned from pve host.
Better VM Allocation procedure
Consistent Naming: Server => Proxmox Virtual Environment Server | VM => Virtual Machine
VM & LXC Template setup need to be fixed and simplified
Provisioning of VMs with Cloudinit (https://pve.proxmox.com/wiki/Cloud-Init_Support)
Work on Usability to configure products and manage customer's products

S4-John

Anuril Prevent disaster by "just" deleting x,y,z

Yep, I can see the value in that 😃

Anuril

I've just pushed Version Preview Version of Proxmox 0.0.6 to https://github.com/Anuril/Proxmox/tree/main

While a lot of functionality doesn't yet work (Provisioning VMs is currently broken due to the WIP on the Templates, Templates currently don't support storage, removable media or network interfaces), I wanted to get feedback on the Module, as this would be the time to make significant Changes to the architecture, not after I've implemented most of it 😃

The Idea is: You configure VM Configuration Templates with CPU Cores, Memory, OS Type, etc.

Then, you create a Product that links to this Configuration Template as well as to the template VM that gets cloned and modified on PVE.

Adding resources dynamically will work via the "Addons" feature and Changing a configuration template via Upgrades.

Same for LXC Configurations.

I've also started rudimentary Implementation of an IPAM

This will allow the admin to run different Network Setups and assigning Adresses & VLANs to services and clients.

These Settings will be reflected on the PVE by either using the SDN Module, or just simple Linux Bridges with internal VLANs.

I'd love for some feedback from testers as to the direction of the Module.

Please note: While I've removed a lot of risky code and even added a Backup Functionality before Upgrades as well as Migrations - please be advised: This Software is not yet ready for Production. Unless and until I finish the template part, it won't allow you to provision orders.

One significant change: Proxmox now has its own Menu Item:

Now - Have fun testing and have a good time 🙂

DarkMonah

I have tried to setup an proxmox server, and got error about port specification, but I don't see port field in my form, however it's a very great idea to do so many things, hope it will be realised. All potential functionality will transform the fossbilling in a powerful platform. Thank you for your effort, and waiting for the updates!

Anuril

DarkMonah

Hey!

Did you clone from here? https://github.com/FOSSBilling/Proxmox/tree/0.1.0

This is the current testing branch, it should have the port field too.

Anuril

There is a new preview release - https://github.com/FOSSBilling/Proxmox/releases/tag/v0.1.0-alpha.0

cloudrack-ca

Anuril Keep up the good work in regards to this module 😃

BelleNottelling

Posting this here to curb any confusion before it happens,. but I have deleted all of the releases for the Proxmox module & shuffled the branches around.

The branch that @Anuril has been working on is now the default & the other one has been renamed to main-old to reflect it's status.

Releases were removed as the module isn't really ready for testing outside of development and quite a few people seemed to think otherwise.

The module isn't going away or anything and I know that @Anuril plans to continue his great work, I just don't want people to be trying to use something in any significant manner when it's just not really ready for that yet.