Ask Your Question

pixelbeat's profile - activity

2017-05-04 01:57:23 -0500 received badge  Guru (source)
2017-05-04 01:57:23 -0500 received badge  Great Answer (source)
2014-11-25 12:18:50 -0500 received badge  Nice Answer (source)
2014-11-20 07:13:05 -0500 answered a question VMs not getting IP through DHCP private 10.x network unreachable

I can't see the version you're using. It's always good to state that.

Please note there was an update to icehouse and juno neutron packages 5 days ago to fix a permissions issue impacting dnsmasq. You should be OK in that regard if you're using >= openstack-neutron-2014.2-9 for Juno, or >= openstack-neutron-2014.1.3-4 for Icehouse

2014-09-24 14:01:00 -0500 answered a question unable to install openstack-keystone

BTW EPEL should be enabled by packstack automatically. This may not happen in edge cases like if epel-release was already installed but explicitly disabled.

2014-09-21 15:34:54 -0500 answered a question Python module for *writing* openstack style config files?

Note the crudini CLI interface is designed to be compat with multi valued options (through the new --list option in version 0.4), though supporing that would require updating iniparse or equivalent. I think the handling of [DEFAULT] is done appropriately by crudini as is.

Please consider updating crudini rather than duplicating any work in a separate project. Any patches are very welcome.

2014-06-09 07:56:57 -0500 received badge  Commentator
2014-06-08 21:00:11 -0500 received badge  Nice Answer
2014-06-06 10:45:13 -0500 answered a question Need better install instructions for trove on CentOS 6.5 in multi-machine environment?
2014-06-06 10:44:17 -0500 answered a question How to install Trove on RDO Icehouse ?

Yes trove is not integrated with packstack or foreman installers yet. Basic install steps would be:

yum install openstack-trove  # meta package to include all host subpackages
openstack-db --service trove --init # may need to get passwords from packstack answer file

There is no further RDO specific config documentation at present

2014-05-29 06:02:13 -0500 commented answer Cannot start docker-registry at PackStacked CONTROLLER node.

This issue with python-backports is tracked at https://bugzilla.redhat.com/1061051

2014-05-20 12:52:17 -0500 received badge  Nice Answer (source)
2014-05-20 08:20:30 -0500 answered a question python-oslo-vmware packaging plans for rdo?
2014-05-16 09:43:34 -0500 received badge  Good Answer (source)
2014-05-16 09:43:25 -0500 received badge  Nice Answer (source)
2014-05-16 08:44:50 -0500 answered a question failed to start keystone

I think this corresponds to https://bugzilla.redhat.com/1098160 That suggested that this install is corrupted due to devstack

