Location Geo-tagging
All resources in your test environment (test harnesses, execution engines, testbeds, and topologies) are associated with a location/site/building (for example, SJC/SJC23) to properly track your resource dependencies.
You must ensure the location of your lab/testbed is registered in XPRESSO, and is correctly associated with your test environment when registered.
NOTE:
XPRESSO has a number of predefined location (sites/buildings) with the initial installation of the system. If these sites do not match the location of your current testing environment, you will need to register your location in XPRESSO.
Why Location Geo-tagging Matters?
All resources in your test environment are associated with a location/site/building to:
Allow the system to geo-fence and prevent users from making trivial mistakes (for example, launching a test run against a testbed located in Asia using an execution engine located in North America and the source code is located on a network server mounted in Europe).
Ensure that Job executions are restricted by a sensible location match up and hence, reduce delays in executions and errors of non-reachable resources/environments due to location restrictions.
Allows the System and Group Administrator to properly track your resource dependencies to ensure smooth and accurate operations and to perform graceful site-specific or bulk actions based on a geo-tagged location (for example, scheduled lab maintenance or downtime required during a CMW).
Location Geo-tag Hierarchy
Each location geo-tag has an assigned hierarchy as follows:
NOTE:
When a registered object is associated with a location geo-tag as shown in the example above, it is considered to be "location sensitive". When these location sensitive resources are used together, they must all fall under the same geo-fence.
- ALL is a special "building" location tag that is created automatically and services the whole site. For example, if a testbed is accessible by the whole site, marking it using the building ALL tag would enable it to be used in conjunction with any other resources within that site.
EXAMPLE:
If a testbed is registered to be located in SJC/SJC-23, and a pyATS virtual environment is registered to be in RTP/RTP-6, they cannot be associated to the same Job/Job Profile, or be selected for Job Request execution. A testbed located in SJC/SJC-23 can only be grouped with a pyATS virtual environment registered to be in SJC.
Managing your Location Details
You need to make sure the location of your lab/testbeds is registered in XPRESSO. If your lab location is missing from the available list of registered locations, you can make a formal request to add the location/site/building.
NOTE:
Only a System Administrator can add a location (site & building) in XPRESSO.
To Manage your Location Details:
This procedure covers how to: (applies to all Member roles)
- Confirm your lab/testbed location (and all building sites) are registered in XPRESSO.
- Make a request to add additional buildings if your location details are not up-to-date.
- Make a request to add a new location in the event your test site is not registered in XPRESSO.
The System Administrator can also perform the following location-specific actions:
- Add a new lab/testbed location.
- Edit the Location description details.
- Add additional buildings to the location details.
- Delete a single registered location, or perform bulk deletions.
CAUTION!
Although XPRESSO is designed to prevent geo-location errors, do not register unreasonable test environment location details (e.g., different continent locations) to circumvent/bypass XPRESSO's location validation. Failure to comply may result in excessive test run execution times and slow response (communication) times.
- From the Main Navigation Bar, choose Main Menu→ENVIRONMENT→Locations to open the Registered Locations page.
NOTE 1:
This page lists all registered locations for all Groups in XPRESSO; not just the locations registered for your specific Group.
NOTE 2:
Ignore the checkbox to the left of the Location column. This checkbox is reserved for the System Administrator use and allows them to perform bulk deletions of lab/testbed locations.
- Scroll through the list of available Registered Locations to confirm your lab/testbed location is listed. If required, click on the right-arrow icon button next to Location column to reveal further details about each location.
- If your lab/testbed location is identified in XPRESSO, go to step 3.
- If your lab/testbed location is not specified, go to step 5.
- Confirm that the specific building site(s) are accounted for in the location details.
- If all building sites are accounted for, no further action is required.
- If a building site is missing, click on the Request Building floating action button located on the right side of the Location page. The Request to Add New Building to Site (Name-of-Site) form opens.
Fill in all required fields on the form and click the Send Request button to complete the action.
If your lab/testbed location is not registered in XPRESSO, click the Request a Location floating action button located on the right side of the Location page. The Request a New Location form opens.
Fill in all required fields on the form and click the Send Request button to complete the action.
NOTE:
You can add all required building sites by clicking the Add New Building button.
- This step is reserved for System Administrator use. As required, click one of the following floating actions buttons to:
- Add Location: To Add a new lab/testbed location.
- Edit: To change the Location description details.
- Add Building: To add additional building to an existing lab/testbed location.
- Delete: To remove a single location from XPRESSO.
- To bulk delete several test sites, click the checkbox adjacent to each site you want to delete and click Delete.