SDX 管理ドメイン
サブドメインへのリソース割り当ての例
| CPUコア | 10 |
| スループット (Mbps) | 18500 |
| メモリ (MB) | 87300 |
| ディスクスペース (GB) | 840 |
| SSLチップ | 36 |
| インスタンス | 36 |
| CPUコア | 5 |
| スループット (Mbps) | 1024 |
| メモリ (MB) | 2048 |
| ディスク容量 (GB) | 40 |
| SSLチップ | 8 |
| インスタンス | 4 |
Something went wrong opening the GitHub link. Please try again.
| CPUコア | 10 |
| スループット (Mbps) | 18500 |
| メモリ (MB) | 87300 |
| ディスクスペース (GB) | 840 |
| SSLチップ | 36 |
| インスタンス | 36 |
| CPUコア | 5 |
| スループット (Mbps) | 1024 |
| メモリ (MB) | 2048 |
| ディスク容量 (GB) | 40 |
| SSLチップ | 8 |
| インスタンス | 4 |
Commit Guidelines
Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file.
Private Small Team
The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository.
Something went wrong opening the GitHub link. Please try again.