2014-05-12 14:41:19 -0500 received badge  Nice Answer (source)
2014-05-12 13:45:26 -0500 answered a question Attempt to upgrade AIO Havana to IceHouse on CentOS 6.5 (VM on Libvirt's subnet))

There were no neutron packages to update?

BTW on the neutron-manage step there is support now in openstack-db, so...

openstack-db --service neutron --update
2014-05-02 04:45:53 -0500 commented answer OpenStack icehouse on a fresh installation of Fedora 20

You can setup a proxy at the yum level like: http://openstack.redhat.com/forum/dis...

Also if you need to setup proxy env variables for general external HTTP access, you might need to adjust openstack settings to avoid the proxy for internal openstack services: https://ask.openstack.org/en/question...

2014-05-02 03:08:06 -0500 commented answer OpenStack icehouse on a fresh installation of Fedora 20

Just to confirm that the currently released packstack (1055) and openstack-puppet-modules-2014.1-0.9 do the above nova/neutron config automatically

2014-05-02 03:06:19 -0500 commented answer OpenStack icehouse on a fresh installation of Fedora 20

Re the vim-minimal thing, see https://bugzilla.redhat.com/1066983 Perhaps the more general fix it to run yum update before proceeding, which will ensure all installed components are up to date.

2014-05-01 19:05:31 -0500 received badge  Nice Answer (source)
2014-05-01 14:38:39 -0500 received badge  Nice Answer (source)
2014-05-01 09:15:37 -0500 commented answer packstack installation ends up with neutron agent intermittently on and off.

you could try to edit the config, that the updated puppet modules are now actually doing. I.E. add the following in /etc/neutron/neutron.conf

nova_url = http://<IP>:8774/v2
nova_admin_username = admin
nova_admin_tenant_id = <admin tenant id>
nova_admin_password = <admin password>
nova_admin_auth_url = http://<IP>:5000/v2.0/
2014-05-01 07:05:37 -0500 commented answer packstack installation ends up with neutron agent intermittently on and off.

packstack-2014.1...1055 and openstack-puppet-modules-2014.1-9 now in the RDO repos should address this issue

2014-05-01 07:02:17 -0500 answered a question Icehouse repository issue ?

You'll need fedora 20 or later as stated on the quick start guide

2014-05-01 06:16:47 -0500 answered a question packstack installation ends up with neutron agent intermittently on and off.

We're fixing this up now. As a workaround please add this to nova.conf on the compute node:

 vif_plugging_is_fatal: false
 vif_plugging_timeout value: 0

p.s. This workaround is listed on the RDO icehouse quick start guide

2014-04-27 14:39:00 -0500 answered a question Fedora 20 / Icehouse all-in-one error applying puppet manifests

That should now be fixed by the latest version of openstack-puppet-modules in the Fedora 20 Icehouse RDO repos

2014-04-27 14:37:30 -0500 answered a question Packstack --allinone failure to install keystone.pp error

TBH you'd be better served by the icehouse repos at this stage.

http://repos.fedorapeople.org/repos/o...

Icehouse has just been released and those packages are much better tested. We'll decide soon what to do with those openstack-trunk packages.

2014-04-03 04:16:59 -0500 commented answer trying to install RDO on centos 6.5, fails installing dashboard components

yes EPEL is required, but packstack should be auto enabling EPEL where required (consider multi host installs also). What might be happening is that the EPEL release RPM was already installed but you had it explicitly disabled in /etc/yum.repos.d/epel.repo for some reason? Note every RDO user would hit this issue on a fresh system otherwise

2014-04-01 07:10:49 -0500 answered a question RDO neutron on github

The package is built in Fedora infrastructure, so the packaging source is:

http://pkgs.fedoraproject.org/cgit/op...

Minimal patches are maintained in various branches on top of the upstream git tree at:

https://github.com/redhat-openstack/q...

2014-03-03 22:02:54 -0500 received badge  Enlightened (source)
2014-03-03 22:02:53 -0500 received badge  Good Answer (source)
2014-03-03 11:03:00 -0500 received badge  Nice Answer (source)
2014-02-28 11:08:54 -0500 received badge  Nice Answer (source)
2014-02-26 08:00:59 -0500 answered a question metadata agent throwing AttributeError: 'HTTPClient' object has no attribute 'auth_tenant_id' with latest release

python-neutronclient-2.3.1-3 is now released for RDO Havana to fix this issue

2014-02-26 07:51:13 -0500 answered a question Nova services are dead on CentOS

Can you look at the nova logs. Anything informative in /var/log/nova/api.log for example?

2014-02-26 07:46:14 -0500 answered a question Dependency error on CentOS 6.5 (python 2.7)

I've just confirmed that all RDO el6 keystone packages have python(abi) = 2.6

What packages is it trying to install exactly?

2014-02-24 07:11:20 -0500 answered a question rdo-release.rpm fails, conflicts with puppetlabs

So the workaround at the moment is to let rdo-release provide the puppetlabs-release bits. I.E. not install the puppetlabs-release on such hosts.

To make this more automatic in future is now tracked at: https://bugzilla.redhat.com/1069200

2014-02-11 05:36:41 -0500 commented answer RDO Install Failing keystone-all

Right devstack does many modifications to the system, and outside any package management etc. and so is best restricted to VMs

2014-02-07 06:08:59 -0500 answered a question packstack --allinone giving error

So packstack tries to see if epel-release is installed and if not will install it if required. Now if you have the epel repo enabled not through the epel-release rpm then packstack might not notice and encounter a conflict when it tries to setup epel? Could you remove epel repo setup from your machine and let packstack enable it?