Re: [openstack-dev] [Ceilometer] Collector no recheck the db status

On Wed, Apr 02 2014, dong jia wrote: > I found that when collector service starting, if the db has not yet ready, > it will log an error info like 'Could not load 'database': could not > connect to...' but the service still goes on. Later when the db is ready, > but there are no mechanisms to chec

Re: [openstack-dev] [Mistral] How Mistral handling long running delegate tasks

On 02 Apr 2014, at 13:38, Kirill Izotov wrote: > I agree that we probably need new engine for that kind of changes and, as > Renat already said in another thread, lazy model seems to be more basic and > it would be easier to build sync engine on top of that rather than other way > around. Yes,

[openstack-dev] Nova Live Migration issue

Hi all I'm following the below link for VM migration from one compute node to the another from the controller node using devstack .. http://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/ I'm able to migrate the instance from one compute node t

Re: [openstack-dev] Nova Live Migration issue

Hi! Can you show libvirt logs? Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2014-04-02 11:55 GMT+04:00 abhishek jain : > Hi all > > I'm following the below link for VM migration from one compute node to the > another from the controller node using devstack

Re: [openstack-dev] [Neutron LBaaS] Need help with LBaaS drivers

Hi Vijay, Currently you may follow two ways in writing an LBaaS driver: 1) write it from scratch (like Radware, Netscaler, Embrane drivers) - in this case your driver should inherit abstract_driver.LoadBalancerAbstractDriver and will be running on Neutron service process, LBaaS agent won't

Re: [openstack-dev] [tempest][scenario] independece test between Stack and backing services?

Hello, Igawa-san Thanks for pointing out Tempest principles. I wasn't aware of them. ok, I'll probably use the current test cases with manually stopping services. I'm checking with Temest(icehouse) and if I write or think up something useful, I'll be back. Also Grenade, too. :) Thank you

[openstack-dev] [Heat] PTL Candidacy

Hello all, I'd like announce my candidacy for Heat PTL. It's been a pleasure to be part of such a great team for about a year now, and that's the main driver for me to want to represent all of you. I trust that as a team we'll continue do a good job delivering nice software, and I hope I could

Re: [openstack-dev] [Heat] PTL Candidacy

confirmed On 04/02/2014 11:06 AM, Thomas Herve wrote: > Hello all, > > I'd like announce my candidacy for Heat PTL. > > It's been a pleasure to be part of such a great team for about a year now, > and that's the main driver for me to want to represent all of you. I trust > that as a team we'll

Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt

On Tue, Apr 01, 2014 at 08:22:37PM +0200, Michał Dubiel wrote: > OK, thanks Russell and Daniel for your suggestions. > > Stackforge sounds reasonable for the time being, though it's not perfect as > it doesn't prevent from occasional conflicts we may hit while pulling > changes from the original N

[openstack-dev] [Tuskar][Horizon] Javascript linter

Hi all, Recently we have been discussing the topic of Javascript linters for Horizon and Tuskar-UI with Radomir, and he told me that JSLint and JSHint can not be integrated into the test environment due to some license issues. I did some search and found Closure Linter [1] by Google which might

Re: [openstack-dev] Nova Live Migration issue

Can you confirm that it's no longer running on the source node and only running on the destination node? What's your libvirt version? Possibly the libvirt monitor lost connection and didn't complete the post-migration which would update the db. As Nikolay suggested, the libvirt.log would tell

[openstack-dev] [Tempest][qa] : backporting "Test Security Groups Basic Ops" in stable/havana ?

Hi everyone, I'm interested in having the Tempest scenario "Test Security Groups Basic Ops" available in the stable/Havana branch . This scenario is nice for acceptance tests and it's running fine with an Havana deployment. Can someone in the Stable-maint team can backport it from master to s

Re: [openstack-dev] [climate] PTL Candidacy

