OpenStack Compute (nova)

Installed Openstack Nova in RedHat Enterprise 6, can upload custom image, run instances, but can't ping neither ssh to VMs

Asked by Liang

I'm new to openstack cloud, but managed to install Openstack Nova in 2 RedHat Enterprise 6 by following documents in wiki, especially "http://wiki.openstack.org/NovaInstall/RHEL6Notes", I was able to custom made a RedHat Enterprise 6 image and uploaded, run instance and saw they show "running", but can't ssh or ping the VMs, of course, I did the euca-authorize thingy. Also, I can't seemed to be able to deploy VMs to 2nd node (computing node) and I ran nova-compute on both controller and computing node.
Following are my configuration files, hope someone can enlighten:

controller:
cat /etc/nova/nova.conf
--verbose=1
--ec2_url=http://10.208.3.239:8773/services/Cloud
--s3_host=10.208.3.239
--cc_host=10.208.3.239
--rabbit_host=10.208.3.239
--sql_connection=mysql://nova:nova@10.208.3.239/nova
--glance_port=9292
--glance_host=10.208.3.239
--use_s3=true
--libvirt_type=kvm
--use_syslog=false
--node_availability_zone=tcscld
--logging_context_format_string=%(asctime)s %(name)s: %(levelname)s [%(request_id)s %(user)s %(project)s] %(message)s
--logging_default_format_string=%(asctime)s %(name)s: %(message)s
--logging_debug_format_suffix=
--use_cow_images=true
--auth_driver=nova.auth.dbdriver.DbDriver
--network_manager=nova.network.manager.FlatDHCPManager
--scheduler_driver=nova.scheduler.zone.ZoneScheduler
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--image_service=nova.image.s3.S3ImageService
--use_ipv6=false
--ca_path=/var/lib/nova/CA
--keys_path=/var/lib/nova/keys
--images_path=/var/lib/nova/images
--buckets_path=/var/lib/nova/buckets
--instances_path=/var/lib/nova/instances
--networks_path=/var/lib/nova/networks
--injected_network_template=/usr/share/nova/interfaces.rhel.template
--libvirt_xml_template=/usr/share/nova/libvirt.xml.template
--vpn_client_template=/usr/share/nova/client.ovpn.template
--credentials_template=/usr/share/nova/novarc.template
--state_path=/var/lib/nova
--flat_interface=eth1
--flat_injected=false
--flat_network_dhcp_start=10.0.0.2
--public_interface=eth0
--fixed_range=10.0.0.0/12
--network_size=32

brctl show:
bridge name bridge id STP enabled interfaces
br100 8000.002128776e85 no eth1
       vnet0
       vnet1
       vnet2
       vnet3
virbr0 8000.000000000000 yes

ip a sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:21:28:77:6e:84 brd ff:ff:ff:ff:ff:ff
    inet 10.208.3.239/23 brd 10.208.3.255 scope global eth0
    inet6 fe80::221:28ff:fe77:6e84/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:21:28:77:6e:85 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::221:28ff:fe77:6e85/64 scope link
       valid_lft forever preferred_lft forever
4: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:21:28:77:6e:85 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.1/26 brd 10.0.0.63 scope global br100
    inet 169.254.169.254/32 scope global br100
    inet6 fe80::221:28ff:fe77:6e85/64 scope link
       valid_lft forever preferred_lft forever
5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether b2:2d:83:3c:93:d1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:58:19:ca brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe58:19ca/64 scope link
       valid_lft forever preferred_lft forever
8: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:5d:02:de brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe5d:2de/64 scope link
       valid_lft forever preferred_lft forever
11: vnet3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:74:c3:61 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe74:c361/64 scope link
       valid_lft forever preferred_lft forever
12: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:5f:0b:70 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe5f:b70/64 scope link
       valid_lft forever preferred_lft forever

iptables:
/etc/init.d/iptables status
Table: mangle
Chain PREROUTING (policy ACCEPT)
num target prot opt source destination

Chain INPUT (policy ACCEPT)
num target prot opt source destination

Chain FORWARD (policy ACCEPT)
num target prot opt source destination

Chain OUTPUT (policy ACCEPT)
num target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
num target prot opt source destination
1 CHECKSUM udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:68 CHECKSUM fill

Table: nat
Chain PREROUTING (policy ACCEPT)
num target prot opt source destination
1 DNAT tcp -- 0.0.0.0/0 169.254.169.254 tcp dpt:80 to:10.208.3.239:8773

Chain POSTROUTING (policy ACCEPT)
num target prot opt source destination
1 MASQUERADE tcp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535
2 MASQUERADE udp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535
3 MASQUERADE all -- 192.168.122.0/24 !192.168.122.0/24
4 ACCEPT all -- 10.0.0.0/12 10.0.0.0/12
5 ACCEPT all -- 10.0.0.0/12 10.128.0.0/24
6 SNATTING all -- 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
num target prot opt source destination

Chain SNATTING (1 references)
num target prot opt source destination
1 SNAT all -- 10.0.0.0/12 0.0.0.0/0 to:10.208.3.239

Table: filter
Chain INPUT (policy ACCEPT)
num target prot opt source destination
1 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
2 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53
3 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:67
4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:67

Chain FORWARD (policy ACCEPT)
num target prot opt source destination
1 nova-local all -- 0.0.0.0/0 0.0.0.0/0
2 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED
5 ACCEPT all -- 192.168.122.0/24 0.0.0.0/0
6 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
7 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable
8 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable

Chain OUTPUT (policy ACCEPT)
num target prot opt source destination
1 nova-local all -- 0.0.0.0/0 0.0.0.0/0

Chain nova-fallback (3 references)
num target prot opt source destination
1 DROP all -- 0.0.0.0/0 0.0.0.0/0

Chain nova-inst-17 (1 references)
num target prot opt source destination
1 DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
2 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
3 nova-sg-1 all -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT udp -- 10.0.0.1 0.0.0.0/0 udp spt:67 dpt:68
5 ACCEPT all -- 10.0.0.0/26 0.0.0.0/0
6 nova-fallback all -- 0.0.0.0/0 0.0.0.0/0

Chain nova-inst-19 (1 references)
num target prot opt source destination
1 DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
2 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
3 nova-sg-1 all -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT udp -- 10.0.0.1 0.0.0.0/0 udp spt:67 dpt:68
5 ACCEPT all -- 10.0.0.0/26 0.0.0.0/0
6 nova-fallback all -- 0.0.0.0/0 0.0.0.0/0

Chain nova-inst-24 (1 references)
num target prot opt source destination
1 DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
2 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
3 nova-sg-1 all -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT udp -- 10.0.0.1 0.0.0.0/0 udp spt:67 dpt:68
5 ACCEPT all -- 10.0.0.0/26 0.0.0.0/0
6 nova-fallback all -- 0.0.0.0/0 0.0.0.0/0

Chain nova-local (2 references)
num target prot opt source destination
1 nova-inst-24 all -- 0.0.0.0/0 10.0.0.11
2 nova-inst-17 all -- 0.0.0.0/0 10.0.0.9
3 nova-inst-19 all -- 0.0.0.0/0 10.0.0.10

Chain nova-sg-1 (3 references)
num target prot opt source destination
1 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0
2 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22

nova-compute node:
--verbose=1
--ec2_url=http://10.208.3.239:8773/services/Cloud
--s3_host=10.208.3.239
--cc_host=10.208.3.239
--rabbit_host=10.208.3.239
--sql_connection=mysql://nova:nova@10.208.3.239/nova
--glance_port=9292
--glance_host=10.208.3.239
--use_s3=true
--libvirt_type=kvm
--use_syslog=false
--node_availability_zone=tcscld
--logging_context_format_string=%(asctime)s %(name)s: %(levelname)s [%(request_id)s %(user)s %(project)s] %(message)s
--logging_default_format_string=%(asctime)s %(name)s: %(message)s
--logging_debug_format_suffix=
--use_cow_images=true
--auth_driver=nova.auth.dbdriver.DbDriver
--network_manager=nova.network.manager.FlatDHCPManager
--scheduler_driver=nova.scheduler.zone.ZoneScheduler
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--image_service=nova.image.s3.S3ImageService
--use_ipv6=false
--ca_path=/var/lib/nova/CA
--keys_path=/var/lib/nova/keys
--images_path=/var/lib/nova/images
--buckets_path=/var/lib/nova/buckets
--instances_path=/var/lib/nova/instances
--networks_path=/var/lib/nova/networks
--injected_network_template=/usr/share/nova/interfaces.rhel.template
--libvirt_xml_template=/usr/share/nova/libvirt.xml.template
--vpn_client_template=/usr/share/nova/client.ovpn.template
--credentials_template=/usr/share/nova/novarc.template
--state_path=/var/lib/nova
--flat_interface=eth1
--flat_injected=false
--public_interface=eth0
--flat_network_dhcp_start=10.0.0.2
--fixed_range=10.0.0.0/12
--network_size=32

brctl show
bridge name bridge id STP enabled interfaces
br100 8000.002128776e1d no eth1
virbr0 8000.000000000000 yes

ip a sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:21:28:77:6e:1c brd ff:ff:ff:ff:ff:ff
    inet 10.208.3.238/23 brd 10.208.3.255 scope global eth0
    inet6 fe80::221:28ff:fe77:6e1c/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:21:28:77:6e:1d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::221:28ff:fe77:6e1d/64 scope link
       valid_lft forever preferred_lft forever
4: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:21:28:77:6e:1d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::221:28ff:fe77:6e1d/64 scope link
       valid_lft forever preferred_lft forever
5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether e6:28:cc:d6:80:ee brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

euca-describe-instances
RESERVATION r-75d0nt9e tcscld default
INSTANCE i-00000013 ami-ajqon2tn 10.0.0.10 10.0.0.10 running None (tcscld, tcscld01.aero.org) 0 m1.small 2011-03-27 03:12:50 tcscld
RESERVATION r-9yrn6tn6 tcscld default
INSTANCE i-00000011 ami-ajqon2tn 10.0.0.9 10.0.0.9 running None (tcscld, tcscld01.aero.org) 0 m1.small 2011-03-27 03:12:43 tcscld
RESERVATION r-ifopq0tl tcscld default
INSTANCE i-00000018 ami-ajqon2tn 10.0.0.11 10.0.0.11 running None (tcscld, tcscld01.aero.org) 0 m1.small 2011-03-27 18:37:52 tcscld

using virt-manager, I can see all the running instances, but console was not available.
console log from one of the running VM follow:
  Welcome to Red Hat Enterprise Linux Server
Starting udev: udev: starting version 147
piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
8139cp 0000:00:02.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, high) -> IRQ 11
eth0: RTL-8139C+ at 0xffffc900009b8000, 02:16:3e:58:19:ca, IRQ 11
8139too Fast Ethernet driver 0.9.28
[ OK ]
Setting hostname nova-rhel: [ OK ]
Setting up Logical Volume Management: No volume groups found
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/vda
/dev/vda: clean, 29726/655360 files, 255255/2621440 blocks
[ OK ]
Remounting root filesystem in read-write mode: EXT3 FS on vda, internal journal
[ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
Entering non-interactive startup
Calling the system activity data collector (sadc):
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
[ OK ]
Bringing up interface eth1: Device eth1 does not seem to be present, delaying initialization.
[FAILED]
Starting system logger: [ OK ]
Starting irqbalance: [ OK ]
Starting kdump:[FAILED]
Starting system message bus: [ OK ]
Mounting other filesystems: [ OK ]
Starting acpi daemon: [ OK ]
Starting HAL daemon: [ OK ]
Retrigger failed udev events[ OK ]
Adding udev persistent rules[ OK ]
Starting postfix: [ OK ]
Starting abrt daemon: [ OK ]
[ OK ] crond: [ OK ]
[ OK ] atd: [ OK ]

Red Hat Enterprise Linux Server release 6.0 (Santiago)
Kernel 2.6.32-71.el6.x86_64 on an x86_64

nova-rhel login: type=1305 audit(1301210003.655:9042): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
readahead-collector: sorting
readahead-collector: finished

Thanks ahead for anyone helping

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Andrey Brindeyev
Solved:
Last query:
Last reply:
Revision history for this message
Best Andrey Brindeyev (abrindeyev) said : 		#1

We have a problem with dnsmasq in that build. Please use injection of network settings as temporary workaround.
We'll update our blog once that problem will be resolved. You can find it at http://openstackgd.wordpress.com/

Revision history for this message
Liang (anzadragon) said : 		#2

Thanks Andrey Brindeyev, that solved my question.

Revision history for this message
Liang (anzadragon) said : 		#3

Hi, Andrey,

Thanks for your pointer, my openstack nova is working in RedHat Enterprise 6
environment.
I'd like to find out where I can find instruction on installing openstack
dashboard to RedHat Enterprise 6, do you have information about such?
I'll check the blog to watch the new release of dnsmasq issue.

Thank you again for your great help.

Wang

On Mon, Mar 28, 2011 at 10:17 PM, Andrey Brindeyev <
<email address hidden>> wrote:

> Your question #150776 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/150776
>
> Status: Open => Answered
>
> Andrey Brindeyev proposed the following answer:
> We have a problem with dnsmasq in that build. Please use injection of
> network settings as temporary workaround.
> We'll update our blog once that problem will be resolved. You can find it
> at http://openstackgd.wordpress.com/
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/nova/+question/150776/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/nova/+question/150776
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
amy lee (amylee) said : 		#4

sorry, what does that mean "injection of network settings"?

Revision history for this message
Andrey Brindeyev (abrindeyev) said : 		#5

amy,

That means during an instance firing up host system mount instance's file system and put networking data (IP address, network mask, gateway's IP and DNS server IP) into some file (/etc/sysconfig/network-scripts/ifcfg-eth0 for Fedora and Fedora-based distros).

