networking problems in running instances

Maybe U should input authorize command,
- for ping
# euca-authorize -P icmp -t -1:-1 default
- for ssh
# ecua-authorize -P tcp -p 22 default

I executed the commands you said jaes but I still can't access the instance via SSH, I rebooted the instance but nothing happened, ty for your answer :)

Cheers
Diego

There are definitely some issues with the setup. First of all, flat manager requires quite a bit of manual setup. You will probably have a much easier time using FlatDHCPManager

Fixed range should match the networks you have set up, and you probably need to set the dhcp start address
--fixed_range=192.168.0.0/24
--flat_network_dhcp_start=192.168.0.2

You may need to recreate your networks after making these changes.

Vish

On May 9, 2011, at 11:35 AM, Diego Lalo wrote:

> New question #156783 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/156783
>
> Hi everyone, it's me again :) This time I have issues with networking of the instances. I'm running openstack in a two node configuration, there are three instances running in a node and one in the other node, here is the output of euca-describe-instances:
>
> euca-describe-instances -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud
> RESERVATION r-qgwxc38z proj1 default
> INSTANCE i-00000002 ami-00000003 192.168.0.2 192.168.0.2 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:04Z nova
> RESERVATION r-0w1f16dn proj1 default
> INSTANCE i-00000004 ami-00000003 192.168.0.4 192.168.0.4 running None (proj1, eucalyptus) 0 m1.tiny 2011-05-09T17:57:28Z nova
> RESERVATION r-20qqjtse proj1 default
> INSTANCE i-00000003 ami-00000003 192.168.0.3 192.168.0.3 running None (proj1, openstack-in-a-box-1rev85) 0 m1.tiny 2011-05-09T17:57:18Z nova
>
> here is the nova.conf of the cloud controller:
>
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.208
> --rabbit_host=192.168.1.208
> --cc_host=192.168.1.208
> --ec2_url=http://192.168.1.208:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --network_size=88
> --network_manager=nova.network.manager.FlatManager
> --routing_source_ip=192.168.1.208
> --FAKE_subdomain=ec2
> --image_service=nova.image.glance.GlanceImageService
> --glance_host=192.168.1.208
> --glance_port=9292
> --sql_connection=mysql://root:nova@192.168.1.208/nova
>
> here is the nova.conf of the compute node:
>
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.208
> --rabbit_host=192.168.1.208
> --cc_host=192.168.1.208
> --ec2_url=http://192.168.1.208:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --network_size=18
> --network_manager=nova.network.manager.FlatManager
> --image_service=nova.image.glance.GlanceImageService
> --glance_host=192.168.1.208
> --glance_port=9292
> --sql_connection=mysql://root:nova@192.168.1.208/nova
>
>
> here is the ifconfig output of the cloud controller:
>
> br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
> inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1304169 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1881333 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:426295659 (426.2 MB) TX bytes:2294268253 (2.2 GB)
>
> eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
> inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1313062 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1885918 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:446334788 (446.3 MB) TX bytes:2294658231 (2.2 GB)
> Interrupt:42 Base address:0xc000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:3758394 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3758394 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2802947135 (2.8 GB) TX bytes:2802947135 (2.8 GB)
>
> virbr0 Link encap:Ethernet HWaddr 96:42:a5:d0:94:cd
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> vnet0 Link encap:Ethernet HWaddr fe:16:3e:19:29:3d
> inet6 addr: fe80::fc16:3eff:fe19:293d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:893 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:0 (0.0 B) TX bytes:61472 (61.4 KB)
>
> vnet1 Link encap:Ethernet HWaddr fe:16:3e:1a:67:89
> inet6 addr: fe80::fc16:3eff:fe1a:6789/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:887 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:0 (0.0 B) TX bytes:61112 (61.1 KB)
>
> here is the output of ifconfig of the compute node:
>
> br100 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1790111 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1063378 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2262867369 (2.2 GB) TX bytes:87105685 (87.1 MB)
>
> eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1791451 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1064105 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2288664158 (2.2 GB) TX bytes:87263526 (87.2 MB)
> Interrupt:42 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:249538 errors:0 dropped:0 overruns:0 frame:0
> TX packets:249538 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:17466459 (17.4 MB) TX bytes:17466459 (17.4 MB)
>
> virbr0 Link encap:Ethernet HWaddr 4a:c0:10:5a:06:2d
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> vnet0 Link encap:Ethernet HWaddr fe:16:3e:72:84:da
> inet6 addr: fe80::fc16:3eff:fe72:84da/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:798 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:1152 (1.1 KB) TX bytes:55528 (55.5 KB)
>
> here is the output of nova-manage network list:
>
> network netmask start address DNS
> 192.168.0.0/25 255.255.255.128 192.168.0.2 8.8.4.4
>
> here is the output of console.log of instance 4 wich is similar to the log of the other instances:
>
> Linux version 2.6.18-194.el5 (<email address hidden>) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Fri Apr 2 14:58:35 EDT 2010
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000010000 - 000000000009d400 (usable)
> BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000001fffd000 (usable)
> BIOS-e820: 000000001fffd000 - 0000000020000000 (reserved)
> BIOS-e820: 00000000feffc000 - 00000000ff000000 (reserved)
> BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
> 0MB HIGHMEM available.
> 511MB LOWMEM available.
> found SMP MP-table at 000fdbc0
> Memory for crash kernel (0x0 to 0x0) notwithin permissible range
> disabling kdump
> Using x86 segment limits to approximate NX protection
> DMI 2.4 present.
> kvm-clock: cpu 0, msr 0:73f9e1, boot clock
> Using APIC driver default
> ACPI: PM-Timer IO Port: 0xb008
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 6:2 APIC version 20
> ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> Enabling APIC mode: Flat. Using 1 I/O APICs
> ACPI: HPET id: 0x8086a201 base: 0xfed00000
> Using ACPI (MADT) for SMP configuration information
> Allocating PCI resources starting at 30000000 (gap: 20000000:deffc000)
> TSC: Frequency read from the hypervisor
> Detected 2700.000 MHz processor.
> kvm-clock: cpu 0, msr 0:1404461, primary cpu clock
> Built 1 zonelists. Total pages: 131069
> Kernel command line: root=/dev/vda console=ttyS0
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> CPU 0 irqstacks, hard=c0768000 soft=c0748000
> PID hash table entries: 2048 (order: 11, 8192 bytes)
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Memory: 512304k/524276k available (2178k kernel code, 11408k reserved, 907k data, 228k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> hpet0: at MMIO 0xfed00000 (virtual 0xe0800000), IRQs 2, 8, 0
> hpet0: 3 64-bit timers, 100000000 Hz
> Using HPET for base-timer
> Calibrating delay loop (skipped), value calculated using timer frequency.. 5400.00 BogoMIPS (lpj=2700000)
> Security Framework v1.0.0 initialized
> SELinux: Initializing.
> selinux_register_security: Registering secondary module capability
> Capability LSM initialized as secondary
> Mount-cache hash table entries: 512
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 512K (64 bytes/line)
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> Checking 'hlt' instruction... OK.
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 14k freed
> ACPI: Core revision 20060707
> CPU0: AMD QEMU Virtual CPU version 0.13.91 stepping 03
> Total of 1 processors activated (5400.00 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> Using local APIC timer interrupts.
> WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
> Brought up 1 CPUs
> checking if image is initramfs... it is
> Freeing initrd memory: 2706k freed
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0
> PCI: Using configuration type 1
> Setting up standard PCI resources
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: No dock devices found.
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI quirk: region b000-b03f claimed by PIIX4 ACPI
> PCI quirk: region b100-b10f claimed by PIIX4 SMB
> ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI init
> pnp: PnP ACPI: found 6 devices
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
> NetLabel: Initializing
> NetLabel: domain hash size = 128
> NetLabel: protocols = UNLABELED CIPSOv4
> NetLabel: unlabeled traffic allowed by default
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
> apm: overridden by ACPI.
> audit: initializing netlink socket (disabled)
> type=2000 audit(1304964042.651:1): initialized
> Total HugeTLB memory allocated, 0
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> alg: No test for crc32c (crc32c-generic)
> ksign: Installing public key data
> Loading keyring
> - Added public key 285B5C47ED7A1E8E
> - User ID: CentOS (Kernel Module GPG key)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Limiting direct PCI/PCI transfers.
> PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
> Activating ISA DMA hang workarounds.
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> Real Time Clock Driver v1.12ac
> Non-volatile memory driver v1.2
> Linux agpgart interface v0.101 (c) Dave Jones
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> �serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> brd: module loaded
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIX3: IDE controller at PCI slot 0000:00:01.1
> PIIX3: chipset revision 0
> PIIX3: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
> ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
> ide-floppy driver 0.99.newide
> usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> TCP bic registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Using IPI No-Shortcut mode
> Time: kvm-clock clocksource has been installed.
> ACPI: (supports S3 S4 S5)
> Initalizing network drop monitor service
> Freeing unused kernel memory: 228k freed
> Write protecting the kernel read-only data: 409k
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> input: AT Translated Set 2 keyboard as /class/input/input0
> input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
> Creating block device nodes.
> Loading ehci-hcd.ko module
> Loading ohci-hcd.ko module
> Loading uhci-hcd.ko module
> USB Universal Host Controller Interface driver v3.0
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:01.2[D] -> Link [LNKD] -> GSI 11 (level, high) -> IRQ 11
> uhci_hcd 0000:00:01.2: UHCI Host Controller
> uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
> uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c020
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> Loading jbd.ko module
> Loading ext3.ko module
> Loading scsi_mod.ko module
> SCSI subsystem initialized
> Loading sd_mod.ko module
> Loading scsi_transport_spi.ko module
> Loading sym53c8xx.ko module
> Loading libata.ko module
> Loading ata_piix.ko module
> Loading dm-mem-cache.ko module
> Loading dm-mod.ko module
> device-mapper: uevent: version 1.0.3
> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: <email address hidden>
> Loading dm-log.ko module
> Loading dm-region_hash.ko module
> Loading dm-message.ko module
> Loading dm-raid45.ko module
> device-mapper: dm-raid45: initialized v0.2594l
> Loading xen-platform-pci.ko module
> Loading xen-vbd.ko module
> insmod: error inserting '/lib/xen-vbd.ko': -1 No such device
> Loading xen-balloon.ko module
> xen_mem: Initialising balloon driver.
> Loading xen-vnif.ko module
> netfront: Initialising virtual ethernet driver.
> insmod: error inserting '/lib/xen-vnif.ko': -1 No such device
> Loading mptbase.ko module
> Fusion MPT base driver 3.04.13rh
> Copyright (c) 1999-2008 LSI Corporation
> Loading mptscsih.ko module
> Loading mptspi.ko module
> Fusion MPT SPI Host driver 3.04.13rh
> Loading scsi_transport_sas.ko module
> Loading mptsas.ko module
> Fusion MPT SAS Host driver 3.04.13rh
> Loading virtio.ko module
> Loading virtio_ring.ko module
> Loading virtio_pci.ko module
> ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 11 (level, high) -> IRQ 11
> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
> ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 10 (level, high) -> IRQ 10
> Loading virtio_blk.ko module
> vda: unknown partition table
> Loading virtio_net.ko module
> Loading virtio_balloon.ko module
> Loading ahci.ko module
> Waiting for driver initialization.
> TSC appears to be running slowly. Marking it as unstable
> Scanning and configuring dmraid supported devices
> Trying to resume from LABEL=SWAP-sda2
> Unable to access resume device (LABEL=SWAP-sda2)
> Creating root device.
> Mounting root filesystem.
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Setting up other filesystems.
> Setting up new root fs
> no fstab.sys, mounting internal defaults
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> type=1404 audit(1304964071.221:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
> type=1403 audit(1304964071.464:3): policy loaded auid=4294967295 ses=4294967295
> INIT: version 2.86 booting
> Welcome to CentOS release 5.5 (Final)
> Press 'I' to enter interactive startup.
> Setting clock (localtime): Mon May 9 18:01:14 BST 2011 [ OK ]
> Starting udev: [ OK ]
> Loading default keymap (us): [ OK ]
> Setting hostname Centos5-5-32Bits-1-0rev2-openstack: [ OK ]
> No devices found
> Setting up Logical Volume Management: [ OK ]
> Checking filesystems
> Checking all file systems.
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/vda
> /: Superblock last mount time is in the future. FIXED.
> /: Superblock last write time is in the future. FIXED.
> /: clean, 23914/397696 files, 220585/397600 blocks
> [ OK ]
> Remounting root filesystem in read-write mode: [ OK ]
> Mounting local filesystems: [ OK ]
> Enabling /etc/fstab swaps: [ OK ]
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> Starting mcstransd: [ OK ]
> Bringing up loopback interface: [ OK ]
> Bringing up interface eth0:
> Determining IP information for eth0... done.
> [ OK ]
> Starting restorecond: [ OK ]
> Starting system message bus: [ OK ]
> Mounting other filesystems: [ OK ]
> Starting HAL daemon: [ OK ]
> Generating SSH1 RSA host key: [ OK ]
> Generating SSH2 RSA host key: [ OK ]
> Generating SSH2 DSA host key: [ OK ]
> Starting sshd: [ OK ]
>
> I can't access the instances using ssh or ping them, the only way to access them is using virt-manager inside the physical machine where the instance is running and opening a console. For example if I do that for instance 4 and execute ifconfig inside the console I can see the real IP of the instance which is 192.168.1.203 and not 192.168.0.4 as euca-describe-instances says. What am I doing wrong?
>
>
> Cheers
> Diego
>
>
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

          Thanks for your answer Vish, I did what you said, I deleted the network using nova-manage, I recreated it using nova-manage network create 192.168.0.0/24 1 255 and finally I restarted all the nova-services on both nodes but I still can't access the instance, if I access the instance using virt-manager and execute ifconfig the IP I see was 192.168.1.233 and not 192.168.0.2, here is the output of euca2ools commands:

[root@lore 160]# euca-run-instances ami-00000003 -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud --kernel aki-00000001 --ramdisk ari-00000002 -t m1.tiny
RESERVATION r-2j0vsybx proj1 default
INSTANCE i-00000008 ami-00000003 scheduling None (proj1, None) 2011-05-11T18:06:19Z None None
[root@lore 160]# euca-describe-instances -a 3b96cc4b-6cba-45b0-bded-2a0356726a5e:proj1 -s b5dd676e-dacc-4cec-bb16-1ebf2d15018b --url http://192.168.1.208:8773/services/Cloud
RESERVATION r-2j0vsybx proj1 default
INSTANCE i-00000008 ami-00000003 192.168.0.2 192.168.0.2 running None (proj1, eucalyptus) 0 m1.tiny 2011-05-11T18:06:19Z nova

Cheers
Diego

192.168.0.0/24 1 255
that should be 256 not 255 (there are 256 addresses in a /24)

The issue that you are having is that you have another dhcp server responding to dhcp requests for that network. You may have an easier time using the 10.x range instead of the 192.168 range. Otherwise you will need to make sure that your other dhcp server isn't handing out ips, which may be a little to complicated to tackle.

You also should probably killall dnsmasq and restart nova-network to make sure that there aren't any lingering dhcp servers on the network host.

Vish

I tried what you said, I modified nova.conf in both machines with the following info:

CLOUD CONTROLLER
br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
          inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1768290 errors:0 dropped:0 overruns:0 frame:0
          TX packets:889712 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:477168390 (477.1 MB) TX bytes:99689011 (99.6 MB)

eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
          inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1769340 errors:0 dropped:0 overruns:0 frame:0
          TX packets:890126 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:501999740 (501.9 MB) TX bytes:99716935 (99.7 MB)
          Interrupt:42 Base address:0xa000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:7259945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7259945 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5251451354 (5.2 GB) TX bytes:5251451354 (5.2 GB)

virbr0 Link encap:Ethernet HWaddr de:18:35:e5:fa:1c
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

COMPUTE NODE

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=192.168.1.208
--rabbit_host=192.168.1.208
--cc_host=192.168.1.208
--ec2_url=http://192.168.1.208:8773/services/Cloud
--fixed_range=10.0.0.0/12
--flat_network_dhcp_start=10.0.0.2
--network_size=88
--network_manager=nova.network.manager.FlatManager
--routing_source_ip=192.168.1.208
--FAKE_subdomain=ec2
--image_service=nova.image.glance.GlanceImageService
--glance_host=192.168.1.208
--glance_port=9292
--sql_connection=mysql://root:nova@192.168.1.208/nova

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=192.168.1.208
--rabbit_host=192.168.1.208
--cc_host=192.168.1.208
--ec2_url=http://192.168.1.208:8773/services/Cloud
--fixed_range=10.0.0.0/12
--flat_network_dhcp_start=10.0.0.2
--network_size=18
--network_manager=nova.network.manager.FlatManager
--image_service=nova.image.glance.GlanceImageService
--glance_host=192.168.1.208
--glance_port=9292
--sql_connection=mysql://root:nova@192.168.1.208/nova

br100 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
          inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:811685 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1550850 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:70397638 (70.3 MB) TX bytes:172917703 (172.9 MB)

eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
          inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:812807 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1551314 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:81841781 (81.8 MB) TX bytes:172950079 (172.9 MB)
          Interrupt:42 Base address:0xe000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:2441 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:328348 (328.3 KB) TX bytes:328348 (328.3 KB)

virbr0 Link encap:Ethernet HWaddr ce:1f:21:69:bf:8f
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

I created the network using:

nova-manage network create 10.0.0.0/12 1 255 (I don't know the amount of a /12 but 255 IPs is enough for me :) )

I killed all dnsmasq processes on both nodes and I restarted nova-network in the Cloud Controller but the network still not working, are the bridges configured fine or there is a mistake?

Cheers
Diego

A) network_size should be a power of two so use 256 instead of 255
B) You still need to switch to FlatDHCPManager
C) The bridges will be created automatically by FlatDHCP so you can move the ip back to eth0 and delete the br100

Vish

On May 11, 2011, at 12:31 PM, Diego Lalo wrote:

> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Open
>
> Diego Lalo is still having a problem:
> I tried what you said, I modified nova.conf in both machines with the
> following info:
>
> CLOUD CONTROLLER
> br100 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
> inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1768290 errors:0 dropped:0 overruns:0 frame:0
> TX packets:889712 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:477168390 (477.1 MB) TX bytes:99689011 (99.6 MB)
>
> eth0 Link encap:Ethernet HWaddr bc:ae:c5:c1:d1:c3
> inet6 addr: fe80::beae:c5ff:fec1:d1c3/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1769340 errors:0 dropped:0 overruns:0 frame:0
> TX packets:890126 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:501999740 (501.9 MB) TX bytes:99716935 (99.7 MB)
> Interrupt:42 Base address:0xa000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:7259945 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7259945 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:5251451354 (5.2 GB) TX bytes:5251451354 (5.2 GB)
>
> virbr0 Link encap:Ethernet HWaddr de:18:35:e5:fa:1c
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> COMPUTE NODE
>
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.208
> --rabbit_host=192.168.1.208
> --cc_host=192.168.1.208
> --ec2_url=http://192.168.1.208:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --flat_network_dhcp_start=10.0.0.2
> --network_size=88
> --network_manager=nova.network.manager.FlatManager
> --routing_source_ip=192.168.1.208
> --FAKE_subdomain=ec2
> --image_service=nova.image.glance.GlanceImageService
> --glance_host=192.168.1.208
> --glance_port=9292
> --sql_connection=mysql://root:nova@192.168.1.208/nova
>
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.208
> --rabbit_host=192.168.1.208
> --cc_host=192.168.1.208
> --ec2_url=http://192.168.1.208:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --flat_network_dhcp_start=10.0.0.2
> --network_size=18
> --network_manager=nova.network.manager.FlatManager
> --image_service=nova.image.glance.GlanceImageService
> --glance_host=192.168.1.208
> --glance_port=9292
> --sql_connection=mysql://root:nova@192.168.1.208/nova
>
> br100 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:811685 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1550850 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:70397638 (70.3 MB) TX bytes:172917703 (172.9 MB)
>
> eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:812807 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1551314 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:81841781 (81.8 MB) TX bytes:172950079 (172.9 MB)
> Interrupt:42 Base address:0xe000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:2441 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2441 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:328348 (328.3 KB) TX bytes:328348 (328.3 KB)
>
> virbr0 Link encap:Ethernet HWaddr ce:1f:21:69:bf:8f
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
>
> I created the network using:
>
> nova-manage network create 10.0.0.0/12 1 255 (I don't know the amount of
> a /12 but 255 IPs is enough for me :) )
>
> I killed all dnsmasq processes on both nodes and I restarted nova-
> network in the Cloud Controller but the network still not working, are
> the bridges configured fine or there is a mistake?
>
>
> Cheers
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

              Is working nooooowwww!!!!! Thanks for your help Vish, the instance gets the right IP and can be accessed via SSH from within the physical machine that is running, for the moment I can't access the instance from other machine inside the local network, the instance IP is 10.0.0.2 and the local machines of our network are in the net 192.168.1.0 how can I do to acces the instance from my machine for example? My IP is 192.168.1.100

