Re: [openstack-dev] Booting a Vm Failed "VirtualMachineInterfaceFailed"

This mailing list is dedicated to openstack development. I would try your question on https://ask.openstack.org/or the general list mentioned here: https://wiki.openstack.org/wiki/Mailing_Lists#General_List Cheers, Kevin Benton On Wed, Jun 4, 2014 at 9:11 PM, Sachi Gupta wrote: > *Hi,* > >

Re: [openstack-dev] [Horizon] request to review bug 1301359

My patch actually does not relies on any not approved feature of a client. And I have not used any such features in my patch. Could you let me know which feature you are talking about which you think I have used, due to which patch would fail in integration testing? On Wed, Jun 4, 2014 at 6:14 PM

Re: [openstack-dev] question about createbackup API in nova

> -Original Message- > From: Andrew Laski [mailto:andrew.la...@rackspace.com] > Sent: Wednesday, June 04, 2014 10:15 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] question about createbackup API in nova > > > On 06/04/2014 02:56 AM, Bohai (ricky) wrote: > > Hi

Re: [openstack-dev] [ironic workflow question]

The deployment kernel/ramdisk is supposed to be built by ramdisk-image-create command. *ramdisk-image-create -a amd64 fedora deploy-ironic -o /tmp/deploy-ramdisk* The deployment kernel/ramdisk is used only for deployment and cannot give a full-fledged system. The deploy images are created by *"di

Re: [openstack-dev] [ironic workflow question]

Excerpts from 严超's message of 2014-06-04 20:34:01 -0700: > BTW, If I run "sudo ./bin/disk-image-create -a amd64 ubuntu deploy-ironic > -o /tmp/deploy-ramdisk-ubuntu", > What is the username/password for image deploy-ramdisk-ubuntu ? There isn't one. You can write an element if you want to include

Re: [openstack-dev] [neutron] Mid-cycle questions for folks

Yes, I was able to book it for $114 a night with no prepayment. I had to call. The agent found the block under Cisco and the date range. Carl On Wed, Jun 4, 2014 at 4:43 PM, Kyle Mestery wrote: > I think it's even cheaper than that. Try calling the hotel to get the > better rate, I think Carl

Re: [openstack-dev] Booting a Vm Failed "VirtualMachineInterfaceFailed"

Hi- Can you check whether all the neutron agents are running. Use this command $> neutron agent-list Check for all :) -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Sachi Gupta [mailto:sachi.gu...@tcs.com] Sent: Thursday, June 05, 2014 9:41 AM To: openstack-

[openstack-dev] Booting a Vm Failed "VirtualMachineInterfaceFailed"

Hi, While booting a virtual machine from Openstack dashboard, the call comes to Openstack compute where it is showing vif_binding details as vif_type = ovs Please suggest on how to change the vif_type to "vrouter" Thanks & Regards Sachi Gupta =-=-= Notice: The information c

Re: [openstack-dev] [ironic workflow question]

BTW, If I run "sudo ./bin/disk-image-create -a amd64 ubuntu deploy-ironic -o /tmp/deploy-ramdisk-ubuntu", What is the username/password for image deploy-ramdisk-ubuntu ? *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 * *My Weibo：http://

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

Wow great. I think the same applies to gre type driver. so we should create similar one after vxlan case is resolved. thanks, On Thu, Jun 05, 2014 at 12:36:54AM +0400, Eugene Nikanorov wrote: > We hijacked the vxlan initialization performance thread with ipam! :) > I've tried to address initia

Re: [openstack-dev] [Neutron][IPv6] Issues on dnsmasq

Shi Xiong, Thanks for asking! The error was found in dnsmasq log during our test. The error looks something like: "no addresses available". Jian Li from my team posted a comment about the PID error on your code review: https://review.openstack.org/#/c/70649/15/neutron/agent/linux/dhcp.py

Re: [openstack-dev] [ironic workflow question]

Thank you very much for your help and replies. It's much clearer and I've solved my problem. *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 * *My Weibo：http://weibo.com/herewearenow --* 2014-

Re: [openstack-dev] [ironic workflow question]

