Currently the runtime build still uses the virtlet's list of dependencies. one apparent issue is that we have to add a copy of the api.pd.go file to bring the interface definition to the same for the two repo.
we should start link Arktos-vm-runtime to Arktos, to solve this hardcopied files. Once the new interfaces were added to the CRI, the Arktps-vm-runtime is no longer a generic one anymore unfortunately and it binds to Arktos anyways.
the work to achieve this should be merely update the build glide.yaml and glide.lock file for a particular Arktos release for the supported level. i.e. release of Arktos matches a release of Arktos-vm-runtime. for dev env, it is free since it is controlled in the dependency glide.yaml file.
Further effort should be update the build-dep to godep and more morden go dep utilities.
Currently the runtime build still uses the virtlet's list of dependencies. one apparent issue is that we have to add a copy of the api.pd.go file to bring the interface definition to the same for the two repo.
we should start link Arktos-vm-runtime to Arktos, to solve this hardcopied files. Once the new interfaces were added to the CRI, the Arktps-vm-runtime is no longer a generic one anymore unfortunately and it binds to Arktos anyways.
the work to achieve this should be merely update the build glide.yaml and glide.lock file for a particular Arktos release for the supported level. i.e. release of Arktos matches a release of Arktos-vm-runtime. for dev env, it is free since it is controlled in the dependency glide.yaml file.
Further effort should be update the build-dep to godep and more morden go dep utilities.