Technical Process
Participants should be familiar with the technical process. In this competition, we provide isolated, independent and audited networks and servers. The following are essential technical processes:
2.1.1 Pre-contest environmental confirmation
All participating teams are suggested to test the environment on site , to see if there's configuration adjustment needed during the designated period of time. For all related issues, refer to Chapter 5, Technical Service Request Means.
2.1.2 Access to the environment
Only through the login server(intro page here), can participants log in to the development and deployment servers ; while the communication between the two servers is not restricted.
Open Login Server by brower on the terminal and login in by the given password;
Click the"Host Operation "from left side ,choose the server you want to connect;
You can connect the WINDOWS SERVER account with RDP or HTML BROWER or local client when your terminal os is Windows with USMSSO(download here) installed ; If your terminal os is not Windows (like MACOS or LINUX), using "HTML BROWER" is the only way;
You can connect the UBUNTU SERVER account with VNC or SSH by HTML BROWER or local client when your terminal os is Windows with USMSSO (download here) installed ;
If your terminal os is not Windows (like MACOS or LINUX), using "HTML BROWER" is the only way.
The WINDOWS SERVER or UBUNTU SERVER only supports one user login at the same time. If the user tries to log in at the same time, the user who has logged in will lose the connection.
2.1.3 Backup
Backup request is strongly recommended during the 80 hours. When making a backup request to technical support group(TSG), the participating teams should save the work and shut down the server first. The backup service could be normally completed within 5 minutes, and the backup recovery could be completed within 20 minutes depending on the amount of data.
For files and code’s backup, network file storage service and GIT service are recommended.
2.1.4 Quota expansion
Every participant will be granted of 5GB network file storage; development and deployment servers have Ubuntu 20+30G capacity or Windows 60G capacity. If the above storage space cannot meet the reasonal needs of development and deployment, the request for expanding the resource may be proposed according to actual needs.
Last updated
Was this helpful?