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 b
> 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 mult
> 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 error
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 insta
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 whic
> 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
+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 +080
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
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 --s
ase with two nics make sense, works 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
wrote:
>
>
> On Mon, Feb 9, 2015 at 8:50 PM, Feodor Tersin
> wrote:
>
>> nova boot ... --nic port-id=xxx --nic net-id=yyy
>&
break anything :)
> I guess the only option then is to just log a warning that security groups
> are ignored in case port_id is provided on boot -
> but this still leaves a chance of broken user expectations.
>
>
>>
>>
>> On Tue, Feb 10, 2015 at 10:29 AM, Oleg Bonda
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 wrote:
> This change for the additional attributes
Hi Sean
On Mon, Apr 6, 2015 at 7:34 PM, Sean Dague 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 how
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
wrote:
> Hi Sean
>
>
> On Mon, Apr 6, 2015 at 7:34 PM, Sean Dague wr
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, wrote:
> Hi Gorka,
>
> Glance is seeing something very similar [3].
>
> I've updated the two bugs ([1],[3]) with some extra info
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
wrote:
> >Given that, is it
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": [
>
>
> 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 no
On Wed, May 13, 2015 at 4:54 PM, Lei Zhang 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 (May, 13) Matt'
+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 2
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
wrote:
> On Thu, May 28, 2015 at 11:55:59AM +0300, Feodor Tersin wrote:
> > +1
> > But we should answer the fol
P. Berrange
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;
> > - utils.get
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 h
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 --block_device
device=/dev/vda,shutdown=false
when originally shutdown attribute for /dev/vda is 'remove' in the instance
snapshot.
N
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
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
Sent: Wednesday, February 8, 2017 2:11:05 PM
To: OpenStack Develo
u going 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
Sent: Sunday, April 2, 2017 6:59:12 PM
To: Matt Riedemann;
'ignore_image_bdms' parameter to run
instance method. This brings another questions, but does not directly affect
bdms at least.
Thanks,
Feodor Tersin.
__
OpenStack Development Mailing List (not for usage qu
> 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
(https://review.openstack.org/#/c/3
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
Sent: Friday, August 12, 2016 4:29:11 PM
To: OpenStack
30 matches
Mail list logo
