I have started an implementation in review:
https://review.openstack.org/#/c/69148/
- Original Message -
From: "sahid"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Saturday, January 25, 2014 5:56:10 PM
Subject: Re: [openstack-dev] [nova] hugepage suppor
Hi all.
If I use the following command to create an image:
curl -i -H "X-Auth-Token:268c536db05b435bb6e631158744e3f6" -H
"x-image-meta-property-IMAGE-TYPE:xxx" -H "x-image-meta-name:test" -X POST
http://127.0.0.1:9292/v1/images
I will get the following results:
{"image": {"status": "queued", "del
Hi,
I have started the implementation, Please review. Address:
https://review.openstack.org/#/c/67067/
Thanks.
Regards,
Lee
2014/1/9 Christopher Yeoh :
> On Thu, Jan 9, 2014 at 5:00 PM, 黎林果 wrote:
>>
>> Oh, I see. Thank you very much.
>> It's just hard coded for attaching volume and swapping v
Hi All,
While trying to work on a bug I was trying to simulate some image
download failures and found that apparently the 'killed' state is never
set using v2 APIs.
If I understand correctly, a file upload goes to
api.v2.image_data.ImageDataController.upload and goes all the way to
store.ImagePro
Hi Stacker,
I would like to add the cli option of neutronclient for specifying service
type.
I have committed the patch including the feature:
https://review.openstack.org/54534
The option can specified via service type or env['OS_NETWORK_SERVICE_TYPE']:
$ export OS_NETWORK_SERVICE_TYPE=network
Hi Wang Hong,
Good catch. I think the issue is caused by line 244-246, see
https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244
For the case-matter issue, I think it's a bug. But as for the - to _, I
would like to listen Jay's opinion since who is the original author. And
ob
Hi David,
I think you're right. The 'killed' status should be set in method upload()
if there is an upload failure, see
https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244
Thanks & Best regards,
Fei Long Wang (王飞龙)
--
Hi Stackers:
Some instance operations and flavor are closely connected, for example,
resize.
If I delete the flavor when resize instance, instance will be error. Like
this:
1. run instance with flavor A
2. resize instance from flavor A to flavor B
3. delete flavor A
4. resize-revert instance
5. i
Hi Fei,
Thanks for the confirmation.
> I think you're right. The 'killed' status should be set in method upload()
> if there is an upload failure, see
> https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244
I think you meant:
https://github.com/openstack/glance/b
Maybe it's up to administrator to decide wether you could delete a flavor,
I prefer regular users have no privileges to do that. Would like to see
others' opinions.
2014-01-26 Rui Chen
> Hi Stackers:
>
> Some instance operations and flavor are closely connected, for example,
> resize.
> If I de
Hi David,
Just had a short talk with markwash. Based on the new design of v2, we
don't need 'killed' status anymore. Since when user is uploading a
modification to an image and the upload fails, it should just go back to
what it was, it shouldn't be deactivated.
Thanks & Best regards,
Fei Long Wa
It does not seem very ReSTful--or very usable, for that matter--for a
resource to be permanently modified when you a PUT fails. So I don't think
we need the 'killed' status. It was purposefully left out of v2 images,
which is not just a reskin of v1.
Perhaps there is still a bug where an image is
On Sun, 2014-01-26 at 18:48 +0800, Fei Long Wang wrote:
> Hi Wang Hong,
>
> Good catch. I think the issue is caused by line 244-246, see
> https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244
> For the case-matter issue, I think it's a bug. But as for the - to _, I would
>
On Sun, 2014-01-26 at 06:36 -0800, Mark Washenberger wrote:
> It does not seem very ReSTful--or very usable, for that matter--for a
> resource to be permanently modified when you a PUT fails.
How so? What is not RESTful about changing the status of a resource
based on a PUT call?
> So I don't th
Hey Jay, thanks for calling my name correctly :)
Wang Hong, feel free to open a bug to track this. And we can get more
info/comments when the patch is reviewed. Thanks.
Thanks & Best regards,
Fei Long Wang (王飞龙)
-
Tech Lead of N
One quick question, do you think there is a potential backward-capability
breaking issue for end user or ISV if we remove existing
standardizing/normalizing logic? I'd like to know the gains/advantages on this
"fix".
thanks,
zhiyan
Sent from my iPad
> On 2014年1月26日, at 23:49, Fei Long Wang w
On Sat, Jan 25, 2014 at 7:11 AM, Clint Byrum wrote:
>
> Excerpts from Robert Collins's message of 2014-01-25 02:47:42 -0800:
> > On 25 January 2014 19:42, Clint Byrum wrote:
> > > Excerpts from Robert Collins's message of 2014-01-24 18:48:41 -0800:
> >
> > >> > However, in looking at how Ironic w
Doesn't nova already have logic for creating N virtual machines (similar to a
group) in the same request? I thought it did (maybe it doesn't anymore in the
v3 API), creating N bare metal machines seems like it would comply to that api?
Sent from my really tiny device...
> On Jan 22, 2014, at 4:
Excerpts from Devananda van der Veen's message of 2014-01-26 10:27:36 -0800:
> On Sat, Jan 25, 2014 at 7:11 AM, Clint Byrum wrote:
> >
> > Excerpts from Robert Collins's message of 2014-01-25 02:47:42 -0800:
> > > On 25 January 2014 19:42, Clint Byrum wrote:
> > > > Excerpts from Robert Collins's
On 27 January 2014 08:04, Joshua Harlow wrote:
> Doesn't nova already have logic for creating N virtual machines (similar to a
> group) in the same request? I thought it did (maybe it doesn't anymore in the
> v3 API), creating N bare metal machines seems like it would comply to that
> api?
It
So great news - we've now got state preserving upgrades actually
working - we can now upgrade a deployed cloud (with downtime) without
tossing away all the users valuable data. Yay. This isn't entirely
done as we have a couple of outstanding patches we're running early
versions of, but - still, it'
On Thu, Jan 23, 2014 at 4:02 PM, Russell Bryant wrote:
> Greetings,
>
> Last cycle we had A "feature proposal deadline" across some projects.
> This was the date that code associated with blueprints had to be posted
> for review to make the release. This was in advance of the official
> feature
I am working on SSL VPN BP.
CA certificate is one of the resources. We decided to use PEM formatted
certificates. It is multi-line string
1 -BEGIN CERTIFICATE-
2 MIID3TCCA0agAwIBAgIJAKRWnul3NJnrMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYD
21 0vO728pEcn6QtOpU7ZjEv8JLKRHwyq8kwd8gKMflWZRng4R2dj
On Sun, 2014-01-26 at 16:36 -0600, [email protected] wrote:
> I am working on SSL VPN BP.
>
> CA certificate is one of the resources. We decided to use PEM formatted
> certificates. It is multi-line string
>
> 1 -BEGIN CERTIFICATE-
> 2 MIID3TCCA0agAwIBAgIJAKRWnul3NJnrMA0GCSqGSI
> Perhaps there is still a bug where an image is getting stuck in 'saving' or
> some other state when a PUT fails?
Yes, that's precisely the problem.
Of course, one could argue that that if an upload fails the user
should be able to continue trying until the upload succeeds! But in that
FSM +1
https://blueprints.launchpad.net/glance/+spec/image-status-global-state-machine
btw, I remember I had posted this information in your change as a
review comment, which is a simple state validation mechanism in image
domain object and already been merged.
thanks,
zhiyan
On Mon, Jan 27, 2
Hi Paul:
Actually, in the scenario of NFV, all the rules or behaviors of the
physical world will apply to that in the virtual world, right?
IMHO, despite of the scenarios, we should at least guarantee the
consistency of creating vms with nics and attaching nics .
2014-01-24 CARVER, PAUL
> I
On Sun, Jan 26, 2014 at 4:37 PM, David Koo wrote:
>
> > Perhaps there is still a bug where an image is getting stuck in 'saving'
> or
> > some other state when a PUT fails?
>
> Yes, that's precisely the problem.
>
We should definitely fix that, thanks for pointing it out!
>
> Of course
> FSM +1
>
> https://blueprints.launchpad.net/glance/+spec/image-status-global-state-machine
>
> btw, I remember I had posted this information in your change as a
> review comment, which is a simple state validation mechanism in image
> domain object and already been merged.
Ah yes, I remem
Hello,
I've been trying to build a transformer, and while I've gotten it to
work as intended for the most part, I've run into a weird issue because
the metric I'm transforming has two inputs.
I created a gauge metric that is updated via notifications, and a
pollster. The data from both of th
> I might be confused now or confused when I did that review, because I
> thought it was reducing download concurrency rather than upload
> concurrency. Are you talking about https://review.openstack.org/#/c/46479/ ?
My bad ... yes it was downloads and not uploads. But I was referring
to conc
Hi Jeremy,
> -Original Message-
> From: Jeremy Stanley [mailto:[email protected]]
> Sent: Saturday, January 25, 2014 7:52 PM
> To: [email protected]
> Subject: Re: [openstack-dev] [Infra] Question about disk partition
>
> On 2014-01-23 13:55:21 -0800 (-0800), Andrew Woodw
+1
> On Jan 25, 2014, at 9:04 AM, "Roshan Agrawal"
> wrote:
>
> +1
>
> From: Rajesh Ramchandani [[email protected]]
> Sent: Friday, January 24, 2014 9:35 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: OpenSt
On Mon, Jan 20, 2014 at 1:29 PM, Mark Washenberger <
[email protected]> wrote:
>
>
>
> On Mon, Jan 20, 2014 at 7:44 AM, Georgy Okrokvertskhov <
> [email protected]> wrote:
>
>> Hi Mark,
>>
>> Happy Martin Luther King Jr. Day!
>>
>> Will Google hangout or skype meeting avail
Zhi Yan,
I think you're talking about backward-compatibility, right? I would say
it's possible, just like the v2 is not compatible with v1 against this. So
that's why I would like to see a bug is opened to track this and then we
get also some comments from the end user/product manager perspective
Thanks, guess this is entering the realm of scheduling & group scheduling and
how "just the right" level of information is needed to do efficient group
scheduling in nova/ironic vs the new/upcoming gantt service.
To me splitting it into N single requests isn't group scheduling but is just
more
@flwang, np at all. We can put the input in bug report as a comment or
here anyway,
as far as it can let us/me know the gains/advantages on this "fix".
I'd like to know whether there is a backward-compatibility issue, but seems
it's not a big deal? To keep the image property be case-sensitive is m
Zhi Yan, FWIW, your concern is reasonable. Thanks for raising it. Based on
the Glance v1 strategy, and backward-compatibility concern, maybe we should
mark it as won't fix?
Brian, may I get your opinion on this from a product manager perspective?
Thanks.
Thanks & Best regards,
Fei Long Wang (王飞龙)
I just verified this scenario. If image uploading is cancelled by Ctrl+C
in v2, the image will be stuck at "saving" status because of
DisconnectionError. Obviously, it doesn't make sense to leave the image in
saving status, though the image can be activated by re-uploading image
file. So if we're
On Mon, Jan 27, 2014 at 03:02:22PM +0800, Fei Long Wang wrote:
> I just verified this scenario. If image uploading is cancelled by Ctrl+C
> in v2, the image will be stuck at "saving" status because of
> DisconnectionError. Obviously, it doesn't make sense to leave the image in
> saving status, th
40 matches
Mail list logo
