Re: [openstack-dev] [oslo.messaging]Optimize RPC performance by reusing callback queue

2017-06-08 Thread lương hữu tuấn
Hi, First of all, the correlation_id is needed for tracking the response for callback queue per client. What you said is the inefficiency of callback queue per request. In any case, callback queue is needed. About oslo_messaging, you can see the correlation_id in the driver of amqp. Br,

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

2017-05-29 Thread lương hữu tuấn
inish something upstream. No > need to explain that. All I’m worried about is getting this thing done. So > if you don’t have capacity please help transfer this work to someone else. > > Thanks > > Renat > > On 29 May 2017, 13:36 +0700, lương hữu tuấn <tuantulu...@gmail.c

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

2017-05-29 Thread lương hữu tuấn
Hi Doug and Renat, I totally agree with what Doug mentioned in the previous mail. In fact, my patch is only the used for the purpose of "implementing trust token", not for full refactoring mistral context. Since i do not have my capacity for contributing to Mistral, my commit now is for the need

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

2017-05-10 Thread lương hữu tuấn
It is well-written here in OPNFV artifact: http://artifacts.opnfv.org/availability/review/33475/development_overview/index.html Br, Tuan/Nokia On Wed, May 10, 2017 at 3:49 PM, Matt Riedemann wrote: > On 5/9/2017 1:11 PM, Waines, Greg wrote: > >> I am looking for guidance

[openstack-dev] [openstack][keystonemiddleware][oslo_context]

