June 2014 - dev - Rdo List Archives

[Rdo-list] Ceilometer Hangout coming July 9

by Rich Bowen

Mark your calendars. On July 9, 15:00 UTC (11 am Eastern US time) Eoghan Glynn will be leading a Google Hangout in which he'll discuss hat's new in Ceilometer in OpenStack Icehouse, and what's coming in Juno. https://plus.google.com/events/c6e8vjjn8klrf78ruhkr95j4tas The presentation will also be available (at that same URL) on Youtube after the event. --Rich -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

9 years, 10 months

1
0
0 / 0

[Rdo-list] Foreman installation

by Ajay Kalambur (akalambu)

Hi Not sure if this is the right list for RDO/Foreman but i am trying to install RDO/Icehouse with Foreman on fedora and tried to install foreman installer with the following commands I ran the following commands and it cant locate the foreman installer sudo yum install -y http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/rdo-rele... 2 sudo yum install -y openstack-foreman-installer sudo yum install -y openstack-foreman-installer Loaded plugins: langpacks, refresh-packagekit No package openstack-foreman-installer available. Anyone tried foreman installer on Fedora. If so what is the correct repository the rdo-release-icehouse does not seem to have openstack-foreman-installer Ajay

9 years, 10 months

3
4
0 / 0

[Rdo-list] Simplest Icehouse Implementation Architecture

by Eric Berg

I'm working toward implementation of a small RDO cloud which should be quite minimal. We will be running < 25 VMs with very low utilization, which will not change very often and which will basically just run to be available. I have two hosts with plenty of RAM and disk, and can get others as required. The initial expectation as communicated to me was to just use two hosts that we already have. I'm not sure if that's a realistic architecture, but it seems from my reading that I might want at least a separate control box if not also have the network box be separate if not on the same as the control host. So, are either of the following architectures sufficient for a development environment? Option 1. - Two hosts to handle the entire cloud Option 2. - Two compute hosts - One control host Thanks as always for your input. Eric -- Eric Berg Sr. Software Engineer Rubenstein Technology Group

9 years, 10 months

2
9
0 / 0

[Rdo-list] RDO IceHouse Setup Two Node (Controller+Compute) Neutron ML2&OVS&GRE Cluster on Fedora 20

by Boris Derzhavets

Two KVMs have been created , each one having 2 virtual NICs (eth0,eth1) for Controller && Compute Nodes setup. Before running `packstack --answer-file=twoNode-answer.txt` SELINUX set to permissive on both nodes. Both eth1's assigned IPs from GRE Libvirts subnet before installation and set to promiscuous mode (192.168.122.127, 192.168.122.137 ). Packstack bind to public IP - eth0 192.169.142.127 , Compute Node 192.169.142.137 Answer file been used by packstack here http://textuploader.com/0ei8 Not sure my answer file is 100% correct, however it successful completion doesn't create file ml2_plugin.ini,/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini on Controller && Compute Nodes which are required by Neutron ML2 plugin && OVS agent. This files have been manually created under /etc/neutron afterwards and allowed to configure neutron OVS agent on both nodes.Files missing after packstack run were created following http://kashyapc.fedorapeople.org/virt/openstack/rdo/IceHouse-Nova-Neutron...

9 years, 10 months

2
2
0 / 0

[Rdo-list] Separating neutron-server from network node

by iain MacDonnell

