Ask Your Question

Francesco's profile - activity

2017-08-05 10:36:55 -0500 received badge  Self-Learner (source)
2017-08-05 10:36:55 -0500 received badge  Teacher (source)
2017-08-05 10:36:52 -0500 received badge  Student (source)
2015-07-22 10:12:06 -0500 commented question Neutron subnet DNS

Hi, did you manage to implement it? I would be interested in doing the same thing. Regards, Francesco

2015-07-21 14:20:43 -0500 commented answer Openstack deployment on two nodes with one NIC

I am using ML2&OVS&VXLAN as you advised. The file are posted as UPDATE 21/07/2015 in the original question, thanks very much. Francesco

2015-07-21 13:45:56 -0500 commented answer Openstack deployment on two nodes with one NIC

Hi dbaxps, thanks for your suggestion - I will try to improve my network background. Anyway I am using a normal cable as my NICs support Auto_MDI-X, which allows the usage of normal cables instead of cross-over ones. Apart from that, do you know why the system is not working using the switch?

2015-07-21 11:32:51 -0500 received badge  Commentator
2015-07-21 11:32:51 -0500 commented answer Openstack deployment on two nodes with one NIC

Hi, please find my latest update in the original question.

Yes, I use a normal cable when connecting the two PCs. I would also like to say that I am having the same issue with a single node all-in-one RDO deployment.

Thanks very much, Francesco

2015-07-21 07:58:43 -0500 answered a question Openstack deployment on two nodes with one NIC

UPDATE 25/08/2015

The problem has now been solved. It wasn't related to any Openstack configuration issues but to a security feature enforced by the physical switch of my lab called port security. Disabling that allowed my Openstack deployment to work as expected.

END UPDATE

Hi thanks all for the reply. I now have a clearer view on how Openstack and Neutron work.

After a week of troubleshooting I managed to have a "partial" answer to the networking issues reported above. It seems that ARP requests generated from within the qrouter and forwarded to the NIC of the controller/network node are somehow dropped by the physical switch interconnecting the PCs of my lab.

When I connect the two Openstack nodes directly using a cable I can ping both both the controller/network node and the compute node (I can ping the former only otherwise).

Does anybody have any idea of what kind of filtering is applied by the physical switch?

Thanks very much, Francesco

2015-07-17 02:57:47 -0500 received badge  Enthusiast
2015-07-15 08:53:04 -0500 commented question Openstack deployment on two nodes with one NIC

Right, I expected that as well. Any idea of what could be wrong? I can obviously ping the gw from my Network Node (without namespaces). Thanks a lot, Francesco.

2015-07-15 05:08:27 -0500 commented question Openstack deployment on two nodes with one NIC

see at the end of the latest update please. Thank you!

2015-07-15 03:00:42 -0500 commented question Openstack deployment on two nodes with one NIC

Hi, please see update 15/07/2015. They seems to be as you advised. Thanks again, Francesco.

2015-07-14 08:50:23 -0500 received badge  Famous Question (source)
2015-07-14 08:46:43 -0500 commented answer Openstack deployment on two nodes with one NIC

Yes, I confirm that 10.20.151.1 is the actual gw of my office network. I can ping both the virtual router 10.20.151.20 and the Controller/Network 10.20.151.48 from within the VM. Any other external address does not seem to be reachable. Could you advise how to troubleshoot? Thanks!

2015-07-14 08:33:07 -0500 commented answer Openstack deployment on two nodes with one NIC

Can you confirm that if i change the command for ext subnet creation with 'start=10.20.151.1,end=10.20.151.200' the IP address assigned to the virtual gateway should be 10.20.151.1? The command does not work in that way: Gateway ip 10.20.151.1 conflicts with allocation pool 10.20.151.1-10.20.151.200

2015-07-14 06:45:33 -0500 commented answer Openstack deployment on two nodes with one NIC

Thanks once again. I followed your instructions and created the virtual networks/devices. I can now ping the virtual gateway 10.20.151.10 from the Compute/Network node. Unfortunately I cannot ping/ssh into the VMs (although I have added the sec rules) and access external IPs from within VM. Thanks!

2015-07-13 23:55:42 -0500 received badge  Notable Question (source)
2015-07-13 18:14:59 -0500 commented answer Openstack deployment on two nodes with one NIC

Hi could you please have a look at the updated question. Thanks!

2015-07-13 18:13:20 -0500 received badge  Editor (source)
2015-07-13 17:49:36 -0500 answered a question Openstack deployment on two nodes with one NIC

Hi, thanks again.

I have switched to CentOS 7.1 and I still have some doubts regarding the network configuration.

