Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Akihiro Suda
@AkihiroSuda
But scalability is not a problem when you use randomized policy
v01dstar
@v01dstar
yes
Akihiro Suda
@AkihiroSuda
because you can launch randomized nmz for each of the node, so there is no interaction between nmz nodes
v01dstar
@v01dstar
cool, that's the next question i want to ask
haha
thanks a lot
Akihiro Suda
@AkihiroSuda
Thank you a lot for looking into our work :smile:
v01dstar
@v01dstar
your project is super cool by the way
Hitoshi Mitake
@mitake
@v01dstar thanks for your interest :)
Akihiro Suda
@AkihiroSuda
也TiDB和TiKV 超酷 :cool:
v01dstar
@v01dstar
haha
thank you
Akihiro Suda
@AkihiroSuda
Please feel free to give us your feedback if you have any further questions and suggestions
v01dstar
@v01dstar
sure
Akihiro Suda
@AkihiroSuda
thanks!
v01dstar
@v01dstar
:smile:
v01dstar
@v01dstar

I found that nmz "container mode" is a very convenient tool to use, it can be easily integrated with CI.
For example:

nmz container run TiKV --name kv1 
nmz container run TiKV --name kv2
nmz container run TiKV --name kv3
nmz container run TiDB

But I also found that nmz doesn't support some docker args like -p. Is there any specific reason for doing this?

v01dstar
@v01dstar
@AkihiroSuda @mitake
Akihiro Suda
@AkihiroSuda
Thank you for trying the container mode
Actually there is no specific reason
Currently, nmz parses CLI flag strings by itself rather than passing them to the docker command
And nmz calls github.com/fsouza/go-dockerclient.CreateContainerOptions() for creating container https://github.com/osrg/namazu/blob/master/nmz/cli/container/run/runflag.go
Due to this implementation approach, currently nmz supports only limited numbers of docker run flags
I'm planning to use os/exec for calling the docker rather than the current approach
Akihiro Suda
@AkihiroSuda
So the current workaround is to use docker run --privileged -p ... instead of nmz container run,
and use nmz inspectors proc or nmz inspectors ethernet within the privileged docker containers
(and of course you can use nmz inspectors fs as well)
v01dstar
@v01dstar
thank you
v01dstar
@v01dstar
I am not sure. Namazu is not in client–server model like docker(docker client <-> docker daemon). So, if we damonize nmz process, it would also surprise some users who may expect nmz will run in background by providing a & flag (eg. nmz container run -d nginx &). Probably, we should inform users the behavior of using -d in our document or through nmz container run --help rather than daemonize nmz.
Akihiro Suda
@AkihiroSuda
OK, thanks
osrg/namazu#158
Akihiro Suda
@AkihiroSuda
@mitake As you might already know, this library seems useful for implementing SCSI inspector: https://github.com/coreos/go-tcmu
Hitoshi Mitake
@mitake
@AkihiroSuda yes, it will be useful if we want to implement this kind of functionalities: https://www.usenix.org/node/186197
Akihiro Suda
@AkihiroSuda
Released Namazu v0.2.1 and Namazu Swarm v0.0.1
img
Namazu Swarm is hosted at https://github.com/osrg/namazu-swarm
Akihiro Suda
@AkihiroSuda
Namazu Swarm rebooted; Python -> Go; Kubernetes -> Docker Swarm-mode...
https://github.com/osrg/namazu-swarm