This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
vims_functional_testing [2015/03/19 13:54] Martin Taylor [Deployment and Test Process] |
vims_functional_testing [2015/04/10 09:06] Martin Taylor [Software Components of the vIMS] |
||
---|---|---|---|
Line 22: | Line 22: | ||
* [[https://github.com/Metaswitch/ellis|Ellis]] - provides a provisioning API enabling subscribers to be configured in Homestead and Homer. | * [[https://github.com/Metaswitch/ellis|Ellis]] - provides a provisioning API enabling subscribers to be configured in Homestead and Homer. | ||
* [[https://github.com/Metaswitch/clearwater-live-test|Clearwater-live-test]] - emulates SIP endpoints to enable automated functional testing of vIMS. | * [[https://github.com/Metaswitch/clearwater-live-test|Clearwater-live-test]] - emulates SIP endpoints to enable automated functional testing of vIMS. | ||
- | * [[https://www.isc.org/downloads/bind/|Bind]] - provides a DNS server to enable the components of Clearwater to find each other. | + | * [[https://www.isc.org/downloads/bind/|BIND]] - provides a DNS server to enable the components of Clearwater to find each other. |
Each of these components will be instantiated as a single virtual machine. | Each of these components will be instantiated as a single virtual machine. | ||
+ | |||
+ | ===== Networking Requirements ===== | ||
+ | All of the software components listed above need to be able to connect to each via IP. There are no other specific networking requirements. It does not matter how the IP connectivity is provided, i.e. whether it uses VLAN, VXLAN, GRE etc. | ||
===== Deployment and Test Process ===== | ===== Deployment and Test Process ===== | ||
We will use OpenStack Heat to automate the deployment of the vIMS and test components, via the following steps: | We will use OpenStack Heat to automate the deployment of the vIMS and test components, via the following steps: |