| | 148 | |
| | 149 | == Config request path == |
| | 150 | |
| | 151 | Given the API/URls the request sequence should go as follows: |
| | 152 | |
| | 153 | === Pnodes === |
| | 154 | |
| | 155 | 1. http://config:5000/computer/<name>. The pnode checks the "type" field and sees that it's a pnode. So it requests information about containers embedded in it next. |
| | 156 | 2. http://config:5000/embed/pnode-0000. The pnode gets a list of nodes embedded in it. |
| | 157 | 3. For each embedded node: http://config:5000/computer/<embedded node name> to get the container specific information (like path to qemu image) and embedded node interfaces so it can setup the virtual networking prior to launching the containers. |
| | 158 | |
| | 159 | |
| | 160 | === Nodes (containers) === |
| | 161 | |
| | 162 | 1. http://config:5000/computer/<name>. To get at least the hostname and maybe the networking information if the system used to spawn the containers does not set that. |
| | 163 | 2. http://config:5000/moutns. Know what remote file systems to mount locally. Again, this may be taken care of by the vm spawn system (it can be when using Vagrant for instance.) |
| | 164 | 3. http://config:5000/users. Get the account information to create the users. |
| | 165 | 4. TBD/other cool stuff. |
