Re: [openstack-dev] Get Tenant Details in novaclient

[Chen CH Ji]

this spec has some thought on functionality to validate the tenant or user
that is consumed by nova, not sure whether it's what you want, FYI

https://review.openstack.org/#/c/92507/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Sachi Gupta sachi.gu...@tcs.com
To: openstack-dev@lists.openstack.org,
Date:   08/13/2014 01:58 PM
Subject:[openstack-dev] Get Tenant Details in novaclient



Hi,

nova --os-tenant-name admin list --tenant c40ad5830e194f2296ad11a96cefc487
--all-tenants 1 - Works Fine and returns all the servers available where
c40ad5830e194f2296ad11a96cefc487  is the id of the demo tenant whereas
nova --os-tenant-name admin list --tenant demo --all-tenants 1 - Returns
nothing when tenant-name demo is passed in place of its id.

For the above bug, need to get the tenant details in novaclient on the
basis of tenant-name being passed to nova api so that the list of servers
can be shown up by both tenant_name or tenant_id.

Also, to interact between Openstaack components we can use the rest calls.

Can anyone suggest how to get the keystone tenant-details in novaclient to
make the above functionality work.

Thanks in advance
Sachi


=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] China blocking access to OpenStack git review push

[Chen CH Ji]

It was found more than weeks before, I asked this question through IRC and
finally found it's GFW issue

the easiest way is to find a server outside China and use ssh tunnel
solution, at least it works for me and other colleagues here

ssh -N -f -L 29418:review.openstack.org:29418 $server_in_US
then mapping review.openstack.org to local host in /etc/hosts.

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   09/09/2014 05:28 AM
Subject:Re: [openstack-dev] China blocking access to OpenStack git
review push





On 9/8/2014 2:20 PM, Thomas Goirand wrote:
 Am I dreaming, or is the Chinese government is trying to push for the
 cloud, they said. However, today, bad surprise:

 # nmap -p 29418 23.253.232.87

 Starting Nmap 6.00 ( http://nmap.org ) at 2014-09-09 03:10 CST
 Nmap scan report for review.openstack.org (23.253.232.87)
 Host is up (0.21s latency).
 PORT  STATESERVICE
 29418/tcp filtered unknown

 Oh dear ... not fun!

 FYI, this is from China Unicom (eg: CNC Group)

 I'm guessing that this is the Great Firewall of China awesome automated
 ban script which detected too many ssh connection to a weird port. It
 has blocked a few of my servers recently too, as it became a way too
 aggressive. I very much prefer to use my laptop to use git review than
 having to bounce around servers. :(

 Are their alternative IPs that I could use for review.openstack.org?

 Cheers,

 Thomas Goirand (zigo)

 P.S: If a Chinese official read this, an easy way to unlist (legitimate)
 servers access would be the first action any reasonable Chinese
 government people must do.

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Yeah the IBM DB2 third party CI is run from a team in China and they've
been blocked for a few weeks now.

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] libvirt boot parameters

[Chen CH Ji]

whether following variables fit for your purpose? guess you want to
override the value through boot command?

cfg.IntOpt(reboot_timeout,
   default=0,
   help=Automatically hard reboot an instance if it has been 
stuck in a rebooting state longer than N seconds. 
Set to 0 to disable.),
cfg.IntOpt(instance_build_timeout,
   default=0,
   help=Amount of time in seconds an instance can be in BUILD

before going into ERROR status.
Set to 0 to disable.),

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Angelo Matarazzo angelo.matara...@dektech.com.au
To: openstack-dev@lists.openstack.org
Date:   09/22/2014 05:30 PM
Subject:[openstack-dev] [nova] libvirt boot parameters



Hi all,
I need to add the option rebootTimeout when the instance boots.


If you use the qemu-kvm, boot parameter reboot-timeout allows  a virtual
machine to retry booting if no bootable device is found:

# qemu-kvm --boot reboot-timeout=1000

Ref:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html


In Openstack a new boot parameter should be entered into Libvirt XML
attributes where required:

bios rebootTimeout=5000 / under the os in the libvirt.xml file.

My idea is to add an option to nova boot command changing  (nova API, nova
base,python-novaclient) but I would like to know what you think about that?


Thank you beforehand
Angelo
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Glance][Nova] Does glance support upper case key/value pair?

[Chen CH Ji]

Got following result when doing bug analysis on nova , is this key/pair
uppercase - lowercase was done by purpose or a restriction? It might be
related to a nova defect, thanks

jichen@cloudcontroller:~$ glance image-update --property Key1=Value2
--purge-props 64f067bd-ce03-4f04-a354-7188a4828e8e
+--+--+
| Property | Value|
+--+--+
| Property 'key1'  | Value2   |

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Should claim fail return all failed reason or the reason of first unsatisfied resource ?

[Chen CH Ji]

Hi
   I am working on https://review.openstack.org/#/c/61359/
and its purpose is to include reason in the exception message when claim
failed
   There are 2 choice for the reasons returned, one is to
return all reasons (e.g both cpu and mem can't be claimed successfully,
both of error info will be returned)
   Or return the first reason whichever resource claim
failed(this is the original way ), do any one know any convention for this
kind of situation?

   Thanks


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] offline check inconsistent configuration during compute and api nodes

[Chen CH Ji]

According to https://bugs.launchpad.net/nova/+bug/1270726

We might have several API node and lot of compute nodes in a cloud,
for example, nova configuration assume instance_name_template should be
same in all nodes; otherwise there is
a potential issue as the bug indicated. I analyzed and I think it's not
easy to find this kind of error configuration in nova .
so do any one has idea on how to handle this kind of problem?
This kind of problem can also be you copied nova.conf but you forget to
change my_ip and it's time consuming to find this problem

we may
1) leave it to admin to guarantee
2) ask other component such as chef or heat ?
3) in nova code to check
4) Do a healthy checker tool to report potential wrong configuration

Any one has any suggestion for it? Thanks



Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] Question about concurrent access of multiple API server

[Chen CH Ji]

According to this bug https://bugs.launchpad.net/nova/+bug/1268569

I am wondering someone can help me in understanding the concurrent access
prevention on api layer?

if we have more than 1 nova-api server, let's say 2(thread A and thread
B) ,so both of them should be able to handle request from user
let's say we delete same floating ip 2 times at almost same time,
if thread A and B both pass the test in following logic (that's possible
because they run concurrently)

api/openstack/compute/contrib/floating_ips.py
def delete(self, req, id):
..
try:
floating_ip = self.network_api.get_floating_ip(context, id)
except (exception.NotFound, exception.InvalidID):
msg = _(Floating ip not found for id %s) % id
raise webob.exc.HTTPNotFound(explanation=msg)
..

then both of them will call following function
self.network_api.release_floating_ip(context, address)

at last function deallocate_floating_ip in nova/network/float_ips.py will
be called by both A and B ,this will not lead to logic error
because db layer will not return error if it can't find the floating_ip
but quota will be reserve and commit 2 times, that lead to wrong quota
error

Could someone help to clarify my understanding or any help on what kind of
concurrent access prevention we have ?


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

[Chen CH Ji]

do a code review and found a function _reclaim_queued_deletes will do the
soft_delete reclaim

if you set reclaim_instance_interval  0 , then delete will be soft_delete
and it will be reclaimed if it's old enough
by default reclaim_instance_interval is 0, so delete will be hard delete ,
user can trigger a force_delete action should delete the instance right now

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   zhangyu (AI) zhangy...@huawei.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   03/07/2014 09:09 AM
Subject:Re: [openstack-dev] [Nova][Cinder] Feature about volume
delete  protection



After looking into Nova code base, I found there is surely a soft_delete()
method in the ComputeDriver() class. Furthermore,
Xenapi (and only Xenapi) has implemented this method, which finally applies
a hard_shutdown_vm() operation to the instance to be deleted.
If I understand it correctly, it means the instance is in fact shutdown,
instead of being deleted. Later, the user can decide whether to restore it
or not.

My question is that, when and how is the soft_deleted instance truly
deleted? A user needs to trigger a real delete operation on it explicitly,
doesn't he?

Not for sure why other drivers, especially libvirt, did not implement such
a feature...

Thanks~

-Original Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
Sent: Thursday, March 06, 2014 8:13 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Cinder] Feature about volume delete
protection

On 6 March 2014 08:50, zhangyu (AI) zhangy...@huawei.com wrote:
 It seems to be an interesting idea. In fact, a China-based public
 IaaS, QingCloud, has provided a similar feature to their virtual
 servers. Within 2 hours after a virtual server is deleted, the server
owner can decide whether or not to cancel this deletion and re-cycle that
deleted virtual server.

 People make mistakes, while such a feature helps in urgent cases. Any
idea here?

Nova has soft_delete and restore for servers. That sounds similar?

John


 -Original Message-
 From: Zhangleiqiang [mailto:zhangleiqi...@huawei.com]
 Sent: Thursday, March 06, 2014 2:19 PM
 To: OpenStack Development Mailing List (not for usage questions)
 Subject: [openstack-dev] [Nova][Cinder] Feature about volume delete
 protection

 Hi all,

 Current openstack provide the delete volume function to the user.
 But it seems there is no any protection for user's delete operation miss.

 As we know the data in the volume maybe very important and valuable.
 So it's better to provide a method to the user to avoid the volume delete
miss.

 Such as:
 We can provide a safe delete for the volume.
 User can specify how long the volume will be delay deleted(actually
deleted) when he deletes the volume.
 Before the volume is actually deleted, user can cancel the delete
operation and find back the volume.
 After the specified time, the volume will be actually deleted by the
system.

 Any thoughts? Welcome any advices.

 Best regards to you.


 --
 zhangleiqiang

 Best Regards



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

inline: graycol.gif___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Question about Ephemeral/swap disk and flavor

[Chen CH Ji]

Hi
 We are trying to fix some eph disk related bugs and also
considering our private driver implementation based for eph disk
 I have some questions related ephemeral_gb in flavor and nova
boot option --ephemeral, and I failed to find out descriptions in
existing documents:

   1.   If I boot a new instance using flavor with ephemeral_gb defined as
  20 G, and no --ephemeral specified, does the new instance have a
  20G additional ephemeral disk after booted?
   2.   The flavor has 20 G ephemeral disk defined, but specified two 5 G
  ephemeral disk through --ephemeral option in nova boot cmd, what
  will happen to the new instance? Get one 20G additional ephemeral? Or
  two 5 G ephemeral disks instead?
   3.   If the answer to question 2 is two 5 G ephemeral disks, what will
  happen if resize this instance to a flavor with ephemeral_gb
  defined as 40 G?
   4.   I think the ephemeral_gb in flavor means maximum disk size you
  can specified, is this understanding correct?
   5.   Also, above question can be applied to swap disk

Asked here and reply guess developers who made this feature can give more
info:
https://ask.openstack.org/en/question/25088/ephemeral_gb-in-flavor-and-nova-boot-option-ephemeral/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] add configuration item to set virtual machine swapfile location

[Chen CH Ji]

if it's local disk to host , +1 since we might get better performance
btw, the base file is in /var/lib/nova/instances/_base/swap_xxx, also need
to be considered



Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Yuzhou (C) vitas.yuz...@huawei.com
To: openstack-dev@lists.openstack.org
openstack-dev@lists.openstack.org,
Date:   03/19/2014 05:39 PM
Subject:[openstack-dev] [nova] add configuration item to set virtual
machine swapfile location



Hi everyone,

 Currently, disk.swap(the swapfile of instance) is created on
the instances_path(deflaut : /var/lib/nova/instances/vm-uuid). Maybe we
should add configuration item in nova.conf to set virtual machine swapfile
location. With such a feature enabled, swapfiles can be placed onto a
specified storage, e.g. a SSD, seperatedly.

Thanks,

Zhou Yu

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

inline: graycol.gif___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova][Trove] Managed Instances Feature

[Chen CH Ji]

the instance lock is a mechanism that prevent non-admin user to operate on
the instance (resize, etc, looks to me snapshot is not currently included)
the permission is a wider concept that major in API layer to allow or
prevent user in using the API , guess instance lock might be enough for
prevent instance actions .


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Hopper, Justin justin.hop...@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   04/08/2014 02:05 PM
Subject:Re: [openstack-dev] [Nova][Trove] Managed Instances Feature



Phil,

I am reviewing the existing “check_instance_lock” implementation to see
how it might be leveraged.  Off the cuff, it looks pretty much what we
need.  I need to look into the permissions to better understand how one
can “lock” and instance.

Thanks for the guidance.


Justin Hopper
Software Engineer - DBaaS
irc: juice | gpg: EA238CF3 | twt: @justinhopper




On 4/7/14, 10:01, Day, Phil philip@hp.com wrote:

I can see the case for Trove being to create an instance within a
customer's tenant (if nothing else it would make adding it onto their
Neutron network a lot easier), but I'm wondering why it really needs to
be hidden from them ?

If the instances have a name that makes it pretty obvious that Trove
created them, and the user presumably knows that did this from Trove, why
hide them  ?I'd of thought that would lead to a whole bunch of
confusion and support calls when they  try to work out why they are out
of quota and can only see subset of the instances being counted by the
system.

If the need is to stop the users doing something with those instances
then maybe we need an extension to the lock mechanism such that a lock
can be made by a specific user (so the trove user in the same tenant
could lock the instance so that a non-trove user in that tenant couldn’t
unlock ).  We already have this to an extent, in that an instance locked
by an admin can' t be unlocked by the owner, so I don’t think it would be
too hard to build on that.   Feels like that would be a lot more
transparent than trying to obfuscate the instances themselves.

 -Original Message-
 From: Hopper, Justin
 Sent: 06 April 2014 01:37
 To: OpenStack Development Mailing List (not for usage questions)
 Subject: Re: [openstack-dev] [Nova][Trove] Managed Instances Feature

 Russell,

 Thanks for the quick reply. If I understand what you are suggesting it
is that
 there would be one Trove-Service Tenant/User that owns all instances
from
 the perspective of Nova.  This was one option proposed during our
 discussions.  However, what we thought would be best is to continue to
use
 the user credentials so that Nova has the correct association.  We
wanted a
 more substantial and deliberate relationship between Nova and a
 dependent service.  In this relationship, Nova would acknowledge which
 instances are being managed by which Services and while ownership was
still
 to that of the User, management/manipulation of said Instance would be
 solely done by the Service.

 At this point the guard that Nova needs to provide around the instance
does
 not need to be complex.  It would even suffice to keep those instances
 hidden from such operations as ³nova list² when invoked by directly by
the
 user.

 Thanks,

 Justin Hopper
 Software Engineer - DBaaS
 irc: juice | gpg: EA238CF3 | twt: @justinhopper




 On 4/5/14, 14:20, Russell Bryant rbry...@redhat.com wrote:

 On 04/04/2014 08:12 PM, Hopper, Justin wrote:
  Greetings,
 
  I am trying to address an issue from certain perspectives and I think
  some support from Nova may be needed.
 
  _Problem_
  Services like Trove use run in Nova Compute Instances.  These
  Services try to provide an integrated and stable platform for which
  the ³service² can run in a predictable manner.  Such elements include
  configuration of the service, networking, installed packages, etc.
  In today¹s world, when Trove spins up an Instance to deploy a
  database on, it creates that Instance with the Users Credentials.
  Thus, to Nova, the User has full access to that Instance through
  Nova¹s API.  This access can be used in ways which unintentionally
 compromise the service.
 
  _Solution_
  A proposal is being formed that would put such Instances in a
  read-only or invisible mode from the perspective of Nova.  That is,
  the Instance can only be managed from the Service from which it was
  created.  At this point, we do not need any granular controls.  A
  simple lock-down of the Nova API for these Instances would suffice.
  However, Trove would still need to interact with this Instance via
Nova
 API.
 
  The basic requirements for Nova would beŠ
 
  A way to identify

[openstack-dev] [Nova] Re:Question about addit log in nova-compute.log

[Chen CH Ji]

Hi
 [1] asked the opinion about nova-compute log questions and
I proposed [2] as the changes for it ,
 Can someone take a look and share your opinion? Thanks a
lot

[1] http://lists.openstack.org/pipermail/openstack-dev/2014-May/034312.html
[2] https://review.openstack.org/#/c/93261

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] Question about thread safe of key-pair and securtiy rules quota

[Chen CH Ji]

According to bug [1], there are some possibilities that concurrent
operations on keypair/security rules can exceed quota
Found that we have 3 kinds of resources in quotas.py:
ReservableResource/AbsoluteResource/CountableResource

curious about CountableResource because it's can't be thread safe due to
its logic:

count = QUOTAS.count(context, 'security_group_rules', id)
try:
projected = count + len(vals)
QUOTAS.limit_check(context, security_group_rules=projected)

was it designed by purpose to be different to ReservableResource? If set it
to ReservableResource just like RAM/CPU, what kind of side effect it might
lead to ?

Also, is it possible to consider a solution like 'hold a write lock in db
layer, check the count of resource and raise exception if it exceed quota'?

Thanks


[1] https://bugs.launchpad.net/nova/+bug/1301532

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Questions on instance_system_metadata rows not being deleted

[Chen CH Ji]

Hi
   I am working on this bug [1] and [2] was submitted to try to
fix it, unfortunately seems both way I can image failed to pass Jenkins
test
   Do anyone have any idea on how to handle this problem or any
mail has conclusion about it? Thanks for support ~

