[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Jan. 13 2017

Sorry for providing the agenda late. 1) Roll Call 2) OPNFV: Daisy CI Progress 3) OPNFV: Daisy Support Escalator 4) OpenStack: Kolla Image Versioning 5) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for

[openstack-dev] [daisycloud-core] Cancelled: IRC meeting 0800UTC Jan. 6 2017

Hi Team, Due to there is no topic to be discussed, I suggest to cancel the meeting. B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Dec. 16 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-12-16-07.59.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-12-16-07.59.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 16 2016

1) Roll Call 2) OPNFV: Daisy CI Progress 3) OpenStack Version management 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 9 2016

1) Roll Call 2) Shanghai Telecom Support (Storage & Bare Metal) 3) OPNFV: Daisy CI Progress 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 2 2016

1) Roll Call 2) China Telecom Support (Storage & Bare Metal) 3) OPNFV: Daisy CI Progress 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] Fw: Re: Re: [kolla] Obtaining version information for Docker container

Adrian, Thank you for the information. B.R., Zhijiang 发件人: Adrian Mouat 收件人: hu.zhiji...@zte.com.cn, 抄送: "OpenStack Development Mailing List (not for usage questions)" 日期: 2016-12-01 23:49 主题:

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

For #1, I think the requirement is that before pulling the image to local registry, one can get its metadata about the version info before hand, thus save time and space spend on pulling wrong images. I don't know if the info in docker label can be retrieved before before pulling the image to

[openstack-dev] Question about OpenStack release model

Hi All, I'm running a project which is a OpenStack related project currently. My questions is:　Is being part of Big Tent a requirement before a project can follow one of those 3 release models(cycle-with-milestones, cycle-with-intermediary, and cycle-trailing) as described in

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Nov. 25 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-25-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-25-08.00.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 25 2016

1) Roll Call 2) OPNFV: CI Progress 3) OPNFV: Escalator Support 4) nominate Ya to be daisycloud-core core reviewer. 5) Newton B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 18 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: CI Progress 4) Core Code Abstraction 5) Newton B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Nominating Ya Zhou for daisycloud-core reviewer

Daisycloud-core team, I'd like to nominate Ya Zhou(IRC name 'zhouya') for daisycloud-core core reviewer. Ya started to work on Daisycloud-core since the beginning of the project and he has made significant contribution to project in last three months including adding Kolla backend,

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 11 2016

Please feel free to add what you need to discuss. 1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: CI Progress 4) Core Code Abstraction 5) Newton B.R., Zhijiang __ OpenStack Development Mailing List (not for usage

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Nov. 4 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-04-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-04-08.00.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 4 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: Daisy4nfv CI Framework Progress 4) Core Code Abstraction B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Oct. 28 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: Daisy4nfv CI Framework Progress 4) Core Code Abstraction 5) Newton Release Related Action items follow-up 1) Newton deployment B.R., Zhijiang __ OpenStack Development

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Oct. 21 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-10-21-07.59.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-10-21-07.59.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Oct. 21 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: Daisy4nfv CI Framework Progress 4) Core Code Abstraction 5) Newton Release Related B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Oct. 14 2016

Meeting ended Fri Oct 14 08:58:52 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-10-14-08.02.html Minutes (text):

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Oct. 14 2016

B.R., Zhijiang __ 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] [daisycloud-core] Agenda for IRC meeting 0800UTC Oct. 14 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: Daisy4nfv CI Framework Progress 4) Host Interface Configration Function Regression 5) Core Code Abstraction B.R., Zhijiang __ OpenStack Development Mailing List (not for

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 30 2016

1) Roll Call 2) Core Code Abstraction 3) Bifrost/Ironic Integration 4) OPNFV: Daisy4nfv CI Framework Progress 5) Bare Metal Deployment(PXE/IPMI) demo2 doc and artifact B.R., Zhijiang __ OpenStack Development Mailing List

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 30 2016

B.R., Zhijiang __ 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] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Sep. 23 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 23 2016

1) Roll Call 2) Core Code Abstraction 3) Bifrost/Ironic Integration 4) OPNFV: Daisy4nfv CI Framework Progress 5) Bare Metal Deployment(PXE/IPMI) Test B.R., Zhijiang __ OpenStack Development Mailing List (not for usage

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 9 2016

1) Roll Call 2) Unit Test Progress 3) Bifrost/Ironic Integration 4) OPNFV: Daisy4nfv CI Framework Progress 5) Bare Metal Deployment(PXE/IPMI) Status Update 6) Bare Metal Related DB Development Status Update B.R., Zhijiang

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Sep. 2 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-02-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-02-08.00.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 2 2016

1) Roll Call 2) Unit Test 3) OPNFV: Daisy4nfv CI Framework Progress 4) Bare Metal Deployment(PXE/IPMI) Status Update 5) Bare Metal Related DB Development Status Update 6) Bifrost/Ironic Integration B.R., Zhijiang __

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting Aug. 26 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-08-26-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-08-26-08.00.txt Log:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting Aug. 26 2016

1) Roll Call 2) OPNFV CI Evolution Study Progress 3) Bare Metal Deployment(PXE/IPMI) Status Update 4) Bare Metal Related DB Deployment Status Update 5) Bifrost/Ironic Integration (does ironic provide all data we need) B.R., Zhijiang

[openstack-dev] [bifrost] Question about the "nics" argument provide to ansible os_ironic module.

Hi Bifrost Team, >From the code study about Bifrost and Shade I found that the "nics" argument provide to ansible's os_ironic module is used for creating ports for a bare metal. I think it is related to neutron. But for bifrost which uses ironic in standalone mode, there is no need to create

[openstack-dev] [daisycloud-core] Agenda for IRC meeting Aug. 19 2016

1) Roll Call 2) OPNFV CI Evolution Study Progress 3) Bare Metal Deployment(PXE/IPMI) Status Update 4) Daisy Bare Metal Related DB Deployment Status Update 5) Bifrost/Ironic Integration B.R., Zhijiang __ OpenStack

[openstack-dev] 答复: Re: [daisycloud-core] Daisy installer demo is out

Hi Will, Yes, Daisy needs httpd to drive the Web UI. And thanks for reminding to add httpd as Daisy's dependency. About you said "daisy work in two VMs", I don't understand what you were meaning. Basically, you can put Daisy into one single VM to reduce the foot print impacted on the bare

[openstack-dev] [daisycloud-core] Daisy installer demo is out

Hi All, Daisycloud-core team are pleased to annonce the first release of Daisy OpenStack Installer. You can download the demo from http://www.daisycloud.org/static/files/installdaisy_el7_noarch.bin. and the corresponding document is here:

[openstack-dev] [daisycloud-core] Agenda for IRC meeting Aug. 12 2016

Sorry for publishing agenda so late. 1) Roll Call 2) Daisycloud: Daisy Demo and doc 3) Daisycloud: Ironic status update 4) Daisycloud: Get backend type by calling host_get_all() 5) Daisy4nfv: Related status update B.R., Zhijiang

[openstack-dev] [kolla] Question about kolla git tag

Hi The image we built before is tagged automatically as 2.0.2. and now the kolla code has been upgrade to 2.0.3. I would like to ask if it is OK to use code 2.0.3 do deploy images 2.0.2, or we'd better to sync the version by using "git tag" command according to the image version? B.R.,

[openstack-dev] 答复: [daisycloud-core] Agenda for IRC meeting Aug. 5 2016

Forgot to mentioned , the channel has been changed from #daisycloud to #openstack-meeting B.R., Zhijiang 发件人: HuZhiJiang180967/user/zte_ltd 收件人: hu.zhiji...@zte.com.cn, huzhiji...@gmail.com, lu.yao...@zte.com.cn, zhou...@zte.com.cn, sun.jin...@zte.com.cn,

[openstack-dev] [daisycloud-core] Agenda for IRC meeting Aug. 5 2016