Thank you very much for your help and replies. It's much clearer and I've solved my problem. *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 * *My Weibo：http://weibo.com/herewearenow --* 2014-

[openstack-dev] [Neutron] dhcp port always in dead status

Hi list, I'm working under Havana. openstack-neutron.noarch 2013.2-1.el6@openstack-havana openstack-neutron-linuxbridge.noarch 2013.2-1.el6@openstack-havana openstack-neutron-openvswitch.noarch 2013.2-1.el6@openstack-ha

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

This patch packages 500 DB ‘add’ operations into 1. And in my own test, time costed reduces from 90s to 30s. boost! /Yalei From: Eugene Nikanorov [mailto:enikano...@mirantis.com] Sent: Thursday, June 05, 2014 4:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [o

[openstack-dev] [Glance] [TC] Program Mission Statement and the Catalog

Hi folks, I'd like to propose the Images program to adopt a mission statement [1] and then change it to reflect our new aspirations of acting as a Catalog that works with artifacts beyond just disk images [2]. Since the Glance mini summit early this year, momentum has been building significantly

Re: [openstack-dev] [nova][glance] Consistency around proposed server instance tagging API

On 06/04/2014 08:21 PM, Christopher Yeoh wrote: On Thu, Jun 5, 2014 at 4:14 AM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: Hi Stackers, I'm looking to get consensus on a proposed API for server instance tagging in Nova: https://review.openstack.org/#__/c/91444/

Re: [openstack-dev] [Heat]Heat template parameters encryption

On Jun 4, 2014, at 7:30 PM, Clint Byrum wrote: > Excerpts from Randall Burt's message of 2014-06-04 17:17:07 -0700: >> On Jun 4, 2014, at 7:05 PM, Clint Byrum >> wrote: >> >>> Excerpts from Zane Bitter's message of 2014-06-04 16:19:05 -0700: On 04/06/14 15:58, Vijendar Komalla wrote:

Re: [openstack-dev] [nova][glance] Consistency around proposed server instance tagging API

+1 to 404 for a DELETE if the tag does not exist. There's a good discussion in this paragraph from "RESTful Web APIs" book - http://books.google.com/books?id=wWnGQBAJ&lpg=PA36&ots=Ff9jCI293b&dq=restful%20http%20delete%20404%20sam%20ruby&pg=PA36#v=onepage&q=restful%20http%20delete%20404%20sam%

Re: [openstack-dev] [Heat]Heat template parameters encryption

Excerpts from Randall Burt's message of 2014-06-04 17:17:07 -0700: > On Jun 4, 2014, at 7:05 PM, Clint Byrum > wrote: > > > Excerpts from Zane Bitter's message of 2014-06-04 16:19:05 -0700: > >> On 04/06/14 15:58, Vijendar Komalla wrote: > >>> Hi Devs, > >>> I have submitted an WIP review (https

Re: [openstack-dev] [nova][glance] Consistency around proposed server instance tagging API

On Thu, Jun 5, 2014 at 4:14 AM, Jay Pipes wrote: > Hi Stackers, > > I'm looking to get consensus on a proposed API for server instance tagging > in Nova: > > https://review.openstack.org/#/c/91444/ > > In the proposal, the REST API for the proposed server instance tagging > looks like so: > > Rem

Re: [openstack-dev] [Heat]Heat template parameters encryption

On Jun 4, 2014, at 7:05 PM, Clint Byrum wrote: > Excerpts from Zane Bitter's message of 2014-06-04 16:19:05 -0700: >> On 04/06/14 15:58, Vijendar Komalla wrote: >>> Hi Devs, >>> I have submitted an WIP review (https://review.openstack.org/#/c/97900/) >>> for Heat parameters encryption blueprint

Re: [openstack-dev] [Heat]Heat template parameters encryption

Excerpts from Zane Bitter's message of 2014-06-04 16:19:05 -0700: > On 04/06/14 15:58, Vijendar Komalla wrote: > > Hi Devs, > > I have submitted an WIP review (https://review.openstack.org/#/c/97900/) > > for Heat parameters encryption blueprint > > https://blueprints.launchpad.net/heat/+spec/encry

[openstack-dev] Missing button to send Ctrl+Alt+Del for SPICE Console

Hello Stackers! I'm using SPICE Consoles now but, there is no button to send "Ctrl + Alt + Del" to a Windows Instance, so, it becomes very hard to log in into those guests... Can you guys enable it at Horizon?! Tks! Thiago ___ OpenStack-dev mailing lis

Re: [openstack-dev] [Heat]Heat template parameters encryption

On 04/06/14 15:58, Vijendar Komalla wrote: Hi Devs, I have submitted an WIP review (https://review.openstack.org/#/c/97900/) for Heat parameters encryption blueprint https://blueprints.launchpad.net/heat/+spec/encrypt-hidden-parameters This quick and dirty implementation encrypts all the paramete

Re: [openstack-dev] [neutron] Mid-cycle questions for folks

I think it's even cheaper than that. Try calling the hotel to get the better rate, I think Carl was able to successfully acquire the room at the cheaper rate (something like $115 a night or so). On Wed, Jun 4, 2014 at 4:56 PM, Edgar Magana Perdomo (eperdomo) wrote: > I tried to book online and it

[openstack-dev] [Barbican] KMIP support

> All, > I'm researching a bunch of HSM applications and I'm struggling to find much > info. I was wondering about the progress of KMIP support in Barbican? Is this > waiting on an open python KMIP support? Just for a bit more clarification, APL is supporting a KMIP implementation as a bac

Re: [openstack-dev] [solum] reviews for the new API

I documented a starting point for "What can be customized in the CI Pipeline". Hopefully this helps in the design discussion Take a look at the google docs below: https://docs.google.com/document/d/1a0yjxKWbwnY7g9NZtYALEZdm1g8Uf4fixDZLAgRBZCU/edit?pli=1# From: Adrian Otto [mailto:adrian.o...@rac

Re: [openstack-dev] [neutron] Mid-cycle questions for folks

I tried to book online and it seems that the pre-payment is non-refundable: "Hyatt.Com Rate Rate RulesFull prepayment required, non-refundable, no date changes." The price is $149 USD per night. Is that what you have blocked? Edgar On 6/4/14, 2:47 PM, "Kyle Mestery" wrote: >Hi all: > >I was

[openstack-dev] [neutron] Mid-cycle questions for folks

Hi all: I was curious if people are having issues booking the room from the block I have setup. I received word from the hotel that only one (1!) person has booked yet. Given the mid-cycle is approaching in a month, I wanted to make sure that people are making plans for travel. Are people booking

Re: [openstack-dev] [Infra] Meeting Tuesday June 3rd at 19:00 UTC

On Mon, Jun 2, 2014 at 9:39 AM, Elizabeth K. Joseph wrote: > Hi everyone, > > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting on Tuesday June 3rd, at 19:00 UTC in #openstack-meeting Meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/infra/2014/in

Re: [openstack-dev] [Neutron] Implementing new LBaaS API

Hi Andres, I've assumed (and we know how assumptions work) that the deprecation would take place in Juno and after a cyle or two it would totally be removed from the code. Even if #1 is the way to go, the old /vips resource would be deprecated in favor of /loadbalancers and /listeners. I agree #2

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

You are right. I did feel a bit bad about hijacking the thread. But, most of discussion was related closely enough that I never decided to fork in to a newer thread. I think I'm done now. I'll have a look at your review and we'll put IPAM to rest for now. :) Carl On Wed, Jun 4, 2014 at 2:36

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

We hijacked the vxlan initialization performance thread with ipam! :) I've tried to address initial problem with some simple sqla stuff: https://review.openstack.org/97774 With sqlite it gives ~3x benefit over existing code in master. Need to do a little bit more testing with real backends to make

[openstack-dev] [Neutron][IPv6] Issues on dnsmasq

Hi, Xu Han: You mentioned in the weekly meeting that you guys saw some issues in the lab, which may pertain to the dnsmasq source code I wrote. Would you please share with me the symptom and the procedures to reproduce them? I would like to take a look and fix the issue if necessary. Thanks!

Re: [openstack-dev] [Neutron] Implementing new LBaaS API

Hi Brandon, hi Kyle! I'm a bit confused about the deprecation (btw, thanks for sending this Brandon!), as I (wrongly) assumed #1 would be the chosen path for the new API implementation. I understand the proposal and #2 sounds actually cleaner. Just out of curiosity, Kyle, where is LBaaS functio

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

Yes, memcached is a candidate that looks promising. First things first, though. I think we need the abstraction of an ipam interface merged. That will take some more discussion and work on its own. Carl On May 30, 2014 4:37 PM, "Eugene Nikanorov" wrote: > > I was thinking it would be a separa

Re: [openstack-dev] [Fuel] Backporting bugfixes to stable releases

The backporting rules are now part of Fuel wiki: https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series There is also a new page on code review rules, please also review and make use of it: https://wiki.openstack.org/wiki/Fuel/Code_Review_Rules On Mon, J

[openstack-dev] [Neutron][L3] Team Meeting Thursday at 1500 UTC

We'll meet tomorrow at the regular time in #openstack-meeting-3. Juno-1 is just one week away. We will discuss the distributed virtual router (DVR) work to see what the community can do to help the DVR team land the hard work that they've been doing. I believe that we also have some IPAM stuff t

[openstack-dev] [Heat]Heat template parameters encryption

Hi Devs, I have submitted an WIP review (https://review.openstack.org/#/c/97900/) for Heat parameters encryption blueprint https://blueprints.launchpad.net/heat/+spec/encrypt-hidden-parameters This quick and dirty implementation encrypts all the parameters on on Stack 'store' and decrypts on on Sta

Re: [openstack-dev] [solum] reviews for the new API

Good question Randall. Either we implement some workflow, which is what we do now that is not configurable, or we adopt another workflow system. We figured that using an existing workflow system would be smarter than duplicating one by making Solum any more configurable. We have plans to allow

Re: [openstack-dev] Kerberization of Horizon (kerbhorizon?)

I suspect that to be true. Just adding a second authentication backend to the django-openstack-auth package would be fine. At least some of the logic should be reusable and creating a whole additional package seems like an unnecessary separation. - Gabriel From: Adam Young [mailto:ay

Re: [openstack-dev] Kerberization of Horizon (kerbhorizon?)

On 06/04/2014 03:10 PM, Gabriel Hurley wrote: I've implemented Kerberos (via Apache) + Django once before, and yes, taking this as pseudo-code you're on the right track. Obviously the devil is in the details and you'll work out the particulars as you go. The most important bit (obviously) is

[openstack-dev] [sahara] team meeting June 5 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140605T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] [solum] reviews for the new API

Sorry to poke my head in, but doesn't that beg the question of why you'd want to expose some third party DSL in the first place? If its an advanced feature, I wonder why it would be even considered before the 90% solution works, much less take a dependency on another non-integrated service. IMO,

[openstack-dev] [Nova] Need help with a gnarly Object Version issue

Hi Folks, I've been working on a change to make the user_data field an optional part of the Instance object since passing it around everywhere seems a bad idea since: - It can be huge - It's only used when getting metadata - It can contain user sensitive data - http

Re: [openstack-dev] [Horizon] How to conditionally modify attributes in CreateNetwork class.

Hi Timur, Really appreciate your reply. Will try your suggestions. Thanks, Nader. On Tue, Jun 3, 2014 at 4:22 AM, Timur Sufiev wrote: > Hello, Nader! > > As for `contributes` attribute, you could override `contribute(self, > data, context)` method in your descendant of `workflows.Step` which

Re: [openstack-dev] [solum] reviews for the new API

The problem with exposing Mistral DSL the way it is, is that there are many things the user should not be aware of. Lets take the example Mistral DSL created here, https://review.openstack.org/#/c/95709/4/etc/solum/workbooks/build.yaml Why should the end user know and define things like auth_to

Re: [openstack-dev] Kerberization of Horizon (kerbhorizon?)

I've implemented Kerberos (via Apache) + Django once before, and yes, taking this as pseudo-code you're on the right track. Obviously the devil is in the details and you'll work out the particulars as you go. The most important bit (obviously) is just making absolutely sure your REMOTE_USER hea

[openstack-dev] Kerberization of Horizon (kerbhorizon?)

OK, so I'm cranking on All of the Kerberso stuff: plus S4U2Proxy work etcexcept that I have never worked with DJango directly before. I want to get a sanity check on my approach: Instead of "authenticating" to Keystone, Horizon will use mod_auth_krb5 and REMOTE_USER to authenticate the u

[openstack-dev] [nova][glance] Consistency around proposed server instance tagging API

Hi Stackers, I'm looking to get consensus on a proposed API for server instance tagging in Nova: https://review.openstack.org/#/c/91444/ In the proposal, the REST API for the proposed server instance tagging looks like so: Get list of tags for server: GET /v2/{project_id}/servers/{server_

Re: [openstack-dev] [heat] Resource action API

On 04/06/14 03:01, yang zhang wrote: Hi all, Now heat only supports suspending/resuming a whole stack, all the resources of the stack will be suspended/resumed, but sometime we just want to suspend or resume only a part of resources Any reason you wouldn't put that subset of resources into

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

- Original Message - > From: "ChangBo Guo" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, June 3, 2014 10:40:19 PM > Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation > ratio out of scheduler > > Jay, thanks for raisin

[openstack-dev] [NFV] - follow up on scheduling discussion

All, Thanks for the interest in the NFV scheduling topic. Please find a proposal on "Smart Scheduler (Solver Scheduler) enhancements for NFV: Use Cases, Constraints etc.". https://docs.google.com/document/d/1k60BQXOMkZS0SIxpFOppGgYp416uXcJVkAFep3Oeju8/edit#heading=h.wlbclagujw8c Based on this

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On 06/04/2014 11:56 AM, Day, Phil wrote: Hi Jay, * Host aggregates may also have a separate allocation ratio that overrides any configuration setting that a particular host may have So with your proposal would the resource tracker be responsible for picking and using override values defined a

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On 06/04/2014 06:10 AM, Murray, Paul (HP Cloud) wrote: Hi Jay, This sounds good to me. You left out the part of limits from the discussion – these filters set the limits used at the resource tracker. Yes, and that is, IMO, bad design. Allocation ratios are the domain of the compute node and t

Re: [openstack-dev] [solum] reviews for the new API

Murali, Roshan. I think there is a misunderstood. By default, the user wouldn't see any "workflow" dsl. If the user does not specify anything, we would use a pre-defined mistral workbook defined by Solum, as Adrian described If the user needs more, mistral is not so complicated. Have a look at th

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On 06/04/2014 12:19 PM, Mike Spreitzer wrote: John Garbutt wrote on 06/04/2014 04:29:36 AM: > On 3 June 2014 14:29, Jay Pipes wrote: > > tl;dr > > = > > > > Move CPU and RAM allocation ratio definition out of the Nova scheduler and > > into the resource tracker. Remove the calculatio

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On 06/04/2014 03:08 AM, Yingjun Li wrote: +1, if doing so, a related bug related bug may be solved as well: https://bugs.launchpad.net/nova/+bug/1323538 Yep, I agree that the above bug would be addressed. Best, -jay On Jun 3, 2014, at 21:29, Jay Pipes mailto:jaypi...@gmail.com>> wrote: Hi

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On 06/03/2014 10:40 PM, ChangBo Guo wrote: Jay, thanks for raising this up . +1 for this . A related question about the CPU and RAM allocation ratio, shall we apply them when get hypervisor information with command "nova hypervisor-show ${hypervisor-name}" The output shows like | memory_mb

Re: [openstack-dev] [solum] reviews for the new API

Agreeing with what Murali said below. We should make things really simple for the 99 percentile of the users, and not force the complexity needed by the minority of the "advanced users" on the rest of the 99 percentile users. Mistral is a generic workflow DSL, we do not need to expose all that c

Re: [openstack-dev] [solum] reviews for the new API

Murali, I’d like to explore the possibility that Solum users don’t need to see a pipeline DSL at all in the general case, and that only power users are interacting with it. If that UX is possible, then what DSL is used is much less important as long as it allows customizations to at least the m

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

On Thu, Jun 5, 2014 at 12:19 AM, Mike Spreitzer wrote: > > Overcommitting affects the quality of service delivered to the cloud user. > In this situation in particular, as in many situations in general, I think > we want to enable the service provider to offer multiple qualities of > service. T

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

Thanks for the excellent feedback on these, guys! I’ll be working on making updates over the next week and will send a fresh link out when done. Anyone else with feedback, please feel free to fire away. Best, Liz On Jun 4, 2014, at 12:33 PM, Eoghan Glynn wrote: > > Hi Liz, > > Two further th

[openstack-dev] test message - please ignore

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

Re: [openstack-dev] [Neutron] Implementing new LBaaS API

Thanks for your feedback Kyle. I will be at that meeting on Monday. Thanks, Brandon On Wed, 2014-06-04 at 11:54 -0500, Kyle Mestery wrote: > On Tue, Jun 3, 2014 at 3:01 PM, Brandon Logan > wrote: > > This is an LBaaS topic bud I'd like to get some Neutron Core members to > > give their opinions

Re: [openstack-dev] [solum] reviews for the new API

Hi Angus, Julien, No major disagreements. My thinking is that we should provide more application developer focused mechanism for customizing workflows (point #3). This may not necessarily be an entirely new DSL. It could just be additions to the current Plan structure. For example, we could add

Re: [openstack-dev] [solum] reviews for the new API

Angus/Julien, I would disagree that we should expose the mistral DSL to end users. What if we decide to use something other than Mistral in the future? We should be able to plug in any workflow system we want without changing what we expose to the end user. To me, the pipeline DSL is similar t

Re: [openstack-dev] [Murano] [meetings] Murano bug scrub

Today we continued our 'bug scrub' meeting and discussed all issues, which were assigned to 'juno-1' mailstone and also all 'new' issues. The meeting minutes are available by the following links: Minutes: http://eavesdrop.openstack.org/meetings/murano_bug_scrub/2014/murano_bug_scrub.2014-06-04-15

Re: [openstack-dev] [Neutron] Implementing new LBaaS API

On Tue, Jun 3, 2014 at 3:01 PM, Brandon Logan wrote: > This is an LBaaS topic bud I'd like to get some Neutron Core members to > give their opinions on this matter so I've just directed this to Neutron > proper. > > The design for the new API and object model for LBaaS needs to be locked > down be

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

Hi Liz, Two further thoughts occurred to me after hitting send on my previous mail. First, is the concept of alarm dimensioning; see my RDO Ceilometer getting started guide[1] for an explanation of that notion. "A key associated concept is the notion of dimensioning which defines the set of ma

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

> > Not only live upgrades but also dynamic reconfiguration. > > Overcommitting affects the quality of service delivered to the cloud user. > In this situation in particular, as in many situations in general, I think > we want to enable the service provider to offer multiple qualities of > service

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

Comments inline ... > Hi Liz, > > The designs look really cool and I think that we should consider a couple of > things (more related to the alarm’s implementation made at Ceilometer): > > · There are combined alarms, which are a combination of two or more alarms. > We need to see how they work

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

John Garbutt wrote on 06/04/2014 04:29:36 AM: > On 3 June 2014 14:29, Jay Pipes wrote: > > tl;dr > > = > > > > Move CPU and RAM allocation ratio definition out of the Nova scheduler and > > into the resource tracker. Remove the calculations for overcommit out of the > > core_filter and ram

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

I will provide a little more context for the TC audience. I asked Hemanth to tag this message [TC] because at the Juno summit in the cross-project track there was discussion of cross-project api consistency [1]. The main outcome of that meeting was that "TC should recommend API conventions via open

Re: [openstack-dev] [Nova] Different tenants can assign the same hostname to different machines without an error

> The patch [2] proposes changing the default DNS driver from > 'nova.network.noop_dns_driver.NoopDNSDriver' to other that verifies if > DNS entries already exists before adding them, such as the > 'nova.network.minidns.MiniDNS'. Changing a default setting in a way that isn't backwards compatible

Re: [openstack-dev] [NFV] Meeting Minutes - Wednesday June 4

Here are the minutes from the first NFV ( https://wiki.openstack.org/wiki/Meetings/NFV ) meeting. Next meeting: June 11, 2014 1400 UTC (Tuesday) 1. a. https://wiki.openstack.org/wiki/Meetings/NFV (russellb, 14:02:50) 2. mission statement (russellb, 14:04:15) a. https://etherpad.openstack.or

Re: [openstack-dev] [solum] reviews for the new API

Hi Angus, I really agree with you. I would insist on #3, most of our users will use the default workbook, and only advanced users will want to customize the workflow. "advanced" users should easily understand a mistral workbook, cause they are "advanced" To add to the cons of creating our own DSL

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

Hi Liz, Looks great! Some thoughts on the wireframe doc: * The description of form: "If CPU Utilization exceeds 80%, send alarm." misses the time-window aspect of the alarm definition. Whereas the boilerplate default descriptions generated by ceilometer itself: "cpu_util >

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

Hi Jay, > * Host aggregates may also have a separate allocation ratio that overrides > any configuration setting that a particular host may have So with your proposal would the resource tracker be responsible for picking and using override values defined as part of an aggregate that includes the

Re: [openstack-dev] [nova] nova default quotas

>Matt and I chatted on IRC and have come up with an outlined plan, if we missed >anything please don't hesitate to comment or ask. > >https://etherpad.openstack.org/p/quota-classes-goof-up I added a few thoughts / questions From: Joe Gordon [mailto:joe.gord...@gmail.com] Sent: 02 June 2014 21:52

Re: [openstack-dev] [NFV] Sub-team Meeting Reminder - Wednesday June 4 @ 1400 utc

No worries Steve I think we figured it out ;-) /Alan -Original Message- From: Steve Gordon [mailto:sgor...@redhat.com] Sent: June-04-14 9:54 AM To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-operat...@lists.openstack.org Subject: Re: [openstack-dev] [NFV]

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

On 05/30/2014 02:22 PM, Hemanth Makkapati wrote: > Hello All, > I'm writing to notify you of the approach the Glance community has > decided to take for doing functional API. Also, I'm writing to solicit > your feedback on this approach in the light of cross-project API > consistency. > > At the

Re: [openstack-dev] [Neutron] test configuration for ml2/ovs L2 and L3 agents

I don't necessarily push new patches when I merge these patches to a new devstack. That is why it appears to be very old. The changes should still be reasonably applicable to the current master in devstack. I used them just last week with devstack master. Don't worry about the base. Just read

Re: [openstack-dev] [Neutron] test configuration for ml2/ovs L2 and L3 agents

Hey Carl, Thanks for the quick response. I'm missing something because the version in your review is quite different the version I see when I clone devstack on my test machine, or when I browse https://github.com/openstack-dev/devstack/blob/master/samples/local.conf. I'm not referring to your

[openstack-dev] failed to load customised image

Hi All, I want to upload my customised rootfs and kernel image for powerpc to the openstack database. For this I followed the following document: http://docs.openstack.org/grizzly/openstack-compute/admin/content/creating-custom-images.html#d6e6473 I followed the following steps as described in

Re: [openstack-dev] [Barbican] KMIP support

Thanks guys, you¹ve answered everything I needed to know! I¹ll look to see what help I can provide to the KMIP efforts. -Rob On 04/06/2014 15:18, "Becker, Bill" wrote: >Regarding: >> Also, is the ³OpenStack KMIP Client² ever going to be a thing? >> (https://wiki.openstack.org/wiki/KMIPclient

Re: [openstack-dev] [ironic workflow question]

On Wed, Jun 4, 2014 at 2:51 PM, 严超 wrote: > Yes, but when you assign a "production" image to an ironic bare metal node. > You should provide ramdisk_id and kernel_id. > Should the ramdisk_id and kernel_id be the same as deploy images (aka the > first set of k+r) ? > You didn't answer me if the two

Re: [openstack-dev] [Marconi] Kafka support and high throughput

Hi Flavio, In your discussions around a developing Kafka plugin for Marconi would that be potentially be done by adding a Kafka transport to oslo.messaging? That is something that I'm very interested in for the monitoring as a service project I'm working on. Thanks --Roland On 6/4/14, 3:06 AM, "

Re: [openstack-dev] [ironic workflow question]

On Wed, Jun 4, 2014 at 6:51 AM, 严超 wrote: > Yes, but when you assign a "production" image to an ironic bare metal node. > You should provide ramdisk_id and kernel_id. > Should the ramdisk_id and kernel_id be the same as deploy images (aka the > first set of k+r) ? > You didn't answer me if the two

Re: [openstack-dev] [Ironic]Need to know the process to make changes to nova ironic virt driver

We are in the process of proposing the nova.virt.ironic driver to the Nova tree, where it really belongs. Specs are here: https://review.openstack.org/#/c/95024/ https://review.openstack.org/#/c/95025/ While that work is ongoing, any significant new features / changes in the nova.virt.ironic driv

[openstack-dev] [Horizon] [UX] [ceilometer] Design for Alarming and Alarm Management

I'm adding the ceilometer tag so the Ceilometer guys can participate as well. Cheers, H From: Martinez, Christian [mailto:christian.marti...@intel.com] Sent: Tuesday, June 3, 2014 5:21 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon] [UX] D

Re: [openstack-dev] [Nova] nova-compute deadlock

Hi Zhu Zhu, Thank you for reading my diagram! I need to clarify that this problem does not occur during data injection. Before creating the ISO, the driver code will extend the disk. Libguestfs is invoked in that time frame. And now I think this problem may occur at any time, if the code use t

Re: [openstack-dev] [Barbican] KMIP support

Regarding: > Also, is the “OpenStack KMIP Client” ever going to be a thing? > (https://wiki.openstack.org/wiki/KMIPclient) We made some progress with some prototype code, but never completed the effort. We subsequently marked the corresponding blueprint as "obsolete": https://blueprints.launchpad

Re: [openstack-dev] [ironic bare metal install problem]

On 04/06/14 17:21 +0800, 严超 wrote: Hi, All: When I tried to deploy a bare metal using ironic and following http://ma.ttwagner.com/bare-metal-deploys-with-devstack-and-ironic/, I face the one issue: It looks like this message came through several times, and that someone helped you in anothe

Re: [openstack-dev] [ironic workflow question]

On Wed, 2014-06-04 at 21:51 +0800, 严超 wrote: > Yes, but when you assign a "production" image to an ironic bare metal > node. You should provide ramdisk_id and kernel_id. What do you mean by "assign" here? Could you quote some documentation? Instance image is "assigned" using --image argument to `n

Re: [openstack-dev] question about createbackup API in nova

On 06/04/2014 02:56 AM, Bohai (ricky) wrote: Hi stackers, When I use the createBackup API, I found it just snapshots the root disk of the instance. For an instance with multiple cinder backend volumes, it will not snapshot them. It's a little different to the things in current createImage API.

[openstack-dev] [Nova] Different tenants can assign the same hostname to different machines without an error

Hi everyone, Concerning the bug described at [1], where n different machines may have the same hostname and then n different DNS entries with that hostname are written; some points have to be discussed with the nova community. On the bug review [2], Andrew Laski pointed out that we should dis

Re: [openstack-dev] [ironic workflow question]

Yes, but when you assign a "production" image to an ironic bare metal node. You should provide *ramdisk_id and kernel_id. * Should the *ramdisk_id and kernel_id* be the same as deploy images (aka the first set of k+r) ? You didn't answer me if the two sets of r + k should be the same ? *Best Regar

Re: [openstack-dev] [NFV] Sub-team Meeting Reminder - Wednesday June 4 @ 1400 utc

Hi all, Just a heads-up - apparently this clashed with the docs meeting, as a result the NFV meeting will occur in #openstack-meeting-alt. Apologies for any convenience, Steve - Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage question

  1   2   >