Revision history for this message
Liang (anzadragon) said : 		#6

Hi,
Few questions after I got nova running in my RHEL6 environment:
1. With the above settings, when I run instance, it only allow me to run 10 instances, after that, it gives me an error:
"euca-run-instances ami-zhgo1eyb -t m1.small
InstanceLimitExceeded: InstanceLimitExceeded: Instance quota exceeded. You can only run 0 more instances of this type."
With the --network-size=32 in nova.conf, I thought I can run instances for up to 30, I think I get this wrong.
2. I can tell the image type have following: m1.tiny, m1.small, m1.medium, m1.large. maybe more, can someone point me to where I can find out how many types are available?
3. after the computers restarted, I lose all the running instances, even though I can find them in mysql db and /var/lib/nova/instances, but I can't no longer show them in euca-describe-instance command even I use virsh to manually start them.

Thanks in advance for any help.

Revision history for this message
Vish Ishaya (vishvananda) said : 		#7

On Apr 13, 2011, at 8:47 AM, Liang wrote:

> Question #150776 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/150776
>
> Liang posted a new comment:
> Hi,
> Few questions after I got nova running in my RHEL6 environment:
> 1. With the above settings, when I run instance, it only allow me to run 10 instances, after that, it gives me an error:
> "euca-run-instances ami-zhgo1eyb -t m1.small
> InstanceLimitExceeded: InstanceLimitExceeded: Instance quota exceeded. You can only run 0 more instances of this type."

try nova-manage project quota

> With the --network-size=32 in nova.conf, I thought I can run instances for up to 30, I think I get this wrong.
> 2. I can tell the image type have following: m1.tiny, m1.small, m1.medium, m1.large. maybe more, can someone point me to where I can find out how many types are available?

nova-manage instance_type list

> 3. after the computers restarted, I lose all the running instances, even though I can find them in mysql db and /var/lib/nova/instances, but I can't no longer show them in euca-describe-instance command even I use virsh to manually start them.

This shouldn't be happening with current trunk. Perhaps the rh packages are a little behind.

>
> Thanks in advance for any help.
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Revision history for this message
Liang (anzadragon) said : 		#8

Thank you very much, Vish.

On Wed, Apr 13, 2011 at 9:27 AM, Vish Ishaya <
<email address hidden>> wrote:

> Your question #150776 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/150776
>
> Vish Ishaya posted a new comment:
>
> On Apr 13, 2011, at 8:47 AM, Liang wrote:
>
> > Question #150776 on OpenStack Compute (nova) changed:
> > https://answers.launchpad.net/nova/+question/150776
> >
> > Liang posted a new comment:
> > Hi,
> > Few questions after I got nova running in my RHEL6 environment:
> > 1. With the above settings, when I run instance, it only allow me to run
> 10 instances, after that, it gives me an error:
> > "euca-run-instances ami-zhgo1eyb -t m1.small
> > InstanceLimitExceeded: InstanceLimitExceeded: Instance quota exceeded.
> You can only run 0 more instances of this type."
>
> try nova-manage project quota
>
> This command shows:
nova-manage project quota tcs-nova
gigabytes: 1000
instances: 10
floating_ips: 10
volumes: 10
cores: 20

And when I tried to set (to increase) instances counts, it just hang, maybe
my syntax is wrong, but I can find any help doc on it
nova-manage project quota tcs-nova instances 20 <--- just hang

> > With the --network-size=32 in nova.conf, I thought I can run instances
> for up to 30, I think I get this wrong.
> > 2. I can tell the image type have following: m1.tiny, m1.small,
> m1.medium, m1.large. maybe more, can someone point me to where I can find
> out how many types are available?
>
> nova-manage instance_type list
>
> This command won't work, nova-manage does not have instance_type option in
my setup

> > 3. after the computers restarted, I lose all the running instances,
> even though I can find them in mysql db and /var/lib/nova/instances, but
> I can't no longer show them in euca-describe-instance command even I use
> virsh to manually start them.
>
> This shouldn't be happening with current trunk. Perhaps the rh packages
> are a little behind.
>
> I'll look into get the newer trunk when I get more understand on my current
setup.

> >
> > Thanks in advance for any help.
> >
> > --
> > You received this question notification because you are a member of Nova
> > Core, which is an answer contact for OpenStack Compute (nova).
>
> You received this question notification because you are a direct
> subscriber of the question.
>