[1] https://bugs.launchpad.net/nova/+bug/1226049
[2]https://review.openstack.org/#/c/109201/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

[Chen CH Ji]

Big +1

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Sagar Nikam sagar.r.ni...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   08/01/2014 11:21 AM
Subject:Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core



+1

Regards,
Sagar


On Thu, Jul 31, 2014 at 2:32 AM, Michael Still mi...@stillhq.com wrote:
  Greetings,

  I would like to nominate Jay Pipes for the nova-core team.

  Jay has been involved with nova for a long time now.  He's previously
  been a nova core, as well as a glance core (and PTL). He's been around
  so long that there are probably other types of core status I have
  missed.

  Please respond with +1s or any concerns.

  References:

    https://review.openstack.org/#/q/owner:%22jay+pipes%22+status:open,n,z

    https://review.openstack.org/#/q/reviewer:%22jay+pipes%22,n,z

    http://stackalytics.com/?module=nova-groupuser_id=jaypipes

  As a reminder, we use the voting process outlined at
  https://wiki.openstack.org/wiki/Nova/CoreTeam to add members to our
  core team.

  Thanks,
  Michael

  --
  Rackspace Australia

  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] libvirtError: XML error: Missing CPU model name on 2nd level vm

[Chen CH Ji]

Hi
  I don't have a real PC to so created a test env ,so I
created a 2nd level env (create a kvm virtual machine on top of a physical
host then run devstack o the vm)
  I am not sure whether it's doable because I saw following
error when start nova-compute service , is it a bug or I need to update my
configuration instead? thanks


2014-08-01 17:04:51.532 DEBUG nova.virt.libvirt.config [-] Generated XML
('cpu\n  archx86_64/arch\n  topology sockets=1 cores=1
threads=1/\n/cpu\n',)  from (pid=16956)
to_xml /opt/stack/nova/nova/virt/libvirt/config.py:79
Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346,
in fire_timers
timer()
  File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56,
in __call__
cb(*args, **kw)
  File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 163, in
_do_send
waiter.switch(result)
  File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line
194, in main
result = function(*args, **kwargs)
  File /opt/stack/nova/nova/openstack/common/service.py, line 490, in
run_service
service.start()
  File /opt/stack/nova/nova/service.py, line 164, in start
self.manager.init_host()
  File /opt/stack/nova/nova/compute/manager.py, line 1055, in init_host
self.driver.init_host(host=self.host)
  File /opt/stack/nova/nova/virt/libvirt/driver.py, line 633, in
init_host
self._do_quality_warnings()
  File /opt/stack/nova/nova/virt/libvirt/driver.py, line 616, in
_do_quality_warnings
caps = self._get_host_capabilities()
  File /opt/stack/nova/nova/virt/libvirt/driver.py, line 2942, in
_get_host_capabilities
libvirt.VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES)
  File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in
doit
result = proxy_call(self._autowrap, f, *args, **kwargs)
  File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in
proxy_call
rv = execute(f,*args,**kwargs)
  File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in
tworker
rv = meth(*args,**kwargs)
  File /usr/lib/python2.7/dist-packages/libvirt.py, line 3127, in
baselineCPU
if ret is None: raise libvirtError ('virConnectBaselineCPU() failed',
conn=self)
libvirtError: XML error: Missing CPU model name

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] libvirtError: XML error: Missing CPU model name on 2nd level vm

[Chen CH Ji]

Thanks a lot for your suggestions , I guess it might be 2nd level
configuration issue ... will take more time on it , thanks


my 1st level host has following output when 'virsh capabilities'

host
uuidc476d525-bba7-e211-98a9-9cd4d92d1300/uuid
cpu
  archx86_64/arch
  modelSandyBridge/model
  vendorIntel/vendor
  topology sockets='1' cores='4' threads='1'/
  feature name='erms'/
  feature name='smep'/
  feature name='fsgsbase'/
  feature name='rdrand'/
  feature name='f16c'/
  feature name='osxsave'/
  feature name='pcid'/
  feature name='pdcm'/
  feature name='xtpr'/
  feature name='tm2'/
  feature name='est'/
  feature name='smx'/
  feature name='vmx'/
  feature name='ds_cpl'/
  feature name='monitor'/
  feature name='dtes64'/
  feature name='pbe'/
  feature name='tm'/
  feature name='ht'/
  feature name='ss'/
  feature name='acpi'/
  feature name='ds'/
  feature name='vme'/
/cpu

while the output on 2nd level is

host
uuida1bb0066-80d2-f9db-aa4e-0520a0562875/uuid
cpu
  archx86_64/arch
  topology sockets='1' cores='1' threads='1'/
/cpu




Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Rafael Folco rafaelfo...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   08/06/2014 02:11 AM
Subject:Re: [openstack-dev] [nova] libvirtError: XML error: Missing CPU
model name on 2nd level vm



cat /proc/cpuinfo
Make sure the cpu model and version is listed
on /usr/share/libvirt/cpu_map.xml

Hope this helps.




On Tue, Aug 5, 2014 at 2:49 PM, Solly Ross sr...@redhat.com wrote:
  Hi Kevin,
  Running devstack in a VM is perfectly doable.  Many developers use
  devstack inside a VM (I run mine inside a VM launched using libvirt
  on KVM).  I can't comment on the issue that you're encountering,
  but perhaps something wasn't configured correctly when you launched the
  VM?

  Best Regards,
  Solly Ross

  - Original Message -
   From: Chen CH Ji jiche...@cn.ibm.com
   To: openstack-dev@lists.openstack.org
   Sent: Friday, August 1, 2014 5:04:16 AM
   Subject: [openstack-dev] [nova] libvirtError: XML error: Missing CPU
  model name on 2nd level vm
  
  
  
   Hi
   I don't have a real PC to so created a test env ,so I created a 2nd
  level env
   (create a kvm virtual machine on top of a physical host then run
  devstack o
   the vm)
   I am not sure whether it's doable because I saw following error when
  start
   nova-compute service , is it a bug or I need to update my configuration
   instead? thanks
  
  
   2014-08-01 17:04:51.532 DEBUG nova.virt.libvirt.config [-] Generated
  XML
   ('cpu\n archx86_64/arch\n topology sockets=1 cores=1
   threads=1/\n/cpu\n',) from (pid=16956) to_xml
   /opt/stack/nova/nova/virt/libvirt/config.py:79
   Traceback (most recent call last):
   File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346,
  in
   fire_timers
   timer()
   File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line
  56, in
   __call__
   cb(*args, **kw)
   File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 163, in
   _do_send
   waiter.switch(result)
   File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line
  194, in
   main
   result = function(*args, **kwargs)
   File /opt/stack/nova/nova/openstack/common/service.py, line 490, in
   run_service
   service.start()
   File /opt/stack/nova/nova/service.py, line 164, in start
   self.manager.init_host()
   File /opt/stack/nova/nova/compute/manager.py, line 1055, in init_host
   self.driver.init_host(host=self.host)
   File /opt/stack/nova/nova/virt/libvirt/driver.py, line 633, in
  init_host
   self._do_quality_warnings()
   File /opt/stack/nova/nova/virt/libvirt/driver.py, line 616, in
   _do_quality_warnings
   caps = self._get_host_capabilities()
   File /opt/stack/nova/nova/virt/libvirt/driver.py, line 2942, in
   _get_host_capabilities
   libvirt.VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURES)
   File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in
  doit
   result = proxy_call(self._autowrap, f, *args, **kwargs)
   File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in
   proxy_call
   rv = execute(f,*args,**kwargs)
   File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in
   tworker
   rv = meth(*args,**kwargs)
   File /usr/lib/python2.7/dist-packages/libvirt.py, line 3127, in
  baselineCPU
   if ret is None: raise libvirtError ('virConnectBaselineCPU() failed',
   conn=self)
   libvirtError: XML error: Missing CPU model name
  
   Best Regards!
  
   Kevin (Chen) Ji 纪 晨
  
   Engineer, zVM Development, CSTL

Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup

[Chen CH Ji]

Just to clarify , I think your case would be run nova-network ,then ^C or
abnormally shutdown it
and it might be during  the period of holding a semaphore without releasing
it, right?

guess all component other than nova have this problem ? so maybe remove
this [nova] can get more input ...


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Alex Xu x...@linux.vnet.ibm.com
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org,
Date:   08/07/2014 04:54 PM
Subject:[openstack-dev] [nova] nova-network stuck at get semaphores
lockwhen startup



When I startup nova-network, it stuck at trying get lock for ebtables.

@utils.synchronized('ebtables', external=True)
def ensure_ebtables_rules(rules, table='filter'):
 .

Checking the code found that invoke utils.synchronized without parameter
lock_path, the code will try to use
posix semaphore.

But posix semaphore won't release even the process crashed. Should we
fix it? I saw a lot of call for synchronized
without lock_path.

Thanks
Alex


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] Enable live migration with one nova compute

[Chen CH Ji]

we used to have one compute service corresponding to multiple hypervisors
(like host and nodes concept )
our major issue on our platform is we can't run nova-compute service on the
hypervisor and we need to find another place to run the nova-compute in
order to talk to
hypervisor management API through REST API
which means we have to run multiple compute service out side of our
hypervisors and it's hard for us to control the compute services at that
time,
but we have no choice since nova migration only can be migrated to another
host instead of node ,so we implement according to it
if we can support host + node, then it might be helpful for the hypervisors
with different arch

The point is whether we are able to expose the internal (say, not only the
host concept but also the node concept ) to outside
guess live-migration is admin only feature, can we expose those node
concept to admin and let admin decide it?

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Jay Lau jay.lau@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   04/06/2014 07:02 PM
Subject:Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] Enable live
migration with one nova compute



Hi Divakar,

Can I say that the bare metal provisioning is now using kind of Parent -
Child compute mode? I was also thinking that we can use host:node to
identify a kind of Parent-Child or Hierarchy Compute. So can you please
show some difference for your Parent - Child Compute Node and bare metal
provisioning?

Thanks!


2014-04-06 14:59 GMT+08:00 Nandavar, Divakar Padiyar 
divakar.padiyar-nanda...@hp.com:
   Well, it seems to me that the problem is the above blueprint and the
  code it introduced. This is an anti-feature IMO, and probably the best
  solution would be to remove the above code and go back to having a single
   nova-compute managing a single vCenter cluster, not multiple ones.

  Problem is not introduced by managing multiple clusters from single
  nova-compute proxy node.  Internally this proxy driver is still
  presenting the compute-node for each of the cluster its managing.
  What we need to think about is applicability of the live migration use
  case when a cluster is modelled as a compute.   Since the cluster is
  modelled as a compute, it is assumed that a typical use case of live-move
  is taken care by the underlying cluster itself.       With this there
  are other use cases which are no-op today like host maintenance mode,
  live move, setting instance affinity etc.,     In order to resolve this I
  was thinking of
  A way to expose operations on individual ESX Hosts like Putting host in
  maintenance mode,  live move, instance affinity etc., by introducing
  Parent - Child compute node concept.   Scheduling can be restricted to
  Parent compute node and Child compute node can be used for providing more
  drill down on compute and also enable additional compute operations.
  Any thoughts on this?

  Thanks,
  Divakar


  -Original Message-
  From: Jay Pipes [mailto:jaypi...@gmail.com]
  Sent: Sunday, April 06, 2014 2:02 AM
  To: openstack-dev@lists.openstack.org
  Subject: Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] Enable live
  migration with one nova compute
  Importance: High

  On Fri, 2014-04-04 at 13:30 +0800, Jay Lau wrote:
  
  
  
   2014-04-04 12:46 GMT+08:00 Jay Pipes jaypi...@gmail.com:
           On Fri, 2014-04-04 at 11:08 +0800, Jay Lau wrote:
            Thanks Jay and Chris for the comments!
           
            @Jay Pipes, I think that we still need to enable one nova
           compute
            live migration as one nova compute can manage multiple
           clusters and
            VMs can be migrated between those clusters managed by one
           nova
            compute.
  
  
           Why, though? That is what I am asking... seems to me like this
           is an
           anti-feature. What benefit does the user get from moving an
           instance
           from one VCenter cluster to another VCenter cluster if the two
           clusters
           are on the same physical machine?
   @Jay Pipes, for VMWare, one physical machine (ESX server) can only
   belong to one VCenter cluster, so we may have following scenarios.
  
   DC
    |
  
    |---Cluster1
    |      |
  
    |      |---host1
    |
  
    |---Cluser2
           |
  
           |---host2
  
  
   Then when using VCDriver, I can use one nova compute manage both
   Cluster1 and Cluster2, this caused me cannot migrate VM from host2 to
   host1 ;-(
  
  
   The bp was introduced by
   https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-
   by-one-service

  Well, it seems to me

Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] Enable live migration with one nova compute

[Chen CH Ji]

It's z/VM which you might got more information here :)
http://www.vm.ibm.com/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matthew Booth mbo...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   04/09/2014 07:02 PM
Subject:Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] Enable live
migration with one nova compute



On 09/04/14 07:07, Chen CH Ji wrote:
 we used to have one compute service corresponding to multiple
 hypervisors (like host and nodes concept )
 our major issue on our platform is we can't run nova-compute service on
 the hypervisor and we need to find another place to run the nova-compute
 in order to talk to
 hypervisor management API through REST API

It may not be directly relevant to this discussion, but I'm interested
to know what constraint prevents you running nova-compute on the
hypervisor.

Matt

--
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team

GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

inline: graycol.gif___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Dynamic scheduling

[Chen CH Ji]

Is the [1] mentioned below open source? Interested in it :)

Also, my own opinion is nova is a cloud solution that aim to control
virtual / real machine lifecycle management   the dynamic scheduling
mechanism is something like
optimization of the cloud resource, so maybe incubate in other places is
better


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Jay Lau jay.lau@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   04/09/2014 11:45 PM
Subject:Re: [openstack-dev] [nova] Dynamic scheduling



@Oleg, Till now, I'm not sure the target of Gantt, is it for initial
placement policy or run time policy or both, can you help clarify?

@Henrique, not sure if you know IBM PRS (Platform Resource Scheduler) [1],
we have finished the dynamic scheduler in our Icehouse version (PRS 2.2),
it has exactly the same feature as your described, we are planning a live
demo for this feature in Atlanta Summit. I'm also writing some document for
run time policy which will cover more run time policies for OpenStack, but
not finished yet. (My shame for the slow progress). The related blueprint
is [2], you can also get some discussion from [3]

[1]
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=ANsubtype=CAhtmlfid=897/ENUS213-590appname=USN

[2]
https://blueprints.launchpad.net/nova/+spec/resource-optimization-service
[3] http://markmail.org/~jaylau/OpenStack-DRS

Thanks.


2014-04-09 23:21 GMT+08:00 Oleg Gelbukh ogelb...@mirantis.com:
  Henrique,

  You should check out Gantt project [1], it could be exactly the place to
  implement such features. It is a generic cross-project Scheduler as a
  Service forked from Nova recently.

  [1] https://github.com/openstack/gantt

  --
  Best regards,
  Oleg Gelbukh
  Mirantis Labs


  On Wed, Apr 9, 2014 at 6:41 PM, Henrique Truta 
  henriquecostatr...@gmail.com wrote:
   Hello, everyone!

   I  am currently a graduate student and member of a group of contributors
   to  OpenStack.  We  believe  that  a dynamic scheduler could improve the
   efficiency  of  an  OpenStack  cloud,  either  by  rebalancing  nodes to
   maximize performance or to minimize the number of active hosts, in order
   to  minimize energy costs. Therefore, we would like to propose a dynamic
   scheduling  mechanism  to  Nova.  The  main idea is using the Ceilometer
   information  (e.g.  RAM,  CPU, disk usage) through the ceilometer-client
   and dinamically decide whether a instance should be live migrated.



   This might me done as a Nova periodic task, which will be executed every
   once  in  a given period or as a new independent project. In both cases,
   the  current  Nova  scheduler  will  not  be  affected,  since  this new
   scheduler  will  be  pluggable.  We have done a search and found no such
   initiative  in the OpenStack BPs. Outside the community, we found only a
   recent  IBM  announcement  for  a  similiar  feature in one of its cloud
   products.



   A possible flow is: In the new scheduler, we periodically make a call to
   Nova, get the instance list from a specific host and, for each instance,
   we make a call to the ceilometer-client (e.g. $ ceilometer statistics -m
   cpu_util  -q resource=$INSTANCE_ID) and then, according to some specific
   parameters  configured by the user, analyze the meters and do the proper
   migrations.



   Do you have any comments or suggestions?



   --
   Ítalo Henrique Costa Truta



   ___
   OpenStack-dev mailing list
   OpenStack-dev@lists.openstack.org
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Thanks,

Jay___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
inline: graycol.gif___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] unit tests method

[Chen CH Ji]

Hi
There are 3 types of unit test existing now (stub, mox and
mock)
Several code reviewers suggest to use mock instead of using
the other 2 and I am following it, but I want to know where can I find the
suggestion and guide line?

Thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] nova-specs

[Chen CH Ji]

As a fresh guy on nova(Have about 1+ year in nova but less than 0.5 year
experience to contribute to community)
I'd like to share my feeling on using nova-specs

1)  let me know what we are going to do for next release,it wider my
understand of whole nova since
I am able to take a look at the design idea and how the idea / decision was
made by looking at comments
much helpful for new comer to catch up what's happening and what will going
to happen

