Re: [openstack-dev] [cinder][qa] release notes for cinder v1 to v2?

So the grizzly API releases notes are dead on. (I put them together and have worked with both API's ;) ) Unfortunately, a lot of the features in v2 got back ported to v1. The main differences are in the upgrade notes. -Mike Perez On Mon, Dec 16, 2013 at 9:57 PM, Zhi Kun Liu wrote: > It seems

Re: [openstack-dev] [cinder] weekly meeting

I agree with Qin here that alternating might be a good option. I'm not opposed to being present to both meetings though. -Mike Perez On Mon, Dec 16, 2013 at 9:31 PM, Qin Zhao wrote: > Hi John, > > Yes, alternating the time for each week should be fine. I just change my > gmail name to English

Re: [openstack-dev] [oslo][glance] Oslo.cfg resets not really resetting the CONF

On Tue, 2013-12-17 at 11:17 +0530, Amala Basha Alungal wrote: > Hi Mark, Ben > > > The reset() method in turn calls the clear() method which does an > unregister_opt(). However the unregister_opt only unregisters the > config_opts. The entire set of options inside _opts remain as is. > We've file

Re: [openstack-dev] [cinder][qa] release notes for cinder v1 to v2?

It seems that there's no document about the change from v1 to v2. Maybe the change is very small. Only found some info in OpenStack release notes. Cinder API v2 - List volumes/snapshots summary actually is a summary view. In v1 it was the same as detail view. - List volumes/snapshots de

Re: [openstack-dev] [oslo][glance] Oslo.cfg resets not really resetting the CONF

Hi Mark, Ben The reset() method in turn calls the *clear()* method which does an *unregister_opt()*. However the unregister_opt only unregisters the *config_opts*. The entire set of options inside *_opts* remain as is. We've filed a bug on the oslo en

Re: [openstack-dev] [cinder] weekly meeting

Hi John, Yes, alternating the time for each week should be fine. I just change my gmail name to English... I think you can see my name now... On Tue, Dec 17, 2013 at 12:05 PM, John Griffith wrote: > On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 wrote: > > Hi John, > > > > I think the current meeting s

[openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

Added openstack-dev On Mon, Dec 16, 2013 at 11:34:05PM +0100, Erik Moe wrote: > Hi, > > I have added a new document to the launchpad. Document should now be more > in line with what we discussed at the Icehouse summit. > > https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms > > Doc:

Re: [openstack-dev] [Openstack][Heat] Creating an Openstack project using Heat

Thanks Steve. Regards, Sayaji On Mon, Dec 16, 2013 at 2:57 PM, Steve Baker wrote: > On 12/17/2013 09:57 AM, Sayaji Patil wrote: > > Hi, > > I have installed Openstack with heat using packstack. One thing I > > noticed > > is that the "Orchestration Heat" option is only available inside a >

Re: [openstack-dev] [cinder] weekly meeting

Hello John, 04:00 or 05:00 UTC works for me too. On Tue, Dec 17, 2013 at 12:05 PM, John Griffith wrote: > On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 wrote: >> Hi John, >> >> I think the current meeting schedule, UTC 16:00, basically works for China >> TZ (12AM), although it is not perfect. If we need

[openstack-dev] Scheduler sub-group agenda 12/17

1) Memcached based scheduler updates 2) Scheduler code forklift 3) Instance groups -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http:/

Re: [openstack-dev] [cinder] weekly meeting

On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 wrote: > Hi John, > > I think the current meeting schedule, UTC 16:00, basically works for China > TZ (12AM), although it is not perfect. If we need to reschedule, I think UTC > 05:00 is better than UTC 04:00, since UTC 04:00 (China 12PM) is our lunch > time. >

Re: [openstack-dev] [cinder] weekly meeting

Hi John, I think the current meeting schedule, UTC 16:00, basically works for China TZ (12AM), although it is not perfect. If we need to reschedule, I think UTC 05:00 is better than UTC 04:00, since UTC 04:00 (China 12PM) is our lunch time. On Tue, Dec 17, 2013 at 11:04 AM, John Griffith wrote:

Re: [openstack-dev] [cinder] weekly meeting

