[openstack-dev] [Infrastructure ]Support for PCI Passthrough

2013-11-22 Thread Tan, Lin
Hi, We add the new feature of PCI passthrough in Nova enables assigning a PCI device to an instance in openstack. Now we want to add integration tests in Temptest to cover our module. We come up with several ideas like fade device or QEMU IOMMU emulator, but they are not possible. We talk

[openstack-dev] [TripleO][DiskImage-builder]How to set up network during the deploy

2014-05-20 Thread Tan, Lin
Hi, I am working on setting up Baremetal for a while. I notice that in the process of deployment in TripleO, I mean in the first round of PXE boot, it will append the IP info in the configuration and pass to the target machine as kernel parameters. Then init script will read the parameters and

[openstack-dev] [Ironic] deadline for specs

2014-12-13 Thread Tan, Lin
Hi, A quick question, do we have a SpecProposalDeadline for Ironic, 18th Dec or ? Thanks Best Regards, Tan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ironic] deadline for specs

2014-12-14 Thread Tan, Lin
, the better your chances for it landing in any given cycle. Regards, Devananda On Sat, Dec 13, 2014, 10:10 PM Tan, Lin lin@intel.commailto:lin@intel.com wrote: Hi, A quick question, do we have a SpecProposalDeadline for Ironic, 18th Dec or ? Thanks Best Regards, Tan

Re: [openstack-dev] [Ironic] Thinking about our python client UX

2015-03-08 Thread Tan, Lin
I agree, we need a discussion asap. I think below things can mitigate the unexpected behavior of python client and this is borrow from object model. 1. Python client should have its own version and attributes like supported api version. 2. It should be able to recognize the server's version and

Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core

2015-03-12 Thread Tan, Lin
Congratulations Ramesh B.R Tan From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Friday, March 13, 2015 12:06 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core Without further ado, and

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

2015-05-26 Thread Tan, Lin
Hi Doug and guys, I would like to work as oslo-ironic liasison to sync Ironic with Oslo. I will attend the regular Oslo meeting for sure. My IRC name is lintan, and Launchpad id is tan-lin-good Thanks Tan -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

2015-05-26 Thread Tan, Lin
Thank you for your effort and wish you luck, Ghe B.R Tan From: Ghe Rivero [mailto:g...@debian.org] Sent: Tuesday, May 26, 2015 12:46 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison My focus on the Ironic project has been

[openstack-dev] [api][ironic] some questions about tags

2015-10-21 Thread Tan, Lin
Hi guys, Ironic is implementing the tags stuff: https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bp/nodes-tagging,n,z And this work is follow the guidelines of API Workgroup: http://specs.openstack.org/openstack/api-wg/guidelines/tags.html But I have two

[openstack-dev] [ironic] The scenary to rolling upgrade Ironic

2015-10-14 Thread Tan, Lin
Hi guys, I am looking at https://bugs.launchpad.net/ironic/+bug/1502903 which is related to rolling upgrade and here is Jim's patch https://review.openstack.org/#/c/234450 I really have a concern or question about how to do Ironic doing rolling upgrades. It might be my mistake, but I would

Re: [openstack-dev] [Ironic] Stepping down from IPA core

2015-09-21 Thread Tan, Lin
It’s great to work with you, Josh. Thanks for your valuable comments and suggestions. Wish you luck in your new Job. Tan From: Josh Gachnang [mailto:j...@pcsforeducation.com] Sent: Monday, September 21, 2015 11:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

2015-11-30 Thread Tan, Lin
Hi guys I recently play around with 'x-openstack-request-id' header but have a dump question about how it works. At beginning, I thought an action across different services should use a same request-id but it looks like this is not the true. First I read the spec:

[openstack-dev] [ironic] Tooling for recovering nodes

2016-05-31 Thread Tan, Lin
Hi, Recently, I am working on a spec[1] in order to recover nodes which get stuck in deploying state, so I really expect some feedback from you guys. Ironic nodes can be stuck in deploying/deploywait/cleaning/cleanwait/inspecting/deleting if the node is reserved by a dead conductor (the

Re: [openstack-dev] [ironic] Tooling for recovering nodes

2016-05-31 Thread Tan, Lin
da van der Veen [mailto:devananda@gmail.com] Sent: Wednesday, June 1, 2016 3:26 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [ironic] Tooling for recovering nodes On 05/31/2016 01:35 AM, Dmitry Tantsur wrote: > On 05/31/2016 10:25 AM, Tan, Lin wrote: >> Hi, &

Re: [openstack-dev] [cross-project]How to make use of x-openstack-request-id

2016-01-21 Thread Tan, Lin
Thanks Kebane, I test glance/neutron/keystone with ``x-openstack-request-id`` and find something interesting. I am able to pass ``x-openstack-request-id`` to glance and it will use the UUID as its request-id. But it failed with neutron and keystone. Here is my test:

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

2016-01-25 Thread Tan, Lin
Thanks Kebane, I test glance/neutron/keystone with ``x-openstack-request-id`` and find something interesting. I am able to pass ``x-openstack-request-id`` to glance and it will use the UUID as its request-id. But it failed with neutron and keystone. Here is my test:

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

2016-01-27 Thread Tan, Lin
without req id defined to the services they behave (apart from nova having different header name) same way, but with glance the request maker has the liberty to specify request id they want to use (within configured length limits). Hopefully that clarifies it for you. - Erno From: Tan, Lin

Re: [openstack-dev] [ironic] Nominating Julia Kreger for core reviewer

2016-03-25 Thread Tan, Lin
+1! Always grateful for the invaluable comments from Julia From: Vladyslav Drok [mailto:vd...@mirantis.com] Sent: Friday, March 25, 2016 5:16 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [ironic] Nominating

[openstack-dev] [nova] no more expand/contract for live upgrade?

2016-03-19 Thread Tan, Lin
Hi, I noticed that expand/migrate/contract was revert in https://review.openstack.org/#/c/239922/ There is a new CMD 'online_data_migrations' was introduced to Nova and some data-migration scripts have been added. So I wonder will Nova keep expand the DB schema at beginning of live upgrade

Re: [openstack-dev] [ironic] upgrade support between which versions of ironic?

2016-04-19 Thread Tan, Lin
I agree this is reasonable to support all these cases in “cold upgrades” but in supports-rolling-upgrade (live upgrade in another word) case it is different and complicated and not necessary, During rolling upgrade, we will have old/new services co-existed, and we need to make services

Re: [openstack-dev] [ironic] Tooling for recovering nodes

2016-07-11 Thread Tan, Lin
: [openstack-dev] [ironic] Tooling for recovering nodes Some comments inline. On 5/31/16 12:26 PM, Devananda van der Veen wrote: > On 05/31/2016 01:35 AM, Dmitry Tantsur wrote: >> On 05/31/2016 10:25 AM, Tan, Lin wrote: >>> Hi, >>> >>> Recently, I am working on a spe