2)  I can select several interesting topics so that I will read carefully
and think about issues and
other alternatives, thus I need to go back to check the code then think
again, it's really helpful
to new comers like me to go deep into some area and propose other
initialtives

3) I need to think more carefully and get some help from other folks when I
try to submit a bp , from the review comments
I might find my original idea is not so good so I can avoid waste time to
implement it , and learn more through the review comments I got


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Dan Smith d...@danplanet.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date:   04/17/2014 12:08 AM
Subject:Re: [openstack-dev] [Nova] nova-specs



 I'm not asking for 100% consistency.  I'm just raising it since it seems
 to be early in the process change and want to work out these kinds of
 things.  If it turns out to be an outlier then great.

Sure, and the spec reviewers are learning in this process as well. It
takes a certain amount of us seeing what other reviewers think is
reasonable and not before we establish a baseline. I'm sure that after
we've done this for a cycle or two, things will look a lot more
consistent :)

--Dan

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

inline: graycol.gif___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Question about addit log in nova-compute.log

[Chen CH Ji]

Hi
   I saw in my compute.log has following logs which looks to me
strange at first, Free resource is negative make me confused and I take a
look at the existing code
   looks to me the logic is correct and calculation doesn't
have problem ,but the output 'Free' is confusing

   Is this on purpose or might need to be enhanced?

2014-05-05 10:51:33.732 4992 AUDIT nova.compute.resource_tracker [-] Free
ram (MB): -1559
2014-05-05 10:51:33.732 4992 AUDIT nova.compute.resource_tracker [-] Free
disk (GB): 29
2014-05-05 10:51:33.732 4992 AUDIT nova.compute.resource_tracker [-] Free
VCPUS: -3
Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Do we have a way to add a non-nova managed host to nova managed?

[Chen CH Ji]

Hi
  Not sure ti's proper to ask this question here, or maybe
someone asked this question before and discussion , please share info to me
if we have

  If we have a bunch of hosts that used to manage by them self,
some vm and hypervisors already running on the hosts
 Do we have a way to include those vms into management of
nova ?


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] formally distinguish server desired state from actual state?

[Chen CH Ji]

Not only ERROR state, but also VERIFY_RESIZE might have this kind problem
https://review.openstack.org/#/c/101435/ has more info
so guess the server task stuff might be the right direction to those
problems ...

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Chris Friesen chris.frie...@windriver.com
To: openstack-dev@lists.openstack.org
openstack-dev@lists.openstack.org
Date:   10/02/2014 03:05 AM
Subject:[openstack-dev] [nova] formally distinguish server desired
state  from actual state?




Currently in nova we have the vm_state, which according to the code
comments is supposed to represent a VM's current stable (not
transition) state, or what the customer expect the VM to be.

However, we then added in an ERROR state.  How does this possibly make
sense given the above definition?  Which customer would ever expect the
VM to be in an error state?

Given this, I wonder whether it might make sense to formally distinguish
between the expected/desired state (i.e. the state that the customer
wants the VM to be in), and the actual state (i.e. the state that nova
thinks the VM is in).

This would more easily allow for recovery actions, since if the actual
state changes to ERROR (or similar) we would still have the
expected/desired state available for reference when trying to take
recovery actions.

Thoughts?

Chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] How does Nova update time for compute nodes?

[Chen CH Ji]

following are code analysis, only FYI

not sure fully understand the question, but I think
servicegroup/drivers/db.py might be a good place to look at
a timer function _report_state is called periodically ,when its updated,
the field will be updated

class TimestampMixin(object):
created_at = Column(DateTime, default=lambda: timeutils.utcnow())
updated_at = Column(DateTime, onupdate=lambda: timeutils.utcnow())

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Gareth academicgar...@gmail.com
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date:   10/08/2014 10:23 AM
Subject:[openstack-dev] [nova] How does Nova update time for compute
nodes?



Hi, Nova guys

I know that 'nova-manage service list' will output 'XXX' for compute nodes
is the time between api node and compute node are larger than
service_down_time. At the same time Nova update db cyclically. So my
question is how does Nova update that data? via crontab or something else?


--
Gareth

Cloud Computing, OpenStack, Distributed Storage, Fitness, Basketball
OpenStack contributor, kun_huang@freenode
My promise: if you find any spelling or grammar mistakes in my email from
Mar 1 2013, notify me
and I'll donate $1 or ￥1 to an open organization you specify.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] Questions on glance alternative link

[Chen CH Ji]

Hi
in nova/api/openstack/compute/views/images.py, there is a
function returns alternate links which contains project_id
However, I didn't see any info in glance API V2 spec
Can any one help me on :

1) what's the purpose of alternate link? can I remove the project_id? maybe
backward compatible issue?
2) if #1 's answer is negative, should we add a image api under nova/image/
to also generate a link with project_id?

 Thanks

def _get_alternate_link(self, request, identifier):
Create an alternate link for a specific image id.
glance_url = glance.generate_glance_url()
glance_url = self._update_glance_link_prefix(glance_url)
return '/'.join([glance_url,
 request.environ[nova.context].project_id, ---
this is the line which add project_id
 self._collection_name,
 str(identifier)])

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova][oslo] how to sync oslo.concurrency to nova?

[Chen CH Ji]

There used to method in oslo-incubator like
https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator or '
https://review.openstack.org/#/c/78429/ ' we can use

however, I was told to submit patch to oslo.concurrency instead of
oslo-incubator, so what's the method can be used now ? Thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova][oslo] how to sync oslo.concurrency to nova?

[Chen CH Ji]

Thanks a lot for the info,

So, my understanding is I need to wait for its released then someone need
to change the code in
projects (e.g. nova) to switch from its original method
(nova/openstack/common/) to oslo.concurrency
just like we did for oslo.utils and other components nowadays?

thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Ben Nemec openst...@nemebean.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   10/10/2014 09:59 PM
Subject:Re: [openstack-dev] [Nova][oslo] how to sync oslo.concurrency
to nova?



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/10/2014 05:05 AM, Ihar Hrachyshka wrote:
 On 10/10/14 10:32, Chen CH Ji wrote:
 There used to method in oslo-incubator like
 https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator
 or '_https://review.openstack.org/#/c/78429/_ ' we can use

 however, I was told to submit patch to oslo.concurrency instead
 of oslo-incubator, so what's the method can be used now ? Thanks
 a lot

 With oslo.concurrency, you don't copy-paste code, you just reuse it
 as any other third-party library. So if your project is not yet
 using the library, just port it to it first, and once a new version
 of oslo.concurrency is released, you will get your change magically
 applied.

At this point oslo.concurrency hasn't been released yet so it won't be
possible to switch any projects to use it.  I think we're on track for
a first release early next week and once that has happened this will
be possible.

Note that we do have a stable branch of the incubator code that can be
used for important changes in projects that haven't yet ported to use
new libs, but when possible we'd rather just make the changes in the lib.

- -Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUN+bgAAoJEDehGd0Fy7uqjhMIANBPX4sTbVSnewoquF3Ih29z
Adxq6KpDymonhpnJuOqM1gKYsd/oyqa6q92WTt9F9c8XwALB1x9IzgUBRRixhts5
p4fDzNTMGJzlT9slnGjyNVD0i3AJ1UuO5+mZADDk3jXqqERmbeCo+BgYqJr7q08r
MmkPuo0EAZtWrY1+Isl1Eg3lz7P2DFC9kEmY8iUj5wObiqINU7L5MNCzCi7V+c8g
uxacoCSXcyTR7nnXcs9cPywthBTLOOqkY1IzEYk38vbnQSmvqKbbovqVB0ZCTueF
8g/WO2+jOhETsyFGY7d3HuOQDxJSx/JeXlpPfriOsxdcrDtmP3YMEgh2kpK0e7k=
=Puy/
-END PGP SIGNATURE-

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] questions on object/db usage

[Chen CH Ji]

Hi
   When I fix some bugs, I found that some code in
nova/compute/api.py

  sometimes we use db ,sometimes we use objects do we have any
criteria for it? I knew we can't access db in compute layer code, how about
others ? prefer object or db direct access? thanks

def service_delete(self, context, service_id):
Deletes the specified service.
objects.Service.get_by_id(context, service_id).destroy()

def instance_get_all_by_host(self, context, host_name):
Return all instances on the given host.
return self.db.instance_get_all_by_host(context, host_name)

def compute_node_get_all(self, context):
return self.db.compute_node_get_all(context)

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

[Chen CH Ji]

I think we already support to specify the host when doing evacuate and
migration ?

if we need use hints that passed from creating instance, that means we need
to persistent schedule hints
I remember we used to have a spec for store it locally ...

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Alex Xu x...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   10/29/2014 12:19 PM
Subject:[openstack-dev] [Nova] Add scheduler-hints when
migration/rebuild/evacuate



Hi,

Currently migration/rebuild/evacuate didn't support pass
scheduler-hints, that means any migration
can't use schedule-hints that passed when creating instance.

Can we add scheduler-hints support when migration/rebuild/evacuate? That
also can enable user
move in/out instance to/from an server group.

Thanks
Alex


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

[Chen CH Ji]

Yes, I remember that spec might talk about local storage (in local db?) and
it can be the root cause

And I think we need persistent storage otherwise the scheduler hints can't
survive in some conditions such as system reboot or upgrade ?

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Alex Xu x...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   10/29/2014 01:34 PM
Subject:Re: [openstack-dev] [Nova] Add scheduler-hints  when
migration/rebuild/evacuate



On 2014年10月29日 12:37, Chen CH Ji wrote:


  I think we already support to specify the host when doing evacuate
  and migration ?


Yes, we support to specify the host, but schedule-hints is different thing.



  if we need use hints that passed from creating instance, that means
  we need to persistent schedule hints
  I remember we used to have a spec for store it locally ...



I also remember we have one spec for persistent before, but I don't know
why it didn't continue.
And I think maybe we needn't persistent schedule-hints, just add pass new
schedule-hints when
migration the instance. Nova just need provide the mechanism.




  Best Regards!

  Kevin (Chen) Ji 纪 晨

  Engineer, zVM Development, CSTL
  Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
  Phone: +86-10-82454158
  Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
  District, Beijing 100193, PRC

  Inactive hide details for Alex Xu ---10/29/2014 12:19:35
  PM---Hi, Currently migration/rebuild/evacuate didn't support
  passAlex Xu ---10/29/2014 12:19:35 PM---Hi, Currently
  migration/rebuild/evacuate didn't support pass

  From: Alex Xu x...@linux.vnet.ibm.com
  To: openstack-dev@lists.openstack.org
  Date: 10/29/2014 12:19 PM
  Subject: [openstack-dev] [Nova] Add scheduler-hints when
  migration/rebuild/evacuate





  Hi,

  Currently migration/rebuild/evacuate didn't support pass
  scheduler-hints, that means any migration
  can't use schedule-hints that passed when creating instance.

  Can we add scheduler-hints support when migration/rebuild/evacuate?
  That
  also can enable user
  move in/out instance to/from an server group.

  Thanks
  Alex


  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][compute] propose to use a table to deal with the vm_state when _init_instance in compute

[Chen CH Ji]

+1,

a good idea, it will make it more clear.
from implementation perspective we need to pay attention that some status
will pass through and some will just return

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eli Qiao ta...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   11/04/2014 03:13 PM
Subject:[openstack-dev] [nova][compute] propose to use a table to deal
with the vm_state when _init_instance in compute



hello all:
in current _init_instance function in compute manager,
there's flood 'and' 'or' logic, to check the vm_state and task_state when
initialize a instance during service list,
this lead hard to read and hard to maintain, so I propose a new way to
handle this.

we can create a vm_state_table, by look up the table  we can find the
action we need to do for the instance,
from this table , you can clearly see what vm_state and task_state should
take the action.

for example:
{vm_states list :{task_states list: action}},

each entry stands for an action,
and we walk though the tuple
so the table should be like this:

vm_state_table = (
{vm_states.SOFT_DELETE :{'ALL': ACTION_NONE}},
{vm_states.ERROR:  {('NOT_IN',[task_states.RESIZE_MIGRATING,

task_states.DELETING]): ACTION_NONE}},
{vm_states.DELETED: {'ALL': _complete_partial_deletion}},
{vm_states.BUILDING: {'ALL': ACTION_ERROR}},
{'ALL': {('IN',[task_states.SCHEDULING,
task_states.BLOCK_DEVICE_MAPPING,
task_states.NETWORKING,
task_states.SPAWNING)]: ACTION_ERROR}},
{('IN',[vm_states.ACTIVE, vm_states.STOPPED]: {('IN',
[task_states.REBUILDING,
task_states.REBUILD_BLOCK_DEVICE_MAPPING,
task_states.REBUILD_SPAWNING]): ACTION_ERROR}},
{('NOT_IN',[vm_states.ERROR]): {('IN',
[task_states.IMAGE_SNAPSHOT_PENDING,

task_states.IMAGE_PENDING_UPLOAD,

task_states.IMAGE_UPLOADING,

task_states.IMAGE_SNAPSHOT]): _post_interrupted_snapshot_cleanup}}
)

what do you think, do we need a bp for this?

--
Thanks,
Eli (Li Yong) Qiao___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] questions on object/db usage

[Chen CH Ji]

I also working on it and I am glad you can help this ,see
https://review.openstack.org/#/c/130744/ for some info though it's still
ongoing

if you want to know general rule  ,I guess
https://wiki.openstack.org/wiki/How_To_Contribute can be a good place to
refer

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Daniele Casini daniele.cas...@dektech.com.au
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   11/05/2014 07:22 PM
Subject:Re: [openstack-dev] [Nova] questions on object/db usage



Hi All:

I replaced all db.instance_get_all_by_host() in nova and tested it using
tox.
Might it be useful? If so, Which is the better way to propose it to
OpenStack community?

Best regards,

Daniele


On 10/23/2014 09:01 PM, Dan Smith wrote:
   When I fix some bugs, I found that some code in
nova/compute/api.py
  sometimes we use db ,sometimes we use objects do
we have
any criteria for it? I knew we can't access db in compute layer
code,
how about others ? prefer object or db direct access? thanks


  Prefer objects, and any remaining db.* usage anywhere (other than the
  object code itself) is not only a candidate for cleanup, it's much
  appreciated :)

  --Dan




  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova][Schedule] how to schedule vms(like database VM, vs web server VM) to different resource pool(either LVM or GlusterFs)?

[Chen CH Ji]

I think you can refer to following for more info
http://blog.csdn.net/tantexian/article/details/39055889
http://blog.russellbryant.net/2013/05/21/availability-zones-and-host-aggregates-in-openstack-compute-nova/

And this is mail list for developers ,so you can ask openstack mail list if
you have configuration or questions next time :)

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   zhang xiaobin 14050...@cnsuning.com
To: openstack-dev openstack-dev@lists.openstack.org
Date:   11/06/2014 04:23 PM
Subject:[openstack-dev] [Nova][Schedule] how to schedule vms(like
databaseVM, vs web server VM) to different resource pool
(either LVM or  GlusterFs)?



 Greeting,

 I have some hosts in one availability zone, some hosts are solely based on
 LVM, which means their root images will be sitting on LVM;
 while other hosts are setup with GlusterFS, which means their root image
 will be allocated on Gluster.

 My question is: what's the best way to let VM be scheduled to the right
 resource pool(either LVM-based, or GlusterFs-based?)
 how to configure and which kind of schedule filter to be used? can we use
 image metadata function to achieve this?

 Many thanks!
 本邮件（包括其附件）可能含有保密、专有或保留著作权的信息。如果您并非本邮件
 指定接受人，请即刻通知发送人并将本邮件从您的系统中删除，您不得散布、保
 留、复制、披露或以其他方式使用本邮件任何相关信息，并且通过邮件告知我们此次
 错误投递。发送人在本邮件下表达的观点并不一定代表苏宁云商集团股份有限公司的
 观点。苏宁云商集团股份有限公司并不保证本邮件是安全或不受任何计算机病毒影响
 的，并且对由于邮件传输而导致的邮件内容错误或缺失不承担任何责任。除非明确说
 明，本邮件并不构成具有约束力的契约。
 This e-mail may contain confidential, copyright and/or privileged
 information. If you are not the addressee or authorized to receive this,
 please inform us of the erroneous delivery by return e-mail, and you
 should delete it from your system and may not use, copy, disclose or take
 any action based on this e-mail or any information herein. Any opinions
 expressed by sender hereof do not necessarily represent those of SUNING
 COMMERCE GROUP CO., LTD.,SUNING COMMERCE GROUP CO., LTD.,does not
 guarantee that this email is secure or free from viruses. No liability is
 accepted for any errors or omissions in the contents of this email, which
 arise as a result of email transmission. Unless expressly stated,this
 email is not intended to form a binding contract.
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Add Modified Compute Driver to Nova

[Chen CH Ji]

which value did you put ?  From my former experience, also check your
my_driver's init function, something wrong in that function can also lead
to this error, good luck

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Mohammad Hosein Zarei hosein.za...@gmail.com
To: openstack-dev@lists.openstack.org
Date:   11/10/2014 04:41 PM
Subject:[openstack-dev] Add Modified Compute Driver to Nova



