Skip to content
  • Em Sharnoff's avatar
    Flatten & unify component structure (#961) · a2f53e32
    Em Sharnoff authored
    This basically encompasses two logical changes:
    
    1. More fully integrating neonvm into the rest of the repository; and
    2. Using a consistent directory structure for all components
    
    The new structure is:
    
    - All components get their own top-level directory (e.g.
      autoscaler-agent, neonvm-controller, vm-builder)
    - Inside the directory, there is:
      - cmd/ - directory containing main.go for the component
      - Dockerfile - for building the component
      - *.yaml - various YAML files for deploying, if applicable
    
    Additionally, all code outside the cmd package are moved into the pkg/
    subdirectory. In particular, there is now pkg/neonvm/.
    
    Also of note: neonvm/hack/kernel has been relocated to the new top-level
    directory neonvm-kernel/.
    
    Under this structure, the user-visible changes are:
    
    1. Introduction of new YAML: neonvm-controller.yaml
    2. Introduction of new YAML: neonvm-vxlan-controller.yaml
    3. neonvm.yaml now is *mostly* just the CRD.
    
    The primary reasons for this change are:
    
    1. Because it's been long enough since we moved the neonvm repository
       here that we might as well make it more well-integrated.
    2. Because as we look to potentially add components in other languages,
       we need a directory structure that supports it.
    a2f53e32
Loading