* Depending on your clouds performance and the flavors selected it can take more than the normal timeout (60 minutes). with build flavor of 4 cores you should be fine in 30 minutes.
* Depending on your clouds performance and the flavors selected it can take more than the normal timeout (60 minutes). with build flavor of 4 cores you should be fine in 30 minutes.
* When the stack was created successfully nodes need to be rebooted for using updated or custom (SPGW) kernels.
* When the stack was created successfully nodes need to be rebooted for using updated or custom (SPGW) kernels. TODO Rebooting instances by template.
* After reboot the three programs oai_hss, mme and spgw on the respective instances need to be started and the core is up.
* After reboot the three programs oai_hss, mme and spgw on the respective instances need to be started and the core is up. TODO Auto starting the services by template.
Here is the corresponding video for that:
Here is the corresponding video for that:
**6. Connecting eNBs to the core**
**6. Connecting eNBs to the core**
We are about to create eNB images directly in the cloud automatically by heat. Stay tuned.
**7. Connecting
TODO
In princple: first connect the eNB to the VPN by installing keys and starting the process. After that configuration is straight-forward. vEPC is reachable by VPN.
We are planning to create eNB images for different sample H/W directly in the cloud by heat and provide some hardware configuration that were tested successfully. Stay tuned.