​​
Hi everyone
I have a modified compute driver (my_driver.py and my_driver.pyc) and I
copied files to /opt/stack/nova/nova/virt/libvirt/ directory.
Also, nova.conf modified to use this driver
(compute_driver=libvirt.my_driver.MyDriver).
I can't start nova-compute with this modified driver and nova.conf. When
nova-compute start , it shows this error:

  2014-11-10 12:03:25.300 DEBUG nova.servicegroup.api [-] ServiceGroup
  driver defined as an instance of db from (pid=18709)
  __new__ /opt/stack/nova/nova/servicegroup/api.py:65
  2014-11-10 12:03:25.401 INFO nova.virt.driver [-] Loading compute driver
  'libvirt.my_driver.MyDriver'
  2014-11-10 12:03:25.406 INFO nova.openstack.common.periodic_task [-]
  Skipping periodic task _periodic_update_dns because its interval is
  negative
  2014-11-10 12:03:25.424 ERROR nova.virt.driver [-] Unable to load the
  virtualization driver
  2014-11-10 12:03:25.424 TRACE nova.virt.driver Traceback (most recent
  call last):
  2014-11-10 12:03:25.424 TRACE nova.virt.driver   File
  /opt/stack/nova/nova/virt/driver.py, line 1385, in load_compute_driver
  2014-11-10 12:03:25.424 TRACE nova.virt.driver virtapi)
  2014-11-10 12:03:25.424 TRACE nova.virt.driver   File
  /usr/local/lib/python2.7/dist-packages/oslo/utils/importutils.py, line
  52, in import_object_ns
  2014-11-10 12:03:25.424 TRACE nova.virt.driver return import_class
  (import_str)(*args, **kwargs)
  2014-11-10 12:03:25.424 TRACE nova.virt.driver   File
  /usr/local/lib/python2.7/dist-packages/oslo/utils/importutils.py, line
  27, in import_class
  2014-11-10 12:03:25.424 TRACE nova.virt.driver __import__(mod_str)
  2014-11-10 12:03:25.424 TRACE nova.virt.driver ImportError: No module
  named my_driver

I really appreciate with any idea.

Best Regard.


--
M.H.Zarei___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] questions on result of diagnostics on libvirt

[Chen CH Ji]

see the error value of diagnostics is huge , but I don't think my disk is
that bad ... is this wrong info or wrong usage of libvirt?
Also, all the disk has same error number curious me , any guide ?

jichen@cloudcontroller:/opt/stack/nova/nova$ nova diagnostics jieph1
+---+--+
| Property  | Value|
+---+--+
| cpu0_time | 1071000  |
| hdd_errors| 18446744073709551615 |
...
| tapf1ce9c02-01_tx_packets | 24   |
| vda_errors| 18446744073709551615 |
| vda_read  | 2848768  |
| vda_read_req  | 453  |
| vda_write | 348160   |
| vda_write_req | 105  |
| vdb_errors| 18446744073709551615 |
| vdb_read  | 829440   |
| vdb_read_req  | 30   |
| vdb_write | 4096 |

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Do we need to add xml support for new API extensions on v2 API ?

[Chen CH Ji]

Hi
 I saw we are removing v2 XML support proposed several days
before

 For new api extensions, do we need to add it now and
remove it later or only support JSON ? Thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'

[Chen CH Ji]

are you using libvirt ? it's not implemented
,guess your bug are talking about other hypervisors?

the message was printed here:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/hosts.py#n236

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Vineet Menon mvineetme...@gmail.com
To: openstack-dev openstack-dev@lists.openstack.org
Date:   11/26/2014 12:10 AM
Subject:[openstack-dev] [nova] nova host-update gives error 'Virt
driver does not implement host disabled status'



Hi,

I'm trying to reproduce the bug
https://bugs.launchpad.net/nova/+bug/1259535.
While trying to issue the command, nova host-update --status disable
machine1, an error is thrown saying,

  ERROR (HTTPNotImplemented): Virt driver does not implement host disabled
  status. (HTTP 501) (Request-ID: req-1f58feda-93af-42e0-b7b6-bcdd095f7d8c)


What is this error about?

Regards,
Vineet Menon
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [gerrit] Gerrit review problem

[Chen CH Ji]

+1, I also found this inconvenient point before ,thanks Jay for bring up :)

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Jay Lau jay.lau@gmail.com
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date:   12/01/2014 01:56 PM
Subject:[openstack-dev] [gerrit] Gerrit review problem




When I review a patch for OpenStack, after review finished, I want to check
more patches for this project and then after click the Project content
for this patch, it will **not** jump to all patches but project
description. I think it is not convenient for a reviewer if s/he wants to
review more patches for this project.

内嵌图片 1

内嵌图片 2

--
Thanks,

Jay___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [api] Using query string or request body to pass parameter

[Chen CH Ji]

Found something might be helpful for you
http://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request



Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eli Qiao ta...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   12/08/2014 02:10 PM
Subject:Re: [openstack-dev] [api] Using query string or request body to
pass parameter




在 2014年12月08日 13:13, Alex Xu 写道:
  Hi,

  I have question about using query string or request body for REST
  API.
I wonder if we can use body in delete, currently , there isn't any case
used in v2/v3 api.

  This question found when I review this spec:
  
https://review.openstack.org/#/c/131633/6..7/specs/kilo/approved/judge-service-state-when-deleting.rst

  Think about use request body will have more benefit:
  1. Request body can be validated by json-schema
  2. json-schema can doc what can be accepted by the parameter

  Should we have guideline for this?


  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thanks,
Eli (Li Yong) Qiao___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] anyway to pep8 check on a specified file

[Chen CH Ji]

tox -e pep8 usually takes several minutes on my test server, actually I
only changes one file and I knew something might wrong there
anyway to only check that file? Thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][resend with correct subject prefix] ask for usage of quota reserve

[Chen CH Ji]

AFAIK, quota will expire in 24 hours

cfg.IntOpt('reservation_expire',
   default=86400,
   help='Number of seconds until a reservation expires'),

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eli Qiao(Li Yong Qiao) ta...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   12/18/2014 04:34 PM
Subject:[openstack-dev] [nova][resend with correct subject prefix] ask
for usage of quota reserve



hi all,
can anyone tell if we call quotas.reserve() but never call quotas.commit()
or quotas.rollback().
what will happen?

for example:

   1.   when doing resize, we call quotas.reserve() to reservea a delta
  quota.(new_flavor - old_flavor)
   2.   for some reasons, nova-compute crashed, and not chance to call
  quotas.commit() or quotas.rollback() (called by finish_resize in
  nova/compute/manager.py)
   3.   next time restart nova-compute server, is the delta quota still
  reserved , or do we need any other operation on quotas?


Thanks in advance
-Eli.


ps: this is related to patch : Handle RESIZE_PREP status when nova compute
do init_instance(https://review.openstack.org/#/c/132827/)


--
Thanks Eli Qiao(qia...@cn.ibm.com)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][resend with correct subject prefix] ask for usage of quota reserve

[Chen CH Ji]

I used to submit a patch and retrieve the reservation of quota, got a -2
because it can expire :)

so, I guess expire do no harm unless the uncommitted / unrollbacked
reservation may occupy the quota
and lead to side effect on upcoming actions...

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eli Qiao ta...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   12/22/2014 11:37 AM
Subject:Re: [openstack-dev] [nova][resend with correct subject prefix]
ask for usage of quota reserve




在 2014年12月18日 17:33, Chen CH Ji 写道:


  AFAIK, quota will expire in 24 hours

  cfg.IntOpt('reservation_expire',
                 default=86400,
                 help='Number of seconds until a reservation expires'),

  Best Regards!


hi Kevin,
but that is not reliable,  user/op can change the default value.
shall we just leave as the quota reservation there can do not
commit/rollback ?
I don't think there will be much more we can do.



  Kevin (Chen) Ji 纪 晨

  Engineer, zVM Development, CSTL
  Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
  Phone: +86-10-82454158
  Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
  District, Beijing 100193, PRC

  Inactive hide details for Eli Qiao(Li Yong
  Qiao)
  ---12/18/2014 04:34:32 PM---hi all, can anyone
  tell if we
  call quotas.reservEli Qiao(Li Yong Qiao) ---12/18/2014 04:34:32
  PM---hi all, can anyone tell if we call quotas.reserve() but never
  call

  From: Eli Qiao(Li Yong Qiao) ta...@linux.vnet.ibm.com
  To: OpenStack Development Mailing List (not for usage questions)
  openstack-dev@lists.openstack.org
  Date: 12/18/2014 04:34 PM
  Subject: [openstack-dev] [nova][resend with correct subject prefix]
  ask for usage of quota reserve





  hi all,
  can anyone tell if we call quotas.reserve() but never call
  quotas.commit() or quotas.rollback().
  what will happen?

  for example:
1. when doing resize, we call quotas.reserve() to reservea a
delta quota.(new_flavor - old_flavor)
2. for some reasons, nova-compute crashed, and not chance to
call quotas.commit() or quotas.rollback() (called by
finish_resize in nova/compute/manager.py)
3. next time restart nova-compute server, is the delta quota
still reserved , or do we need any other operation on quotas?

  Thanks in advance
  -Eli.


  ps: this is related to patch : Handle RESIZE_PREP status when nova
  compute do init_instance(https://review.openstack.org/#/c/132827/)


  --
  Thanks Eli Qiao(qia...@cn.ibm.com)
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev






  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thanks,
Eli (Li Yong) Qiao___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] should 'ip address' be retrived when decribe host?

[Chen CH Ji]

Hi
  Sorry If I didn't understand clearly about it , looks to me
the hypervisor itself hosts the instances and it should have a IP with it
(like Linux host KVM instances, Linux is the hypervisor, the PC is the
host)
  while the host is physical node and only to be used by
'hypervisor' concept ,so I think maybe we don't need ip for the 'host' ?
thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Lingxian Kong anlin.k...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   12/31/2014 07:22 AM
Subject:Re: [openstack-dev] [Nova] should 'ip address' be retrived when
decribe host?



Thanks Kevin for your clarification, which further affirms my belief
that ip address should be included in the host info.

I will contact Jay Pipes on IRC, to see what can I help towards this
effort, soon after the New Year's Day in China. :)

2014-12-31 0:34 GMT+08:00 Kevin L. Mitchell kevin.mitch...@rackspace.com:
 On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:
 Just as what Jay Lau said, 'nova hypervisor-show hypervisor_id'
 indeed returns host ip address, and there are more other information
 included than 'nova host-describe hostname'. I feel a little
 confused about the 'host' and 'hypervisor', what's the difference
 between them? For cloud operator, maybe 'host' is more usefull and
 intuitive for management than 'hypervisor'. From the implementation
 perspective, both 'compute_nodes' and 'services' database tables are
 used for them. Should them be combined for more common use cases?

 Well, the host and the hypervisor are conceptually distinct objects.
 The hypervisor is, obviously, the thing on which all the VMs run.  The
 host, though, is the node running the corresponding nova-compute
 service, which may be separate from the hypervisor.  For instance, on
 Xen-based setups, the host runs in a VM on the hypervisor.  There has
 also been discussion of allowing one host to be responsible for multiple
 hypervisors, which would be useful for providers with large numbers of
 hypervisors.
 --
 Kevin L. Mitchell kevin.mitch...@rackspace.com
 Rackspace


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Regards!
---
Lingxian Kong

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] should 'ip address' be retrived when decribe host?

[Chen CH Ji]

ok, that make sense to me , thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Kevin L. Mitchell kevin.mitch...@rackspace.com
To: openstack-dev@lists.openstack.org
Date:   12/31/2014 09:37 PM
Subject:Re: [openstack-dev] [Nova] should 'ip address' be retrived when
decribe host?



On Wed, 2014-12-31 at 20:56 +0100, Chen CH Ji wrote:
   Sorry If I didn't understand clearly about it , looks to
 me the hypervisor itself hosts the instances and it should have a IP
 with it (like Linux host KVM instances, Linux is the hypervisor, the
 PC is the host)
   while the host is physical node and only to be used by
 'hypervisor' concept ,so I think maybe we don't need ip for the
 'host' ?  thanks a lot

The hypervisor hosts the VMs, yes, but the component that sits between
the hypervisor and the rest of nova―that is, nova-compute―does not
necessarily reside on the hypervisor.  It is the nova-compute node
(which may be either a VM or a physical host) that is referred to by the
nova term host.  For KVM, I believe the host is often the same as the
hypervisor, meaning that nova-compute runs directly on the hypervisor…
but this is not necessarily the case for all virt drivers.  For example,
the host for Xen-based installations is often a separate VM on the same
hypervisor, which would have its own distinct IP address.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] novaclient support for V2.1 micro versions

[Chen CH Ji]

No, AFAICT it's not supported because the v2.1 microversion and related bp
are still under implementation ,there is no change on novaclient now ...

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Day, Phil philip@hp.com
To: OpenStack Development Mailing List
(openstack-dev@lists.openstack.org)
openstack-dev@lists.openstack.org
Date:   01/23/2015 05:56 PM
Subject:[openstack-dev] [nova] novaclient support for V2.1 micro
versions



Hi Folks,

Is there any support yet in novaclient for requesting a specific
microversion ?   (looking at the final leg of extending clean-shutdown to
the API, and wondering how to test this in devstack via the novaclient)

Phil

 __
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 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

Re: [openstack-dev] [nova] proposal for unwinding database usage from tests

[Chen CH Ji]

Sorry for late reply and thanks for bring this out, I agree the create_db
flag will increase the complexity
so I might do some PoC and write a spec to do it next release

For this sentence, I don't fully understand, are you suggesting to every db
usage remove should be a
patch for a test class? thanks a lot
I'd like to propose instead DB usage should be removed per test Class as
an atomic unit.

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Sean Dague s...@dague.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Cc: Chen CH Ji/China/IBM@IBMCN
Date:   01/24/2015 07:13 PM
Subject:[nova] proposal for unwinding database usage from tests



I've been looking at the following patch series -
https://review.openstack.org/#/c/131691/13 for removing database
requirements from some tests.

I whole heartedly support getting DB usage out of tests, but I'd like to
make sure that we don't create new challenges in the process. The
conditional create_db parameter in test functions adds a bit more
internal test complexity than I think we should have.

I'd like to propose instead DB usage should be removed per test Class as
an atomic unit. If that turns into too large a patch that probably means
breaking apart the test class into smaller test classes first.

The other thing to be careful in understanding the results of timing
tests. The way the database fixture works it caches the migration
process -
https://github.com/openstack/nova/blob/master/nova/tests/fixtures.py#L206

That actually means that the overhead of the db-migration sync is paid
only once per testr worker (it's 1s on my fast workstation, might be 2s
on gate nodes). The subsequence db setups for tests 2 - N in the worker
only take about 0.020s on my workstation (scale appropriately). So
removing all the unneeded db setup code is probably only going to save
~30s over an entire test run.

Which doesn't mean it shouldn't be done, there are other safety reasons
we shouldn't let every test randomly punch data into the db and still
pass. But time savings should not be the primary motivator here, because
it's actually not nearly as much gain as it looks like from running only
a small number of tests.

 -Sean

--
Sean Dague
http://dague.net

(See attached file: signature.asc)

signature.asc
Description: Binary data
__
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

Re: [openstack-dev] [nova] Questions on pep8 F811 hacking check for microversion

[Chen CH Ji]

Is there a way to overwrite the rule in our hacking (not familiar with
it ...)?
if so ,maybe we can do as suggested to avoid 811 for the class which has
Microversion definition? Thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Christopher Yeoh cbky...@gmail.com
To: openstack-dev@lists.openstack.org
Date:   01/28/2015 09:37 AM
Subject:Re: [openstack-dev] [nova] Questions on pep8 F811 hacking check
for microversion



On Tue, 06 Jan 2015 07:31:19 -0500
Jay Pipes jaypi...@gmail.com wrote:

 On 01/06/2015 06:25 AM, Chen CH Ji wrote:
  Based on nova-specs api-microversions.rst
  we support following function definition format, but it violate the
  hacking rule pep8 F811 because duplicate function definition
  we should use #noqa for them , but considering microversion may
  live for long time ,
  keep adding #noqa may be a little bit ugly, can anyone suggest a
  good solution for it ? thanks
 
  @api_version(min_version='2.1')
  def _version_specific_func(self, req, arg1):
 pass
   
  @api_version(min_version='2.5')
  def _version_specific_func(self, req, arg1):
 pass

 Hey Kevin,

 This was actually one of my reservations about the proposed
 microversioning implementation -- i.e. having functions that are
 named exactly the same, only decorated with the microversioning
 notation. It kinda reminds me of the hell of debugging C++ code that
 uses STL: how does one easily know which method one is in when inside
 a debugger?

 That said, the only other technique we could try to use would be to
 not use a decorator and instead have a top-level dispatch function
 that would inspect the API microversion (only when the API version
 makes a difference to the output or input of that function) and then
 dispatch the call to a helper method that had the version in its name.

 So, for instance, let's say you are calling the controller's GET
 /$tenant/os-hosts method, which happens to get routed to the
 nova.api.openstack.compute.contrib.hosts.HostController.index()
 method. If you wanted to modify the result of that method and the API
 microversion is at 2.5, you might do something like:

   def index(self, req):
   req_api_ver = utils.get_max_requested_api_version(req)
   if req_api_ver == (2, 5):
   return self.index_2_5(req)
   return self.index_2_1(req)

   def index_2_5(self, req):
   results = self.index_2_1(req)
   # Replaces 'host' with 'host_name'
   for result in results:
   result['host_name'] = result['host']
   del result['host']
   return results

   def index_2_1(self, req):
   # Would be a rename of the existing index() method on
   # the controller


