Ask Your Question

polslinux's profile - activity

2017-02-01 08:07:50 -0500 received badge  Good Question (source)
2015-05-07 06:27:35 -0500 received badge  Nice Question (source)
2015-01-14 04:15:22 -0500 received badge  Taxonomist
2014-06-26 22:29:37 -0500 marked best answer vm error, cannot boot

I have used this guide (https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/master/OpenStack_Grizzly_Install_Guide.rst) to deploy openstack on a Ubuntu VM inside vmware esxi.
I want to boot the cirros image but after i've created & launched the vm i got "Error" on the "State" column.
My /var/log/nova/nova-compute.log file is empty. I've tried also with an ubuntu image but i always got the same result. What am i doing wrong?
With nova show $vmname i've found this: fault message no valid host was found.

2014-01-23 18:42:04 -0500 marked best answer br100 setup and nova fixed ip range

This is my situation:

  • An ESXi 5.0 Server (I'm doing a project for my BD);
  • A pool with 2 VM (1 controller node and 1 compute node)
  • Ubuntu 13.04 amd64 Server installed on both VM
  • The controller IP is 172.25.27.11
  • i've successfully setup keystone, glance and partially nova

My problem with nova is the creation of the br100 and the fixed range subnet. Inside the /etc/network/interfaces file i have:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto br100
iface br100 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

inside the file /etc/nova/nova.conf i have:

# NETWORK
network_manger_nova=nova.network.manger.FlatDHCPManager
my_ip=172.25.27.11
fixed_range=172.25.27.0/24
public_interface=eth0
vlan_interface=eth0
flat_interface=eth0
flat_network_bridge=br100

I have also enabled ip forwarding inside /etc/sysctl.conf and i have set eth0 promisc with ip link set eth0 promisc on.

The cmd brctl show show:

bridge name      bridge id    STP enabled        interfaces
br100            8000.xxxx    no                 eth0

What i am doing wrong?

2014-01-07 03:09:42 -0500 marked best answer cannot remove volume

If i do cinder delete $volume_id i got an "error_deleting" and i cannot remove the volume! What can i do to force the remove of it?

2013-12-10 01:45:14 -0500 received badge  Famous Question (source)
2013-10-26 00:05:32 -0500 marked best answer openstack single node single nic

I would like to install OpenStack 2013.1.1 on Ubuntu 13.04 which is installed in my notebook.
I thought to follow this guide: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/master/OpenStack_Grizzly_Install_Guide.rst but i have some doubts:

  1. I have only 1 NIC so what i have to do? Just ignore where the guide say "add eth0 10.10.100.51"?
  2. I want that all the VMs can be connected to my LAN (192.168.1.1/24) so with 1 NIC is this possible?

Thanks

2013-10-01 16:02:56 -0500 received badge  Famous Question (source)
2013-09-18 04:57:43 -0500 received badge  Notable Question (source)
2013-09-01 11:51:37 -0500 received badge  Favorite Question (source)
2013-08-23 09:58:12 -0500 received badge  Student (source)
2013-08-20 06:04:03 -0500 received badge  Famous Question (source)
2013-08-13 09:13:39 -0500 received badge  Famous Question (source)
2013-08-12 07:20:28 -0500 received badge  Famous Question (source)
2013-07-22 07:56:35 -0500 received badge  Famous Question (source)
2013-07-08 10:11:20 -0500 received badge  Famous Question (source)
2013-07-08 07:54:25 -0500 commented answer openstack single node single nic

yes, i'm using vNIC now :)

2013-07-03 16:17:38 -0500 commented answer cloudify openstack grizzly

+barakme: i think that this is the only thing i can do... :)

2013-07-02 10:27:49 -0500 received badge  Notable Question (source)
2013-07-01 15:46:28 -0500 received badge  Famous Question (source)
2013-07-01 15:43:41 -0500 commented question connect vms to external net

i solved by using OVS instead of linux bridge :)

2013-07-01 15:43:19 -0500 commented answer cloudify openstack grizzly

i have a problem because the floating ip is not associated :(

2013-07-01 15:30:38 -0500 marked best answer cloudify openstack grizzly

I have a problem with Cloudify (both 2.5 and 2.6-rc release).

I have an All-In-One Openstack 2013.1.1 setup and i'm trying to use cloudify to bootstrap a cirros 0.3.1 vm.

My quantum configuration is:

a private fixed ip 10.0.0.0/24 for vm management

floating ip 192.168.1.170-190 taken from the pool (192.168.1.1/24 is my lan)

When i deploy a vm first an ip from 10.0.0.0/24 is given (i cannot reach it from PCs because it is only for vm management) and then i associate a floating ip with which i can ping the/ssh into deployed machine.

The problem is that when i do:

bootstrap-cloud openstack

because cloudify stay forever into "attempting to access management vm 10.0.0.3" and this is due to the fact that 10.0.0.3 is not reachable.

What can i do to get cloudify take the floating ip instead of the fixed one?

Thanks

2013-07-01 15:30:38 -0500 commented answer cloudify openstack grizzly

but does it works with Quantum? Because i don't use nova-network!

2013-07-01 14:57:01 -0500 received badge  Scholar (source)
2013-07-01 13:46:01 -0500 received badge  Notable Question (source)
2013-06-30 17:54:08 -0500 received badge  Popular Question (source)
2013-06-29 12:39:21 -0500 received badge  Famous Question (source)
2013-06-28 08:45:20 -0500 received badge  Notable Question (source)
2013-06-28 05:15:24 -0500 edited question route fixed ip to floating ip

I'm trying to deploy a VM using cloudify but it tries to connect to the fixed ip (10.0.0.3) instead of the floating one (192.168.1.173).
There is a way to route the fixed ip to the floating ip so when cloudify tries to connect to 10.0.0.3 is will be redirected to 192.168.1.173?