subject:"\[openstack\-dev\] \[tricircle\] playing tricircle with devstack under two\-region configuration"

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-03-01 Thread 时鹏飞

Hi, Zhiyuan.

When I rebooted all the nodes. It works!

I set the network device promiscuous type, and it don’t be useful until reboot…

Thank you for suggestions!


Best Regards

Pengfei Shi (时鹏飞)
Shanghai Jiao Tong University
Network & Information Center Room 304

shipengfe...@gmail.com






> On Mar 1, 2016, at 4:11 PM, Vega Cai  wrote:
> 
> Hi, Pengfei,
> 
> I suppose you are using "internal network" in virtual box to connect your 
> virtual machines, and I find a link that seems to related to your problem.
> 
> https://forums.virtualbox.org/viewtopic.php?f=1&t=38037 
> 
> 
> BR
> Zhiyuan
> 
> On 1 March 2016 at 11:14, Vega Cai  > wrote:
> Hi, All,
> 
> Let's move the discussion to #openstack-tricircle in IRC.
> 
> BR
> Zhiyuan
> 
> On 1 March 2016 at 11:07, Yipei Niu  > wrote:
> Hi, all,
> 
> The bug of deploying devstack with two-node configuration is already fixed. 
> According to the official document, I have already installed devstack in two 
> nodes successfully.
> 
> Moreover, I am still trying to play tricircle in two nodes. When installing 
> tricircle to node1, I still encounter the same error as before. The link is 
> http://paste.openstack.org/show/488682/ 
> .
> 
> Best regards,
> Yipei
> 
> On Tue, Mar 1, 2016 at 10:56 AM, joehuang  > wrote:
> Hi, Yipei,
> 
>  
> 
> The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for 
> Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating 
> endpoint in Keystone, devstack will use command like “openstack endpoint 
> create” to access KeyStone, the OS_REGION_NAME should be the region name 
> where the KeyStone located, in two-nodes installation, it should be 
> “RegionOne” for the command itself.
> 
>  
> 
> So it can be fixed by adding one more configurable global variable to 
> separate KeyStone region name and other services(Nova,Cinder,Neutron) region 
> name.
> 
>  
> 
> Best Regards
> 
> Chaoyi Huang ( Joe Huang )
> 
>  
> 
> From: Yipei Niu [mailto:newy...@gmail.com ] 
> Sent: Monday, February 29, 2016 10:02 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Vega Cai; joehuang; 时鹏飞
> Subject: Re: [tricircle] playing tricircle with devstack under two-region 
> configuration
> 
>  
> 
> Hi Pengfei,
> 
>  
> 
> I also encounter the same error when installing devstack on node2. I insert a 
> command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and it works. 
> However, I am not sure whether it is correct. I am trying to verify it. 
> Recently, I try to re-install devstack on node1, but I encounter some errors. 
> The link is http://paste.openstack.org/show/488005/ 
> . Do you have any suggestion about 
> it?
> 
>  
> 
> To Joe and Zhiyuan, could you please give me some advice about how to solve 
> it?
> 
>  
> 
> Best regards,
> 
> Yipei
> 
>  
> 
> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  > wrote:
> 
> Hi Joe and Zhiyuan,
> 
>  
> 
> My VM has recovered. When I re-install devstack in node1, I encounter the 
> following errors.
> 
>  
> 
> The info in stack.sh.log is as follows:
> 
>  
> 
> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
> 
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n 
> /opt/stack/status/stack/n-sch.failure ']'
> 
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More 
> details about the above errors can be found with screen, with 
> ./rejoin-stack.sh'
> 
> 2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:   
> local exitcode=0
> 
> 2016-02-23 11:18:27.239 | [Call Trace]
> 
> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
> 
> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
> 
> 2016-02-23 11:18:27.261 | [ERROR] /home/stack/devstack/functions-common:1626 
> More details about the above errors can be found with screen, with 
> ./rejoin-stack.sh
> 
> 2016-02-23 11:18:28.271 | Error on exit
> 
> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
> 
>  
> 
> The info in n-sch.log is as follows:
> 
>  
> 
> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler --config-file 
> /et ^Mc/nova/nova.conf & echo $! >/opt/stack/status/stack/n-sch.pid; fg || 
> echo "n-sch ^M failed to start" | tee "/opt/stack/status/stack/n-sch.failure"
> 
> [1] 29467
> 
> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
> 
> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m] 
> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from 
> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend 
> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
>

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-03-01 Thread Vega Cai

Hi, Pengfei,

I suppose you are using "internal network" in virtual box to connect your
virtual machines, and I find a link that seems to related to your problem.

https://forums.virtualbox.org/viewtopic.php?f=1&t=38037

BR
Zhiyuan

On 1 March 2016 at 11:14, Vega Cai  wrote:

