Anyway the code is pretty terrible, its not easy to customise and full of bugs. Unfortunately its just not fit for production. The good news is I'm most of the way through writing our own.
Network status page that is manually updated?
If you know of an issue and manually post an update, we know you know the problem and don't need to open ticket.
If there isn't status page or it's only automatic update, we don't know if you know the problem and want to open ticket or complain on forum.
@yoursunny said:
Network status page that is manually updated?
If you know of an issue and manually post an update, we know you know the problem and don't need to open ticket.
If there isn't status page or it's only automatic update, we don't know if you know the problem and want to open ticket or complain on forum.
@MichaelCee said:
Upmind does look kinda sexy from experience but a bit fiddly.
It looks and works amazing based on my testing experience, I didn't have any issues with it. It was top of my list when testing out the usability, performance etc - the only con was that it was a SaaS product and I don't have direct access to the backend. Not a massive issue day to day, but the question of what if they closed down? What would happen to my data?
Yes - I can use their API and extract the data I need to backup but it's just something else to deal with, especially when their are other products that can automatically backup the database, send it via email or FTP or whatever.
Anyway, those screenshots are looking pretty slick so far @natvps_uk - good work!
Had a quick Look over things this evening to work out what is left to do.
The Launch/Create instance view is complete. We will be forcing Key based auth from the release of the new panel.
Key validation will be done using sshpubkeys in strict mode: https://pypi.org/project/sshpubkeys/
strict: defaults to True. Disallows keys OpenSSH’s ssh-keygen refuses to create. For instance, this includes DSA keys where length != 1024 bits and RSA keys shorter than 1024-bit. If set to False, tries to allow all keys OpenSSH accepts, including highly insecure 1-bit DSA keys.
Additional OS Templates have been added:
I'm open to adding more but they will need to be tested for compatibility and cut down substantially.
The first instance was launched from the new panel this evening with is defiantly a milestone.
Tun/tap is now enabled at the time of creation removing the need for an additional button/process.
Bonus locations will be a thing of the past, whilst we do have a location that is not entirely stable this will hopefully be improved before the time of release.
Our Amsterdam location will no longer come with double resources to simplify things further. Any instances previously created will keep their memory allocated at creation.
Probably not, we’ve tested it. It’s dangerous, and can easily trash a container. If it does get added it will come with a whole bunch of warnings strongly recommending that it’s not used.
Probably not, we’ve tested it. It’s dangerous, and can easily trash a container. If it does get added it will come with a whole bunch of warnings strongly recommending that it’s not used.
Diks enlargement should be safe.
Shrinking … not so much … but can be done as long as there's plenty of free space.
Probably not, we’ve tested it. It’s dangerous, and can easily trash a container. If it does get added it will come with a whole bunch of warnings strongly recommending that it’s not used.
Diks enlargement should be safe.
Shrinking … not so much … but can be done as long as there's plenty of free space.
Enlarging is fine but shrinking is dangerous, not only does it have a tendency to fail it also doesn’t clean up after itself and the image file has to be manually shrunk using the likes of fstrim.
I’m reluctant to add a feature to enlarge disks if people can’t then shrink them.
That being said if I do find a safe way to shrink the disk I’m not opposed to adding the feature I’m just not willing to introduce unnecessary risk for a feature that few would use.
Probably not, we’ve tested it. It’s dangerous, and can easily trash a container. If it does get added it will come with a whole bunch of warnings strongly recommending that it’s not used.
Autocorrect says the button should be named enlarge dik.
A bigger dik has more girth and can store more files, so you don't have to delete the whole container and re-create from scratch.
It's okay not having a shrink button.
Found some time over the weekend to finish the Launch Instance view. Whilst it was already functional I wasn't happy with the design etc.
Deleting instances is now complete although the UI needs to be finished for the devices table as I'm not happy with it
Started on Ram Upgrade/Downgrades and did some testing on growing disks.
Email templates are also basically done
Postbacks from the worker is also complete, the end user will receive both a notification in the panel and an email once the instance has been provisioned.
"Light Mode" has also been implemented everywhere for everyone that likes to be given permanent retina damage from their VPS panel:
Todo:
View Invoices
Create/Edit Loadbalancer
Memory Increase/Decrease Delete Instance
Reboot Instance
Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.) Create SSH Keys
some of the email templates
Also as we're aiming to fully discontinue normal VPS' we need to make way for clients with storage VPS'. We'll be offering block storage priced at £1 per year per 100GB in the FR location and potentially the NL location. This will be while stocks last initially and is intended to assist in migrating people with higher storage plans with ourselves, there is easily enough space for a few people to grab this offer though at launch.
Comments
Todo:
Support ticketing
Loadbalancer creation and Editing
Stripe integration (Maybe)
I think I'll have this out early next year!
Clientexec more attractive but their development very long.
Upmind does look kinda sexy from experience but a bit fiddly.
Michael from DragonWebHost & OnePoundEmail
Spent some time over the last few evenings playing with Django-helpdesk thinking I could cut a massive corner on the support ticketing side - https://github.com/django-helpdesk/django-helpdesk
Anyway the code is pretty terrible, its not easy to customise and full of bugs. Unfortunately its just not fit for production. The good news is I'm most of the way through writing our own.
Thats as far as I'm going with ticketing, after all we offer a no support service!
Network status page that is manually updated?
If you know of an issue and manually post an update, we know you know the problem and don't need to open ticket.
If there isn't status page or it's only automatic update, we don't know if you know the problem and want to open ticket or complain on forum.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
https://micronode.uk/status/ Is automatically updated and we have full alerting on all nodes.
This will all be built into the new panel though, with the relevant notifications and messages.
No progress has been made this evening, catching up on tickets still from Black Friday.
I’m hoping to have the new panel functionally working over the weekend.
I’ve purchased a decent server to host the panel on although it should be pretty performant anyway compared to our WHMCS setup.
Hoping to have a public beta before the end of the year.
It looks and works amazing based on my testing experience, I didn't have any issues with it. It was top of my list when testing out the usability, performance etc - the only con was that it was a SaaS product and I don't have direct access to the backend. Not a massive issue day to day, but the question of what if they closed down? What would happen to my data?
Yes - I can use their API and extract the data I need to backup but it's just something else to deal with, especially when their are other products that can automatically backup the database, send it via email or FTP or whatever.
Anyway, those screenshots are looking pretty slick so far @natvps_uk - good work!
SharedGrid | Fast, secure, and reliable UK, USA and Singapore web, reseller and VPS Hosting
Litespeed, Redis Cache, NVMe Drives, Daily Backups, 24x7 Support, Wordpress Optimised.
Had a quick Look over things this evening to work out what is left to do.
The Launch/Create instance view is complete.
We will be forcing Key based auth from the release of the new panel.
Key validation will be done using sshpubkeys in strict mode:
https://pypi.org/project/sshpubkeys/
strict: defaults to True. Disallows keys OpenSSH’s ssh-keygen refuses to create. For instance, this includes DSA keys where length != 1024 bits and RSA keys shorter than 1024-bit. If set to False, tries to allow all keys OpenSSH accepts, including highly insecure 1-bit DSA keys.Additional OS Templates have been added:
I'm open to adding more but they will need to be tested for compatibility and cut down substantially.
The first instance was launched from the new panel this evening with is defiantly a milestone.
Tun/tap is now enabled at the time of creation removing the need for an additional button/process.
Bonus locations will be a thing of the past, whilst we do have a location that is not entirely stable this will hopefully be improved before the time of release.
Our Amsterdam location will no longer come with double resources to simplify things further. Any instances previously created will keep their memory allocated at creation.
Todo:
Diks enlargement and shrinking?
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
Probably not, we’ve tested it. It’s dangerous, and can easily trash a container. If it does get added it will come with a whole bunch of warnings strongly recommending that it’s not used.
Diks enlargement should be safe.
Shrinking … not so much … but can be done as long as there's plenty of free space.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
Enlarging is fine but shrinking is dangerous, not only does it have a tendency to fail it also doesn’t clean up after itself and the image file has to be manually shrunk using the likes of fstrim.
I’m reluctant to add a feature to enlarge disks if people can’t then shrink them.
That being said if I do find a safe way to shrink the disk I’m not opposed to adding the feature I’m just not willing to introduce unnecessary risk for a feature that few would use.
*Disks
Autocorrect says the button should be named enlarge dik.
A bigger dik has more girth and can store more files, so you don't have to delete the whole container and re-create from scratch.
It's okay not having a shrink button.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
Got a little done today, SSH Keys are now integrated. This is using the sshpubkeys library for validation.
Todo:
View Invoices
Create/Edit Loadbalancer
Memory Increase/Decrease
Delete Instance
Reboot Instance
Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.)
Create SSH Keys
Most of the email templates
Found some time over the weekend to finish the Launch Instance view. Whilst it was already functional I wasn't happy with the design etc.
Deleting instances is now complete although the UI needs to be finished for the devices table as I'm not happy with it
Started on Ram Upgrade/Downgrades and did some testing on growing disks.
Email templates are also basically done
Postbacks from the worker is also complete, the end user will receive both a notification in the panel and an email once the instance has been provisioned.
"Light Mode" has also been implemented everywhere for everyone that likes to be given permanent retina damage from their VPS panel:
Todo:
View Invoices
Create/Edit Loadbalancer
Memory Increase/Decrease
Delete Instance
Reboot Instance
Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.)
Create SSH Keys
some of the email templates
Also as we're aiming to fully discontinue normal VPS' we need to make way for clients with storage VPS'. We'll be offering block storage priced at £1 per year per 100GB in the FR location and potentially the NL location. This will be while stocks last initially and is intended to assist in migrating people with higher storage plans with ourselves, there is easily enough space for a few people to grab this offer though at launch.
As someone who has worked extensively with Blesta and Hostbill, I surely prefer Hostbill.
View Invoices
Create/Edit Loadbalancer
Memory Increase/Decrease
Delete Instance
Reboot Instance
Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.)
Create SSH Keys
some of the email templates
This is done: Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.)
Using Apex charts for the graphing for CPU load and Bandwidth usage, not graphing memory usage on the first release but I’ll likely come back to it.
todo:
View Invoices
Create/Edit Loadbalancer
Memory Increase/Decrease
Delete Instance
Reboot Instance
Instance Details (Including Ports, SSH command, bandwidth use, CPU usage, Memory usage etc.)
Create SSH Keys
some of the email templates