08:02:16 <joehuang> #startmeeting multisite
08:02:16 <collabot> Meeting started Thu May  4 08:02:16 2017 UTC.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:16 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:02:16 <collabot> The meeting name has been set to 'multisite'
08:11:25 <May-meimei> hi
08:11:31 <joehuang> Hi, Meimei
08:11:47 <joehuang> let's start the meeting
08:11:57 <May-meimei> OK！
08:12:07 <joehuang> #topic Beijing OPNFV Demo Application On Boarding
08:12:21 <joehuang> hello, the environment is ready now
08:12:27 <joehuang> but only two blades
08:12:40 <joehuang> one blade will be returned by the end of this week
08:12:58 <joehuang> so the last region will join in next week
08:13:13 <boucherv> I have some issue on floating IP creation in RegionOne (ext-net network)
08:13:22 <joehuang> ok, please
08:13:48 <joehuang> external network is ready, in RegionOne, the ext-network is ext-net1
08:14:15 <joehuang> create network topology in central Neutron, not directly in RegionOne
08:15:02 <joehuang> what's the issue you found in RegionOne
08:15:39 <boucherv> Internal server error
08:16:08 <joehuang> Have you created the FIP from central region?
08:16:37 <boucherv> No
08:16:44 <joehuang> Zhiyuan is core of Tricircle, he will also help the APP on boarding
08:17:18 <boucherv> The FIP on central region work but I can't attach this same as regionone_test_vm
08:18:26 <boucherv> I created a FIP on central_region with ext-net1 and my VM port
08:19:36 <joehuang> ok, one second, zhiyuan, could you check the log in central Neutron, to see what happened
08:20:16 <boucherv> ok
08:20:43 <joehuang> Tianwei, could you confirm the last blade could be returned by the end of this week?
08:23:01 <boucherv> https://pastebin.com/2mbqStqG
08:25:58 <May-meimei> joehuang: yes, the blade of 192.168.22.2 will return next monday
08:26:23 <zhiyuan> hi boucherv, could you send me the command you used to create the floating ip?
08:27:39 <boucherv> $rc floating ip create --port=6f13c53c-f26d-490a-b06b-5e5abfead047 ext-net1
08:28:10 <boucherv> joehuang: Each floating IP must be created in the CentralRegion ?
08:28:19 <joehuang> yes
08:28:56 <joehuang> I saw "$r1 floating ip create --port=6f13c53c-f26d-490a-b06b-5e5abfead047 ext-net"
08:29:23 <boucherv> Yes, but only $rc floating ip create --port=6f13c53c-f26d-490a-b06b-5e5abfead047 ext-net1 works
08:29:36 <boucherv> "$r1 floating ip create --port=6f13c53c-f26d-490a-b06b-5e5abfead047 ext-net" doesn't work
08:29:49 <joehuang> yes, only $rc works
08:30:08 <joehuang> should not create on $r1
08:30:33 <boucherv> But the floating ip creation by cloudify-manager will be more complex with this way
08:32:16 <boucherv> I will describe each network component with the centralRegion on the manager
08:32:39 <zhiyuan> after creating floating ip in CentralRegion, Tricircle will automatically sync the floating ip to RegionOne. It's based on the location of the external network
08:33:09 <boucherv> Ok thanks for this information
08:33:21 <joehuang> no need to create FIP in local OpenStack again
08:34:05 <boucherv> Ok
08:34:25 <boucherv> $r1 floating ip list
08:34:40 <boucherv> But my FIP is not in r1
08:34:42 <boucherv> :/
08:34:56 <joehuang> this is an issue, will investigate
08:35:03 <boucherv> ok
08:35:32 <zhiyuan> oh, this may be creating floating ip doesn't trigger our async job
08:35:35 <joehuang> I'll attend OpenStack summit next week, so you can ping zhiyuan if you need any help in #openstack-tricircle or #opnfv-multisite
08:36:05 <zhiyuan> one workaround is to first create an empty floating ip, then associate the floating ip to vm port
08:36:24 <boucherv> ok
08:36:25 <zhiyuan> in this case, you may need to use neutron client
08:36:47 <zhiyuan> since I don't fine a "floating ip set" command in openstack client
08:36:52 <zhiyuan> s/fine/find
08:36:56 <joehuang> sometimes OpenStack client in Newton is not mature, some parameter is not supported
08:37:23 <boucherv> So it's the rigth way, yes you are right
08:37:41 <boucherv> I associated the port directly
08:38:32 <boucherv> Same as history command for the regionone_test_vm
08:39:48 <joehuang> @Meimei, if the blade is returned, could you please install RegionTwo just like it before was borrowed
08:39:48 <collabot> joehuang: Error: "Meimei," is not a valid command.
08:40:41 <joehuang> to Meimei, if the blade is returned, could you please install RegionTwo just like it before was borrowed
08:44:53 <joehuang> to boucherv,  I'll attend OpenStack summit next week, so you can ping zhiyuan if you need any help in #openstack-tricircle or #opnfv-multisite
08:45:06 <boucherv> joehuang: ok thanks
08:45:55 <boucherv> joehuang: the networking part for the IMS is ready or not ? (in regionOne and Three ?)
08:46:51 <May-meimei> joehuang: ok! no problem
08:47:17 <joehuang> you have to wait for a patch for IMS project to work
08:47:30 <zhiyuan> boucherv, have you disassociated the floating ip and associated again? I find floating ip 192.168.20.115 is still not synced to RegionOne
08:47:32 <joehuang> currently you can test VMs in the admin project
08:48:13 <boucherv> zhiyuan: No, I can do that
08:48:26 <boucherv> joehuang: Ok no problem
08:50:41 <joehuang> once the patch is ready, will inform you about that
08:50:53 <boucherv> joehuang: ok thanks
08:52:00 <joehuang> The issue could be debugged offline
08:52:56 <joehuang> Tianwei, whether we can bring the blades to OPNFV Beijing Summit, or we can only access these blades remotely
08:54:19 <hw_wutianwei> joehuang: maybe not
08:54:51 <joehuang> So we can only access the blades remotely
08:55:10 <hw_wutianwei> yep
08:55:38 <joehuang> ok
08:55:53 <joehuang> other topics?
08:57:07 <joehuang> to boucherv, we
08:58:14 <joehuang> let's stay in IRC channel #openstack-tricircle or #opnfv-multisite or both, so that we can communicate as needed immediately.
08:58:33 <boucherv> ok
08:59:18 <joehuang> fine, if no other topics, let's stay in touch in IRC channel, and we can end the meeting
08:59:40 <joehuang> thank you for attending the meeting
08:59:44 <joehuang> #endmeeting