totten25's profile - activity

2014-07-31 00:13:45 -0600 received badge  Famous Question (source)
2014-07-30 05:13:57 -0600 received badge  Famous Question (source)
2014-07-29 04:53:08 -0600 received badge  Notable Question (source)
2014-07-29 03:57:49 -0600 commented answer How to modify resize instance code OpenStack Havana/Icehouse ?

I just gave up for this problem and resize instance by OpenStack behavior.

2014-07-29 03:54:34 -0600 commented question Problems with floating IPs and neutron

How's about neutron security-group ?

2014-07-28 05:48:55 -0600 answered a question Icehouse installation with a single NIC: VMs do not have Internet

Did you install in bare-metal or Virtual Machine ? I ever faced this problem in VMWare ESXi, my problem is about promiscuous mode because you use single interface. Anyway, if you just have single interface, you can deploy openstack icehouse with neutron because i use single interface and it works for me.

2014-07-28 05:40:26 -0600 answered a question VM cannot access external network

From dbaxps' s suggestion, OpenStack Documentation didn't tell about setting up br-ex. i suppose that you create br-ex as a name of bridge interface of eth0 as external interface to connecting the outside world.

auto br-ex
iface br-ex inet static
        address 10.10.193.10
        netmask 255.255.255.0
        gateway 10.10.193.1
        dns-nameservers  8.8.8.8

auto eth0
iface eth0 inet manual
up ip address add 0/0 dev $IFACE
up ip link set $IFACE up
down ip link set $IFACE down

after you've configure like above, just remove ip address of eth0 and just add ip address of br-ex and restart network

ip addr del 10.10.193.10/24 dev eth0 
ip addr add 10.10.193.10/24 dev br-ex
/etc/init.d/networking restart # for Ubuntu 12.04 
service networking restart # for Ubuntu 14.04

after you've done this and if you found some problem, please check routing table and tcpdump of virtual router. Anyway, i ever faced problem about creating external network, my vm cannot access internet. When I check routing table of virtual router, i found that my default gateway is not my ip address gateway of my lab environment.

2014-07-28 02:44:56 -0600 answered a question How to attach two interfaces in the same subnet to the instance?

Did you try to set "allow_overlapping_ips = True" in /etc/neutron/neutron.conf

2014-07-28 02:39:46 -0600 answered a question Virtual machine as gateway

I don't understand why do you use VM-1 as gateway because by default, when you created internal network and you add it to be interface in virtual router. Router can help you to route between network A and network B. For this problem, VM-1 in network A didn't has routing information about VM-2 in network B. You should add routing which is linux command and when you reboot VM-1, routing table will be cleared and back to default. You may add route in /etc/network/interfaces. Moreover, i think "tcpdump" command can help you to figure out this problem.

2014-07-28 02:24:43 -0600 commented answer neutron stops working with multiple compute nodes

It seems your output is ok but i will show my neutron, nova files later. I think that your settings file are something wrong.

2014-07-28 01:14:59 -0600 received badge  Nice Answer (source)
2014-07-27 23:54:50 -0600 answered a question How to modify resize instance code OpenStack Havana/Icehouse ?

after i try to figure out it, i found validate-targethost-live-migration that may help me to the right way. I try to adapt this concept to resize instance to target host.

2014-07-27 23:38:28 -0600 answered a question neutron stops working with multiple compute nodes

How's about neutron agent-list and ovs-vsctl show ? which connection type do you use between VLAN and GRE tunneling ? I never faced this problem. The neutron must work well with multiple compute node. I've installed icehouse with GRE tunneling which have 1 controller node, 1 network node and 15 compute nodes. If it has problem, it should has something in neutron log files. Anyway, I would like to suggest you to follow from OpenStack icehouse manual in main websites and I'm totally sure that everything work. I didn't find other websites for troubleshooting as same as previous versions.

2014-07-27 23:32:07 -0600 received badge  Notable Question (source)
2014-07-27 18:24:32 -0600 received badge  Teacher (source)
2014-07-27 12:48:22 -0600 answered a question how can I find the IP assigned to every instance created?

if you mean about internal IP address of each instance, you can get it from nova list command and retrieve what you want

2014-07-27 08:45:27 -0600 received badge  Popular Question (source)
2014-07-27 05:08:33 -0600 received badge  Enthusiast
2014-07-26 04:17:08 -0600 received badge  Student (source)
2014-07-26 03:47:43 -0600 received badge  Editor (source)
2014-07-26 03:44:57 -0600 asked a question How to modify resize instance code OpenStack Havana/Icehouse ?

