Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap. Text that we'd like to wrap.
{ | |
"comment": "Atomic Container Controller", | |
"osname": "project-atomic-controller", | |
"repo": "http://YOUR_REPO_SERVER_HERE/repo", | |
"architectures": ["x86_64"], | |
"releases": ["fc20"], |
FROM centos:centos7 | |
MAINTAINER jbrooks@redhat.com | |
WORKDIR /tmp | |
RUN yum upgrade -y && yum clean all | |
RUN yum install -y tar rubygems-devel rubygem-bundler ruby-devel git make gcc gcc-c++ patch curl-devel ImageMagick && yum clean all | |
ADD config.rb /tmp/config.rb | |
ADD data /tmp/data | |
ADD Gemfile /tmp/Gemfile | |
ADD Gemfile.lock /tmp/Gemfile.lock | |
ADD lib /tmp/lib |
This document is meant to serve as a baseline definition for Project Atomic hosts, to be implemented from CentOS, Fedora, and Red Hat Enterprise Linux (RHEL).
The purpose of the document is not to restrict the packages or services offered with an Atomic host, but to ensure a baseline of functionality and working standard that each product team can implement before adding additional functionality.
The initial working draft is being taken from work going into RHEL Atomic, but it is expected that the CentOS Atomic SIG and Fedora Cloud Workgroup will provide input and direction to Project Atomic going forward. This is simply the first cut at a shared understanding that gives each team a basis for cooperation.
I hereby claim:
- I am jasonbrooks on github.
- I am jasonbrooks (https://keybase.io/jasonbrooks) on keybase.
- I have a public key whose fingerprint is C7AB 6F73 5864 1B43 FBDB 407E E9AA C42C E8C9 644C
To claim this, I am signing this object:
Atomic hosts include Kubernetes for orchestration and management of containerized application deployments, across a cluster of container hosts. If you're interested in taking Kubernetes for a spin on an Atomic host, read on!
First, boot into CentOS Atomic host. You ought to be able to use Fedora Atomic as well, but currently, Atomic Fedora comes with an earlier version of kubernetes, so for each of the kubectl
commands in this howto, there's a different kubecfg
command, for now.
Due to a bug in CentOS Atomic (not necessary in Fedora Atomic), you must:
For vagrant-libvirt, the second disk can be added w/ libvirt.storage :file, :size => '5G'
.
To make use of this disk, we can use docker-storage-setup, as described in http://www.projectatomic.io/docs/docker-storage-recommendation.
The lines in the config.vm.provision
section below add DEVS="/dev/vdb"
to /etc/sysconfig/docker-storage-setup
. The commented-out line is supposed to run docker-storage-setup
to set up the storage, but this isn't working when run from the Vagrantfile here. Once logged in to the vagrant VM, however, running sudo docker-storage-setup
works as expected, except for a syntax error with part of the setup script which doesn't appear to stop the script from doing its job.
Vagrant.configure("2") do |config|
config.vm.box = "f22atomic"
Project Atomic hosts are built from standard RPM packages which have been composed into filesystem trees using rpm-ostree. This guide provides a method for customizing existing filesystem trees or creating new trees.
- a machine running CentOS or Fedora for composing filesystem trees
- a web server for hosting these tree repositories
.NET | |
ActionScript | |
ActiveMQ | |
Ada | |
Agile | |
Akka | |
Android | |
Ansible | |
AngularJS/js[Angular] | |
Apache |