[openstack-dev] question about createbackup API in nova

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. My question is whether it's reasonable and dis

[openstack-dev] [heat] Resource action API

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 in the stack, so I think adding resource-action API for heat isnecessary. this API will be he

Re: [openstack-dev] [Ceilometer] Question of necessary queries for Event implemented on HBase

Hello, For today I have prepared a spec for events feature in HBase https://review.openstack.org/#/c/96417/, and it was successfully merged. In spec was described the details of event features in HBase. Yours, Igor D. On Wed, May 21, 2014 at 3:03 PM, Dmitriy Ukhlov wrote: > Hello Igor, > > Sou

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

+1, if doing so, a related bug related bug may be solved as well: https://bugs.launchpad.net/nova/+bug/1323538 On Jun 3, 2014, at 21:29, Jay Pipes wrote: > Hi Stackers, > > tl;dr > = > > Move CPU and RAM allocation ratio definition out of the Nova scheduler and > into the resource tracke

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

Hi, Xurong, How do you test it in postgresql? Do you use tox to do a unittest and get the result(1h)? /Yalei From: Xurong Yang [mailto:ido...@gmail.com] Sent: Thursday, May 29, 2014 6:01 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Neutron] One

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

Excerpts from yang zhang's message of 2014-06-04 00:01:41 -0700: > > > > > > > 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 in the stac

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

