Interesting -- it looks like I didn't reimplement setupPrivateMounts() when I changed the architecture of MiniNExT ~1.5 years ago. My apologizes -- I haven't been able to put nearly as much time into this project as I'd hoped.

However, the process required to set up a private mount is very similar to the logic used to setup the private run and private log mounts in node.py

For instance, the following code is used for setting up a container's private log directory, binding it to the path provided in privateLogDir (a string).

    def setupPrivateLogs(self, privateLogDir):
        ...
        # Create the PathProperties and MountProperties objects
        logPathProperties = PathProperties(path=privateLogDir,
                                           perms=getObjectPerms('/var/log'),
                                           create=True,
                                           createRecursive=True,
                                           setPerms=False)
        mount = MountProperties(target='/var/log', source=logPathProperties)

        # Pass the created mountPoint off...
        self.setupMountPoint(mount)

Note that you could also just create a mount without defining a path properties object if you don't need the mount point to be created / permissions to be set / etc.

mount = MountProperties(target='/var/log', source='/var/log/mininext/container1')
self.setupMountPoint(mount)

You should be able to call setupMountPoint and create a MountProperties object outside of node.py (you can do it in your topo setup), or you could implement setupPrivateMounts().

Let me know if this makes sense and/or if I've misunderstood your question.

setupPrivateMounts() method implementation is missing from net.py #7

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions