Thursday, 2016-11-24

-openstackstatus- NOTICE: Due to a problem with the cinder volume backing the log server, jobs are failing with POST_FAILURE. Please avoid issuing 'recheck' commands until the issue is resolved.00:12
*** ChanServ changes topic to "Due to a problem with the cinder volume backing the log server, jobs are failing with POST_FAILURE. Please avoid issuing 'recheck' commands until the issue is resolved."00:12
*** kevinz has joined #openstack-nimble01:19
zhenguomorning nimble01:27
*** yuntongjin has joined #openstack-nimble01:29
zhenguoshaohe_feng, yuntongjin, liusheng, shihanzhang, luyao, Kevin_Zheng, kevinz: we will start our weekly meeting at 10am, please feel free to add agenda here https://wiki.openstack.org/wiki/Meetings/Nimble#Agenda_for_next_meeting01:34
openstackgerritZhenguo Niu proposed openstack/nimble: [Do Not Merge] testing tempest  https://review.openstack.org/40182001:36
openstackgerritgecong proposed openstack/nimble: Update flake8 ignore list  https://review.openstack.org/40182301:50
*** lei-zh has joined #openstack-nimble02:00
zhenguo#startmeeting nimble02:00
openstackMeeting started Thu Nov 24 02:00:50 2016 UTC and is due to finish in 60 minutes.  The chair is zhenguo. Information about MeetBot at http://wiki.debian.org/MeetBot.02:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:00
openstackThe meeting name has been set to 'nimble'02:00
zhenguoo/02:00
lei-zho/02:01
zhenguoshaohe_feng, yuntongjin: are you around?02:01
shihanzhango/02:02
yuntongjinhi02:02
liushengo/02:02
zhenguothe agenda:02:02
zhenguo#link https://wiki.openstack.org/wiki/Meetings/Nimble#Agenda_for_next_meeting02:02
zhenguook, let's jump in02:03
zhenguo#topic announcements and reminders02:03
zhenguoOur initial tempest patch has been merged yesterday02:03
zhenguoand the infras dsvm gate has been seup as well02:03
zhenguothanks liusheng02:04
*** RuiChen has joined #openstack-nimble02:04
zhenguobut seems there are something wrong with the devstack setup there according to the logs of my test patch02:04
zhenguo#link http://logs.openstack.org/20/401820/1/check/gate-nimble-dsvm-tempest-plugin/4464112/logs/02:05
zhenguoso currently our gate is broken :(02:05
shaohe_fengzhenguo: hi02:05
liushengzhenguo: :(02:05
zhenguoshaohe_feng: o/02:05
zhenguoliusheng: we don't need the devstack gate hook anymore right?02:06
RuiCheno/02:07
liushengzhenguo: I don't think it need, I have referenced other project's02:07
zhenguoRuiChen: hi02:07
RuiChensorry, i'm late02:07
zhenguoRuiChen: np02:07
RuiChenso we start?02:07
zhenguoRuiChen: sure, haha02:07
zhenguoliusheng: yes, so we can cleanup that hook script02:08
RuiChenplease go ahead :-)02:08
liushengzhenguo: which one ?02:08
liushengzhenguo: oh I see02:08
zhenguonimble/devstack/gate/02:08
zhenguoliusheng: but without that, we can't control which services are enabled02:09
zhenguoliusheng: I read the currently dsvm logs, seems it setup all services02:09
liushengzhenguo: I will check02:10
zhenguoliusheng: ok thanks02:10
zhenguoand we still need to add more tests including UT and functional02:10
zhenguoespecially for api and engine02:10
zhenguowho are still working on tests now?02:11
yuntongjinwe could have a wiki/list to track test-case task02:12
*** fredli has joined #openstack-nimble02:12
yuntongjinor have a blueprint to track02:12
zhenguoyuntongjin: seems like there will be many test cases02:12
zhenguoyuntong: I'm afraid it's hard to list all :(02:13
yuntongjincan list by resource like instance/type....02:13
zhenguoyuntongjin: yes, we already list by place them into different dir now02:14
yuntongjink, that works02:14
liushengzhenguo: about the tempest, I think it is easy to add tests for instance_type, but for instance, I am not sure...02:14
zhenguoliusheng: yes, recently I merged the refactor patch02:14
zhenguoliusheng: It will affect all instances related tests02:15
liushengzhenguo: e.g. if we add test for instance creation, it is ok to create an instance from nimble-api to ironic ?02:15
liushengzhenguo: Ok02:15
zhenguoliusheng: I think it's ok, because our current devstack setup can support that02:16
liushengzhenguo: ok, let's try :)02:16
zhenguoliusheng: you can just add tests for creating with the parameters we create in devstack by default02:16
liushengzhenguo: ok, thanks02:16
zhenguook, so next, seems like we still lack the basic abilities of powering instance in our CLI02:17
zhenguoRuiChen, shihanzhang: do we have a plan for that ?02:18
shihanzhangi will do it  next week02:18
zhenguoshihanzhang: ok, many thanks :)02:19
zhenguothe contribution report:02:19
zhenguo#link http://stackalytics.com/report/contribution/nimble/9002:19
zhenguothanks all for that :P02:20
zhenguonot much of announcement, anyone else have a thing here?02:20
*** tiantian has quit IRC02:21
zhenguook02:21
zhenguo#topic Ocata feature priorities02:21
zhenguo#link https://trello.com/b/FBsIvUTp/ironic-nimble-plan02:21
zhenguo#link https://blueprints.launchpad.net/nimble02:22
zhenguoreally so many things to do02:22
zhenguobut seems we only have about 3 developers full time dedicated to nimble now, which is less than we startup :(02:22
liushengzhenguo: :(02:23
liushengzhenguo: attract new comers in Bug Smash :)02:24
zhenguoliusheng: I hope so, hah02:24
zhenguoor maybe we can add some simple bug on launchpad to attract new developers?02:24
zhenguobut we are not a offical project, seems nobody want to join to a new startup project :(02:25
liushengzhenguo: new startup project can make them easy to become core members, hah02:26
zhenguoliusheng: hah, that' true02:26
zhenguomaybe we can announce a new core member in mailing list, that seems the best way to attract new developers, lol02:27
liushengzhenguo: which day we want to announce our project to public ?02:28
zhenguoliusheng: I would to do that by this week02:28
zhenguodo you still have any concerns about that02:28
zhenguo02:28
liushengzhenguo: no, it is cool, I will check the tempest job and fix it today02:30
zhenguoliusheng: thanks a lot?02:30
zhenguoshaohe_feng: do you still have some concerns?02:30
zhenguoyuntongjin, RuiChen: wdyt?02:31
zhenguook02:32
zhenguonext week I plan to finish az and quota,02:32
zhenguoand do you think which is the highest priority thing we need to do?02:33
yuntongjinzhenguo: i think it's the announcement02:33
zhenguoyuntongjin: ok02:34
zhenguocome on, please say something here, @everyone02:34
liushengzhenguo: may we can share some docs about Nimble besides the Wiki, but I am not sure we have02:35
yuntongjini was think to add network device in nimble as new resource02:35
liushengzhenguo: when announcing the project02:35
zhenguoliusheng: we only have a dev-quickstart doc currently02:35
zhenguoyuntongjin: yes, I also want to add that02:36
yuntongjingreat, will file a BP for that02:36
zhenguoyuntongjin: ok, thanks, and maybe we need to add a specs, and discuss there, wdyt?02:36
zhenguoas we support to specify port type when requesting to create a new instance, but no way to scheduling a node with that type of network interfaces02:37
yuntongjindo we have a BP for this task?02:38
zhenguoit's unaccepatable, and we also want to support portgroup in future, which also depends on the network resources02:38
zhenguoyuntongjin: no02:38
zhenguoyuntongjin: can you help to add a bp for that, or maybe also draft a specs :)02:39
yuntongjinwill do02:39
zhenguoyuntong: thanks very much!02:39
zhenguook, what's next02:39
zhenguo#topic open discussion02:39
luyaozhen02:40
zhenguoluyao: hi02:40
zhenguoluyao: I remember you have been investigating taskflow this week, right?02:40
luyaoyes,I have something to do last week02:41
zhenguoluyao: how about that? could we introduce flow work in our create method02:41
luyaoI want add rollback mechanism for creating intsance this week02:42
zhenguoluyao: awsome!02:42
zhenguoluyao: I have refactored some codes, please update you dev repo to see02:42
luyaoI 'am not sure,I need trying :)02:42
luyaoOK02:42
zhenguoluyao: ok, thanks02:42
zhenguohi all, do you have other things want to discuss here?02:43
yuntongjinluyao: add a BP for your task so that everyone can contribute02:43
zhenguoyuntongjin: oh yes, thanks for remindering that!02:44
zhenguokevinz: are you around?02:44
luyaoyuntongjin: OK02:45
yuntongjinnext step, after annoucement, let's keep focus on killer feature02:45
zhenguoyuntongjin: sure02:45
zhenguoyuntongjin: do you think it's easy for us to add instance transfer ability?02:45
yuntongjinlike ironic did?02:46
kevinzzhenguo: Hi zhenguo I'm here just now :D02:46
zhenguokevinz: oh, hah02:46
zhenguoyuntongjing: like cinder volume02:46
yuntongjink, i see02:46
zhenguokevinz: do you have some suggestion for us, like do we need to add more docs?02:47
yuntongjintransfer b/w tenenats?02:47
zhenguoyuntongjin: yes02:47
zhenguokevinz: as we want to announce the project in mainling list this week, not sure if we are ready02:48
yuntongjintry file a BP to discuss, i prefer it's a low P task02:48
zhenguoyuntongjin: yes02:48
kevinzzhenguo: Wow cool, push nimble to big-tent?02:48
zhenguokevinz: no, not ready for big-tent, just announce in the mailing list :P02:49
yuntongjinshould pay more focus on feature that related HW02:49
zhenguoyuntongjin: we are open source, lol02:49
yuntongjinkevinz: that's the plan02:49
yuntongjinHW = Hardware 8-)02:50
zhenguoyuntongjin: oh, sorry, I misunderstood, lol02:51
zhenguoyuntongjin: I think it means huawei, hah02:51
yuntongjinmy bat02:51
yuntongjinmy bad02:51
zhenguoyuntongjin: hah02:51
zhenguooh, any other things want to discuss here?02:52
yuntongjinnot much from here02:53
kevinzgood luck to nimble :D02:53
zhenguokevinz: thanks02:53
zhenguodo you think notifications should be a high priority thing for us now?02:54
zhenguonotifications of nimble, or leveraing ironic's notifications02:54
yuntongjini don't think so02:55
shaohe_fengzhenguo: I'm back02:55
zhenguoshaohe_feng: o/02:55
zhenguoyuntongjin: ok, maybe later02:55
yuntongjinfocus on hardware feature02:55
RuiChenagree with yuntongjin, notification should not be high02:56
shaohe_fengRuiChen: do we have a priority list?02:56
zhenguoRuiChen, yuntongjin: ok, but we need to consider charging in future02:56
zhenguoshaohe_feng: not cureently02:57
shaohe_fengzhenguo: do we need spec for the BP?02:57
zhenguoshaohe_feng: for new bp, I think we can try to use specs02:58
zhenguoshaohe_feng: but for some thing easy to implement seems not needed02:58
RuiChenyes, and we can discuss details in the comments02:58
zhenguoyes, and we need to file bugs for patches02:59
zhenguoshould follow the offical way02:59
RuiChenzhenguo agree, but we should give a exact describe in blueprint03:00
zhenguoRuiChen: seems not, just some summarize it's enough IMO03:00
RuiCheni means if we don't parpere a spec for BP03:01
zhenguoRuiChen: oh, yes, it's needed for those bps03:01
zhenguooh, seems time's up03:01
zhenguothanks everyone, we can continue to discuss in our channel03:01
zhenguo#endmeeting03:02
openstackMeeting ended Thu Nov 24 03:02:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-11-24-02.00.html03:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-11-24-02.00.txt03:02
openstackLog:            http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-11-24-02.00.log.html03:02
RuiChenthanks03:02
*** yuntongjin has quit IRC03:04
shaohe_fengzhenguo:  what is instance transfer ability?03:08
zhenguoshaohe_feng: like you can transfer a instance from one tenant to another03:08
zhenguoshaohe_feng: only admins can do this03:09
shaohe_fengzhenguo: got it.03:09
zhenguoshaohe_feng: like we want to import active node to nimble, then I think we need to transfer it to a tenant03:10
shaohe_fengzhenguo: yes, that's the scenario.03:11
zhenguoshaohe_feng: yes, like volume, we can also to import exist volume to cinder03:11
shaohe_fengzhenguo: for the existed instance in nimble, do we allow transfer?03:12
zhenguoshaohe_feng: I think we should support that03:13
shaohe_fengzhenguo: is there a scenario?03:14
shaohe_fengzhenguo: for example, a instance belong to one tenant.03:14
shaohe_fengzhenguo: there may be some tenant's data on it03:15
zhenguoshaohe_feng: like in a private cloud senario, we may have many departments each have a separate tenant, support transfer seems it's more convinient to management03:15
shaohe_fengzhenguo: yes,  admin instance to another tenant,  another tenant still need the user/password or keys to logon the host.03:16
shaohe_fengzhenguo: seem OK.03:17
zhenguoshaohe_feng: yes, but it's more complex to transfer a instance than a volume03:17
zhenguoshaohe_feng: sorry, I didn't finish the az api yesterday :(03:18
zhenguoshaohe_feng: seems we only need a single list api03:19
zhenguoshaohe_feng: but unlike nova, cinder, and neutron, our az is offered by ironic node, so I think we can list az by filtering the cached nodes in nimble engine03:21
* zhenguo is away for smoking, brb03:22
shaohe_fengzhenguo: Do worry. I think we do not need rush, we need quality goods.03:24
zhenguoshaohe_feng: sure03:34
*** lei-zh has quit IRC04:11
*** yuntongjin has joined #openstack-nimble04:14
*** yuntongjin has quit IRC04:50
*** ChanServ changes topic to "Bugs: bugs.launchpad.net/nimble | Review: https://review.openstack.org/#/q/project:openstack/nimble,n,z"05:38
-openstackstatus- NOTICE: The affected filesystems on the log server are repaired. Please leave 'recheck' comments on any changes which failed with POST_FAILURE.05:38
*** lei-zh has joined #openstack-nimble05:53
*** yuntongjin has joined #openstack-nimble06:01
*** fredli has quit IRC06:05
openstackgerritliusheng proposed openstack/nimble: WIP: fix gate  https://review.openstack.org/40186506:07
zhenguoliusheng: thanks for fix the devstack06:12
zhenguoliusheng: not sure why we have a check like "$KEYSTONE_CATALOG_BACKEND" = 'sql' before creating the endpoint06:13
liushengzhenguo: hmmm, I am also not sure, I have asked shihanzhang, he said just copied from other project...06:14
zhenguoliusheng: ok, let's see whether it works06:15
shihanzhangi agree with liusheng, we should remove the check06:16
*** yuntongjin has quit IRC06:31
zhenguoliusheng: seems it works, but we still have some problems with ironic tempest configuration06:37
liushengzhenguo: do you know if ironic need to create a flavor named baremetal ?06:37
zhenguoliusheng: seems it's a required if tempest enabled06:38
zhenguoliusheng: and that depends on nova06:38
liushengzhenguo: yes, we need to create the flavor in nimble's script ?06:39
liushengzhenguo: yes06:39
zhenguoliusheng: I don't think we need to do that06:39
zhenguoliusheng: but for ironic+nova, it's created on nova script?06:40
liushengzhenguo: it is strange, it is ok several days ago when we added the dsvm functional job06:40
liushengzhenguo: oh it is depent by tempest06:41
zhenguoliusheng: that's because we have a devstack/gate with a script06:41
zhenguoliusheng: we disable tempest there, so it works06:41
liusheng2016-11-24 06:26:20.794 | +++ /opt/stack/new/ironic/devstack/lib/ironic:ironic_configure_tempest:1586 :   openstack flavor show baremetal -f value -c id06:41
zhenguoliusheng: yes, we do have this issue, so I disabled tempest06:42
liushengzhenguo:  it has installed Nova06:47
liusheng2016-11-24 06:24:52.280 | ++ lib/tempest:configure_tempest:193        :   available_flavors='+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+06:47
liusheng2016-11-24 06:24:52.280 | | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |06:47
liusheng2016-11-24 06:24:52.280 | +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+06:47
liusheng2016-11-24 06:24:52.280 | | 1  | m1.tiny   | 512       | 1    | 0         |      | 1     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | c1 | cirros256 | 256       | 0    | 0         |      | 1     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | d1 | ds512M    | 512       | 5    | 0         |      | 1     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | d2 | ds1G      | 1024      | 10   | 0         |      | 1     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | d3 | ds2G      | 2048      | 10   | 0         |      | 2     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | | d4 | ds4G      | 4096      | 20   | 0         |      | 4     | 1.0         | True      |06:47
liusheng2016-11-24 06:24:52.280 | +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+'06:47
zhenguoliusheng: yes, as it use devstack default configuration now,06:48
zhenguoliusheng: so all services started, but I don't know why baremetal flavor isnt' created.06:48
zhenguoliusheng: seems we have to set VIRT_DRIVER to ironic06:50
liushengzhenguo: set it as an env variable ?06:51
zhenguoliusheng: yes, let me check ironic tempest job defination first06:51
zhenguoliusheng: https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/ironic.yaml#L18706:53
zhenguoliusheng: we need to add this as well06:53
zhenguoliusheng: and maybe  DEVSTACK_GATE_NEUTRON=1 and other options06:55
zhenguoliusheng: DEVSTACK_GATE_NEUTRON=1 is also required06:57
liushengzhenguo: let's try again06:58
zhenguoliusheng: ok06:59
zhenguoliusheng: we need to send a patch to infras06:59
liushengzhenguo: how about add these two in nimble's devstack script ?06:59
zhenguoliusheng: no, as devstack is not only for gate07:00
liushengzhenguo: when  "is_service_enabled tempest" ?07:00
zhenguoliusheng: seems add to gate job defination is more common07:01
zhenguoliusheng: in fact, we don't need VIRT_DIRVER at all, it's a nova thing07:02
zhenguolusheng: it's somewhat strange to leave such a thing to our devstack script07:02
liushengzhenguo: but we depend on Nova07:02
liushengzhenguo: agree.07:02
zhenguoliusheng: No, we only depends on nova in gate checking07:02
zhenguoliusheng: for our devstack we don't need nova :P07:03
zhenguoliusheng: new developers maybe confused if we have these settings07:03
liushengzhenguo: hah07:03
zhenguoliusheng: hah07:03
zhenguoliusheng: I can draft a patch, and seems every afternoon infras cores review patches.07:04
liushengzhenguo: I am afraied it cannot works again even we chenge the infra job, since the infro cannot check if it works...07:04
zhenguoliusheng: after infra patch landed, we can recheck with you patch to fix our devstack07:05
zhenguoliusheng: then it will work07:05
liushengzhenguo: the infra changes are absolutely checked manully07:05
liushengzhenguo: ok07:05
zhenguoliusheng: yes07:05
liushengzhenguo: may I can add these two lines to my patch to check firstly, just test ?07:06
zhenguoliusheng: sure07:07
openstackgerritliusheng proposed openstack/nimble: WIP: fix gate  https://review.openstack.org/40186507:12
zhenguoliusheng: I'm afraid maybe your test patch can't work, as ironic script will run before we export VIRT_DRIVER07:17
liushengzhenguo: yes, I am also think so07:18
zhenguoliusheng: but I'm not sure, in our tempest job defination, we enable ironic plugin first then nimble plugin07:18
liushengzhenguo: but just test, no harm, hah07:18
zhenguoliusheng; yes, lol07:18
*** lei-zh has quit IRC07:23
*** lei-zh has joined #openstack-nimble07:30
*** yuntongjin has joined #openstack-nimble07:31
*** lei-zh has quit IRC07:55
*** lei-zh has joined #openstack-nimble08:38
*** lei-zh has quit IRC09:02
*** yuntongjin has quit IRC09:55
*** lei-zh has joined #openstack-nimble10:04
*** lei-zh has quit IRC10:48
openstackgerritZhenguo Niu proposed openstack/nimble: Add availability zones API  https://review.openstack.org/40199711:59
*** yuntongjin has joined #openstack-nimble12:52
*** yuntongjin has quit IRC13:26
-openstackstatus- NOTICE: OpenStack CI has taken a Thanksgiving break; no new jobs are currently launched. We're currently hoping for a friendly admin to come out of Thanksgiving and fix the system.13:38
*** yuntongjin has joined #openstack-nimble13:45
*** yuntongjin has quit IRC13:58
-openstackstatus- NOTICE: OpenStack CI is processing jobs again. Thanks to the Canadian admin "team" that had their Thanksgiving holiday already ;) Jobs are all enqueued, no need to recheck.14:48
*** openstackgerrit has quit IRC15:03
*** openstackgerrit has joined #openstack-nimble15:05
openstackgerritZhenguo Niu proposed openstack/nimble: Remove unnecessary check before creating Nimble endpoints  https://review.openstack.org/40186517:32
openstackgerritZhenguo Niu proposed openstack/nimble: Remove unneeded devstack gate hook script  https://review.openstack.org/40216817:45

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!