Both the machines (Controller/Network and Compute) are connected to the same private network 10.20.151.0/24, which is routed to Internet through the gw 10.20.151.1. On both machines, the NIC connected to this network is em1. DHCP is disabled on this network.

I would like to a have the VM instances connected to a different network (e.g. 192.168.1.0/24) and have IP addressed assigned through DHCP. I would also like each VM instance to be connected to Internet and being accessible via ssh from the Controller and/or computing node.

Could you please help me to figure out how to change the settings in the answer file to achieve that?

Thanks very much, Francesco.

2015-07-13 10:36:32 -0500 commented answer Openstack deployment on two nodes with one NIC

Thanks for the answer. Do you know it that has been actually tested on two single NIC nodes? It does not seem to work for me... There is anything else I have to change in the answer file? What changes to network interfaces file are needed? Thanks and regards, Francesco.

2015-07-11 12:47:39 -0500 received badge  Popular Question (source)
2015-07-11 02:52:36 -0500 commented answer Openstack deployment on two nodes with one NIC

Hi, thanks for your answer. Could you please provide some details on how the network will be setup. I see I need to chance the answer file to use one interface only. Thanks again!

2015-07-10 11:12:34 -0500 asked a question Openstack deployment on two nodes with one NIC

Hi all, although I have some knowledge on the Openstack Architecture, I am quite new to its actual deployment.

I am trying install its basic components (Nova, Glance and Neutron) on a small cluster formed of two PCs, each having a single NIC available.

I am following this document guide: http://docs.openstack.org/icehouse/install-guide/install/yum/content/ch_overview.html (http://docs.openstack.org/icehouse/in...)

as I have Fedora 21 installed on both the machines.

I am trying to adapt the process as in that document three nodes are expected to be used, each having more than 1 NIC. I would like to deploy the network manager on the controller node.

I thought creating virtual NICs could have been a workaround but that did not work.

Could anybody provide a small guide on how to modify the network configuration (e.g. creating virtual NICs, linux bridges, etc) but still using that guide as reference?

Thanks in advance, Francesco.

UPDATE 13/07/2015

I have switched to CentOS 7.1 and I still have some doubts regarding the network configuration.

Both the machines (Controller/Network and Compute) are connected to the same private network 10.20.151.0/24, which is routed to Internet through the gw 10.20.151.1. On both machines, the NIC connected to this network is em1. DHCP is disabled on this network.

I would like to a have the VM instances connected to a different network (e.g. 192.168.1.0/24) and have IP addresses assigned through DHCP. I would also like each VM instance to be connected to Internet and being accessible via ssh from the Controller and/or computing node.

Could you please help me to figure out how to change the settings in the answer file to achieve that?

Thanks very much, Francesco.

UPDATE 14/07/2015 After setting up the networks, subnets and router as advised, I cannot ping/ssh any VM instances. Furthermore I cannot ping any external IP from the VMs other than the virtual router (10.20.151.20) and the Network/Controller node.

On the Controller/Network:

ovs-vsctl show
91296ee0-4e36-420e-ba86-06995f4dba69
    Bridge br-int
        fail_mode: secure
        Port "qr-c15092f4-bb"
            tag: 1
            Interface "qr-c15092f4-bb"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "tapf3d9ab30-3e"
            tag: 1
            Interface "tapf3d9ab30-3e"
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "em1"
            Interface "em1"
        Port "qg-b9d315ce-54"
            Interface "qg-b9d315ce-54"
                type: internal
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
    Bridge br-tun
        fail_mode: secure                                                                                                                                    
        Port patch-int                                                                                                                                       
            Interface patch-int                                                                                                                              
                type: patch                                                                                                                                  
                options: {peer=patch-tun}                                                                                                                    
        Port br-tun                                                                                                                                          
            Interface br-tun                                                                                                                                 
                type: internal                                                                                                                               
        Port "vxlan-0a14972f"                                                                                                                                
            Interface "vxlan-0a14972f"                                                                                                                       
                type: vxlan                                                                                                                                  
                options: {df_default="true", in_key=flow, local_ip="10.20.151.48", out_key=flow, remote_ip="10.20.151.47"}                                   
    ovs_version: "2.3.1"



cat /etc/sysconfig/network-scripts/ifcfg-em1 
#HWADDR=74:E6:E2:DA:3A:61
DEVICE="em1"
ONBOOT=yes
TYPE="OVSPort"
DEVICETYPE="ovs"
OVS_BRIDGE="br-ex"
#BOOTPROTO=none
#IPADDR=10 ...
(more)