2017-04-13 Thread lương hữu tuấn
Hi, I am now trying to refactor the mistral context by using oslo_context. However, it turns out the error in testing of keystone (this test belongs to mistral unittest). What i saw in the error that, the below statement does not return value: auth_url = CONF.keystone_authtoken.auth_uri (

Re: [openstack-dev] [Keystone][Token expiration]

2017-04-10 Thread lương hữu tuấn
features > [2] https://docs.openstack.org/releasenotes/keystone/ocata. > html#upgrade-notes > [3] https://docs.openstack.org/ocata/config-reference/ > identity/samples/keystone.conf.html > > On Mon, Apr 3, 2017 at 7:58 AM lương hữu tuấn <tuantulu...@gmail.com> > wrote: >

Re: [openstack-dev] [Keystone][Token expiration]

2017-04-03 Thread lương hữu tuấn
have any > specific security concerns, please raise them appropriately (such as a > security bug, if necessary). > > On Mon, Apr 3, 2017 at 5:27 AM lương hữu tuấn <tuantulu...@gmail.com> > wrote: > >> Hi keystone folks, >> >> I have had a chance to tak

[openstack-dev] [Keystone][Token expiration]

2017-04-03 Thread lương hữu tuấn
Hi keystone folks, I have had a chance to take a look to this below patch for allowing the expired token and it was merged in Octaka: https://specs.openstack.org/openstack/keystone-specs/specs/keystone/ocata/allow-expired.html In our project, we also have problem with token expiration when

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

2017-03-14 Thread lương hữu tuấn
of creating extra Minxin classes. Br, Tuan On Tue, Mar 14, 2017 at 11:38 AM, Dougal Matthews <dou...@redhat.com> wrote: > > > On 14 March 2017 at 10:21, lương hữu tuấn <tuantulu...@gmail.com> wrote: > >> >> >> On Tue, Mar 14, 2017 at 10:28 AM, Do

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

2017-03-14 Thread lương hữu tuấn
On Tue, Mar 14, 2017 at 10:28 AM, Dougal Matthews <dou...@redhat.com> wrote: > > > On 13 March 2017 at 09:49, lương hữu tuấn <tuantulu...@gmail.com> wrote: > >> >> >> On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve <the...@redhat.com> wrote: >>

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

2017-03-14 Thread lương hữu tuấn
s? > > IMO, base class is still needed to define the contract that all actions > should follow. So that > a runner knew what’s possible to do with actions. > > Renat Akhmerov > @Nokia > > On 13 Mar 2017, at 16:49, lương hữu tuấn <tuantulu...@gmail.com> wrote: &

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

2017-03-13 Thread lương hữu tuấn
On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: > On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: > > > > One of the pain points for me as an action developer is the OpenStack > > actions[1]. Since they all use the same method name to retrieve the

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

2017-03-10 Thread lương hữu tuấn
Hi, I did not know about this change before but after reading the whole story, IMHO i myself love the way of keeping it as simple at this moment as you guys i think agreed on. For MixinAction or PolicyMixin, etc. we can develop them later when we have concrete case studies. Br, Tuan/Nokia On

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

2017-03-01 Thread lương hữu tuấn
+1 for me. Sorry Michal if you read this thread, I thought that you are a man by calling you Mike :d. Tuan/Nokia On Mar 1, 2017 6:04 PM, "Dougal Matthews" wrote: > > > On 1 March 2017 at 16:47, Renat Akhmerov wrote: > >> Hi, >> >> Based on the

[openstack-dev] [Tacker] Tacker upgrade vnf

2017-02-13 Thread lương hữu tuấn
Hi Tacker folks, I have my own consideration about vnf upgrade. Please correct me if i am wrong. As i saw that tacker supports the vnf update when vnfd and vnfd_id do not change. What about the situation of upgrading vnf, for instance, i would like to upgrade my vnf which is deployed with one

Re: [openstack-dev] [yaql] Yaql validating performance

2017-01-23 Thread lương hữu tuấn
st your expression and data that you use to evaluate > this expression? And times. Workflow itself has nothing to do with what > we’re discussing. > > Renat Akhmerov > @Nokia > > On 23 Jan 2017, at 21:44, lương hữu tuấn <tuantulu...@gmail.com> wrote: > > Hi guys,

Re: [openstack-dev] [yaql] Yaql validating performance

2017-01-23 Thread lương hữu tuấn
in 11262.710 ms INFO mistral.expressions.yaql_expression.InlineYAQLEvaluator [-] Function evaluate finished in 8146.324 ms .. The average value is around 10s each time of valuating. Br, Tuan On Mon, Jan 23, 2017 at 11:48 AM, lương hữu tuấn <tuantulu...@gmail.com> wrote

Re: [openstack-dev] [yaql] Yaql validating performance

2017-01-23 Thread lương hữu tuấn
ask YAQL authors to comment and help if we > realize that the problem really exists. > > I’m interested in this too since I’m always looking for ways to speed > Mistral up. > > Thanks > > Renat Akhmerov > @Nokia > > On 18 Jan 2017, at 16:25, lương hữu tuấn <tuan

Re: [openstack-dev] [yaql] Yaql validating performance

2017-01-18 Thread lương hữu tuấn
Hi Kirill, Do you have any information related to the performance of Jinja and Yaql validating. With the big size of input, yaql runs quite so slow in our case therefore we have plan to switch to jinja. Br, @Nokia/Tuan On Tue, Jan 17, 2017 at 3:02 PM, lương hữu tuấn <tuantulu...@gmail.

Re: [openstack-dev] [yaql] Yaql validating performance

2017-01-17 Thread lương hữu tuấn
fuel team encountered similar problems, I’d advice asking them > around. Also Stan (author of yaql) might shed some light on the problem =) > > -- > Kirill Zaitsev > Murano Project Tech Lead > Software Engineer at > Mirantis, Inc > > On 17 January 2017 at 15:11:52, lương hữu

Re: [openstack-dev] Yaql validating performance

2017-01-17 Thread lương hữu tuấn
. On Tue, Jan 17, 2017 at 1:10 PM, lương hữu tuấn <tuantulu...@gmail.com> wrote: > Hi, > > We are now using yaql in mistral and what we see that the process of > validating yaql expression of input takes a lot of time, especially with > the big size input. Do you guys have

[openstack-dev] Yaql validating performance

2017-01-17 Thread lương hữu tuấn
Hi, We are now using yaql in mistral and what we see that the process of validating yaql expression of input takes a lot of time, especially with the big size input. Do you guys have any information about performance of yaql? Br, @Nokia/Tuan

[openstack-dev] [glance][vsphere][datastore]

2016-10-05 Thread lương hữu tuấn
Hi, I have a problem related to glance when i try to install Openstack Liberty using Fuel MOS8.0 on top of Vsphere: - It had problem of uploading cirros image and i found out that at that time, glance-api was not working. The error is"Datacenter reference can not be None" - Then i checked the

[openstack-dev] [Fuel][Glance][Vsphere][Datastore]