Confirmed. On Wed, Apr 2, 2014 at 12:11 AM, Dina Belova wrote: > Howdy, folks! > > I'd like to announce my wish to continue being Climate PTL during next Juno > release cycle. > > I have been working on Climate initiative since really early stages of its > development and was leading the subteam

[openstack-dev] Missleading and hardly parseable default neutron config files

Hi, The default neutron configuration files aren't useable by default. So, I'm heavily patching them in my Debian package. This isn't an idea situation already, especially that I have to rebase my patch on each (pre-)release. Though here, if I'm not mistaking, we're having a completely *wrong* exa

Re: [openstack-dev] [tempest][scenario] independece test between Stack and backing services?

Fault injection is a problem I've been thinking about, though I don't have time to dive into it any time soon. But I'll share my ideas in case they are interesting. I think we need a Fault Injection Service for OpenStack. It would act like many of the other OpenStack services, have an API service,

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

Hi Thomas, it probably won't be a bad idea if you can share the patches you're applying to the default configuration files. I think all distros are patching them anyway, so this might allow us to provide mostly ready to use config files. Is there a chance you can push something to gerrit? Salvat

[openstack-dev] Documenting FWaaS

Hi! I am currently documenting FWaaS for development purposes. My focus is to have a detailed end-to-end flow (from plugin to driver. I thought it would be a good idea to share my deliverables (document + images) with the community and have feedback from the community. Since I am a newcomer to op

Re: [openstack-dev] Facing an issue in swift

In my experience 'Endpoint for object-store not found - have you specified a region?' can be returned by swift client if: (a) You have specified a region that isn't found among the service endpoints e.g. % swift --os-auth-url http://example:5000/v2.0 --os-password=testing stat --os-username=te

Re: [openstack-dev] Nova Live Migration issue

Thanks Nikolay and Parthipan I have confirmed that the instance is running on the newer compute node by using sudo virsh list command. I'm using below libvirt version .. libvirtd (libvirt) 0.9.8 Actually I will not be able to present the libvirt logs due to setup problem.I'll send logs as soon

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

Hi, from my side there is definite interest in this, as the changes didn’t make it yet. Thanks Sebastian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Nova Live Migration issue

Hello Abhishek, Did you check on the source node whether the instance is still running or even defined (virsh list -all). This is because nova notices that the migration is completed when the VM in the source is gone and then triggers the post-migration. IIRC, there's a bug in 0.x libvirt wher

Re: [openstack-dev] Nova Live Migration issue

Hi Parthi I have confirmed on the destination node i.e( newer compute node on which the instance is migrated ) by using sudo virsh list and the instance is being reflected there. Moreover on the source node the sudo virsh list command reflects nothing. Also I'll try with libvirt 1.x and let you

[openstack-dev] [Trove] Icehouse RC1 available

Hello everyone, Trove just published its first Icehouse release candidate. The list of bugs fixed since feature freeze and the RC1 tarball are available at: https://launchpad.net/trove/icehouse/icehouse-rc1 Unless release-critical issues are found that warrant a release candidate respin, this RC

[openstack-dev] Keystone PTL Candidacy

Hello, everyone! I'd like to keep my name in the hat as PTL for Keystone during the Juno release cycle. As I'm not looking to shake things up for Juno, I'm going to direct you to my Icehouse PTL candidacy email [1], and promise that I will continue to deliver on that philosophy in Juno. Specific

Re: [openstack-dev] Keystone PTL Candidacy

confirmed On 04/02/2014 02:48 PM, Dolph Mathews wrote: > Hello, everyone! > > I'd like to keep my name in the hat as PTL for Keystone during the Juno > release cycle. > > As I'm not looking to shake things up for Juno, I'm going to direct you to > my Icehouse PTL candidacy email [1], and promise

Re: [openstack-dev] [tempest][scenario] independece test between Stack and backing services?

Hi Sean, I'm already working on something similar. What I'm trying to do is not a service, but a set of tests that would be able to run commands on the nodes and restart services, kill disks, etc. The basic idea is to inject some fault, see if everything still works as expected and restore th

Re: [openstack-dev] [Keystone] python-keystoneclient v3 functionality

On 04/01/2014 07:36 AM, Yaguang Tang wrote: Thanks Jamie, then the following question is do we intend to move other services client library V3 identity support to python-openstackclient? AFAIK it's poorly supported for Nova Cinder Neutron client library, and I am working on add v3 support for

Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API

On Tue, Apr 1, 2014 at 7:40 PM, Anne Gentle wrote: > > > > On Wed, Mar 26, 2014 at 5:30 AM, Thierry Carrez wrote: > >> Russell Bryant wrote: >> > [...] >> > First, it seems there isn't a common use of "deprecated". To me, >> > marking something deprecated means that the deprecated feature: >> >

Re: [openstack-dev] Operators & Design Summit ideas for Atlanta

On Mon, Mar 31, 2014 at 10:40 PM, Adam Young wrote: > On 03/28/2014 03:01 AM, Tom Fifield wrote: > >> Thanks to those projects that responded. I've proposed sessions in swift, >> ceilometer, tripleO and horizon. >> > > > Keystone would also be interested in user feedback, of course. Crossing op

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

What licensing issues were brought up that prevent the use of JSLint or JSHint? Both are MIT licensed. Granted, JSLint has an additional clause: > The Software shall be used for Good, not Evil. Maybe that's it? If so, Crockford has been known to make exceptions for organizations that wish to us

Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API

On 04/02/2014 09:20 AM, Dolph Mathews wrote: > > On Tue, Apr 1, 2014 at 7:40 PM, Anne Gentle > wrote: > > > > > On Wed, Mar 26, 2014 at 5:30 AM, Thierry Carrez > mailto:thie...@openstack.org>> wrote: > > Russell Bryant wrote: > > [...] >

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

On 02/04/14 15:26, Kevin Conway wrote: > What licensing issues were brought up that prevent the use of JSLint or > JSHint? Both are MIT licensed. > > Granted, JSLint has an additional clause: > > The Software shall be used for Good, not Evil. > > > Maybe that's it? If so, Crockford has been

Re: [openstack-dev] [tempest][scenario] independece test between Stack and backing services?

Good stuff. I like the semantics of what the destroy stack tests look like, very clean. I still think there would be value in doing this as a API service, which would let you decouple the test cases (and even put them in Tempest), as the tests could just assume certain fault semantics, and the imp

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

On 04/02/2014 06:38 AM, Salvatore Orlando wrote: > Hi Thomas, > > it probably won't be a bad idea if you can share the patches you're > applying to the default configuration files. > I think all distros are patching them anyway, so this might allow us to > provide mostly ready to use config files.

[openstack-dev] [sahara] team meeting April 3 1800 UTC [savanna]

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#Agenda_for_April.2C_3 http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140403T18 -- Sincerely yours, Sergey

Re: [openstack-dev] [tempest][scenario] independece test between Stack and backing services?

On Wed 02 Apr 2014 03:38:18 PM CEST, Sean Dague wrote: Good stuff. I like the semantics of what the destroy stack tests look like, very clean. I still think there would be value in doing this as a API service, which would let you decouple the test cases (and even put them in Tempest), as the t

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

I understand, and appreciate, the concern for licensing, but it would be a real shame to discount some of the most widely used linters because of a clause that prevents us from being evil. Any chance we could run this by legal-disc...@lists.openstack.org and hear their reactions before we axe the

Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API

On Wed, Apr 2, 2014 at 8:43 AM, Russell Bryant wrote: > On 04/02/2014 09:20 AM, Dolph Mathews wrote: > > > > On Tue, Apr 1, 2014 at 7:40 PM, Anne Gentle > > wrote: > > > > > > > > > > On Wed, Mar 26, 2014 at 5:30 AM, Thierry Carrez > > mailto:thie...@openstack.

Re: [openstack-dev] [Ceilometer] Collector no recheck the db status

> I found that when collector service starting, if the db has not yet > ready, it will log an error info like 'Could not load 'database': > could not connect to...' but the service still goes on. Later when > the db is ready, but there are no mechanisms to check the db status > and reconnect it

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

IMHO, having "Example:" on a separate line from the actual option is a lot easier for humans: you just delete a single character or use your editor-of-choice's uncomment macro to activate a line. - Original Message - From: "Russell Bryant" To: openstack-dev@lists.openstack.org Sent: Wed

[openstack-dev] [OSSG][OSSN] Potential token revocation abuse via group membership

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Potential token revocation abuse via group membership - --- ### Summary ### Deletion of groups in Keystone causes token revocation for group members. If group capabilities are delegated to users, they can abuse those capabilities to maliciously revok

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

The patch that enables the new attribute support in dnsmasq still has a lot of work that needs to be done. Once that patch is ready, I suppose we can ask for it to be backported to Icehouse. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-d

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

Awesome guys! I'll do it! I have the "neutron-ipv6.patch" that came from the output of "git format-patch -1 --stdout FETCH_HEAD" but, it did not got applied successfully against "neutron-2014.1.rc1", look: --- builder@neutron-dev-1:~/neutron/neutron-2014.1.rc1$ patch -p1 < ../ipv6-bits/neutron-sh

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

On Wed, Apr 02, 2014 at 11:13:32AM EDT, Martinx - ジェームズ wrote: > Awesome guys! I'll do it! OK - so keep an eye on: https://review.openstack.org/#/c/70649/ Once it is rebased to solve the merge conflicts, and all the tests pass, then perhaps we can look into any of this backporting or PPA busines

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

LOL! AWESOME!! No problem... I know that you guys have a lot to do... :-) But, can this current "neutron-ipv6.patch" at least, be used to enable Neutron IPv6 with RA (--ipv6_ra_mode slaac --ipv6_address_mode slaac) ? Otherwise, is a nutshell, what can be achieved these days with the bleeding ed

