New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Problems of a NAT based provider?
Hello folks,
As you can see that Hypervisor is being developed at a good pace, I'm here today to ask providers a few questions.
1) What are the problems you face when providing NAT based servers in your control panels?
2) Is everything automated? If no, then which part needs automation?
3) What else do you need but don't have in your current control panel that could ease provisioning?
Regards,
Bharat B.
Comments
@AnthonySmith @mikho @Cam @Neoon
customers.
1) control panel wise, none.
2) yes
3) better support for OpenVZ7
As I thought no one is doing KVM NAT
customers.
@Neoon is
Everything works fine with Proxmox, no issues there.
No reason to go for SolusVM crap panel.
1) none, since I have developed my own
2) yes, I can accept requests with one click and it deploys it fully automatic
3) nothin
Can you tell me more about your provisioning setup?
Are you cloning a template which then gets assigned an IPv4/v6 via DHCP?
Can you build a feature to automatically detect idiotic customers and cancel provisioning their boxes?
We have this already, people failing to access the machines if they do not read.
It works better then expected.
But not reading stuff, does not mean they are idiots.
I need AI
I can agree with this in principle, but in practice, I wouldn't rely on them for really important stuff. You don't hand over the wheels of a Ferrari to a person who didn't read the Tesla manual and goes to a gas station forcing the gas pump nozzle into the electrical charging port.
Tier 2 DHCP v4 flux compensator yes.
Also got a Tier 3 radavan route announcing device, which is using the neighbour stalking protocol for v6.
And yes of course, we make clones, makes life easy.
When a VM is cloned, the adapter settings will be adjusted and then it will be launched.
As Soon the VM launches and connects to the interwebs, it will let the panel know, that the launch was successfull by handing over the random generated password which has been configured on the boot to the API.
Afterwards the user can see the login information and can start using it.
Hi.
hi @BharatB
by the way, i aint sure, if you have support for openvz in your panel, so you may ignore the '2'nd point
Well I guess no use fretting over this feature unless someone explicitly requests this to be done. I'll just continue with block storage volumes next.
lack of real support for my dumb questions
Thats what forums are for.
Is that why LES is down?
Forum is up?
LES is more
EDIT2: also, it's up