Directory structure suggestion

[Metallion]

With centos 7 support and the new Jenkins 2 CI, there have been some concerns about how to use the directory structure. Therefore it's a good time to decide a clear policy together. To start the conversation, I suggest the following structure:

Structure decided after meeting:

openvnet/
├── ci
│   ├── ci_cluster_build
│   │   ├── jenkins2
│   │   └── packer
│   │       ├── build_kvm.sh
│   │       └── build_virtualbox.sh
│   └── integration_test
├── client
├── deployment
│   ├── conf_files
│   └── packagebuild
│       └── rhel
│           ├── docker
│           ├── rpmbuild
│           │   ├── third_party
│           │   │   ├── build.sh
│           │   │   ├── openvswitch
│           │   │   │   ├── conf.el6
│           │   │   │   ├── conf.el7
│           │   │   │   └── rpmbuild.sh
│           │   │   └── ruby
│           │   │       ├── conf.el6
│           │   │       ├── conf.el7
│           │   │       ├── rpmbuild.sh
│           │   │       └── ruby.spec
│           │   └── vnet
│           │       ├── build.sh
│           │       ├── conf.el6
│           │       ├── conf.el7
│           │       └── openvnet.spec
│           └── yum_repositories
│               ├── develop
│               └── stable
├── docs
└── vnet

[Metallion]

In my opinion the integration_test/bootstrap directory from #502 should be moved to CI/ci_cluster_build/packer_virtualbox

[akirapop]

Fundamentally, the scripts only build packer templates and then have packer run using them. And packer itself largely runs virtualbox. So the suggested name seems appropriate.

[unakatsuo]

I think "ci/ci_cluster" is enough.

openvnet/
├── ci
│   ├── ci_cluster
│   │   ├── jenkins2