Cheers
Diego

I have another question about multinode configuration, I have two compute nodes, the network manager is FlatDHCPManager and the network is 10.0.0.0/12, I configured both nodes with the same flags:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=192.168.1.234
--rabbit_host=192.168.1.234
--cc_host=192.168.1.234
--ec2_url=http://192.168.1.234:8773/services/Cloud
--fixed_range=10.0.0.0/12
--network_size=2048
--network_manager=nova.network.manager.FlatDHCPManager
--routing_source_ip=192.168.1.234
--FAKE_subdomain=ec2
--image_service=nova.image.glance.GlanceImageService
--glance_host=192.168.1.234
--glance_port=9292
--sql_connection=mysql://root:nova@192.168.1.234/nova

The problem is that one of the nodes has no IP in it's bridge, this is the output of ifconfig in the CloudController:

br100 Link encap:Ethernet HWaddr fe:16:3e:18:b4:41
          inet addr:10.0.0.1 Bcast:10.0.3.255 Mask:255.255.252.0
          inet6 addr: fe80::5c06:fdff:fef5:bef0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1046 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1101 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:175557 (175.5 KB) TX bytes:193852 (193.8 KB)

eth0 Link encap:Ethernet HWaddr 00:24:8c:2e:50:88
          inet addr:192.168.1.234 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::224:8cff:fe2e:5088/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1272863 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1852857 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:433340720 (433.3 MB) TX bytes:2296477103 (2.2 GB)
          Interrupt:42 Base address:0x6000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:3224420 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3224420 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4916528700 (4.9 GB) TX bytes:4916528700 (4.9 GB)

