Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC ObjectScale 1.2.x Administration Guide

About the ObjectScale service pod

Working with the service pod in ObjectScale

ObjectScale utilizes a service pod to provide:

  • A CLI-based "working environment" that can be used to troubleshoot issues.
  • An always-available endpoint for troubleshooting-related remote access - a "gateway" to the rest of the system.
  • Tools and access required to troubleshoot issues, particularly advanced-level troubleshooting.

Customers and support personnel can connect into the service pod to execute troubleshooting or CLI-based maintenance tasks. The service pod is their primary environment for access - potentially the only environment they access directly while investigating an issue.

The service pod provides a Linux-based working environment with the tools and access needed to maintain the rest of the product. This would be, for example, the most common way to access kubectl and kubernetes commands, to examine system logs (from a CLI level), and as a gateway to the rest of the system.

This service pod is deployed on ObjectScale installations by default, and is expected to be running to provide remote support. The service pod also hosts the SupportAssist and remote-access functionality, although SupportAssist is not required to use the service pod.

The pod can be upgraded independently from the rest of the ObjectScale system, to provide updates as needed.

This pod also contains the utilities needed to troubleshoot the product, including standard Linux utilities (grep, awk, top, ping, ssh), Kubernetes utilities (kubectl), as well as serviceability tools and libraries developed specifically for ObjectScale.

Finally, customers and support personnel access the service pod using kubectl exec and, if remote-assist is enabled, SupportLink and SSH. Review the example in the following section to see how to access the service pod using kubectl exec.

Accessing the service pod and service tools

ObjectScale contains a service pod available in each ObjectScale instance. The service pod provides CLI access to a Linux shell environment inside the Kubernetes network.

The service pod is designed for use during troubleshooting. To access the service pod run the following command to find the name of the service pod in the ObjectScale instance:
kubectl -n <OBJECTSCALE_NAMESPACE> get pods | grep objectscale-manager-service-pod
To access the service pod execute the kubectl exec command using similar syntax. Replace the pod name with the name of the service pod found above.
kubectl -n <OBJECTSCALE_NAMESPACE> exec -it objectscale-manager-service-pod-5966667f5f-dxn85 -- bash

Expected output:

objectscale-manager-service-pod-5966667f5f-dxn85: /#

From here you are able to run supported service tools from the service pod. For example, the svc_log and the svc_store tools.

Service tools in this release

Name Description

svc_alerts

For listing alerts

svc_bucket

Bucket listing/details

svc_chunk

Chunk troubleshooting

svc_collect

Log/data collection

svc_dt

DT Troubleshooting tools (search, status)

svc_exec

Run CLI commands across pods

svc_fluxFor running flux queries
svc_gc

GC stats/troubleshooting

svc_hcFor running/checking the healthcheck
svc_log

Log CLI - search, stats, save

svc_objectFor checking object related info
svc_param

CMF param list/set/revert

svc_pod

Pod details, other actions

svc_request

Request log utilities

svc_rest

Run REST API commands

svc_store

Object store details, other actions

svc_task

Object store task utilities

svc_versionFor checking app/object store/kubernetes

version

kpi

Object store workload details, performance indicators


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\