1) Roll Call 2) Daisy Call Graph doc and CI doc 3) Git tag sync between Kolla code and images 4) Getting backend type and its use cases 5) Image 2.0.3 login problem 6) Daisy4nfv related status update B.R., Zhijiang __

[openstack-dev] [daisycloud-core] IRC Meeting Log 20160722

Hi Team, About the daisy4nfv things we did not have time to discuss, I want to add that: I thought in the future, when we move to work with OPNFV world, we will still use this channel to discuss not only daisycloud but also daisy4nfv. I personaly do not want to maintain two meeting by myself.

[openstack-dev] [daisycloud-core] Today(20160722)'s weekly meeting agenda

20160722 Agenda 1) roll call 2) Agenda bashing 3) Approved Wei (kong.w...@zte.com.cn) as daisycloud core reviewer 4) daisycloud status update 5) daisy4nfv status update 6) daisy4nfv disscussion in daisycloud channel B.R., Zhijiang ZTE

[openstack-dev] [kolla] Why base image always be built each time build a specific image.

Hi, When I use the following command to build keystone image, I saw base/openstack-base image was built for the first time as the dependances, which is OK. kolla-build --registry 127.0.0.1:4000 --push keystone But right after that, when I was building another image (for example rabbitmq), I

[openstack-dev] 答复: [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

OK, we got a consensus. I will add Wei as core committor soon. B.R., Zhijiang 发件人: LuYao00184532/user/zte_ltd 收件人: HuZhiJiang180967/user/zte_ltd@ZTE_LTD, 抄送: openstack-dev@lists.openstack.org, huzhiji...@gmail.com, zhou...@zte.com.cn, sun.jin...@zte.com.cn,

[openstack-dev] [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

Hi Team, I would like to propose adding Wei Kong(kong.w...@zte.com.cn) to the daisycloud-core core team. He has good experience on openstack development, previously he lead another team finished a BP of a cinder driver and his current commitment is on testing, ci for daisycloud-core. Until

[openstack-dev] [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

Hi Team, I would like to propose adding Wei Kong(kong.w...@zte.com.cn) to the daisycloud-core core team. He has good experience on openstack development, previously he lead another team finished a BP of a cinder driver and his current commitment is on testing, ci for daisycloud-core. Until

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [daisycloud-core] [kolla] Kolla Mitakarequirementssupported by CentOS

Steve, I agree with you on that Kolla can use EPEL, because Kolla is not a function part of OpenStack but a deployment tool. In the same vein, is that means Kolla do not need to catch up with the global requirements of OpenStack? For example, instead of using oslo required by OpenStack, can

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [daisycloud-core] Kolla Mitaka requirementssupported by CentOS

Hi Haïkel > Actually, all the dependency above but ansible, docker and git python > modules are in CentOS Cloud SIG repositories. > If you are interested to work w/ CentOS Cloud SIG, we can add missing > dependencies in our repositories. So currently Jinja2 version >= 2.8 is already in the

Re: [openstack-dev] [daisycloud-core] [kolla] Kolla Mitaka requirementssupported by CentOS

> As one of RDO maintainer, I strongly invite kolla, not to use EPEL. > It's proven very hard to prevent EPEL pushing broken updates, or push > updates to fit OpenStack requirements. > Actually, all the dependency above but ansible, docker and git python > modules are in CentOS Cloud SIG

[openstack-dev] 答复: [probably forge email可能是仿冒邮件] [kolla] version of python2-oslo-config

Sorry I used the wrong branch of Kolla, in stable/Mitaka , Kolla only requires oslo-config ver 3.7 发件人: hu.zhiji...@zte.com.cn 收件人: "OpenStack Development Mailing List (not for usage questions)" , 日期: 2016-06-28 19:34 主题: [probably

[openstack-dev] [kolla] version of python2-oslo-config

Hi Kolla team, Base upon requirement.txt, Kolla needs oslo-config version 3.10. But CentOS Mitaka uses 3.9 ,which is python2-oslo-config-3.9.0-1.el7.noarch.rpm. I want to know if Kolla can also work on oslo-config-3.9.0. If it can, then will be a benefit because pip is conflict with rpm on

[openstack-dev] 答复: [probably forge email可能是仿冒邮件] [kolla] reclaimed the kolla namespace on docker

Could you please tell me how to get all Kolla images for Mitaka from Docker registry if I don't want to build them locally? Thank you Zhijiang 发件人: "Steven Dake (stdake)" 收件人: "openstack-dev@lists.openstack.org" , 日期:

[openstack-dev] [daisycloud-core] IRC weekly meeting logistics

Hi Team, Here is the IRC weekly meeting logistics: Weekly on Friday at 1200 UTC, You can check out your local time here: http://www.timeanddate.com/worldclock/fixedtime.html?hour=12=0=0 IRC channel: #daisycloud at freenode So our first meeting will be on this friday (Jun 17). The Agenda

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Neutron][Kolla][ovs-discuss] error whenstarting neutron-openvswitch-agent service

Hi Liyong, I think may be that is a consequent. At least it is not the reason for the following error, 2016-06-06 09:19:45.236 1 ERROR neutron.agent.ovsdb.impl_vsctl [req-5b36-4eae-45d0-8240-ed9e76b04a73 - - - - -] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline',

[openstack-dev] [Neutron][Kolla][ovs-discuss] error when starting neutron-openvswitch-agent service

Hi Guys, I am new to Neutron Kolla and OVS, I was trying to deploy Mitaka on CeontOS in a all-in-one environment using Kolla. After a successful deploying I realized that I should disable NetworkManager service roughly according to:

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

Hi Steven, Thanks for the information. Some further questions: > Reconfigure was not designed to handle changes to globals.yml. I think its a good goal that it should be able to do so, but it does not today. So waht is the prefered method to change kolla_internal_vip_address and make it

[openstack-dev] [Kolla] About kolla-ansible reconfigure

Hi After modifying the kolla_internal_vip_address in /etc/kolla/global.yml , I use kolla-ansible reconfigure to reconfigure OpenStack. But I got the following error. TASK: [mariadb | Restart containers] ** skipping: [localhost] => (item=[{'group':

[openstack-dev] Call for Commiters & Contributors for daisycloud-core project

Hi All, I would like to introduce to you a new OpenStack installer project Daisy(project name: daisycloud-core). Daisy used to be a closed source project mainly developed by ZTE, but currently we make it a OpenStack related project(http://www.daisycloud.org,

[openstack-dev] [kolla] How to get prebuilt all images from dockerhub for a specific tag

Hi, Kolla fellows, The latest quickstart.rst says: "the `dockerhub image registry https://hub.docker.com/u/kollaglue/`__ contains all images from each of Kolla’s major releases. " So I decided to get images from above URL to save time for building them. But when I trying to get the all

[openstack-dev] [kolla] How to contribute to kolla

Hi all kolla fellows, Previously, I managed submit a code review to kolla repo but now I couldn't. Do I need additional rights or configurations? Below is my git remote -a output: gerrit https://hu...@review.openstack.org/openstack/kolla.git (fetch) gerrit

[openstack-dev] [kolla] Kolla rpm distribution

Hi， One of our application would like to use Kolla as an upstream deployment tools. As the application may run in the environment without internet connections, we are trying to packaging Kolla as well as its requirements, such as jinja2, into rpm packages and deliver them along with the

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [kolla] centos-binary-neutron-openvswitch-agent

Hi Jeffrey, Here is the output: [root@forimg tools]# docker logs neutron_openvswitch_agent INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Copying service

[openstack-dev] [kolla] centos-binary-neutron-openvswitch-agent

Hi, After I deployed OpenStack with Kolla the first time, I found that the centos-binary-neutron-openvswitch-agent container mainly in restarting status. Is it OK? Or can you show me some way on how to figure out and resolve this kind of problems? Many thanks! [root@forimg tools]# docker

[openstack-dev] [kolla] How to get rpm locally during kolla build

Hi, I have network problem, it is unstable. Then `kolla-build --registry 127.0.0.1:4000 --push ` always fail when building openstack-base image like this: INFO:kolla.cmd.build:openstack-base: