Bug #801
Use well-formed messages to the user for the Connect UI operation
| Status: | Closed | Start date: | 07/11/2011 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | v0.5.2 |
Description
For every combination of client OS / server OS, use well-formed messages to the user.
All messages must use gettext().
More specifically:
Client/Server:
Windows/Windows: download the rdp file immediately, without any prompts. Rename the file to "1234-192.168.2.1.rdp", where "1234" is the id of the server and "192.168.2.1" its IP. This way the user may choose to store the RDP for later use.
Windows/Linux: "Open an ssh client such as PuTTY to connect to your machine at IP: "
followed by a large green box showing the machine's IP. Beneath the green box:
If you do not have it installed, <a href="...">Download PuTTY</a>"
Linux/Windows: "Use a remote desktop client, such as <a href="http://sourceforge.net/projects/tsclient/"tsclient</a> to connect to your machine at IP:", followed by a large green box containing the link to the RDP file, with the caption "Remote desktop to 192.168.2.1"
Linux/Linux: "Open a terminal and type the following to connect to your machine:"
followed by a large green box that contains "ssh root@192.168.2.1"
It is still not very clear how the UI can propose the username to use (root? user?), since it is not currently available to it.
Related issues
History
#1 Updated by Constantinos Venetsanopoulos almost 13 years ago
- Status changed from New to Closed
The proposable username remains as a questionable problem and will be targeted to a next version. Ticket is closed for now.
#2 Updated by Vangelis Koukis almost 13 years ago
- Status changed from Closed to Assigned
- Target version changed from v0.5.1 to v0.5.2
Re-opening for 0.5.2.
Short-term: Modify the message to list common login names, e.g. "login as 'user' if this is an Ubuntu/Kubuntu/Fedora machine and as 'root' to Debian machines.", or modify the messsage to depend on the value of the OS metadata key. If OS="ubuntu" or OS="kubuntu", then propose the "user" username, else propose the "root" username.
Long-term: How can the UI know the login name to propose for ssh connections?
Proposal: use a UI-specific metadata key, e.g. "loginname", set for each Image individually.
Whenever a new Server is created, it inherits the value of this key along with "OS" based on a mechanism such as the one prescribed in #847.
#3 Updated by Kostas Papadimitriou almost 13 years ago
Short-term: Modify the message to list common login names, e.g. "login as 'user' if this is an Ubuntu/Kubuntu/Fedora machine and as 'root' to Debian machines.", or modify the messsage to depend on the value of the OS metadata key. If OS="ubuntu" or OS="kubuntu", then propose the "user" username, else propose the "root" username.
for ubuntu, kubuntu, fedora username is "user", for other non-windows os values username is "root"
Long-term: How can the UI know the login name to propose for ssh connections?
Proposal: use a UI-specific metadata key, e.g. "loginname", set for each Image individually.
Whenever a new Server is created, it inherits the value of this key along with "OS" based on a mechanism such as the one prescribed in #847.
implemented using "User" metadata key
#4 Updated by Vangelis Koukis almost 13 years ago
- Status changed from Assigned to Closed
This works great and proposes the correct username very nicely.
Closing ticket.