Unit tests use sqlite db backend, so it might be much faster than production environment where DB is on different server. Eugene. On Wed, Jun 4, 2014 at 11:14 AM, Wang, Yalei wrote: > Hi, Xurong, > > > > How do you test it in postgresql? Do you use tox to do a unittest and get > the result(1h

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

> From: cl...@fewbar.com > To: openstack-dev@lists.openstack.org > Date: Wed, 4 Jun 2014 00:09:39 -0700 > Subject: Re: [openstack-dev] [Spam] [heat] Resource action API > > Excerpts from yang zhang's message of 2014-06-04 00:01:41 -0700: > > > > > > > > > > > > > > Hi all, Now heat only

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

Excerpts from yang zhang's message of 2014-06-04 01:14:37 -0700: > > > From: cl...@fewbar.com > > To: openstack-dev@lists.openstack.org > > Date: Wed, 4 Jun 2014 00:09:39 -0700 > > Subject: Re: [openstack-dev] [Spam] [heat] Resource action API > > > > Excerpts from yang zhang's message of 2014-0

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

+1, makes sense to me. On Wed, Jun 4, 2014 at 3:08 PM, Yingjun Li wrote: > +1, if doing so, a related bug related bug may be solved as well: > https://bugs.launchpad.net/nova/+bug/1323538 > > On Jun 3, 2014, at 21:29, Jay Pipes wrote: > > Hi Stackers, > > tl;dr > = > > Move CPU and RAM all

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

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_filter scheduler pieces. +1 I hope to see us send more specif

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

+1 for this proposal. We are highly interested in this one. Jaesuk Ahn, Ph.D. Team Lead, Next Generation Cloud Platform Dev. Project KT … active member of openstack community On Jun 4, 2014, 5:29:36 PM, John Garbutt wrote: On 3 June 2014 14:29, Jay Pipes

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

HI All, Could someone please, review the bug https://bugs.launchpad.net/horizon/+bug/1301359 Made Size parameter optional while creating DB Instance. While creating Database Instance size parameter depends on whether trove_volume_support is set. So size paramater is set to mandatory if trove_vol

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

On 02/06/14 07:52 -0700, Keith Newstadt wrote: Thanks for the responses Flavio, Roland. Some background on why I'm asking: we're using Kafka as the message queue for a stream processing service we're building, which we're delivering to our internal customers as a service along with OpenStack.

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

Does there is any blueprint related to this? Thanks. 2014-06-03 21:29 GMT+08:00 Jay Pipes : > Hi Stackers, > > 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

[openstack-dev] [NFV] No-brainer BPs submitted and specs on NFV meeting page

I've written up three blueprints for some problems that were repeatedly aired at the summit's NFV BOF. This may well only be a start of the blockers list, but at least it is a start, and I think at least two of them are straightforward. (I might even have found a workaround for one, not had chanc

Re: [openstack-dev] [Rally] Tempest + Rally: first success

Thanks for traceback. I reported a bug on launchpad[1] based on your logs. Below you can find several possible solutions at the moment: 1) Wait for bug-fix 2) Create neutron subnet manually(some tutorials: [2], [3]) 3) Copy existing Tempest configuration file into Rally(Rally stores Tempest config

Re: [openstack-dev] [Murano] Murano API improvements

+2 to Stan: there is a strong need for v2 API which would satisfy the needs of Murano 0.5+. The current one is definitely outdated. I'd like to point that there are at least two major flaws in the v1 design: 1. Sessions. Actually, they violate one of the core principles of RESTful design - the cl

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

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. You also left out the force-to-host and its effect on limits. Yes, I would agree with doing this at the resource tracker too. And of course the exten

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

On Wed, Jun 04, 2014 at 02:18:19PM +0530, Harshada Kakad wrote: > HI All, > Could someone please, review the bug > https://bugs.launchpad.net/horizon/+bug/1301359 > > > Made Size parameter optional while creating DB Instance. > > While creating Database Instance size parameter depends on > wheth

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

HI Matthias Runge, Which feature in trove are you talking about? And even which capabilities are missing which will make the patch fail? I believe the patch has nothing to do with https://review.openstack.org/#/c/83503/ On Wed, Jun 4, 2014 at 3:45 PM, Matthias Runge wrote: > On Wed, Jun 04, 2

[openstack-dev] [ironic workflow question]

Hi, All: I searched a lot about how ironic automatically install image on bare metal. But there seems to be no clear workflow out there. What I know is, in traditional PXE, a bare metal pull image from PXE server using tftp. In tftp root, there is a ks.conf which tells tftp which im

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

On 05/31/2014 11:13 PM, Jeremy Stanley wrote: On 2014-05-29 20:55:01 + (+), Lyle, David wrote: [...] There are several more xstatic packages that horizon will pull in that are maintained outside openstack. The packages added are only those that did not have existing xstatic packages. The

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

Hi! Workflow is not entirely documented by now AFAIK. After PXE boots deploy kernel and ramdisk, it exposes hard drive via iSCSI and notifies Ironic. After that Ironic partitions the disk, copies an image and reboots node with final kernel and ramdisk. On Wed, 2014-06-04 at 19:20 +0800, 严超 wrote:

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I have posted this series and it has evoked a surprising (to me) amount of discussion so I wanted to clarify some things and talk to some of the issues so we can move forward. So first note is this is an early posting and still is not tested m

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

Hi, Thank you very much for your reply ! But there are still some questions for me. Now I've come to the step where ironic partitions the disk as you replied. Then, how does ironic copies an image ? I know the image comes from glance. But how to know image is really available when reboot? And, what

[openstack-dev] [horizon] mocking policy

Hello, I'd like to start a discussion about the use of mocking libraries in Horizon's tests, in particular, mox and mock. As you may know, Mox is the library that has been used so far, and we have a lot of tests written using it. It is based on a similar Java library and does very strict checking

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

On Wed, Jun 04, 2014 at 04:13:33PM +0530, Harshada Kakad wrote: > HI Matthias Runge, > > Which feature in trove are you talking about? > And even which capabilities are missing which will make the patch fail? > I believe the patch has nothing to do with > https://review.openstack.org/#/c/83503/ I

Re: [openstack-dev] [horizon] mocking policy

On 06/04/2014 02:41 PM, Radomir Dopieralski wrote: > Hello, > > I'd like to start a discussion about the use of mocking libraries in > Horizon's tests, in particular, mox and mock. > > As you may know, Mox is the library that has been used so far, and we > have a lot of tests written using it. It

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

On Wed, 2014-06-04 at 20:29 +0800, 严超 wrote: > Hi, > > Thank you very much for your reply ! > > But there are still some questions for me. Now I've come to the step > where ironic partitions the disk as you replied. > > Then, how does ironic copies an image ? I know the image comes from > glance

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

On Wed, 2014-06-04 at 21:18 +0800, 严超 wrote: > Thank you ! > > I noticed the two sets of k+r in tftp configuration of ironic. > > Should the two sets be the same k+r ? Deploy images are created for you by DevStack/whatever. If you do it by hand, you may use diskimage-builder. Currently they are s

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

Thank you ! I noticed the two sets of k+r in tftp configuration of ironic. Should the two sets be the same k+r ? The first set is defined in the ironic node definition. How do we define the second set correctly ? *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727

Re: [openstack-dev] [horizon] mocking policy

On 06/04/2014 02:56 PM, Ana Krivokapic wrote: > +1 for adding Mock to the requirements (test-requirements.txt rather > than requirements.txt, right?) and using it in newly written tests. +1 for the usage of mock. Also the use of mox3 should be preferred. mox is not compatible with Python3 and it'

[openstack-dev] [QA] Meeting Thursday June 5th at 17:00UTC

Hi Everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be this Thursday, June 5th at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an

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

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

[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] 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.

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

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

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

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

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

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

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] [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] [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] [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] [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/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] [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 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] [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

[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

- 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

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

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

[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

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

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

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

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

[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

[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

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

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

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

  1   2   >