virbr0 Link encap:Ethernet HWaddr 82:af:25:15:73:00
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet0 Link encap:Ethernet HWaddr fe:16:3e:18:b4:41
          inet6 addr: fe80::fc16:3eff:fe18:b441/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:431 errors:0 dropped:0 overruns:0 frame:0
          TX packets:630 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:75956 (75.9 KB) TX bytes:89856 (89.8 KB)

vnet1 Link encap:Ethernet HWaddr fe:16:3e:61:e8:a9
          inet6 addr: fe80::fc16:3eff:fe61:e8a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:300 errors:0 dropped:0 overruns:0 frame:0
          TX packets:434 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:54527 (54.5 KB) TX bytes:65572 (65.5 KB)

vnet2 Link encap:Ethernet HWaddr fe:16:3e:71:51:0c
          inet6 addr: fe80::fc16:3eff:fe71:510c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:170 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:32256 (32.2 KB) TX bytes:40773 (40.7 KB)

vnet3 Link encap:Ethernet HWaddr fe:16:3e:3e:a0:39
          inet6 addr: fe80::fc16:3eff:fe3e:a039/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:9642 (9.6 KB) TX bytes:13266 (13.2 KB)

vnet4 Link encap:Ethernet HWaddr fe:16:3e:54:0e:16
          inet6 addr: fe80::fc16:3eff:fe54:e16/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:51 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:9258 (9.2 KB) TX bytes:12867 (12.8 KB)