[openstack-dev] [Ironic] Icehouse RC1 available

Hello everyone, Ironic published its first Icehouse release candidate yesterday. The list of bugs fixed since feature freeze and the RC1 tarball are available at: https://launchpad.net/ironic/icehouse/icehouse-rc1 Unless release-critical issues are found that warrant a release candidate respin,

Re: [openstack-dev] Documenting FWaaS

Hi Israel, Thanks for taking this up. There is currently an ongoing effort to provide some level of developer documentation within the neutron source tree itself. The patch in review proposes creating placeholders for advanced services, and details for each of the services can be added in follow u

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

On Wed, Apr 02, 2014 at 11:40:39AM EDT, Martinx - ジェームズ wrote: > But, can this current "neutron-ipv6.patch" at least, be used to enable > Neutron IPv6 with RA (--ipv6_ra_mode slaac --ipv6_address_mode slaac) ? No, because even if you solved all the merge conflicts, the tests were not passing in t

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

I think that would be a good idea. We're not shipping this, we're just using it in test (AIUI), so I don't think incompatibility with the OpenStack license is necessarily an issue. But IANAL. :-) -Ben On 04/02/2014 09:24 AM, Kevin Conway wrote: I understand, and appreciate, the concern for

Re: [openstack-dev] [Murano] MuranoPL => UML visualization <- best implementation practices?