So having to manually add switching code everything we have an API
patch I think is not only longer and more complicated but more error
prone when updating. If we change something at the core in the future it
means changing all the microversioned code rather than just the
switching architecture at the core of wsgi.


 Another option would be to use something like JSON-patch to determine
 the difference between two output schemas and automatically translate
 one to another... but that would be a huge effort.

 That's the only other way I can think of besides disabling F811,
 which I really would not recommend, since it's a valuable safeguard
 against duplicate function names (especially duplicated test methods).

So I don't think we need to disable F811 in general - why not just
disable it for any method with the api_version decorator? On those ones
we can do checks on what is passed to api_version which will help
verify that there hasn't been a typo to an api_version decorator.

Chris

__
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 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

Re: [openstack-dev] [nova] proposal for unwinding database usage from tests

[Chen CH Ji]

ok, I understand the purpose and way to go now, thanks for the sharing
and I will refactory the patches I have ,thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   01/28/2015 06:17 PM
Subject:Re: [openstack-dev] [nova] proposal for unwinding database
usage from tests





On 1/28/2015 10:59 AM, Chen CH Ji wrote:
 Sorry for late reply and thanks for bring this out, I agree the
 create_db flag will increase the complexity
 so I might do some PoC and write a spec to do it next release

 For this sentence, I don't fully understand, are you suggesting to every
 db usage remove should be a
 patch for a test class? thanks a lot
 /I'd like to propose instead DB usage should be removed per test Class as
 an atomic unit./

 Best Regards!

 Kevin (Chen) Ji 纪 晨

 Engineer, zVM Development, CSTL
 Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
 Phone: +86-10-82454158
 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
 District, Beijing 100193, PRC

 Inactive hide details for Sean Dague ---01/24/2015 07:13:45 PM---I've
 been looking at the following patch series - https://reviSean Dague
 ---01/24/2015 07:13:45 PM---I've been looking at the following patch
 series - https://review.openstack.org/#/c/131691/13 for rem

 From: Sean Dague s...@dague.net
 To: OpenStack Development Mailing List (not for usage questions)
 openstack-dev@lists.openstack.org
 Cc: Chen CH Ji/China/IBM@IBMCN
 Date: 01/24/2015 07:13 PM
 Subject: [nova] proposal for unwinding database usage from tests

 



 I've been looking at the following patch series -
 https://review.openstack.org/#/c/131691/13 for removing database
 requirements from some tests.

 I whole heartedly support getting DB usage out of tests, but I'd like to
 make sure that we don't create new challenges in the process. The
 conditional create_db parameter in test functions adds a bit more
 internal test complexity than I think we should have.

 I'd like to propose instead DB usage should be removed per test Class as
 an atomic unit. If that turns into too large a patch that probably means
 breaking apart the test class into smaller test classes first.

 The other thing to be careful in understanding the results of timing
 tests. The way the database fixture works it caches the migration
 process -
 https://github.com/openstack/nova/blob/master/nova/tests/fixtures.py#L206

 That actually means that the overhead of the db-migration sync is paid
 only once per testr worker (it's 1s on my fast workstation, might be 2s
 on gate nodes). The subsequence db setups for tests 2 - N in the worker
 only take about 0.020s on my workstation (scale appropriately). So
 removing all the unneeded db setup code is probably only going to save
 ~30s over an entire test run.

 Which doesn't mean it shouldn't be done, there are other safety reasons
 we shouldn't let every test randomly punch data into the db and still
 pass. But time savings should not be the primary motivator here, because
 it's actually not nearly as much gain as it looks like from running only
 a small number of tests.

 -Sean

 --
 Sean Dague
 http://dague.net

 /(See attached file: signature.asc)/



__
 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


I take that to mean doing something like this:

https://review.openstack.org/#/c/142655/

But I don't want to speak for Sean.  But that would be a lot of work for
some test classes, so I'd think it'd have to be phased, which is
happening in some places, e.g. danpb was doing some of that with the
libvirt unit test refactoring, and we've done some of that with the
compute manager tests.  test_compute_mgr is huge though so refactoring
and moving tests to NoDB will take time (test_neutronv2 also has some of
this similar issue, i.e. we want to get away from the DB and mega-mox in
setUp and move to using mock, so there is a separate test class in that
module which uses Mock and NoDB and new tests should live there unless
we can just update small parts of old tests).

So this is kind of like the mox-mock conversion, it's OK to update
existing test cases for bug fixes, but if you have new unit tests (new
test cases/classes), do them in mock (and do them w/o the DB).

--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe

[openstack-dev] [nova] microversion and backward incompatible changes on v2.1

[Chen CH Ji]

Hi
https://review.openstack.org/#/c/144995/ introduced a
backward incompatible change with mirco version support
and I think it's the microversion's purpose to enable v2.1
(v3) API to make those changes

The question is whether we should make bp for each change
for the API change? should we make a simple bp or go through the nova-spec
process? Thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Questions on pep8 F811 hacking check for microversion

[Chen CH Ji]

Based on nova-specs api-microversions.rst
we support following function definition format, but it violate the hacking
rule pep8 F811 because duplicate function definition
we should use #noqa for them , but considering microversion may live for
long time ,
keep adding #noqa may be a little bit ugly, can anyone suggest a good
solution for it ? thanks

   @api_version(min_version='2.1')
   def _version_specific_func(self, req, arg1):
  pass

   @api_version(min_version='2.5')
   def _version_specific_func(self, req, arg1):
  pass



Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] local and gate pep8 check comparsion

[Chen CH Ji]

Thanks, I did the 'tox -r -e pep8' in my local env and it seems the problem
is gone ... thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   01/06/2015 05:29 PM
Subject:Re: [openstack-dev] [nova] local and gate pep8 check comparsion





On 1/6/2015 10:21 AM, Chen CH Ji wrote:
 I got following error in patch
 https://review.openstack.org/#/c/137009/ from Jenkins

 _2015-01-06 12:24:20.445_
 
http://logs.openstack.org/09/137009/2/check/gate-nova-pep8/b868ad8/console.html#_2015-01-06_12_24_20_445
 |
 ./nova/compute/manager.py:5325:13: N331  Use LOG.warning due to
 compatibility with py3
 _2015-01-06 12:24:20.445_
 
http://logs.openstack.org/09/137009/2/check/gate-nova-pep8/b868ad8/console.html#_2015-01-06_12_24_20_445
 |
 ./nova/compute/manager.py:5726:13: N331  Use LOG.warning due to
 compatibility with py3
 _2015-01-06 12:24:20.916_
 
http://logs.openstack.org/09/137009/2/check/gate-nova-pep8/b868ad8/console.html#_2015-01-06_12_24_20_916
 |
 ERROR: InvocationError:
 '/home/jenkins/workspace/gate-nova-pep8/.tox/pep8/bin/flake8'

 but I didn't get it either by ./run_test.sh -8 or tox -e pep8 in my
 local test env, I am pretty sure I have the latest nova code so I think
 I should get same result ?

 Thanks a lot

 Best Regards!

 Kevin (Chen) Ji 纪 晨

 Engineer, zVM Development, CSTL
 Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
 Phone: +86-10-82454158
 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
 District, Beijing 100193, PRC


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Stale venv?  Try tox -r -e pep8.

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] local and gate pep8 check comparsion

[Chen CH Ji]

I got following error in patch https://review.openstack.org/#/c/137009/
from Jenkins

2015-01-06 12:24:20.445 | ./nova/compute/manager.py:5325:13: N331  Use
LOG.warning due to compatibility with py3
2015-01-06 12:24:20.445 | ./nova/compute/manager.py:5726:13: N331  Use
LOG.warning due to compatibility with py3
2015-01-06 12:24:20.916 | ERROR: InvocationError:
'/home/jenkins/workspace/gate-nova-pep8/.tox/pep8/bin/flake8'

but I didn't get it either by ./run_test.sh -8 or tox -e pep8 in my local
test env, I am pretty sure I have the latest nova code so I think I should
get same result ?

Thanks a lot

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Whether microversion implementation only need to be applied to first layer API?

[Chen CH Ji]

During
http://lists.openstack.org/pipermail/openstack-dev/2015-March/059000.html,
we had some discussions on
whether we need version specific code remaining even we suggest user can
use API version directly in API,  [1][2] aiming to remove that
And if we should keep following stuff , then [3][4]  might be thought
because of some potential issue

can someone give some suggestions ? thanks

[1]https://review.openstack.org/#/c/164229/
[2]https://review.openstack.org/#/c/164234/
[3]https://review.openstack.org/#/c/144998/
[4]https://review.openstack.org/#/c/145240/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC__
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

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

[Chen CH Ji]

oops, duplication ... I submitted changes to spec after got this info since
it make sense to me ...

https://review.openstack.org/#/c/164229/
https://review.openstack.org/#/c/164234/

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Alex Xu sou...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   03/16/2015 02:53 AM
Subject:Re: [openstack-dev] [nova] is it possible to microversion a
static class method?





2015-03-16 9:48 GMT+08:00 Alex Xu sou...@gmail.com:


  2015-03-13 19:10 GMT+08:00 Sean Dague s...@dague.net:
   On 03/13/2015 02:55 AM, Chris Friesen wrote:
On 03/12/2015 12:13 PM, Sean Dague wrote:
On 03/12/2015 02:03 PM, Chris Friesen wrote:
Hi,
   
I'm having an issue with microversions.
   
The api_version() code has a comment saying This decorator MUST
   appear
first (the outermost decorator) on an API method for it to work
correctly
   
I tried making a microversioned static class method like this:
   
         @wsgi.Controller.api_version(2.4)  # noqa
         @staticmethod
         def _my_func(req, foo):
   
and pycharm highlighted the api_version decorator and complained
   that
This decorator will not receive a callable it may expect; the
   built-in
decorator returns a special object.
   
Is this a spurious warning from pycharm?  The pep8 checks don't
complain.
   
If I don't make it static, then pycharm suggests that the method
   could
be static.
   
*API method*
   
This is not intended for use by methods below the top controller
   level.
If you want conditionals lower down in your call stack pull the
   request
version out yourself and use that.
   
Both the original spec and doc/source/devref/api_microversions.rst
contain text talking about decorating a private method.  The latter
gives this example:
   
        @api_version(2.1, 2.4)
        def _version_specific_func(self, req, arg1):
            pass
   
        @api_version(min_version=2.5) #noqa
        def _version_specific_func(self, req, arg1):
            pass
   
        def show(self, req, id):
             common stuff 
            self._version_specific_func(req, foo)
             common stuff 
   
It's entirely possible that such a private method might not need to
reference self, and could therefore be static, so I think it's a
   valid
question.

   That's a doc bug, we should change it.


  Actually it is not a bug. It's controversial point in the spec, but
  finally that was keep in the spec.
  
http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/api-microversions.html

  The discussion at line 268
  
https://review.openstack.org/#/c/127127/7/specs/kilo/approved/api-microversions.rst

Submit a patch for devref https://review.openstack.org/164555  Let see
whether we can get agreement



           -Sean

   --
   Sean Dague
   http://dague.net

   __

   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 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 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

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

[Chen CH Ji]

I would think a on v2 extension is needed
for v2.1 , mircoversion is a way but not very sure it's needed.

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Chris Friesen chris.frie...@windriver.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   03/11/2015 04:35 PM
Subject:[openstack-dev] [nova] need input on possible API change for
bug #1420848




Hi,

I'm working on bug #1420848 which addresses the issue that doing a
service-disable followed by a service-enable against a down compute
node
will result in the compute node going up for a while, possibly causing
delays
to operations that try to schedule on that compute node.

The proposed solution is to add a new reported_at field in the DB schema
to
track when the service calls _report_state().

The backend is straightforward, but I'm trying to figure out the best way
to
represent this via the REST API response.

Currently we response includes an updated_at property, which maps
directly to
the auto-updated updated_at field in the database.

Would it be acceptable to just put the reported_at value (if it exists)
in the
updated_at property?  Logically the reported_at value is just a
determination of when the service updated its own state, so an argument
could be
made that this shouldn't break anything.

Otherwise, by my reading of

https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK
 it
seems like if I wanted to add a new reported_at property I would need to
do it
via an API extension.

Anyone have opinions?

Chris

__
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 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

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

[Chen CH Ji]

FYI :)
you may take a look at doc/source/devref/api_plugins.rst which was merged
recently
you can take a look at
http://lists.openstack.org/pipermail/openstack-dev/2015-March/058493.html
and its follow up discussion


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Chris Friesen chris.frie...@windriver.com
To: openstack-dev@lists.openstack.org
Date:   03/11/2015 11:44 PM
Subject:Re: [openstack-dev] [nova] need input on possible API change
for bug #1420848




I can see how to do a v2 extension following the example given for
extended_services.py and extended_services_delete.py.  That seems to be
working now.

I'm not at all clear on how to go about doing the equivalent for v2.1.
Does
that use the api/openstack/compute/plugins/v3/ subdirectory?   Is it
possible to
do the equivalent to the v2 extended_services.py (where the code in
api/openstack/compute/plugins/v3/services.py checks to see if the other
extension is enabled) or do I have to write a whole new extension that
builds on
the output of api/openstack/compute/plugins/v3/services.py?

Thanks,
Chris


On 03/11/2015 09:51 AM, Chen CH Ji wrote:
 I would think a on v2 extension is needed
 for v2.1 , mircoversion is a way but not very sure it's needed.

 Best Regards!

 Kevin (Chen) Ji 纪 晨

 Engineer, zVM Development, CSTL
 Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
 Phone: +86-10-82454158
 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
 Beijing 100193, PRC

 Inactive hide details for Chris Friesen ---03/11/2015 04:35:01 PM---Hi,
I'm
 working on bug #1420848 which addresses the issue tChris Friesen
---03/11/2015
 04:35:01 PM---Hi, I'm working on bug #1420848 which addresses the issue
that doing a

 From: Chris Friesen chris.frie...@windriver.com
 To: OpenStack Development Mailing List (not for usage questions)
 openstack-dev@lists.openstack.org
 Date: 03/11/2015 04:35 PM
 Subject: [openstack-dev] [nova] need input on possible API change for bug
#1420848








 Hi,

 I'm working on bug #1420848 which addresses the issue that doing a
 service-disable followed by a service-enable against a down compute
node
 will result in the compute node going up for a while, possibly causing
delays
 to operations that try to schedule on that compute node.

 The proposed solution is to add a new reported_at field in the DB
schema to
 track when the service calls _report_state().

 The backend is straightforward, but I'm trying to figure out the best way
to
 represent this via the REST API response.

 Currently we response includes an updated_at property, which maps
directly to
 the auto-updated updated_at field in the database.

 Would it be acceptable to just put the reported_at value (if it exists)
in the
 updated_at property?  Logically the reported_at value is just a
 determination of when the service updated its own state, so an argument
could be
 made that this shouldn't break anything.

 Otherwise, by my reading of
 
https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK
 it
 seems like if I wanted to add a new reported_at property I would need
to do it
 via an API extension.

 Anyone have opinions?

 Chris


__
 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 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 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 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

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

[Chen CH Ji]

I posted same question below yesterday, not sure why it's not posted in the
list ...


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Chris Friesen chris.frie...@windriver.com
To: openstack-dev@lists.openstack.org
Date:   03/13/2015 07:57 AM
Subject:Re: [openstack-dev] [nova] is it possible to microversion a
static class method?



On 03/12/2015 12:13 PM, Sean Dague wrote:
 On 03/12/2015 02:03 PM, Chris Friesen wrote:
 Hi,

 I'm having an issue with microversions.

 The api_version() code has a comment saying This decorator MUST appear
 first (the outermost decorator) on an API method for it to work
correctly

 I tried making a microversioned static class method like this:

  @wsgi.Controller.api_version(2.4)  # noqa
  @staticmethod
  def _my_func(req, foo):

 and pycharm highlighted the api_version decorator and complained that
 This decorator will not receive a callable it may expect; the built-in
 decorator returns a special object.

 Is this a spurious warning from pycharm?  The pep8 checks don't
complain.

 If I don't make it static, then pycharm suggests that the method could
 be static.

 *API method*

 This is not intended for use by methods below the top controller level.
 If you want conditionals lower down in your call stack pull the request
 version out yourself and use that.

Both the original spec and doc/source/devref/api_microversions.rst contain
text
talking about decorating a private method.  The latter gives this example:

 @api_version(2.1, 2.4)
 def _version_specific_func(self, req, arg1):
 pass

 @api_version(min_version=2.5) #noqa
 def _version_specific_func(self, req, arg1):
 pass

 def show(self, req, id):
  common stuff 
 self._version_specific_func(req, foo)
  common stuff 

It's entirely possible that such a private method might not need to
reference
self, and could therefore be static, so I think it's a valid question.

Chris

__
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 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

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

[Chen CH Ji]

Know it's a little bit tricky but from
doc/source/devref/api_microversions.rst,
can we make _version_specific_func static function thought it's not
required or we can explicitly suggest not to do so...


 91 @api_version(2.1, 2.4)
 92 def _version_specific_func(self, req, arg1):
 93 pass
 94
 95 @api_version(min_version=2.5) #noqa
 96 def _version_specific_func(self, req, arg1):
 97 pass
 98
 99 def show(self, req, id):
