jasongiedymin / collective Goto Github PK

Add docker registry to chef-zero node. Things to consider:

• chef-zero node doesn't have lxc (yet)
• chef-zero node needs docker installed

If Travis is doable, lets do it.

vagrant -> ubuntu -> docker -> travis

after that, we can try to force travis to use docker instead of whatever it does today

Deploy strider on DevStack

Need rake download:baseboxes

But first see what is needed for openstack/devstack.

Install via mainfest script DevStack

Similar to how the current cluster command works but will at startup run the provisioning.

Will involve specifying config info at the node level

On the chef server, move from the git cookbook to berkshelf. Manifest is shared so this can be done from the host and the manage_chef.sh script can upload to the server (as it is executed on the chef server).

Add Cluster config to specify 'unmanaged' machines such as bare metal

# core.yml
clusters: 
  - cluster:
      name: 'jnet'
      managed: false # <= here we flag that this cluster is not managed via vagrant
                     #    and that we expect the machines to be when interacting with it
      admin_account: admin # under a vagrant managed box, the user is vagrant
                          # this is ignored if managed

Kernel drivers are not being loaded if you install Mavericks. Work around is to re-install vbox, until the next reboot. Then your up the creek again. Need a fix.

Test creating VMs in DevStack and local OpenStack (cluster:base)

Depends on Issue #10 to be complete first.

The Node1 vm should install OpenStack via the chef server, not DevStack. This server install will be production like to give us a leg up on getting our environment ready when that time comes.

I'd like nothing more than to design it myself, and i may still do it :-)

But seems to be a good alternative that is 'mainstream'.

Would like to see better use of typography and add some more 'response' to the elements.

• this one is hot
• rocking
• rise
• keylight
• element

Choices:

• avacado - looks great on a mobile device
• admin-plus - uses bootstrap
• moon-light
• melon - I would make changes to the selected item as I think it is too light, otherwise a great look
• rootified

Use chef roles to install chef-server and to decouple init

Would like to move to using Thor instead of Rake. This would make it cleaner (possibly) and remove the need for rake pre-pending the command. This moves us closer to utility mode and allows for a higher level from which we can switch providers (openstack/docker via libcloud, away from vagrant as exclusive)

Possibilites:
collective --cluster base start # starts cluster 'base'
collective --node chef start # starts node 'base'
collective --provider vagrant --node chef -- command start

Add foodcritic to download:cookbooks to lint cookbooks.

Box export, maybe with veewee so that the clusters don't take so long.

Would be nice to do: vm:cluster:base:export

Using my 0.0.7 branch

First:
# In core.yml, replace the ci box with chef as well as adding it to the base cluster

clusters: # cluster config
  - cluster:
      name: 'base'
      nodes: 
        - 'chef'
        - 'dev'


nodes:  # node registry
  - node:
      hostname: 'chef'
      box: 'chef'
      cpus: 1
      mem: 256
      ip: '10.10.10.10'
      mac: '080027EB6B03'
      url: 'ubuntu_13_04_lts.box'
      init: 'init.sh'
    `mkdir manifests/chef`

Then create an init file:
cp manifests/dev manifests/chef

This cluster can be brought up or down via: rake vm:cluster:base:up.

Side note, would also be nice to clean up the manifests folder to something like [manifests/init, manifest/src], instead of everything sitting in one folder.

The rest makes more sense as we need that box to install open source chef server.

This server will help deploy openstack via chef recipes. The recipes are 'production' quality and this chef server should also be first class.