So it does, I hadn't realized that. The earlier message mentioned using a command-line tool to produce pretty graph images, and I figured I knew just the tool for the job. Since you're already indirectly using Graphviz, if you're only using PlantUML for processing the output of umlgen.py into a

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

On 04/02/2014 10:10 AM, Russell Bryant wrote: On 04/02/2014 11:01 AM, Solly Ross wrote: IMHO, having "Example:" on a separate line from the actual option is a lot easier for humans: you just delete a single character or use your editor-of-choice's uncomment macro to activate a line. Sure, ag

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

On 04/02/2014 11:01 AM, Solly Ross wrote: > IMHO, having "Example:" on a separate line from the actual option is a lot > easier for humans: > you just delete a single character or use your editor-of-choice's uncomment > macro to activate > a line. Sure, agreed. But in any case, it seems to make

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

I don't see why the license of a piece of software used to check the codebase (i.e. the linter) infects the codebase being checked. That would be like saying the Google terms of service under which I'm writing this email (Google Apps) infects the codebase. -- Kili - Cloud for Africa: kili.io Musi

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

On 04/02/2014 11:01 PM, Solly Ross wrote: > IMHO, having "Example:" on a separate line from the actual option is a lot > easier for humans: > you just delete a single character or use your editor-of-choice's uncomment > macro to activate > a line. Please re-read what I wrote. There's things like