100  common stuff 
101 self._version_specific_func(req, foo)
102  common stuff 

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Sean Dague s...@dague.net
To: openstack-dev@lists.openstack.org
Date:   03/12/2015 07:16 PM
Subject:Re: [openstack-dev] [nova] is it possible to microversion a
static class method?



On 03/12/2015 02:03 PM, Chris Friesen wrote:
 Hi,

 I'm having an issue with microversions.

 The api_version() code has a comment saying This decorator MUST appear
 first (the outermost decorator) on an API method for it to work
correctly

 I tried making a microversioned static class method like this:

 @wsgi.Controller.api_version(2.4)  # noqa
 @staticmethod
 def _my_func(req, foo):

 and pycharm highlighted the api_version decorator and complained that
 This decorator will not receive a callable it may expect; the built-in
 decorator returns a special object.

 Is this a spurious warning from pycharm?  The pep8 checks don't complain.

 If I don't make it static, then pycharm suggests that the method could
 be static.

*API method*

This is not intended for use by methods below the top controller level.
If you want conditionals lower down in your call stack pull the request
version out yourself and use that.

 -Sean

--
Sean Dague
http://dague.net

__
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 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

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

[Chen CH Ji]

+1

and +1 for not a core :)

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Davanum Srinivas dava...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   04/30/2015 03:14 PM
Subject:Re: [openstack-dev] [nova] Proposal to add Melanie Witt to
nova-core



+1 from me as well! (Ditto as Ed, not a core).

-- dims

On Thu, Apr 30, 2015 at 9:00 AM, Ed Leafe e...@leafe.com wrote:
 On Apr 30, 2015, at 6:30 AM, John Garbutt j...@johngarbutt.com wrote:

 I propose we add Melanie to nova-core.

 I know I'm not core, so my vote doesn't count, but I think that this
would be a great addition.

 +1

 -- Ed Leafe







__
 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




--
Davanum Srinivas :: https://twitter.com/dims

__
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 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] [cinder][nova] Question on Cinder client exception handling

[Chen CH Ji]

Hi
   In order to work on [1] , nova need to know what kind of
exception are raised when using cinderclient so that it can handle like [2]
did?
   In this case, we don't need to distinguish the error case
based on string compare , it's more accurate and less error leading
   Anyone is doing it or any other methods I can use to catch
cinder specified  exception in nova? Thanks


[1] https://bugs.launchpad.net/nova/+bug/1450658
[2]
https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L64

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC__
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

Re: [openstack-dev] [cinder][nova] Question on Cinder client exception handling

[Chen CH Ji]

no, I only want to confirm whether cinder folks is doing this or there are
already tricks can be used that before submit the change ... thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Date:   05/07/2015 10:12 PM
Subject:Re: [openstack-dev] [cinder][nova] Question on Cinder client
exception handling





On 5/6/2015 7:02 AM, Chen CH Ji wrote:
 Hi
 In order to work on [1] , nova need to know what kind of
 exception are raised when using cinderclient so that it can handle like
 [2] did?
 In this case, we don't need to distinguish the error
 case based on string compare , it's more accurate and less error leading
 Anyone is doing it or any other methods I can use to
 catch cinder specified  exception in nova? Thanks


 [1] https://bugs.launchpad.net/nova/+bug/1450658
 [2]

https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L64


 Best Regards!

 Kevin (Chen) Ji 纪 晨

 Engineer, zVM Development, CSTL
 Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
 Phone: +86-10-82454158
 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
 District, Beijing 100193, PRC



__
 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


Is there anything preventing us from adding a more specific exception to
cinderclient and then once that's in and released, we can pin the
minimum version of cinderclient in global-requirements so nova can
safely use it?

--

Thanks,

Matt Riedemann


__
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 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] [nova] Which error code should we return when OverQuota

[Chen CH Ji]

In doing patch [1], A suggestion is submitted that we should return 400
(bad Request) instead of 403 (Forbidden)
I take a look at [2], seems 400 is not a good candidate because
'The request could not be understood by the server due to malformed syntax.
The client SHOULD NOT repeat the request without modifications. '

may be a 409 (conflict) error if we really don't think 403 is a good one?
Thanks


[1] https://review.openstack.org/#/c/173985/
[2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC__
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

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

[Chen CH Ji]

+1
I can't believe we lost him When we met in Hongkong summit his smile
give me very deep impression...
he is very helpful to me from the first day I contribute to community and I
learnt a lot from him

May his soul rest in peace

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Qiao, Liyong liyong.q...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   04/08/2015 11:30 AM
Subject: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 2.1 micro version api.

I hot he will leave in peace and won’t be worry about the review duty in
heaven.
I will never forget his word when ending the scrum, “let talk it tomorrow,
CU”

BR, Eli(Li Yong)Qiao

From: Alex Xu [mailto:sou...@gmail.com]
Sent: Wednesday, April 08, 2015 5:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] In loving memory of Chris Yeoh

Feel very sad. Just few weeks ago, I still saw him active on the community.
Really hard believe this happen such suddenly.

He was my leader in IBM and mentored me on the openstack community also,
offered lots of help without reservation, really
learn a lot from him.  We have phone call meeting every morning before, he
always sounds happy and enthusiastic even after
he got health problem.
May his soul rest in peace.

2015-04-08 12:49 GMT+08:00 Michael Still mi...@stillhq.com:


 It is my sad duty to inform the community that Chris Yeoh passed away this
 morning. Chris leaves behind a daughter Alyssa, aged 6, who I hope will
 remember Chris as the clever and caring person that I will remember him
 as. I haven’t had a chance to confirm with the family if they want flowers
 or a donation to a charity. As soon as I know those details I will reply
 to this email.


 Chris worked on open source for a very long time, with OpenStack being
 just the most recent in a long chain of contributions. He worked
 tirelessly on his contributions to Nova, including mentoring other
 developers. He was dedicated to the cause, with a strong vision of what
 OpenStack could become. He even named his cat after the project.


 Chris might be the only person to have ever sent an email to his coworkers
 explaining what his code review strategy would be after brain surgery. It
 takes phenomenal strength to carry on in the face of that kind of
 adversity, but somehow he did. Frankly, I think I would have just sat on
 the beach.


 Chris was also a contributor to the Linux Standards Base (LSB), where he
 helped improve the consistency and interoperability between Linux
 distributions. He ran the ‘Hackfest’ programming contests for a number of
 years at Australia’s open source conference -- linux.conf.au. He supported
 local Linux user groups in South Australia and Canberra, including
 involvement at installfests and speaking at local meetups. He competed in
 a programming challenge called Loki Hack, and beat out the world to win
 the event[1].


 Alyssa’s memories of her dad need to last her a long time, so we’ve
 decided to try and collect some fond memories of Chris to help her along
 the way. If you feel comfortable doing so, please contribute a memory or
 two at
 
https://docs.google.com/forms/d/1kX-ePqAO7Cuudppwqz1cqgBXAsJx27GkdM-eCZ0c1V8/viewform


 Chris was humble, helpful and honest. The OpenStack and broader Open
 Source communities are poorer for his passing.


 Michael


 [1] http://www.lokigames.com/hack/

 __
 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 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 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] [nova] How to microversion API code which is not in API layer

[Chen CH Ji]

Hi
 We have [1] in the db layer and it's directly used by API
layer , the filters is directly from client's input
 In this case, when doing [2] or similar changes, do we need to
consider microversion usage when we change options?
 Thanks

[1]
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L4440
[2] https://review.openstack.org/#/c/144883

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC__
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

Re: [openstack-dev] [nova] API: Question on 'Retry-After': 0 in HTTPForbidden

[Chen CH Ji]

ok thanks for confirm, I will file a bug and fix it~,

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Alex Xu hejie...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date:   08/19/2015 08:14 AM
Subject:Re: [openstack-dev] [nova] API: Question on 'Retry-After': 0 in
HTTPForbidden



+1 for Retry-After is wrong for quota case

  在 2015年8月19日，下午1:32，GHANSHYAM MANN ghanshyamm...@gmail.com
  写道：

  Retry-After
__
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 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

Re: [openstack-dev] [nova] compute - conductor and version compatibility

[Chen CH Ji]

I remembered I saw somewhere about how to upgrade, (step by step in
updating from J to K or others)
I think it's best and suitable way to use this kind of 'different version'
talking to make compute host alive
during system upgrade.


so I believe controller should be upgrade first the compute node to be
update set by set
that means Kilo conductor should works with Juno compute
but on the contrary I didn't see a value for supporting it

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Jay Pipes jaypi...@gmail.com
To: openstack-dev@lists.openstack.org
Date:   08/17/2015 05:01 PM
Subject:Re: [openstack-dev] [nova] compute - conductor and version
compatibility



On 08/17/2015 10:41 AM, Markus Zoeller wrote:
 I have the impression that more and more people try to run OpenStack
 in a mixed-releases-mode and face some troubles to understand how
 the capabilities and limitations look like. For example, the reporter
 of [1] runs a nova-conductor (Juno) with a nova-compute (Kilo). I tried
 in comment #3 of [1] to rationalize if this is a valid setup or not
 and I failed...
 If someone with more experience and knowledge could help there and
 clarify it also for other users in the future, that would be awesome.

 [1] https://bugs.launchpad.net/nova/+bug/1483321

No, that's not valid behaviour. You need to upgrade the controller
infrastructure (conductor, API nodes, etc) before any compute nodes.

Best,
-jay

__
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 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] [nova] API: Question on 'Retry-After': 0 in HTTPForbidden

[Chen CH Ji]

When doing patch[1] Ken'ichi raise a good suggestion on not raise
Retry-After according to [2]

seems nova also when doing create[3] and resize[4] a server nova may raise
those, too
is this a bug or something made on purpose? Thanks

[1]
https://review.openstack.org/#/c/180469/5/nova/api/openstack/compute/tenant_networks.py
[2]http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
[3]
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L591
[4]
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L846

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC__
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

Re: [openstack-dev] [nova] [python-novaclient] microversions support

[Chen CH Ji]

+1 , added a doc change just now  https://review.openstack.org/#/c/253644 -"Kevin L. Mitchell"  wrote: -To: From: "Kevin L. Mitchell" Date: 12/04/2015 06:25PMSubject: Re: [openstack-dev] [nova] [python-novaclient] microversions supportOn Fri, 2015-12-04 at 18:58 +0200, Andrey Kurilin wrote:> This week I added 5 patches to enable 2.7-2.11 microversions in> novaclient[1][2][3][4][5]. I'm not bragging. Just want to ask everyone> who are working on new microversions: Please, do not forget to add> support of your microversion to official Nova client.Perhaps this is something we should add to the review guidelines—no APIchange can be merged to nova unless there is a pending change tonovaclient to add support?  We already more or less enforce the criteriathat no addition to novaclient can be added unless the correspondingnova change has been merged…-- Kevin L. Mitchell Rackspace__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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] [nova][API]what's the purpose of fping in nova API?

[Chen CH Ji]

 In doing some API work on http://developer.openstack.org/api-ref-compute-v2.1.htmlnoticed that fping was [1] and try to ping the instance to check whether it's pingable or not..but this is running on API service host which mostly have no access to instance with private IP?Just curious about it ...[1] https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/fping.py#L53


__
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] [nova][virt] rebuild action not in support-matrix

[Chen CH Ji]

 Hi   We have been trying to enablement of our CI work for our nova virt layer code ,so we need to configure the tempest cases based on our nova driver capability  I found that rebuild action is not listed in [1] (only talk about rebuild in evacuate), but code [2] seems support virt layer abstraction   can someone point the rebuild action in [1] or it's missing on purpose ? Thanks[1]http://docs.openstack.org/developer/nova/support-matrix.html[2]https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2920


__
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

Re: [openstack-dev] [nova][API]what's the purpose of fping in nova API?

[Chen CH Ji]

ok, a potential work for N release, thanks-Sean Dague <s...@dague.net> wrote: -To: openstack-dev@lists.openstack.orgFrom: Sean Dague <s...@dague.net>Date: 02/01/2016 11:07AMSubject: Re: [openstack-dev] [nova][API]what's the purpose of fping in nova API?On 01/29/2016 09:18 AM, Chen CH Ji wrote:> In doing some API work on> http://developer.openstack.org/api-ref-compute-v2.1.html> noticed that fping was [1] and try to ping the instance to check whether> it's pingable or not..> but this is running on API service host which mostly have no access to> instance with private IP?> Just curious about it ...> > > [1]> https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/fping.py#L53fping is probably an API we should deprecate, as you've seen, it'shighly foulable and requires a network topology that people may not have.-Sean-- Sean Daguehttp://dague.net__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev[attachment "signature.asc" removed by Chen CH Ji/China/IBM]


__
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] [nova][API] Question about HTTPNotImplementError

[Chen CH Ji]

In reading some API guide line doc [1] seems we should not return 501 to clientbut nova still doing so at API layer [2], any discussion before about this can be referred ? [1]https://github.com/openstack/api-wg/blob/master/guidelines/http.rst#use-of-501---not-implemented[2]https://github.com/openstack/nova/blob/master/nova/api/openstack/common.py#L536


__
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

Re: [openstack-dev] [nova][virt] rebuild action not insupport-matrix

[Chen CH Ji]

 ok, thanks, guess even if all virt layer support this 'rebuild' , we can still say it's supported by all hypervisors so others can take it as a reference, will submit a new patch for it, thanks-"Daniel P. Berrange" <berra...@redhat.com> wrote: -To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>From: "Daniel P. Berrange" <berra...@redhat.com>Date: 02/02/2016 10:21AMSubject: Re: [openstack-dev] [nova][virt] rebuild action not insupport-matrixOn Mon, Feb 01, 2016 at 05:04:37PM -0700, Matt Riedemann wrote:> > > On 2/1/2016 12:39 PM, Chen CH Ji wrote:> >Hi> >           We have been trying to enablement of our CI work for our nova> >virt layer code ,so we need to configure the tempest cases based on our> >nova driver capability> >           I found that rebuild action is not listed in [1] (only talk> >about rebuild in evacuate), but code [2] seems support virt layer> >abstraction> >           can someone point the rebuild action in [1] or it's missing> >on purpose ? Thanks> >> >[1]http://docs.openstack.org/developer/nova/support-matrix.html> >[2]https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2920> >> >> >> >__> >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> >> > Only the Ironic driver overrides the rebuild method, otherwise the compute> manager has a default impl, so it's technically implemented for all virt> drivers. There is also confusion around rebuild vs evacuate since both> operations go through the rebuild_instance method in the compute manager,> they are just separated by the 'recreate' parameter.> > danpb might have reasons for not listing rebuild in the hypervisor support> matrix - it might have just never been on the original wiki matrix. It'd be> worth asking him.The hypervisor matrix just copied the data from the original wiki. It iscertainly not a complete list of all features that are relevant. You couldmake the matrix x10 bigger and it still wouldn't cover all interesting factsacross virt drivers. If anyone has things they want shown they should submitpatches> But at the same time, since there is a default implementation, I'm also not> sure if it's worth listing separately in the support matrix (but is also> confusing I suppose to not list it at all).That there is a default impl is really just an impl detail - if it is aninteresting feature from the user POV it is worth listing IMHORegards,Daniel-- |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :||: http://libvirt.org              -o-             http://virt-manager.org :||: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :||: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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

Re: [openstack-dev] nova cli commands fail with 404. devstack installation from today

[Chen CH Ji]

 Guess it's image-list instead of image list,right?  maybe you can check with nova --debug image-list and see the API which wassend to nova-api server then analyze the nova api log to know what's exactly the error?-"Bob Hansen"  wrote: -To: openstack-dev@lists.openstack.orgFrom: "Bob Hansen" Date: 01/20/2016 10:31PMSubject: [openstack-dev] nova cli commands fail with 404. devstackinstallation from todayInstalled devstack today, this morning actually,  and most everything works except simple nova cli commands, nova image list, list, flavor-list all fail) glance ok, nuetron ok, As an example, nova image list returns:devstack$ nova image listERROR (NotFound): The resource could not be found. (HTTP 404)However the command; openstack image list returns the correct list of cirros images, plus one I have already imported.key.log has:127.0.0.1 - - [20/Jan/2016:21:10:49 +] "POST /tokens HTTP/1.1" 404 93 "-" "keystoneauth1/2.2.0 python-requests/2.9.1 CPython/2.7.6" 2270(us)Clearly an authentication thing. Since other commands work, e.g. neutorn subnet-list, I concluded keystone auth is just fine.I suspect it is something in nova.conf. [keystone_auth] has this in it, which stack.sh built[keystone_authtoken]signing_dir = /var/cache/novacafile = /opt/stack/data/ca-bundle.pemauth_uri = http://127.0.0.1:5000project_domain_id = defaultproject_name = serviceuser_domain_id = defaultpassword = secretserviceusername = novaauth_url = http://127.0.0.1:35357auth_type = passwordAny suggestions on where else to look?Bob Hansenz/VM OpenStack Enablement 
__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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

Re: [openstack-dev] [Nova][API] Does nova API allow the server_id parem as DB index?

[Chen CH Ji]

