Env config

[amdfxlucas]

for description see: #5

Its a first working draft and request for comments . Just compile i.e. ScionBandwidthTester and note the '.env' file which is generated next to docker-compose.yml and the new 'environment:' sections for each service in the compose file.
You can change any of the ENV variables and simply 'docker compose stop / start' to run the simulation with the new settings, rather than recompiling & rebuilding any images

---

This change is 

[lschulz]

Works as you describe it on my system.

Have you thought about feature dependencies? For example, SCMP authentication and ID-INT require DRKey.

Reviewable status: 0 of 5 files reviewed, 3 unresolved discussions (waiting on @amdfxlucas)

---

seedemu/compiler/Docker.py line 418 at r1 (raw file):

            @brief retuns ENV variables defined in the given scope
        """
        import toolz

Is this dependency worth it? (also why not import at the top of the file?) The expression below isn't very readable anyway.

---

seedemu/compiler/Docker.py line 434 at r1 (raw file):

        """
                
        from cawdrey import frozendict

Is there a good reason to import this type? Wouldn't a normal dict do the job?

---

seedemu/core/AutonomousSystem.py line 48 at r1 (raw file):

        self.__as_features = {}

    def setFeatures(self, key_val: Optional[Union[Dict[str, str], tuple]] = None, key: Optional[str] = None, val: Optional[str] = None):

Have you considered taking keyword arguments (**kwargs), so you could do something like setFeatures(bfd=False)?

[amdfxlucas]

Works as you describe it on my system.

Have you thought about feature dependencies? For example, SCMP authentication and ID-INT require DRKey.

Yes, with the reification of Options we'd have a good starting point to cater for mutual interdependencies or exclusion ...