Re: [openstack-dev] [Murano] MuranoPL => UML visualization <- best implementation practices?

On Wed, Apr 2, 2014 at 7:54 PM, Ed Cranford wrote: > Granted, it'll take some work to build a similar visual style--I see > elaborate record nodes in your future--but you don't have to be bound to > PlantUML if you don't want to be. > I've used Graphviz before for a few applications, and if I can

[openstack-dev] [Nova] icehouse-rc1 libvirt broken - VIR_DOMAIN_START_PAUSED

I tried icehouse-rc1 in my libvirt-Xen environment, and found that instance launches were failing. Some digging determined that it was caused by use of the libvirt VIR_DOMAIN_START_PAUSED flag, which is not supported with Xen. I was about to report this when Google found: https://bugs.launchpad.ne

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

Okay, cool! I'll... Tks! On 2 April 2014 12:49, Collins, Sean wrote: > On Wed, Apr 02, 2014 at 11:40:39AM EDT, Martinx - ジェームズ wrote: > > But, can this current "neutron-ipv6.patch" at least, be used to enable > > Neutron IPv6 with RA (--ipv6_ra_mode slaac --ipv6_address_mode slaac) ? > > No, bec

Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API

I’ve added the depreciation process to the section on meet the PTLs/TC for the Atlanta Ops unconference (https://etherpad.openstack.org/p/ATL-ops-unconference-RFC). Currently, it is difficult to tell how much a particular feature is being used and the impact of depreciation. Tim Sessions are

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

I agree - it's not a viral license, and we're not shipping it anyway. I'm going to go back to the original thing: " Recently we have been discussing the topic of Javascript linters for Horizon and Tuskar-UI with Radomir, and he told me that JSLint and JSHint can not be integrated into the test

Re: [openstack-dev] Missleading and hardly parseable default neutron config files

On 04/02/2014 06:38 PM, Salvatore Orlando wrote: > Hi Thomas, > > it probably won't be a bad idea if you can share the patches you're > applying to the default configuration files. > I think all distros are patching them anyway, so this might allow us to > provide mostly ready to use config files.

Re: [openstack-dev] [Nova] icehouse-rc1 libvirt broken - VIR_DOMAIN_START_PAUSED

On 04/02/2014 12:37 PM, iain macdonnell wrote: > I tried icehouse-rc1 in my libvirt-Xen environment, and found that > instance launches were failing. Some digging determined that it was > caused by use of the libvirt VIR_DOMAIN_START_PAUSED flag, which is > not supported with Xen. I was about to re

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

On my phone so I can't follow this up more now, but it looks like JSHint is already used. https://review.openstack.org/#/c/41087/___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openst

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

On 04/02/2014 07:36 PM, Dougal Matthews wrote: On my phone so I can't follow this up more now, but it looks like JSHint is already used. https://review.openstack.org/#/c/41087/ That commit has since been reverted and JSHint removed from Horizon codebase: https://bugs.launchpad.net/horiz

Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API

On Wed, 2014-04-02 at 17:08 +, Tim Bell wrote: > I’ve added the depreciation process to the section on meet the PTLs/TC > for the Atlanta Ops unconference > (https://etherpad.openstack.org/p/ATL-ops-unconference-RFC). > Currently, it is difficult to tell how much a particular feature is > being

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

On 04/02/2014 11:05 AM, Ana Krivokapic wrote: On 04/02/2014 07:36 PM, Dougal Matthews wrote: On my phone so I can't follow this up more now, but it looks like JSHint is already used. https://review.openstack.org/#/c/41087/ That commit has since been reverted and JSHint removed from Horizon

[openstack-dev] Support for multiple sort keys and sort directions in REST GET APIs

I have proposed blueprints in both nova and cinder for supporting multiple sort keys and sort directions for the GET APIs (servers and volumes). I am trying to get feedback from other projects in order to have a more uniform API across services. Problem description from nova proposal: "There i

Re: [openstack-dev] [sahara] team meeting April 3 1800 UTC [savanna]

Hi, I'm wondering if you have plans to use Murano for a cluster management? Thanks, Dmitry On Wed, Apr 2, 2014 at 4:48 PM, Sergey Lukjanov wrote: > Hi folks, > > We'll be having the Sahara team meeting as usual in > #openstack-meeting-alt channel. > > Agenda: > https://wiki.openstack.org/wiki/Me

[openstack-dev] Summit session for config validation and diagnostic

Hello, OpenStack developers Everyone knows that finding out the root cause of some failure in OpenStack with many projects interacting with each other and external components could be serious challenge even for seasoned stacker. I've seen more than one attempt to attack this task since I joined th

Re: [openstack-dev] [Neutron][ML2][Ml2Plugin] Setting _original_network in NetworkContext:

On Fri, Mar 28, 2014 at 6:44 PM, Nader Lahouti wrote: > Hi Mathieu, > > Thanks a lot for your reply. > > Even in the neutron/neutron/db/db_base_plugin_v2.py: create_network() > passes network object: > > 911 > >

Re: [openstack-dev] Summit session for config validation and diagnostic

Oleg, Seems like very interesting topic. Especially I am interested in how could be this integrated with production clouds (could it be run on controllers?). What API it present and is there integration with horizon? Best regards, Boris Pavlovic On Wed, Apr 2, 2014 at 11:20 PM, Oleg Gelbukh

[openstack-dev] [QA] Meeting Thursday April 3rd at 22:00UTC

Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, April 3rd at 22: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 item to t

Re: [openstack-dev] [Neutron LBaaS] Need help with LBaaS drivers

Hi VijayV, Oleg! Thanks for the pointers! It turns out I had to put in an __init__.py in the dummy/ directory, else the driver wouldn't get loaded. Now I see newer issues, and am trying to fix those. I'll ping back on how that goes and if I have any questions.. Cheers! Regards, Vijay On Wed, Ap

[openstack-dev] [heat] metadata for a HOT

I would like to suggest that a metadata section be allowed at the top level of a HOT. Note that while resources in a stack can have metadata, there is no way to put metadata on a stack itself. What do you think? Thanks, Mike___ OpenStack-dev mailing

[openstack-dev] [ceilometer] PTL candidacy

hi, i'd like to announce my candidacy for PTL of Ceilometer. as a little background, i've been a contributor to OpenStack for the past year and a half and have been primarily focused on Ceilometer for the past two cycles where i've been a core contributor. i contribute regularly to the project

Re: [openstack-dev] [heat] metadata for a HOT

On 02/04/14 16:45, Mike Spreitzer wrote: I would like to suggest that a metadata section be allowed at the top level of a HOT. Note that while resources in a stack can have metadata, there is no way to put metadata on a stack itself. What do you think? I think that if you're going to propose

[openstack-dev] [Heat] [Murano] [Solum] applications in the cloud

This is a continuation of the "MuranoPL questions" thread. As a result of ongoing discussions, we figured out that definition of layers which each project operates on and has responsibility for is not yet agreed and discussed between projects and teams (Heat, Murano, Solum (in alphabetical order))

Re: [openstack-dev] [ceilometer] PTL candidacy

confirmed On 04/02/2014 04:47 PM, Gordon Chung wrote: > hi, > > i'd like to announce my candidacy for PTL of Ceilometer. > > as a little background, i've been a contributor to OpenStack for the past > year and a half and have been primarily focused on Ceilometer for the past > two cycles where

[openstack-dev] [TripleO] PTL Candidacy

I'm running for TripleO PTL again! Over the last 6 months TripleO has come a long way in the last 6 months: - CI on all changes (not yet gating) - Persistent storage on nodes - a significantly increased community I've been thrilled to see our progress - and the more time we spend running runni

Re: [openstack-dev] [Heat] [Murano] [Solum] applications in the cloud

Excerpts from Ruslan Kamaldinov's message of 2014-04-02 14:39:17 -0700: > This is a continuation of the "MuranoPL questions" thread. > > As a result of ongoing discussions, we figured out that definition of layers > which each project operates on and has responsibility for is not yet agreed > and

Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases. Data from Operators needed.

Thanks Eugene, I added our data onto the requirements page since I was hoping to prioritize requirements based on the operator data that gets provided. We can move it over to the other page if you think that makes sense. See everyone on the weekly meeting tomorrow! Cheers, --Jorge From: Susan

[openstack-dev] [Glance] PTL candidacy

Hi all, I'd like to submit myself as a candidate to continue in the role of Glance PTL for the Juno release cycle. A bit of history about me: I joined Rackspace's Team Titan back in February 2011, where were initially focused on filling out the OpenStack 1.1 api for nova. I've been working with G

Re: [openstack-dev] [TripleO] PTL Candidacy

confirmed On 04/02/2014 06:23 PM, Robert Collins wrote: > I'm running for TripleO PTL again! > > Over the last 6 months TripleO has come a long way in the last 6 months: > - CI on all changes (not yet gating) > - Persistent storage on nodes > - a significantly increased community > > I've bee

Re: [openstack-dev] [Glance] PTL candidacy

confirmed On 04/02/2014 06:51 PM, Mark Washenberger wrote: > Hi all, > > I'd like to submit myself as a candidate to continue in the role of Glance > PTL for the Juno release cycle. > > A bit of history about me: I joined Rackspace's Team Titan back in February > 2011, where were initially focus

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

+1 on talking to lawyers. Some more context: JSHint is a fork of JSLint, from which the problem license originates. The team has made a significant effort to strip out and replace JSLint code, however there remains one file which they haven’t tackled yet. There’s a large discussion here, incl

Re: [openstack-dev] [Keystone] python-keystoneclient v3 functionality

- Original Message - > From: "Adam Young" > To: openstack-dev@lists.openstack.org > Sent: Wednesday, 2 April, 2014 11:13:22 PM > Subject: Re: [openstack-dev] [Keystone] python-keystoneclient v3 > functionality > > On 04/01/2014 07:36 AM, Yaguang Tang wrote: > > > > Thanks Jamie

Re: [openstack-dev] [ceilometer] PTL candidacy

On 04/02/2014 05:47 PM, Gordon Chung wrote: > I'd like to announce my candidacy for PTL of Ceilometer. Woot! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Heat] [Murano] [Solum] applications in the cloud

On 03/04/14 10:39, Ruslan Kamaldinov wrote: > This is a continuation of the "MuranoPL questions" thread. > > As a result of ongoing discussions, we figured out that definition of layers > which each project operates on and has responsibility for is not yet agreed > and discussed between projects an

[openstack-dev] [Mistral] Next crack at real workflows

Two more workflows drafted - cloud cron, and lifecycle, version 1. The mindset questions are: 1) is DSL syntax expressive, and capable and convenient to handle real use cases? 2) most importantly: what are the implied workflow capabilities which make it all work? * Take a look here: https:

