Sure,

 

The main objective is just to verify that our deployment is able to communicate between all existing nodes.

That is we are just planning to perform a basic ping test on them + the ssh connection in different stages.

Added to that we want to create different kind of networks besides the default VLAN that always is working and play a little bit with existing IP’s given by the user, emulating a real use scenario.

 

We don’t want to include more tests on the sanity since the suite needs to be executed as fast as possible.

 

BR

 

Elio

 

From: Victor Rodriguez [mailto:vm.rod25@gmail.com]
Sent: Wednesday, May 1, 2019 10:47 AM
To: Martinez Monroy, Elio <elio.martinez.monroy@intel.com>
Cc: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Networking TC to be included in the Sanity Suite

 

Hi Elio 

 

Thanks a lot for the heads up, could you please provide a bit of description of each test case . I knwo some are very clear but I am not network expert :S

 

Thanks

 

Victor R

 

 

On Wed, May 1, 2019 at 10:42 AM Martinez Monroy, Elio <elio.martinez.monroy@intel.com> wrote:

Hello guys

 

I’m proposing to include the following TC to the sanity Suite, please let me know your thoughts

 

·        Ping/ssh  between controllers

·        Ping/ssh from controller to compute

·        Ping/ssh from controller to the storage node

·        Ping/ssh from compute to storage node

·        Ping/ssh from instance to compute

·        Ping/ssh from instance to instance

·        Vxlan creation

·        Flat creation

·        Bring down/up management/OAM/data

·        IP change for all previous mentioned networks if is possible

 

 

 

cid:image001.png@01CF8BAC.3B4C5DD0      Martinez Monroy, Elio.

                       QA Engineer.

                       Open-source Technology Center

 

 

 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss