My.VPSLink.com Control Center Updated

[chriss]

My first package created through the new control panel, and so far things are looking ok.

The requests seem to be a little broken though, as the two so far (create & start) both ended in error. Maybe this is a known issue, but I thought I'd share them anyway just in case:

create:
2009-04-04 04:36:04  	info  	 	Request Submitted
2009-04-04 04:36:04 	debug 		Posting updated provisioning data
2009-04-04 04:36:32 	ok 		__success_add_successful_on_vps_#####.vm
2009-04-04 04:36:32 	ok 		__success_add_successful_on_vps_#####.vm
2009-04-04 04:36:32 	debug 		Assigned ##### to hw_node ###.###.###.###
2009-04-04 04:36:33 	debug 		Assigned ips to #####
2009-04-04 04:36:33 	debug 		Posting updated provisioning data
2009-04-04 04:36:33 	error 		Error decoding message: malformed JSON string, neither array, object, number,
2009-04-04 04:36:33 	debug 		Posting updated provisioning data

start:
2009-04-04 04:42:10  	info  	 	Request Submitted
2009-04-04 04:42:10 	debug 		Posting updated provisioning data
2009-04-04 04:42:11 	debug 		About to call 'Provision::Unix::VirtualOS'::'start_virtualos'
2009-04-04 04:42:11 	error 	operation 	Unable to start
Audit:

    * find_config: searching for provision.conf
    * looking for provision.conf in /opt/local/etc
    * looking for provision.conf in /usr/local/etc
    * looking for provision.conf in /etc
    * found provision.conf in /etc
    * loaded Provision::Unix::VirtualOS
    * loaded P:U:V::Linux::Xen
    * checking for presense of virtual container #####
    * checking at /home/xen/#####.vm
    * found ##### at /home/xen/#####.vm
    * cmd: /usr/sbin/xm create /home/xen/#####.vm/#####.vm.cfg
    * syscmd: /usr/sbin/xm create /home/xen/#####.vm/#####.vm.cfg

Exception:
FATAL ERROR at /usr/lib/perl5/site_perl/5.8.8/Provision/Unix/Utility.pm line 2761

Even though the "start" request ends with "Unable to start", the vps has started just fine and is accessible on both console and ip address.

[Naaktgeboren]

Pretty please, fix issue #7 from my previous post. Underscores are valid characters in Name fields of NS records. Moreover, this thing is absolutely essential for deploying DomainKeys/DKIM. Unfortunately this bug prevents me from using your nameservers, because if I did I would not be able to delegate subdomains with underscores.
Cheers

[DanL@VPSLink]

Originally Posted by Naaktgeboren

7. test._domainkey NS ns.example.com. is a legal entry, so please make the interface not reject it. According to RFC the name in NS records doesn't have the status of "host name" and as such it can consist of any printable ASCII characters, underscores inclusive.

This item is on our development team's To Do list.

Originally Posted by Naaktgeboren

P.S. Could you please make the forum session lifetime longer? I'm usually automatically logged out before I manage to finish my post. Retyping is really annoying...

Do you have the "Remember me?" option checked? (If checked, vBulletin will associate a cookie with your session which will effectively eliminate session timeouts)

[Naaktgeboren]

Another small glitches in the DNS interface:
8. When I try to create record test IN TXT "v=spf1 redirect=example.com" the system automatically adds a dot at the end to turn it into FQDN, which is not desirable here. The same with "v=spf1 include:example.com ~all". TXT records should be left verbatim (apart from the necessary encoding for TinyDNS).

Otherwise, thanks for the assurance about #7 and the tip with cookies.

[DanL@VPSLink]

Forwarded to our developers for review - thank you for the reports (please keep them coming if you spot further inconsistencies).

[Naaktgeboren]

ad 8. Fixed partially. If I am editing records for domain example.org, then test IN TXT "v=spf1 redirect=example.com" works fine. However, test IN TXT "v=spf1 redirect=example.org" still gets the final dot appended. Looks like the content check for TXT records was slightly corrected, yet I still believe that it would be better to drop it completely. Such is the definition of TXT records: no fixed meaning, no semantics. What is there to check and "correct"?

New one:
9. The system suggests using nameservers ns1.vpslink.com and ns2.vpslink.com. However, the NS records actually created are ns1.dnscloud.com and ns2.dnscloud.com. Similarly, SOA contains ns1.dnscloud.com. The servers are identical, it might be good to use identical names as well.

[DanL@VPSLink]

Updated 8 and 9 added to the list.

[housefull]

Originally Posted by DanL@VPSLink

The Low-Fi version does not make use of menu icons or transition effects, so it should be possible to at least see the icons disappearing when switching from Hi-Fi to Low-fi.

If you are using any version of Internet Explorer, the Hi-Fi version will lack the quick navigation bar at the bottom of the page; however, you should see menu icons and subtle transition effects when you mouse over top menu items.

While we do not have a set timeframe for this feature's inclusion, I have spoken with our developers and I expect that we will support different control center skins in the future (including a revised edition of the skin which you mentioned).




Simple fix - Pending Renewal packages will now display all the same options which active packages display.




The "Web Console" option has been renamed "Java Console".

If the applet prompted you for authentication information, it would indicate that the issue is most likely a matter of connectivity for the applet. If your VPS is not listening for SSH connections on port 22 or your local network is configured to block port 22, the applet may time out or silently fail after prompting for authentication - is it possible either of these conditions may apply?




The variables intended to store package remote access URL's appear to be empty (OpenVZ) or malformed (Xen). Our developers are looking at this issue now and I expect a fix today.

One server is currently offline, but the status of that server on the first page of the control panel indicates "Online".

What determines the server status that is displayed?

Would it be possible to make the message box that is provided for entering ticket details a little larger?

[DanL@VPSLink]

Originally Posted by housefull

One server is currently offline, but the status of that server on the first page of the control panel indicates "Online".

What determines the server status that is displayed?

The status displayed in the control center is pulled from a database - the control panel display should be updated asynchronously whenever you access the control center, however, the operation may time out (as in the case of an issue with the hardware node hosting your VPS) and is designed to fail silently rather than prevent access.

Originally Posted by housefull

Would it be possible to make the message box that is provided for entering ticket details a little larger?

Increased the width - the height could be increased, however, we're looking to avoid vertical scrolling for the most common screen resolutions (i.e. 1280x1024+) while using the control center.

[chriss]

Originally Posted by housefull

One server is currently offline, but the status of that server on the first page of the control panel indicates "Online".

What determines the server status that is displayed?

Would it be possible to make the message box that is provided for entering ticket details a little larger?

hmm... Now where have I seen these questions before?