04:00 or 05:00 UTC works for me. On Tue, Dec 17, 2013 at 11:04 AM, John Griffith wrote: > Hi All, > > Prompted by a recent suggestion from Tom Fifield, I thought I'd gauge > some interest in either changing the weekly Cinder meeting time, or > proposing a second meeting to accomodate folks in oth

[openstack-dev] [cinder] weekly meeting

Hi All, Prompted by a recent suggestion from Tom Fifield, I thought I'd gauge some interest in either changing the weekly Cinder meeting time, or proposing a second meeting to accomodate folks in other time-zones. A large number of folks are already in time-zones that are not "friendly" to our cu

Re: [openstack-dev] Project-Scoped Service Catalog Entries

On 12/16/2013 08:39 PM, Adam Young wrote: See the endpoint filtering blueprint from the Havana release as a starting point. I think the difference between that and what you have here is that these endpoints should only show up in a subset of the service catalogs returned? https://github.com/op

Re: [openstack-dev] Project-Scoped Service Catalog Entries

On 12/16/2013 08:39 PM, Adam Young wrote: On 12/16/2013 02:57 PM, Gabriel Hurley wrote: I've run into a use case that doesn't currently seem to have a great solution: Let's say my users want to use a "top-of-stack" OpenStack project such as Heat, Trove, etc. that I don't currently support in m

Re: [openstack-dev] Multidomain User Ids

On 12/04/2013 12:35 PM, Henry Nash wrote: On 4 Dec 2013, at 13:28, Dolph Mathews > wrote: On Sun, Nov 24, 2013 at 9:39 PM, Adam Young > wrote: The #1 pain point I hear from people in the field is that they need to consume re

Re: [openstack-dev] Project-Scoped Service Catalog Entries

On 12/16/2013 02:57 PM, Gabriel Hurley wrote: I've run into a use case that doesn't currently seem to have a great solution: Let's say my users want to use a "top-of-stack" OpenStack project such as Heat, Trove, etc. that I don't currently support in my deployment. There's absolutely no reason

Re: [openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

Hi! Actually, I have already filed cancel of LiveMigration with using taskflow [0]. But my approach to blueprint was not so good at that time. So, I rewrote this blueprint from also point of russelb. I want to repush and wanted to approved. If you have any suggestions, ideas etc... I appreciate i

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Dec 13, 2013, at 8:06 PM, Isaku Yamahata wrote: > On Fri, Dec 06, 2013 at 04:30:17PM +0900, > Maru Newby wrote: > >> >> On Dec 5, 2013, at 5:21 PM, Isaku Yamahata wrote: >> >>> On Wed, Dec 04, 2013 at 12:37:19PM +0900, >>> Maru Newby wrote: >>> In the current architecture, the Neu

Re: [openstack-dev] [qa][ceilometer] Who can be a asked to help review tempest tests?

On 12/16/2013 05:50 PM, Doug Hellmann wrote: It might be good, to start out, if we all look at them. That way we can all learn a bit about tempest, too. If you add "ceilometer-core" as a reviewer gerrit will expand the group name. Doug Thanks, Doug. That makes sense. The only reason I asked t

[openstack-dev] [Neutron] Enable to set DHCP port attributes

Hi Neutron developers, I submitted the following blue print. https://blueprints.launchpad.net/neutron/+spec/enable-to-set-dhcp-port-attributes It is a proposal to be enable to control dhcp port attributes (especially ip address) by a user. This is based on a real requirement from our customer.

Re: [openstack-dev] [oslo][glance] Oslo.cfg resets not really resetting the CONF

Hi On Fri, 2013-12-13 at 14:14 +0530, Amala Basha Alungal wrote: > Hi, > > > > I stumbled into a situation today where in I had to write few tests that > modifies the oslo.config.cfg and in turn resets the values back in a tear > down. Acc to the docs, oslo.cfg reset() "*Clears the object state

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

Hi Thierry, On Fri, 2013-12-13 at 15:53 +0100, Thierry Carrez wrote: > Hi everyone, > > TL;DR: > Incubation is getting harder, why not ask efforts to apply for a new > program first to get the visibility they need to grow. > > Long version: > > Last cycle we introduced the concept of "Programs"

Re: [openstack-dev] a time-based resource management system

Hi Alan, Looks like an interesting project. Some questions/comments: 1) For resources, are you targeting only VMs, or is the scope going to include other resources as well (swift, load balancers, etc.) 2) Is the scope of reservation limited to time/duration or do you envision the scope t

