Execution Environment Tests

T0001 – SA_PLM_ADMIN_LOCK/SA_PLM_ADMIN_UNLOCK

Setup

TES-001

Pre-test

  • Verify that the SAF aware application is running in active mode on payload 1
  • Verify that apache is running on payload 1 (/etc/init.d/apache2 status)
  • Verify that plmcd is running on payload 1 and 2

Test

  • Issue SA_PLM_ADMIN_LOCK in IMM
    immadm -o 1 safEE=PL-7,safHE=blade_7,safDomain=domain_1
  • Verify the outcome 1-4
  • Issue SA_PLM_ADMIN_UNLOCK
    immadm -o 2 safEE=PL-7,safHE=blade_7,safDomain=domain_1
  • Verify the outcome 5-8

Outcome

  1. OpenSAF shuts down on payload 1
    # ps -ef | grep opensaf
  2. Apache shuts down on payload 1
  3. SAF aware application shuts down on payload 1
  4. The SAF aware application becomes active on payload 2
  5. Apache starts on payload 1
  6. SAF aware application starts on payload 1 in standby mode
  7. Opensaf is running again on payload 1


T0002 SA_PLM_ADMIN_LOCK_INSTANTIATION

Setup

TES-001

Pre-test

  • Verify that the SAF aware application is running in active mode on payload 2
  • Verify that OpenSAF and Apache are running on payload 1
  • Verify that plmcd is running on payload 1 and 2

Test

  • Issue SA_PLM_ADMIN_LOCK on payload 2 in IMM
  • Verify outcome 1-4
  • Issue SA_PLM_ADMIN_LOCK_INSTANTIATION in IMM.
  • Verify outcome 5-6.

Outcome

  1. OpenSAF shuts down on payload 2
    # ps -ef | grep opensaf
  2. Apache shuts down on payload 2
  3. SAF aware application shuts down on payload 2
  4. The SAF aware application becomes active on payload 1
  5. Payload 2 shuts down
  6. The OS does NOT execute.


T0003 – SA_PLM_ADMIN_UNLOCK_INSTANTIATION

Setup

TES-001

Pre-test

  • Verify that the OS is not executing on payload 2
  • Verify that immlist on payload 2 gives you the admin state 3 (SA_PLM_EE_ADMIN_LOCKED_INSTANTIATION)

Test

  • Issue a SA_PLM_ADMIN_UNLOCK_INSTANTIATION on payload 2 in IMM
  • Verify outcome 1-4
  • Issue a SA_PLM_ADMIN_UNLOCK
  • Verify outcome 5-7

Outcome

  1. The admin state for the EE of payload 2 becomes locked
  2. The admin operation doesn't return any error messages. If it returns SA_AIS_ERR_DEPLOYMENT the management lost flag has to be set.
  3. The OS on payload 2 will reboot
  4. The EE's present state becomes instantiated, the admin state is locked, the operational state is enabled but the readiness state is out of service
  5. The EE readiness state becomes in service and the admin state is unlocked
  6. The demo app is starting again in standby mode
  7. Apache is again executing on the node


T0004 – SA_PLM_ADMIN_SHUTDOWN

Setup

TES-001

Pre-test

  • Verify that the SAF aware application is running in active mode on payload 1
  • Verify that plmcd and osaf are running on payload 1 and 2.
  • Verify that Payload 1 EE has the admin state unlocked, operational state enabled and presence state instantiated

Test

  • Issue SA_PLM_ADMIN_SHUTDOWN in IMM on payload 1's EE

Outcome

  1. The SAF aware application becomes active on payload 2
  2. The OS on payload 1 starts shutting down
  3. The administrative state transitions to shutting-down (4) and the readiness state to stopping (3)
  4. Administrative state transitions to locked and the readiness state to out-of-service


T0005 – Lock & Unlock Controllers

Setup

TES-001 With controller 1 being active

Pre-test

Verify that Controller 1 is active and Controller 2 is standby
# clear; /etc/init.d/opensafd status

Test

  • Issue a lock on Controller 1 (SC-5 here)
    immadm -o 1 safEE=SC-5,safDomain=domain_1
  • Verify that controller 1 doesn't provide any services by runnig the following on controller 2
    # clear; /etc/init.d/opensafd status
  • Unlock controller 1
    immadm -o 2 safEE=SC-5,safDomain=domain_1
  • Verify that controller 1 is providing service again and that it is running in standby mode
    # clear; /etc/init.d/opensafd status


T0006 – Unlock and Lock a payload whose dependencies are not defined

Pre-test

  • Verify that plmcd is running on the payload.
  • Get the status of the payload using immlist.

Test

  • Unlock the payload (PL-15)
  • immadm -o 2 safEE=PL-15,safDomain=domain_1
  • Verify the services are running, checksafd and amf_demo
  • lock the payload
  • immadm -o 1 safEE=PL-15,safDomain=domain_1
  • Verify the services are not running
  • Verify the status
  • immlist safEE=PL-15,safDomain=domain_1

T0007 – Lock a HE whose EE is not dependent on it and Lock a HE whose EE is dependent on it

Pre-test

  • Verify the machines are in a clean state.
  • Clean means - ** HE's are IN_SERVICE, ACTIVE, ENABLED and UNLOCKED with no management flags ** EE's are IN_SERVICE, INSTANTIATED, ENABLED and UNLOCKED with no management flags ** All the services are running in proper ACTIVE/STANDBY mode

Test

  • ps -ef | egrep "opensaf|openhpid|plmcd|checksaf|amf_demo|snmpd"
  • immfind | grep saf[HE]E | grep -v saf[HE]EType
  • for ent in immfind | grep saf[HE]E | grep -v saf[HE]EType
  • do
  • echo "Output of immlist $ent"
  • immlist $ent
  • echo "====================================================================================="
  • done | more
  • immadm -o 1 safHE=blade_15,safDomain=domain_1
  • immlist safHE=blade_15,safDomain=domain_1
  • Expect the above state to be OUT_OF_SERVICE, ACTIVE, ENABLED, LOCKED with no management flags
  • immlist safEE=PL-15,safDomain=domain_1
  • Expect the above state to be IN_SERVICE, INSTANTIATED, ENABLED and UNLOCKED with no management flags
  • immlist safHE=blade_16,safDomain=domain_1
  • Expect the above state to be OUT_OF_SERVICE, ACTIVE, ENABLED, LOCKED with no management flags
  • Expect the machine to go into the maintenance mode, reboot.
  • immlist safEE=PL-16,safDomain=domain_1
  • Expect the above state to be OUT_OF_SERVICE, INSTANTIATING, ENABLED and LOCKED with management flags


Back to testing =>

Last modified by ehsjoar, 06/07/10 12:58:37 (2 years ago)