My desired architecture includes a Linux VM which runs the controller parts of OpenStack (including all of the API endpoints), one (for now) bare-metal network node (L3, DHCP and maybe metadata) and many bare-metal compute nodes. I'm trying to install thusly: CONTROLLER=10.0.1.10 NETNODE=10.0.2.10 COMPUTENODES=10.0.2.20,10.0.2.21,10.0.2.22,... TENANT_NET_TYPE=vlan VLAN_RANGES=pubphysnet01,priphysnet01:100:199 BRIDGE_MAPPINGS=priphysnet01:br-bond0 BRIDGE_INTERFACES=br-bond0:bond0 packstack \ --neutron-l2-plugin=ml2 \ --neutron-ml2-type-drivers=flat,${TENANT_NET_TYPE} \ --neutron-ml2-tenant-network-types=${TENANT_NET_TYPE} \ --neutron-ml2-mechanism-drivers=openvswitch \ --neutron-ml2-flat-networks=pubphysnet01 \ --neutron-ml2-vlan-ranges="${VLAN_RANGES}" \ --neutron-ovs-bridge-mappings="${BRIDGE_MAPPINGS}" \ --neutron-ovs-bridge-interfaces="${BRIDGE_INTERFACES}" \ --neutron-l3-hosts=${NETNODE} \ --neutron-dhcp-hosts=${NETNODE} \ --neutron-metadata-hosts=${NETNODE} \ --install-hosts=${CONTROLLER},${COMPUTENODES} This presents two problems: 1) (less intrusive, but annoying) neutron-openvswitch-agent is installed and enabled on the controller VM, which I don't want (I can disable the service, 'neutron agent-delete', and unwind the ovs config that it did) 2) neutron-server gets launched on the network node (10.0.2.10) as well as the controller (10.0.1.10). Curiously, the service is not enabled on the network node (chkconfig --list shows 'off'), but it is running when packstack completes. This causes mass confusion for the agents, as there are two neutron-server's running at the same time. It results in obscure problems, including apparent messaging failures, and agents reporting tables missing from the database (neutron.conf on the network node doesn't have the SQL connection info). Am I doing something wrong here? Should it work as above? I can file a bug or two, but thought I'd check here first.... Tnx, ~iain

9 years, 10 months

2
1
0 / 0

[Rdo-list] Tempest with RDO

by Ajay Kalambur (akalambu)

Hi When i ask RDO to configure and install tempest it needs to install dependencies like testtools, fixtures, mock, oslotest module i presumed But all the tests fail because none of these modules are installed by RDO I followed the instructions here to try to get tempest working and it does not work http://openstack.redhat.com/Testing_IceHouse_using_Tempest Because the tempest installation does not install these modules Ajay

9 years, 10 months

3
3
0 / 0

[Rdo-list] Heat installation config

by Ajay Kalambur (akalambu)

Hi The RDO answers_file has a config parameter as follow # Set to 'y' if you would like Packstack to install OpenStack # Orchestration (Heat) CONFIG_HEAT_INSTALL=n Even if this is set to n heat seems to have installed and i can run the heat CLIs What actually is this parameter intended for? Ajay

9 years, 10 months

2
1
0 / 0

[Rdo-list] Installation Issue

by Ajay Kalambur (akalambu)

Hi I tried the RDO installation based on instructions at http://openstack.redhat.com/Quickstart With the default config if we spawn off a VM failed because the neutron-openvswitch-agent.service terminated. The reason is the error below which looks like https://bugs.launchpad.net/neutron/+bug/1322139 2014-06-07 02:35:55.311 15597 ERROR neutron.plugins.openvswitch.agent.ovs_neutron_agent [req-aae1a4c5-7b45-42b3-886c-1657b25032e2 None] Agent terminated 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py", line 231, in _check_ovs_version 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ovs_lib.check_ovs_vxlan_version(self.root_helper) 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py", line 551, in check_ovs_vxlan_version 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent 'kernel', 'VXLAN') 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py", line 529, in _compare_installed_and_required_version 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent raise SystemError(msg) 2014-06-07 02:35:55.311 15597 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent SystemError: Unable to determine kernel version for Open vSwitch with VXLAN support. To use VXLAN tunnels with OVS, please ensure that the version is 1.10 or newer! I thought the install would go through with default options. Would it be possible to fix the default answers file so that the default installation passes on some simple tests like VM launcher Ajay

9 years, 10 months

4
4
0 / 0

[Rdo-list] TripleO hangout, Friday 1pm Eastern

by Rich Bowen

Hugh Brock will present a hangout on #Openstack #TripleO on Friday at 1pm Eastern: https://plus.google.com/events/cp6fpffs4a9maqfn3h92tvvck1o -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

9 years, 10 months

1
1
0 / 0

[Rdo-list] Notes for (manually) setting up a 2-node minimal IceHouse RDO setup in virtual machines

by Kashyap Chamarthy

I've been using this minimal, manually-configured IceHouse virtual setup based on this notes[1] for a few weeks as a virtual test environment reasonably successfully. This may not be issue-free, but if anyone ever dares to try this, comments/feedforward welcome. And, here[2] the resulting configuration files (although, I've posted this here a couple of times, but posting again for completness' sake). [1] http://kashyapc.fedorapeople.org/virt/openstack/rdo/Minimal-OpenStack-Ice... [2] http://kashyapc.fedorapeople.org/virt/openstack/rdo/IceHouse-Nova-Neutron... -- /kashyap

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev June 2014