Re: [openstack-dev] Re-initializing or dynamically configuring cinder driver

Hi, On Sat, 2013-12-14 at 10:23 +0530, iKhan wrote: > Hi All, > > At present cinder driver can be only configured with adding entries in conf > file. Once these driver related entries are modified or added in conf file, > we need to restart cinder-volume service to validate the conf entries and >

Re: [openstack-dev] [Openstack][Heat] Creating an Openstack project using Heat

On 12/17/2013 09:57 AM, Sayaji Patil wrote: > Hi, > I have installed Openstack with heat using packstack. One thing I > noticed > is that the "Orchestration Heat" option is only available inside a > project view. > Is this by design ? > Yes, heat stacks are scoped to a project/tenant. > My use

[openstack-dev] Global Load Balancing

All: I am trying to get a clear understanding of where or if Global Load Balancing as a Service fits within the OpenStack ecosystem. I have included a list of basic use cases that I think a Global Load Balancing service should provide: • Route traffic (HTTP/FTP/Database/etc...) across

Re: [openstack-dev] [qa][ceilometer] Who can be a asked to help review tempest tests?

It might be good, to start out, if we all look at them. That way we can all learn a bit about tempest, too. If you add "ceilometer-core" as a reviewer gerrit will expand the group name. Doug On Mon, Dec 16, 2013 at 5:33 PM, David Kranz wrote: > Ceilometer team, we are reviewing tempest tests a

[openstack-dev] a time-based resource management system

Hi everyone, My name is Alan and I am from the Cyber Security Lab in University of Waikato. We have recently started deploying and using Openstack in our experimental private cloud testbed. The cloud testbed is mainly used in running our research and teaching purposes. However, we notice t

[openstack-dev] [qa][ceilometer] Who can be a asked to help review tempest tests?

Ceilometer team, we are reviewing tempest tests and hope to see more. The tempest review team is hoping to identify some ceilometer devs who could help answer questions or provide a review if needed for ceilometer patches. Since ceilometer is new we are not all familiar with many of the details

[openstack-dev] [savanna][qa] How will tempest tests run?

So it's great to see a submission of savanna tests for tempest. We would like to see these tests run before reviewing them. Is the intent that savanna will be enabled by default in devstack? If not, then I guess there will need to be separate savanna jobs. I see that right now there are savanna

Re: [openstack-dev] Project-Scoped Service Catalog Entries

On 12/16/2013 04:17 PM, Georgy Okrokvertskhov wrote: By they way, there is an initiative to create generic metadata repository based on Glance project. As services endpoints are just URLs they also can be stored in this Glance metadata repository and have all features related to visibility and ac

Re: [openstack-dev] [neutron][policy] Policy-Rules discussions based on Dec.12 network policy meeting

Hi Please see inline On Sun, Dec 15, 2013 at 8:49 AM, Stephen Wong wrote: > Hi, > > During Thursday's group-policy meeting[1], there are several > policy-rules related issues which we agreed should be posted on the > mailing list to gather community comments / consensus. They are: > >

[openstack-dev] [cinder][qa] release notes for cinder v1 to v2?

Sorry for lost subject in last message. Is there a document that describes the api changes from v1 to v2, similar to the one documenting nova v2 to v3? -David ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.o

[openstack-dev] [cinder][qa]

Is there a document that describes the api changes from v1 to v2, similar to the one documenting nova v2 to v3? -David ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack][Heat] Creating an Openstack project using Heat

On 16/12/13 15:57, Sayaji Patil wrote: Hi, I have installed Openstack with heat using packstack. One thing I noticed is that the "Orchestration Heat" option is only available inside a project view. Is this by design ? My use case it to create a project with images, networks,routers and fire

Re: [openstack-dev] Announcing Fuel