Hi , I deployed both of Icehouse and Havana OpenStack version which have 1 Controller Node, 1 Network Node and 15 Compute Nodes connected together via VPN network so i want to resize instance at same node because migration to other node take more time. I've already edit allow_resize_to_same_host = True and scheduler_default_filters = AllHostsFilter in both of Controller Node and Compute Nodes. I faced the problem of Icehouse and Havana

Problem in OpenStack Havana when i try to resize instance, sometime OpenStack try to migrate instance to other nodes and sometime instance can be resized successfully at same node. I'm sure my current node that instance is located have enough resources. why does OpenStack sometime try to migrate after i allow_resize_to_same_host ? moreover, nova-compute.log just show error about ssh to other nodes and my point just want to resize at same node. It should not migrate to other nodes anymore.

Problem in OpenStack Icehouse (Compute01 is a first Compute Node that be installed before other Compute Nodes) when i try to resize instance which is not launched to Compute01 in case instance is launched between Compute02-15, OpenStack will migrate instance to Compute01 every time. On the other hand, if instance is launched to Compute01, it can be resized successfully. I think Icehouse is difference from Havana, because Compute01's instance can be resized successfully every time.

I want to force resize instance to the same node only. I would like to know which OpenStack python files that involved with this problem? For me, i deeply found some file in /usr/lib/python2.7/dist-packages/nova/compute/ such as api.py and manage.py which has resize_instance method. Finally, I just want to know How to modified code of OpenStack resize instance both of havana and icehouse ?

Best regards, totten25

2014-07-24 10:22:42 -0600 received badge  Popular Question (source)
2014-07-23 05:03:26 -0600 commented question Resize openstack icehouse instance at same node BUG

I'm not sure that a disk resize down the instance should be whether BUG or prevent the problem from OpenStack older version (Havana) in OpenStack icehouse from code above. it doesn't make sense if root_disk and ephemeral_disk are less than current instance for disk resize down (I understand this point because it may corrupt the filesystem) but it isn't possible in small,medium and large or others flavor will have equally disk capacity. My point is how does OpenStack do when instance is resizing down to smaller flavor? For now, i can comment this condition. Anyway, I never face this behavior when i want to resize down the instance in OpenStack Havana.

2014-07-23 02:55:01 -0600 commented question Resize openstack icehouse instance at same node BUG

Oh, it's unbelievable. I can resize instance more than one time but I sometime found new error from nova-compute.log as shown below

2014-07-23 14:17:04.229 1610 INFO nova.compute.manager [req-bc2cc04a-b32b-455b-9112-988b8ad6ab1a00067bdf3023482ebcc6142da5282b36 81e29a87757e4134afd59c1e5292649c] [instance: 77a2e697-451d-41f1-83df-4f2629097751] Setting instance back to ACTIVE after: Instance rollback performed due to: Resize error: Unable to resize disk down.

I deeply research about this error and fortunately, i can figure out it!!!!!. The problem occur from this

# Checks if the migration needs a disk resize down.
    for kind in ('root_gb', 'ephemeral_gb'):
        if flavor[kind] < instance[kind]:
            reason = _("Unable to resize disk down.")
            raise exception.InstanceFaultRollback(
                exception.ResizeError(reason=reason))
2014-07-22 23:46:41 -0600 commented question Resize openstack icehouse instance at same node BUG

From Instance not resizing, skipping migration, it will happen only after i resize more than 1 time. it will be changed to resize state then instance is not resizing and change back to active state as same as i mentioned in first questions.

2014-07-22 23:17:05 -0600 commented question Resize openstack icehouse instance at same node BUG

ok I'm sorry I will add important error and warning are shown below after i try resize more than one time /var/log/nova/nova-compute.log in compute node

2014-07-23 06:47:14.411 1610 WARNING nova.compute.resource_tracker [-] [instance: 03971852-647a-4116-b4e7-b65345c1d300] Instance not resizing, skipping migration.

/var/log/nova/nova-scheduler.log

2014-07-22 21:08:26.761 9217 WARNING nova.scheduler.host_manager [req-d46ad3a1-be18-464b-a3b9-11123e481fcc bdb162ee567d4230a988895f2a000a8b9 84ec9bb0ccc34eea84fbf49b557c4a66] Host has more disk space than database expected (43gb > 34gb)

with my respect, i just found 2 useful warning in Controller node and Compute node. Anyway, my settings in nova.conf of Controller node

allow_resize_to_same_host = True, scheduler_default_filters = AllHostsFilter

and Compute node

allow_resize_to_same_host = True

Thank you for your response