Re: [openstack-dev] [nova] RFC for Intel RDT/CAT Support in Nova for Virtual Machine QoS

Hi Marcelo, Reserved size means can’t be allocated to Apps(VMs), it is reserved by host, and decided by hardware. This capabilities only show host’s capabilities, there will be another libvirt API to report how many bytes can be allocated to VM per cache bank. Still working on it. Best

[openstack-dev] [nova] RFC for Intel RDT/CAT Support in Nova for Virtual Machine QoS

Hi folks: Seeking community input on an initial design for Intel Resource Director Technology (RDT), in particular for Cache Allocation Technology in OpenStack Nova to protect workloads from co-resident noisy neighbors, to ensure quality of service (QoS). 1. What is Cache Allocation

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

+1 Best Regards Eli Qiao(乔立勇）OpenStack Core team OTC Intel. -- 在 16/12/2 上午9:55，“Shuu Mutou” 写入: +1 for both. Thanks, Shu > -Original Message- > From: Hongbin Lu [mailto:hongbin...@huawei.com] > Sent: Thursday, December 01,

Re: [openstack-dev] [Magnum]

@Zhangshuai I believe you running Magnum service in China’s server, please be note that K8s would pull images from gcr.io, so please be sure you can reach gcr.io in case of China Firewall blocking it. — Best Regards 此致， 敬礼 Eli Qiao（乔立勇）Intel SSG OTC OpenStack Core Team 发件人: Ton Ngo

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

tu 1500 qdisc noop state DOWN link/ether 32:0d:72:8d:d6:42 brd ff:ff:ff:ff:ff:ff 9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN link/ether ea:d4:72:22:e2:4f brd ff:ff:ff:ff:ff:ff I noted that these devices are not in UP state, you’d better to check them first. Best Re

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Oh, that reminds me, MesosMonitor requires to use master node’s floating ip address directly to get state information. BR, Eli(Li Yong)Qiao From: 王华 [mailto:wanghua.hum...@gmail.com] Sent: Thursday, March 31, 2016 11:41 AM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [openstack][keystone] What is the difference between auth_url and auth_uri?

Uri and url are different but sometime they might be same. Well ,you can see it from http://www.ietf.org/rfc/rfc3986.txt BR, Eli(Li Yong)Qiao From: 王华 [mailto:wanghua.hum...@gmail.com] Sent: Monday, February 29, 2016 7:04 PM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [nova]summary of blue print of 'making_live_migration_api_friendly'

Hi folks There are some discussion about this blue print http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/making_live_migration_api_friendly.html As we discussed on yesterday's Nova-Api/Nova-Live-Migration meeting, Alex and me did some summary and write them here

[openstack-dev] [all]Whom should I contact to ask for ATC code

Hello all I am sorry for the broadcasting, but I really don't know whom should I contact. Things is: My friend is a newly developer who already has contribute to openstack project, and would like to know in what way(or email contactor) he can get the ATC code for Austin summit. BR, Eli(Li

Re: [openstack-dev] How to add feature to diskimage-builder

hi here's some links may helps [1] is the general development guide for OpenStack contributors. It may provide some useful guide. [2] is the the place you register blueprint. Hope you play well. Thanks Eli [1]https://wiki.openstack.org/wiki/How_To_Contribute#Feature_development

Re: [openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

hi Everett I'd like to take it. thanks Eli. On 2015年12月02日 05:18, Everett Toews wrote: Hello Magnumites, The API Working Group [1] is looking for a Cross-Project Liaison [2] from the Magnum project. What does such a role entail? The API Working Group seeks API subject matter experts for

[openstack-dev] [Magnum] Why set DEFAULT_DOCKER_TIMEOUT = 10 in docker client?

hi all In Magnum code, we hardcode it as DEFAULT_DOCKER_TIMEOUT = 10 This bring troubles in some bad networking environment (or bad performance swarm master) At least it doesn't work on our gate. Here is the test patch on gate https://review.openstack.org/249522 , I set it as 180 to make sure

[openstack-dev] [Magnum]How do we support swarm master node HA

hi all, failed to set up swarm master HA cluster: here is my setup . 2 master and 1 node, and I put a LB in front of 2 master node(Round-Robin) I saw from swarm ha guide and get confirmed from swarm guys: /jimmyxian | elqiao: I'm here. :). Swarm does not support A-A. But can access the

Re: [openstack-dev] [neutron][heat][magnum] LBaaS of Neutron

/swarm/multi-manager-setup/ even replica can handle user request “You can use the docker command on any Docker Swarm primary manager or any replica." it means "round-robin" should works. — Egor From: "Qiao,Liyong" <liyong.q...@intel.com<mailto:liyong.q...@intel.com>

Re: [openstack-dev] [neutron][heat][magnum] LBaaS of Neutron

A-A mode, so it can use ROUND_ROBIN). https://github.com/openstack/magnum/blob/master/magnum/templates/kubernetes/kubecluster.yaml#L343 P.S Copy to Magnum team. thanks Eli. On 2015年11月16日 15:15, Sergey Kraynev wrote: On 16 November 2015 at 09:46, Qiao,Liyong <liyong.q...@intel.

[openstack-dev] [neutron][heat] LBaaS of Neutron

hi, I have some questions about neutorn LBaas. seen from the wiki, the load balancer only support: *Table 4.6. Load Balancing Algorithms* *Name* LEAST_CONNECTIONS ROUND_ROBIN https://wiki.openstack.org/wiki/Neutron/LBaaS/API think about if I have a A-P mode HA VIP : 192.168.0.10 master-1

[openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

hello all: I will update some Magnum functional testing status, functional/integration testing is important to us, since we change/modify the Heat template rapidly, we need to verify the modification is correct, so we need to cover all templates Magnum has. and currently we only has k8s

Re: [openstack-dev] [Nova] live migration sub-team meeting

hi Paul +1, will attend for this meeting. On 2015年11月10日 19:48, Murray, Paul (HP Cloud) wrote: Thank you for the prompting Michael. I was chasing up a couple of key people to make sure they were available. The IRC meeting should be Tuesdays at 1400 UTC on #openstack-meeting-3 starting

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

+1, Alex worked on Nova project for a long time, and push lot of API feature in last few cycles, And spend lots of time doing reviewing, I am glad to add my +1 to him. BR, Eli(Li Yong)Qiao -Original Message- From: Ed Leafe [mailto:e...@leafe.com] Sent: Saturday, November 07, 2015 2:34

[openstack-dev] [Magnum] [RFC] split pip line of functional testing

hi Magnum hackers: Currently there is a pip line on project-config to do magnum functional testing [1] on summit, we've discussed that we need to split it per COE[2], we can do this by adding new pip line to testing./ / /- '{pipeline}-functional-dsvm-magnum{coe}{job-suffix}':/ coe could be

[openstack-dev] [magnum] k8s api tls_enabled mode testing

Hello, I need your help on k8s api tls_enabled mode. Here’s my patch https://review.openstack.org/232421 It is always failed on gate, but it works in my setup. Debug more I found that the ca cert return api return length with difference: On my setup： 10.238.157.49 - - [21/Oct/2015 19:16:17]

Re: [openstack-dev] [Magnum] Coe components status

hi Vikas, thanks for propose this changes, I wonder if you can show some examples for other coes we currently supported: swarm, mesos ? if we propose a public api like you proposed, we'd better to support all coes instead of coe specific. thanks Eli. On 2015年10月20日 18:14, Vikas Choudhary

Re: [openstack-dev] [magnum] Failed to create swarm baywithfedora-21-atomic-5-d181.qcow2

I co-worked with Mars last week, but in my environment I can not reproduce this issue. I'v told my docker daemon line to Mars, but same errors. one thing I forget to ask, it is same with hongbin's question: if you need proxy to access internet, please add them in baymodel:

[openstack-dev] [Magnum] Testing result of new atomic-6 image

Testing result of new atomic-6 image [1] built by Tango atomic-5 image has issue to start a container instance(docker version is 1.7.1), Tango built a new atomic-6 image with docker 1.8.1 version. eghobo and I (eliqiao) did some testing works (eghobo_ did most of them) Here is the summary: *

[openstack-dev] [magnum] How to verify a service is correctly setup in heat template

hi Magnum hackers: Recently, we upgrade to fedora atomic-5 image, but the docker (1.7.1) in that image doesn't works well. see [1]. When I using that image to create a swarm bay, magnum told me that bay is usable, actually swarm-master swarm-agent service are not running correctly, so that

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

+1, we can add more detail explanation information of --memory in magnum CLI instead of quick start. Eli. On 2015年10月09日 07:45, Vikas Choudhary wrote: In my opinion, there should be a more detailed document explaining importance of commands and options. Though --memory is an important

[openstack-dev] [magnum] debugging functional testing on gate

hi folks, I am working on add functional testing case for "creating" bays on gate. for now, there is k8s bay creation/deletion testing, I want to adding more swarm/mesos type bay testing, but I tried times , gate failed to create swarm bay. per my experience, swarm-master/node requires to

[openstack-dev] [Nova] 2nd prc hackathon event finised, need your help to review patch

Hi folks We just finished 2nd prc hackathon this Friday. For nova project, we finially have 31 patch/bug submitted/updated, we finally get out a etherpad link to track all bugs/patches, can you kindly help to review these patches on link https://etherpad.openstack.org/p/hackathon2_nova_list

[openstack-dev] [Magnum] Add periodic task threading for conductor server

hi magnum team, I am planing to add periodic task for magnum conductor service, it will be good to sync task status with heat and container service. and I have already have a WIP patch[1], I'd like to start a discussion on the implement. Currently, conductor service is an rpc server, and it

Re: [openstack-dev] TC Candidacy

+1 BR, Eli(Li Yong)Qiao From: David Lyle [mailto:dkly...@gmail.com] Sent: Thursday, April 23, 2015 8:57 AM To: OpenStack Development Mailing List Subject: [openstack-dev] TC Candidacy I'm announcing my candidacy for the Technical Committee elections. I have been contributing to OpenStack since

[openstack-dev] [resend] [nova][libvirt] livemigration failed due to invalid of cpuset

Hi all, Just resend to bring attentions BR, Eli(Li Yong)Qiao From: Qiao, Liyong [mailto:liyong.q...@intel.com] Sent: Wednesday, April 15, 2015 10:22 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [nova][libvirt] livemigration failed due to invalid of cpuset Hi all Live

[openstack-dev] [nova][libvirt] livemigration failed due to invalid of cpuset

Hi all Live migration an instance will fail due to invalid cpuset, more detail can be find in this bug[1] this exception is raised by python-libvirt's migrateToURI2/ migrateToURI. I'd like to get your idea on this: 1. disable live-migration and raise exception early since migrateToURI2/

Re: [openstack-dev] In loving memory of Chris Yeoh

+1 from me. Chris is also my leader in IBM some time before, He is a helpful and talkative man. I learn lots from him, he work so hard that I see he send out email shortly before even he is ill in bed. we never forget the contribution for the nova community, nova v3 api, nova v2.1 api nova

[openstack-dev] [nova] will instance action deprecate in feature

Hi all will instance action deprecate in feature since we have notify mechanism now? Currently, nova have instance action and instance event action to record specify actions performed on a instances. For some enterprise user, they may need to compute the latency when they perform an action on an