On 17 December 2013 09:59, Mike Scherbakov wrote: > Thanks for support, > as a starting point we have chosen Ironic - we really want to see it as a > replacement of Fuel's existing provisioning layer, with an intention of > participation and delivery of many features which we already know from the

Re: [openstack-dev] Project-Scoped Service Catalog Entries

By they way, there is an initiative to create generic metadata repository based on Glance project. As services endpoints are just URLs they also can be stored in this Glance metadata repository and have all features related to visibility and access control provides by this repository. Thanks Georg

Re: [openstack-dev] [Nova][Docker] Environment variables

> eg use a 'env_' prefix for glance image attributes > > We've got a couple of cases now where we want to overrides these > same things on a per-instance basis. Kernel command line args > is one other example. Other hardware overrides like disk/net device > types are another possibility > > Rathe

Re: [openstack-dev] Announcing Fuel

Thanks for support, as a starting point we have chosen Ironic - we really want to see it as a replacement of Fuel's existing provisioning layer, with an intention of participation and delivery of many features which we already know from the real-world installations with Fuel. We are trying to be m

[openstack-dev] [Openstack][Heat] Creating an Openstack project using Heat

Hi, I have installed Openstack with heat using packstack. One thing I noticed is that the "Orchestration Heat" option is only available inside a project view. Is this by design ? My use case it to create a project with images, networks,routers and firewall rules in a single workflow. I looked

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

On Mon, Dec 16, 2013 at 9:49 AM, Thierry Carrez wrote: > Flavio Percoco wrote: > > What I'm arguing here is: > > > > 1. Programs that are not part of OpenStack's release cycle shouldn't > > be considered official nor they should have the rights that integrated > > projects have. > > > > 2. I think

[openstack-dev] [Ceilometer] Complex query BP implementation

Hi guys, The first working version of the Complex filter expressions in API queries blueprint [1] was pushed for review[2]. We implemented a new query REST resource in order to provide rich query functionality for samples, alarms and alarm history. The future plans (in separated blueprints) wi

Re: [openstack-dev] Project-Scoped Service Catalog Entries

+1 There is also the use case where a new service is being introduced for everyone eventually but you wish to start with a few friends. In the event of problems, the effort to tidy up is much less. Documentation can be updated with the production environment. Tim > -Original Message-

[openstack-dev] Project-Scoped Service Catalog Entries

I've run into a use case that doesn't currently seem to have a great solution: Let's say my users want to use a "top-of-stack" OpenStack project such as Heat, Trove, etc. that I don't currently support in my deployment. There's absolutely no reason these services can't live happily in a VM talk

Re: [openstack-dev] [TripleO] UI Wireframes for Resource Management - ready for implementation

On 12/13/2013 01:53 PM, Tzu-Mainn Chen wrote: On 2013/13/12 11:20, Tzu-Mainn Chen wrote: These look good! Quick question - can you explain the purpose of Node Tags? Are they an additional way to filter nodes through nova-scheduler (is that even possible?), or are they there solely for displa

Re: [openstack-dev] [Heat] [Murano] [Solum] [Glance]Metadata repository initiative discussion for Glance

Hi, Doodle shows that the most suitable time is 10AM PST on Tuesday. Lets keep this time for Metadata Repository\Catalog meeting in #openstack-glance IRC channel. See you tomorrow! Thanks Georgy On Fri, Dec 13, 2013 at 12:09 PM, Georgy Okrokvertskhov < gokrokvertsk...@mirantis.com> wrote: > Hi

Re: [openstack-dev] [TripleO] [Horizon] [Tuskar] [UI] Horizon and Tuskar-UI merge

On 12/16/2013 04:22 PM, Jiri Tomasek wrote: > > Thanks for pointing this out, In Horizon you can easily decide which > dashboards to show, so the Infrastructure management Horizon instance > can have Project and Admin dashboards disabled. > > I think there has been discussed that some panels of

Re: [openstack-dev] [Neutron] Does any plugin require hairpinning to be enabled?