vnet5 Link encap:Ethernet HWaddr fe:16:3e:52:c8:ef
          inet6 addr: fe80::fc16:3eff:fe52:c8ef/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:9642 (9.6 KB) TX bytes:13266 (13.2 KB)

And here is the output of ifconfig of the Compute Node:

br100 Link encap:Ethernet HWaddr fe:16:3e:2f:3c:1a
          inet6 addr: fe80::d878:36ff:fe03:47e2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)

eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
          inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:16369 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29714 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1790308 (1.7 MB) TX bytes:3021205 (3.0 MB)
          Interrupt:42

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

virbr0 Link encap:Ethernet HWaddr 0e:77:fd:80:e5:82
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet0 Link encap:Ethernet HWaddr fe:16:3e:2f:3c:1a
          inet6 addr: fe80::fc16:3eff:fe2f:3c1a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B) TX bytes:1268 (1.2 KB)

So br100 has no IP on the compute node, what are the modifs I need to do to have both nodes working?

Cheers
Diego

You have a couple options here.

1. set up a route on the external node specifying the host as the gateway.
route add -net 10.0.0.0/24 gw 192.168.1.100

2. use floating ips and euca-allocate-address and euca-associate-address
nova-manage floating create <hostname> 192.168.1.128/25 # hostname is the hostname of the host running nova-network
euca-allocate-address
euca-associate-address -i i-1 192.168.1.128 # for example

either way you will need to use euca-authorize to open up specific ports to be accessible:
euca-authorize -P tcp -p 22 default

Vish

On May 12, 2011, at 7:26 AM, Diego Lalo wrote:

> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Solved
>
> Diego Lalo confirmed that the question is solved:
> Is working nooooowwww!!!!! Thanks for your help Vish, the
> instance gets the right IP and can be accessed via SSH from within the
> physical machine that is running, for the moment I can't access the
> instance from other machine inside the local network, the instance IP is
> 10.0.0.2 and the local machines of our network are in the net
> 192.168.1.0 how can I do to acces the instance from my machine for
> example? My IP is 192.168.1.100
>
>
> Cheers
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

       Ty for your answer Vish, but how I configure the extra compute node to make it work? I mean when I launch an instance that will run in the new compute node it doesn't get a valid IP because the bridge has no IP on that node, how I should create the network for the project and how should the flags be configured for each node (the Cloud Controller and the Compute Node).

Cheers
Diego

If you want to use flatdchp with multiple hosts you will need to use
--flat_interface=eth0 # or whatever interface they share

If you only have one interface on all of your hosts, you also may need to do:
ip link set promisc on dev br100

Vish

On May 12, 2011, at 9:41 AM, Diego Lalo wrote:

> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Open
>
> Diego Lalo is still having a problem:
> Ty for your answer Vish, but how I configure the extra compute
> node to make it work? I mean when I launch an instance that will run in
> the new compute node it doesn't get a valid IP because the bridge has no
> IP on that node, how I should create the network for the project and how
> should the flags be configured for each node (the Cloud Controller and
> the Compute Node).
>
> Cheers
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

      I tried to do what you said: ip link set promisc on dev br100 on the compute node but br100 only appears when some instance is launched on that node but it doesn't exist right now. I also set the flag --flat_interface on both nodes.

Cheers
Diego

Promisc only needs to be set on the network host. You will have to restart
all of the workers after setting flat interface.
On May 12, 2011 12:25 PM, "Diego Lalo" <email address hidden>
wrote:
> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Open
>
> Diego Lalo is still having a problem:
> I tried to do what you said: ip link set promisc on dev br100 on
> the compute node but br100 only appears when some instance is launched
> on that node but it doesn't exist right now. I also set the flag
> --flat_interface on both nodes.
>
> Cheers
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Thanks again for your answer Vish, I restarted both machines and I set promisc only in the host that is running nova-network, now in the compute node the instance gets the correct IP but it can't be pinged or accessed via SSH, I executed ifconfig in the compute node after launching the instance and this is the output:

br100 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
          inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::c448:7aff:fef8:fa05/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:18055 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34659 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1542409 (1.5 MB) TX bytes:11416258 (11.4 MB)

eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
          inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:26926 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50887 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2928673 (2.9 MB) TX bytes:13152301 (13.1 MB)
          Interrupt:42 Base address:0x8000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:935 errors:0 dropped:0 overruns:0 frame:0
          TX packets:935 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:187503 (187.5 KB) TX bytes:187503 (187.5 KB)

virbr0 Link encap:Ethernet HWaddr 42:9c:11:d8:13:d0
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet0 Link encap:Ethernet HWaddr fe:16:3e:2f:d6:3b
          inet6 addr: fe80::fc16:3eff:fe2f:d63b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:33 errors:0 dropped:0 overruns:0 frame:0
          TX packets:248 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:4835 (4.8 KB) TX bytes:18541 (18.5 KB)

Cheers
Diego

Are you pinging from the network host? You won't be able to get to it from
the compute host. If you get console output on the instance are there any
errors?
On May 12, 2011 2:01 PM, "Diego Lalo" <email address hidden>
wrote:
> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Open
>
> Diego Lalo is still having a problem:
> Thanks again for your answer Vish, I restarted both machines and I set
> promisc only in the host that is running nova-network, now in the
> compute node the instance gets the correct IP but it can't be pinged or
> accessed via SSH, I executed ifconfig in the compute node after
> launching the instance and this is the output:
>
> br100 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::c448:7aff:fef8:fa05/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:18055 errors:0 dropped:0 overruns:0 frame:0
> TX packets:34659 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1542409 (1.5 MB) TX bytes:11416258 (11.4 MB)
>
> eth0 Link encap:Ethernet HWaddr 00:24:8c:88:a2:9d
> inet6 addr: fe80::224:8cff:fe88:a29d/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:26926 errors:0 dropped:0 overruns:0 frame:0
> TX packets:50887 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2928673 (2.9 MB) TX bytes:13152301 (13.1 MB)
> Interrupt:42 Base address:0x8000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:935 errors:0 dropped:0 overruns:0 frame:0
> TX packets:935 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:187503 (187.5 KB) TX bytes:187503 (187.5 KB)
>
> virbr0 Link encap:Ethernet HWaddr 42:9c:11:d8:13:d0
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> vnet0 Link encap:Ethernet HWaddr fe:16:3e:2f:d6:3b
> inet6 addr: fe80::fc16:3eff:fe2f:d63b/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:33 errors:0 dropped:0 overruns:0 frame:0
> TX packets:248 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:4835 (4.8 KB) TX bytes:18541 (18.5 KB)
>
>
> Cheers
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

The console output is fine, you are right I can't access the instance from within the compute node but I can access it through the cloud controller :) The only problem that remains is that the instance doesn't have internet, I tried to do a yum update from within the instance and nothing happened, I also tried to do a ping www.free.fr and didn't work:

-bash-3.2# ping www.free.fr
PING www.free.fr (212.27.48.10) 56(84) bytes of data.

this is the only line that appears in the instance console

Thanks a lot for the help you are giving to me Vish!!
Diego

The promisc on is supposed to fix the public internet problem. you might want to make sure you set
--my_ip=192.168.1.100 # (or whatever the ip is for each server)
sometimes it can't discover the key properly. Afterwards you may have to flush all of the iptables rules on both hosts and restart the services and rerun instances.

Vish

On May 12, 2011, at 12:16 PM, Diego Lalo wrote:

> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Open
>
> Diego Lalo is still having a problem:
> The console output is fine, you are right I can't access the instance
> from within the compute node but I can access it through the cloud
> controller :) The only problem that remains is that the instance doesn't
> have internet, I tried to do a yum update from within the instance and
> nothing happened, I also tried to do a ping www.free.fr and didn't work:
>
> -bash-3.2# ping www.free.fr
> PING www.free.fr (212.27.48.10) 56(84) bytes of data.
>
> this is the only line that appears in the instance console
>
>
> Thanks a lot for the help you are giving to me Vish!!
> Diego
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

I reconfigured the cloud and the problem has gone, ty for your help Vish :)

\o/
On May 12, 2011, at 1:45 PM, Diego Lalo wrote:

> Question #156783 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/156783
>
> Status: Answered => Solved
>
> Diego Lalo confirmed that the question is solved:
> I reconfigured the cloud and the problem has gone, ty for your help Vish
> :)
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).