Re: [openstack-dev] [Heat] [Murano] [Solum] applications in the cloud

Hi Steve, I think this is exactly the place where we have a boundary between Murano catalog and HOT. In your example one can use abstract resource type and specify a correct implementation via environment file. This is how it will be done on the final stage in Murano too. Murano will solve anoth

Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases. Data from Operators needed.

Hi y'all-- Looking at the data in the page already, it looks more like a feature wishlist than actual usage data. I thought we agreed to provide data based on percentage usage of a given feature, the end result of the data collection being that it would become more obvious which features are the m

Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases. Data from Operators needed.

More additions to the use cases ( https://wiki.openstack.org/wiki/Neutron/LBaaS/Usecases). I have updated some of the features we are interested in. Thanks, Prashanth On Wed, Apr 2, 2014 at 8:12 PM, Stephen Balukoff wrote: > Hi y'all-- > > Looking at the data in the page already, it looks mo

[openstack-dev] [Oslo][Nova][Heat] Sample config generator issue

We have an issue in Heat where the sample config generator from Oslo is currently broken (see bug #1288586). Unfortunately it turns out that there is no fix to the generator script itself that can do the Right Thing for both Heat and Nova. A brief recap on how the sample config generator works

Re: [openstack-dev] [Openstack] [NOVA] Missing network info in nova list

Hi Slawek, Interesting, I haven't seen this issue of network info not showing up on nova list and the instance being in ACTIVE state. Could you check out the nova logs and see if there are any TRACE's there? If you're using icehouse you should be able to do neutron port-update that maps to the i

Re: [openstack-dev] [neutron]Success to create securitygroup with invalid tenant_id. Does it need to check the tenant_id?

Hi Lee, No, currently only an admin user can create something with a different tenant_id by default. The issue with validating the tenant_id is we need to involve keystone in order to check if the tenant_id is valid (which will cause things to slow down). I believe this question has already come u

[openstack-dev] [ceilometer] Serveral questions about alarm function of ceilometer

Hi I have a requirement of monitoring VMs, if a VM's meter like cpu_util become too high, then system generate an alarm for this VM with meter information. I have tested alarm function of ceilometer, below are commands I used to create alarm object with meter and resource id or not: ceilometer

[openstack-dev] [Cinder]a question about os-volume_upload_image

Hi, When I use an image to create a cinder volume, I found image's metadata is saved into DB table "volume_glance_metadata". But when I use " os-volume_upload_image" to create image from cinder volume, the metadata in "volume_glance_metadata" is not setted back to the newly created image. I ca

[openstack-dev] [Tempest][Nova] Can we remove XML tests of Nova v2 API from Tempest?

Hi, The XML support of Nova v2 API is marked as deprecated, and the message is 'XML support has been deprecated and will be removed in the Juno release.' with https://review.openstack.org/#/c/75439 Now we are in Juno cycle, so can we remove these tests from Tempest? If doing it, the gate testing

Re: [openstack-dev] [heat] Standing down as PTL

Let's vote for the K, L, M release names now. :) Thanks, Steve. On Mon, Mar 31, 2014 at 11:22:49AM +1300, Steve Baker wrote: > I don't intend to run for PTL for the Juno cycle; thankfully there are > many Heat developers who would do a great job. > > Hopefully this wasn't a one-off though. I m

Re: [openstack-dev] [Keystone] python-keystoneclient v3 functionality

2014-04-03 7:12 GMT+08:00 Jamie Lennox : > > > - Original Message - > > From: "Adam Young" > > To: openstack-dev@lists.openstack.org > > Sent: Wednesday, 2 April, 2014 11:13:22 PM > > Subject: Re: [openstack-dev] [Keystone] python-keystoneclient v3 > functionality > > > > On 04/01/2014 0

Re: [openstack-dev] [heat] metadata for a HOT

Is there any relevant wiki or specification doc? 2014-04-03 4:45 GMT+08:00 Mike Spreitzer : > I would like to suggest that a metadata section be allowed at the top > level of a HOT. Note that while resources in a stack can have metadata, > there is no way to put metadata on a stack itself. Wha

  1   2   >