+1 for no microversion, it's internal implementation and we should be free to remove it since we didn't document it anywhere-GHANSHYAM MANN  wrote: -To: "OpenStack Development Mailing List (not for usage questions)" From: GHANSHYAM MANN Date: 02/16/2016 03:49AMSubject: Re: [openstack-dev] [Nova][API] Does nova API allow the server_id parem as DB index?Yes, currently Nova support that for show/update/delete server APIs etc (both v2 and v2.1) and python-novaclient too. But I think that was old behaviour and for ec2 API mainly?I searched on ec2 repo [1] and they get the instance from nova using UUID, i did not find any place they are fetching using id. Hut not sure if external interface directly fetch that on nova by 'id'.But apart from that, may be some users using 'id' instead of 'uuid' but that was not recommended or documented anywhere So in that case can we remove this old behaviour without version bump?[1].. https://github.com/openstack/ec2-apiRegardsGhanshyam MannOn Tue, Feb 16, 2016 at 11:24 AM, Anne Gentle  wrote:On Mon, Feb 15, 2016 at 6:03 PM, 少合冯  wrote:I guess others may ask the same questions. I read the nova API doc: such as this API: http://developer.openstack.org/api-ref-compute-v2.1.html#showServerGET /v2.1/​{tenant_id}​/servers/​{server_id}​Show server detailsRequest parametersParameterStyleTypeDescriptiontenant_idURIcsapi:UUIDThe UUID of the tenant in a multi-tenancy cloud.server_idURIcsapi:UUIDThe UUID of the server.But I can get the server by DB index: curl -s -H X-Auth-Token:6b8968eb38df47c6a09ac9aee81ea0c6 http://192.168.2.103:8774/v2.1/f5a8829cc14c4825a2728b273aa91aa1/servers/2{    "server": {        "OS-DCF:diskConfig": "MANUAL",        "OS-EXT-AZ:availability_zone": "nova",        "OS-EXT-SRV-ATTR:host": "shaohe1",        "OS-EXT-SRV-ATTR:hypervisor_hostname": "shaohe1",        "OS-EXT-SRV-ATTR:instance_name": "instance-0002",        "OS-EXT-STS:power_state": 1,        "OS-EXT-STS:task_state": "migrating",        "OS-EXT-STS:vm_state": "error",        "OS-SRV-USG:launched_at": "2015-12-18T07:41:00.00",        "OS-SRV-USG:terminated_at": null,        ..    }}and the code really allow it use  DB indexhttps://github.com/openstack/nova/blob/master/nova/compute/api.py#L1939Nice find. Can you log this as an API bug and we'll triage it -- can even help you fix it on the site if you like. https://bugs.launchpad.net/openstack-api-site/+filebugBasically, click that link, write a short summary, then copy and paste in this email's contents, it has lots of good info.Let me know if you'd also like to fix the bug on the site.And hey nova team, if you think it's actually an API bug, we'll move it over to you.Thanks for reporting it!Anne __OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev-- Anne GentleRackspacePrincipal Engineerwww.justwriteclick.com__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

[Chen CH Ji]

 agree we can ask people to submit their requirement through backlog spec but not sure it might have too much process sometimes the bug opener is not a developer, it might be some operatoror openstack user, they just want to get it done but they don't know more detailso we can keep the wishlist and cleanup it and mark it invalid as you suggestedlike 6 month or 1 year, but mark the bug which may contains valid request Invalid like [1] right afterwe found it's not current supported seems too rush[1]https://bugs.launchpad.net/bugs/1556756-Matt Riedemann  wrote: -To: openstack-dev@lists.openstack.orgFrom: Matt Riedemann Date: 03/15/2016 02:50PMSubject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?On 3/15/2016 8:37 AM, Chris Dent wrote:> On Tue, 15 Mar 2016, Markus Zoeller wrote:>>> Long story short, I'm in favor of abandoning the use of "wishlist">> as an importance in bug reports to track requests for enhancements.>> While I'm very much in favor of limiting the amount of time issues> (of any sort) linger in launchpad[1] I worry that if we stop making> "wishlist" available as an option then people who are not well> informed about the complex system for achieving features in Nova> will have no medium to get their ideas into the system. We want> users to sometime be able to walk up, drop an idea and move on without> having to be responsible for actually doing that work. If we insist> that such ideas must go through the blueprint process then most> ideas will be left unstated.We do have a way for people to drop off RFEs/ideas for features without actually providing design details, which is the backlog specs:https://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html>> What I think we need to do instead is fix this problem:>>> * we don't have a process to transform wishlist bugs to blueprints>> such that we do have a process of some kind where a wishlist idea> either gets an owner who starts the blueprint process (because it is> just that cool) or dies from lack of attention.>> It's clear, though, that we already have a huge debt in bug/issue> management so adding yet another task is hard to contemplate.>> I think we can address some of that by more quickly expiring bugs> that have had no recent activity or attention, on the assumption> that:>> * They will come back up again if they are good ideas or real bugs.> * Lack of attention is a truthy signal of either lack of resources or lack>    of importance.>> What needs to happen is that fewer things which are not actionable> or nobody is interested in show up when traversing the bugs looking> for something to work on.>> I'm happy to help some of this become true, in part because of [1]> below.>> [1] I've recently spent a bit of time chasing bugs tagged> "scheduler" and far too many of them are so old that it's impossible> to tell whether they matter any more, and many of them are confused> by patches and people who have gone in and out of existence. It's> challenging to tease out what can be done and the information has> very little archival value. It should go off the radar. Having a> bunch of stuff that looks like it needs to be done but never> actually is is stop energy and depressing. __> 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>We need to shrink the nova bug backlog. I'd say any wishlist bugs that are open for over a year (maybe even 6 months) should be marked Invalid with a comment saying to file a blueprint or a backlog spec (with links on how to do that).-- Thanks,Matt Riedemann__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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] [nova][novaclient]novaclient backward compatible changes

[Chen CH Ji]

 From [1], some questions raised is whether and how we will guarantee the return value of novaclient? e.g some toolssuch as openstackclient utilize novaclient return value , we don't have microversion mechanism (and seems not helpfuland too heavy) to do those kind of changes... so novaclient should make every changes backward compatible?BTW: [1] seems not mandatory(better to have), so the question is related to the patch, just for general idea..[1] https://review.openstack.org/#/c/291915/1


__
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

Re: [openstack-dev] [nova] api-ref sprint today & wed

[Chen CH Ji]

+1 to include .inc in the commit message, I also have to manually search in the open list
 
 
- Original message -From: Augustina Ragwitz To: OpenStack Development Mailing List  (not for usage questions)Cc:Subject: Re: [openstack-dev] [nova] api-ref sprint today & wedDate: Tue, May 10, 2016 12:29 AM 
Currently it's really hard to tell (at least to me) which files havepatches against them and which don't. I've had to manually make aspreadsheet because it's not obvious to me, at a glance, from thecurrent commit messages, and I've accidentally started work on severalfiles that already have owners. Maybe if people could put the .incfilename in their commit message, or maybe we could agree on aconsistent commit message for whichever phase we're on, it would beeasier to tell, at a glance from the list, what's already being workedon. Other suggestions welcome, or if there's another list somewhere Idon't know about, a link to that would be great.This is the list I'm referring to:https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:openThanks!Augustina--Augustina RagwitzSr Systems Software Engineer, HPE CloudHewlett Packard Enterprise---irc: auggy__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
 


__
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

Re: [openstack-dev] [nova] Proposing Andrey Kurilin for python-novaclient core

[Chen CH Ji]

+1
 
 
- Original message -From: Boris Pavlovic To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [nova] Proposing Andrey Kurilin for python-novaclient coreDate: Thu, Apr 14, 2016 8:07 AM 
Great!
 
On Wed, Apr 13, 2016 at 2:56 PM, Sylvain Bauza  wrote:

Le 13/04/2016 19:53, Matt Riedemann a écrit :
I'd like to propose that we make Andrey Kurilin core on python-novaclient.He's been doing a lot of the maintenance the last several months and a lot of times is the first to jump on any major issue, does a lot of themicroversion work, and is also working on cleaning up docs and helping me with planning releases.His work is here [1].Review stats for the last 4 months (although he's been involved in the project longer than that) [2].Unless there is disagreement I plan to make Andrey core by the end of the week.[1] https://review.openstack.org/#/q/owner:akurilin%2540mirantis.com+project:openstack/python-novaclient[2] http://stackalytics.com/report/contribution/python-novaclient/120  +1.
__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 


__
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] [stable][liberty] [cinder] is stable liberty broken?

[Chen CH Ji]

Hi,
  I am backporting https://review.openstack.org/#/c/333749/ 
  to stable/liberty and failed in gating job, then I submitted another doc change https://review.openstack.org/#/c/338699/  to verify and seems failed with same reason and I have no idea what's wrong in test... can someone help to take a look or give some hint?
 
error is :

ft17.1: cinder.tests.unit.api.contrib.test_quotas.QuotaSetsControllerTest.test_delete_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "cinder/tests/unit/api/contrib/test_quotas.py", line 100, in setUp
self.fixture = self.useFixture(config_fixture.Config(auth_token.CONF))
AttributeError: 'module' object has no attribute 'CONF'


__
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

Re: [openstack-dev] [nova] scaling rabbitmq with cells v2 requires manual database update

[Chen CH Ji]

Should be this one https://bugs.launchpad.net/nova/+bug/1664913 and
https://review.openstack.org/434179 ?

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Corey Bryant <corey.bry...@canonical.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date:   02/16/2017 05:37 AM
Subject:Re: [openstack-dev] [nova] scaling rabbitmq with cells v2
requires manual database update





On Wed, Feb 15, 2017 at 4:34 PM, Corey Bryant <corey.bry...@canonical.com>
wrote:

  On Wed, Feb 15, 2017 at 4:26 PM, melanie witt <melwi...@gmail.com> wrote:
   On Wed, 15 Feb 2017 16:12:14 -0500, Corey Bryant wrote:
 This works but you have to specify all of the args (--cell_uuid,
 --name,
 --transport-url and --database_connection).  Otherwise you'll hit
 this: http://paste.ubuntu.com/24003055/

   Corey,

   Thanks for pointing that out.

   It looks like the command intended to have --transport-url and
   --database_connection as optional but missed defaulting them to None in
   the function parameter list.

   -melanie

  I think I figured it out.  I'll submit a patch in a little bit.



You're correct btw :)


--
Regards,
Corey
__
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 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] [glance][cinder][nova] zip for raw Disk Format

[Chen CH Ji]

From [1] we support a few common and vendor specific disk format, as use
raw image sometimes will be very big and do we have existing any method to
consider zip the raw disk so the disk space might be saved as an option to
offer to end user and admin  ? so something like [2] could be enhanced to
support zipped format?
Thanks

[1] http://docs.openstack.org/developer/glance/formats.html
[2]
https://github.com/openstack/cinder/blob/master/cinder/image/image_utils.py#L182

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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

Re: [openstack-dev] [glance][cinder][nova] zip for raw Disk Format

[Chen CH Ji]

Thanks for the reply

the question is how can I distinguish the image in 'real' qcow2 format ? I
mean, considering cinder copy from image to volume case,
I need first download that image from glance, then copy contents to
volume ,'real' qcow2 will keep the image while I expect the qcow2
to be converted into raw format within the given command, without a
explicit format, how to decide whether the convent will be made or not?

Thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eric Harney <ehar...@redhat.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date:   10/05/2016 06:19 PM
Subject:Re: [openstack-dev] [glance][cinder][nova] zip for raw Disk
Format



On 10/05/2016 05:46 AM, Chen CH Ji wrote:
>
> From [1] we support a few common and vendor specific disk format, as use
> raw image sometimes will be very big and do we have existing any method
to
> consider zip the raw disk so the disk space might be saved as an option
to
> offer to end user and admin  ? so something like [2] could be enhanced to
> support zipped format?
> Thanks
>

The qcow2 format supports compression and is one of the most widely
supported image formats that can be used with OpenStack.

You can convert a raw image to qcow2 with:
 $ qemu-img convert -f raw -O qcow2 -c image.raw image.qcow2

And then upload image.qcow2 to Glance.

> [1] http://docs.openstack.org/developer/glance/formats.html
> [2]
>
https://github.com/openstack/cinder/blob/master/cinder/image/image_utils.py#L182

>
> Best Regards!
>
> Kevin (Chen) Ji 纪 晨
>
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
> Phone: +86-10-82454158
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
> Beijing 100193, PRC
>


__
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 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] [nova] mutate config options on compute service

[Chen CH Ji]

According to http://docs.openstack.org/newton/config-reference/mutable.html
, seems this option is valid to compute service (as it says: Log onto the
compute node. )
but from following test result seems it's not honored by compute service,
is it a bug or wrong usage?

this is a all in one environment, Newton release version
I did change debug options from True to none (default to False) in the node
and tried command 'pkill -HUP nova'

compute logs shows it's still in DEBUG mode (and only service restart will
make the debug logs disappear)

2017-01-05 05:16:46.174 62225 INFO oslo_service.service
[req-de8349f2-ceb7-4eef-94ce-7cb09fd289bf - - - - -] Caught SIGHUP, exiting
2017-01-05 05:16:46.175 62225 DEBUG oslo_concurrency.lockutils
[req-de8349f2-ceb7-4eef-94ce-7cb09fd289bf - - - - -] Acquired semaphore
"singleton_lock"
lock /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:212
2017-01-05 05:16:46.175 62225 DEBUG oslo_concurrency.lockutils
[req-de8349f2-ceb7-4eef-94ce-7cb09fd289bf - - - - -] Releasing semaphore
"singleton_lock"
lock /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:225
2017-01-05 05:16:51.287 62225 DEBUG oslo_messaging._drivers.amqpdriver [-]
CALL msg_id: a86b7b1cb66745e485e5ab75a1eb2a83 exchange 'nova' topic
'conductor'
_send /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:448
2017-01-05 05:16:51.295 62225 INFO nova.compute.manager
[req-de8349f2-ceb7-4eef-94ce-7cb09fd289bf - - - - -] Reloading compute RPC
API

api log shows it honored the flag and follow on there is no debug log based
on the 'Option DEFAULT.debug changed from [true] to [None]'

2017-01-05 05:16:46.130 62146 INFO oslo_service.service
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Child caught SIGHUP,
exiting
2017-01-05 05:16:46.130 62146 DEBUG oslo_concurrency.lockutils
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Acquired semaphore
"singleton_lock"
lock /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:212
2017-01-05 05:16:46.130 62146 DEBUG oslo_concurrency.lockutils
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Releasing semaphore
"singleton_lock"
lock /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:225
2017-01-05 05:16:46.151 62145 INFO oslo_config.cfg
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Option DEFAULT.debug
changed from [true] to [None]
2017-01-05 05:16:46.151 62145 INFO nova.wsgi
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Stopping WSGI server.
2017-01-05 05:16:46.151 62145 INFO nova.osapi_compute.wsgi.server
[req-3d3dfc79-4c42-460e-8311-7eab381adff3 - - - - -] (62145) wsgi exited,
is_accepting=True
2017-01-05 05:16:46.152 62145 INFO nova.wsgi
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] WSGI server has
stopped.
2017-01-05 05:16:46.154 62146 INFO oslo_config.cfg
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Option DEFAULT.debug
changed from [true] to [None]
2017-01-05 05:16:46.155 62146 INFO nova.wsgi
[req-1dc88c01-f1a2-4553-b13d-0a06f8242879 - - - - -] Stopping WSGI server.



2017-01-05 05:16:46.164 62146 INFO nova.osapi_compute.wsgi.server
[req-c0aaa8de-b181-4fb0-a3e1-0e4ed201457b - - - - -] (62146) wsgi starting
up on https://0.0.0.0:8774
Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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

Re: [openstack-dev] [nova][api] quota-class-show not sync toquota-show

[Chen CH Ji]

ok, thanks for the info,  I will submit the spec and wait for more response
from the spec

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Lance Bragstad <lbrags...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date:   04/12/2017 03:09 AM
Subject:Re: [openstack-dev] [nova][api] quota-class-show not sync to
quota-show





On Tue, Apr 11, 2017 at 1:21 PM, Matt Riedemann <mriede...@gmail.com>
wrote:
  On 4/11/2017 2:52 AM, Alex Xu wrote:
   We talked about remove the quota-class API for multiple times
   (
   http://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html
   )

   I guess we can deprecate the entire quota-class API directly.


  I had a spec proposed to deprecate the os-quota-class-sets API [1] but it
  was abandoned since we discussed it at the Pike PTG and decided we would
  just leave it alone until Nova was getting limits information from
  Keystone [2].

FWIW - in addition to merging the conceptual document [0], Sean recently
proposed the limits interface [1] for the keystone bits.

[0]
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-limits.htm
[1] https://review.openstack.org/#/c/455709/


  I think the reason we probably missed this API was because of the really
  roundabout way that the information is provided in the response. It calls
  the quota engine driver [3] to get the class quotas. For the DB driver if
  nothing is overridden then nothing comes back here [4]. And the resources
  in the quota driver have a default property which is based on the config
  options [5]. So we'll return quotas on floating_ips and other proxy
  resources simply because of how abstract this all is.

  To fix it, the os-quota-class-sets API would have to maintain a blacklist
  of resources to exclude from the response, like what we do for limits
  [6].

  So yeah, I guess we'd need a new spec and microversion for this.

  [1] https://review.openstack.org/#/c/411035/
  [2] https://review.openstack.org/#/c/440815/
  [3]
  
https://github.com/openstack/nova/blob/15.0.0/nova/api/openstack/compute/quota_classes.py#L67

  [4] https://github.com/openstack/nova/blob/15.0.0/nova/quota.py#L92
  [5] https://github.com/openstack/nova/blob/15.0.0/nova/quota.py#L1069
  [6]
  