2016-10-05 Thread lương hữu tuấn
Hi, I have a problem related to glance when i try to install Openstack Liberty using Fuel MOS8.0 on top of Vsphere: - It had problem of uploading cirros image and i found out that at that time, glance-api was not working. The error is"Datacenter reference can not be None" - Then i checked the

[openstack-dev] [Fuel][Glance][Vsphere][Datastore]

2016-10-05 Thread lương hữu tuấn
Hi, I have a problem related to glance when i try to install Openstack Liberty using Fuel MOS8.0 on top of Vsphere: - It had problem of uploading cirros image and i found out that at that time, glance-api was not working. The error is "Datacenter reference can not be None" - Then i checked the

Re: [openstack-dev] [Vitrage] Installation

2016-10-05 Thread lương hữu tuấn
> Best Regards, > > Alexey > > > > *From:* lương hữu tuấn [mailto:tuantulu...@gmail.com] > *Sent:* Wednesday, October 05, 2016 4:13 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Vitrage] Installation > >

Re: [openstack-dev] [Vitrage] Installation

2016-10-05 Thread lương hữu tuấn
Hi, I have another question based on the getting information of vitrage from monitoring solution. As i see that we have the default one now is nagios and with the zabbix, we just have only the script that gets information from zabbix as below:

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

2016-08-24 Thread lương hữu tuấn
Oh, my bad for the write permission of nova user. That should not be like this. Thanks Jeffrey. Cheers, T On Wed, Aug 24, 2016 at 2:39 PM, Jeffrey Zhang <zhang.lei@gmail.com> wrote: > On Wed, Aug 24, 2016 at 5:24 PM, lương hữu tuấn <tuantulu...@gmail.com> > wrote: > &

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

2016-08-24 Thread lương hữu tuấn
> On Tue, Aug 23, 2016 at 11:11 PM, Steven Dake (stdake) <std...@cisco.com> > wrote: > > > > > > > > > > > > On 8/23/16, 7:05 AM, "Gerard Braad" <m...@gbraad.nl> wrote: > > > >>On Tue, Aug 23, 2016 at 9:56 PM, lương hữu tu

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

2016-08-23 Thread lương hữu tuấn
I also prefer a dedicated user ("kolla" seems the best choice) as same as other projects in OpenStack. Cheers, Tuan On Tue, Aug 23, 2016 at 3:51 PM, Paul Bourke wrote: > In my experience operators prefer a dedicated user (kolla:kolla), though I > can't see any major

[openstack-dev] [Cinder] IBM SVC creates iSCSI initiator when using FC

2016-07-21 Thread lương hữu tuấn
Hi, We had problem when using FC for our SAN using IBM SVC in Mitaka. Each time we create an instance booted from volume, we always see another iSCSI port on SVC. All the FC ports were created on backend before. We try the change in Mitaka for setting connection protocol via extra_spec in volume

Re: [openstack-dev] [nova] theoretical race between live migration and resource audit?

2016-06-10 Thread lương hữu tuấn
Hi, Yes, it is actually a race and we have already faced a negative effect when using evacuation. Some information of cpu pinning is lost. Imagine that, in some cases, we do some re-scheduling actions (evacuate, live-migration, etc.) then immediately do the next actions (delete, resize, etc.)

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

2016-05-08 Thread lương hữu tuấn
; On 08/05/16 08:11, lương hữu tuấn wrote: > >> Hi, >> >> @Robert: I was successful to update the kernel without change the image. >> > > But that was Robert's point entirely. Installing the kernel will work > fine, but it does not get you running that kernel -

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

2016-05-08 Thread lương hữu tuấn
Hi, @Robert: I was successful to update the kernel without change the image. It seems Kolla is quite unstable. Tutj On Sun, May 8, 2016 at 5:43 AM, Hui Kang wrote: > Robert, > Thanks for you reply. Is there any way to change the VM image on the gate? > > BTW, I do see

[openstack-dev] [Nova] Automatically updating the status of service in Nova

2016-04-16 Thread lương hữu tuấn
Hi Nova stacker, In the time checking/researching for the multi agent platform in OpenStack Nova, i tried to figure out how the services (nova-compute, nova-scheduler,etc.) update themselves to the Nova db (service table)? What are the terminology behind these mechanism that agents use to update