Goutham,
Add ‘recheck’ as a comment. It will retrigger the jenkins jobs.
Thank you,
Abhishek
From: Goutham Pratapa [mailto:pratapagout...@gmail.com]
Sent: Thursday, October 05, 2017 5:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [all] Zuul
Hi all,
As of now in the current master AggregateImagePropertiesIsolation filter
returns True even if image property is not present in the host aggregate
metadata.
Example:
(1) Set below required config options in nova.conf under 'filter_scheduler'
section:
Hi Zhihao,
Have you tried, glance image-list -visibility=shared
Hope this will help.
Thank you,
Abhishek Kekane
From: zhihao wang [mailto:wangzhihao...@hotmail.com]
Sent: Thursday, September 21, 2017 4:08 AM
To: openstack-dev-requ...@lists.openstack.org; openstack
Subject: [Openstack] Fw:
Hi Brian,
Thanks a lot for appreciation.
It was a great opportunity for me to work along with you, jokke and other
peoples on glance pike cycle. A huge learning platform for me. It is my
pleasure to be a part of glance core.
Thank you,
Abhishek Kekane
From:
Hi Brian,
Thanks a lot for appreciation.
It was a great opportunity for me to work along with you, jokke and other
peoples on glance pike cycle. A huge learning platform for me. It is my
pleasure to be a part of glance core.
Thank you,
Abhishek Kekane
From:
--file gentoo_root.img
--disk-format iso --container-format bare
After this I was able to create image without any issue.
So another workaround is to set socket-timeout to higher value in
/etc/glance/glance-uwsgi.ini file.
Thank you,
Abhishek Kekane
From: Kekane, Abhishek [mailto:abhishek.kek
Someone has reported this issue in glance recently.
Please refer, https://bugs.launchpad.net/glance/+bug/1703856
I think it is same kind of failure which Andrey was mentioning.
As mentioned in the bug temporary solution is to enable the v1 api using the v1
parameter, --location instead of using
: Monday, July 10, 2017 2:01 PM
To: Kekane, Abhishek
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [openstack-dev] [masakari][nova] Allow
evacuation of instances in resized state
Hello,
as far as I know from the Openstack survey there is a very small number
Hi Saverio,
Thank you for reply.
Currently we are using Ocata release for Openstack.
Please let me know if you get any update.
Thank you,
Abhishek
-Original Message-
From: Saverio Proto [mailto:ziopr...@gmail.com]
Sent: Monday, July 10, 2017 12:52 PM
To: Kekane, Abhishek
Cc
Hi Saverio,
Thank you for reply.
Currently we are using Ocata release for Openstack.
Please let me know if you get any update.
Thank you,
Abhishek
-Original Message-
From: Saverio Proto [mailto:ziopr...@gmail.com]
Sent: Monday, July 10, 2017 12:52 PM
To: Kekane, Abhishek
Cc
Hi Operators,
Could you please let me know your opinion on below scenario? It will help me to
proceed my work.
Thank you,
Abhishek
-Original Message-
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Tuesday, July 04, 2017 2:52 PM
To: OpenStack Development Mailing
Hi Operators,
Could you please let me know your opinion on below scenario? It will help me to
proceed my work.
Thank you,
Abhishek
-Original Message-
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Tuesday, July 04, 2017 2:52 PM
To: OpenStack Development Mailing
n real
world scenario?
2. If yes is there any way to cleanup unused (*_resize) instance files from the
source compute node other than cleaning up it manually?
3. Should we add support of evacuating of resized instances in nova?
Please let me know your opinions about the same.
Thank you,
Abhishek
n real
world scenario?
2. If yes is there any way to cleanup unused (*_resize) instance files from the
source compute node other than cleaning up it manually?
3. Should we add support of evacuating of resized instances in nova?
Please let me know your opinions about the same.
Thank you,
Abhishek
Hi Nikhil,
I am very thankful for support and guidance you have provided to me and other
new members. Hoping to work with you again in near future. All the best for
your future activities.
Cheers,
Abhishek
Sent from OWA on Android
From: Nikhil Komawar
28, 2017 8:54 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [masakari][nova] Allow evacuation of instances in
resized state
On 06/28/2017 05:50 AM, Kekane, Abhishek wrote:
> In masakari, we are setting an instance to an error state if the
> vmstate is resized
Hi Devs,
Masakari [1] provides Virtual Machine High Availability (VMHA) service for
OpenStack clouds by automatically recovering the KVM-based Virtual Machine(VM)s
from failure events such as VM process down, provisioning process down, and
nova-compute host failure. It also provides API
Thank you all for your positive responses.
I will definitely put 100% efforts to justify my selection as core.
Best Regards,
Abhishek Kekane
-Original Message-
From: Brian Rosmaita [mailto:rosmaita.foss...@gmail.com]
Sent: Wednesday, June 21, 2017 4:47 PM
To: OpenStack Development
+1, agree with Nikhil.
Abhishek
From: Nikhil Komawar [mailto:nik.koma...@gmail.com]
Sent: Friday, May 26, 2017 6:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core
This is great news. Always +2 for
Thank you, Steve for your help.
Hope to see you back. .
All the best ☺
Abhishek
From: Steve Lewis [mailto:steve...@gmail.com]
Sent: Friday, May 19, 2017 9:26 AM
To: OpenStack
Subject: [openstack-dev] [glance][openstack-ansible] Moving on
It is clear to me now that I won't be able to work on
Hi All,
As per suggested by Doug, this is what we will implement.
Add new method (format_canonical_uuid()) in oslo_utils.uuidutils module which
will return valid uuid and then all other projects which are using
is_uuid_like() method needs to call this method to get valid uuid. This
approach
Hi All,
As per suggested by @jay_pipes's
if val.count('-') not in (0, 4):
raise TypeError
It is not sufficient solution because "is_uuid_like" returns only True or False.
For example,
If user passes uuid like "urn:----" or
Sorry for wrong auto-correction :)
Congratulations Dharini, All the best. .
Abhishek
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Sunday, January 29, 2017 8:39 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [glance] Propose Dharini Chandrasekar
Congratulations Sharing. .
All the best.
Abhishek
Sent from OWA on Android
From: Brian Rosmaita
Sent: Thursday, January 26, 2017 8:56:30 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [glance] Propose Dharini
Nice work Sabari, Thank you for your efforts and help you provided. Hope to see
you back in the list.
All the best,
Abhishek
-Original Message-
From: Brian Rosmaita [mailto:rosmaita.foss...@gmail.com]
Sent: Tuesday, January 24, 2017 4:32 AM
Cc: Sabari Murugesan; OpenStack Development
not true. you need to either do
"keystoneauth1 >= 2.18.0" or "keystoneauth1 > 2.17.0" and we prefer the ">="
notation i think.
Thanks,
Dims
On Fri, Jan 20, 2017 at 10:53 PM, Kekane, Abhishek
<abhishek.kek...@nttdata.com> wrote:
> Hi Dims,
>
> T
client][ python-neutronclient] Remove x-openstack-request-id
logging code as it is logged twice
On Fri, Jan 20, 2017 at 10:53 PM, Kekane, Abhishek
<abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote:
Hi Dims,
Thank you for reply. I will propose a patch soon.
oned have
"keystoneauth1>=2.17.0",
2) i do not see a review request to bump the minimum version in global
requirements for keystoneauth1 to "keystoneauth1>=2.18.0"
(https://review.openstack.org/#/q/project:openstack/requirements+is:open)
Can you please file one?
Thanks,
Dims
On Fr
Hi Devs,
In the latest keystoneauth1 version 2.18.0, x-openstack-request-id is logged
for every HTTP response. This keystoneauth1 version will be used for ocata.
The same request id is also logged in 'request' method of SessionClient class
for python-novaclient, python-glanceclient,
Sep 15, 2016 at 10:59 PM, Kekane, Abhishek
<abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote:
Hi All,
I have got invitation letter in spanish.
Those who requires this letter in spanish, send mail to
eventv...@openstack.org<mailto:eventv...@openstack.org>
amire...@gmail.com>> wrote:
That's good. Please share the appropriate link/url to openstack visa team.
On Thu, Sep 15, 2016 at 1:14 PM, Kekane, Abhishek
<abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote:
Hi,
Yes it’s request from embassy than for Indi
.
Thanks
Swami
On Thu, Sep 15, 2016 at 11:58 AM, Kekane, Abhishek
<abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote:
Hi Janki,
I will keep you posted about this. Mean time sent mail to
‘eventv...@openstack.org<mailto:eventv...@openstack.org>’ to explain yo
applying from India can request to have the letter in Spanish
too.
Let me know how you proceed further. It would help me while applying.
Thanks
Janki
On Thu, Sep 15, 2016 at 11:30 AM, Kekane, Abhishek
<abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote:
Hi John,
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Spain Visa for Indian contributors
On that page they seem to list a contact email:
eventv...@openstack.org
Hopefully they can help with the issue.
John
On Wed, Sep 14, 2016 at 9:24 PM, Kekane, Abhishek <abhishek.
on the Visa process at:
https://www.openstack.org/summit/barcelona-2016/travel/#visa
Not sure if you have already read that information.
They talk about the steps needed to get an invitation letter.
Good luck!
On Wed, Sep 14, 2016 at 8:51 PM, Kekane, Abhishek <abhishek.kek...@nttdata.com>
Hi Devs, Stackers,
While applying visa from Pune (India), I came to know that Invitation letter is
required in Spanish language and its mandatory.
Has anyone from India has faced similar kind of issue while applying for visa?
If not please let me know from which city you have applied for the
Hi Nikhil,
Thank you for your support, guidance and hard work as Glance PTL.
I have enjoyed working with you and glad to know that you will be there to help
:)
Thank you,
Abhishek
-Original Message-
From: Nikhil Komawar [mailto:nik.koma...@gmail.com]
Sent: Monday, September 12, 2016
From: John Griffith [mailto:john.griffi...@gmail.com]
Sent: Friday, August 26, 2016 10:21 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Reconciling flavors and block device
mappings
On Fri, Aug 26, 2016 at 10:20 AM, Ed Leafe
Hi Nova developers,
This is about the patch: https://review.openstack.org/#/c/200870/19
We would like to fix this issue in Newton and back port it to Mitaka.
Reason:
Ubuntu 16.04 LTS supports Mitaka release. If we wait for this fix until Ocata
release (~April 2017), then Ubuntu team might need
Hi Operators,
Could you please provide your opinion on below mail. I need to discuss this in
coming nova meeting (12 May, 2016).
Thank you,
Abhishek Kekane
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Monday, May 09, 2016 7:22 AM
To: openstack-operators
Hi All,
In Liberty release, we had upstream [1] a security fix to cleanup orphaned
instance files from compute nodes for resize operation. To fix this security
issue, a new periodic task '_cleanup_incomplete_migrations’ was introduced that
runs on each compute node which queries for deleted
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: Wednesday, March 16, 2016 8:35 PM
To: openstack-operators
Subject: Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log
request-ids in cross-projects
Excerpts from Kekane, Abhishek's message of
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: Wednesday, March 16, 2016 8:35 PM
To: openstack-operators
Subject: Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log
request-ids in cross-projects
Excerpts from Kekane, Abhishek's message of
-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: 24 March 2016 17:21
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] Block subtractive schema changes
On 24/03/16 05:42 +, Kekane, Abhishek wrote:
>
Hi Glance Team,
I have registered a blueprint [1] for blocking subtractive schema changes.
Cinder and Nova are already supporting blocking of subtractive schema
operations. Would like to add similar support here.
Please let me know your opinion on the same.
[1]
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: 15 March 2016 19:29
To: openstack-operators
Subject: Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log
request-ids in cross-projects
Excerpts from Kekane, Abhishek's message of 2016-03-15
Excerpts from Kekane, Abhishek's message of 2016-03-01 06:17:15 +:
> Hi Devs,
>
> Considering return request-id to caller specs [1] is implemented in
> python-*client, I would like to begin discussion on how these request-ids
> will be logged in cross-projects. In logging work-group
Excerpts from Kekane, Abhishek's message of 2016-03-01 06:17:15 +:
> Hi Devs,
>
> Considering return request-id to caller specs [1] is implemented in
> python-*client, I would like to begin discussion on how these request-ids
> will be logged in cross-projects. In logging work-group
Thanks for all your leadership, Flavio! Really appreciated all help from you!
Abhishek
-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: 09 March 2016 19:45
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Glance Mitaka: Passing the torch
: [openstack-dev] [all][log] Ideas to log request-ids in
cross-projects
On 01.03.2016 07:17, Kekane, Abhishek wrote:
> Hi Devs,
>
> Considering return request-id to caller specs [1] is implemented in
> python-*client, I would like to begin discussion on how these request-ids
> will be
: [openstack-dev] [all][log] Ideas to log request-ids in
cross-projects
On 01.03.2016 07:17, Kekane, Abhishek wrote:
> Hi Devs,
>
> Considering return request-id to caller specs [1] is implemented in
> python-*client, I would like to begin discussion on how these request-ids
> will be
Hi Devs,
Considering return request-id to caller specs [1] is implemented in
python-*client, I would like to begin discussion on how these request-ids
will be logged in cross-projects. In logging work-group meeting (11-Nov-2015)
[2] there was a discussion about how to log request-id in the log
hishek
> [1]
> http://git.openstack.org/cgit/openstack/python-neutronclient/tree/tox.ini#n26
> [2]
> http://git.openstack.org/cgit/openstack/python-openstackclient/tree/tox.ini#n15
> [3] http://git.openstack.org/cgit/openstack/python-novaclient/tree/tox.ini#n24
From: Kekane, Abhishek [mailto:a
-Original Message-
From: Andreas Jaeger [mailto:a...@suse.com]
Sent: 19 January 2016 15:19
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][clients] Enable hacking in python-*clients
On 2016-01-19 10:44, Abhishek Kekane wrote:
>> Hi
Hi Devs,
As of now all OpenStack projects has hacking checks which take cares about
OpenStack guidelines issues are caught while running PEP8 checks using tox.
There are no such checks in any of the python-*client.
IMO its worth to enable hacking checks in python-*clients as well which will
Hi Devs,
I have submitted a cross-project specs [1] for returning request-id to the
caller which was approved. For implementation we have submitted patches in
python-cinderclient [2] as per design in cross-project specs. However we have
found one issue while implementing this design in
-Original Message-
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: 10 December 2015 12:56
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [python-glanceclient] Return request-id to caller
-Original Message-
From
Hi Devs,
We are adding support for returning 'x-openstack-request-id' to the caller as
per the design proposed in cross-project specs:
http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html
Problem Description:
Cannot add a new property of list type to the
:33 +0000, Kekane, Abhishek wrote:
> >Hi Devs,
> >
> >
> >
> >We are adding support for returning ‘x-openstack-request-id’ to the
> >caller as per the design proposed in cross-project specs:
> >
> >http://specs.openstack.org/opensta
:09:10 -0430:
>> On 09/12/15 11:33 +0000, Kekane, Abhishek wrote:
>>> Hi Devs,
>>>
>>>
>>>
>>> We are adding support for returning ?x-openstack-request-id? to the caller
>>> as
>>> per the design proposed in cross-project s
Hi Tan,
Most of the OpenStack RESTful API returns `X-Openstack-Request-Id` in the API
response header but this request id is not available to the caller from the
python client.
When you use --debug option from command from the command prompt using client,
you can see
Hi Operators,
I have added a nova-specs [1] which talks about improving performance of
unshelve api which we want to implement during Mitaka release.
We have following use cases for the same.
1. User wants unshelving instance to be faster irrespective of how the instance
is booted (EBS volume
on it!!
Abhishek
On Fri, Nov 20, 2015 at 2:32 AM, Kekane, Abhishek <abhishek.kek...@nttdata.com>
wrote:
> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: 16 November 2015 21:46
> To: openstack-dev
> Subject: Re: [openstack-dev] [oslo]
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: 16 November 2015 21:46
To: openstack-dev
Subject: Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils
Excerpts from Kekane, Abhishek's message of 2015-11-16 07:33:48 +:
> Hi,
>
> As apiclient is
Hi Devs,
As per mentioned in cross-project specs [1] 'Proposed Change' section, I would
like to proceed with adding 'request-id' attribute to base exception class.
request-id is most needed when api returns anything >= 400 error code. As of
now python-cinderclient, python-keystoneclient and
Hi,
As apiclient is now removed from oslo-incubator, to proceed with request-id
spec [1] I have two options in mind,
1. Use keystoneauth1 + cliff in all python-clients (add request-id
support in cliff library)
2. apiclient code is available in all python-*clients, modify this
Hi Devs,
In the Mitaka design summit session [1], it was decided to create a new
library apiclient with completely new code (Metadata classes) and copy
only code from oslo-incubator/openstack/common/apiclient that is needed by
all python clients libraries.
We have done extensive analysis to
Hi Devs,
Nova shared storage has issue [1] for counting free space, total space and disk
available least which affects hypervisor stats and scheduler.
I have created a etherpad [2] which contains detail problem description and
possible solution with possible challenges for this design.
Later I
Hi Jay,
Thank you for the update.
Abhishek Kekane
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 30 September 2015 15:48
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Shared storage space count for Nova
On 09/30/2015 03:04 AM, Kekane
Hi Sean,
Author of specs is Eric Harney, If he is ok with it then I will submit the
patch for moving specs to Mitaka.
Thank you,
Abhishek Kekane
-Original Message-
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: 29 September 2015 17:47
To: OpenStack Development
Hi Devs,
The cinder-specs [1] for snapshot and cloning NFS backend submitted by Eric was
approved in Kilo but due to nova issue [2] it is not implemented in Kilo and
Liberty.
I am discussing about this nova bug with nova team for finding possible
solutions and Nikola has given some pointers
] [cinder] snapshot and cloning for NFS backend
On Tue, Sep 29, 2015 at 06:26:06AM +, Kekane, Abhishek wrote:
> Hi Devs,
>
> The cinder-specs [1] for snapshot and cloning NFS backend submitted by Eric
> was approved in Kilo but due to nova issue [2] it is not implemented in Kilo
&
Hi,
There is a bug for this, you can add murano projects to this bug.
https://bugs.launchpad.net/heat/+bug/1259292
Thanks,
Abhishek Kekane
-Original Message-
From: Bulat Gaifullin [mailto:bgaiful...@mirantis.com]
Sent: 24 September 2015 13:29
To: OpenStack Development Mailing List
Hi All,
I am working on "Returning request-id to caller".
Please refer, https://review.openstack.org/#/c/156508
To implement this specs in cross-projects it is also required to move
oslo-incubator to private modules.
IMO moving oslo-incubator/openstack as a private module
Hi Mahendra,
openstack-dev mailing list is proper mailing list to ask this question.
There are many locations which are populating compute_nodes records, one of
them is hypervisor-stats.
Please check
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/hypervisors.py#L91
Hi Andrew,
My launchpad id is abhishek-kekane
Thank you,
Abhishek
From: Andrew Melton [andrew.mel...@rackspace.com]
Sent: Monday, September 21, 2015 10:54 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] New
Thank you Michal,
Abhishek
-Original Message-
From: Dulko, Michal [mailto:michal.du...@intel.com]
Sent: 16 September 2015 15:23
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Pycharm License for OpenStack developers
> From: Kek
AM, Kekane, Abhishek wrote:
Hi Devs,
There is an NFS backend driver for cinder, which supports only limited
volume handling features. Specifically, snapshot and cloning
features are missing.
Eric Harney has proposed a feature of NFS driver snapshot [1][2][3],
which was approved
Hi Nova Devs,
I have submitted a nova-specs for liberty but as it is not approved I have
moved it under liberty/backlog.
Now mitaka specs directory is added in nova-specs.
Should it be ok to move nova-specs from specs/liberty/backlog/approved to
specs/mitaka/approved directory?
Please let me
Hi Devs,
I have modified the cross-project specs for request-id based on this analysis
and submitted same for review.
Please refer,
https://review.openstack.org/#/c/156508/17/specs/return-request-id.rst and give
your valuable feedback on the same.
Thank you in advance.
Abhishek Kekane
Hi Devs,
There is an NFS backend driver for cinder, which supports only limited volume
handling features. Specifically, snapshot and cloning features are missing.
Eric Harney has proposed a feature of NFS driver snapshot [1][2][3], which
was approved on Dec 2014 but not implemented yet.
[1]
driver would be great !
[4] https://review.openstack.org/#/c/149037/
Jordan
On Tue, Jul 28, 2015 at 10:00 AM, Kekane, Abhishek
abhishek.kek...@nttdata.commailto:abhishek.kek...@nttdata.com wrote:
Hi Devs,
There is an NFS backend driver for cinder, which supports only limited volume
handling
Hi Devs,
X-Openstack-Request-Id. We have analysed python-cinderclient,
python-glanceclient, python-novaclient, python-keystoneclient and
python-neutronclient to check the return types.
There are 9 ways return values are returned from python clients:
1. List
2. Dict
3. Resource class object
4.
Kekane, Abhishek would like to recall the message, [Nova] [Liberty] Approval
dates for non-priority specs .
__
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may
Hi Nova Devs,
I have submitted a nova spec [1] for improving unshelve api performance.
It's not listed under the liberty priorities, in spec also I have set project
priority as None and in Launchpad blueprint [2] also milestone target is None.
As per nova liberty schedule, June 23-25, 2015 were
Hi Nova Devs,
I have submitted a nova spec [1] for improving unshelve api performance.
It's not listed under the liberty priorities, in spec also I have set project
priority as None and in Launchpad blueprint [2] also milestone target is None.
As per nova liberty schedule, June 23-25, 2015 were
Kekane, Abhishek would like to recall the message, [Nova] [Liberty] Approval
dates for non-priority specs .
__
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may
on Solution 1
On 5/28/15 2:14 AM, Kekane, Abhishek wrote:
Hi Devs,
Thank you for your opinions/thoughts.
However I would like to suggest that please give +1 against the
solution which you will like to propose so that at the end it will be
helpful for us to consolidate the voting
with while adopting a cross project
solution. If our logs follow certain prefix and or suffix style across
projects, that would help a long way.
Personally: +1 on Solution 1
On 5/28/15 2:14 AM, Kekane, Abhishek wrote:
Hi Devs,
Thank you for your opinions/thoughts.
However I would like
.
Abhishek Kekane
From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: 28 May 2015 00:31
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
On Wed, May 27, 2015 at 12:06 AM, Kekane, Abhishek
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses. This
request ID can be useful for tracking down problems in the logs. However, when
operation crosses service boundaries, this tracking can become difficult, as
each service has its own request ID. Request ID is not
Hi Devs,
Earlier request_utils module was removed from oslo-incubator [1] as it was not
used.
Now we want to use this module for logging request-id across
openstack-services [2].
I have submitted a patch [3] to add request_utils module back to oslo-incubator.
If anyone has suggestions please
Hi Devs,
I have couple of questions regarding cells V2.
Once cells V2 is implemented then there will be no concept on non-cell
deployment which means there will be one cell at least (by default).
1. How the deployment with multiple availability zones done with cells V2?
2. How the availability
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization
Questions
Hi,
On 11 March 2015 at 06:35, Kekane, Abhishek abhishek.kek...@nttdata.com wrote:
In case of start/stop API’s cpu/memory are not released/reassigned. We
can
(not for usage questions)
Subject: Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization
Questions
Hi,
On 11 March 2015 at 06:35, Kekane, Abhishek abhishek.kek...@nttdata.com wrote:
In case of start/stop API’s cpu/memory are not released/reassigned. We
can modify these API’s to release
/
Please let me know your opinion, whether we can modify start/stop API’s as an
alternative to shelve/unshelve API’s.
Thank You,
Abhishek Kekane
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: 24 February 2015 12:47
To: OpenStack Development Mailing List (not for usage
You,
Abhishek Kekane
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: 24 February 2015 12:47
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization
Questions
Hi Duncan,
Thank you
Hi Michal,
1. Need of distributed lock to avoid same task being resumed by two instances
of a service. Do we need tooz to do that or is there any other solution?
Tooz library is already being used in ceilometer to manage group membership.
Hi Devs,
Problem Statement: Performance and storage efficiency of shelving/unshelving
instance booted from image is far worse than instance booted from volume.
When you unshelve hundreds of instances at the same time, instance spawning
time varies and it mainly depends on the size of the
Hi Devs,
This change is not backward compatible and to do not break OpenStack services
which are using cinder-client,
we need to first make provision in these consumer services to handle
cinder-client return type change.
To make this cinder-client change backward compatible we need to do
1 - 100 of 119 matches
Mail list logo