Skip to content

[PSST] New test -- singularity validation #94

Open

Description

@bbockelm

We should copy the singularity validation test from SAM or the pilot. Would see if there is a functional isolation mechanism on the worker node.

Activity

  1. roksys commented on Jun 27, 2017

    @roksys
    Contributor

    Currently there is a default glexec validation from glideinWMS side and it seems to be running according CMS frontend configuration.
    As far as I understood, it runs if GLEXEC_BIN attribute in the factory entry is set.

    Do we need to duplicate this test? Do we need some information from this test to be reported to ES?

  2. bbockelm commented on Jul 3, 2017

    @bbockelm
    Author

    Knowing whether there is functioning isolation is pretty important.

    Is it possible to just get the result from the Singularity / glexec test and advertise it in ES?

  3. roksys commented on Jul 5, 2017

    @roksys
    Contributor

    Default glideinWMS glexec setup script runs after custom scripts. So I can't get result of it.
    I need to find other way as I want to avoid duplicating tests.

    I can add singularity validation script to PSST or just take value from HAS_SINGULARITY.

  4. bbockelm commented on Jul 5, 2017

    @bbockelm
    Author

    Let's just take the value from HAS_SINGULARITY - we can add glexec test support later.

  5. roksys commented on Jul 7, 2017

    @roksys
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions