Jyu's profile - activity

Hi,

I have few configured VM on openstack and work normally(maybe it's icehouse version.I downloaded it from GIT yesterday).I find that If I delete the VM all,there will be residual ovs-port information on my network node.If I don't manually use neutron-ovs-clear to delete these ovs information,fixed-ip and floating-ip on the new created VM will lose efficacy.Other services on controller node(neutron-server) and compute node(neutron-openvswitch) works well.Is there anyone could tell me why this kind of information always occur and how could I avoid this situation happened again?Any comments would be appreciated.Thx a lot.

This is the outputs on my network node:

[root@cnt9-network ~(keystone_admin)]# nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+

[root@cnt9-network ~(keystone_admin)]# ovs-vsctl show
9e860eb3-e027-41d1-bf71-1e1959acedef
    Bridge br-ex
        Port "tapaacc7109-0d"
            Interface "tapaacc7109-0d"
        Port "eth0"
            Interface "eth0"
        Port br-ex
            Interface br-ex
                type: internal
        Port phy-br-ex
            Interface phy-br-ex
    Bridge br-int
        Port "tap86352e3d-7c"
            tag: 1
            Interface "tap86352e3d-7c"
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-eth1"
            Interface "int-br-eth1"
        Port int-br-ex
            Interface int-br-ex
        Port "tapade8d0d8-00"
            tag: 1
            Interface "tapade8d0d8-00"
                type: internal
    Bridge "br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
        Port "eth2"
            Interface "eth2"
    ovs_version: "1.11.0"
[root@cnt9-network ~]# ./status.sh
neutron-dhcp-agent (pid  19491) is running...
neutron-l3-agent (pid  13865) is running...
neutron-lbaas-agent dead but pid file exists
neutron-metadata-agent is stopped
neutron-openvswitch-agent (pid  13913) is running...
neutron dead but pid file exists

Hi,

I deploy openstack with source code by pip install.

I notice that if I've configured neutron and boot a VM with fixed IP,then update the openstack pip package,the fixed IP I've assigned to VM wouldn't be accessed.If I clean and recreate net,subnet and router configurations,the new VM could be accessed again.I want to know this is a regular result or not.Is there anyway I can keep all of my configuration after update all component?

This is my updated operation:

First,uninstall all openstack pip package and keep the configure files(including mysql backend and all related file in /etc/XX,/var/lib/XXX,var/run/XXX,/usr/share/XXX,),then download newly packages and make pip-install.
Any comment would be appreciated.Thanks a lot.

Thanks,the problem is caused by my yum repo.I've fixed it.

Hi, I use packstack to deploy openstack on multi-node (RHEL6.4) and get stuck at selinux-installation step. The outputs shows: Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-selinux' returned 1: Error: Package: openstack-selinux-0.1.3-2.el6ost.noarch (openstack-havana)

Then I find this error after I manually execute command "yum -y install openstack-selinux".It looks like there's no "policycoreutils-python" package in RDO repo : Error: Package: openstack-selinux-0.1.3-2.el6ost.noarch (openstack-havana) Requires: policycoreutils-python You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodiges

Did anyone have a solution?Any comments would be appreciated.Thanks a lot!

Thanks a lot!The problem is solved.

I update packstack and rdo repo today and I find below error when begin to do packstack deploy.So my question is:Is there some packages missing in RDO repo?~

Error: Package: openstack-selinux-0.1.3-2.el6ost.noarch (openstack-havana) Requires: selinux-policy-base >= 3.7.19-231.el6 Installed: selinux-policy-targeted-3.7.19-216.el6.noarch (@openstack-havana) selinux-policy-base = 3.7.19-216.el6 Available: selinux-policy-minimum-3.7.19-216.el6.noarch (openstack-havana) selinux-policy-base = 3.7.19-216.el6 Available: selinux-policy-mls-3.7.19-216.el6.noarch (openstack-havana) selinux-policy-base = 3.7.19-216.el6

Error: Package: openstack-selinux-0.1.3-2.el6ost.noarch (openstack-havana) Requires: selinux-policy-targeted >= 3.7.19-231.el6 Installed: selinux-policy-targeted-3.7.19-216.el6.noarch (@openstack-havana) selinux-policy-targeted = 3.7.19-216.el6

when I check RDO repo,there are only those packages:

selinux-policy-3.7.19-216.el6.noarch.rpm 19-Sep-2013 13:55 820K
selinux-policy-3.7.19-216.el6.src.rpm 19-Sep-2013 13:55 19M
selinux-policy-doc-3.7.19-216.el6.noarch.rpm 19-Sep-2013 13:55 1.5M
selinux-policy-minimum-3.7.19-216.el6.noarch.rpm 19-Sep-2013 13:55 2.4M
selinux-policy-mls-3.7.19-216.el6.noarch.rpm 19-Sep-2013 13:55 2.3M
selinux-policy-targeted-3.7.19-216.el6.noarch.rpm