Ask Your Question

OmegaHarvest's profile - activity

2017-08-23 05:10:50 -0500 received badge  Famous Question (source)
2016-07-07 01:07:51 -0500 received badge  Famous Question (source)
2016-05-08 21:35:55 -0500 received badge  Notable Question (source)
2016-05-08 21:35:55 -0500 received badge  Popular Question (source)
2016-04-25 11:44:50 -0500 commented answer RDO Packstack --provision-all-in-one-ovs-bridge no longer works

Thanks, much easier

2016-04-25 10:39:27 -0500 asked a question RDO Packstack --provision-all-in-one-ovs-bridge no longer works

I'm setting up RDO Openstack Mitaka on a CentOS 7.2 VM and am running the following command:

packstack --allinone --provision-all-in-one-ovs-bridge=n --nagios-install=n

I'm getting the following message:

packstack: error: no such option: --provision-all-in-one-ovs-bridge

Has this option been deprecated? I'm running through my documentation which I haven't used for about a year, but this always worked previously.


2015-10-10 01:26:10 -0500 received badge  Famous Question (source)
2015-06-26 06:22:46 -0500 received badge  Notable Question (source)
2015-05-27 06:55:56 -0500 received badge  Famous Question (source)
2015-05-11 15:30:22 -0500 commented question Cannot start instance after reboot on RDO OpenStack

I also have no free space on the only hard disk for this system? Should I have left some for cinder to use for LVM?

2015-05-11 15:24:12 -0500 received badge  Notable Question (source)
2015-05-11 13:41:20 -0500 commented question Cannot start instance after reboot on RDO OpenStack

I didnt enabled LVMiSCSI explicitly, although maydbe the allinone install of packstack does this by default? I do have the option to set volume types as iscsi. Should I be using this? Seems odd as its all on one host though.

2015-05-11 13:40:13 -0500 commented question Cannot start instance after reboot on RDO OpenStack

I ran losetup -a commands and got the following:

/dev/loop0: [64768]:10223620 (/srv/loopback-device/swiftloopback)
/dev/loop1: [64768]:8389772 (/var/lib/cinder/cinder-volumes)

All seems ok to me?

2015-05-11 02:15:48 -0500 received badge  Popular Question (source)
2015-05-10 14:49:18 -0500 asked a question Cannot start instance after reboot on RDO OpenStack

Just setup RDO OpenStack all in one setup on a single workstation (CentOS 7). Everything works fine except when I reboot and try to launch an existing instance.

Prior to shutting down I'll shut down my test CirrOS instance from the GUI and then shutdown the host via an acpi shutdown. When the host is back up, I go to start the shutoff instance in the UI but it fails after a few seconds to start. I notice the following of interest in the nova-compute log:

ERROR oslo.messaging.rpc.dispatcher [req-3e94838d-e627-4278-8cc1-2f69435813c8 ] Exception during message handling: Unexpected error while running command. Command: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node -T -p --rescan 
Exit code: 21 
Stdout: u''
Stderr: u'iscsiadm: No session found.\n'

I wondered if there was a correct procedure for shutting down my particular config?

I created the instance with a 10 gig volume which I see before and after rebooting if I run 'lvdisplay' on the host. The host has 1 single SSD formatted using LVM and ext4 if this matters?

Thanks for any help you can provide.


2015-05-07 13:20:43 -0500 commented answer RDO All in one - Cannot associate floating ID to ports

Many thanks, this solution also works if I associate the floating IP to the private port. A learning curve issue on my part. Thank you for your time.

2015-05-07 13:18:55 -0500 commented question RDO All in one - Cannot associate floating ID to ports

Thank you for the clarification. I was expecting to see the public IP as well as the private IP in the instance. Now I know to associate the floating IP to the related port on the private network, everything is accessible at last!

Thanks again.

2015-05-07 13:17:20 -0500 received badge  Famous Question (source)
2015-05-06 23:58:51 -0500 received badge  Notable Question (source)
2015-05-06 23:58:51 -0500 received badge  Popular Question (source)
2015-05-06 15:34:33 -0500 asked a question RDO All in one - Cannot associate floating ID to ports

Dear All

I'm currently in the process of attempting to setup RDO Juno on CentOS 7 in VMware Workstation as an all in one. I've read over many guides which all seem simple and easy to follow for an OpenStack beginner like me. This one has been especially helpful: (

All goes well and I am able to spin up instances from the dashboard (accessed from another VM on the same LAN segment. However, the instances fail to get an IP. I'm assuming I have to associate a floating IP to the public network but when I select to do so I have no ports available.

I came across this bug and replaced the file but still had no luck after a reboot: (

I tried manually adding a port association following this guide but get HTTP400 Bad Request on the final command. I checked for typos in IDs many times: (

I'm confident the interfaces are set OK as I can access Horizon from the bridges interface on another VM on the same LAN segment.

I'm at a loss at this point on what it could be. The RDO installer is very simple and completes fine, I just cannot get access to the instances on the public network. From a console session to an instance I am unable to ping anywhere on public as I have no IP associated. I'm running instances in the admin project if this is relevant?

Thanks for any help. At this point I'm kind of desperate. Could this be an issue with running it all in VMware Workstation? People seem to have had luck with VirtualBox so hoped this would also be ok.

2015-05-06 12:48:09 -0500 received badge  Enthusiast
2015-04-28 08:24:41 -0500 received badge  Notable Question (source)
2015-04-25 20:31:47 -0500 received badge  Popular Question (source)
2015-04-24 15:10:53 -0500 asked a question Creating External Bridge

Final quick question regarding bridges and tunnels, I promise!

When configuring the external network on my 3 node cluster, I have the following bridge setup:

auto eth2 iface eth2 inet manual up ifconfig $IFACE up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down

auto br-eth2 iface br-eth2 inet static address netmask gateway

Do I also need to set bridge_ports eth2 or is this handled fully by the virtual switch? I only ask as Ubuntu 14.04 hangs on loading the network on startup for a few minutes. However, I can then see br-eth2 when I ifconfig and can also ping the static IP on the bridge from another host on the same network.

All of the neutron logs show no errors with this config so is this just Ubuntu fussing because it doesnt understand that the OVS is handling things now? If that makes sense...

Thank you all for your kind help and patience.


2015-04-24 15:05:03 -0500 received badge  Notable Question (source)
2015-04-24 08:22:45 -0500 received badge  Popular Question (source)
2015-04-24 02:34:05 -0500 asked a question Interface Bridges with GRE tunnels

Mainly a quick sanity check, but when creating GRE tunnels between compute and network nodes, do I need to manually create a bridge in the interfaces file or is this only required for the external interface on the network node? Pretty sure I don't but thought I'd make sure before I try.



2015-04-24 00:59:36 -0500 received badge  Scholar (source)
2015-04-23 18:54:51 -0500 received badge  Popular Question (source)
2015-04-23 08:35:48 -0500 commented answer Unsure what bridges to create?

Thank you. I now know what to create and how to check. I'm creating a GRE tunnel between my network node and my compute nodes. I understand I need to create br-int in the OVS for this. I'm assuming I don't need to create a bridge in the interfaces file for the tunnel, only for the external network?

2015-04-23 08:31:10 -0500 received badge  Supporter (source)
2015-04-23 08:31:08 -0500 commented answer Unsure what bridges to create?

That clears up a lot. Many Thanks!

2015-04-22 15:33:59 -0500 asked a question Unsure what bridges to create?

I'm currently following the OpenStack Juno guide for Ubuntu 14.04: (

The only bit I'm confused on is where to configure network bridges for use with OVS? From what I can tell, the guide only wants a bridge created for the external network on the network node. However, I'm unsure if I also have to create a bridge for the tunnel network between my compute node and network node? I keep reading about br-int for internal traffic in the OVS but am unsure if this actually needs creating in the interfaces file itself?

I'm attempting a three node setup.

Many Thanks