Jump to content

omaticon

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by omaticon

  1. I would absolutely create ISO based KVM services by mounting the ISO to the virtual CD drive. For KVM systems based off images, it would need to be handled similar to the current OVZ solution.
  2. Would this include support for KVM and unified IP pools?
  3. Thank you for the post! I will begin testing of the module this weekend.
  4. I believe what he is getting at is that it would be possible to have "cleaner" URLs for the ordering system if rewrites or post URLs were used.
  5. Donation made of the aforementioned amount for your work on a better Proxmox PVE module. Other folks that use, or are interested in using, Proxmox PVE should show their appreciation and support by making a donation as well. Thank you!
  6. naja7host, I'll get the ball rolling... I'll contribute $200 toward the creation of this improved Proxmox module.
  7. naja7host, It would probably be best to reference "[Rewrite] Proxmox Modules" in Developer Corner - Extensions.
  8. It is also necessary to allow the admin to specify separate paths for both the images and templates.
  9. Michael, we have done this in one or two other threads. I'm trying to drum up some increased interest from some coders to quickly get this done. I know nana7host has stated he plans to work on a module. But, he's been quite busy with other projects. Thus my motivation to see if there was enough interest in putting together a community bounty for anyone able to get the task done. Regards, Chris
  10. Those of us that use Proxmox know the current module is severely lacking. What would it take to get one of the Blesta or 3rd party devs on this and turning out a truly workable product quickly? Would a group bounty be enough incentive? I am at a point where I may need to use a different billing platform so that I can have usable Proxmox support. This is something I would prefer to not do.
  11. Is this on the roadmap for client accounts?
  12. As directed... here's another need for the proxmox module. I need for it to allow a customer to select (likely from a drop down) their desired openvz template or KVM ISO, as well. Regards, Chris
  13. EXACTLY! This is an option that should have been there day one. Let's hope the guys are able to pull this in quickly.
  14. I need for it to allow a customer to select (likely from a drop down) their desired openvz template or KVM ISO, as well.
  15. naja7host, I would tend to agree. Your signature says someone is doing just that. Who would that be, or, is there a thread covering it? The downside is that fixing the module would result in DB changes. Regards, Chris
  16. Tyson, All you need to do is create multiple storage locations inside Proxmox. Specify one as the location that hosts ISOs & templates. Specify the other(s) as locations to store containers and images. In the Proxmox module included in Blesta there is a "default storage location." If you specify one of the storage locations configured to store containers or images then the module will never fill the templates drop down in the client's "re-install" view because the templates do not exist in the same location as the one specified in the "default storage location."
  17. The Proxmox module does not support cases where templates are stored in a different storage zone than the zone the VMs are configured to be created in. As I don't have the time right now to investigate how to properly fix this I had to hack the following function. I hope this helps others and gets the issue resolved in a coming update. /** * Retrieves a list of the virtual server templates * * @param string $node The node of the server * @param stdClass $module_row A stdClass object representing a single server * @return stdClass An stdClass object representing the server templates */ private function getServerTemplates($node, $module_row) { $api = $this->getApi($module_row->meta->user, $module_row->meta->password, $module_row->meta->host, $module_row->meta->port); // Load the nodes API $api->loadCommand("proxmox_nodes"); $response = null; try { $node_api = new ProxmoxNodes($api); $params = array('node' => $node, 'storage' => $module_row->meta->storage); $this->log($module_row->meta->host . "|vserver-templates", serialize($params), "input", true); $response = $this->parseResponse($node_api->storageContent($params), $module_row); } catch (Exception $e) { // Nothing to do } $result = array(); foreach($response->data as $file) { if($file->content == "vztmpl") $result[$file->volid] = $file->volid; } return $result; } The hack: $params = array('node' => $node, 'storage' => "local"); Regards, Chris
  18. sysc, Thank you for your assistance. It got service creation working. Though, I haven't tried since the more recent proxmox updates. I will have to test that this weekend. I do agree the whole console access support is a mess along with how the module does not allow a real time selection of template to use by the customer during order. Hopefully these will be fixed soon. I don't know that I have the energy to brush up on my scripting/coding skills to fix the existing module.
  19. Thank you! With some modification of the path and using the complete file name I was able to successfully create a service. The two issues I now face is how to let a customer select which OpenVZ/KVM template he desires as well as the console page in Blesta showing the user ID specified in the module config and a "password" that is uber-long. Do you or anyone else have any insights? I appreciate all the help!
  20. Is anyone having issues with the actual creation of packages in Proxmox via the Blesta Proxmox module? I seem to get a null response to the the API call for the container creation. I'm just curious if this is a common problem post update or just a problem with my environment. Thanks!
×
×
  • Create New...