https://github.com/openstack/nova/blob/15.0.0/nova/api/openstack/compute/views/limits.py#L20


  --

  Thanks,

  Matt


  __

  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 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 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] [nova][api] quota-class-show not sync to quota-show

[Chen CH Ji]

Version 2.35 removed most deprecated output like floating ip etc so we
won't have following in quota-show output
| floating_ips| 10|
| fixed_ips   | -1|
| security_groups | 10|
| security_group_rules| 20|

however, quota-class-show still have those output, should we use 2.35 to
fix this bug or add a new microversion or because os-quota-class-sets is
about to deprecate, we can let it be ? Thanks

DEBUG (session:347) REQ: curl -g -i -X GET
http://192.168.123.10:8774/v2.1/os-quota-class-sets/1 -H
"OpenStack-API-Version: compute 2.41" -H "User-Agent: python-novaclient" -H
"Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.41" -H
"X-Auth-Token: {SHA1}5008bb2787a9548d65b063f4db2525b4e3bf7163"

RESP BODY: {"quota_class_set": {"injected_file_content_bytes": 10240,
"metadata_items": 128, "ram": 51200, "floating_ips": 10, "key_pairs": 100,
"id": "1", "instances": 10, "security_group_rules": 20, "injected_files":
5, "cores": 20, "fixed_ips": -1, "injected_file_path_bytes": 255,
"security_groups": 10}}

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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] [nova] About use oslo_service in nova and fix for OSSN-0039

[Chen CH Ji]

Hi
 In https://wiki.openstack.org/wiki/OSSN/OSSN-0039, it's
requested that SSL/TLS library (OpenSSL in this case) is compiled without
SSLv3 ,
 our internal discussion from some security experts suggested
we need add some code to
https://github.com/openstack/nova/blob/master/nova/wsgi.py#L168
 maybe something like:   dup_socket = eventlet.wrap_ssl
(dup_socket, ssl_version=ssl.PROTOCOL_TLSv1_2,
 so that nova client only requests TLSv1_2

 so the question is
1) why nova didn't use oslo service, so we can honor some options like
following while seems nova don't have?
https://github.com/openstack/oslo.service/blob/master/oslo_service/_options.py#L108
https://github.com/openstack/oslo.service/blob/master/oslo_service/_options.py#L114

2) is there a existing requirement to nova (and maybe other projects) on
OSSN 0039 in addition to recompile ssl library?


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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

Re: [openstack-dev] [nova][deployment] FYI: changes to cells v2 setup guide (pike only)

[Chen CH Ji]

Thanks for sharing, our zvm CI had exactly same issue those days , we need
'nova hypervisor-list' to be 'up' in order to do further conf/test
so ,even if nova service-list returns 'up' info but actually the host
mapping is not built and in turn you still can't schedule workload to it
so we build a loop and because the discovery hosts action are idempotent,
we build a loop and keep discover host until
the compute node is created and then in turn create the hostmap

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann <mriede...@gmail.com>
To: openstack-dev@lists.openstack.org
Date:   04/17/2017 11:46 PM
Subject:Re: [openstack-dev] [nova][deployment] FYI: changes to cells v2
setup guide (pike only)



On 4/16/2017 10:35 PM, Alex Xu wrote:
> Is it strange that the 'nova service-list' and 'nova host-list' return
> the hosts which didn't have host mapping yet?

It's kind of strange yes. We could probably make GET /os-hypervisors
work without requiring the host mappings, but it just doesn't today
because of some targeted calls within each cell to fill the response.

So we could probably decouple things a bit internally in the API if we
wanted to do this differently and not require a host mapping, but for
now I knew we could get the same results by just using os-services and
get Kolla unblocked (this came up Friday morning last week so I was
rushing for a solution).

>
> How the user to know whether a host was added to a cell or not?

A user doesn't need to know, but an operator would care. This actually
came up in IRC last week [1] when Kevin Fox was asking similar
questions, and I have a TODO to write some FAQs for cells v2.

We talked about how the "nova-manage cell_v2 discover_hosts" command is
idempotent and if there are new unmapped hosts you could just run it and
pick them up - the trick is knowing when to run it, unless you configure
the scheduler to use "discover_hosts_in_cells_interval" for auto-discovery.

We also talked about the option of building on the "nova-manage cell_v2
list_cells" command to also optionally dumping hosts per cell, or just
run the "nova-manage host list" command pointed at your cell config.

At some point we might want to consider returning cell uuid out of the
os-services API when listing services or hosts, something like that.

[1]
http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-04-10.log.html#t2017-04-10T20:25:47


--

Thanks,

Matt

__
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 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] [nova] about usage of /consoles

[Chen CH Ji]

Per https://bugs.launchpad.net/nova/+bug/1682303 , POST with return 200
while GET returns [] is weird
 what's the purpose of /consoles? looks like
https://github.com/openstack/nova/blob/master/nova/console/rpcapi.py#L72
will send a rpc message and which service is the reciever of this message
and handle it? Thanks

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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] [nova][keystone] keystoneauth1 and keystonemiddle setting

[Chen CH Ji]

In fixing bug 1704798, there's a proposed patch
https://review.openstack.org/#/c/485121/7
but we stuck at http_connection_timeout and timeout value in keystoneauth1
and keystonemiddle repo

basically we want to reuse the keystone_auth section in nova.conf to avoid
create another section so we can
use following to create a session

sess = ks_loading.load_session_from_conf_options(CONF,
'keystone_authtoken', auth=context.get_auth_plugin())

any comments or we have to create another section and configure it anyway?
thanks


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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

Re: [openstack-dev] [nova][keystone] keystoneauth1 and keystonemiddle setting

[Chen CH Ji]

ok, thanks for Morgan and Brant's comments, will rework the patch based on
the comments, thanks!

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Morgan Fainberg <morgan.fainb...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date:   08/17/2017 07:51 AM
Subject:Re: [openstack-dev] [nova][keystone] keystoneauth1 and
keystonemiddle setting





On Aug 16, 2017 11:31, "Brant Knudson" <b...@acm.org> wrote:


  On Mon, Aug 14, 2017 at 2:48 AM, Chen CH Ji <jiche...@cn.ibm.com> wrote:
   In fixing bug 1704798, there's a proposed patch
   https://review.openstack.org/#/c/485121/7
   but we stuck at http_connection_timeout and timeout value in
   keystoneauth1 and keystonemiddle repo

   basically we want to reuse the keystone_auth section in nova.conf to
   avoid create another section so we can
   use following to create a session

   sess = ks_loading.load_session_from_conf_options(CONF,
   'keystone_authtoken', auth=context.get_auth_plugin())

   any comments or we have to create another section and configure it
   anyway? thanks


   Best Regards!

   Kevin (Chen) Ji 纪 晨

   Engineer, zVM Development, CSTL
   Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
   Phone: +86-10-82451493
   Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
   District, Beijing 100193, PRC

   __

   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


  I think reusing the keystone_authtoken config is a bad idea.
  keystone_authtoken contains the configuration for the auth_token
  middleware so this is what we keystone developers expect it to be used
  for. A deployment may have different security needs for the auth_token
  middleware vs checking quotas in which case they'll need different users
  or project for the auth_token middleware and quota checking. And even if
  we don't need it now we might need it in the future, and it's going to
  create a lot of work going forward to rearchitect.

  If a deployer wants to use the same authentication for both auth_token
  middleware and the proxy, they can create a new section with the config
  and point both keystone_authtoken and quota checking to it (by setting
  the auth_section).

  --
  - Brant

  __

  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



What Brant said. Please do not lean on the options from keystone middleware
for anything outside of keystone middleware. We have had to change these
options before and those changes should only ever impact the keystone
middleware code. If you re-use those options for something in Nova, it will
likely break and need to be split into it's own option block in the future.

Please create a new option block (even if a deployers uses the same
user/passord) rather than using the authtoken config section for anything
outside of authtoken.

--Morgan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=tObIBKyCbf77oLwdSwaHb3_FM8au2aTVSaHGYMH8-1Q=vRncIuk0n5yybdLrZA8uRBC3A0UZDhzj5-pX5alqUc0=



__
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

Re: [openstack-dev] [nova] about usage of /consoles

[Chen CH Ji]

Thanks for the info, looks like this is xen only stuff,  not sure whether
this is needed for now or we can remove it
remote_consoles seems related to some general console but not specific to
xvp,

so https://review.openstack.org/459266 just for some info to api reader and
if we are sure xen don't use it any more, we can remove it totally.

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Markus Zoeller <mzoel...@linux.vnet.ibm.com>
To: openstack-dev@lists.openstack.org
Date:   04/21/2017 08:35 PM
Subject:Re: [openstack-dev] [nova] about usage of /consoles



On 21.04.2017 12:12, Chen CH Ji wrote:
>
> Per https://bugs.launchpad.net/nova/+bug/1682303 , POST with return 200
> while GET returns [] is weird
>  what's the purpose of /consoles? looks like
> https://github.com/openstack/nova/blob/master/nova/console/rpcapi.py#L72
> will send a rpc message and which service is the reciever of this message
> and handle it? Thanks
>
> Best Regards!
>
> Kevin (Chen) Ji 纪 晨

Looks like this API works for the "Xen VNC proxy" service only. The
console manager triggers the console creation here:
https://github.com/openstack/nova/blob/66c661258873e2544e286099c4bc027c26c851c4/nova/console/manager.py#L79


The XVPConsoleProxy implements it here:
https://github.com/openstack/nova/blob/46b3a3ca1ac3a5ffdc7c5420263223f2d3b9a660/nova/console/xvp.py#L56-L58


Looks like that service runs with default Devstack settings as service
"nova-xvpvncproxy":
https://github.com/openstack-dev/devstack/blob/f3b2f4c85307b14f115a020f5eaf6c92026b55b4/lib/nova#L892-L892


The API microversion 2.6 introduced a consolidation of the remote consoles:
https://github.com/openstack/nova/blob/3e032fd45be28c6098235ce336e675d03ebc6619/nova/api/openstack/compute/schemas/remote_consoles.py#L101-L102


Could it be that the "GET /console" API shouldn't be available anymore
since microversion 2.6?

api-ref about the consoles:
https://developer.openstack.org/api-ref/compute/?expanded=get-vnc-console-os-getvncconsole-action-deprecated-detail,create-remote-console-detail


--
Regards, Markus Zoeller (markus_z)


__
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 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

Re: [openstack-dev] [nova][out-of-tree drivers] InstanceInfo/get_info getting a haircut

[Chen CH Ji]

Thanks for posting this, we do have an out-of-tree driver ,and as you
pointed out in the patch , those parameters seems not used
and this change didn't modify the compute layer functions and params so it
should be no impact

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Eric Fried <openst...@fried.cc>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date:   06/07/2017 12:35 AM
Subject:[openstack-dev] [nova][out-of-tree drivers]
InstanceInfo/get_info   getting a haircut



If you don't maintain an out-of-tree nova compute driver, you can
probably hit Delete now.

A proposed change [1] gets rid of some unused fields from
nova.virt.hardware.InstanceInfo, which is the thing returned by
ComputeDriver.get_info().

I say "unused" in the context of the nova project.  If you have a
derived project that's affected by this, feel free to respond or reach
out to me (efried) on #openstack-nova to discuss.

This change is planned for Pike only.

[1] https://review.openstack.org/#/c/471146/

Thanks,
Eric
.

__
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 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] [nova] About live-resize spec

[Chen CH Ji]

spec [1] has been there since 2014 and some patches proposed but abandoned
after that, can someone
please provide some info/background about why it's postponed or due to some
limitations that nova hasn't been implemented yet?

some operators suggested that this is a valuable funcationality so better
to have it in the near feature... thanks


[1]:https://blueprints.launchpad.net/nova/+spec/instance-live-resize

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

[Chen CH Ji]

in analyzing other code, found seems we don't need PUT
/servers/{server_id}/metadata/{key} ?

as the id is only used for check whether it's in the body and we will honor
the whole body (body['meta'] in the code)
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/server_metadata.py#L80

looks like it's identical to
PUT /servers/{server_id}/metadata

why we need this API or it should be something like

PUT /servers/{server_id}/metadata/{key} but we only accept a value to
modify the meta given by {key} in the API side?

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
__
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

Re: [openstack-dev] [nova] About live-resize spec

[Chen CH Ji]

ok, thanks, I will pick up and get Claudiu's help as well, the original
spec is abandoned ,could you please help to restore it?

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann <mriede...@gmail.com>
To: openstack-dev@lists.openstack.org
Date:   09/20/2017 09:11 PM
Subject:Re: [openstack-dev] [nova] About live-resize spec



On 9/20/2017 12:16 AM, Chen CH Ji wrote:
> spec [1] has been there since 2014 and some patches proposed but
> abandoned after that, can someone
> please provide some info/background about why it's postponed or due to
> some limitations that nova hasn't been implemented yet?
>
> some operators suggested that this is a valuable funcationality so
> better to have it in the near feature... thanks
>
>
> [1]:
https://urldefense.proofpoint.com/v2/url?u=https-3A__blueprints.launchpad.net_nova_-2Bspec_instance-2Dlive-2Dresize=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=8URBCAs-AokrPQobkaJ801kitvJThbGRR-TJ4o-LcIE=_CAt9-g8ZEY5LXXo10rhhd-GMWz4B1YBQ28dhuFZnj0=

>
> Best Regards!
>
> Kevin (Chen) Ji 纪 晨
>
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
> Phone: +86-10-82451493
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
> District, Beijing 100193, PRC
>
>
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=8URBCAs-AokrPQobkaJ801kitvJThbGRR-TJ4o-LcIE=anotHeOxKU8HE2ff2CnYn4rwT48cG1wkINchYamlckw=

>

We talked about this during the newton midcycle and from what I remember
we wanted to make this depend on having the ability for users to know
what they are capable of doing with their server instance in any given
cloud. This has grown into the cross project capabilities API
discussions that happen with the API work group.

At this point, I don't think we have anyone working on doing anything
for a capabilities API in nova, nor do we have cross project agreement
on a perfect solution that will work for all projects. At the PTG in
Denver I think we just said we care less about having a perfect
guideline for all projects to have a consistent API, and more about
actually documenting the APIs that each project does have, which we do a
pretty good job of in Nova.

So I think live resize would be fine to pick up again if you're just
resizing CPU/RAM from the flavor and if we provide a policy rule to
disable it in clouds that don't want to expose that feature.

Cloudbase was originally driving it for Hyper-v so you might want to
talk with Claudiu Belu.

--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=8URBCAs-AokrPQobkaJ801kitvJThbGRR-TJ4o-LcIE=anotHeOxKU8HE2ff2CnYn4rwT48cG1wkINchYamlckw=




__
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

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

[Chen CH Ji]

yes, I didn't go to that detail and missed the delete flag , that's exactly
what I am looking for, which is a little bit confusing...
Thanks for the info for know this...

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Matt Riedemann <mriede...@gmail.com>
To: openstack-dev@lists.openstack.org
Date:   09/20/2017 09:15 PM
Subject:Re: [openstack-dev] [nova][api] why need
PUT /servers/{server_id}/metadata/{key} ?



On 9/20/2017 12:48 AM, Chen CH Ji wrote:
> in analyzing other code, found seems we don't need PUT
> /servers/{server_id}/metadata/{key} ?
>
> as the id is only used for check whether it's in the body and we will
> honor the whole body (body['meta'] in the code)
>
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_nova_blob_master_nova_api_openstack_compute_server-5Fmetadata.py-23L80=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=DSFbFb2bqll3hC8yrttkW6teiZtFod4XBQIC8jauVlE=1S1y1O0K2KOZgQd1wmx5_P8IhzNqf-i6d4IThx0yLrI=

>
> looks like it's identical to
> PUT /servers/{server_id}/metadata
>
> why we need this API or it should be something like
>
> PUT /servers/{server_id}/metadata/{key}but we only accept a value to
> modify the meta given by {key} in the API side?
>
> Best Regards!
>
> Kevin (Chen) Ji 纪 晨
>
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
> Phone: +86-10-82451493
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
> District, Beijing 100193, PRC
>
>
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=DSFbFb2bqll3hC8yrttkW6teiZtFod4XBQIC8jauVlE=EMTJozBhxl7wXNyB7emtzxXMkegVXKWV6Ko8E2uhsPs=

>

This API is a bit confusing, and the code is too since it all goes down
to some common code, and I think you're missing the 'delete' flag:

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_nova_blob_5bf1bb47c7e17c26592a699d07c2faa59d98bfb8_nova_compute_api.py-23L3830=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=DSFbFb2bqll3hC8yrttkW6teiZtFod4XBQIC8jauVlE=AMY4S8Ux0G78V_Nu2H17kNivICkiKErqDzPj0eFsUgg=


If delete=False, as it is in this case, we only add/update the existing
metadata with the new metadata from the request body. If delete=True,
then we overwrite the instance metadata with whatever is in the request.

Does that answer your question?

This API is problematic and we have bugs against it since it's not
atomic, i.e. two concurrent requests will overwrite one of them. We
should really have a generation ID or etag on this data to be sure it's
atomically updated.

--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=DSFbFb2bqll3hC8yrttkW6teiZtFod4XBQIC8jauVlE=EMTJozBhxl7wXNyB7emtzxXMkegVXKWV6Ko8E2uhsPs=




__
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