openstack ansible ceph

in the deploy server git clone -b liberty https://github.com/openstack/openstack-ansible.git /opt/openstack-ansible cd /opt/openstack-ansible scripts/bootstrap-ansible.sh copy the config folder to /etc cp -a /opt/openstack-ansible/etc/openstack_deploy /etc/ Follow  ceph setup ubuntu three node tutorial disable is_metal from /etc/openstack_deploy/env.d/cinder.yml # /etc/openstack_deploy/user_variables.yml glance_default_store: rbd glance_notification_driver: noop glance_ceph_client: glance glance_rbd_store_pool: glance-images glance_rbd_store_chunk_size: 8 nova_libvirt_images_rbd_pool: ephemeral-vms cinder_ceph_client: cinder cephx: true ceph_mons:   – […]

Read More

openstack-ansible-managed-ceph

This method is not officially supported(yet) and  is a Jerry-rigged implementation Alternatively,  You can use the normal method to create your cluster create /etc/openstack_deploy/conf.d/ceph.yml  to define your ceph cluster — mons_hosts: ## can be same as my infra hosts ## c11: ip: 172.29.240.11 c12: ip: 172.29.240.12 c13: ip: 172.29.240.13 osds_hosts: c20: ip: 172.29.240.20 container_vars: raw_journal_devices: […]

Read More

ceph setup ubuntu three node

From your deploy server If you need to start fresh again and again 🙂 cd /opt/ceph-deploy/ ceph-deploy purge c20 c21 c22 ceph-deploy purgedata c20 c21 c22 mkdir /opt/ceph-deploy/ cd /opt/ceph-deploy/ rm -f * ceph-deploy new c20 c21 c22 add the following to ceph.conf public_network = 172.29.244.0/22 cluster_network = 172.29.240.0/22 ceph-deploy install c20 c21 c22 ceph-deploy […]

Read More

OpenStack – Stacking vs Spreading

By default, when instances are created, they are spread in the cluster. So the first instance will be in  the first compute node, the second one in the second compute node and so on.  This will ensure that all nodes are properly used up and filled up. Suppose, H1 has 8 CPUs and H2 has […]

Read More

OpenStack add direct attached dhcp ips

In our architecture, direct attached dhcp IPs are in VLAN 201 neutron net-create dhcp-192-168-201  \ –shared –router:external false \ –provider:network_type vlan \ –provider:physical_network vlan \ –provider:segmentation_id 201 +—————————+————————————–+ | Field | Value | +—————————+————————————–+ | admin_state_up | True | | id | 1d0fc020-d33b-406e-a287-02032a5a09b0 | | mtu | 0 | | name | dhcp-192-168-201 | | […]

Read More

OpenStack add floating ips

In our architecture, floating IPs are in VLAN 101. neutron net-create floating-192-168-101 \ –shared –router:external true –provider:network_type vlan \ –provider:physical_network vlan –provider:segmentation_id 101     +—————————+————————————–+ | Field | Value | +—————————+————————————–+ | admin_state_up | True | | id | 01c41b9a-3241-4236-9e52-77e0967d4b53 | | mtu | 0 | | name | floating-192-168-101 | | port_security_enabled | […]

Read More

OpenStack Dev Server Setup – CentOS

generate a ssh key without password. Copy the pub-key to the kickstart file. install necessary software yum install epel yum install bridge-utils libvirt qemu-kvm tcpdump wget yum-plugin-remove-with-leaves nginx mosh tmux virt-install htop chkconfig NetworkManager off chkconfig network on /etc/init.d/NetworkManager stop /etc/init.d/network restart go to your /etc/sysconf/network-scripts/ folder edit ifcfg-em1 to be something like this TYPE=Ethernet […]

Read More

OpenStack Dev Server Setup – Ubuntu

OpenStack all-in-one development server. Get a good server with a fair amount of CPU and RAM. This also depends on the number of instances you plan to run on it. For a basic minimum, you need at least 1 vyos, 1 controller and 1 compute … You might be able to get away with 8 […]

Read More

OpenStack Private Cloud – Architecture

Virtual Architecture [Dev/Test] For the Dev/Test setup, you can have one (good/powerful) server or a few OK ones. The minimum requirement is that it must have 1 network card and run Ubuntu 14.04 LTS. Your main OS has 3 bridges br-net — we create this and put the public IP address here virbr0 – this […]

Read More

OpenStack affinity and anti-affinity

Affinity: ensures instances are in the same compute node Anti-Affinity: ensures that the instances are not in the same compute node.   nova server-group-list +—-+——+———-+———+———-+ | Id | Name | Policies | Members | Metadata | +—-+——+———-+———+———-+ +—-+——+———-+———++———+   nova server-group-create far-apart anti-affinity  ##  ‘far-apart’ is just an arbitrary name I used +————————————–+———–+——————–+———+———-+ | Id […]

Read More