GUI가있는 별도의 노드로 비 GUI 노드를 관리 할 수 있습니까?

우선 설명해 주셔서 감사합니다. 먼저 "파일 액세스"부분을 다룰 것입니다. 개인적으로 처리 된 데이터가 대신 중앙 파일 서버로 푸시되는 방식으로 노드를 스크립팅하고 싶지만 ... 그건 귀하의 질문이 아닙니다. 각 노드에 Samba를 설치하고 일반적인 Windows 공유를 사용할 수 있지만 더 쉬운 방법이 있습니다. 이제 ssh명령 줄에 액세스하기 위해 노드에 연결하는 방법에 익숙하다고 가정합니다 . 이 서비스는 전체 파일 서버 서비스를 포함합니다.

Ubuntu 파일 관리자를 엽니 다 ( "Dock"의 캐비넷 로고). (왼쪽 하단에 "서버에 연결"이라는 항목이 있습니다. 아래 스크린 샷에 강조 표시되어 있습니다. Ubuntu 16.04를 사용하고 있으며 이전 버전에서 약간 다르게 보일 수 있습니다. 찾을 수없는 경우, 14.04에서 찾아 볼 수 있습니다.

이제 더블 클릭하면 다음과 같은 인터페이스가 나타납니다. Ubuntu 12.04의 인터페이스는 당신을 안내했기 때문에 훨씬 더 좋았습니다. 이제 정확히 무엇을 입력해야하는지 알아야합니다. 멍청하지만 여전히. 무엇을 입력해야하는지 안다면 쉽습니다. 분명히 큰 "만약".

So what do you type. Basically, a URL to a resource on the network. To use a Windows Share (Samba in Linux nomenclature), you'd type smb://nameofthesever/nameoftheshare, so apart from the slashes instead of the backslashes and smb: in front, the same as on Windows. However, your nodes do not have Samba, so we are going to use ssh. That looks slightly different: ssh://username@nameofnode/full/path/to/desired/folder. Type what fits for you. You can also use IP addresses instead of the name of the node, I am obviously unfamiliar with your infrastructure.

Press connect and it will ask you for the password of the user. When everything is successful, you end up with a dialog asking for a password, where you will fill in the password of the user you used in the connection string. You should now be seeing the files of that nodes in your graphical interface. You will notice your connection in the left and list with a "eject" button next to it. If you right click on that text, you can add a bookmark so you don't have to do the procedure all over again next time. This might seem cumbersome if you have thousands of nodes, I'm well aware of that. It's basically the equivalent of net use graphically. If you want to make logging in using ssh easier you can use keyfiles for that, because it allows basically passwordless login from one station to another. That is a rather huge topic, but worth it once you get more the hang of Linux.

Now let's tackle your MySQL question. It is hard to generalize, because it does depend a lot on your configuration. In a default installation, MySQL will only listen to localhost, so you wouldn't be able to access it from network. You have to explicitly allow that on the server. Furthermore, you need connection data to access the database. Usernames in MySQL aren't simple usernames, they are always comprised of a host part and as such you won't simply have a user called chris with a password, but you have something like christ@workstation007 and a password, meaning you can only remotely connect from workstation007 with a user namedchris`. Frankly, it's a full blown clusterfuck and very confusing at first. I will make my work easy here and assume you have all that set up right. In that case, it comes down to suggesting software you can use to connect to your MySQL instances. I'm going to recommend two, but they have fully different use cases.

1. phpmyadmin - It basically is a web interface to MySQL databases with really pretty much anything you can think of. Ok, perhaps database design isn't it. Since it's web-based, you usually have a server which has it installed and that server connects to your different MySQL instances. It's great for teams, since no-one actually needs to install any software locally on their desktops.
2. MySQL Workbench - I don't really have experience with this, but it is the official graphical interface for MySQL. Since it's a native program, it might be more to what you are used to.

I understand many things will still be unclear, that's normal. Happened to all of us. Linux isn't hard, Ubuntu even less so. It's just a different mindset. For example, I still don't get why you can't manage your cluster directly from your desktop over the network. Unless the cluster is on a totally cut of network segment, I don't see the need. But, I don't know enough about the infrastructure and your needs, so basically, I'm just guessing.

Hope this helped somehow. Learn Linux, it's worth it! (With the direction Microsoft is taking, you might want to keep an escape path open. ;-) )