> Hi, All,
>
> Let's move the discussion to #openstack-tricircle in IRC.
>
> BR
> Zhiyuan
>
> On 1 March 2016 at 11:07, Yipei Niu  wrote:
>
>> Hi, all,
>>
>> The bug of deploying devstack with two-node configuration is already
>> fixed. According to the official document, I have already installed
>> devstack in two nodes successfully.
>>
>> Moreover, I am still trying to play tricircle in two nodes. When
>> installing tricircle to node1, I still encounter the same error as before.
>> The link is http://paste.openstack.org/show/488682/.
>>
>> Best regards,
>> Yipei
>>
>> On Tue, Mar 1, 2016 at 10:56 AM, joehuang  wrote:
>>
>>> Hi, Yipei,
>>>
>>>
>>>
>>> The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for
>>> Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating
>>> endpoint in Keystone, devstack will use command like “openstack endpoint
>>> create” to access KeyStone, the OS_REGION_NAME should be the region name
>>> where the KeyStone located, in two-nodes installation, it should be
>>> “RegionOne” for the command itself.
>>>
>>>
>>>
>>> So it can be fixed by adding one more configurable global variable to
>>> separate KeyStone region name and other services(Nova,Cinder,Neutron)
>>> region name.
>>>
>>>
>>>
>>> Best Regards
>>>
>>> Chaoyi Huang ( Joe Huang )
>>>
>>>
>>>
>>> *From:* Yipei Niu [mailto:newy...@gmail.com]
>>> *Sent:* Monday, February 29, 2016 10:02 AM
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Cc:* Vega Cai; joehuang; 时鹏飞
>>> *Subject:* Re: [tricircle] playing tricircle with devstack under
>>> two-region configuration
>>>
>>>
>>>
>>> Hi Pengfei,
>>>
>>>
>>>
>>> I also encounter the same error when installing devstack on node2. I
>>> insert a command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and
>>> it works. However, I am not sure whether it is correct. I am trying to
>>> verify it. Recently, I try to re-install devstack on node1, but I encounter
>>> some errors. The link is http://paste.openstack.org/show/488005/. Do
>>> you have any suggestion about it?
>>>
>>>
>>>
>>> To Joe and Zhiyuan, could you please give me some advice about how to
>>> solve it?
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Yipei
>>>
>>>
>>>
>>> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  wrote:
>>>
>>> Hi Joe and Zhiyuan,
>>>
>>>
>>>
>>> My VM has recovered. When I re-install devstack in node1, I encounter
>>> the following errors.
>>>
>>>
>>>
>>> The info in stack.sh.log is as follows:
>>>
>>>
>>>
>>> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n
>>> /opt/stack/status/stack/n-sch.failure ']'
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
>>> details about the above errors can be found with screen, with
>>> ./rejoin-stack.sh'
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:die:L186:   local exitcode=0
>>>
>>> 2016-02-23 11:18:27.239 | [Call Trace]
>>>
>>> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
>>>
>>> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
>>>
>>> 2016-02-23 11:18:27.261 | [ERROR]
>>> /home/stack/devstack/functions-common:1626 More details about the above
>>> errors can be found with screen, with ./rejoin-stack.sh
>>>
>>> 2016-02-23 11:18:28.271 | Error on exit
>>>
>>> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
>>>
>>>
>>>
>>> The info in n-sch.log is as follows:
>>>
>>>
>>>
>>> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
>>> --config-file /et ^Mc/nova/nova.conf & echo $!
>>> >/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
>>> tee "/opt/stack/status/stack/n-sch.failure"
>>>
>>> [1] 29467
>>>
>>> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
>>>
>>> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
>>> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
>>> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
>>> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
>>>
>>> 2016-02-23 19:13:00.300 ^[[01;33mWARNING
>>> oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
>>> ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
>>> default for backward compatibility. SIGUSR1 will no longer be registered in
>>> a future release, so please use SIGUSR2 to generate reports.^[[00m
>>>
>>> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
>>> ^[[01;35m^[[01;31mValueError: Empty module name
>>>
>>> ^[[00m
>>>
>>> ^[[01;31m2016-02-23

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread Yipei Niu

Hi, all,

I don't know why I clone an old version of devstack, which hasn't been
influenced by the patch. Hence, I install devstack in two nodes
successfully. I think I know how to fix it.

BTW, Zhiyuan's solution to solving the problem in my last mail works. Thank
you for your help.

Best regards,
Yipei

On Tue, Mar 1, 2016 at 11:14 AM, Vega Cai  wrote:

> Hi, All,
>
> Let's move the discussion to #openstack-tricircle in IRC.
>
> BR
> Zhiyuan
>
> On 1 March 2016 at 11:07, Yipei Niu  wrote:
>
>> Hi, all,
>>
>> The bug of deploying devstack with two-node configuration is already
>> fixed. According to the official document, I have already installed
>> devstack in two nodes successfully.
>>
>> Moreover, I am still trying to play tricircle in two nodes. When
>> installing tricircle to node1, I still encounter the same error as before.
>> The link is http://paste.openstack.org/show/488682/.
>>
>> Best regards,
>> Yipei
>>
>> On Tue, Mar 1, 2016 at 10:56 AM, joehuang  wrote:
>>
>>> Hi, Yipei,
>>>
>>>
>>>
>>> The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for
>>> Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating
>>> endpoint in Keystone, devstack will use command like “openstack endpoint
>>> create” to access KeyStone, the OS_REGION_NAME should be the region name
>>> where the KeyStone located, in two-nodes installation, it should be
>>> “RegionOne” for the command itself.
>>>
>>>
>>>
>>> So it can be fixed by adding one more configurable global variable to
>>> separate KeyStone region name and other services(Nova,Cinder,Neutron)
>>> region name.
>>>
>>>
>>>
>>> Best Regards
>>>
>>> Chaoyi Huang ( Joe Huang )
>>>
>>>
>>>
>>> *From:* Yipei Niu [mailto:newy...@gmail.com]
>>> *Sent:* Monday, February 29, 2016 10:02 AM
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Cc:* Vega Cai; joehuang; 时鹏飞
>>> *Subject:* Re: [tricircle] playing tricircle with devstack under
>>> two-region configuration
>>>
>>>
>>>
>>> Hi Pengfei,
>>>
>>>
>>>
>>> I also encounter the same error when installing devstack on node2. I
>>> insert a command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and
>>> it works. However, I am not sure whether it is correct. I am trying to
>>> verify it. Recently, I try to re-install devstack on node1, but I encounter
>>> some errors. The link is http://paste.openstack.org/show/488005/. Do
>>> you have any suggestion about it?
>>>
>>>
>>>
>>> To Joe and Zhiyuan, could you please give me some advice about how to
>>> solve it?
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Yipei
>>>
>>>
>>>
>>> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  wrote:
>>>
>>> Hi Joe and Zhiyuan,
>>>
>>>
>>>
>>> My VM has recovered. When I re-install devstack in node1, I encounter
>>> the following errors.
>>>
>>>
>>>
>>> The info in stack.sh.log is as follows:
>>>
>>>
>>>
>>> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n
>>> /opt/stack/status/stack/n-sch.failure ']'
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
>>> details about the above errors can be found with screen, with
>>> ./rejoin-stack.sh'
>>>
>>> 2016-02-23 11:18:27.238 | +
>>> /home/stack/devstack/functions-common:die:L186:   local exitcode=0
>>>
>>> 2016-02-23 11:18:27.239 | [Call Trace]
>>>
>>> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
>>>
>>> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
>>>
>>> 2016-02-23 11:18:27.261 | [ERROR]
>>> /home/stack/devstack/functions-common:1626 More details about the above
>>> errors can be found with screen, with ./rejoin-stack.sh
>>>
>>> 2016-02-23 11:18:28.271 | Error on exit
>>>
>>> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
>>>
>>>
>>>
>>> The info in n-sch.log is as follows:
>>>
>>>
>>>
>>> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
>>> --config-file /et ^Mc/nova/nova.conf & echo $!
>>> >/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
>>> tee "/opt/stack/status/stack/n-sch.failure"
>>>
>>> [1] 29467
>>>
>>> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
>>>
>>> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
>>> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
>>> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
>>> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
>>>
>>> 2016-02-23 19:13:00.300 ^[[01;33mWARNING
>>> oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
>>> ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
>>> default for backward compatibility. SIGUSR1 will no longer be registered in
>>> a future release, so please use SIGUSR2 to generate reports.^[[00m
>>>
>>> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
>>> ^[[01;35m

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread Vega Cai

Hi, All,

Let's move the discussion to #openstack-tricircle in IRC.

BR
Zhiyuan

On 1 March 2016 at 11:07, Yipei Niu  wrote:

> Hi, all,
>
> The bug of deploying devstack with two-node configuration is already
> fixed. According to the official document, I have already installed
> devstack in two nodes successfully.
>
> Moreover, I am still trying to play tricircle in two nodes. When
> installing tricircle to node1, I still encounter the same error as before.
> The link is http://paste.openstack.org/show/488682/.
>
> Best regards,
> Yipei
>
> On Tue, Mar 1, 2016 at 10:56 AM, joehuang  wrote:
>
>> Hi, Yipei,
>>
>>
>>
>> The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for
>> Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating
>> endpoint in Keystone, devstack will use command like “openstack endpoint
>> create” to access KeyStone, the OS_REGION_NAME should be the region name
>> where the KeyStone located, in two-nodes installation, it should be
>> “RegionOne” for the command itself.
>>
>>
>>
>> So it can be fixed by adding one more configurable global variable to
>> separate KeyStone region name and other services(Nova,Cinder,Neutron)
>> region name.
>>
>>
>>
>> Best Regards
>>
>> Chaoyi Huang ( Joe Huang )
>>
>>
>>
>> *From:* Yipei Niu [mailto:newy...@gmail.com]
>> *Sent:* Monday, February 29, 2016 10:02 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Cc:* Vega Cai; joehuang; 时鹏飞
>> *Subject:* Re: [tricircle] playing tricircle with devstack under
>> two-region configuration
>>
>>
>>
>> Hi Pengfei,
>>
>>
>>
>> I also encounter the same error when installing devstack on node2. I
>> insert a command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and
>> it works. However, I am not sure whether it is correct. I am trying to
>> verify it. Recently, I try to re-install devstack on node1, but I encounter
>> some errors. The link is http://paste.openstack.org/show/488005/. Do you
>> have any suggestion about it?
>>
>>
>>
>> To Joe and Zhiyuan, could you please give me some advice about how to
>> solve it?
>>
>>
>>
>> Best regards,
>>
>> Yipei
>>
>>
>>
>> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  wrote:
>>
>> Hi Joe and Zhiyuan,
>>
>>
>>
>> My VM has recovered. When I re-install devstack in node1, I encounter the
>> following errors.
>>
>>
>>
>> The info in stack.sh.log is as follows:
>>
>>
>>
>> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
>>
>> 2016-02-23 11:18:27.238 | +
>> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n
>> /opt/stack/status/stack/n-sch.failure ']'
>>
>> 2016-02-23 11:18:27.238 | +
>> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
>> details about the above errors can be found with screen, with
>> ./rejoin-stack.sh'
>>
>> 2016-02-23 11:18:27.238 | +
>> /home/stack/devstack/functions-common:die:L186:   local exitcode=0
>>
>> 2016-02-23 11:18:27.239 | [Call Trace]
>>
>> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
>>
>> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
>>
>> 2016-02-23 11:18:27.261 | [ERROR]
>> /home/stack/devstack/functions-common:1626 More details about the above
>> errors can be found with screen, with ./rejoin-stack.sh
>>
>> 2016-02-23 11:18:28.271 | Error on exit
>>
>> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
>>
>>
>>
>> The info in n-sch.log is as follows:
>>
>>
>>
>> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
>> --config-file /et ^Mc/nova/nova.conf & echo $!
>> >/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
>> tee "/opt/stack/status/stack/n-sch.failure"
>>
>> [1] 29467
>>
>> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
>>
>> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
>> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
>> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
>> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
>>
>> 2016-02-23 19:13:00.300 ^[[01;33mWARNING
>> oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
>> ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
>> default for backward compatibility. SIGUSR1 will no longer be registered in
>> a future release, so please use SIGUSR2 to generate reports.^[[00m
>>
>> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
>> ^[[01;35m^[[01;31mValueError: Empty module name
>>
>> ^[[00m
>>
>> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback
>> (most recent call last):
>>
>> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
>> "/usr/local/bin/nova-scheduler", line 10, in 
>>
>> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>>  sys.exit(main())
>>
>> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
>> "/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
>>
>> ^[[01;31m2016-

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread Yipei Niu

Hi, all,

The bug of deploying devstack with two-node configuration is already fixed.
According to the official document, I have already installed devstack in
two nodes successfully.

Moreover, I am still trying to play tricircle in two nodes. When installing
tricircle to node1, I still encounter the same error as before. The link is
http://paste.openstack.org/show/488682/.

Best regards,
Yipei

On Tue, Mar 1, 2016 at 10:56 AM, joehuang  wrote:

> Hi, Yipei,
>
>
>
> The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for
> Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating
> endpoint in Keystone, devstack will use command like “openstack endpoint
> create” to access KeyStone, the OS_REGION_NAME should be the region name
> where the KeyStone located, in two-nodes installation, it should be
> “RegionOne” for the command itself.
>
>
>
> So it can be fixed by adding one more configurable global variable to
> separate KeyStone region name and other services(Nova,Cinder,Neutron)
> region name.
>
>
>
> Best Regards
>
> Chaoyi Huang ( Joe Huang )
>
>
>
> *From:* Yipei Niu [mailto:newy...@gmail.com]
> *Sent:* Monday, February 29, 2016 10:02 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Cc:* Vega Cai; joehuang; 时鹏飞
> *Subject:* Re: [tricircle] playing tricircle with devstack under
> two-region configuration
>
>
>
> Hi Pengfei,
>
>
>
> I also encounter the same error when installing devstack on node2. I
> insert a command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and
> it works. However, I am not sure whether it is correct. I am trying to
> verify it. Recently, I try to re-install devstack on node1, but I encounter
> some errors. The link is http://paste.openstack.org/show/488005/. Do you
> have any suggestion about it?
>
>
>
> To Joe and Zhiyuan, could you please give me some advice about how to
> solve it?
>
>
>
> Best regards,
>
> Yipei
>
>
>
> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  wrote:
>
> Hi Joe and Zhiyuan,
>
>
>
> My VM has recovered. When I re-install devstack in node1, I encounter the
> following errors.
>
>
>
> The info in stack.sh.log is as follows:
>
>
>
> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
>
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n
> /opt/stack/status/stack/n-sch.failure ']'
>
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
> details about the above errors can be found with screen, with
> ./rejoin-stack.sh'
>
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:die:L186:   local exitcode=0
>
> 2016-02-23 11:18:27.239 | [Call Trace]
>
> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
>
> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
>
> 2016-02-23 11:18:27.261 | [ERROR]
> /home/stack/devstack/functions-common:1626 More details about the above
> errors can be found with screen, with ./rejoin-stack.sh
>
> 2016-02-23 11:18:28.271 | Error on exit
>
> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
>
>
>
> The info in n-sch.log is as follows:
>
>
>
> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
> --config-file /et ^Mc/nova/nova.conf & echo $!
> >/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
> tee "/opt/stack/status/stack/n-sch.failure"
>
> [1] 29467
>
> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
>
> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
>
> 2016-02-23 19:13:00.300 ^[[01;33mWARNING
> oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
> ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
> default for backward compatibility. SIGUSR1 will no longer be registered in
> a future release, so please use SIGUSR2 to generate reports.^[[00m
>
> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
> ^[[01;35m^[[01;31mValueError: Empty module name
>
> ^[[00m
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most
> recent call last):
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/usr/local/bin/nova-scheduler", line 10, in 
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  sys.exit(main())
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  topic=CONF.scheduler_topic)
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/service.py", line 281, in create
>
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  db_allowed=db_allowed)
>

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread joehuang

Hi, Yipei,

The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for 
Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating 
endpoint in Keystone, devstack will use command like “openstack endpoint 
create” to access KeyStone, the OS_REGION_NAME should be the region name where 
the KeyStone located, in two-nodes installation, it should be “RegionOne” for 
the command itself.

So it can be fixed by adding one more configurable global variable to separate 
KeyStone region name and other services(Nova,Cinder,Neutron) region name.

Best Regards
Chaoyi Huang ( Joe Huang )

From: Yipei Niu [mailto:newy...@gmail.com]
Sent: Monday, February 29, 2016 10:02 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Vega Cai; joehuang; 时鹏飞
Subject: Re: [tricircle] playing tricircle with devstack under two-region 
configuration

Hi Pengfei,

I also encounter the same error when installing devstack on node2. I insert a 
command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and it works. 
However, I am not sure whether it is correct. I am trying to verify it. 
Recently, I try to re-install devstack on node1, but I encounter some errors. 
The link is http://paste.openstack.org/show/488005/. Do you have any suggestion 
about it?

To Joe and Zhiyuan, could you please give me some advice about how to solve it?

Best regards,
Yipei

On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu 
mailto:newy...@gmail.com>> wrote:
Hi Joe and Zhiyuan,

My VM has recovered. When I re-install devstack in node1, I encounter the 
following errors.

The info in stack.sh.log is as follows:

2016-02-23 11:18:27.238 | Error: Service n-sch is not running
2016-02-23 11:18:27.238 | + 
/home/stack/devstack/functions-common:service_check:L1625:   '[' -n 
/opt/stack/status/stack/n-sch.failure ']'
2016-02-23 11:18:27.238 | + 
/home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More 
details about the above errors can be found with screen, with ./rejoin-stack.sh'
2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:   
local exitcode=0
2016-02-23 11:18:27.239 | [Call Trace]
2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
2016-02-23 11:18:27.261 | [ERROR] /home/stack/devstack/functions-common:1626 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
2016-02-23 11:18:28.271 | Error on exit
2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied

The info in n-sch.log is as follows:

stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler --config-file 
/et ^Mc/nova/nova.conf & echo $! >/opt/stack/status/stack/n-sch.pid; fg || echo 
"n-sch ^M failed to start" | tee "/opt/stack/status/stack/n-sch.failure"
[1] 29467
/usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m] 
^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from 
'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
2016-02-23 19:13:00.300 ^[[01;33mWARNING oslo_reports.guru_meditation_report 
[^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 
and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be 
registered in a future release, so please use SIGUSR2 to generate reports.^[[00m
2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m] 
^[[01;35m^[[01;31mValueError: Empty module name
^[[00m
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most 
recent call last):
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/usr/local/bin/nova-scheduler", line 10, in 
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00msys.exit(main())
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
topic=CONF.scheduler_topic)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/opt/stack/nova/nova/service.py", line 281, in create
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
db_allowed=db_allowed)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/opt/stack/nova/nova/service.py", line 167, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.manager = 
manager_class(host=self.host, *args, **kwargs)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/opt/stack/nova/nova/scheduler/manager.py", line 49, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.driver = 
importutils.import_object(scheduler_driver)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
^[[01;31m2016-02-

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread Vega Cai

>> | 38066909-c315-41d0-a83e-11aebab1c51d | net2
>>   | aeb34101-0e0f-402c-94a4-e4d45235d531 10.0.2.0/24|
>> | acb5039a-c076-49ff-9db6-3879630dc531 | net1
>>   | 6a1cafcd-6bc7-4788-8a38-b26616dd43a4 10.0.1.0/24|
>> | afd0ea21-8e0e-4951-97bb-296c18e2ed6a |
>> ns_bridge_net_f55068b6dcfd4b4d9d357b46eedc6644 |
>> a241e73f-8ae6-4a9f-9e03-445f70a11629 100.128.0.0/24 |
>>
>> +--++-+
>>
>>
>> stack@node1:~$ neutron port-list
>>
>> +--+--+---+--+
>> | id   | name
>> | mac_address   | fixed_ips
>> |
>>
>> +--+--+---+--+
>> | 5ff4f7c4-5e47-4cc5-8a17-e011938bd930 |
>> 5ff4f7c4-5e47-4cc5-8a17-e011938bd930 | fa:16:3e:d0:1e:8e | {"subnet_id":
>> "aeb34101-0e0f-402c-94a4-e4d45235d531",|
>> |  |
>> |   | "ip_address": "10.0.2.3"}
>> |
>> | 4f2fb455-8cc5-43ea-87cd-4d4d845548a0 |
>> 4f2fb455-8cc5-43ea-87cd-4d4d845548a0 | fa:16:3e:ed:d2:49 | {"subnet_id":
>> "aeb34101-0e0f-402c-94a4-e4d45235d531",|
>> |  |
>> |   | "ip_address": "10.0.2.1"}
>> |
>> | 67e16de6-ad02-4e5f-b035-6525a5a6dcc4 |
>> | fa:16:3e:c6:07:65 | {"subnet_id":
>> "aeb34101-0e0f-402c-94a4-e4d45235d531",|
>> |  |
>> |   | "ip_address": "10.0.2.2"}
>> |
>> | 15cc5862-443f-44a0-a060-33a66b0686cc |
>> 15cc5862-443f-44a0-a060-33a66b0686cc | fa:16:3e:b9:2c:14 | {"subnet_id":
>> "34405fae-e796-48ae-a6e7-f7943b84a117",|
>> |  |
>> |   | "ip_address": "100.0.0.3"}
>> |
>> | 5367f76e-6a00-478d-b9b8-54d0b4754da7 |
>> 5367f76e-6a00-478d-b9b8-54d0b4754da7 | fa:16:3e:01:70:36 | {"subnet_id":
>> "34405fae-e796-48ae-a6e7-f7943b84a117",|
>> |  |
>> |   | "ip_address": "100.0.0.2"}
>> |
>> | 1be92584-a800-474f-a105-877e8a30875f |
>> 1be92584-a800-474f-a105-877e8a30875f | fa:16:3e:5d:0d:59 | {"subnet_id":
>> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
>> |  |
>> |   | "ip_address": "10.0.1.3"}
>> |
>> | fda27c48-ce7c-4852-b9f6-4af7da2d0b3d |
>> fda27c48-ce7c-4852-b9f6-4af7da2d0b3d | fa:16:3e:26:f3:40 | {"subnet_id":
>> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
>> |  |
>>     |       | "ip_address": "10.0.1.1"}
>> |
>> | 7b51933e-edb4-4210-9df4-e346fe99fded |
>> | fa:16:3e:8f:d7:ad | {"subnet_id":
>> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
>> |  |
>> |   | "ip_address": "10.0.1.2"}
>> |
>> | 4b5a8392-abfc-4261-b98f-e39e377991a7 |
>> | fa:16:3e:ae:bc:4d | "> |
>> |  |
>> |   | 7f9d252aad90]
>> {port_id=u'4b5a8392-abfc-4261-b98f-|
>> |  |
>> |   | e39e377991a7', ip_address=u'10.50.11.30',
>> |
>> |  |
>> |   |
>> subnet_id=u'b50d19d5-435e-4c46-a8fc-cdfc02fbdd29',   |
>> |  |
>> |   |
>> network_id=u'e268445b-398f-40c0-ba03-6ebcc33a64a7'}>"|
>> | aee04b98-4dfb-431a-8b8f-50c1f6a67fc6 |
>> | fa:16:3e:3e:d8:ac | "> |
>> |  |
>> |   | 7f9d2174a710]
>> {port_id=u'aee04b98-4dfb-431a-8b8f-|
>> |  |
>>

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-29 Thread Vega Cai

;aeb34101-0e0f-402c-94a4-e4d45235d531",|
> |  |
> |   | "ip_address": "10.0.2.3"}
> |
> | 4f2fb455-8cc5-43ea-87cd-4d4d845548a0 |
> 4f2fb455-8cc5-43ea-87cd-4d4d845548a0 | fa:16:3e:ed:d2:49 | {"subnet_id":
> "aeb34101-0e0f-402c-94a4-e4d45235d531",|
> |  |
> |   | "ip_address": "10.0.2.1"}
> |
> | 67e16de6-ad02-4e5f-b035-6525a5a6dcc4 |
> | fa:16:3e:c6:07:65 | {"subnet_id":
> "aeb34101-0e0f-402c-94a4-e4d45235d531",|
> |  |
> |   | "ip_address": "10.0.2.2"}
> |
> | 15cc5862-443f-44a0-a060-33a66b0686cc |
> 15cc5862-443f-44a0-a060-33a66b0686cc | fa:16:3e:b9:2c:14 | {"subnet_id":
> "34405fae-e796-48ae-a6e7-f7943b84a117",|
> |  |
> |   | "ip_address": "100.0.0.3"}
> |
> | 5367f76e-6a00-478d-b9b8-54d0b4754da7 |
> 5367f76e-6a00-478d-b9b8-54d0b4754da7 | fa:16:3e:01:70:36 | {"subnet_id":
> "34405fae-e796-48ae-a6e7-f7943b84a117",|
> |  |
> |   | "ip_address": "100.0.0.2"}
> |
> | 1be92584-a800-474f-a105-877e8a30875f |
> 1be92584-a800-474f-a105-877e8a30875f | fa:16:3e:5d:0d:59 | {"subnet_id":
> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
> |  |
> |   | "ip_address": "10.0.1.3"}
> |
> | fda27c48-ce7c-4852-b9f6-4af7da2d0b3d |
> fda27c48-ce7c-4852-b9f6-4af7da2d0b3d | fa:16:3e:26:f3:40 | {"subnet_id":
> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
> |  |
> |   | "ip_address": "10.0.1.1"}
> |
> | 7b51933e-edb4-4210-9df4-e346fe99fded |
> | fa:16:3e:8f:d7:ad | {"subnet_id":
> "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",|
> |  |
> |   | "ip_address": "10.0.1.2"}
> |
> | 4b5a8392-abfc-4261-b98f-e39e377991a7 |
> | fa:16:3e:ae:bc:4d | " |
> |  |
> |   | 7f9d252aad90]
> {port_id=u'4b5a8392-abfc-4261-b98f-|
> |  |
> |   | e39e377991a7', ip_address=u'10.50.11.30',
>     |
> |              |
> |   |
> subnet_id=u'b50d19d5-435e-4c46-a8fc-cdfc02fbdd29',   |
> |  |
> |   |
> network_id=u'e268445b-398f-40c0-ba03-6ebcc33a64a7'}>"|
> | aee04b98-4dfb-431a-8b8f-50c1f6a67fc6 |
> | fa:16:3e:3e:d8:ac | " |
> |  |
> |   | 7f9d2174a710]
> {port_id=u'aee04b98-4dfb-431a-8b8f-|
> |  |
> |   | 50c1f6a67fc6', ip_address=u'10.50.11.31',
> |
> |  |
> |   |
> subnet_id=u'b50d19d5-435e-4c46-a8fc-cdfc02fbdd29',   |
> |  |
> |   |
> network_id=u'e268445b-398f-40c0-ba03-6ebcc33a64a7'}>"|
>
> +--+--+---+--+
>
>
>
>
> Best Regards
>
> Pengfei Shi (时鹏飞)
> Shanghai Jiao Tong University
> Network & Information Center Room 304
>
> shipengfe...@gmail.com
>
>
>
>
>
>
> On Feb 29, 2016, at 8:36 AM, joehuang  wrote:
>
> Hi, Pengfei,
>
> Volume type is not supported in Tricircle yet.
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
> *From:* 时鹏飞 [mailto:shipengfe...@gmail.com ]
> *Sent:* Sunday, February 28, 2016 9:36 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [tricircle] playing tricircle with
> devstack under two-region configuration
>
> Hi,Joe and Zhiyuan,
>
> When I install the devstack in Node2, it occur errors when test
> cinder_volume_types:
>
> 2016-02-27 17:05:00.920 | + ./devstack/stack.sh:main:L1267:
> create_volume_types
> 2016-02-27 17:05:00.920 | +
> /home/stack/devstack/lib/cinder:crea

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-28 Thread 时鹏飞

-b9b8-54d0b4754da7 | 5367f76e-6a00-478d-b9b8-54d0b4754da7 
> | fa:16:3e:01:70:36 | {"subnet_id": "34405fae-e796-48ae-a6e7-f7943b84a117",   
>  |
> |  |  
> |   | "ip_address": "100.0.0.2"}  
>  |
> | 1be92584-a800-474f-a105-877e8a30875f | 1be92584-a800-474f-a105-877e8a30875f 
> | fa:16:3e:5d:0d:59 | {"subnet_id": "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",   
>  |
> |  |  
> |   | "ip_address": "10.0.1.3"}   
>  |
> | fda27c48-ce7c-4852-b9f6-4af7da2d0b3d | fda27c48-ce7c-4852-b9f6-4af7da2d0b3d 
> | fa:16:3e:26:f3:40 | {"subnet_id": "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",   
>  |
> |  |  
> |   | "ip_address": "10.0.1.1"}   
>  |
> | 7b51933e-edb4-4210-9df4-e346fe99fded |  
> | fa:16:3e:8f:d7:ad | {"subnet_id": "6a1cafcd-6bc7-4788-8a38-b26616dd43a4",   
>  |
> |  |  
> |   | "ip_address": "10.0.1.2"}   
>  |
> | 4b5a8392-abfc-4261-b98f-e39e377991a7 |  
> | fa:16:3e:ae:bc:4d | "  |
> |  |  
> |   | 7f9d252aad90] {port_id=u'4b5a8392-abfc-4261-b98f-   
>  |
> |  |  
> |   | e39e377991a7', ip_address=u'10.50.11.30',   
>  |
> |  |  
> |   | subnet_id=u'b50d19d5-435e-4c46-a8fc-cdfc02fbdd29',  
>  |
> |  |  
> |   | network_id=u'e268445b-398f-40c0-ba03-6ebcc33a64a7'}>"   
>  |
> | aee04b98-4dfb-431a-8b8f-50c1f6a67fc6 |  
> | fa:16:3e:3e:d8:ac | "  |
> |  |  
> |   | 7f9d2174a710] {port_id=u'aee04b98-4dfb-431a-8b8f-   
>  |
> |  |  
> |   | 50c1f6a67fc6', ip_address=u'10.50.11.31',   
>  |
> |          |  
> |   | subnet_id=u'b50d19d5-435e-4c46-a8fc-cdfc02fbdd29',  
>  |
> |  |  
> |   | network_id=u'e268445b-398f-40c0-ba03-6ebcc33a64a7'}>"   
>  |
> +--+--+---+--+
> 
> 
> 
> 
> Best Regards
> 
> Pengfei Shi (时鹏飞)
> Shanghai Jiao Tong University
> Network & Information Center Room 304
> 
> shipengfe...@gmail.com <mailto:shipengfe...@gmail.com>
> 
> 
> 
> 
> 
> 
>> On Feb 29, 2016, at 8:36 AM, joehuang > <mailto:joehu...@huawei.com>> wrote:
>> 
>> Hi, Pengfei,
>>  
>> Volume type is not supported in Tricircle yet.
>>  
>> Best Regards
>> Chaoyi Huang ( Joe Huang )
>>  
>> From: 时鹏飞 [mailto:shipengfe...@gmail.com <mailto:shipengfe...@gmail.com>] 
>> Sent: Sunday, February 28, 2016 9:36 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [tricircle] playing tricircle with devstack 
>> under two-region configuration
>>  
>> Hi,Joe and Zhiyuan,
>>  
>> When I install the devstack in Node2, it occur errors when test 
>> cinder_volume_types:
>>  
>> 2016-02-27 17:05:00.920 | + ./devstack/stack.sh:main:L1267:   
>> create_volume_types
>> 2016-02-27 17:05:00.920 | + 
>> /home/stack/devstack/lib/cinder:create_volume_types:L549:   
>> is_service_enabled c-api
>> 2016-02-27 17:05:00.927 | + 
>> /home/stack/devstack/functions-common:is_service_enabled:L2026:   return 0
>> 2016-02-27 17:05:00.927 | + 
>> /home/stack/devstack/lib/cinder:create_volume_types:L549:   [[ -n 
>> lvm:lvmdriver-1 ]]
>> 2016-02-27 17:05:00.927 | + 
>> /home/stack/devstack/lib/cinder:create_volume_types:L550:   local be b

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-28 Thread 时鹏飞

Hi, Yipei

you should 

export OS_REGION_NAME=RegionOne

which is the name of your top openstack region.

Best Regards

Pengfei Shi (时鹏飞)
Shanghai Jiao Tong University
Network & Information Center Room 304

shipengfe...@gmail.com






> On Feb 29, 2016, at 10:02 AM, Yipei Niu  wrote:
> 
> Hi Pengfei,
> 
> I also encounter the same error when installing devstack on node2. I insert a 
> command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and it works. 
> However, I am not sure whether it is correct. I am trying to verify it. 
> Recently, I try to re-install devstack on node1, but I encounter some errors. 
> The link is http://paste.openstack.org/show/488005/ 
> . Do you have any suggestion about 
> it?
> 
> To Joe and Zhiyuan, could you please give me some advice about how to solve 
> it?
> 
> Best regards,
> Yipei
> 
> On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  > wrote:
> Hi Joe and Zhiyuan,
> 
> My VM has recovered. When I re-install devstack in node1, I encounter the 
> following errors.
> 
> The info in stack.sh.log is as follows:
> 
> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n 
> /opt/stack/status/stack/n-sch.failure ']'
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More 
> details about the above errors can be found with screen, with 
> ./rejoin-stack.sh'
> 2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:   
> local exitcode=0
> 2016-02-23 11:18:27.239 | [Call Trace]
> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
> 2016-02-23 11:18:27.261 | [ERROR] /home/stack/devstack/functions-common:1626 
> More details about the above errors can be found with screen, with 
> ./rejoin-stack.sh
> 2016-02-23 11:18:28.271 | Error on exit
> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
> 
> The info in n-sch.log is as follows:
> 
> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler --config-file 
> /et ^Mc/nova/nova.conf & echo $! >/opt/stack/status/stack/n-sch.pid; fg || 
> echo "n-sch ^M failed to start" | tee "/opt/stack/status/stack/n-sch.failure"
> [1] 29467
> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m] 
> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from 
> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend 
> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
> 2016-02-23 19:13:00.300 ^[[01;33mWARNING oslo_reports.guru_meditation_report 
> [^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 
> and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be 
> registered in a future release, so please use SIGUSR2 to generate 
> reports.^[[00m
> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m] 
> ^[[01;35m^[[01;31mValueError: Empty module name
> ^[[00m
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most 
> recent call last):
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/usr/local/bin/nova-scheduler", line 10, in 
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
> sys.exit(main())
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
> topic=CONF.scheduler_topic)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/opt/stack/nova/nova/service.py", line 281, in create
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
> db_allowed=db_allowed)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/opt/stack/nova/nova/service.py", line 167, in __init__
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.manager = 
> manager_class(host=self.host, *args, **kwargs)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/opt/stack/nova/nova/scheduler/manager.py", line 49, in __init__
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.driver = 
> importutils.import_object(scheduler_driver)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, 
> in import_object
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mreturn 
> import_class(import_str)(*args, **kwargs)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, 
> in import_class
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
> __import__(mod_str)
> ^[[01;31m

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-28 Thread Yipei Niu

Hi Pengfei,

I also encounter the same error when installing devstack on node2. I insert
a command "export OS_REGION_NAME=Pod2" in line 1262 in stack.sh and it
works. However, I am not sure whether it is correct. I am trying to verify
it. Recently, I try to re-install devstack on node1, but I encounter some
errors. The link is http://paste.openstack.org/show/488005/. Do you have
any suggestion about it?

To Joe and Zhiyuan, could you please give me some advice about how to solve
it?

Best regards,
Yipei

On Wed, Feb 24, 2016 at 9:29 AM, Yipei Niu  wrote:

> Hi Joe and Zhiyuan,
>
> My VM has recovered. When I re-install devstack in node1, I encounter the
> following errors.
>
> The info in stack.sh.log is as follows:
>
> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n
> /opt/stack/status/stack/n-sch.failure ']'
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
> details about the above errors can be found with screen, with
> ./rejoin-stack.sh'
> 2016-02-23 11:18:27.238 | +
> /home/stack/devstack/functions-common:die:L186:   local exitcode=0
> 2016-02-23 11:18:27.239 | [Call Trace]
> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
> 2016-02-23 11:18:27.261 | [ERROR]
> /home/stack/devstack/functions-common:1626 More details about the above
> errors can be found with screen, with ./rejoin-stack.sh
> 2016-02-23 11:18:28.271 | Error on exit
> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
>
> The info in n-sch.log is as follows:
>
> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
> --config-file /et ^Mc/nova/nova.conf & echo $!
> >/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
> tee "/opt/stack/status/stack/n-sch.failure"
> [1] 29467
> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
> 2016-02-23 19:13:00.300 ^[[01;33mWARNING
> oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
> ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
> default for backward compatibility. SIGUSR1 will no longer be registered in
> a future release, so please use SIGUSR2 to generate reports.^[[00m
> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
> ^[[01;35m^[[01;31mValueError: Empty module name
> ^[[00m
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most
> recent call last):
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/usr/local/bin/nova-scheduler", line 10, in 
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  sys.exit(main())
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  topic=CONF.scheduler_topic)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/service.py", line 281, in create
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  db_allowed=db_allowed)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/service.py", line 167, in __init__
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  self.manager = manager_class(host=self.host, *args, **kwargs)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/opt/stack/nova/nova/scheduler/manager.py", line 49, in __init__
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.driver
> = importutils.import_object(scheduler_driver)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
> 44, in import_object
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mreturn
> import_class(import_str)(*args, **kwargs)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
> "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
> 30, in import_class
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
>  __import__(mod_str)
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mValueError:
> Empty module name
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
> n-sch failed to start
>
>
> Best regards,
> Yipei
>
> On Tue, Feb 23, 2016 at 10:23 AM, Yipei Niu  wrote:
>
>> Hi Jeo,
>>
>> I have checked. The Neutron API has not started, but no process is
>> listening 9696.
>>
>> Best regards,
>> Yipei
>>
>
>
___

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-28 Thread joehuang

Hi, Pengfei,

Volume type is not supported in Tricircle yet.

Best Regards
Chaoyi Huang ( Joe Huang )

From: 时鹏飞 [mailto:shipengfe...@gmail.com]
Sent: Sunday, February 28, 2016 9:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] playing tricircle with devstack under 
two-region configuration

Hi,Joe and Zhiyuan,

When I install the devstack in Node2, it occur errors when test 
cinder_volume_types:

2016-02-27 17:05:00.920 | + ./devstack/stack.sh:main:L1267:   
create_volume_types
2016-02-27 17:05:00.920 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L549:   is_service_enabled 
c-api
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/functions-common:is_service_enabled:L2026:   return 0
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L549:   [[ -n 
lvm:lvmdriver-1 ]]
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L550:   local be be_name
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L551:   for be in 
'${CINDER_ENABLED_BACKENDS//,/ }'
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L552:   be_name=lvmdriver-1
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L553:   openstack volume 
type create --property volume_backend_name=lvmdriver-1 lvmdriver-1
2016-02-27 17:05:02.937 | Unable to establish connection to 
http://10.50.11.5:19997/v2/00d182cbe7664762809f4f5a0866635d/types
2016-02-27 17:05:03.025 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L1:   exit_trap
2016-02-27 17:05:03.025 | + ./devstack/stack.sh:exit_trap:L474:   local r=1
2016-02-27 17:05:03.027 | ++ ./devstack/stack.sh:exit_trap:L475:   jobs -p
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L475:   jobs=
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L478:   [[ -n '' ]]
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L484:   kill_spinner
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:kill_spinner:L370:   '[' '!' -z 
'' ']'
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L486:   [[ 1 -ne 0 ]]
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L487:   echo 'Error 
on exit'
2016-02-27 17:05:03.029 | Error on exit
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L488:   
generate-subunit 1456592181 522 fail
2016-02-27 17:05:03.375 | + ./devstack/stack.sh:exit_trap:L489:   [[ -z 
/opt/stack/logs ]]
2016-02-27 17:05:03.375 | + ./devstack/stack.sh:exit_trap:L492:   
/home/stack/devstack/tools/worlddump.py -d /opt/stack/logs
stack@node2:~$ 2016-02-27 17:05:03.843 | + ./devstack/stack.sh:exit_trap:L498:  
 exit 1


Best Regards
Pengfei Shi (时鹏飞)
Shanghai Jiao Tong University
Network & Information Center Room 304

shipengfe...@gmail.com<mailto:shipengfe...@gmail.com>





On Feb 24, 2016, at 9:29 AM, Yipei Niu 
mailto:newy...@gmail.com>> wrote:

Hi Joe and Zhiyuan,

My VM has recovered. When I re-install devstack in node1, I encounter the 
following errors.

The info in stack.sh.log is as follows:

2016-02-23 11:18:27.238 | Error: Service n-sch is not running
2016-02-23 11:18:27.238 | + 
/home/stack/devstack/functions-common:service_check:L1625:   '[' -n 
/opt/stack/status/stack/n-sch.failure ']'
2016-02-23 11:18:27.238 | + 
/home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More 
details about the above errors can be found with screen, with ./rejoin-stack.sh'
2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:   
local exitcode=0
2016-02-23 11:18:27.239 | [Call Trace]
2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
2016-02-23 11:18:27.261 | [ERROR] /home/stack/devstack/functions-common:1626 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
2016-02-23 11:18:28.271 | Error on exit
2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied

The info in n-sch.log is as follows:

stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler --config-file 
/et ^Mc/nova/nova.conf & echo $! >/opt/stack/status/stack/n-sch.pid; fg || echo 
"n-sch ^M failed to start" | tee "/opt/stack/status/stack/n-sch.failure"
[1] 29467
/usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m] 
^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from 
'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
2016-02-23 19:13:00.300 ^[[01;33mWARNING oslo_reports.guru_meditation_report 
[^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 
and SIGUSR2 by default for

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-27 Thread 时鹏飞

Hi,Joe and Zhiyuan,

When I install the devstack in Node2, it occur errors when test 
cinder_volume_types:

2016-02-27 17:05:00.920 | + ./devstack/stack.sh:main:L1267:   
create_volume_types
2016-02-27 17:05:00.920 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L549:   is_service_enabled 
c-api
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/functions-common:is_service_enabled:L2026:   return 0
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L549:   [[ -n 
lvm:lvmdriver-1 ]]
2016-02-27 17:05:00.927 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L550:   local be be_name
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L551:   for be in 
'${CINDER_ENABLED_BACKENDS//,/ }'
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L552:   be_name=lvmdriver-1
2016-02-27 17:05:00.928 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L553:   openstack volume 
type create --property volume_backend_name=lvmdriver-1 lvmdriver-1
2016-02-27 17:05:02.937 | Unable to establish connection to 
http://10.50.11.5:19997/v2/00d182cbe7664762809f4f5a0866635d/types
2016-02-27 17:05:03.025 | + 
/home/stack/devstack/lib/cinder:create_volume_types:L1:   exit_trap
2016-02-27 17:05:03.025 | + ./devstack/stack.sh:exit_trap:L474:   local r=1
2016-02-27 17:05:03.027 | ++ ./devstack/stack.sh:exit_trap:L475:   jobs -p
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L475:   jobs=
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L478:   [[ -n '' ]]
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:exit_trap:L484:   kill_spinner
2016-02-27 17:05:03.028 | + ./devstack/stack.sh:kill_spinner:L370:   '[' '!' -z 
'' ']'
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L486:   [[ 1 -ne 0 ]]
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L487:   echo 'Error 
on exit'
2016-02-27 17:05:03.029 | Error on exit
2016-02-27 17:05:03.029 | + ./devstack/stack.sh:exit_trap:L488:   
generate-subunit 1456592181 522 fail
2016-02-27 17:05:03.375 | + ./devstack/stack.sh:exit_trap:L489:   [[ -z 
/opt/stack/logs ]]
2016-02-27 17:05:03.375 | + ./devstack/stack.sh:exit_trap:L492:   
/home/stack/devstack/tools/worlddump.py -d /opt/stack/logs
stack@node2:~$ 2016-02-27 17:05:03.843 | + ./devstack/stack.sh:exit_trap:L498:  
 exit 1


Best Regards

Pengfei Shi (时鹏飞)
Shanghai Jiao Tong University
Network & Information Center Room 304

shipengfe...@gmail.com






> On Feb 24, 2016, at 9:29 AM, Yipei Niu  wrote:
> 
> Hi Joe and Zhiyuan,
> 
> My VM has recovered. When I re-install devstack in node1, I encounter the 
> following errors.
> 
> The info in stack.sh.log is as follows:
> 
> 2016-02-23 11:18:27.238 | Error: Service n-sch is not running
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1625:   '[' -n 
> /opt/stack/status/stack/n-sch.failure ']'
> 2016-02-23 11:18:27.238 | + 
> /home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More 
> details about the above errors can be found with screen, with 
> ./rejoin-stack.sh'
> 2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:   
> local exitcode=0
> 2016-02-23 11:18:27.239 | [Call Trace]
> 2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
> 2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
> 2016-02-23 11:18:27.261 | [ERROR] /home/stack/devstack/functions-common:1626 
> More details about the above errors can be found with screen, with 
> ./rejoin-stack.sh
> 2016-02-23 11:18:28.271 | Error on exit
> 2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
> 
> The info in n-sch.log is as follows:
> 
> stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler --config-file 
> /et ^Mc/nova/nova.conf & echo $! >/opt/stack/status/stack/n-sch.pid; fg || 
> echo "n-sch ^M failed to start" | tee "/opt/stack/status/stack/n-sch.failure"
> [1] 29467
> /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
> 2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m] 
> ^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from 
> 'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend 
> /usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
> 2016-02-23 19:13:00.300 ^[[01;33mWARNING oslo_reports.guru_meditation_report 
> [^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 
> and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be 
> registered in a future release, so please use SIGUSR2 to generate 
> reports.^[[00m
> 2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m] 
> ^[[01;35m^[[01;31mValueError: Empty module name
> ^[[00m
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most 
> recent call last):
> ^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File 
> "/usr/local/bin/nova-scheduler", line 10, in 
> ^[[01;31m2016-0

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-23 Thread Yipei Niu

Hi Joe and Zhiyuan,

My VM has recovered. When I re-install devstack in node1, I encounter the
following errors.

The info in stack.sh.log is as follows:

2016-02-23 11:18:27.238 | Error: Service n-sch is not running
2016-02-23 11:18:27.238 | +
/home/stack/devstack/functions-common:service_check:L1625:   '[' -n
/opt/stack/status/stack/n-sch.failure ']'
2016-02-23 11:18:27.238 | +
/home/stack/devstack/functions-common:service_check:L1626:   die 1626 'More
details about the above errors can be found with screen, with
./rejoin-stack.sh'
2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:
  local exitcode=0
2016-02-23 11:18:27.239 | [Call Trace]
2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
2016-02-23 11:18:27.261 | [ERROR]
/home/stack/devstack/functions-common:1626 More details about the above
errors can be found with screen, with ./rejoin-stack.sh
2016-02-23 11:18:28.271 | Error on exit
2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied

The info in n-sch.log is as follows:

stack@nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
--config-file /et ^Mc/nova/nova.conf & echo $!
>/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
tee "/opt/stack/status/stack/n-sch.failure"
[1] 29467
/usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
2016-02-23 19:13:00.300 ^[[01;33mWARNING
oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
default for backward compatibility. SIGUSR1 will no longer be registered in
a future release, so please use SIGUSR2 to generate reports.^[[00m
2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
^[[01;35m^[[01;31mValueError: Empty module name
^[[00m
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most
recent call last):
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/usr/local/bin/nova-scheduler", line 10, in 
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
 sys.exit(main())
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
 topic=CONF.scheduler_topic)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/opt/stack/nova/nova/service.py", line 281, in create
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
 db_allowed=db_allowed)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/opt/stack/nova/nova/service.py", line 167, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.manager
= manager_class(host=self.host, *args, **kwargs)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/opt/stack/nova/nova/scheduler/manager.py", line 49, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mself.driver
= importutils.import_object(scheduler_driver)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
44, in import_object
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mreturn
import_class(import_str)(*args, **kwargs)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
30, in import_class
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
 __import__(mod_str)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mValueError:
Empty module name
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
n-sch failed to start


Best regards,
Yipei

On Tue, Feb 23, 2016 at 10:23 AM, Yipei Niu  wrote:

> Hi Jeo,
>
> I have checked. The Neutron API has not started, but no process is
> listening 9696.
>
> Best regards,
> Yipei
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-22 Thread Yipei Niu

Hi Jeo,

I have checked. The Neutron API has not started, but no process is
listening 9696.

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-22 Thread joehuang

Hi, Yipei,

You can use “ps aux |grep python” to see processes started for OpenStack, and 
make sure services started successfully. And use “netstat -tulpn | grep :9696” 
to see which process is listening this port. Maybe your Neutron API has not 
started successfully.

Best Regards
Chaoyi Huang ( Joe Huang )

From: Yipei Niu [mailto:newy...@gmail.com]
Sent: Tuesday, February 23, 2016 10:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: joehuang; Vega Cai
Subject: Re: [tricircle] playing tricircle with devstack under two-region 
configuration

Hi Joe and Zhiyuan,

When creating network with AZ scheduler hints specified, I execute "curl -X 
POST http://127.0.0.1:9696/v2.0/networks -H "Content-Type: application/json" -H 
"X-Auth-Token: $token" -d '{"network": {"name": "net1", "admin_state_up": true, 
"availability_zone_hints": ["az1"]}}'". The results also indicate that

Failed to connect to 127.0.0.1 port 9696: Connection refused.

Unlike the error mentioned in last mail, I still cannot find any processor is 
listening on port 9696 after running "rejoin-stack.sh".

Best regards,
Yipei

On Mon, Feb 22, 2016 at 11:45 AM, Vega Cai 
mailto:luckyveg...@gmail.com>> wrote:
Hi Yipei,

One reason for that error is that the API service is down. You can run 
"rejoin-stack.sh" under your DevStack folder to enter the "screen" console of 
DevStack, to check if services are running well. If you are not familiar with 
"screen", which is a window manager for Linux, you can do a brief search.

One more thing you can try, change the IP address to 127.0.0.1 and issue the 
request in the machine hosting the services to see if there is still 
"Connection refused" error.

BR
Zhiyuan

On 20 February 2016 at 20:49, Yipei Niu 
mailto:newy...@gmail.com>> wrote:
Hi Joe and Zhiyuan,

I encounter an error when executing the following command:

stack@nyp-VirtualBox:~/devstack$ curl -X POST 
http://192.168.56.101:1/v1.0/pods -H "Content-Type: application/json" -H 
"X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d '{"pod": {"pod_name":  
"RegionOne"}}'
curl: (7) Failed to connect to 192.168.56.101 port 1: Connection refused

Before executing the command, I source the file "userrc_early", whose content 
is as follows:
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://192.168.56.101:35357
export OS_USERNAME=admin
export OS_USER_DOMAIN_ID=default
export OS_PASSWORD=nypnyp0316
export OS_PROJECT_NAME=admin
export OS_PROJECT_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne

Furthermore, the results of "openstack endpoint list" are as follows:
stack@nyp-VirtualBox:~/devstack$ openstack endpoint list
+--+---+--++-+---++
| ID   | Region| Service Name | Service Type   
| Enabled | Interface | URL|
+--+---+--++-+---++
| 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy  | compute_legacy 
| True| internal  | http://192.168.56.101:8774/v2/$(tenant_id)s|
| 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy  | compute_legacy 
| True| admin | http://192.168.56.101:8774/v2/$(tenant_id)s|
| 11cea2de9407459480a30b190e005a5c | Pod1  | neutron  | network
| True| internal  | http://192.168.56.101:20001/   |
| 16c0d9f251d84af897dfdd8df60f76dd | Pod2  | nova_legacy  | compute_legacy 
| True| admin | http://192.168.56.102:8774/v2/$(tenant_id)s|
| 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2   
| True| public| http://192.168.56.101:19997/v2/$(tenant_id)s   |
| 1a068f85aa12413582c4f4d256d276af | Pod2  | nova | compute
| True| admin | http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
| 1b3799428309490bbce57043e87ac815 | RegionOne | cinder   | volume 
| True| internal  | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 221d74877fdd4c03b9b9b7d752e30473 | Pod2  | neutron  | network
| True| internal  | http://192.168.56.102:9696/|
| 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2  | cinderv2 | volumev2   
| True| public| http://192.168.56.102:8776/v2/$(tenant_id)s|
| 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity   
| True| admin | http://192.168.56.101:35357/v2.0   |
| 45e4ccd5e16a423e8cb9f59742acee27 | Pod1  | neutron  | network
| True| public| http://192.168.56.101:20001/   |
| 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder   | volume 
| True| admin | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 47351cda93a54a2a9379b83c0eb445ca | Pod2  | neutro

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-22 Thread Yipei Niu

Hi Joe and Zhiyuan,

When creating network with AZ scheduler hints specified, I execute "curl -X
POST http://127.0.0.1:9696/v2.0/networks -H "Content-Type:
application/json" -H "X-Auth-Token: $token" -d '{"network": {"name":
"net1", "admin_state_up": true, "availability_zone_hints": ["az1"]}}'". The
results also indicate that

Failed to connect to 127.0.0.1 port 9696: Connection refused.

Unlike the error mentioned in last mail, I still cannot find any processor
is listening on port 9696 after running "rejoin-stack.sh".

Best regards,
Yipei

On Mon, Feb 22, 2016 at 11:45 AM, Vega Cai  wrote:

> Hi Yipei,
>
> One reason for that error is that the API service is down. You can run
> "rejoin-stack.sh" under your DevStack folder to enter the "screen" console
> of DevStack, to check if services are running well. If you are not familiar
> with "screen", which is a window manager for Linux, you can do a brief
> search.
>
> One more thing you can try, change the IP address to 127.0.0.1 and issue
> the request in the machine hosting the services to see if there is still
> "Connection refused" error.
>
> BR
> Zhiyuan
>
> On 20 February 2016 at 20:49, Yipei Niu  wrote:
>
>> Hi Joe and Zhiyuan,
>>
>> I encounter an error when executing the following command:
>>
>> stack@nyp-VirtualBox:~/devstack$ curl -X POST
>> http://192.168.56.101:1/v1.0/pods -H "Content-Type:
>> application/json" -H "X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d
>> '{"pod": {"pod_name":  "RegionOne"}}'
>> curl: (7) Failed to connect to 192.168.56.101 port 1: Connection
>> refused
>>
>> Before executing the command, I source the file "userrc_early", whose
>> content is as follows:
>> export OS_IDENTITY_API_VERSION=3
>> export OS_AUTH_URL=http://192.168.56.101:35357
>> export OS_USERNAME=admin
>> export OS_USER_DOMAIN_ID=default
>> export OS_PASSWORD=nypnyp0316
>> export OS_PROJECT_NAME=admin
>> export OS_PROJECT_DOMAIN_ID=default
>> export OS_REGION_NAME=RegionOne
>>
>> Furthermore, the results of "openstack endpoint list" are as follows:
>> stack@nyp-VirtualBox:~/devstack$ openstack endpoint list
>>
>> +--+---+--++-+---++
>> | ID   | Region| Service Name | Service
>> Type   | Enabled | Interface | URL
>>|
>>
>> +--+---+--++-+---++
>> | 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy  |
>> compute_legacy | True| internal  |
>> http://192.168.56.101:8774/v2/$(tenant_id)s|
>> | 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy  |
>> compute_legacy | True| admin |
>> http://192.168.56.101:8774/v2/$(tenant_id)s|
>> | 11cea2de9407459480a30b190e005a5c | Pod1  | neutron  | network
>>  | True| internal  | http://192.168.56.101:20001/
>> |
>> | 16c0d9f251d84af897dfdd8df60f76dd | Pod2  | nova_legacy  |
>> compute_legacy | True| admin |
>> http://192.168.56.102:8774/v2/$(tenant_id)s|
>> | 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2
>>   | True| public|
>> http://192.168.56.101:19997/v2/$(tenant_id)s   |
>> | 1a068f85aa12413582c4f4d256d276af | Pod2  | nova | compute
>>  | True| admin |
>> http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
>> | 1b3799428309490bbce57043e87ac815 | RegionOne | cinder   | volume
>>   | True| internal  | http://192.168.56.101:8776/v1/$(tenant_id)s
>>|
>> | 221d74877fdd4c03b9b9b7d752e30473 | Pod2  | neutron  | network
>>  | True| internal  | http://192.168.56.102:9696/
>>|
>> | 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2  | cinderv2 | volumev2
>>   | True| public| http://192.168.56.102:8776/v2/$(tenant_id)s
>>|
>> | 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity
>>   | True| admin | http://192.168.56.101:35357/v2.0
>> |
>> | 45e4ccd5e16a423e8cb9f59742acee27 | Pod1  | neutron  | network
>>  | True| public| http://192.168.56.101:20001/
>> |
>> | 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder   | volume
>>   | True| admin | http://192.168.56.101:8776/v1/$(tenant_id)s
>>|
>> | 47351cda93a54a2a9379b83c0eb445ca | Pod2  | neutron  | network
>>  | True| admin | http://192.168.56.102:9696/
>>|
>> | 56d6f7641ee84ee58611621c4657e45d | Pod2  | nova_legacy  |
>> compute_legacy | True| internal  |
>> http://192.168.56.102:8774/v2/$(tenant_id)s|
>> | 57887a9d15164d6cb5b58d9342316cf7 | RegionOne | glance   | image
>>  | True| internal  | http://192.168.56.101:9292
>> |
>> | 5f2a4f69682941edbe54a85c45a5fe1b | Pod1  | cinderv2 | volumev2
>>   | True| public| http://192.168.56.101:8776/v2/$(tenant

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-21 Thread Vega Cai

Hi Yipei,

One reason for that error is that the API service is down. You can run
"rejoin-stack.sh" under your DevStack folder to enter the "screen" console
of DevStack, to check if services are running well. If you are not familiar
with "screen", which is a window manager for Linux, you can do a brief
search.

One more thing you can try, change the IP address to 127.0.0.1 and issue
the request in the machine hosting the services to see if there is still
"Connection refused" error.

BR
Zhiyuan

On 20 February 2016 at 20:49, Yipei Niu  wrote:

> Hi Joe and Zhiyuan,
>
> I encounter an error when executing the following command:
>
> stack@nyp-VirtualBox:~/devstack$ curl -X POST
> http://192.168.56.101:1/v1.0/pods -H "Content-Type: application/json"
> -H "X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d '{"pod":
> {"pod_name":  "RegionOne"}}'
> curl: (7) Failed to connect to 192.168.56.101 port 1: Connection
> refused
>
> Before executing the command, I source the file "userrc_early", whose
> content is as follows:
> export OS_IDENTITY_API_VERSION=3
> export OS_AUTH_URL=http://192.168.56.101:35357
> export OS_USERNAME=admin
> export OS_USER_DOMAIN_ID=default
> export OS_PASSWORD=nypnyp0316
> export OS_PROJECT_NAME=admin
> export OS_PROJECT_DOMAIN_ID=default
> export OS_REGION_NAME=RegionOne
>
> Furthermore, the results of "openstack endpoint list" are as follows:
> stack@nyp-VirtualBox:~/devstack$ openstack endpoint list
>
> +--+---+--++-+---++
> | ID   | Region| Service Name | Service
> Type   | Enabled | Interface | URL
>|
>
> +--+---+--++-+---++
> | 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy  |
> compute_legacy | True| internal  |
> http://192.168.56.101:8774/v2/$(tenant_id)s|
> | 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy  |
> compute_legacy | True| admin |
> http://192.168.56.101:8774/v2/$(tenant_id)s|
> | 11cea2de9407459480a30b190e005a5c | Pod1  | neutron  | network
>  | True| internal  | http://192.168.56.101:20001/
>   |
> | 16c0d9f251d84af897dfdd8df60f76dd | Pod2  | nova_legacy  |
> compute_legacy | True| admin |
> http://192.168.56.102:8774/v2/$(tenant_id)s|
> | 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2
> | True| public| http://192.168.56.101:19997/v2/$(tenant_id)s
>   |
> | 1a068f85aa12413582c4f4d256d276af | Pod2  | nova | compute
>  | True| admin | http://192.168.56.102:8774/v2.1/$(tenant_id)s
>  |
> | 1b3799428309490bbce57043e87ac815 | RegionOne | cinder   | volume
> | True| internal  | http://192.168.56.101:8776/v1/$(tenant_id)s
>  |
> | 221d74877fdd4c03b9b9b7d752e30473 | Pod2  | neutron  | network
>  | True| internal  | http://192.168.56.102:9696/
>|
> | 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2  | cinderv2 | volumev2
> | True| public| http://192.168.56.102:8776/v2/$(tenant_id)s
>  |
> | 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity
> | True| admin | http://192.168.56.101:35357/v2.0
>   |
> | 45e4ccd5e16a423e8cb9f59742acee27 | Pod1  | neutron  | network
>  | True| public| http://192.168.56.101:20001/
>   |
> | 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder   | volume
> | True| admin | http://192.168.56.101:8776/v1/$(tenant_id)s
>  |
> | 47351cda93a54a2a9379b83c0eb445ca | Pod2  | neutron  | network
>  | True| admin | http://192.168.56.102:9696/
>|
> | 56d6f7641ee84ee58611621c4657e45d | Pod2  | nova_legacy  |
> compute_legacy | True| internal  |
> http://192.168.56.102:8774/v2/$(tenant_id)s|
> | 57887a9d15164d6cb5b58d9342316cf7 | RegionOne | glance   | image
>  | True| internal  | http://192.168.56.101:9292
>   |
> | 5f2a4f69682941edbe54a85c45a5fe1b | Pod1  | cinderv2 | volumev2
> | True| public| http://192.168.56.101:8776/v2/$(tenant_id)s
>  |
> | 6720806fe7e24a7c8335159013dba948 | Pod2  | cinderv2 | volumev2
> | True| admin | http://192.168.56.102:8776/v2/$(tenant_id)s
>  |
> | 72e2726b55414d25928b4fc9925a06ed | RegionOne | nova_legacy  |
> compute_legacy | True| public|
> http://192.168.56.101:8774/v2/$(tenant_id)s|
> | 75163e97c3014a389ab56184f970908f | Pod2  | neutron  | network
>  | True| public| http://192.168.56.102:9696/
>|
> | 77b67589282e4776916ead802646de11 | Pod1  | nova | compute
>  | True| internal  | http://192.168.56.101:8774/v2.1/$(tenant_id)s
>  |
> | 789f3456899f4381aef850822c412436 | Pod2  | nova | compute
>  | True| internal  | http://19

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-21 Thread joehuang

Hi, Yipei,

Is this port disabled to be visit in your host? Pls. check iptables.

Best Regards
Chaoyi Huang ( Joe Huang )

From: Yipei Niu [mailto:newy...@gmail.com]
Sent: Saturday, February 20, 2016 8:49 PM
To: openstack-dev@lists.openstack.org
Cc: joehuang; Zhiyuan Cai
Subject: [tricircle] playing tricircle with devstack under two-region 
configuration

Hi Joe and Zhiyuan,

I encounter an error when executing the following command:

stack@nyp-VirtualBox:~/devstack$ curl -X POST 
http://192.168.56.101:1/v1.0/pods -H "Content-Type: application/json" -H 
"X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d '{"pod": {"pod_name":  
"RegionOne"}}'
curl: (7) Failed to connect to 192.168.56.101 port 1: Connection refused

Before executing the command, I source the file "userrc_early", whose content 
is as follows:
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://192.168.56.101:35357
export OS_USERNAME=admin
export OS_USER_DOMAIN_ID=default
export OS_PASSWORD=nypnyp0316
export OS_PROJECT_NAME=admin
export OS_PROJECT_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne

Furthermore, the results of "openstack endpoint list" are as follows:
stack@nyp-VirtualBox:~/devstack$ openstack endpoint list
+--+---+--++-+---++
| ID   | Region| Service Name | Service Type   
| Enabled | Interface | URL|
+--+---+--++-+---++
| 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy  | compute_legacy 
| True| internal  | http://192.168.56.101:8774/v2/$(tenant_id)s|
| 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy  | compute_legacy 
| True| admin | http://192.168.56.101:8774/v2/$(tenant_id)s|
| 11cea2de9407459480a30b190e005a5c | Pod1  | neutron  | network
| True| internal  | http://192.168.56.101:20001/   |
| 16c0d9f251d84af897dfdd8df60f76dd | Pod2  | nova_legacy  | compute_legacy 
| True| admin | http://192.168.56.102:8774/v2/$(tenant_id)s|
| 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2   
| True| public| http://192.168.56.101:19997/v2/$(tenant_id)s   |
| 1a068f85aa12413582c4f4d256d276af | Pod2  | nova | compute
| True| admin | http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
| 1b3799428309490bbce57043e87ac815 | RegionOne | cinder   | volume 
| True| internal  | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 221d74877fdd4c03b9b9b7d752e30473 | Pod2  | neutron  | network
| True| internal  | http://192.168.56.102:9696/|
| 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2  | cinderv2 | volumev2   
| True| public| http://192.168.56.102:8776/v2/$(tenant_id)s|
| 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity   
| True| admin | http://192.168.56.101:35357/v2.0   |
| 45e4ccd5e16a423e8cb9f59742acee27 | Pod1  | neutron  | network
| True| public| http://192.168.56.101:20001/   |
| 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder   | volume 
| True| admin | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 47351cda93a54a2a9379b83c0eb445ca | Pod2  | neutron  | network
| True| admin | http://192.168.56.102:9696/|
| 56d6f7641ee84ee58611621c4657e45d | Pod2  | nova_legacy  | compute_legacy 
| True| internal  | http://192.168.56.102:8774/v2/$(tenant_id)s|
| 57887a9d15164d6cb5b58d9342316cf7 | RegionOne | glance   | image  
| True| internal  | http://192.168.56.101:9292 |
| 5f2a4f69682941edbe54a85c45a5fe1b | Pod1  | cinderv2 | volumev2   
| True| public| http://192.168.56.101:8776/v2/$(tenant_id)s|
| 6720806fe7e24a7c8335159013dba948 | Pod2  | cinderv2 | volumev2   
| True| admin | http://192.168.56.102:8776/v2/$(tenant_id)s|
| 72e2726b55414d25928b4fc9925a06ed | RegionOne | nova_legacy  | compute_legacy 
| True| public| http://192.168.56.101:8774/v2/$(tenant_id)s|
| 75163e97c3014a389ab56184f970908f | Pod2  | neutron  | network
| True| public| http://192.168.56.102:9696/|
| 77b67589282e4776916ead802646de11 | Pod1  | nova | compute
| True| internal  | http://192.168.56.101:8774/v2.1/$(tenant_id)s  |
| 789f3456899f4381aef850822c412436 | Pod2  | nova | compute
| True| internal  | http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
| 78da748f6fdc41e8b690acefec8e2838 | Pod1  | cinderv2 | volumev2   
| True| internal  | http:

[openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

2016-02-20 Thread Yipei Niu

Hi Joe and Zhiyuan,

I encounter an error when executing the following command:

stack@nyp-VirtualBox:~/devstack$ curl -X POST
http://192.168.56.101:1/v1.0/pods -H "Content-Type: application/json"
-H "X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d '{"pod":
{"pod_name":  "RegionOne"}}'
curl: (7) Failed to connect to 192.168.56.101 port 1: Connection refused

Before executing the command, I source the file "userrc_early", whose
content is as follows:
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://192.168.56.101:35357
export OS_USERNAME=admin
export OS_USER_DOMAIN_ID=default
export OS_PASSWORD=nypnyp0316
export OS_PROJECT_NAME=admin
export OS_PROJECT_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne

Furthermore, the results of "openstack endpoint list" are as follows:
stack@nyp-VirtualBox:~/devstack$ openstack endpoint list
+--+---+--++-+---++
| ID   | Region| Service Name | Service
Type   | Enabled | Interface | URL
   |
+--+---+--++-+---++
| 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy  |
compute_legacy | True| internal  |
http://192.168.56.101:8774/v2/$(tenant_id)s|
| 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy  |
compute_legacy | True| admin |
http://192.168.56.101:8774/v2/$(tenant_id)s|
| 11cea2de9407459480a30b190e005a5c | Pod1  | neutron  | network
   | True| internal  | http://192.168.56.101:20001/   |
| 16c0d9f251d84af897dfdd8df60f76dd | Pod2  | nova_legacy  |
compute_legacy | True| admin |
http://192.168.56.102:8774/v2/$(tenant_id)s|
| 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2
| True| public| http://192.168.56.101:19997/v2/$(tenant_id)s   |
| 1a068f85aa12413582c4f4d256d276af | Pod2  | nova | compute
   | True| admin | http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
| 1b3799428309490bbce57043e87ac815 | RegionOne | cinder   | volume
| True| internal  | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 221d74877fdd4c03b9b9b7d752e30473 | Pod2  | neutron  | network
   | True| internal  | http://192.168.56.102:9696/|
| 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2  | cinderv2 | volumev2
| True| public| http://192.168.56.102:8776/v2/$(tenant_id)s|
| 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity
| True| admin | http://192.168.56.101:35357/v2.0   |
| 45e4ccd5e16a423e8cb9f59742acee27 | Pod1  | neutron  | network
   | True| public| http://192.168.56.101:20001/   |
| 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder   | volume
| True| admin | http://192.168.56.101:8776/v1/$(tenant_id)s|
| 47351cda93a54a2a9379b83c0eb445ca | Pod2  | neutron  | network
   | True| admin | http://192.168.56.102:9696/|
| 56d6f7641ee84ee58611621c4657e45d | Pod2  | nova_legacy  |
compute_legacy | True| internal  |
http://192.168.56.102:8774/v2/$(tenant_id)s|
| 57887a9d15164d6cb5b58d9342316cf7 | RegionOne | glance   | image
   | True| internal  | http://192.168.56.101:9292 |
| 5f2a4f69682941edbe54a85c45a5fe1b | Pod1  | cinderv2 | volumev2
| True| public| http://192.168.56.101:8776/v2/$(tenant_id)s|
| 6720806fe7e24a7c8335159013dba948 | Pod2  | cinderv2 | volumev2
| True| admin | http://192.168.56.102:8776/v2/$(tenant_id)s|
| 72e2726b55414d25928b4fc9925a06ed | RegionOne | nova_legacy  |
compute_legacy | True| public|
http://192.168.56.101:8774/v2/$(tenant_id)s|
| 75163e97c3014a389ab56184f970908f | Pod2  | neutron  | network
   | True| public| http://192.168.56.102:9696/|
| 77b67589282e4776916ead802646de11 | Pod1  | nova | compute
   | True| internal  | http://192.168.56.101:8774/v2.1/$(tenant_id)s  |
| 789f3456899f4381aef850822c412436 | Pod2  | nova | compute
   | True| internal  | http://192.168.56.102:8774/v2.1/$(tenant_id)s  |
| 78da748f6fdc41e8b690acefec8e2838 | Pod1  | cinderv2 | volumev2
| True| internal  | http://192.168.56.101:8776/v2/$(tenant_id)s|
| 844402eaacb24f0480aacf7bae9139ee | Pod1  | nova | compute
   | True| public| http://192.168.56.101:8774/v2.1/$(tenant_id)s  |
| 854c00bb353548ad85e691278f74f51f | Pod1  | cinderv2 | volumev2
| True| admin | http://192.168.56.101:8776/v2/$(tenant_id)s|
| 8d1cd835e76b4f8d9ebb4c61526cb0b0 | Pod2  | cinderv2 | volumev2
| True| internal  | http://192.168.56.102:8776/v2/$(tenant_i

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

[openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

20 matches

Site Navigation

Mail list logo

Footer information