from:"Yipei Niu"

[openstack-dev] [tricircle] About the specification for dynamic pod binding

2016-06-15 Thread Yipei Niu

Dear Shinobu,

I have revised the description of dynamic pod binding and submitted a new
patch. Here is the link of the path:
https://review.openstack.org/#/c/306224/12. Is the description clear enough
to help readers understand the patch. Could you please go through the
description and give me some further comments?

Look forward to your valuable comments.

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] About registering and loading a plugin

2016-06-29 Thread Yipei Niu

Hi all,

I have succeed in registering a config option and obtaining it. So how to
load an option from a customized file? Through
cfg.CONF(default_config_files=[setup.cfg]? Still fails loading the config
options in setup.cfg.

Best regards,
Yipei

On Wed, Jun 29, 2016 at 8:36 AM, joehuang <joehu...@huawei.com> wrote:

> Hi, Yipei,
>
>
> "Moreover, I tried to load drivers by line "cfg.CONF.nyp.plugins.simple",
> the console prompts oslo_config.cfg.NoSuchOptError: no such option in group
> DEFAULT: nyp. The setup.cfg is defined as follows."
>
> You are using entry point but not configuration options for plugin
> discovery, and no config option you have registered in oslo_config.cfg, so
> " no such option in group DEFAULT:".
>
> Best Regards
> Chaoyi Huang ( joehuang )
>
> --
> *From:* Yipei Niu [newy...@gmail.com]
> *Sent:* 28 June 2016 22:05
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Cc:* joehuang; Vega Cai; ski...@redhat.com; 金城 忍
> *Subject:* Re: [tricircle] About registering and loading a plugin
>
> Hi all,
>
> Thanks a lot for your valuable advice. I have already succeed in
> registering and loading a self-defined plugin. The entry_point is generated
> by executing setup.py, and found in .egg-info/entry_points.txt, which is
> different from using setup.cfg in https://review.openstack.org/#/c/331638/
> .
>
> Moreover, I tried to load drivers by line "cfg.CONF.nyp.plugins.simple",
> the console prompts oslo_config.cfg.NoSuchOptError: no such option in group
> DEFAULT: nyp. The setup.cfg is defined as follows.
>
> [entry_points]
> nyp.plugins.formmater =
> simple = nyp.plugins.simple:SimpleFormatter
> plain = nyp.plugins.simple:SimpleFormatter
> field = nyp.plugins.field:FieldList
>
> How to solve the problem?
>
> Best regards,
> Yipei
>
> On Tue, Jun 28, 2016 at 10:35 AM, Vega Cai <luckyveg...@gmail.com> wrote:
>
>> Hi Yipei,
>>
>> You can also refer to my network type driver implementation:
>>
>> https://review.openstack.org/#/c/331638/
>>
>> Type driver is registered in setup.cfg and loaded by code.
>>
>> BR
>> Zhiyuan
>>
>> On 27 June 2016 at 21:44, Yipei Niu <newy...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> Recently, I learn to name a plugin based on the doc
>>> http://docs.openstack.org/developer/stevedore/tutorial/naming.html#. I
>>> define a new entry_point for the plugin, then it fails. The console prompts
>>> "stevedore.exception.NoMatches: No 'net.nyp.formatter' driver found,
>>> looking for 'simple'". After setting a new entry_point with setuptools, why
>>> stevedore cannot find the driver based on the entry_point?
>>>
>>> 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

2016-01-27 Thread Yipei Niu

Hi Jeo,

This error occurred when installing devstack on node2.

Best regards,
Yipei

On Wed, Jan 27, 2016 at 3:13 PM, Yipei Niu <newy...@gmail.com> wrote:

>
> -- Forwarded message ------
> From: Yipei Niu <newy...@gmail.com>
> Date: Tue, Jan 26, 2016 at 8:42 PM
> Subject: Re: [tricircle] Playing Tricircle with Devstack
> To: openstack-dev@lists.openstack.org
>
>
> Hi Zhiyuan,
>
> Your solution works, but I encountered another error. When executing
> command
>
> "openstack volume type create --property volume_backend_name=lvmdriver-1
> lvmdriver-1",
>
> it returns
>
> "Unable to establish connection to
> http://192.168.56.101:19997/v2/c4f6ad92427b49f9a59810e88fbe4c11/types;.
>
>
> Then I execute the command with debug option, it returns
>
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/openstackclient/shell.py",
> line 113, in run
> ret_val = super(OpenStackShell, self).run(argv)
>   File "/usr/local/lib/python2.7/dist-packages/cliff/app.py", line 255, in
> run
> result = self.run_subcommand(remainder)
>   File "/usr/local/lib/python2.7/dist-packages/cliff/app.py", line 367, in
> run_subcommand
> self.prepare_to_run_command(cmd)
>   File "/usr/local/lib/python2.7/dist-packages/openstackclient/shell.py",
> line 352, in prepare_to_run_command
> self.client_manager.auth_ref
>   File
> "/usr/local/lib/python2.7/dist-packages/openstackclient/common/clientmanager.py",
> line 189, in auth_ref
> self.setup_auth()
>   File
> "/usr/local/lib/python2.7/dist-packages/openstackclient/common/clientmanager.py",
> line 128, in setup_auth
> auth.check_valid_auth_options(self._cli_options, self.auth_plugin_name)
>   File
> "/usr/local/lib/python2.7/dist-packages/openstackclient/api/auth.py", line
> 172, in check_valid_auth_options
> raise exc.CommandError('Missing parameter(s): \n%s' % msg)
> CommandError: Missing parameter(s):
> Set a username with --os-username, OS_USERNAME, or auth.username
> Set an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_url
> Set a scope, such as a project or domain, set a project scope with
> --os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope
> with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name
>
> These parameters have been set before, and why the error happens?
>
> Best regards,
> Yipei
>
>
> On Tue, Jan 26, 2016 at 10:40 AM, Yipei Niu <newy...@gmail.com> wrote:
>
>> Hi Joe, Zhiyuan,
>>
>> I found that such an error may be caused by "export OS_REGION_NAME=Pod2".
>> When I source "userrc_early" without "export OS_REGION_NAME=Pod2" on node2,
>> the command "openstack project show admin -f value -c id" returns the
>> same result as it does on node1. How can I deal with it so that I can
>> proceed?
>>
>> Best regards,
>> Yipei
>>
>> On Mon, Jan 25, 2016 at 4:13 PM, Yipei Niu <newy...@gmail.com> wrote:
>>
>>> There doesn't any problems when installing devstack on node1. However,
>>> when install devstack to node2, I encounter an error and the trace is as
>>> follows:
>>>
>>> 2016-01-25 07:40:47.068 | + echo -e Starting Keystone
>>> 2016-01-25 07:40:47.069 | + '[' 192.168.56.101 == 192.168.56.102 ']'
>>> 2016-01-25 07:40:47.070 | + is_service_enabled tls-proxy
>>> 2016-01-25 07:40:47.091 | + return 1
>>> 2016-01-25 07:40:47.091 | + cat
>>> 2016-01-25 07:40:47.093 | + source /home/stack/devstack/userrc_early
>>> 2016-01-25 07:40:47.095 | ++ export OS_IDENTITY_API_VERSION=3
>>> 2016-01-25 07:40:47.095 | ++ OS_IDENTITY_API_VERSION=3
>>> 2016-01-25 07:40:47.095 | ++ export OS_AUTH_URL=
>>> http://192.168.56.101:35357
>>> 2016-01-25 07:40:47.095 | ++ OS_AUTH_URL=http://192.168.56.101:35357
>>> 2016-01-25 07:40:47.095 | ++ export OS_USERNAME=admin
>>> 2016-01-25 07:40:47.095 | ++ OS_USERNAME=admin
>>> 2016-01-25 07:40:47.095 | ++ export OS_USER_DOMAIN_ID=default
>>> 2016-01-25 07:40:47.095 | ++ OS_USER_DOMAIN_ID=default
>>> 2016-01-25 07:40:47.096 | ++ export OS_PASSWORD=nypnyp0316
>>> 2016-01-25 07:40:47.096 | ++ OS_PASSWORD=nypnyp0316
>>> 2016-01-25 07:40:47.096 | ++ export OS_PROJECT_NAME=admin
>>> 2016-01-25 07:40:47.097 | ++ OS_PROJECT_NAME=admin
>>> 2016-01-25 07:40:47.098 | ++ export OS_PROJECT_DOMAIN_ID=default
>>> 2016-01-25 07:40:47.099 | ++ OS_PROJECT_DOMAIN_ID=default
>>> 2016-01-25 07:40:47.100 | ++ export OS_RE

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 <newy...@gmail.com> 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-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 <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^[[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^[[00mValu

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 <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 <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 | Regi

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

[openstack-dev] [tricircle] Playing Tricircle with Devstack

2016-01-25 Thread Yipei Niu

There doesn't any problems when installing devstack on node1. However, when
install devstack to node2, I encounter an error and the trace is as follows:

2016-01-25 07:40:47.068 | + echo -e Starting Keystone
2016-01-25 07:40:47.069 | + '[' 192.168.56.101 == 192.168.56.102 ']'
2016-01-25 07:40:47.070 | + is_service_enabled tls-proxy
2016-01-25 07:40:47.091 | + return 1
2016-01-25 07:40:47.091 | + cat
2016-01-25 07:40:47.093 | + source /home/stack/devstack/userrc_early
2016-01-25 07:40:47.095 | ++ export OS_IDENTITY_API_VERSION=3
2016-01-25 07:40:47.095 | ++ OS_IDENTITY_API_VERSION=3
2016-01-25 07:40:47.095 | ++ export OS_AUTH_URL=http://192.168.56.101:35357
2016-01-25 07:40:47.095 | ++ OS_AUTH_URL=http://192.168.56.101:35357
2016-01-25 07:40:47.095 | ++ export OS_USERNAME=admin
2016-01-25 07:40:47.095 | ++ OS_USERNAME=admin
2016-01-25 07:40:47.095 | ++ export OS_USER_DOMAIN_ID=default
2016-01-25 07:40:47.095 | ++ OS_USER_DOMAIN_ID=default
2016-01-25 07:40:47.096 | ++ export OS_PASSWORD=nypnyp0316
2016-01-25 07:40:47.096 | ++ OS_PASSWORD=nypnyp0316
2016-01-25 07:40:47.096 | ++ export OS_PROJECT_NAME=admin
2016-01-25 07:40:47.097 | ++ OS_PROJECT_NAME=admin
2016-01-25 07:40:47.098 | ++ export OS_PROJECT_DOMAIN_ID=default
2016-01-25 07:40:47.099 | ++ OS_PROJECT_DOMAIN_ID=default
2016-01-25 07:40:47.100 | ++ export OS_REGION_NAME=Pod2
2016-01-25 07:40:47.101 | ++ OS_REGION_NAME=Pod2
2016-01-25 07:40:47.102 | + create_keystone_accounts
2016-01-25 07:40:47.105 | + local admin_tenant
2016-01-25 07:40:47.111 | ++ openstack project show admin -f value -c id
2016-01-25 07:40:48.408 | Could not find resource admin
2016-01-25 07:40:48.452 | + admin_tenant=
2016-01-25 07:40:48.453 | + exit_trap
2016-01-25 07:40:48.454 | + local r=1
2016-01-25 07:40:48.456 | ++ jobs -p
2016-01-25 07:40:48.461 | + jobs=
2016-01-25 07:40:48.464 | + [[ -n '' ]]
2016-01-25 07:40:48.464 | + kill_spinner
2016-01-25 07:40:48.464 | + '[' '!' -z '' ']'
2016-01-25 07:40:48.464 | + [[ 1 -ne 0 ]]
2016-01-25 07:40:48.464 | + echo 'Error on exit'
2016-01-25 07:40:48.464 | Error on exit
2016-01-25 07:40:48.464 | + generate-subunit 1453707531 117 fail
2016-01-25 07:40:48.885 | + [[ -z /opt/stack/logs ]]
2016-01-25 07:40:48.886 | + /home/stack/devstack/tools/worlddump.py -d
/opt/stack/logs
2016-01-25 07:40:48.944 | df: '/run/user/112/gvfs': Permission denied
2016-01-25 07:40:49.166 | + exit 1

Could you please give me some advice on solving it?
__
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

2016-01-26 Thread Yipei Niu

Hi Zhiyuan,

Your solution works, but I encountered another error. When executing
command

"openstack volume type create --property volume_backend_name=lvmdriver-1
lvmdriver-1",

it returns

"Unable to establish connection to
http://192.168.56.101:19997/v2/c4f6ad92427b49f9a59810e88fbe4c11/types;.


Then I execute the command with debug option, it returns

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/openstackclient/shell.py",
line 113, in run
ret_val = super(OpenStackShell, self).run(argv)
  File "/usr/local/lib/python2.7/dist-packages/cliff/app.py", line 255, in
run
result = self.run_subcommand(remainder)
  File "/usr/local/lib/python2.7/dist-packages/cliff/app.py", line 367, in
run_subcommand
self.prepare_to_run_command(cmd)
  File "/usr/local/lib/python2.7/dist-packages/openstackclient/shell.py",
line 352, in prepare_to_run_command
self.client_manager.auth_ref
  File
"/usr/local/lib/python2.7/dist-packages/openstackclient/common/clientmanager.py",
line 189, in auth_ref
self.setup_auth()
  File
"/usr/local/lib/python2.7/dist-packages/openstackclient/common/clientmanager.py",
line 128, in setup_auth
auth.check_valid_auth_options(self._cli_options, self.auth_plugin_name)
  File
"/usr/local/lib/python2.7/dist-packages/openstackclient/api/auth.py", line
172, in check_valid_auth_options
raise exc.CommandError('Missing parameter(s): \n%s' % msg)
CommandError: Missing parameter(s):
Set a username with --os-username, OS_USERNAME, or auth.username
Set an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_url
Set a scope, such as a project or domain, set a project scope with
--os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope
with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name

These parameters have been set before, and why the error happens?

Best regards,
Yipei


On Tue, Jan 26, 2016 at 10:40 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi Joe, Zhiyuan,
>
> I found that such an error may be caused by "export OS_REGION_NAME=Pod2".
> When I source "userrc_early" without "export OS_REGION_NAME=Pod2" on node2,
> the command "openstack project show admin -f value -c id" returns the
> same result as it does on node1. How can I deal with it so that I can
> proceed?
>
> Best regards,
> Yipei
>
> On Mon, Jan 25, 2016 at 4:13 PM, Yipei Niu <newy...@gmail.com> wrote:
>
>> There doesn't any problems when installing devstack on node1. However,
>> when install devstack to node2, I encounter an error and the trace is as
>> follows:
>>
>> 2016-01-25 07:40:47.068 | + echo -e Starting Keystone
>> 2016-01-25 07:40:47.069 | + '[' 192.168.56.101 == 192.168.56.102 ']'
>> 2016-01-25 07:40:47.070 | + is_service_enabled tls-proxy
>> 2016-01-25 07:40:47.091 | + return 1
>> 2016-01-25 07:40:47.091 | + cat
>> 2016-01-25 07:40:47.093 | + source /home/stack/devstack/userrc_early
>> 2016-01-25 07:40:47.095 | ++ export OS_IDENTITY_API_VERSION=3
>> 2016-01-25 07:40:47.095 | ++ OS_IDENTITY_API_VERSION=3
>> 2016-01-25 07:40:47.095 | ++ export OS_AUTH_URL=
>> http://192.168.56.101:35357
>> 2016-01-25 07:40:47.095 | ++ OS_AUTH_URL=http://192.168.56.101:35357
>> 2016-01-25 07:40:47.095 | ++ export OS_USERNAME=admin
>> 2016-01-25 07:40:47.095 | ++ OS_USERNAME=admin
>> 2016-01-25 07:40:47.095 | ++ export OS_USER_DOMAIN_ID=default
>> 2016-01-25 07:40:47.095 | ++ OS_USER_DOMAIN_ID=default
>> 2016-01-25 07:40:47.096 | ++ export OS_PASSWORD=nypnyp0316
>> 2016-01-25 07:40:47.096 | ++ OS_PASSWORD=nypnyp0316
>> 2016-01-25 07:40:47.096 | ++ export OS_PROJECT_NAME=admin
>> 2016-01-25 07:40:47.097 | ++ OS_PROJECT_NAME=admin
>> 2016-01-25 07:40:47.098 | ++ export OS_PROJECT_DOMAIN_ID=default
>> 2016-01-25 07:40:47.099 | ++ OS_PROJECT_DOMAIN_ID=default
>> 2016-01-25 07:40:47.100 | ++ export OS_REGION_NAME=Pod2
>> 2016-01-25 07:40:47.101 | ++ OS_REGION_NAME=Pod2
>> 2016-01-25 07:40:47.102 | + create_keystone_accounts
>> 2016-01-25 07:40:47.105 | + local admin_tenant
>> 2016-01-25 07:40:47.111 | ++ openstack project show admin -f value -c id
>> 2016-01-25 07:40:48.408 | Could not find resource admin
>> 2016-01-25 07:40:48.452 | + admin_tenant=
>> 2016-01-25 07:40:48.453 | + exit_trap
>> 2016-01-25 07:40:48.454 | + local r=1
>> 2016-01-25 07:40:48.456 | ++ jobs -p
>> 2016-01-25 07:40:48.461 | + jobs=
>> 2016-01-25 07:40:48.464 | + [[ -n '' ]]
>> 2016-01-25 07:40:48.464 | + kill_spinner
>> 2016-01-25 07:40:48.464 | + '[' '!' -z '' ']'
>> 2016-01-25 07:40:48.464 | + [[ 1 -ne 0 ]]
>> 2016-01-25 07:40:48.464 | + echo 'Error on exit'
&g

Re: [openstack-dev] [tricircle] Playing Tricircle with Devstack

2016-01-25 Thread Yipei Niu

Hi Joe, Zhiyuan,

I found that such an error may be caused by "export OS_REGION_NAME=Pod2".
When I source "userrc_early" without "export OS_REGION_NAME=Pod2" on node2,
the command "openstack project show admin -f value -c id" returns the same
result as it does on node1. How can I deal with it so that I can proceed?

Best regards,
Yipei

On Mon, Jan 25, 2016 at 4:13 PM, Yipei Niu <newy...@gmail.com> wrote:

> There doesn't any problems when installing devstack on node1. However,
> when install devstack to node2, I encounter an error and the trace is as
> follows:
>
> 2016-01-25 07:40:47.068 | + echo -e Starting Keystone
> 2016-01-25 07:40:47.069 | + '[' 192.168.56.101 == 192.168.56.102 ']'
> 2016-01-25 07:40:47.070 | + is_service_enabled tls-proxy
> 2016-01-25 07:40:47.091 | + return 1
> 2016-01-25 07:40:47.091 | + cat
> 2016-01-25 07:40:47.093 | + source /home/stack/devstack/userrc_early
> 2016-01-25 07:40:47.095 | ++ export OS_IDENTITY_API_VERSION=3
> 2016-01-25 07:40:47.095 | ++ OS_IDENTITY_API_VERSION=3
> 2016-01-25 07:40:47.095 | ++ export OS_AUTH_URL=
> http://192.168.56.101:35357
> 2016-01-25 07:40:47.095 | ++ OS_AUTH_URL=http://192.168.56.101:35357
> 2016-01-25 07:40:47.095 | ++ export OS_USERNAME=admin
> 2016-01-25 07:40:47.095 | ++ OS_USERNAME=admin
> 2016-01-25 07:40:47.095 | ++ export OS_USER_DOMAIN_ID=default
> 2016-01-25 07:40:47.095 | ++ OS_USER_DOMAIN_ID=default
> 2016-01-25 07:40:47.096 | ++ export OS_PASSWORD=nypnyp0316
> 2016-01-25 07:40:47.096 | ++ OS_PASSWORD=nypnyp0316
> 2016-01-25 07:40:47.096 | ++ export OS_PROJECT_NAME=admin
> 2016-01-25 07:40:47.097 | ++ OS_PROJECT_NAME=admin
> 2016-01-25 07:40:47.098 | ++ export OS_PROJECT_DOMAIN_ID=default
> 2016-01-25 07:40:47.099 | ++ OS_PROJECT_DOMAIN_ID=default
> 2016-01-25 07:40:47.100 | ++ export OS_REGION_NAME=Pod2
> 2016-01-25 07:40:47.101 | ++ OS_REGION_NAME=Pod2
> 2016-01-25 07:40:47.102 | + create_keystone_accounts
> 2016-01-25 07:40:47.105 | + local admin_tenant
> 2016-01-25 07:40:47.111 | ++ openstack project show admin -f value -c id
> 2016-01-25 07:40:48.408 | Could not find resource admin
> 2016-01-25 07:40:48.452 | + admin_tenant=
> 2016-01-25 07:40:48.453 | + exit_trap
> 2016-01-25 07:40:48.454 | + local r=1
> 2016-01-25 07:40:48.456 | ++ jobs -p
> 2016-01-25 07:40:48.461 | + jobs=
> 2016-01-25 07:40:48.464 | + [[ -n '' ]]
> 2016-01-25 07:40:48.464 | + kill_spinner
> 2016-01-25 07:40:48.464 | + '[' '!' -z '' ']'
> 2016-01-25 07:40:48.464 | + [[ 1 -ne 0 ]]
> 2016-01-25 07:40:48.464 | + echo 'Error on exit'
> 2016-01-25 07:40:48.464 | Error on exit
> 2016-01-25 07:40:48.464 | + generate-subunit 1453707531 117 fail
> 2016-01-25 07:40:48.885 | + [[ -z /opt/stack/logs ]]
> 2016-01-25 07:40:48.886 | + /home/stack/devstack/tools/worlddump.py -d
> /opt/stack/logs
> 2016-01-25 07:40:48.944 | df: '/run/user/112/gvfs': Permission denied
> 2016-01-25 07:40:49.166 | + exit 1
>
> Could you please give me some advice on solving it?
>
__
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

[openstack-dev] Installing devstack with multi-region setting fails

2016-02-17 Thread Yipei Niu

2016-01-29 03:26:29.317 | + source /home/stack/devstack/userrc_early
2016-01-29 03:26:29.317 | ++ export OS_IDENTITY_API_VERSION=3
2016-01-29 03:26:29.317 | ++ OS_IDENTITY_API_VERSION=3
2016-01-29 03:26:29.318 | ++ export OS_AUTH_URL=http://192.168.56.101:35357
2016-01-29 03:26:29.318 | ++ OS_AUTH_URL=http://192.168.56.101:35357
2016-01-29 03:26:29.318 | ++ export OS_USERNAME=admin
2016-01-29 03:26:29.318 | ++ OS_USERNAME=admin
2016-01-29 03:26:29.318 | ++ export OS_USER_DOMAIN_ID=default
2016-01-29 03:26:29.318 | ++ OS_USER_DOMAIN_ID=default
2016-01-29 03:26:29.318 | ++ export OS_PASSWORD=nypnyp0316
2016-01-29 03:26:29.318 | ++ OS_PASSWORD=nypnyp0316
2016-01-29 03:26:29.319 | ++ export OS_PROJECT_NAME=admin
2016-01-29 03:26:29.319 | ++ OS_PROJECT_NAME=admin
2016-01-29 03:26:29.319 | ++ export OS_PROJECT_DOMAIN_ID=default
2016-01-29 03:26:29.319 | ++ OS_PROJECT_DOMAIN_ID=default
2016-01-29 03:26:29.319 | ++ export OS_REGION_NAME=RegionTwo
2016-01-29 03:26:29.319 | ++ OS_REGION_NAME=RegionTwo
2016-01-29 03:26:29.319 | + create_keystone_accounts
2016-01-29 03:26:29.319 | + local admin_tenant
2016-01-29 03:26:29.320 | ++ openstack project show admin -f value -c id
2016-01-29 03:26:30.624 | Could not find resource admin
2016-01-29 03:26:30.667 | + admin_tenant=
2016-01-29 03:26:30.668 | + exit_trap
2016-01-29 03:26:30.668 | + local r=1
2016-01-29 03:26:30.669 | ++ jobs -p
2016-01-29 03:26:30.671 | + jobs=
2016-01-29 03:26:30.672 | + [[ -n '' ]]
2016-01-29 03:26:30.672 | + kill_spinner
2016-01-29 03:26:30.672 | + '[' '!' -z '' ']'
2016-01-29 03:26:30.672 | + [[ 1 -ne 0 ]]
2016-01-29 03:26:30.673 | + echo 'Error on exit'
2016-01-29 03:26:30.674 | Error on exit
2016-01-29 03:26:30.675 | + generate-subunit 1454037870 120 fail
2016-01-29 03:26:31.045 | + [[ -z /opt/stack/logs ]]
2016-01-29 03:26:31.045 | + /home/stack/devstack/tools/worlddump.py -d
/opt/stack/logs
2016-01-29 03:26:31.111 | df: '/run/user/112/gvfs': Permission denied
2016-01-29 03:26:31.312 | + exit 1

Under the multi-region setting, two devstack, i.e., RegionOne and
RegionTwo, share the same Keystone service in RegionOne. The file of
local.conf of RegionTwo is set as
http://docs.openstack.org/developer/devstack/configuration.html#multi-region-setup
indicated.
In the configuration, the REGION_NAME is set as "RegionTwo".
Correspondingly, OS_REGION_NAME is set as "RegionTwo" as well based on
"export OS_REGION_NAME=$REGION_NAME" in stack.sh. When executing "openstack
project show admin -f value -c id", it hence fails finding resource admin
in RegionTwo instead of RegionOne.

I have report the bug, seen in
https://bugs.launchpad.net/devstack/+bug/1540802.
__
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

[openstack-dev] [devstack] Installing devstack with multi-region setting fails

2016-02-18 Thread Yipei Niu

2016-01-29 03:26:29.317 | + source /home/stack/devstack/userrc_early
2016-01-29 03:26:29.317 | ++ export OS_IDENTITY_API_VERSION=3
2016-01-29 03:26:29.317 | ++ OS_IDENTITY_API_VERSION=3
2016-01-29 03:26:29.318 | ++ export OS_AUTH_URL=http://192.168.56.101:35357
2016-01-29 03:26:29.318 | ++ OS_AUTH_URL=http://192.168.56.101:35357
2016-01-29 03:26:29.318 | ++ export OS_USERNAME=admin
2016-01-29 03:26:29.318 | ++ OS_USERNAME=admin
2016-01-29 03:26:29.318 | ++ export OS_USER_DOMAIN_ID=default
2016-01-29 03:26:29.318 | ++ OS_USER_DOMAIN_ID=default
2016-01-29 03:26:29.318 | ++ export OS_PASSWORD=nypnyp0316
2016-01-29 03:26:29.318 | ++ OS_PASSWORD=nypnyp0316
2016-01-29 03:26:29.319 | ++ export OS_PROJECT_NAME=admin
2016-01-29 03:26:29.319 | ++ OS_PROJECT_NAME=admin
2016-01-29 03:26:29.319 | ++ export OS_PROJECT_DOMAIN_ID=default
2016-01-29 03:26:29.319 | ++ OS_PROJECT_DOMAIN_ID=default
2016-01-29 03:26:29.319 | ++ export OS_REGION_NAME=RegionTwo
2016-01-29 03:26:29.319 | ++ OS_REGION_NAME=RegionTwo
2016-01-29 03:26:29.319 | + create_keystone_accounts
2016-01-29 03:26:29.319 | + local admin_tenant
2016-01-29 03:26:29.320 | ++ openstack project show admin -f value -c id
2016-01-29 03:26:30.624 | Could not find resource admin
2016-01-29 03:26:30.667 | + admin_tenant=
2016-01-29 03:26:30.668 | + exit_trap
2016-01-29 03:26:30.668 | + local r=1
2016-01-29 03:26:30.669 | ++ jobs -p
2016-01-29 03:26:30.671 | + jobs=
2016-01-29 03:26:30.672 | + [[ -n '' ]]
2016-01-29 03:26:30.672 | + kill_spinner
2016-01-29 03:26:30.672 | + '[' '!' -z '' ']'
2016-01-29 03:26:30.672 | + [[ 1 -ne 0 ]]
2016-01-29 03:26:30.673 | + echo 'Error on exit'
2016-01-29 03:26:30.674 | Error on exit
2016-01-29 03:26:30.675 | + generate-subunit 1454037870 120 fail
2016-01-29 03:26:31.045 | + [[ -z /opt/stack/logs ]]
2016-01-29 03:26:31.045 | + /home/stack/devstack/tools/worlddump.py -d
/opt/stack/logs
2016-01-29 03:26:31.111 | df: '/run/user/112/gvfs': Permission denied
2016-01-29 03:26:31.312 | + exit 1

Under the multi-region setting, two devstack, i.e., RegionOne and
RegionTwo, share the same Keystone service in RegionOne. The file of
local.conf of RegionTwo is set as
http://docs.openstack.org/developer/devstack/configuration.html#multi-region-setup
indicated.
In the configuration, the REGION_NAME is set as "RegionTwo".
Correspondingly, OS_REGION_NAME is set as "RegionTwo" as well based on
"export OS_REGION_NAME=$REGION_NAME" in stack.sh. When executing "openstack
project show admin -f value -c id", it hence fails finding resource admin
in RegionTwo instead of RegionOne.

I have reported the bug, seen in
https://bugs.launchpad.net/devstack/+bug/1540802.
__
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

[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  |

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 <joehu...@huawei.com> 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 <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 
>
> ^[[

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 <luckyveg...@gmail.com> wrote:

> Hi, All,
>
> Let's move the discussion to #openstack-tricircle in IRC.
>
> BR
> Zhiyuan
>
> On 1 March 2016 at 11:07, Yipei Niu <newy...@gmail.com> 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 <joehu...@huawei.com> 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 <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

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-28 Thread Yipei Niu

Hi, all,

I checked nova.conf and local.conf both.

In nova.conf, the option "nova_api_class" is missing while "use_neutron" is
set as True. I modify the lib/nova so that the devstack can write
"nova_api_class=nova.network.api.API" to nova.conf [1]. However, after
installing devstack with tricircle, the same error still happens as before.

In local.conf, n-net is disabled, which is the same as the sample file of
tricircle.

[1] http://docs.openstack.org/developer/nova/sample_config.html

Best regards,
Yipei

On Mon, Mar 28, 2016 at 4:46 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote:

> FYI:
> This is the reason is that there is still n-net. [1]
>
> [1]
> http://docs.openstack.org/openstack-ops/content/nova-network-deprecation.html
>
> Cheers,
> S
>
> On Mon, Mar 28, 2016 at 5:08 PM, joehuang <joehu...@huawei.com> wrote:
> > Hi,
> >
> >
> >
> > Agree, it’s quite important not to use Nova-network in devstack. In
> devstack
> > local.conf, make sure the Neutron service is enabled and Nova-network is
> > disabled.
> >
> >
> >
> > # Use Neutron instead of nova-network
> >
> > disable_service n-net
> >
> > enable_service q-svc
> >
> > enable_service q-svc1
> >
> > enable_service q-dhcp
> >
> > enable_service q-agt
> >
> >
> >
> > And also check the configuration in Nova to use Neutron
> >
> >
> >
> > Best Regards
> >
> > Chaoyi Huang ( Joe Huang )
> >
> >
> >
> > From: Vega Cai [mailto:luckyveg...@gmail.com]
> > Sent: Monday, March 28, 2016 2:55 PM
> > To: Yipei Niu
> > Cc: OpenStack Development Mailing List (not for usage questions);
> joehuang
> > Subject: Re: [openstack-dev] [tricircle] playing tricircle with two node
> > configuration
> >
> >
> >
> > Hi Yipei,
> >
> >
> >
> > Check "network_api_class" and "use_neutron" options in your nova.conf. It
> > seems that your nova API is not configured to use neutron.
> >
> >
> >
> > BR
> >
> > Zhiyuan
> >
> >
> >
> > On 28 March 2016 at 13:25, Yipei Niu <newy...@gmail.com> wrote:
> >
> > Hi, all,
> >
> >
> >
> > After I execute the command "nova boot --flavor 1 --image
> > c30b097c-b185-4f70-9fcd-09ffdaee5793 --nic
> > net-id=a9059cde-3065-4615-859a-facd6aa66b76 --availability-zone az1 vm1",
> > there exist some problem with the argument port. In t-ngw.log, I find
> that
> > the status of port switches from ACTIVE to DOWN, which is marked as bold
> > below. Is it the reason why I failed to boot a VM?
> >
> >
> >
> > 2016-03-28 11:49:44.026 ^[[00;32mDEBUG neutronclient.client
> > [^[[01;36mreq-414f74df-019a-425c-8d49-a081706b2bd4 ^[[00;36madmin
> > admin^[[00;32m] ^[[01;35m^[[00;32mREQ: curl -i
> > http://192.168.56.101:9696//v2.0/ports.json -X POST -H "User-Agent:
> > python-neutronclient" -H "X-Auth-Token:
> 7cfcfb91173a4920adaf24db7eebd773" -d
> > '{"port": {"network_id": "a9059cde-3065-4615-859a-facd6aa66b76",
> > "admin_state_up": true}}'^[[00m ^[[00;33mfrom (pid=17537) http_log_req
> >
> /usr/local/lib/python2.7/dist-packages/neutronclient/common/utils.py:141^[[00m
> >
> > 2016-03-28 11:49:44.254 ^[[00;32mDEBUG neutronclient.client
> > [^[[01;36mreq-414f74df-019a-425c-8d49-a081706b2bd4 ^[[00;36madmin
> > admin^[[00;32m] ^[[01;35m^[[00;32mRESP: 201 {'Date': 'Mon, 28 Mar 2016
> > 03:49:44 GMT', 'Connection': 'keep-alive', 'Content-Type':
> > 'application/json; charset=UTF-8', 'Content-Length': '384',
> > 'X-Openstack-Request-Id': 'req-b824dc9e-2fcf-4922-96a5-83beb1f0bff3'}
> > {"port": {"status": "ACTIVE", "name": "", "admin_state_up": true,
> > "network_id": "a9059cde-3065-4615-859a-facd6aa66b76", "tenant_id":
> > "29a524d386754a94850277afea1e569f", "device_owner": "", "mac_address":
> > "fa:16:3e:11:bd:09", "fixed_ips": [{"subnet_id":
> > "2bb5f6fd-01b5-4ad3-ac41-eb8a89a6323d", "ip_address": "10.0.8.5"}], "id":
> > "e27dc15d-188f-4d60-a38c-f48052d6330b", "device_id": ""}}^[[00m
> > ^[[00;33mfrom (pid=17537) http_log_resp
> >
> /usr/local/lib/python2.7/dist-packages/neutronclient/common/utils.py:150^[[00m
> >
> > 2016-03-28 11:49:44.277 ^[[00;32mDEBUG neutronclient.clien

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-22 Thread Yipei Niu

OK. Got it. Thanks a lot for your help!

Best regards,
Yipei

On Wed, Mar 23, 2016 at 11:41 AM, joehuang <joehu...@huawei.com> wrote:

> Hi, Yipei,
>
>
>
> When you play Tricircle, it’s important to know that Tricircle is the
> OpenStack API gateway to other OpenStack instances. In the Readme, Pod1,
> Pod2 are two OpenStack instances, before trying Tricircle, you can make
> sure the environment is normal or not by executeing command separately on
> Pod1, Pod2, just  Nova –os-region-name Pod1, or Nova –os-region-name Pod2,
> in fact, because Pod1,Pod2 are two normal OpenStack instances, any command
> to Pod1,Pod2 should be successful.  Otherwise that means there are some
> issue in the installation of the environment itself. Only when each bottom
> OpenStack can work correctly, then you can even manually add Tricircle, or
> through the scripts in the github to install Tircircle automaticly, as the
> API gateway to Pod1 and Pod2, just like you add one load balancer before
> your multiple web servers.
>
>
>
> After the Tricircle was added, then the API will flow from Tricircle
> services like Nova-APIGW/Cinder-APIGW/Neutron API to the bottom Pod1, Pod2.
>
>
>
> So if you use Nova boot, and some error happened, you can ask question:
>
> 1.  Is the command sent to the Tricircle Nova-APIGW?
>
> 2.  What’ll will do for the Nova-APIGW for the next step?
>
> 3.  Is the API request forwarded by Tricircle correctly to the proper
> bottom OpenStack?
>
> 4.  Is the bottom OpenStack working normal even without Tricircle?
>
> 5.  Is the API request forwarded by Tricircle includes the correct
> request content?
>
> 6.  …
>
>
>
> You can carry the map before you try to fix the issue. And break down a
> big system into smaller part, and make sure which part works fine, which
> not in order.
>
>
>
> From the information you provided, can’t make judgment the error is
> occurred at Tricircle services, or bottom pod, or which pod. Don’t know
> which step the error occurred. And don’t know the request information, how
> the requested will be routed and processed, a lot of context needed to
> diagnose an error.
>
>
>
> Best Regards
>
> Chaoyi Huang ( Joe Huang )
>
>
>
> *From:* Yipei Niu [mailto:newy...@gmail.com]
> *Sent:* Wednesday, March 23, 2016 10:36 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Cc:* joehuang; Zhiyuan Cai
> *Subject:* [tricircle] playing tricircle with two node configuration
>
>
>
> Hi, Joe and Zhiyuan,
>
>
>
> I have already finished installing devstack in two nodes with tricircle. I
> encounter some errors when testing cross-pod L3 networking with DevStack. I
> followed the README.md in github, every thing goes well until I boot
> virtual machines with the following command:
>
>
>
> nova boot --flavor 1 --image 60a8184b-a4be-463d-a8a1-48719edc37a3 --nic
> net-id=76356099-f3bd-40a5-83bd-600b78b671eb --availability-zone az1 vm1
>
>
>
> The info in the terminal is as follows:
>
> Your request was processed by a Nova API which does not support
> microversions (X-OpenStack-Nova-API-Version header is missing from
> response). Warning: Response may be incorrect.
>
> Your request was processed by a Nova API which does not support
> microversions (X-OpenStack-Nova-API-Version header is missing from
> response). Warning: Response may be incorrect.
>
> Your request was processed by a Nova API which does not support
> microversions (X-OpenStack-Nova-API-Version header is missing from
> response). Warning: Response may be incorrect.
>
> ERROR (ClientException): Unknown Error (HTTP 500)
>
>
>
> I run rejoin-stack.sh and find some error in n-api screen. In n-api.log,
> the error is as follows:
>
> 2016-03-22 19:19:38.248 ^[[01;31mERROR nova.api.openstack.extensions
> [^[[01;36mreq-cf58e7aa-bd7d-483f-aa57-bca5268ce963 ^[[00;36madmin
> admin^[[01;31m] ^[[01;35m^[[01;31mUnexpected exception in API method^[[00m
>
> ^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
> ^[[01;35m^[[00mTraceback (most recent call last):
>
> ^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
> ^[[01;35m^[[00m  File "/opt/stack/nova/nova/api/openstack/extensions.py",
> line 478, in wrapped
>
> ^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
> ^[[01;35m^[[00mreturn f(*args, **kwargs)
>
> ^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
> ^[[01;35m^[[00m  File "/opt/stack/nova/nova/api/validation/__init__.py",
> line 73, in wrapper
>
> ^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
> ^[[01;

[openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-22 Thread Yipei Niu

Hi, Joe and Zhiyuan,

I have already finished installing devstack in two nodes with tricircle. I
encounter some errors when testing cross-pod L3 networking with DevStack. I
followed the README.md in github, every thing goes well until I boot
virtual machines with the following command:

nova boot --flavor 1 --image 60a8184b-a4be-463d-a8a1-48719edc37a3 --nic
net-id=76356099-f3bd-40a5-83bd-600b78b671eb --availability-zone az1 vm1

The info in the terminal is as follows:
Your request was processed by a Nova API which does not support
microversions (X-OpenStack-Nova-API-Version header is missing from
response). Warning: Response may be incorrect.
Your request was processed by a Nova API which does not support
microversions (X-OpenStack-Nova-API-Version header is missing from
response). Warning: Response may be incorrect.
Your request was processed by a Nova API which does not support
microversions (X-OpenStack-Nova-API-Version header is missing from
response). Warning: Response may be incorrect.
ERROR (ClientException): Unknown Error (HTTP 500)

I run rejoin-stack.sh and find some error in n-api screen. In n-api.log,
the error is as follows:
2016-03-22 19:19:38.248 ^[[01;31mERROR nova.api.openstack.extensions
[^[[01;36mreq-cf58e7aa-bd7d-483f-aa57-bca5268ce963 ^[[00;36madmin
admin^[[01;31m] ^[[01;35m^[[01;31mUnexpected exception in API method^[[00m
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mTraceback (most recent call last):
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/api/openstack/extensions.py",
line 478, in wrapped
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn f(*args, **kwargs)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/api/validation/__init__.py",
line 73, in wrapper
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn func(*args, **kwargs)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/api/validation/__init__.py",
line 73, in wrapper
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn func(*args, **kwargs)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File
"/opt/stack/nova/nova/api/openstack/compute/servers.py", line 604, in create
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m**create_kwargs)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/hooks.py", line 149, in inner
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mrv = f(*args, **kwargs)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/compute/api.py", line 1504, in
create
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mcheck_server_group_quota=check_server_group_quota)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/compute/api.py", line 1097, in
_create_instance
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mauto_disk_config, reservation_id, max_count)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/compute/api.py", line 871, in
_validate_and_build_base_options
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mpci_request_info, requested_networks)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/network/neutronv2/api.py", line
981, in create_pci_requests_for_sriov_ports
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mneutron = get_client(context, admin=True)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/network/neutronv2/api.py", line
149, in get_client
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m_ADMIN_AUTH = _load_auth_plugin(CONF)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m  File "/opt/stack/nova/nova/network/neutronv2/api.py", line
125, in _load_auth_plugin
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mraise neutron_client_exc.Unauthorized(message=err_msg)
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mUnauthorized: Unknown auth plugin: None
^[[01;31m2016-03-22 19:19:38.248 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m
2016-03-22 20:04:19.992 ^[[00;36mINFO nova.api.openstack.wsgi
[^[[01;36mreq-ed35efe8-5dc0-40b0-bb2b-c1a73618aa50 ^[[00;36madmin

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-27 Thread Yipei Niu

y", line
302, in _create
_resp, body = self.api.client.post(url, body=body)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py", line
451, in post
return self._cs_request(url, 'POST', **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py", line
426, in _cs_request
resp, body = self._time_request(url, method, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py", line
399, in _time_request
resp, body = self.request(url, method, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py", line
393, in request
raise exceptions.from_response(resp, body, url, method)
*BadRequest: Unknown argument: port (HTTP 400)* (Request-ID:
req-d6719f21-ee97-49ed-a058-a303b16abcf1)
^[[00m
2016-03-28 11:49:44.814 ^[[00;36mINFO eventlet.wsgi.server
[^[[01;36mreq-414f74df-019a-425c-8d49-a081706b2bd4 ^[[00;36madmin
admin^[[00;36m] ^[[01;35m^[[00;36m192.168.56.101 "POST
/v2.1/29a524d386754a94850277afea1e569f/servers HTTP/1.1" status: 500  len:
139 time: 2.1919141^[[00m

Best regards,
Yipei

On Wed, Mar 23, 2016 at 1:19 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote:

> On Wed, Mar 23, 2016 at 12:41 PM, joehuang <joehu...@huawei.com> wrote:
> > Hi, Yipei,
> >
> >
> >
> > When you play Tricircle, it’s important to know that Tricircle is the
> > OpenStack API gateway to other OpenStack instances. In the Readme, Pod1,
> > Pod2 are two OpenStack instances, before trying Tricircle, you can make
> sure
> > the environment is normal or not by executeing command separately on
> Pod1,
> > Pod2, just  Nova –os-region-name Pod1, or Nova –os-region-name Pod2, in
> > fact, because Pod1,Pod2 are two normal OpenStack instances, any command
> to
> > Pod1,Pod2 should be successful.  Otherwise that means there are some
> issue
> > in the installation of the environment itself. Only when each bottom
> > OpenStack can work correctly, then you can even manually add Tricircle,
> or
> > through the scripts in the github to install Tircircle automaticly, as
> the
> > API gateway to Pod1 and Pod2, just like you add one load balancer before
> > your multiple web servers.
>
> Yeah, above explanation is really essential for the tricircle.
>
> >
> >
> >
> > After the Tricircle was added, then the API will flow from Tricircle
> > services like Nova-APIGW/Cinder-APIGW/Neutron API to the bottom Pod1,
> Pod2.
> >
> >
> >
> > So if you use Nova boot, and some error happened, you can ask question:
> >
> > 1.  Is the command sent to the Tricircle Nova-APIGW?
> >
> > 2.  What’ll will do for the Nova-APIGW for the next step?
> >
> > 3.  Is the API request forwarded by Tricircle correctly to the proper
> > bottom OpenStack?
> >
> > 4.  Is the bottom OpenStack working normal even without Tricircle?
> >
> > 5.  Is the API request forwarded by Tricircle includes the correct
> > request content?
> >
> > 6.  …
> >
> >
> >
> > You can carry the map before you try to fix the issue. And break down a
> big
> > system into smaller part, and make sure which part works fine, which not
> in
> > order.
> >
> >
> >
> > From the information you provided, can’t make judgment the error is
> occurred
> > at Tricircle services, or bottom pod, or which pod. Don’t know which step
> > the error occurred. And don’t know the request information, how the
> > requested will be routed and processed, a lot of context needed to
> diagnose
> > an error.
> >
> >
> >
> > Best Regards
> >
> > Chaoyi Huang ( Joe Huang )
> >
> >
> >
> > From: Yipei Niu [mailto:newy...@gmail.com]
> > Sent: Wednesday, March 23, 2016 10:36 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Cc: joehuang; Zhiyuan Cai
> > Subject: [tricircle] playing tricircle with two node configuration
> >
> >
> >
> > Hi, Joe and Zhiyuan,
> >
> >
> >
> > I have already finished installing devstack in two nodes with tricircle.
> I
> > encounter some errors when testing cross-pod L3 networking with
> DevStack. I
> > followed the README.md in github, every thing goes well until I boot
> virtual
> > machines with the following command:
> >
> >
> >
> > nova boot --flavor 1 --image 60a8184b-a4be-463d-a8a1-48719edc37a3 --nic
> > net-id=76356099-f3bd-40a5-83bd-600b78b671eb --availability-zone az1 vm1
> >
> >
> >
> > The info in the terminal is as follows:
> >

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-29 Thread Yipei Niu

Hi, all,

I follow the advice given by Zhiyuan, and it works. For the port error,
somebody removes the line "iniset $NOVA_CONF DEFAULT network_api_class
nova.network.neutronv2.api.API" in lib/neutron-legacy. For the unknown
auth_plugin error in the first mail, somebody changes the auth_plugin to
auth_type in lib/neutron-legacy, but the loader still searches auth_plugin
for configuration in nova/network/neutronv2/api.py, which therefore leads
to none in auth_plugin option. I change the files to their original
versions, respectively. Now I have booted two VMs successfully. Is the
solution OK?

BTW, I have some trouble with creating router and I am trying to fix it.

Best regards,
Yipei

On Tue, Mar 29, 2016 at 2:25 PM, joehuang <joehu...@huawei.com> wrote:

> I think we can do it later. It's still a little bit strange that if
> nova-network in the Local.conf is disabled at first before devstack
> installation, the devstack should use Neutron instead, not sure how clean
> Yipei's environment is.
>
> I suggest Yipei to use clean virtual machines running in virtualbox, and
> follow the readme[1] and pengfei's experience[2] to install Tricircle.
>
> [1] https://github.com/openstack/tricircle/blob/master/README.md
> [2] http://shipengfei92.cn/play_tricircle_with_virtualbox
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Tuesday, March 29, 2016 10:48 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Yipei Niu
> Subject: Re: [openstack-dev] [tricircle] playing tricircle with two node
> configuration
>
> Sorry for interruption.
>
> >> I followed the README.md in github, every thing goes well until I
> >> boot virtual machines with the following command
>
> Point here is that even Yipei was following READM provided by us, setting
> up the tricircle was failed. [1] It may be required to review it, I think.
>
> [1] https://github.com/openstack/tricircle/blob/master/README.md
>
> Cheers,
> Shinobu
>
>
> On Tue, Mar 29, 2016 at 11:21 AM, Vega Cai <luckyveg...@gmail.com> wrote:
> > Hi Yipei,
> >
> > If you want to use neutron, you need to set "nova_api_class" to
> > "nova.network.neutronv2.api.API", "nova.network.api.API" is for nova
> > network.
> >
> > Related code:
> > https://github.com/openstack/nova/blob/master/nova/network/__init__.py
> > #L47
> >
> > Simply search "Unknown argument: port" which is the error showed in
> > the log in the nova code tree then you can find the above code.
> >
> > Also, if all the services are running but you want to change some of
> > the configuration options, you can just modify the configuration files
> > then restart the services, so you can quickly check if your
> > modification works without restarting devstack.
> >
> > BR
> > Zhiyuan
> >
> > On 29 March 2016 at 08:56, Yipei Niu <newy...@gmail.com> wrote:
> >>
> >> Hi, all,
> >>
> >> I checked nova.conf and local.conf both.
> >>
> >> In nova.conf, the option "nova_api_class" is missing while "use_neutron"
> >> is set as True. I modify the lib/nova so that the devstack can write
> >> "nova_api_class=nova.network.api.API" to nova.conf [1]. However,
> >> after installing devstack with tricircle, the same error still happens
> as before.
> >>
> >> In local.conf, n-net is disabled, which is the same as the sample
> >> file of tricircle.
> >>
> >> [1] http://docs.openstack.org/developer/nova/sample_config.html
> >>
> >> Best regards,
> >> Yipei
> >>
> >> On Mon, Mar 28, 2016 at 4:46 PM, Shinobu Kinjo <shinobu...@gmail.com>
> >> wrote:
> >>>
> >>> FYI:
> >>> This is the reason is that there is still n-net. [1]
> >>>
> >>> [1]
> >>> http://docs.openstack.org/openstack-ops/content/nova-network-depreca
> >>> tion.html
> >>>
> >>> Cheers,
> >>> S
> >>>
> >>> On Mon, Mar 28, 2016 at 5:08 PM, joehuang <joehu...@huawei.com> wrote:
> >>> > Hi,
> >>> >
> >>> >
> >>> >
> >>> > Agree, it’s quite important not to use Nova-network in devstack.
> >>> > In devstack local.conf, make sure the Neutron service is enabled
> >>> > and Nova-network is disabled.
> >>> >
> >>> >
> >>> >
> >>> > # Use

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

2016-03-29 Thread Yipei Niu

api.v2.resource
^[[01;35m^[[00mreturn self.post(self.networks_path, body=body)
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
271, in post
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00mheaders=headers, params=params)
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
206, in do_request
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00mself._handle_fault_response(status_code, replybody)
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
182, in _handle_fault_response
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00mexception_handler_v20(status_code, des_error_body)
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00m  File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
69, in exception_handler_v20
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00mstatus_code=status_code)
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00mBadRequest: Invalid input for operation: 'None' is not an
integer.
^[[01;31m2016-03-29 15:41:04.122 TRACE neutron.api.v2.resource
^[[01;35m^[[00m
2016-03-29 15:41:04.137 ^[[00;36mINFO neutron.wsgi
[^[[01;36mreq-0180a3f5-e34c-4d4c-bd39-3c0c714b02de ^[[00;36madmin
685f8f37363f4467bead5a375e855ccd^[[00;36m] ^[[01;35m^[[00;36m192.168.56.101
- - [29/Mar/2016 15:41:04] "PUT
/v2.0/routers/999a46c9-8055-4514-82d6-81945f095bd6/add_router_interface.json
HTTP/1.1" 500 383 1.574475^[[00

I search solutions with google, but get little information. Sorry to
trouble you guys.

Best regards,
Yipei

On Tue, Mar 29, 2016 at 4:36 PM, Vega Cai <luckyveg...@gmail.com> wrote:

> Hi Yipei,
>
> Glad to hear that you can successfully boot VMs. So the problems are
> caused by the incompatibility of the nova, neutron and devstack code trees
> in your environment. Yeah, what you did is what I always do. When devstack
> fails to start or has some troubles, find the reason then modify the
> scripts.
>
> I am updating the code trees in my environment to the newest version to
> see if tricircle can be correctly deployed. I will send out the result
> later.
>
> BR
> Zhiyuan
>
>
> On 29 March 2016 at 16:10, Yipei Niu <newy...@gmail.com> wrote:
>
>> Hi, all,
>>
>> I follow the advice given by Zhiyuan, and it works. For the port error,
>> somebody removes the line "iniset $NOVA_CONF DEFAULT network_api_class
>> nova.network.neutronv2.api.API" in lib/neutron-legacy. For the unknown
>> auth_plugin error in the first mail, somebody changes the auth_plugin to
>> auth_type in lib/neutron-legacy, but the loader still searches auth_plugin
>> for configuration in nova/network/neutronv2/api.py, which therefore leads
>> to none in auth_plugin option. I change the files to their original
>> versions, respectively. Now I have booted two VMs successfully. Is the
>> solution OK?
>>
>> BTW, I have some trouble with creating router and I am trying to fix it.
>>
>> Best regards,
>> Yipei
>>
>> On Tue, Mar 29, 2016 at 2:25 PM, joehuang <joehu...@huawei.com> wrote:
>>
>>> I think we can do it later. It's still a little bit strange that if
>>> nova-network in the Local.conf is disabled at first before devstack
>>> installation, the devstack should use Neutron instead, not sure how clean
>>> Yipei's environment is.
>>>
>>> I suggest Yipei to use clean virtual machines running in virtualbox, and
>>> follow the readme[1] and pengfei's experience[2] to install Tricircle.
>>>
>>> [1] https://github.com/openstack/tricircle/blob/master/README.md
>>> [2] http://shipengfei92.cn/play_tricircle_with_virtualbox
>>>
>>> Best Regards
>>> Chaoyi Huang ( Joe Huang )
>>>
>>>
>>> -Original Message-
>>> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
>>> Sent: Tuesday, March 29, 2016 10:48 AM
>>> To: OpenStack Development Mailing List (not for usage questions)
>>> Cc: Yipei Niu
>>> Subject: Re: [openstack-dev] [tricircle] playing tricircle with two node
>>> configuration
>>>
>>> Sorry for interruption.
>>>
>>> >> I followed the README.md in github, every thing goes well until I
>>> >> boot virtual machines with the followi

Re: [openstack-dev] [tricircle] Launch work group for cross-pod L2 networking feature

2016-05-23 Thread Yipei Niu

Hi, all,

Since I have to attend the dissertation defense of my master degree on
Wednesday morning, I cannot attend the group meeting. Sorry about that. If
it is inconvenient to reschedule the meeting, I will keep online in
#openstack-tricircle so as to receive the meeting log.

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]Proposing Shinobu Kinjo for Tricircle core reviewer

2016-05-04 Thread Yipei Niu

+1. He is experienced and helps me a lot. He is qualified to be a core
reviewer.


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

[openstack-dev] [tricircle] About the dynamic pod binding

2016-05-05 Thread Yipei Niu

Hi, all,

For dynamic pod binding, I have some questions.

1. Do we need to store historical pod binding records in the pod binding
table? Why?
2. How do we manage pod binding filters, store them in DB?
3. How is Tricircle aware of what type of resource wanted by tenants? For
example, a tenant wants to boot VMs for CAD modelling with corresponding
flavor. But in current code, the flavorRef is not get involved in function
get_pod_by_az_tenant, when querying pod bindings. So do we need to modify
the pod binding table to add such a column?

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] About the dynamic pod binding

2016-05-05 Thread Yipei Niu

Got it with thanks.

Best regards,
Yipei

On Fri, May 6, 2016 at 9:48 AM, joehuang <joehu...@huawei.com> wrote:

> Hi, Yipei,
>
> Shinobu is correct, this should be taken into consideration in the design
> of dynamic pod binding.
>
> How to schedule pod, you can refer to host-aggregate scheduling with
> flavor, the difference is that the scheduling granularity is on pod level.
> By the tag in flavor extra-spec and volume type extrac_spec , tricircle can
> be aware of which type of resource the tenant wants to provision.
>
> For example:
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Configuration_Reference_Guide/host-aggregates.html
>
> So in
> https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit,
> one field called resource_affinity_tag is proposed to be added into the pod
> table, it could be used for scheduling purpose. But this is only one
> proposal, you may have better idea to do that, after the spec is reviewed
> and approved, the doc can be update to reflect the new idea.
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Friday, May 06, 2016 8:06 AM
> To: Yipei Niu
> Cc: OpenStack Development Mailing List (not for usage questions);
> joehuang; Zhiyuan Cai; 金城 忍
> Subject: Re: [tricircle] About the dynamic pod binding
>
> Hi Yipei,
>
> On Thu, May 5, 2016 at 9:54 PM, Yipei Niu <newy...@gmail.com> wrote:
> > Hi, all,
> >
> > For dynamic pod binding, I have some questions.
> >
> [snip]
> > 3. How is Tricircle aware of what type of resource wanted by tenants?
> > For example, a tenant wants to boot VMs for CAD modelling with
> > corresponding flavor. But in current code, the flavorRef is not get
> > involved in function get_pod_by_az_tenant, when querying pod bindings.
> > So do we need to modify the pod binding table to add such a column?
>
> Working through code bases, probably you are talking about future
> implementation, I guess.
>
> Cheers,
> Shinobu
>
> >
> > Best regards,
> > Yipei
>
>
>
> --
> Email:
> shin...@linux.com
> shin...@redhat.com
>
__
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] About registering and loading a plugin

2016-06-28 Thread Yipei Niu

Hi all,

Thanks a lot for your valuable advice. I have already succeed in
registering and loading a self-defined plugin. The entry_point is generated
by executing setup.py, and found in .egg-info/entry_points.txt, which is
different from using setup.cfg in https://review.openstack.org/#/c/331638/.

Moreover, I tried to load drivers by line "cfg.CONF.nyp.plugins.simple",
the console prompts oslo_config.cfg.NoSuchOptError: no such option in group
DEFAULT: nyp. The setup.cfg is defined as follows.

[entry_points]
nyp.plugins.formmater =
simple = nyp.plugins.simple:SimpleFormatter
plain = nyp.plugins.simple:SimpleFormatter
field = nyp.plugins.field:FieldList

How to solve the problem?

Best regards,
Yipei

On Tue, Jun 28, 2016 at 10:35 AM, Vega Cai <luckyveg...@gmail.com> wrote:

> Hi Yipei,
>
> You can also refer to my network type driver implementation:
>
> https://review.openstack.org/#/c/331638/
>
> Type driver is registered in setup.cfg and loaded by code.
>
> BR
> Zhiyuan
>
> On 27 June 2016 at 21:44, Yipei Niu <newy...@gmail.com> wrote:
>
>> Dear all,
>>
>> Recently, I learn to name a plugin based on the doc
>> http://docs.openstack.org/developer/stevedore/tutorial/naming.html#. I
>> define a new entry_point for the plugin, then it fails. The console prompts
>> "stevedore.exception.NoMatches: No 'net.nyp.formatter' driver found,
>> looking for 'simple'". After setting a new entry_point with setuptools, why
>> stevedore cannot find the driver based on the entry_point?
>>
>> 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

[openstack-dev] [tricircle] About registering and loading a plugin

2016-06-27 Thread Yipei Niu

Dear all,

Recently, I learn to name a plugin based on the doc
http://docs.openstack.org/developer/stevedore/tutorial/naming.html#. I
define a new entry_point for the plugin, then it fails. The console prompts
"stevedore.exception.NoMatches: No 'net.nyp.formatter' driver found,
looking for 'simple'". After setting a new entry_point with setuptools, why
stevedore cannot find the driver based on the entry_point?

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] your proposal for the name of networking and gateway sub-projects

2016-09-04 Thread Yipei Niu

Triangel +1

Angel is a spiritual being believed to act as an attendant, agent, or
messenger of God, which is very similar to our project.

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] your proposal for the name of networking and gateway sub-projects

2016-09-04 Thread Yipei Niu

Trifennel +1

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] [neutron-lbaas][octavia] About running Neutron LBaaS

2016-11-22 Thread Yipei Niu

Hi, Micheal,

Thanks a lot for your help. I am trying your solution.

Best regards,
Yipei

On Sun, Nov 20, 2016 at 1:46 PM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Micheal,
>
> Thanks a lot for your comments.
>
> Please find the errors of o-cw.log in link http://paste.openstack.
> org/show/589806/ <http://paste.openstack.org/show/589669/>. Hope it will
> help.
>
> About the lb-mgmt-net, I just follow the guide of running LBaaS. If I
> create a ordinary subnet with neutron for the two VMs, will it prevent the
> issue you mentioned happening?
>
> 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

[openstack-dev] [tricircle] About playing Neutron LBaaS

2016-11-17 Thread Yipei Niu

Hi, all,

Recently I try to configure and play Neutron LBaaS in one OpenStack
instance and have some trouble when creating a load balancer.

I install devstack with neutron networking as well as LBaaS in one VM. The
detailed configuration of local.conf is pasted in the link
http://paste.openstack.org/show/589669/.

Then I boot two VMs in the OpenStack instance, which can be reached via
ping command from the host VM. The detailed information of the two VMs are
listed in the following table.

+--+-+++-+--+
| ID   | Name| Status | Task State |
Power State | Networks |
+--+-+++-+--+
| 4cf7527b-05cc-49b7-84f9-3cc0f061be4f | server1 | ACTIVE | -  |
Running | lb-mgmt-net=192.168.0.6  |
| bc7384a0-62aa-4987-89b6-8b98a6c467a9 | server2 | ACTIVE | -  |
Running | lb-mgmt-net=192.168.0.12 |
+--+-+++-+--+

After building up the environment, I try to create a load balancer based on
the guide in https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun. When
executing the command "neutron lbaas-loadbalancer-create --name lb1
private-subnet", the state of the load balancer remains "PENDING_CREATE"
and finally becomes "ERROR". I checked q-agt.log and q-svc.log, the
detailed info is pasted in http://paste.openstack.org/show/589676/.

Look forward to your valuable comments. Thanks a lot!

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] [neutron-lbaas][octavia] About running Neutron LBaaS

2016-11-19 Thread Yipei Niu

Hi, Micheal,

Thanks a lot for your comments.

Please find the errors of o-cw.log in link http://paste.openstack.org/
show/589806/ . Hope it will help.

About the lb-mgmt-net, I just follow the guide of running LBaaS. If I
create a ordinary subnet with neutron for the two VMs, will it prevent the
issue you mentioned happening?

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

[openstack-dev] [devstack] About installing devstack on Ubuntu

2016-12-05 Thread Yipei Niu

Hi, All,

I failed installing devstack on Ubuntu. The detailed info of local.conf and
error is pasted in http://paste.openstack.org/show/591493/.

BTW, python2.7 is installed in Ubuntu, and Python.h can be found under
/usr/include/python2.7.

stack@stack-VirtualBox:~$ locate Python.h

/usr/include/python2.7/Python.h


Look forward to your comments. Thanks.

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

[openstack-dev] [devstack][neutron-lbaas][octavia] About installing Devstack on Ubuntu

2016-12-05 Thread Yipei Niu

Hi, All,

I failed installing devstack on Ubuntu. The detailed info of local.conf and
error is pasted in http://paste.openstack.org/show/591493/.

BTW, python2.7 is installed in Ubuntu, and Python.h can be found under
/usr/include/python2.7.

stack@stack-VirtualBox:~$ locate Python.h

/usr/include/python2.7/Python.h


However, after I comment the configuration related to Neutron-LBaaS and
Octavia in local.conf, it successes.

Is it a bug? How to fix it? Look forward to your comments. Thanks.

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

[openstack-dev] [neutron-lbaas][octavia] Error when creating load balancer

2016-12-27 Thread Yipei Niu

Hi, All,

I failed creating a load balancer on a subnet. The detailed info of
o-cw.log is pasted in the link http://paste.openstack.org/show/593492/.

Look forward to your valuable comments. Thank you.

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]Nominating Victor Morales as Tricircle Core

2017-02-28 Thread Yipei Niu

+1.
__
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] mascot for the Tricircle

2017-04-24 Thread Yipei Niu

+1.

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] [octavia] fail to plug vip to amphora

2017-06-28 Thread Yipei Niu

Hi, Michael,

Thanks for your help. I have already created a load balancer successfully,
but failed creating a listener. The detailed errors of amphora-agent and
syslog in the amphora are as follows.

In amphora-agent.log:

[2017-06-28 08:54:12 +] [1209] [INFO] Starting gunicorn 19.7.0
[2017-06-28 08:54:13 +] [1209] [DEBUG] Arbiter booted
[2017-06-28 08:54:13 +] [1209] [INFO] Listening at: http://[::]:9443
(1209)
[2017-06-28 08:54:13 +] [1209] [INFO] Using worker: sync
[2017-06-28 08:54:13 +] [1209] [DEBUG] 1 workers
[2017-06-28 08:54:13 +] [1816] [INFO] Booting worker with pid: 1816
[2017-06-28 08:54:15 +] [1816] [DEBUG] POST /0.5/plug/vip/10.0.1.8
:::192.168.0.12 - - [28/Jun/2017:08:54:59 +] "POST /0.5/plug/vip/
10.0.1.8 HTTP/1.1" 202 78 "-" "Octavia HaProxy Rest Client/0.5 (
https://wiki.openstack.org/wiki/Octavia)"
[2017-06-28 08:59:18 +] [1816] [DEBUG] PUT
/0.5/listeners/9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy
:::192.168.0.12 - - [28/Jun/2017:08:59:19 +] "PUT
/0.5/listeners/9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy
HTTP/1.1" 400 414 "-" "Octavia HaProxy Rest Client/0.5 (
https://wiki.openstack.org/wiki/Octavia)"

In syslog:

Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
#
Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
-BEGIN SSH HOST KEY FINGERPRINTS-
Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 1024
SHA256:qDQcKq2Je/CzlpPndccMf0aR0u/KPJEEIAl4RraAgVc
root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (DSA)
Jun 28 08:57:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 256
SHA256:n+5tCCdJwASMaD/kJ6fm0kVNvXDh4aO0si2Uls4MXkI
root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (ECDSA)
Jun 28 08:57:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 256
SHA256:7RWMBOW+QKzeolI6BDSpav9dVZuon58weIQJ9/peVxE
root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (ED25519)
Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 2048
SHA256:9z+EcAAUyTENKJRctKCzPslK6Yf4c7s9R8sEflDITIU
root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (RSA)
Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: -END
SSH HOST KEY FINGERPRINTS-
Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
#
Jun 28 08:57:17 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
cloud-init[2092]: Cloud-init v. 0.7.9 running 'modules:final' at Wed, 28
Jun 2017 08:57:03 +. Up 713.82 seconds.
Jun 28 08:57:17 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
cloud-init[2092]: Cloud-init v. 0.7.9 finished at Wed, 28 Jun 2017 08:57:16
+. Datasource DataSourceConfigDrive [net,ver=2][source=/dev/sr0].  Up
727.30 seconds
Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
Started Execute cloud user/final scripts.
Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
Reached target Cloud-init target.
Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
Startup finished in 52.054s (kernel) + 11min 17.647s (userspace) = 12min
9.702s.
Jun 28 08:59:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
amphora-agent[1209]: 2017-06-28 08:59:19.243 1816 ERROR
octavia.amphorae.backends.agent.api_server.listener [-] Failed to verify
haproxy file: Command '['haproxy', '-c', '-L', 'NK20KVuD6oi5NrRP7KOVflM
3MsQ', '-f',
'/var/lib/octavia/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy.cfg.new']'
returned non-zero exit status 1
Jun 28 09:00:11 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
Starting Cleanup of Temporary Directories...
Jun 28 09:00:12 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
systemd-tmpfiles[3040]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line
for path "/var/log", ignoring.
Jun 28 09:00:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
Started Cleanup of Temporary Directories.

Look forward to your valuable comments.

Best regards,
Yipei

On Tue, Jun 27, 2017 at 2:33 PM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Micheal,
>
> Thanks a lot for your help, but I still have one question.
>
> In Octavia, once the controller worker fails plugging VIP to the amphora,
> the amphora is deleted immediately, making it impossible to trace the
> error. How to prevent Octavia from stopping and deleting the amphora?
>
> Best regards,
> Yipei
>
> On Mon, Jun 26, 2017 at 11:21 AM, Yipei Niu <newy...@gmail.com> wrote:
>
>> Hi, all,
>>
>> I am trying to create a load balancer in octavia. The amphora can be
>> booted successfully, and can be reached via icmp. However, octavia fails to
>> plug vip to the amphora through the amphora client api and returns 500
>> status code, causing some errors as f

Re: [openstack-dev] [octavia] fail to plug vip to amphora

2017-06-28 Thread Yipei Niu

Hi, Ganpat,

Thanks a lot for your comments. I do not really understand your solution.
Do you mean I need to create a dummy file and verify it in the amphora?

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]poll for new weekly meeting time

2017-04-25 Thread Yipei Niu

Wed  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM +1.

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

[openstack-dev] [octavia] fail to plug vip to amphora

2017-06-25 Thread Yipei Niu

Hi, all,

I am trying to create a load balancer in octavia. The amphora can be booted
successfully, and can be reached via icmp. However, octavia fails to plug
vip to the amphora through the amphora client api and returns 500 status
code, causing some errors as follows.

   |__Flow
'octavia-create-loadbalancer-flow': InternalServerError: Internal Server
Error
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker Traceback (most recent call
last):
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/executor.py",
line 53, in _execute_task
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker result =
task.execute(**arguments)
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py",
line 240, in execute
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker amphorae_network_config)
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py",
line 219, in execute
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker amphora, loadbalancer,
amphorae_network_config)
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py",
line 137, in post_vip_plug
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker net_info)
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py",
line 378, in plug_vip
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker return
exc.check_exception(r)
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker   File
"/opt/stack/octavia/octavia/amphorae/drivers/haproxy/exceptions.py", line
32, in check_exception
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker raise
responses[status_code]()
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker InternalServerError: Internal
Server Error
2017-06-21 09:49:35.864 25411 ERROR
octavia.controller.worker.controller_worker

To fix the problem, I log in the amphora and find that there is one http
server process is listening on port 9443, so I think the amphora api
services is active. But do not know how to further investigate what error
happens inside the amphora api service and solve it? Look forward to your
valuable comments.

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] [octavia] fail to plug vip to amphora

2017-06-27 Thread Yipei Niu

Hi, Micheal,

Thanks a lot for your help, but I still have one question.

In Octavia, once the controller worker fails plugging VIP to the amphora,
the amphora is deleted immediately, making it impossible to trace the
error. How to prevent Octavia from stopping and deleting the amphora?

Best regards,
Yipei

On Mon, Jun 26, 2017 at 11:21 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, all,
>
> I am trying to create a load balancer in octavia. The amphora can be
> booted successfully, and can be reached via icmp. However, octavia fails to
> plug vip to the amphora through the amphora client api and returns 500
> status code, causing some errors as follows.
>
>|__Flow
> 'octavia-create-loadbalancer-flow': InternalServerError: Internal Server
> Error
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> Traceback (most recent call last):
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File "/usr/local/lib/python2.7/dist-packages/taskflow/
> engines/action_engine/executor.py", line 53, in _execute_task
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> result = task.execute(**arguments)
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File 
> "/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py",
> line 240, in execute
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> amphorae_network_config)
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File 
> "/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py",
> line 219, in execute
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> amphora, loadbalancer, amphorae_network_config)
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File 
> "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py",
> line 137, in post_vip_plug
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> net_info)
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File 
> "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py",
> line 378, in plug_vip
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> return exc.check_exception(r)
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
>   File "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/exceptions.py",
> line 32, in check_exception
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> raise responses[status_code]()
> 2017-06-21 09:49:35.864 25411 ERROR 
> octavia.controller.worker.controller_worker
> InternalServerError: Internal Server Error
> 2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.
> controller_worker
>
> To fix the problem, I log in the amphora and find that there is one http
> server process is listening on port 9443, so I think the amphora api
> services is active. But do not know how to further investigate what error
> happens inside the amphora api service and solve it? Look forward to your
> valuable comments.
>
> 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] [octavia] haproxy fails to receive datagram

2017-10-08 Thread Yipei Niu

Hi, Michael,

I once installed a successful environment, so I move the amphora image of the 
environment to my latest environment which doesn’t work. I create a load 
balancer in the latest environment using the old amphora image, and it works.

So I think there is some problem with the amphora image of my latest 
environment. The detailed info of my amphora image is as follows.

stack@VM-IP10:~$ glance image-show 3bc4a09e-86b5-4e54-b468-b3d9c7ac8607
+--+--+
| Property | Value|
+--+--+
| checksum | 4bd41781226068fe91bf181efd2df8c3 |
| container_format | bare |
| created_at   | 2017-09-28T02:50:48Z |
| disk_format  | qcow2|
| id   | 3bc4a09e-86b5-4e54-b468-b3d9c7ac8607 |
| min_disk | 0|
| min_ram  | 0|
| name | amphora-x64-haproxy  |
| owner| 01fd6fdee6ba436abe1a4bfe5defeea2 |
| protected| False|
| size | 678293504|
| status   | active   |
| tags | ["amphora"]  |
| updated_at   | 2017-09-28T02:51:13Z |
| virtual_size | None |
| visibility   | public   |
+--+———+

Is the checksum the same to yours?

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] [octavia] haproxy fails to receive datagram

2017-10-08 Thread Yipei Niu

Hi, Michael,

I checked neutron_lbaas.conf, the service provider is set as 
“LOADBALANCERV2:Octavia:neutron_lbaas.drivers.octavia.driver.OctaviaDriver:default”.

Further, I installed a new environment in a new VM today, it still doesn’t work.

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] [octavia] haproxy fails to receive datagram

2017-09-26 Thread Yipei Niu

Hi, Michael,

The instructions are listed as follows.

First, create a net1.
$ neutron net-create net1
$ neutron subnet-create net1 10.0.1.0/24 --name subnet1

Second, boot two vms in net1
$ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm1
$ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm2

Third, logon to the two vms, respectively. Here take vm1 as an example.
$ MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print
$1}')
$ while true; do echo -e "HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP" | sudo
nc -l -p 80 ; done&

Fourth, exit vms and update the default security group shared by the vms by
adding a rule of allowing traffic to port 80.
$ neutron security-group-rule-create --direction ingress --protocol tcp
--port-range-min 80 --port-range-max 80 --remote-ip-refix 0.0.0.0/0
$default_security_group
Note: make sure "sudo ip netns exec $qdhcp-net1_id curl -v $vm_ip" works.
In other words, make sure the vms can accept HTTP requests and return its
IP, respectively.

Fifth, create a lb, a listener, and a pool. Then add the two vms to the
pool as members.
$ neutron lbaas-loadbalancer-create --name lb1 subnet1
$ neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
--protocol-port 80 --name listener1
$ neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1
--protocol HTTP --name pool1
$ neutron baas-member-create --subnet subnet1 --address $vm1_ip
--protocol-port 80 pool1
$ neutron baas-member-create --subnet subnet1 --address $vm2_ip
--protocol-port 80 pool1

Finally, try "sudo ip netns qdhcp-net1_id curl -v $VIP" to see whether
lbaas works.

Best regards,
Yipei

On Wed, Sep 27, 2017 at 1:30 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> I think the octavia is the latest, since I pull the up-to-date repo of
> octavia manually to my server before installation.
>
> Anyway, I run "sudo ip netns exec amphora-haproxy ip route show table 1"
> in the amphora, and find that the route table exists. The info is listed as
> follows.
>
> default via 10.0.1.1 dev eth1 onlink
>
> I think it may not be the source.
>
> 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

[openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-25 Thread Yipei Niu

Hi, all,

I encounter some problems when using Octavia. After installing octavia with
devstack, I create a load balancer named lb1 (VIP: 10.0.1.9, IP of VRRP
port: 10.0.1.3) for a subnet (10.0.1.0/24), then a listener, a pool, and
two members. All the resources are created successfully. The two members
(VMs) reside in the same subnet, whose IP are 10.0.1.6 and 10.0.1.7,
respectively. To simulate a web server in each VM, I run "while true; do
echo -e "HTTP/1.0 200 OK\r\n\r\nWelcome to $VM_IP" | sudo nc -l -p 80;done"
to listen on port 80 and return the VM's IP if the request is accepted. I
run "sudo ip netns exec qdhcp- curl -v $VM_IP" to send requests to VMs,
the "web servers" in VMs work (already added corresponding security rules
to the VMs). Then I tried to run "sudo ip netns exec qdhcp- curl -v
$VIP" to send requests, the VMs do not respond, and finally returns a
timeout error.

The configuration details in local.conf are as follows.

*[[local|localrc]]*

*DATABASE_PASSWORD=password*
*RABBIT_PASSWORD=password*
*SERVICE_PASSWORD=password*
*SERVICE_TOKEN=password*
*ADMIN_PASSWORD=password*

*HOST_IP=192.168.56.9*

*LOGFILE=/opt/stack/logs/stack.sh.log*
*VERBOSE=True*
*LOG_COLOR=True*
*SCREEN_LOGDIR=/opt/stack/logs*

*# Neutron LBaaS*
*enable_plugin neutron-lbaas https://github.com/openstack/neutron-lbaas.git
*
*enable_plugin octavia https://github.com/openstack/octavia.git
*
*ENABLED_SERVICES+=,q-lbaasv2*
*ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api*

*disable_service horizon*
*disable_service tempest*

To investigate the source of the error, I logon to the amphora. The details
of interfaces of amphora_haproxy network namespace are as follows.

*1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1*
*link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00*
*3: eth1:  mtu 1450 qdisc pfifo_fast state
UP group default qlen 1000*
*link/ether fa:16:3e:42:bf:d9 brd ff:ff:ff:ff:ff:ff*
*inet 10.0.1.3/24  brd 10.0.1.255 scope global eth1*
*   valid_lft forever preferred_lft forever*
*inet 10.0.1.9/24  brd 10.0.1.255 scope global
secondary eth1:0*
*   valid_lft forever preferred_lft forever*
*inet6 fe80::f816:3eff:fe42:bfd9/64 scope link*
*   valid_lft forever preferred_lft forever*

So I run "sudo ip netns exec amphora-haproxy tcpdump -i eth1 -nn 'tcp'" to
check whether amphora receive the request. The details are as follows.

*tcpdump: verbose output suppressed, use -v or -vv for full protocol decode*
*listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes*
*^C06:11:49.048973 IP 10.0.1.2.33700 > 10.0.1.9.80: Flags [S], seq
1717936594, win 28200, options [mss 1410,sackOK,TS val 28032309 ecr
0,nop,wscale 7], length 0*
*06:11:50.031976 IP 10.0.1.2.33700 > 10.0.1.9.80: Flags [S], seq
1717936594, win 28200, options [mss 1410,sackOK,TS val 28032559 ecr
0,nop,wscale 7], length 0*
*06:11:52.026565 IP 10.0.1.2.33700 > 10.0.1.9.80: Flags [S], seq
1717936594, win 28200, options [mss 1410,sackOK,TS val 28033060 ecr
0,nop,wscale 7], length 0*
*06:11:56.002577 IP 10.0.1.2.33700 > 10.0.1.9.80: Flags [S], seq
1717936594, win 28200, options [mss 1410,sackOK,TS val 28034062 ecr
0,nop,wscale 7], length 0*
*06:12:03.909721 IP 10.0.1.2.33700 > 10.0.1.9.80: Flags [S], seq
1717936594, win 28200, options [mss 1410,sackOK,TS val 28036064 ecr
0,nop,wscale 7], length 0*

Based on the trace, we can see that amphora do receive the request, but
haproxy does not send handshake datagram to respond. Then, to see whether
haproxy in the amphora listens on the right IP and port, I print
/var/lib/octavia/ec5ee7c5-7474-424f-9f44-71b338cf3e57/haproxy.cfg in the
console and see the following info.

*# Configuration for lb1*
*global*
*daemon*
*user nobody*
*log /dev/log local0*
*log /dev/log local1 notice*
*stats socket
/var/lib/octavia/ec5ee7c5-7474-424f-9f44-71b338cf3e57.sock mode 0666 level
user*

*defaults*
*log global*
*retries 3*
*option redispatch*
*timeout connect 5000*
*timeout client 5*
*timeout server 5*

*frontend ec5ee7c5-7474-424f-9f44-71b338cf3e57*
*option httplog*
*bind 10.0.1.9:80 *
*mode http*
*default_backend 40537c80-979d-49c9-b3ae-8504812c0f42*

*backend 40537c80-979d-49c9-b3ae-8504812c0f42*
*mode http*
*balance roundrobin*
*server 73dc9a1d-1e92-479b-a6f3-8debd0ea17b8 10.0.1.6:80
 weight 1*
*server 4cdca33f-9cde-4ac2-a5bd-550d3e65f0f2 10.0.1.7:80
 weight 1*

Next, I print the info of all the running haproxy process in the console
and copy it below.

*root  2367  0.0  0.0   4228   740 ?Ss   07:14   0:00
/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid*
*haproxy   2370  0.0  0.5  37692  5340 ?S07:14   0:00

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-26 Thread Yipei Niu

Hi, Michael,

I think the octavia is the latest, since I pull the up-to-date repo of
octavia manually to my server before installation.

Anyway, I run "sudo ip netns exec amphora-haproxy ip route show table 1" in
the amphora, and find that the route table exists. The info is listed as
follows.

default via 10.0.1.1 dev eth1 onlink

I think it may not be the source.

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] [octavia] haproxy fails to receive datagram

2017-09-28 Thread Yipei Niu

Hi, Michael,

Thanks a lot. Look forward  to your further test. I try deploying a new
environment, too. Hope it can work well this time.

Best regards,
Yipei

On Wed, Sep 27, 2017 at 10:27 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> The instructions are listed as follows.
>
> First, create a net1.
> $ neutron net-create net1
> $ neutron subnet-create net1 10.0.1.0/24 --name subnet1
>
> Second, boot two vms in net1
> $ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm1
> $ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm2
>
> Third, logon to the two vms, respectively. Here take vm1 as an example.
> $ MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print
> $1}')
> $ while true; do echo -e "HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP" | sudo
> nc -l -p 80 ; done&
>
> Fourth, exit vms and update the default security group shared by the vms
> by adding a rule of allowing traffic to port 80.
> $ neutron security-group-rule-create --direction ingress --protocol tcp
> --port-range-min 80 --port-range-max 80 --remote-ip-refix 0.0.0.0/0
> $default_security_group
> Note: make sure "sudo ip netns exec $qdhcp-net1_id curl -v $vm_ip" works.
> In other words, make sure the vms can accept HTTP requests and return its
> IP, respectively.
>
> Fifth, create a lb, a listener, and a pool. Then add the two vms to the
> pool as members.
> $ neutron lbaas-loadbalancer-create --name lb1 subnet1
> $ neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
> --protocol-port 80 --name listener1
> $ neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener
> listener1 --protocol HTTP --name pool1
> $ neutron baas-member-create --subnet subnet1 --address $vm1_ip
> --protocol-port 80 pool1
> $ neutron baas-member-create --subnet subnet1 --address $vm2_ip
> --protocol-port 80 pool1
>
> Finally, try "sudo ip netns qdhcp-net1_id curl -v $VIP" to see whether
> lbaas works.
>
> Best regards,
> Yipei
>
> On Wed, Sep 27, 2017 at 1:30 AM, Yipei Niu <newy...@gmail.com> wrote:
>
>> Hi, Michael,
>>
>> I think the octavia is the latest, since I pull the up-to-date repo of
>> octavia manually to my server before installation.
>>
>> Anyway, I run "sudo ip netns exec amphora-haproxy ip route show table 1"
>> in the amphora, and find that the route table exists. The info is listed as
>> follows.
>>
>> default via 10.0.1.1 dev eth1 onlink
>>
>> I think it may not be the source.
>>
>> 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] [octavia] haproxy fails to receive datagram

2017-10-09 Thread Yipei Niu

Hi, Adam,

The following details of my older amphora image are as follows.

+--+--+
| Property | Value|
+--+--+
| checksum | aa279b9ae1f265a232266e17ea04065c |
| container_format | bare |
| created_at   | 2017-07-24T10:46:34Z |
| disk_format  | qcow2|
| id   | 5d6d5f69-a4b1-440a-b6bb-10bf945e3f85 |
| min_disk | 0|
| min_ram  | 0|
| name | amphora-x64-haproxy  |
| owner| c4f8c2a8fadc4b7c915f299db95c88a8 |
| protected| False|
| size | 674900480|
| status   | active   |
| tags | ["amphora"]  |
| updated_at   | 2017-07-24T10:47:54Z |
| virtual_size | None |
| visibility   | public   |
+--+--+

It is created on 2017-07-24, while my latest one is created at 2017-09-28.

I installed octavia with devstack, but it doesn't work. I discussed the
issue with Michael, he cannot reproduce the error. Please refer to the
history mails here
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122814.html.
I can console in the amphora and trace the packet is received by my
amphora, but haproxy fails to respond. More details are here
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122587.html.
I think maybe there is something wrong with my latest amphora image, I
hence use an older amphora image in the latest environment, it works. As a
result, the networking are supposed to be fine. What do you think?

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] [octavia] amphora fails to send request to members

2017-11-10 Thread Yipei Niu

Hi, Michael,

Thanks a lot for your reply.

I can make sure that there is no router or multiple dhcp services in my
environment.

As shown in my first mail, the haproxy in the amphora tries to find the
gateway ip 10.0.1.1 that does not exist in the environment.

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy tcpdump -i eth1 -nn
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
^C07:25:24.225614 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq
1637781601, win 28200, options [mss 1410,sackOK,TS val 30692602 ecr
0,nop,wscale 7], length 0
07:25:24.237854 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:25.224801 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:25.228610 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq 1637781601,
win 28200, options [mss 1410,sackOK,TS val 30692853 ecr 0,nop,wscale 7],
length 0
07:25:26.224533 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:27.230911 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:27.250858 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq 1637781601,
win 28200, options [mss 1410,sackOK,TS val 30693359 ecr 0,nop,wscale 7],
length 0
07:25:28.228796 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:29.228697 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:29.290551 ARP, Request who-has 10.0.1.4 tell 10.0.1.2, length 28
07:25:29.290985 ARP, Reply 10.0.1.4 is-at fa:16:3e:be:5a:d5, length 28
07:25:31.251122 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:32.248737 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:33.250309 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28

*So if the subnet is not attached to any router, why does haproxy try to
find the gateway ip that does not exist at all? Maybe that is the reason
why haproxy receives the packet from curl but fail to respond. *

I think the gateway ip (10.0.1.10) confuses you. Actually, in my
environment octavia and tricircle (https://wiki.openstack.org/wiki/Tricircle)
are installed together. Because of the cross-neutron mechanism of
tricircle, the gateway ip of subnet in that region is 10.0.1.10. But I can
make sure that gateway ip (10.0.1.1 or 10.0.1.10) does not exist in the
network, since there is no router at all. This error also happens in my
another environment where octavia is installed alone. The environment is
installed on Oct. 6, and all the repos are the latest at that time.

Best regards,
Yipei


On Thu, Nov 9, 2017 at 2:50 PM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> Based on your mail, the information is as follows.
>
> 1. The version of Octavia I used is Queens, and the latest commit message
> is
> commit 2ab2836d0ebdd0fd5bc32d3adcc44a92557c8c1d
> Author: OpenStack Proposal Bot <openstack-in...@lists.openstack.org>
> Date:   Fri Nov 3 17:58:59 2017 +
>
> Updated from global requirements
>
> Change-Id: I9047e289b8a3c931156da480b3f9f676c54a8358
>
> 2. The info of the amphora and other VMs is as follows.
> +--+
> --+++---
> --+-+
> | ID   | Name
>| Status | Task State | Power State | Networks
>   |
> +--+
> --+++---
> --+-+
> | 33bd02cb-f853-404d-a705-99bc1b04a178 | 
> amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> | ACTIVE | -  | Running | lb-mgmt-net1=192.168.1.4;
> net1=10.0.1.8 |
> | dd046fc9-e2bf-437d-8c51-c397bccc3dc1 | client1
> | ACTIVE | -  | Running | net1=10.0.1.3
>|
> | 50446c75-7cb7-43eb-b057-4b6b89a926bc | client3
> | ACTIVE | -  | Running | net4=10.0.4.3
>|
> +--+
> --+++---
> --+-+
>
> 3. The info of the load balancer is as follows.
> +-++
> | Field   | Value  |
> +-++
> | admin_state_up  | True   |
> | description ||
>

[openstack-dev] [octavia][tricircle] About enabling automatic installation of octavia with tricircle

2017-12-04 Thread Yipei Niu

Hi, all

Tricircle team has already enabled LBaaS with tricircle. Here is the guide
https://github.com/openstack/tricircle/blob/master/doc/source/install/installation-lbaas.rst
.

However, automatic installation and configuration of Octavia in tricircle
is not implemented yet, since some modifications are needed to adapt
Octavia. The detailed info is presented the section of "Setup &
Installation" in
https://github.com/openstack/tricircle/blob/master/doc/source/install/installation-lbaas.rst#setup--installation

What do you think? Look forward to your comments on automatic installation
of Octavia with tricircle.

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] [octavia] amphora fails to send request to members

2017-11-13 Thread Yipei Niu

Hi, Michael,

Thanks a lot for your comments.

In the environment where octavia and tricircle are installed together, I
created a router and attached subnet1 to it. Then I bind the mac address of
10.0.1.9 (real gateway) to ip of 10.0.1.1 in the amphora arp cache,
manually making amphora knows the mac address of 10.0.1.1 (actually it is
the mac of 10.0.1.9, since 10.0.1.1 does not exist), it works.

To make the situation clear, I run the commands in the environment
installed octavia alone. Please note that in this environment, there is no
router. The results are as follows.

stack@stack-VirtualBox:~$ neutron lbaas-loadbalancer-list
neutron CLI is deprecated and will be removed in the future. Use openstack
CLI instead.
+--+--+--+-+-+--+
| id   | name | tenant_id
  | vip_address | provisioning_status | provider |
+--+--+--+-+-+--+
| d087d3b4-afbe-4af6-8b31-5e86fc97da1b | lb1  |
e59bb8f3bf9342aba02f9ba5804ed2fb | 10.0.1.9| ACTIVE  |
octavia  |
+--+--+--+-+-+--+

ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
amphora-haproxy ip addr
sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state
UP group default qlen 1000
link/ether fa:16:3e:dc:9e:61 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.11/24 brd 10.0.1.255 scope global eth1
   valid_lft forever preferred_lft forever
inet 10.0.1.9/24 brd 10.0.1.255 scope global secondary eth1:0
   valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fedc:9e61/64 scope link
   valid_lft forever preferred_lft forever

ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
amphora-haproxy ip route show table all
sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
default via 10.0.1.1 dev eth1  table 1 onlink
default via 10.0.1.1 dev eth1 onlink
10.0.1.0/24 dev eth1  proto kernel  scope link  src 10.0.1.11
broadcast 10.0.1.0 dev eth1  table local  proto kernel  scope link  src
10.0.1.11
local 10.0.1.9 dev eth1  table local  proto kernel  scope host  src
10.0.1.11
local 10.0.1.11 dev eth1  table local  proto kernel  scope host  src
10.0.1.11
broadcast 10.0.1.255 dev eth1  table local  proto kernel  scope link  src
10.0.1.11
fe80::/64 dev eth1  proto kernel  metric 256  pref medium
unreachable default dev lo  table unspec  proto kernel  metric 4294967295
error -101 pref medium
local fe80::f816:3eff:fedc:9e61 dev lo  table local  proto none  metric 0
pref medium
ff00::/8 dev eth1  table local  metric 256  pref medium
unreachable default dev lo  table unspec  proto kernel  metric 4294967295
error -101 pref medium

ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
amphora-haproxy ip rule show
sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
0: from all lookup local
100: from 10.0.1.9 lookup 1
32766: from all lookup main
32767: from all lookup default

If there is no router, the packets are supposed to forwarded in layer 2, as
amphora is plugged with ports of every member's subnet. The priority of
“from 10.0.1.9 lookup 1” is higher than that of "from all lookup local".
Maybe this patch (https://review.openstack.org/#/c/501915/) affects the l2
traffic.

Best regards,
Yipei

On Sat, Nov 11, 2017 at 11:24 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> I tried to run to command, and I think the amphora can connect to the
> member (10.0.1.3). The results are as follows.
>
> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
> amphora-haproxy ping 10.0.1.3
> sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> PING 10.0.1.3 (10.0.1.3) 56(84) bytes of data.
> 64 bytes from 10.0.1.3: icmp_seq=1 ttl=64 time=189 ms
> 64 bytes from 10.0.1.3: icmp_seq=2 ttl=64 time=1.72 ms
> ^C
> --- 10.0.1.3 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1006ms
> rtt min/avg/max/mdev = 1.722/95.855/189.989/94.134 ms
>
> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
> amphora-haproxy curl 10.0.1.3
> sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> Welcome to 10.0.1.3
>
> stack@devstack-1:~$ sudo ip netns exec 
> qdhcp-310fea4b-36ae-4617-b499-5936e8eda842
> curl 10.0.1.3
> Welcome to 10.0.1.3
>
> As mentioned in my previous mail, I also have

Re: [openstack-dev] [octavia] amphora fails to send request to members

2017-11-13 Thread Yipei Niu

rwarded in layer 2, as
amphora is plugged with ports of every member's subnet. The priority of
“from 10.0.1.9 lookup 1” is higher than that of "from all lookup local".
Maybe this patch (https://review.openstack.org/#/c/501915/) affects the l2
traffic.

Best regards,
Yipei

On Tue, Nov 14, 2017 at 10:40 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> Thanks a lot for your comments.
>
> In the environment where octavia and tricircle are installed together, I
> created a router and attached subnet1 to it. Then I bind the mac address of
> 10.0.1.9 (real gateway) to ip of 10.0.1.1 in the amphora arp cache,
> manually making amphora knows the mac address of 10.0.1.1 (actually it is
> the mac of 10.0.1.9, since 10.0.1.1 does not exist), it works.
>
> To make the situation clear, I run the commands in the environment
> installed octavia alone. Please note that in this environment, there is no
> router. The results are as follows.
>
> stack@stack-VirtualBox:~$ neutron lbaas-loadbalancer-list
> neutron CLI is deprecated and will be removed in the future. Use openstack
> CLI instead.
> +--+--+-
> -+-+-+--+
> | id   | name | tenant_id
>   | vip_address | provisioning_status | provider |
> +--+--+-
> -+-+-+--+
> | d087d3b4-afbe-4af6-8b31-5e86fc97da1b | lb1  |
> e59bb8f3bf9342aba02f9ba5804ed2fb | 10.0.1.9| ACTIVE  |
> octavia  |
> +--+--+-
> -+-+-+--+
>
> ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
> amphora-haproxy ip addr
> sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
> 1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether fa:16:3e:dc:9e:61 brd ff:ff:ff:ff:ff:ff
> inet 10.0.1.11/24 brd 10.0.1.255 scope global eth1
>valid_lft forever preferred_lft forever
> inet 10.0.1.9/24 brd 10.0.1.255 scope global secondary eth1:0
>valid_lft forever preferred_lft forever
> inet6 fe80::f816:3eff:fedc:9e61/64 scope link
>valid_lft forever preferred_lft forever
>
> ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
> amphora-haproxy ip route show table all
> sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
> default via 10.0.1.1 dev eth1  table 1 onlink
> default via 10.0.1.1 dev eth1 onlink
> 10.0.1.0/24 dev eth1  proto kernel  scope link  src 10.0.1.11
> broadcast 10.0.1.0 dev eth1  table local  proto kernel  scope link  src
> 10.0.1.11
> local 10.0.1.9 dev eth1  table local  proto kernel  scope host  src
> 10.0.1.11
> local 10.0.1.11 dev eth1  table local  proto kernel  scope host  src
> 10.0.1.11
> broadcast 10.0.1.255 dev eth1  table local  proto kernel  scope link  src
> 10.0.1.11
> fe80::/64 dev eth1  proto kernel  metric 256  pref medium
> unreachable default dev lo  table unspec  proto kernel  metric 4294967295
> <0429%20496%207295>  error -101 pref medium
> local fe80::f816:3eff:fedc:9e61 dev lo  table local  proto none  metric 0
> pref medium
> ff00::/8 dev eth1  table local  metric 256  pref medium
> unreachable default dev lo  table unspec  proto kernel  metric 4294967295
> <0429%20496%207295>  error -101 pref medium
>
> ubuntu@amphora-dcbff58a-d418-4271-9374-9de2fd063ce9:~$ sudo ip netns exec
> amphora-haproxy ip rule show
> sudo: unable to resolve host amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
> 0: from all lookup local
> 100: from 10.0.1.9 lookup 1
> 32766: from all lookup main
> 32767: from all lookup default
>
> If there is no router, the packets are supposed to forwarded in layer 2,
> as amphora is plugged with ports of every member's subnet. The priority of
> “from 10.0.1.9 lookup 1” is higher than that of "from all lookup local".
> Maybe this patch (https://review.openstack.org/#/c/501915/) affects the
> l2 traffic.
>
> Best regards,
> Yipei
>
> On Sat, Nov 11, 2017 at 11:24 AM, Yipei Niu <newy...@gmail.com> wrote:
>
>> Hi, Michael,
>>
>> I tried to run to command, and I think the amphora can connect to the
>> member (10.0.1.3). The results are as follows.
>>
>> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns
>> exec amphora-hap

Re: [openstack-dev] [octavia] amphora fails to send request to members

2017-11-14 Thread Yipei Niu

Hi, Michael,

Please ignore my last two mails. Sorry about that.

The results of the two commands are as follows.

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy ip route show table all
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
default via 10.0.1.1 dev eth1  table 1 onlink
default via 10.0.1.10 dev eth1
10.0.1.0/24 dev eth1  proto kernel  scope link  src 10.0.1.8
broadcast 10.0.1.0 dev eth1  table local  proto kernel  scope link  src
10.0.1.8
local 10.0.1.4 dev eth1  table local  proto kernel  scope host  src
10.0.1.8
local 10.0.1.8 dev eth1  table local  proto kernel  scope host  src
10.0.1.8
broadcast 10.0.1.255 dev eth1  table local  proto kernel  scope link  src
10.0.1.8
fe80::/64 dev eth1  proto kernel  metric 256  pref medium
unreachable default dev lo  table unspec  proto kernel  metric 4294967295
<0429%20496%207295>  error -101 pref medium
local fe80::f816:3eff:febe:5ad5 dev lo  table local  proto none  metric 0
pref medium
ff00::/8 dev eth1  table local  metric 256  pref medium
unreachable default dev lo  table unspec  proto kernel  metric 4294967295
<0429%20496%207295>  error -101 pref medium

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy ip rule show
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
0: from all lookup local
100: from 10.0.1.4 lookup 1
32766: from all lookup main
32767: from all lookup default

I think I know the source. When haproxy receives packets sent by curl, it
responds with taking VIP as source ip for 3-way handshake. Before adding “
100: from 10.0.1.9 lookup 1”, the datagrams are routed based on main table.
After adding "100: from 10.0.1.9 lookup 1", the haproxy tries to find the
gateway based on "default via 10.0.1.1 dev eth1  table 1 onlink". However,
if there is no router, the gateway ip is missing, making haproxy fails to
build tcp connection.

Best regards,
Yipei


On Tue, Nov 14, 2017 at 11:04 AM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> Sorry about the typo in the last mail. Please just ignore the last mail.
>
> In the environment where octavia and tricircle are installed together, I
> created a router and attached subnet1 to it. Then I bind the mac address of
> 10.0.1.10 (real gateway) to ip of 10.0.1.1 in the amphora arp cache,
> manually making amphora knows the mac address of 10.0.1.1 (actually it is
> the mac of 10.0.1.10, since 10.0.1.1 does not exist), it works.
>
> I also run the commands in this environment.
>
> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
> amphora-haproxy ip route show table all
> sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> default via 10.0.1.1 dev eth1  table 1 onlink
> default via 10.0.1.10 dev eth1
> 10.0.1.0/24 dev eth1  proto kernel  scope link  src 10.0.1.8
> broadcast 10.0.1.0 dev eth1  table local  proto kernel  scope link  src
> 10.0.1.8
> local 10.0.1.4 dev eth1  table local  proto kernel  scope host  src
> 10.0.1.8
> local 10.0.1.8 dev eth1  table local  proto kernel  scope host  src
> 10.0.1.8
> broadcast 10.0.1.255 dev eth1  table local  proto kernel  scope link  src
> 10.0.1.8
> fe80::/64 dev eth1  proto kernel  metric 256  pref medium
> unreachable default dev lo  table unspec  proto kernel  metric 4294967295
> <0429%20496%207295>  error -101 pref medium
> local fe80::f816:3eff:febe:5ad5 dev lo  table local  proto none  metric 0
> pref medium
> ff00::/8 dev eth1  table local  metric 256  pref medium
> unreachable default dev lo  table unspec  proto kernel  metric 4294967295
> <0429%20496%207295>  error -101 pref medium
> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
> amphora-haproxy ip rule show
> sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> 0: from all lookup local
> 100: from 10.0.1.4 lookup 1
> 32766: from all lookup main
> 32767: from all lookup default
>
>
> To make the situation clear, I run the commands in the environment
> installed octavia alone. Please note that in this environment, there is no
> router. The results are as follows.
>
> stack@stack-VirtualBox:~$ neutron lbaas-loadbalancer-list
> neutron CLI is deprecated and will be removed in the future. Use openstack
> CLI instead.
> +--+--+-
> -+-+-+--+
> | id   | name | tenant_id
>   | vip_address | provisioning_status | provider |
> +--+--+---

Re: [openstack-dev] [octavia] amphora fails to send request to members

2017-11-10 Thread Yipei Niu

   |
| tenant_id | e59bb8f3bf9342aba02f9ba5804ed2fb   |
| updated_at| 2017-10-08T06:33:09Z   |
+---++

Some other info in this octavia env is as follows.

The info of load balancer:
+-++
| Field   | Value  |
+-++
| admin_state_up  | True   |
| description ||
| id  | d087d3b4-afbe-4af6-8b31-5e86fc97da1b   |
| listeners   | {"id": "d22644d2-cc40-44f1-b37f-2bb4f555f9b9"} |
| name| lb1|
| operating_status| ONLINE |
| pools   | {"id": "bc95c8e0-8475-4d97-9606-76c431e78ef7"} |
| provider| octavia|
| provisioning_status | ACTIVE |
| tenant_id   | e59bb8f3bf9342aba02f9ba5804ed2fb   |
| vip_address | 10.0.1.9   |
| vip_port_id | 902a78e7-a618-455b-91c7-cd36595475cc   |
| vip_subnet_id   | 37023e56-a8bf-4070-8022-f6b6bb7b8e82   |
+-++

The info of VMs:
+--+
--+++---
--+--+
| ID   | Name
   | Status | Task State | Power State | Networks
   |
+--+
--+++---
--+--+
| 50ae3581-94fc-43ce-b53c-728715cd5597 |
amphora-dcbff58a-d418-4271-9374-9de2fd063ce9
| ACTIVE | -  | Running | lb-mgmt-net=192.168.0.10;
net1=10.0.1.11 |
| d19b565d-14aa-4679-9d98-ff51461cd625 | vm1
  | ACTIVE | -  | Running | net1=10.0.1.5
  |
+--+
--+++---
--+--+

The info of listener:
+---+---
-+
| Field | Value
  |
+---+---
-+
| admin_state_up| True
 |
| connection_limit  | -1
 |
| default_pool_id   | bc95c8e0-8475-4d97-9606-76c431e78ef7
 |
| default_tls_container_ref |
  |
| description   |
  |
| id| d22644d2-cc40-44f1-b37f-2bb4f555f9b9
 |
| loadbalancers | {"id": "d087d3b4-afbe-4af6-8b31-5e86fc97da1b"}
|
| name  | listener1
  |
| protocol  | HTTP
 |
| protocol_port | 80
 |
| sni_container_refs|
  |
| tenant_id | e59bb8f3bf9342aba02f9ba5804ed2fb
 |
+---+---
-+

So I think the amphora can reach the member, it just cannot respond to
curl, hence failing to balance load across members. Maybe there is
something wrong with the image of the amphora. Since I replaced the latest
amphora image with an old one (built on 2017-07-24), it works. Totally same
environment except the amphora image.

Best regards,
Yipei

On Fri, Nov 10, 2017 at 5:24 PM, Yipei Niu <newy...@gmail.com> wrote:

> Hi, Michael,
>
> Thanks a lot for your reply.
>
> I can make sure that there is no router or multiple dhcp services in my
> environment.
>
> As shown in my first mail, the haproxy in the amphora tries to find the
> gateway ip 10.0.1.1 that does not exist in the environment.
>
> ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
> amphora-haproxy tcpdump -i eth1 -nn
> sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
> ^C07:25:24.225614 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq
> 1637781601, win 28200, options [mss 1410,sackOK,TS val 30692602 ecr
> 0,nop,wscale 7], length 0
> 07:25:24.237854 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
> 07:25:25.224801 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
> 07:25:25.228610 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq
> 1637781601, win 28200, options [mss 1410,sackOK,TS val 30692853 ecr
>

[openstack-dev] [octavia] amphora fails to send request to members

2017-11-07 Thread Yipei Niu

Hi, all,

I created a lb whose vip is 10.0.1.4. When requesting the vip, i cannot
receive the responses. Hence, I console in the amphora and trace packets
handled by eth0 in the amphora-haproxy network namespace. The detailed info
is as follows.

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy tcpdump -i eth1 -nn
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
^C07:25:24.225614 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq
1637781601, win 28200, options [mss 1410,sackOK,TS val 30692602 ecr
0,nop,wscale 7], length 0
07:25:24.237854 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:25.224801 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:25.228610 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq 1637781601,
win 28200, options [mss 1410,sackOK,TS val 30692853 ecr 0,nop,wscale 7],
length 0
07:25:26.224533 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:27.230911 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:27.250858 IP 10.0.1.2.55294 > 10.0.1.4.80: Flags [S], seq 1637781601,
win 28200, options [mss 1410,sackOK,TS val 30693359 ecr 0,nop,wscale 7],
length 0
07:25:28.228796 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:29.228697 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:29.290551 ARP, Request who-has 10.0.1.4 tell 10.0.1.2, length 28
07:25:29.290985 ARP, Reply 10.0.1.4 is-at fa:16:3e:be:5a:d5, length 28
07:25:31.251122 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:32.248737 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28
07:25:33.250309 ARP, Request who-has 10.0.1.1 tell 10.0.1.4, length 28

14 packets captured
14 packets received by filter
0 packets dropped by kernel

As shown above, the amphora can receive the requests comes from outside but
it fails to find 10.0.1.1. As a result, amphora cannot send the request to
its load balancing member.

To further demonstrate my environment, the route table and arp cache are
listed as follows.

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy route
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
default 10.0.1.10.0.0.0 UG0  00 eth1
10.0.1.0*   255.255.255.0   U 0  00 eth1

ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy arp
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
Address  HWtype  HWaddress   Flags Mask
Iface
10.0.1.2 ether   fa:16:3e:62:68:a8   C
 eth1
10.0.1.1 (incomplete)
eth1

What do you think? Look forward to your comments. Thank you.

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] [octavia] amphora fails to send request to members

2017-11-08 Thread Yipei Niu

Hi, Michael,

Based on your mail, the information is as follows.

1. The version of Octavia I used is Queens, and the latest commit message is
commit 2ab2836d0ebdd0fd5bc32d3adcc44a92557c8c1d
Author: OpenStack Proposal Bot 
Date:   Fri Nov 3 17:58:59 2017 +

Updated from global requirements

Change-Id: I9047e289b8a3c931156da480b3f9f676c54a8358

2. The info of the amphora and other VMs is as follows.
+--+
--+++---
--+-+
| ID   | Name
   | Status | Task State | Power State | Networks
  |
+--+
--+++---
--+-+
| 33bd02cb-f853-404d-a705-99bc1b04a178 |
amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f
| ACTIVE | -  | Running | lb-mgmt-net1=192.168.1.4;
net1=10.0.1.8 |
| dd046fc9-e2bf-437d-8c51-c397bccc3dc1 | client1
  | ACTIVE | -  | Running | net1=10.0.1.3
 |
| 50446c75-7cb7-43eb-b057-4b6b89a926bc | client3
  | ACTIVE | -  | Running | net4=10.0.4.3
 |
+--+
--+++---
--+-+

3. The info of the load balancer is as follows.
+-++
| Field   | Value  |
+-++
| admin_state_up  | True   |
| description ||
| id  | 51cba1d5-cc3c-48ff-b41e-839619093334   |
| listeners   | {"id": "b20ad920-c6cd-4e71-a9b9-c134e57ecd20"} |
| name| lb1|
| operating_status| ONLINE |
| pools   | {"id": "d0042605-da50-4048-b298-660420b0a1d2"} |
| provider| octavia|
| provisioning_status | ACTIVE |
| tenant_id   | c2a97a04cb6d4f25bdcb8b3f263c869e   |
| vip_address | 10.0.1.4   |
| vip_port_id | 2209a819-0ac8-4211-b878-f0b41ac4727b   |
| vip_subnet_id   | cbcf4f04-da6d-4800-8b40-4b141972c2bf   |
+-++

4. The info of the listener is as follows.
+---+---
-+
| Field | Value
  |
+---+---
-+
| admin_state_up| True
 |
| connection_limit  | -1
 |
| default_pool_id   | d0042605-da50-4048-b298-660420b0a1d2
 |
| default_tls_container_ref |
  |
| description   |
  |
| id| b20ad920-c6cd-4e71-a9b9-c134e57ecd20
 |
| loadbalancers | {"id": "51cba1d5-cc3c-48ff-b41e-839619093334"}
|
| name  | listener1
  |
| protocol  | HTTP
 |
| protocol_port | 80
 |
| sni_container_refs|
  |
| tenant_id | c2a97a04cb6d4f25bdcb8b3f263c869e
 |
+---+---
-+

5. The members of the load balancer lb1 are as follows.
+--+--+-
-+--+---++--
++
| id   | name | tenant_id
  | address  | protocol_port | weight | subnet_id
  | admin_state_up |
+--+--+-
-+--+---++--
++
| 420c905c-1077-46c9-8b04-526a59d93376 |  |
c2a97a04cb6d4f25bdcb8b3f263c869e | 10.0.1.3 |80 |  1 |
cbcf4f04-da6d-4800-8b40-4b141972c2bf | True   |
+--+--+-
-+--+---++--
++

6. Since the VIP and the members reside in the same subnet, only two
subnets are listed as follows.
+--+-+--
++--
-+
| id

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team (crh)

2018-03-14 Thread Yipei Niu

+1.

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

58 matches

Mail list logo