Jump to content

xxxxx

Members
  • Posts

    82
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by xxxxx

  1. The awesome thing about having a 'Kubernetes Module' would be that it'd be a single API end-point for Blesta to hook in to, with no other knowledge or orchestration required by Blesta. Kubernetes offers the abstraction. I'll be publishing a paper on Kubernetes (and various other alternatives such as the CoreOS stack) shortly and I'm more than happy to help out where required. Some pointers on the API can be found here, although still in Beta: http://kubernetes.io/third_party/swagger-ui/#!/v1beta3/createPod It's worth noting that Kubernetes only currently supports the likes of Docker and Rocket containers, although there is interest in LXC/LXD runtime support it may take a while to come.
  2. You know what'd be awesome? To be able to be able to sell Linux containers. Containers are becoming increasingly popular, and orchestration frameworks with simple REST API's are coming out of the woodwork such as Google's Kubernetes (kubernetes.io). I know this is gonna be a while of...but one to think about.
  3. I'm aware of the 3rd party plugin. If the Blesta developers determine that it's of good enough quality they can feel free to reject my feature request here.
  4. Now that Digital Ocean's v2 API is stable, it'd be great to have an official module to allow our customers to spin up custom-branded Droplets.
  5. Guys, any plans to possibly add this to the feature list?
  6. I've just experienced the same issue in 3.3.1. Adding the service manually via the Enom module also threw the registered_for error forcing me too add the service not via module and register it manually via the Enom site.
  7. "...never stated it was necessarily a public module..."
  8. Not that I wish to drag this out, but... 1) As far as "you" know ... you don't know everything, and I never stated it was necessarily a public module. Don't assume things. 2) Yes, you are missing something. "Hold off" referring to holding off the feature implementation, and the second part was simply stating a fact. 3) See 1.
  9. 1) I didn't specify whose module I was speaking out. 2) Never once did I say that the V1 API should be used, quite the opposite actually. 3) This is a request for an official module. 4) If I want support with your module, whichever that is, I'll contact you, but don't hold your breath.
  10. If anyone else is interested in this please +1. There is a 3rd party (paid) module but it seems sketchy to say the least. The V2 API is in Beta so obviously they devs may wish to hold off, the the V1 API is stable and established.
  11. If anyone else is interested please +1. This would allow us to be dynamically competitive on domain pricing with no effort.
  12. Awesome. Thanks for taking the request on-board Paul.
  13. The V1 API is stable and well established, but I understand the holding off until V2 is out of beta. They've not released the Droplet MetaData API which is pretty cool.
  14. They've released a Public Beta of the new API. It looks super easy to use: https://developers.digitalocean.com/
  15. It looks like everyone is up for this. Any plans to implement please?
  16. Any plans for this guys? It looks like it has potential to be a much more popular module than VPS.net in my opinion. I've been test driving DigitalOcean for a while now and the quality and prices of packages they offer would be incredible to pass on to our Blesta-managed clients.
  17. Woo, thanks x is the best email address to get me on.
  18. Awesome, winning on Client Theme so far. Any votes appreciated Can we vote on out own theme given it's genuinely our favourite (I haven't btw)?
  19. More the price for me than anything. I'd struggle to resell VPS.net even at their Reseller prices. DigitalOcean are overall better in my opinion. I'd love the module.
  20. Hi guys, I've noticed that when a client pays via PayPal there is no Blesta email confirmation sent, it's completely left to PayPal to send a receipt which feels a bit unprofessional from the client's perspective. Could this be implemented?
  21. Hi guys, DigitalOcean would be a better alternative to VPS.net for a lot of us. They have an API so this would be a great module: https://developers.digitalocean.com/
  22. [26-Feb-2013 15:00:01 US/Central] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20090626/imagick.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20090626/imagick.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 07:55:02 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 07:55:02 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 08:00:01 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 08:00:01 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 08:05:01 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0 [17-Aug-2013 08:05:01 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so' - /usr/local/php54/lib/php/extensions/no-debug-non-zts-20100525/pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
  23. Okay, so I've had my reseller host make the changes you suggested in terms of PHP config, etc, however I'm still having the problem. I've noticed the job only fails when there's an email in the inbox. If it's empty, there are no issues.
  24. Thanks for your quick reply, Paul. - I don't think the messages are too large, there's generally only one message per cron job, if that, and it tends to be a couple of lines. - I can't imagine connectivity to the mail server or the credentials are the problem either, I have other mail clients hooked up to these accounts and mail is delivered fine. - That leaves me with looking in to increasing the timeout or memory limit, but I'll try dig around for PHP logs as suggested and get back to you.
  25. Hi, I know this issue has been brought to light a few times, but the solution has usually been to manually do some SQL and this is happening far too often for that to be a suitable fix for me. Version: Blesta 3.2.0 with all Plugins up-to-date. The problem: You can see there is an issue when logging in to the Admin Dashboard and looking at the System Status widget: "There are one or more cron tasks that have been executing for more than 60 minutes. View Automated Tasks." On digging in to the Tasks, the "Download Tickets" job is the issue. The spinner graphic continuously spins. The mail server and credentials are fine. How often: It happened once or twice previously, but since upgrading to 3.2.0 this has happened on either a weekly or sometimes daily basis. Sometimes the issue seems to fix itself (I know the lock file clears after 6 hours) but sometimes it's not suitable to wait this long and we are forced to use fixes detailed in the below threads. Hacky fixes used so far: http://www.blesta.com/forums/index.php?/topic/1805-there-are-one-or-more-cron-tasks-that-have-been-executing-for-more-than-60-minutes/ http://www.blesta.com/forums/index.php?/topic/1052-system-status-there-are-one-or-more-cron-tasks-that-have-been-executing-for-more-than-60-minutes/ Please can you take a look at this as soon as possible. Thank you, Daniel.
×
×
  • Create New...