Hi, I have registered two blueprints, one in Nova and one in Neutron to make it a VIF attribute that the libvirt driver in Nova will honor. https://blueprints.launchpad.net/neutron/+spec/vif-attribute-for-hairpinning https://blueprints.launchpad.net/nova/+spec/nova-hairpin-vif-attribute -- Sea

Re: [openstack-dev] [nova][db] Thoughts on making instances.uuid non-nullable?

On 12/16/2013 11:59 AM, Russell Bryant wrote: On 12/16/2013 11:45 AM, Matt Riedemann wrote: 1. Add a migration to change instances.uuid to non-nullable. Besides the obvious con of having yet another migration script, this seems the most straight-forward. The instance object class already defines

Re: [openstack-dev] Unified Guest Agent proposal

On 12/16/2013 10:29 AM, Fox, Kevin M wrote: Yeah, this is similar to what I am proposing. I think we just about have just about everything we need already. Thread started out discussing a slightly different use case then below. The use case is processing events like: User performs "backup data

Re: [openstack-dev] [Nova][VMware] Deploy from vCenter template

IIRC someone who shows up at https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Meetings is planning on working on that again for Icehouse-3 but there's some new debate on the best way to implement the desired effect. The goal of that change would be to avoid streaming the disk image out of vCenter

[openstack-dev] [marconi] Meeting agenda for tomorrow at 1500 UTC

The Marconi project team holds a weekly meeting in #openstack-meeting-alt on Tuesdays, 1500 UTC. The next meeting is Tomorrow, Dec. 10. Everyone is welcome, but please take a minute to review the wiki before attending for

Re: [openstack-dev] Unified Guest Agent proposal

Yeah, this is similar to what I am proposing. I think we just about have just about everything we need already. Thread started out discussing a slightly different use case then below. The use case is processing events like: User performs "backup database B" in Trove UI, Trove sends event "backu

Re: [openstack-dev] Unified Guest Agent proposal

The idea being discussed is using 169.254.169.254 for long term messaging between a vm and some other process. For example, Trove -> TroveVM. I guess this thread is getting too long. The details are getting lost. Thanks, Kevin From: Lars Kellogg-Stedman

Re: [openstack-dev] [oslo]: implementing olso.messaging over amqp 1.0

On 12/16/2013 10:37 AM, Gordon Sim wrote: On 12/12/2013 02:14 PM, Flavio Percoco wrote: I've a draft in my head of how the amqp 1.0 driver could be implemented and how to map the current expectations of the messaging layer to the new protocol. I think a separate thread to discuss this mapping i

[openstack-dev] [Mistral] Community meeting minutes - 12/16/2013

Hello, Thanks for joining us today in IRC, here are the links to meeting minutes and logs: Minutes: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-16-16.00.html Logs: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-16-16.00.log.html Join us next time

Re: [openstack-dev] [nova][db] Thoughts on making instances.uuid non-nullable?

On 12/16/2013 11:45 AM, Matt Riedemann wrote: > 1. Add a migration to change instances.uuid to non-nullable. Besides the > obvious con of having yet another migration script, this seems the most > straight-forward. The instance object class already defines the uuid > field as non-nullable, so it's

Re: [openstack-dev] [nova][db] Thoughts on making instances.uuid non-nullable?

+1 on a migration to make uuid a non-nullable column. I advocated a few patches back in Havana that make assumptions based on the UUID being present and unique per instance. If it gets nulled the VMware drivers will have have breakage and I have no idea how to avoid that reasonably without the UUID

Re: [openstack-dev] Re-initializing or dynamically configuring cinder driver

Ah, u might be able to do what u said. Try it out and see how far u can get :) I would be interested to know how u plan on waiting for all existing operations to finish. Maybe it's not so hard, not really sure... Sent from my really tiny device... On Dec 15, 2013, at 9:43 PM, "iKhan" mailto:ik

[openstack-dev] [nova][db] Thoughts on making instances.uuid non-nullable?

