arky / iiab-dev-mode Goto Github PK

This repository provides a quick setup of Internet-in-a-Box (IIAB) development environment using Vagrant.

internet-in-a-box vagrant-machine virtualbox ansible vagrant ubuntu centos fedora debian

iiab-dev-mode's Introduction

Internet-in-a-Box (IIAB) Development Mode

This repository provides a quick setup of Internet-in-a-Box (IIAB) development environment using Vagrant. You will need a computer with virtualization enabled and git, Vagrant (2.0 or later) and VirtualBox installed.

Requirements

git
Vagrant (2.0 or later)
Virtualbox
Editor (Atom, Emacs, Vi etc)
Ansible
Ansible-lint and [Ansible-review)[https://github.com/willthames/ansible-review] tools

Usage

Check out this repository and its submodules on to your development machine. git clone --recursive https://github.com/arky/iiab-dev-mode.git
Change directory into 'iiab-dev-mode' with cd iiab-dev-mode. You can update all the submodules to latest master using git submodule foreach git pull origin master
Setup a vagrant machine with vagrant up and provision it with vagrant provision. Please select the available bridge network interface (wlan0 or eth0) that connects your host machine to the Internet.
You can now connect to your vagrant machine with vagrant ssh. All your local development files available as shared folder in /opt/iiab directory.

You can setup IIAB from the Ansible Playbooks following the installation wiki page.

   cd /opt/iiab/iiab/scripts/
   ./ansible

   cd /opt/iiab/iiab/
   ./runansible

   cd /opt/iiab/iiab-admin-console/
   ./install

   cd /opt/iiab/iiab-menu/
   ./cp-menus

Hack away! You can commit your local changes and send pull request to IIAB project by setting a default git remote push setting with cd <repo> && git remote set-url --push origin [email protected]:<your_username>/<your_forked_iiab_repo_name>.git. Learn more by reading this blog post and Working with Remotes in Pro Git Book
Once you are done, you can stop your vagrant machine with vagrant halt or remove it completely with vagrant destroy.

iiab-dev-mode's People

Contributors

Stargazers

Watchers

Forkers

veeara282

iiab-dev-mode's Issues

Clean Up For Stable Release

This code base seems to be stable. I have been using this for over a month. Time to do a through cleanup and make a stable release.

Vagrant doesn't work on Ubuntu 18.04

As part of my team project (main pull request here), we tried to set up a staging server on an Ubuntu 18.04 virtual machine using Vagrant. While doing so, we ran into problems using vagrant up. We eventually switched to installing IIAB directly on the VM, but would like to provide the steps we took for the IIAB project's benefit.

The problem was that vagrant up was failing with the error Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory. We addressed this error by running the following commands:

vagrant plugin install vagrant-libvirt
sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager
sudo adduser `whoami` libvirt
sudo adduser `whoami` libvirt-qemu
sudo /etc/init.d/libvirtd restart

and then logging out and back in to apply group membership to the current user. (Source)

However, this did not solve the problem. We are still getting this error:

Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: 
invalid argument: could not find capabilities for domaintype=kvm

Vagrantfile: Default PWD /opt/iiab

Make '/opt/iiab' default change directory. When a user does 'vagrant ssh'. The default pwd should /opt/iiab

Disable 'Shallow' mode

You can't pull your changes when a repo is checked out in shallow mode. I think we have revert this setting on local repos.

Rsync fails with symlinks

Rsync seems have trouble with symlinks.

Error: symlink has no referent: "iiab-dev-mode/iiab/roles/httpd/templates/iiab-console.conf.j2"
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]

ls -l iiab/roles/httpd/templates/iiab-console.conf.j2
lrwxrwxrwx 1 arky root 76 Oct 1 11:53 iiab/roles/httpd/templates/iiab-console.conf.j2 -> /opt/schoolserver/xsce/roles/xsce-admin/templates/console/xs-console.conf.j2

[Feature] Git hook to call `git submodule update` automatically.

Add a Git hook to call git submodule update automatically. Perhaps this would be a good idea to force update of all the submodules on checkout or change.

Perhaps a 'post-checkout' git hook to automatically update all submodules would be a good idea.

post-checkout

This hook is invoked when a git-checkout is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of git-checkout.

Set Submodules track master branch instead HEAD

Please set all submodules to track master branch by default. At the moment they track HEAD of the individual branches.

Commit hooks for Ansible linting and testing

Add ansible linting and code review tests at commit time. Add notes to README about ansible-lint and ansible-review module setup.

Use : Commit hooks with 'ansible-review -q' option.

git ls-files | xargs ansible-review
git diff master | ansible-review