[trustable-software] Environments was RE: trustable-software Digest, Vol 18, Issue 2

[rupertb at cix.co.uk]

A couple of thoughts on environments 

Environments must have a purpose -  dev test "prod copy" etc
But with that must also go a scope/feature/capacity - e.g.  Dev has no resilience and only xx storage
This can be defined by some sort of expected topology and the build scripts to make it

As regards the wider t.list I think the notion of a t.simulation might be  in order - its not quite the same as a set of tests but somewhat intertwingled.  Perhaps more significant in a control system (trains/planes etc)  or a CAD/CAM context where you don't actually want to make a physical part to test



-R


-----Original Message-----
From: trustable-software <trustable-software-bounces at lists.trustable.io> On Behalf Of trustable-software-request at lists.trustable.io
Sent: 17 March 2018 12:00
To: trustable-software at lists.trustable.io
Subject: trustable-software Digest, Vol 18, Issue 2

Send trustable-software mailing list submissions to
	trustable-software at lists.trustable.io

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.trustable.io/cgi-bin/mailman/listinfo/trustable-software

or, via email, send a message with subject or body 'help' to
	trustable-software-request at lists.trustable.io

You can reach the person managing the list at
	trustable-software-owner at lists.trustable.io

When replying, please edit your Subject line so it is more specific than "Re: Contents of trustable-software digest..."


Today's Topics:

   1. Environments for Trustable (trustable at panic.fluff.org)


----------------------------------------------------------------------

Message: 1
Date: Fri, 16 Mar 2018 16:04:56 +0000 (GMT)
From: trustable at panic.fluff.org
To: Trustable software engineering discussion
	<trustable-software at lists.trustable.io>
Subject: [trustable-software] Environments for Trustable
Message-ID: <Pine.LNX.4.64.1803161602470.21714 at trinity.fluff.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

   I've been looking at the Trustable Workflow
     https://gitlab.com/trustable/workflow/blob/master/markdown/basics.md
and as part of the work here looking CI/CD issues and particularly this is moving the discussion from Tools to requirements and then we can do a mapping to what the tool choices should provision..

However, one thing missing in that discussion is the concept of an environment.

None of this can occur without the provision of an environment in which you can execute things like the t.build or the t.function which can be validated by t.test to confirm that the t.requirements have been satisfied the outstanding requirements.

So here is the question.. What is an environment ? It is something for the management of risk during testing and development. Frequently when executing on the cloud an environment is a VPC in effect a method of isolating the impact of resources one from another in which it is possible to orchestrate and instantiate software artefacts.

Within an embedded environment I think we might have environments we use for construction.. in effect a cross compiler environment which produces the t.build t.artefacts..However this environment might be different from where some tests are performed.. for example we might do this in a emulation environment with QEMU being an ARM CPU emulation on x86_64, as we can spin up many of thse so shortening the test cycle before going on to doing a execution and validation on the real cpu board.

So how do we define an environment across all these spaces.. Any ideas ??
Edmund

--
========================================================================
Edmund J. Sutcliffe                     Thoughtful Solutions; Creatively
<edmunds at panic.fluff.org>               Implemented and Communicated
<http://panic.fluff.org>                +44 (0) 7976 938841




------------------------------

Subject: Digest Footer

_______________________________________________
trustable-software mailing list
trustable-software at lists.trustable.io
https://lists.trustable.io/cgi-bin/mailman/listinfo/trustable-software


------------------------------

End of trustable-software Digest, Vol 18, Issue 2
*************************************************