I've got a blueprint [1] scheduled for icehouse-3 to add DB2 support to Nova. That's blocked by a patch working it's way through sqlalchemy-migrate to add DB2 support [2] there. I've held off pushing any nova patches up until the sqlalchemy-migrate DB2 support is merged (which is also blocked

[openstack-dev] [infra] Meeting Tuesday December 17th at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday December 17th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in in

Re: [openstack-dev] Unified Guest Agent proposal

On Fri, Dec 13, 2013 at 11:32:01AM -0800, Fox, Kevin M wrote: > I hadn't thought about that use case, but that does sound like it > would be a problem. That, at least, is not much of a problem, because you can block access to the metadata via a blackhole route or similar after you complete your in

Re: [openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

could we use Taskflow to manage task state and resource for this kind of tasks in Nova? Cinder has been an pilot to use Taskflow for volume backup tasks. anyone interested in this suggestion or has done some research to improve the live migration workflow?

Re: [openstack-dev] [Ceilometer] Nomination of Sandy Walsh to core team

+1. Sandy has been both helpful and insightful, plus he happens to have a good handle on the many moving parts that make up this project. :-) -Phil > -Original Message- > From: Lu, Lianhao [mailto:lianhao...@intel.com] > Sent: Sunday, December 15, 2013 5:29 PM > To: OpenStack Development

Re: [openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

I would block it in the API or have the API cancelling the migration first. I don't see a reason why to start an operation that is meant to fail, which also has a complex chain of event, following it failure. Regardless of the above, I think that the suggested exception handling is needed in an

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On 12/16/13 5:25 PM, "Daniel P. Berrange" wrote: >On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote: >> Hi, >> At the moment the administrator is able to retrieve diagnostics for a >>running VM. Currently the implementation is very loosely defined, that >>is, each driver returns whate

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote: > On 16 December 2013 15:25, Daniel P. Berrange wrote: > > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote: > >> I'd like to propose the following for the V3 API (we will not touch V2 > >> in case operators have applications

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On 13/12/13 19:06 +1300, Robert Collins wrote: On 13 December 2013 06:24, Will Foster wrote: I just wanted to add a few thoughts: Thank you! For some comparative information here "from the field" I work extensively on deployments of large OpenStack implementations, most recently with a ~22

Re: [openstack-dev] [Nova][Docker] Environment variables

On 12/16/2013 10:39 AM, Daniel P. Berrange wrote: > On Mon, Dec 16, 2013 at 04:18:52PM +0100, Daniel Kuffner wrote: >> Hi Russell, >> >> You actually propose to extend the whole nova stack to support >> environment variables. Would any other driver benefit from this API >> extension? >> >> Is that

Re: [openstack-dev] [Nova][Docker] Environment variables

On Mon, Dec 16, 2013 at 04:18:52PM +0100, Daniel Kuffner wrote: > Hi Russell, > > You actually propose to extend the whole nova stack to support > environment variables. Would any other driver benefit from this API > extension? > > Is that what you imagine? > nova --env SQL_URL=postgres://user:pa

Re: [openstack-dev] [Nova][Docker] Environment variables

On 12/16/2013 10:18 AM, Daniel Kuffner wrote: > Hi Russell, > > You actually propose to extend the whole nova stack to support > environment variables. Would any other driver benefit from this API > extension? > > Is that what you imagine? > nova --env SQL_URL=postgres://user:password --image ...

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On 16 December 2013 15:25, Daniel P. Berrange wrote: > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote: >> Hi, >> At the moment the administrator is able to retrieve diagnostics for a >> running VM. Currently the implementation is very loosely defined, that is, >> each driver returns

Re: [openstack-dev] [Nova][Docker] Environment variables

That would be great, I have also a couple of change request waiting for approval. Would be good to know if it has any relevance in the future. https://review.openstack.org/#/c/59824/ https://review.openstack.org/#/c/62182/ https://review.openstack.org/#/c/62183/ https://review.openstack.org/#/c/62

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote: > Hi, > At the moment the administrator is able to retrieve diagnostics for a running > VM. Currently the implementation is very loosely defined, that is, each > driver returns whatever they have to return. This is problematic in a numb

[openstack-dev] [Solum] Third working group meeting on language packs today

Hi, We will hold our third Git Integration working group meeting on IRC in #solum on Monday, December 16, 2013 1700 UTC / 0900 PST. Previous meeting notes are here [4] Agenda for today's meeting: * Administrative: * Topics: * Discuss lang-pack-examples spec for

Re: [openstack-dev] [TripleO] [Horizon] [Tuskar] [UI] Horizon and Tuskar-UI merge

On 12/16/2013 03:32 PM, Jaromir Coufal wrote: On 2013/16/12 14:03, Matthias Runge wrote: On 12/13/2013 03:08 PM, Ladislav Smola wrote: Horizoners, As discussed in TripleO and Horizon meetings, we are proposing to move Tuskar UI under the Horizon umbrella. Since we are building our UI solution

Re: [openstack-dev] [Nova][Docker] Environment variables

Hi Chuck, yes please, I'm eager to see what you have. :) Daniel On Mon, Dec 16, 2013 at 4:12 PM, Chuck Short wrote: > Hi Russel, > > I have something that is pushing it for to stay in nova (at least the > compute drivers). I should have a gerrit branch for people to review soon. > > Regards > c

Re: [openstack-dev] [Nova][Docker] Environment variables

Hi Russell, You actually propose to extend the whole nova stack to support environment variables. Would any other driver benefit from this API extension? Is that what you imagine? nova --env SQL_URL=postgres://user:password --image Regarding the discussion you mentioned. Are there any publi

Re: [openstack-dev] [Nova][Docker] Environment variables

On 12/16/2013 10:12 AM, Chuck Short wrote: > I have something that is pushing it for to stay in nova (at least the > compute drivers). I should have a gerrit branch for people to review soon. OK. Do you have any design notes for whatever you're proposing? That would probably be easier to review

Re: [openstack-dev] [nova] time for a new major network rpc api version?

On 12/15/2013 05:12 PM, Robert Collins wrote: > That said, doing anything to the network RPC API seems premature until > the Neutron question is resolved. This. I've been pretty much ignoring this API since it has been frozen and "almost deprecated" for a long time. My plan was to revisit the st

Re: [openstack-dev] [Nova][Docker] Environment variables

Hi Russel, I have something that is pushing it for to stay in nova (at least the compute drivers). I should have a gerrit branch for people to review soon. Regards chuck On Mon, Dec 16, 2013 at 10:07 AM, Russell Bryant wrote: > On 12/16/2013 09:27 AM, Daniel Kuffner wrote: > > Hi All, > > > >

Re: [openstack-dev] [Nova][Docker] Environment variables

On 12/16/2013 09:27 AM, Daniel Kuffner wrote: > Hi All, > > I have submitted a new blueprint which addresses the a common pattern > in the docker world. A usual pattern in the docker world is to use > environment variables to configure a container. > > docker run -e "SQL_URL=postgres://user:passw

Re: [openstack-dev] [Tempest][Neutron] Network client and API tests refactoring.

Hi Eugene, as you have already noticed there's already some overlap with your work and the current tests development. We should find a productive way to coordinate the efforts. Thanks for starting the refactoring, in my opinion it's needed. cheers, Rossella On Sat, Dec 14, 2013 at 4:53 PM, Jay

[openstack-dev] [nova] VM diagnostics - V3 proposal

Hi, At the moment the administrator is able to retrieve diagnostics for a running VM. Currently the implementation is very loosely defined, that is, each driver returns whatever they have to return. This is problematic in a number of respects: 1. The tempest tests were written specifically fo

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

Flavio Percoco wrote: > What I'm arguing here is: > > 1. Programs that are not part of OpenStack's release cycle shouldn't > be considered official nor they should have the rights that integrated > projects have. > > 2. I think requesting Programs to exist at the early stages of the > project is

Re: [openstack-dev] [TripleO] [Horizon] [Tuskar] [UI] Horizon and Tuskar-UI merge

On 2013/16/12 14:03, Matthias Runge wrote: On 12/13/2013 03:08 PM, Ladislav Smola wrote: Horizoners, As discussed in TripleO and Horizon meetings, we are proposing to move Tuskar UI under the Horizon umbrella. Since we are building our UI solution on top of Horizon, we think this is a good fit.

Re: [openstack-dev] Performance Regression in Neutron/Havana compared to Quantum/Grizzly

Hello Salvatore, I agree with you on we need both items to improve the scaling and performance of neutron server. I am not a developer so can't implement the changes myself. If somebody is going to implement I am more than happy to do the tests. Thanks & Regards, Sreedhar Nathani From: Salva

[openstack-dev] [Nova][Docker] Environment variables

Hi All, I have submitted a new blueprint which addresses the a common pattern in the docker world. A usual pattern in the docker world is to use environment variables to configure a container. docker run -e "SQL_URL=postgres://user:password@/db" my-app The nova docker driver doesn't support to s

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

On 13/12/13 16:37 +0100, Flavio Percoco wrote: On 13/12/13 15:53 +0100, Thierry Carrez wrote: Hi everyone, TL;DR: Incubation is getting harder, why not ask efforts to apply for a new program first to get the visibility they need to grow. Long version: Last cycle we introduced the concept of "

Re: [openstack-dev] [TripleO] [Tuskar] [UI] Icehouse Requirements - Summary, Milestones

On 12/13/2013 05:22 PM, James Slagle wrote: On Fri, Dec 13, 2013 at 03:04:09PM +0100, Imre Farkas wrote: One note to deploy: It's not done only by Heat and Nova. If we expect a fully functional OpenStack installation as a result, we are missing a few steps like creating users, initializing and

Re: [openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

Isn’t just handling the exception instance_not_found enough? By this time source would’ve been cleaned up. Destination VM resources will get cleaned up by the periodic task since the VM is not associated with this host. Am I missing something here? From: 王宏 [mailto:w.wangho...@gmail.com] Sent:

Re: [openstack-dev] [TripleO] [Horizon] [Tuskar] [UI] Horizon and Tuskar-UI merge

On 12/13/2013 03:08 PM, Ladislav Smola wrote: > Horizoners, > > As discussed in TripleO and Horizon meetings, we are proposing to move > Tuskar UI under the Horizon umbrella. Since we are building our UI > solution on top of Horizon, we think this is a good fit. It will allow > us to get feedback

Re: [openstack-dev] Performance Regression in Neutron/Havana compared to Quantum/Grizzly

Multiple RPC servers is something we should definitely look at. I don't see a show-stopper reason for which this would not work, although I recall we found out a few caveats one should be aware of when doing multiple RPC servers when reviewing the patch for multiple API server (I wrote them in some

Re: [openstack-dev] [tuskar] How to install tuskar-ui from packaging point of view

On 12/16/2013 08:52 AM, Stephen Gran wrote: On 16/12/13 03:47, Thomas Goirand wrote: Hi, I've been working over the last 2 months to get Ironic, TripleO and Tuskar ready for an upload in Debian. However, for tuskar-ui, I'm facing the fact that there's a lack of documentation. It was easy to ge

[openstack-dev] [Mistral] Community meeting agenda - 12/16/2013

Hi! This is a reminder that we will have another community meeting today in IRC (#openstack-meeting) at 16.00 UTC. Here’s the agenda: https://wiki.openstack.org/wiki/Meetings/MistralAgenda As usually, you’re welcome to join! Renat Akhmerov @ Mirantis Inc. ___

Re: [openstack-dev] Performance Regression in Neutron/Havana compared to Quantum/Grizzly

Hello Salvatore, Thanks for the updates. All the changes which you talked is from the agent side. >From my tests, with multiple L2 agents running and sending/requesting >messages at the same time from the single neutron rpc server process is not >able to handle All the load fast enough and c

[openstack-dev] [multipath] Could I use the multipath software provided by the SAN vendors instead of dm-multipath in openstack?

Hi,all The storage array used by cinder in my experiment is produced by Huawei. The vendor releases its own multipath named Ultrapath with the SAN. Could I use the Ultrapath instead of dm-multipath in openstack? Best wishes, Qi Qi Xiaozhen CLOUD OS PDU, IT Produc

[openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

Hi all. When I try to fix a bug:https://bugs.launchpad.net/nova/+bug/1242961, I get a trouble. To reproduce the bug is very easy. Live migrate a vm in block_migration mode, and then delelte the vm immediately. The reason of this bug is as follow: 1. Because live migrate costs more time, so the vm

  1   2   >