[openstack-dev] [nova] Reconfiguring devices when boot from instance snapshot

2014-02-05 Thread Feodor Tersin
There is a task - device reconfiguration when boot instance from instance snapshot. For example, one may want to change shutdown behaviour by nova boot ... --image instance_snapshot --block_device device=/dev/vda,shutdown=false when originally shutdown attribute for /dev/vda is 'remove' in the

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

2015-02-02 Thread Feodor Tersin
Hi Ken, 1 imageRef isn't the only attribute, which could receive an image id. There are kernelId, ramdiskId, and even bdm v2 as well. So we couldn't guess which attribute has the invalid value. 2 Besides NotFound case, other mixed cases are there. Such as attaching of a volume. A mountpoint can

Re: [openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.

2015-02-10 Thread Feodor Tersin
now, and can be used by someone. Do you really want to break it? On Tue, Feb 10, 2015 at 10:29 AM, Oleg Bondarev obonda...@mirantis.com wrote: On Mon, Feb 9, 2015 at 8:50 PM, Feodor Tersin fter...@cloudscaling.com wrote: nova boot ... --nic port-id=xxx --nic net-id=yyy this case is valid

Re: [openstack-dev] [nova][neutron] Create VM using port-create vs nova boot only?

2015-02-09 Thread Feodor Tersin
Hi When you create a port separately, you can specify additional fixed IPs, extra DHCP options. But with 'nova boot' you cannot. Also if you need an instance with several nics, and you want that each nic has its own set of security groups, you should create ports separately. Because 'nova boot

Re: [openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.

2015-02-09 Thread Feodor Tersin
nova boot ... --nic port-id=xxx --nic net-id=yyy this case is valid, right? I.e. i want to boot instance with two ports. The first port is specified, but the second one is created at network mapping stage. If i specify a security group as well, it will be used for the second port (if not - default

Re: [openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.

2015-02-11 Thread Feodor Tersin
at 5:26 PM, Feodor Tersin fter...@cloudscaling.com wrote: I definitely don't expect any change of the existing port in the case with two nics. However in the case of single nic a question like 'what is impact of security-groups parameter' arises. Also a similar question arises out of '--nic port

Re: [openstack-dev] [nova] what's the merge plan for current proposed microversions?

2015-03-05 Thread Feodor Tersin
Since the first microversion is merged ( https://review.openstack.org/#/c/140313/), please, pay attention to a novaclient upgrade to work with microversions ( https://review.openstack.org/#/c/152569/) On Mon, Mar 2, 2015 at 2:30 PM, Sean Dague s...@dague.net wrote: This change for the

Re: [openstack-dev] [nova] novaclient 'stable-compat-jobs-{name}' broken

2015-04-14 Thread Feodor Tersin
I proposed a solution (https://review.openstack.org/#/c/172522/) But i have no idea how to push it. btw. As i see, glanceclient developers decided to just remove these jobs ( https://review.openstack.org/#/c/172999/) On Tue, Apr 14, 2015 at 11:47 AM, Andrey Kurilin akuri...@mirantis.com wrote:

[openstack-dev] [nova] ImageRef vs bdm v2 in REST API

2015-05-11 Thread Feodor Tersin
Hi. Since that bdm v2 was introduced for Havana, it requires a caller to specify bdm for an image together with imageRef to boot an instance in a case of using bdm v2 to attach additional volumes. {server: {imageRef: xxx, block_device_mapping_v2: [

Re: [openstack-dev] [Nova] The security group is confused in the create server api

2015-05-14 Thread Feodor Tersin
On Wed, May 13, 2015 at 4:54 PM, Lei Zhang zhang.lei@gmail.com wrote: Thank for your reply. I read that thread, but it just throw a exception when using confused params. To solve this issue, is it worth to create a now micro version of api to implement above cli? As i see at the last

Re: [openstack-dev] [Nova] The security group is confused in the create server api

2015-05-13 Thread Feodor Tersin
nova boot test --flavor m1.tiny --security_group ssh --security_group http --nic net-id=xxx --nic port-id=yyy Which port/nic the security group should bind to? the first one? both? Both groups will be set to a new port of xxx network. A set of port yyy SG will not be

Re: [openstack-dev] [infra][glanceclient][cinderclient] Problems with juno check jobs

2015-04-13 Thread Feodor Tersin
I proposed https://review.openstack.org/#/c/172522/ to fix this for all projects whose versions are restricted by global requirements. On Mon, Apr 13, 2015 at 5:55 PM, stuart.mcla...@hp.com wrote: Hi Gorka, Glance is seeing something very similar [3]. I've updated the two bugs ([1],[3])

Re: [openstack-dev] [nova][ec2-api] Need advice about running Tempest against stackforge/ec2-api

2015-04-07 Thread Feodor Tersin
Hi Sean On Mon, Apr 6, 2015 at 7:34 PM, Sean Dague s...@dague.net wrote: On 04/06/2015 12:13 PM, Andrey M. Pavlov wrote: Hi, We've got a couple of problems running original Tempest EC2 API test against new standalone stackforge/ec2-api project and I wanted to ask for some advice about

Re: [openstack-dev] [nova][ec2-api] Need advice about running Tempest against stackforge/ec2-api

2015-04-09 Thread Feodor Tersin
Hi. As you can see adjusted Tempest (https://review.openstack.org/#/c/171222/) runs well against both Nova EC2 and ec2api ( https://review.openstack.org/#/c/172059). On Tue, Apr 7, 2015 at 5:50 PM, Feodor Tersin fter...@cloudscaling.com wrote: Hi Sean On Mon, Apr 6, 2015 at 7:34 PM, Sean

Re: [openstack-dev] [nova] Availability of device names for operations with volumes and BDM and other features.

2015-05-28 Thread Feodor Tersin
Nicola, i would add some words to Alexandre repsonse. We (standalone ec2api project guys) have filed some bugs (the main is [1]), but we don't know how to fix them since the way Nova's device names are moved on is unclear for us. Neither BP, nor wiki you've mentioned above don't explain what was

Re: [openstack-dev] [nova] correct API for getting image metadata for an instance ?

2015-05-28 Thread Feodor Tersin
+1 But we should answer the following question before switching libvirt to utils.get_image_from_system_metadata. Some differences of utils.get_image_from_system_metadata from compute.utils.get_image_metadata are: 1) Instance metadata has a restriction of property length: long data is stripped to

Re: [openstack-dev] [nova] correct API for getting image metadata for an instance ?

2015-05-28 Thread Feodor Tersin
of utils.get_image_from_system_metadata by the image metadata and returns full AAA and added BBB. This is the difference i mean. On Thu, May 28, 2015 at 11:59 AM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, May 28, 2015 at 11:55:59AM +0300, Feodor Tersin wrote: +1 But we should answer the following

Re: [openstack-dev] [nova] correct API for getting image metadata for an instance ?

2015-05-28 Thread Feodor Tersin
P. Berrange berra...@redhat.com wrote: On Thu, May 28, 2015 at 12:22:59PM +0300, Feodor Tersin wrote: I mean the case: - an image has long property AAA and non inheritable property BBB; - an instance based on the image stores truncated AAA and full BBB

Re: [openstack-dev] [nova] contextlib.nested and Python3 failing

2015-08-23 Thread Feodor Tersin
From: kevin.mitch...@rackspace.com Actually, there should no longer be a need to use contextlib.nested. We've explicitly dropped Python 2.6 compatibility, which means we're expecting compatibility with Python 2.7+ only, and as of Python 2.7, the 'with' statement supports accepting multiple

[openstack-dev] [Nova] Let's set instance.root_gb=0 for volume-backed instances

2015-06-26 Thread Feodor Tersin
There are several problems in algorithms which calculate size of host local disk space consumed by a volume-backed instance [1]. Obviously the volume-backed instance does not use the host local disk for the root volume. But these algorithms use root_gb, min_size, size

Re: [openstack-dev] [nova][cinder][glance] Should we allow this kind of action?

2015-07-27 Thread Feodor Tersin
+1 to the wonder We could have more explicit check in Cinder.Either check disk_format (it's None for volume-backed images)or add to Glance a new container_format type for this kind of images (it's also None currently) and check it. From: sxmatch1...@gmail.com Date: Mon, 27 Jul 2015 10:49:39

Re: [openstack-dev] [Nova] Device names supplied to the boot request

2015-07-16 Thread Feodor Tersin
Date: Thu, 16 Jul 2015 20:10:45 +0100 From: ndipa...@redhat.com To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Device names supplied to the boot request On 07/16/2015 06:35 PM, Matt Riedemann wrote: On 7/16/2015 11:47 AM, Nikola ─Éipanov wrote: On

Re: [openstack-dev] [nova] Fine-grained error reporting via the external API

2015-09-11 Thread Feodor Tersin
> From: mbo...@redhat.com > To: openstack-dev@lists.openstack.org > Date: Fri, 11 Sep 2015 10:41:47 +0100 > Subject: [openstack-dev] [nova] Fine-grained error reporting via the > external API > > However, all I have is that I made a BadRequest. I could potentially > grep the human readable

Re: [openstack-dev] [nova] About availability zones

2015-09-23 Thread Feodor Tersin
Hi. Currently, when performing live-migration the AZ of the instance didn't update. In usecase like this:Instance_1 is in host1 which is in az1, we live-migrate it to host2 (provide host2 in API request) which is in az2. The operation will secusess but the availability zone data stored in

Re: [openstack-dev] [nova] Fix evaluation of host disk usage by volume-backed instances

2016-08-12 Thread Feodor Tersin
attribute of a new flavor. And i did not found an easy way how to provide there the fact that root_gb need to be ignored. I hope these info was useful for you. Thanks, Feodor Tersin From: Kekane, Abhishek <abhishek.kek...@nttdata.com> Sent: Friday, August 12

Re: [openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

2017-02-08 Thread Feodor Tersin
HI Zhenyu You're referring to API doc, but you're checking it with nova cli, which does not do exactly that what you want. In the case when you specify image and block-device parameters, nova cli sends image_ref and two (!) bdms. Both these bdms have the same boot_index and conflict with each

Re: [openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

2017-02-08 Thread Feodor Tersin
Zhenyu, btw iianm if you specify image only (w/o bdm) in the command line, nova cli sends exactly that combination which you're interesting for: image_ref and bdmv2. From: Feodor Tersin <fter...@hotmail.com> Sent: Wednesday, February 8, 2017 2:11

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

2017-04-04 Thread Feodor Tersin
> I raised the question though, could we move forward with removing the > device field from the "POST /servers/{server_id}/os-volume_attachments" > API since that doesn't do anything with image BDM overrides. Will this affect detaching/attaching of root volume

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

2017-04-02 Thread Feodor Tersin
to provide instead for this purpose? [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html#Using_OverridingAMIBDM Thanks, Feodor Tersin. From: Matt Riedemann <mriede...@gmail.com> Sent: Sunday, April 2, 2017 6:59:12 PM To

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

2017-04-02 Thread Feodor Tersin
stance method. This brings another questions, but does not directly affect bdms at least. Thanks, Feodor Tersin. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.opens