Re: [openstack-dev] [neutron]Can somebody describe the all the rolls about networks' admin_state_up

- Original Message - > Hi, > > I want to know the admin_state_up attribute about networks but I > have not found any describes. > > Can you help me to understand it? Thank you very much. > There's a discussion about this in this bug [1]. >From what I gather, nobody knows what admi

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On Fri, Feb 21, 2014 at 10:24:24AM +0100, Tomas Sedovic wrote: > On 20/02/14 16:24, Imre Farkas wrote: > > On 02/20/2014 03:57 PM, Tomas Sedovic wrote: > >> On 20/02/14 15:41, Radomir Dopieralski wrote: > >>> On 20/02/14 15:00, Tomas Sedovic wrote: > >>> > Are we even sure we need to store the

Re: [openstack-dev] [Neutron]Do you think tanent_id should be verified

I think 'tenant_id' should always be validated when creating neutron resources, whether or not Neutron can handle the notifications from Keystone when tenant is deleted. thoughts? 2014-02-20 20:21 GMT+08:00 Dong Liu : > Dolph, thanks for the information you provided. > > Now I have two question

Re: [openstack-dev] [neutron]Can somebody describe the all the rolls about networks' admin_state_up

Hi Lee, Here is a discussion maybe help: https://answers.launchpad.net/neutron/+question/230508 Damon 2014-02-24 16:03 GMT+08:00 Assaf Muller : > > > - Original Message - > > Hi, > > > > I want to know the admin_state_up attribute about networks but I > > have not found any describ

Re: [openstack-dev] [neutron]Can somebody describe the all the rolls about networks' admin_state_up

Thanks you very much. "IMHO when admin_state_up is false that entity should be down, meaning network should be down. otherwise what it the usage of admin_state_up ? same is true for port admin_state_up" It likes switch's power button? 2014-02-24 16:03 GMT+08:00 Assaf Muller : > > > - Origina

[openstack-dev] [Mistral] Community meeting reminder - 02/24/2014

Hi Mistral team, This is a reminder that we’ll have another IRC community meeting today (#openstack-meeting) at 16.00 UTC. Here’s the agenda: Review action items Discuss current status Continue DSL discussion Open discussion (roadblocks, suggestions, etc.) You can also find the agenda and the l

Re: [openstack-dev] Win 2008 R2 VMDK upload to glance

Hi, Did you install the VMWare tools and sysprepped the image before adding it to Glance? Here's how we automate the creation of Windows OpenStack images for KVM, Hyper-V and VMWare (unattended setup, hypervisor drivers, windows updates, Cloudbase-Init and sysprep): https://github.com/cloudba

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 02/23/2014 01:16 AM, Clint Byrum wrote: Excerpts from Imre Farkas's message of 2014-02-20 15:24:17 +: On 02/20/2014 03:57 PM, Tomas Sedovic wrote: On 20/02/14 15:41, Radomir Dopieralski wrote: On 20/02/14 15:00, Tomas Sedovic wrote: Are we even sure we need to store the passwords in t

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 21/02/14 10:03, Radomir Dopieralski wrote: On 21/02/14 10:38, Dougal Matthews wrote: At the moment we are guessing, we don't even know how many passwords we need to store. So we should progress with the safest and simplest option (which is to not store them) and consider changing this later.

[openstack-dev] [Neutron] "Auto-created ports count against port quota" bug status

Hello all, I have the following bug assigned for icehouse~3 milestone: https://bugs.launchpad.net/neutron/+bug/1212338 I proposed a (maybe too much) trivial solution in the launchpad comments, but I haven't received a confirmation that solution would solve the issue. Could a more experienced

Re: [openstack-dev] [OpenStack-Dev] [Cinder] Cinder driver verification

Boris Renski wrote: > There are a couple of additional things we are working on driver > verification front that, I believe, it is now time to socialize with the > dev community: > > 1. In addition to the scare tactic of deprecating the code for those > that don't test their drivers, we also want

Re: [openstack-dev] [Murano] Need a new DSL for Murano

I think this is the great new service which will accompany OpenStack Solum similarly as Bosh is accompanying Cloud Foundry and CloudForms is accompanying OpenShift. I wouldn't call it the Application Catalog but the Service Catalog, because of the primary focus on the Service Life-cycle management

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 24 Feb 2014 02:06:50 -0500 Jay Pipes wrote: > On Mon, 2014-02-24 at 17:20 +1030, Christopher Yeoh wrote: > > - Proposed way forward: > > - Release the V3 API in Juno with nova-network and tasks support > > - Feature freeze the V2 API when the V3 API is released > > - Set the timel

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 02/24/2014 09:39 AM, Ladislav Smola wrote: On 02/23/2014 01:16 AM, Clint Byrum wrote: Excerpts from Imre Farkas's message of 2014-02-20 15:24:17 +: On 02/20/2014 03:57 PM, Tomas Sedovic wrote: On 20/02/14 15:41, Radomir Dopieralski wrote: On 20/02/14 15:00, Tomas Sedovic wrote: Are w

Re: [openstack-dev] [keystone] Notification When Creating/Deleting a Tenant in openstack

Hi Nader, These notifications must be handled by Ceilometer like others [1]. it is surprising that it does not already identity meters indeed... probably nobody needs them before you. I guess it remains to open a BP and code them like I recently did for Heat [2] http://docs.openstack.org/develop

[openstack-dev] [oslo] AMQP 1.0 based messaging driver available for review

I have been working with Ken Giusti on an AMQP 1.0 messaging driver for olso.messaging. The code for this is now available for review at https://review.openstack.org/#/c/75815/ As previously mentioned on this list, this uses the Apache Qpid Proton 'protocol engine' library. This is not a standa

[openstack-dev] [qa] : error during "gate-tempest-dsvm-neutron-large-ops" when attaching floating IP

Hello everyone, I'm currently pushing a stress test in Tempest which at some point tries to attach a floating IP to newly started servers . The change I'm talking about is available here : https://review.openstack.org/#/c/74067/ . This test runs fine on my local devstack, but I have an issue du

Re: [openstack-dev] Incubation Request: Murano

Mark Washenberger wrote: > Prior to this email, I was imagining that we would expand the Images > program to go beyond storing just block device images, and into more > structured items like whole Nova instance templates, Heat templates, and > Murano packages. In this scheme, Glance would know ever

Re: [openstack-dev] [Murano] Need a new DSL for Murano

Hi Dmitry, I agree with you on this vision, however we have to think more on the terminology: "Service Catalog" in OpenStack relates to Keystone (where by "Service" we mean Openstack's infrastructure-level services). I understand your concerns on "runtime lifecycle" vs "code-to-binary" lifecycle t

Re: [openstack-dev] [qa] [neutron] Neutron Full Parallel job very close to voting - call to arms by neutron team

Ciao Salvatore, thanks a lot for analyzing the failures! This link is not working for me: 7) https://bugs.launchpad.net/neutron/+bug/1253533 I took a minor bug that was not assigned. Most of the bugs are assigned to you, I was wondering if you´d use some help. I guess we can coordinate better

[openstack-dev] [neutron]The mechanism of physical_network & segmentation_id is logical?

Hi stackers, When create a network, if we don't set provider:network_type, provider:physical_network or provider:segmentation_id, the network_type will be from cfg, but the other tow is from db's first record. Code is (physical_network, segmentation_id) = ovs_db_v2.reserve_

[openstack-dev] Missing tests

Hi, I had uploaded to Gerrit the code for Domain Quota Management. One of the test is failing due to the missing tests for the following extensions. Extensions are missing tests: ['os-extended-hypervisors', 'os-extended-services-delete'] What can i do now? (these extensions are not done by me)

[openstack-dev] Unified Guest Agent in Savanna

Hello folks, Not long ago we had a discussion on unified guest agent [1] - a way for performing actions 'inside' VMs. Such thing is needed for PaaS projects for tasks such as application reconfiguration and user requests pass-through. As a proof of concept I've made os_collect_config as a guest a

Re: [openstack-dev] [qa] [neutron] Neutron Full Parallel job very close to voting - call to arms by neutron team

Hi Rossella, I had no idea most of the bugs were assigned to me. I have pushed several patches for bug 1253896 and that's why launchpad is stating I "own" the ticket. But if you find another fault causing that bug, feel free to push a patch for it. I think today I will push only a patch for bug 1

[openstack-dev] [Keystone] Tenant expiration dates

Hi, I’m thinking about creating a blueprint to allow the creating of tenants defining start-date and end-date of that tenant. These dates will define a time window in which the tenant is considered ‘enabled’ and auth tokens will be given only when current time is between those dates. This can be

[openstack-dev] [nova] oslo.messaging rampant errors in nova-api logs

I'm looking at whether we can get ourselves to enforcing only known ERRORs in logs. In doing so one of the most visible issues on non neutron runs is oslo.messaging spewing approximately 50: ERROR oslo.messaging.notify._impl_messaging [-] Could not send notification to notifications http://logs.o

Re: [openstack-dev] [Keystone] Tenant expiration dates

Cristian, hello I believe that should not be done in such direct way, really. Why not using project.extra field in DB to store this info? Is that not appropriate for your ideas or there will be problems with there implementing using extras? Thanks, Dina On Mon, Feb 24, 2014 at 5:25 PM, Sanchez,

Re: [openstack-dev] [neutron]The mechanism of physical_network & segmentation_id is logical?

On 02/24/2014 07:09 AM, 黎林果 wrote: > Hi stackers, > > When create a network, if we don't set provider:network_type, > provider:physical_network or provider:segmentation_id, the > network_type will be from cfg, but the other tow is from db's first > record. Code is > > (physical_network, >

[openstack-dev] [Ironic] ilo driver need to submit a code change in nova ironic driver

Hi All, I am currently working on ilo driver for ironic project. As part of this implementation and to integrate with nova ironic driver ( https://review.openstack.org/#/c/51328/) we need to make changes to "driver.py" and "ironic_driver_fields.py" files, to pass down ilo driver specific fields to

[openstack-dev] Outreach Program for Women - May-Aug 2014

Hi all, Thanks the OpenStack Foundation for funding a spot for an intern with the GNOME Outreach Program for Women for May-August 2014. I've updated the OpenStack wiki page and would like to recruit mentors for this round. If you're interested in mentoring an intern and have a good idea for a 3-mon

Re: [openstack-dev] [All] Fixed recent gate issues

2014-02-23 10:52 GMT+01:00 Gary Kotton : > It looks like this does not solve the issue. Yeah https://review.openstack.org/74451 doesn't solve the issue completely, we have SKIP_EXERCISES=boot_from_volume,bundle,client-env,euca,swift,client-args but failure is now in Grenade's Javelin script: + sw

[openstack-dev] [oslo] review priority list

Team - I've made a list of the reviews associated with bugs and blueprints for icehouse-3, to make it easier to prioritize them. Some are very close to being ready to merge, so please take a look through the list for any changes you haven't already reviewed. Thanks! Doug * oslo.db graduation (o

Re: [openstack-dev] [oslo] review priority list

I suppose if I'm going to leave anything out, it's best for me to leave out the blueprint I'm working on. * oslo.test graduation https://blueprints.launchpad.net/oslo/+spec/graduate-oslo-test https://review.openstack.org/#/c/74408/ - Set up tox to run cross-project tests On Mon, Feb 24, 2014

Re: [openstack-dev] [nova] oslo.messaging rampant errors in nova-api logs

On Monday, February 24, 2014 7:26:04 AM, Sean Dague wrote: I'm looking at whether we can get ourselves to enforcing only known ERRORs in logs. In doing so one of the most visible issues on non neutron runs is oslo.messaging spewing approximately 50: ERROR oslo.messaging.notify._impl_messaging

[openstack-dev] [Neutron] ERROR: InvocationError: when running tox

Has anyone experienced this issue when running tox. I'm trying to figure if this is some limit of tox environment or something else. I've seen this referenced in other projects, but can't seem to zero in on a proper fix. tox -e py27 [...8><...snip a lot] neutron.tests.unit.test_routerserviceinse

[openstack-dev] [oslo] meeting 1400UTC 28 Feb 2014

I'd like for the oslo team to meet this Friday, 28 Feb, at 1400 UTC to review our icehouse-3 status and talk about integrating with the security response team. If you have anything else we need to go over, please add it to https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting Doug

[openstack-dev] What's Up Doc? Feb 24 2014

Hi all, Just kicked off announcing another round for the Outreach Program for Women, exciting! I also wanted to give a round up from the world of docs so here goes. 1. In review and merged this past week: We've had a good number of reviews going through as well as changes to doc tools to improve

[openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Hi, I would like to initiate one more discussion about an approach we selected to solve a particular problem in Murano. The problem statement is the following: We have multiple entities like low level resources and high level application definitions. Each entity does some specific actions for exa

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Sorry folks, I didn't put the proper image url. Here it is: https://creately.com/diagram/hrxk86gv2/kvbckU5hne8C0r0sofJDdtYgxc%3D -- Regards, Alexander Tivelkov On Mon, Feb 24, 2014 at 7:39 PM, Alexander Tivelkov wrote: > Hi, > > I would like to initiate one more discussion about an approach

Re: [openstack-dev] [nova] Future of the Nova API

> - We want to make backwards incompatible changes to the API > and whether we do it in-place with V2 or by releasing V3 > we'll have some form of dual API support burden. IMHO, the cost of maintaining both APIs (which are largely duplicated) for almost any amount of time outweighs the cost of

[openstack-dev] [Neutron] L3 HA VRRP concerns

Hi everyone, A few concerns have popped up recently about [1] which I'd like to share and discuss, and would love to hear your thoughts Sylvain. 1) Is there a way through the API to know, for a given router, what agent is hosting the active instance? This might be very important for admins to k

Re: [openstack-dev] [Neutron]Do you think tanent_id should be verified

On Mon, 2014-02-24 at 16:23 +0800, Lingxian Kong wrote: > I think 'tenant_id' should always be validated when creating neutron > resources, whether or not Neutron can handle the notifications from > Keystone when tenant is deleted. -1 Personally, I think this cross-service request is likely too e

[openstack-dev] [nova] Simulating many fake nova compute nodes for scheduler testing

Hello all, I have been trying some new ideas on scheduler and I think I'm reaching a resource issue. I'm running 6 compute service right on my 4 CPU 4 Gig VM, and I started to get some memory allocation issues. Keystone and Nova are already complaining there is not enough memory. The obvious so

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

On Feb 21, 2014, at 1:29 PM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: I disagree on this point. I believe that the more implementation details bleed into the API, the harder the API is to evolve and improve, and the less flexible the API becomes. I'd personally love to see the next version

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Hi Alex, Personally I like the approach and how you explain it. I just would like to know your opinion on how this is better from someone write Heat template that creates Active Directory lets say with one primary and one secondary controller and then publish it somewhere. Since Heat do supports

Re: [openstack-dev] [Neutron] ERROR: InvocationError: when running tox

Yes - it's a problem with non-Linux platforms not being able to install pyudev, which is a requirement for the linuxbridge plugin, which makes testr barf when it hits an ImportError. http://lists.openstack.org/pipermail/openstack-dev/2014-January/023268.html In the past, I've run tox -e py26 as a

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 2014-02-24 at 20:22 +1030, Christopher Yeoh wrote: > On Mon, 24 Feb 2014 02:06:50 -0500 > Jay Pipes wrote: > > > On Mon, 2014-02-24 at 17:20 +1030, Christopher Yeoh wrote: > > > - Proposed way forward: > > > - Release the V3 API in Juno with nova-network and tasks support > > > - Feat

Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for scheduler testing

On 24 February 2014 16:24, David Peraza wrote: > Hello all, > > I have been trying some new ideas on scheduler and I think I'm reaching a > resource issue. I'm running 6 compute service right on my 4 CPU 4 Gig VM, > and I started to get some memory allocation issues. Keystone and Nova are > alread

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 01:50 AM, Christopher Yeoh wrote: > Hi, > > There has recently been some speculation around the V3 API and whether > we should go forward with it or instead backport many of the changes > to the V2 API. I believe that the core of the concern is the extra > maintenance and test burden

[openstack-dev] [Mistral] Community meeting minutes - 02/24/2014

Folks, Thanks for joining us at #openstack-meeting. Here are the links to the meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-24-16.00.html Log: http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-24-16.00.log.html Next m

Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?

On 02/20/2014 11:38 AM, Matt Riedemann wrote: On 2/19/2014 4:05 PM, Matt Riedemann wrote: The os-hosts OS API extension [1] showed up before I was working on the project and I see that only the VMware and XenAPI drivers implement it, but was wondering why the libvirt driver doesn't - either no

Re: [openstack-dev] [Neutron] ERROR: InvocationError: when running tox

Sorry - fired off this e-mail without looking too closely at your log output - I just saw the escape characters and the long lines from tox and it reminded me of the last discussion we had about it. It's probably not the same error as I was describing. That's the tough thing that I strongly dislik

[openstack-dev] [gantt] scheduler sub-group meeting tomorrow (2/25)

All- I'm tempted to cancel the gantt meeting for tomorrow. The only topics I have are the no-db scheduler update (we can probably do that via email) and the gantt code forklift (I've been out with the flu and there's no progress on that). I'm willing to chair but I'd like to have some specifi

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Mark, I'm not sure I understand what are implementation details in the workflow I have proposed in the email above, could you point to them? Thanks, Eugene. On Mon, Feb 24, 2014 at 8:31 PM, Mark McClain wrote: > > On Feb 21, 2014, at 1:29 PM, Jay Pipes wrote: > > I disagree on this point. I

Re: [openstack-dev] [keystone] Notification When Creating/Deleting a Tenant in openstack

Hi Swann, I was able to listen to keystone notification by setting notifications in the keystone.conf file. I only needed the notification (CURD) for project and handle it in my plugin code so don't need ceilometer to handle them. The other issue is that the notification is only for limited to res

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi, I also agree that the model should be pure logical. I think that the existing model is almost correct but the pool should be made pure logical. This means that the vip <>pool relationships needs also to become any to any. Eugene, has rightfully pointed that the current "state" management

Re: [openstack-dev] [nova] Question about USB passthrough

On Mon, 2014-02-24 at 04:10 +, Liuji (Jeremy) wrote: > I have found a BP about USB device passthrough in > https://blueprints.launchpad.net/nova/+spec/host-usb-passthrough. > I have also read the latest nova code and make sure it doesn't support > USB passthrough by now. > > Are there any pro

Re: [openstack-dev] [nova] Future of the Nova API

On 2/24/2014 10:13 AM, Russell Bryant wrote: On 02/24/2014 01:50 AM, Christopher Yeoh wrote: Hi, There has recently been some speculation around the V3 API and whether we should go forward with it or instead backport many of the changes to the V2 API. I believe that the core of the concern is

Re: [openstack-dev] [Ironic] ilo driver need to submit a code change in nova ironic driver

Hi Barmawer, Currently the Ironic Nova driver is blocked from merging. The Ironic team is working on getting all the pieces in place for our C.I. testing. At this point I would say your best path is to create your patch with 51328 as a dependency. Please note that the nova driver will most likely

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Folks, So far everyone agrees that the model should be pure logical, but no one came up with the API and meaningful implementation details (at least at idea level) of such obj model. As I've pointed out, 'pure logical' object model has some API and user experience inconsistencies that we need to s

Re: [openstack-dev] [nova] Question about USB passthrough

On 02/24/2014 01:10 AM, Liuji (Jeremy) wrote: > Hi, Boris and all other guys: > > I have found a BP about USB device passthrough in > https://blueprints.launchpad.net/nova/+spec/host-usb-passthrough. > I have also read the latest nova code and make sure it doesn't support USB > passthrough by no

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Hi Stan, It is good that we are on a common ground here :) Of course this can be done by Heat. In fact - it will be, in the very same manner as it always was, I am pretty sure we've discussed this many times already. When Heat Software config is fully implemented, it will be possible to use it in

Re: [openstack-dev] [Neutron] ERROR: InvocationError: when running tox

On 2014-02-24 09:02, Randy Tuttle wrote: > Has anyone experienced this issue when running tox. I'm trying to figure if > this is some limit of tox environment or something else. I've seen this > referenced in other projects, but can't seem to zero in on a proper fix. > > tox -e py27 > > [.

Re: [openstack-dev] [Neutron] ERROR: InvocationError: when running tox

Thanks guys. Yes, Ben, I can see oslo.config installed in tox sub-directory. I will try to wipe tox out and try again. You are right though, the tox.ini only has site-packages for Jenkins noted. Sean, I think your first email response might be right. I am running on a Mac instead of Ubuntu box. I

Re: [openstack-dev] [keystone] Notification When Creating/Deleting a Tenant in openstack

Response below. Best Regards, Lance Bragstad ldbra...@us.ibm.com Nader Lahouti wrote on 02/24/2014 11:31:10 AM: > From: Nader Lahouti > To: "OpenStack Development Mailing List (not for usage questions)" > , > Date: 02/24/2014 11:37 AM > Subject: Re: [openstack-dev] [keystone] Notification W

Re: [openstack-dev] [Neutron] L3 HA VRRP concerns

Hi Assaf, some comments inline. As a general comment, I'd prefer to move all the discussions to gerrit since the patches are now in review. This unless you have design concerns (the ones below look more related to the implementation to me) Salvatore On 24 February 2014 15:58, Assaf Muller wrot

Re: [openstack-dev] Missing tests

HI! I'm sorry it took me this long to answer you. During the fixtures of the UT , there must be somewhere where you can add the extensions to load them, so their tests won't break.Could you send me a link to your patch in gerrit? From: Vinod Kumar Boppanna [mailto:vinod.kumar.boppa...@cern.ch] S

[openstack-dev] OpenStack and GSoC 2014

Hi all, We're in! Just got notified by Admin Team that our Organization Application has been accepted. I've updated the etherpad with the full responses from them. https://etherpad.openstack.org/p/gsoc2014orgapp thanks, dims ___ OpenStack-dev mailing

[openstack-dev] [infra] Meeting Tuesday February 25th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday February 25th, 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 in

[openstack-dev] [Mistral] Porting executor and engine to oslo.messaging

Renat, Regarding your comments on change https://review.openstack.org/#/c/75609/, I don't think the port to oslo.messaging is just a swap from pika to oslo.messaging. OpenStack services as I understand is usually implemented as an RPC client/server over a messaging transport. Sync vs async calls

Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for scheduler testing

Thanks John, I also think it is a good idea to test the algorithm at unit test level, but I will like to try out over amqp as well, that is, we process and threads talking to each other over rabbit or qpid. I'm trying to test out performance as well. Regards, David Peraza -Original Messag

[openstack-dev] Satori Project Update (Configuration Discovery)

We had our first team meeting[1] today and will be holding weekly team meetings on Mondays at 15:00 UTC on #openstack-meeting-alt. An early prototype of Satori is available on pypi [2]. We’re working towards adding the following features before making an announcement to the user list on availab

Re: [openstack-dev] bug 1203680 - fix requires doc

On 2014-02-21 17:09, Sean Dague wrote: On 02/21/2014 05:28 PM, Clark Boylan wrote: On Fri, Feb 21, 2014 at 1:00 PM, Ben Nemec wrote: On 2014-02-21 13:01, Mike Spreitzer wrote: https://bugs.launchpad.net/devstack/+bug/1203680 is literally about Glance but Nova has the same problem. There is

Re: [openstack-dev] OpenStack and GSoC 2014

So happy to hear that! Congrats all! 2014-02-24 16:16 GMT-03:00 Davanum Srinivas : > Hi all, > > We're in! Just got notified by Admin Team that our Organization > Application has been accepted. I've updated the etherpad with the full > responses from them. > > https://etherpad.openstack.org/p/gs

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Thanks, Eugene! I've given the API a bit of thought today and jotted down some thoughts below. On Fri, 2014-02-21 at 23:57 +0400, Eugene Nikanorov wrote: > Could you provide some examples -- even in the pseudo-CLI > commands like > I did below. It's really difficult to unde

Re: [openstack-dev] bug 1203680 - fix requires doc

On 02/24/2014 03:10 PM, Ben Nemec wrote: > On 2014-02-21 17:09, Sean Dague wrote: >> On 02/21/2014 05:28 PM, Clark Boylan wrote: >>> On Fri, Feb 21, 2014 at 1:00 PM, Ben Nemec >>> wrote: On 2014-02-21 13:01, Mike Spreitzer wrote: https://bugs.launchpad.net/devstack/+bug/1203680 is l

Re: [openstack-dev] [Neutron][LBaaS] Feedback on SSL implementation

Hi, Barbican is the storage option we're considering, however it seems that there's not much progress with incubation of it. Another week point of our current state is a lack of secure communication between neutron server and the agent, but that is solvable. Thanks, Eugene. On Fri, Feb 21, 201

Re: [openstack-dev] [savanna] Nominate Andrew Lazarew for savanna-core

Unanimously. Congratulations, Andrew, welcome to the core team! On Fri, Feb 21, 2014 at 4:46 PM, Matthew Farrellee wrote: > On 02/19/2014 05:40 PM, Sergey Lukjanov wrote: > >> Hey folks, >> >> I'd like to nominate Andrew Lazarew (alazarev) for savanna-core. >> >> He is among the top reviewers

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi Jay, Thanks for suggestions. I get the idea. I'm not sure the essence of this API is much different then what we have now. 1) We operate on parameters of loadbalancer rather then on vips/pools/listeners. No matter how we name them, the notions are there. 2) I see two opposite preferences: one i

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 24 Feb 2014 07:56:19 -0800 Dan Smith wrote: > > - We want to make backwards incompatible changes to the API > > and whether we do it in-place with V2 or by releasing V3 > > we'll have some form of dual API support burden. > > IMHO, the cost of maintaining both APIs (which are largely

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Have you considered writing Heat resource plug-ins that perform (or configure within other services) instance snapshots, backups, or whatever other maintenance workflow possibilities you want that don't exist? Then these maintenance workflows you mention could be expressed in the Heat template

Re: [openstack-dev] Sent the first batch of invitations to Atlanta's Summit

On 02/17/2014 05:21 PM, Steve Kowalik wrote: > I found it completely non-obvious too, and had to go back and look for > the link. If the promotion code text box was always visible with the > Apply button grayed out when the text box is empty, I think that would help. Unfortunately the site is mana

[openstack-dev] [Ironic] Starting to postpone work to Juno

Hi all, For the last few meetings, we've been discussing how to prioritize the work that we need to get done as we approach the close of Icehouse development. There's still some distance between where we are and where we need to be -- integration with other projects (eg. Nova), CI testing of that

Re: [openstack-dev] [nova] Future of the Nova API

On the topic of backwards incompatible changes: I strongly believe that breaking current clients that use the APIs directly is the worst option possible. All the arguments about needing to know which APIs work based upon which backend drivers are used are all valid, but making an API incompatib

Re: [openstack-dev] Sent the first batch of invitations to Atlanta's Summit

Make sure that you also log in, or have your username and password handy before you redeem it. If you click a link to send a password reset, you'll lose your session, and the invite code is a one-time use – I had to dig through my history to get the URL back, since the back button did not work

[openstack-dev] [nova] why doesn't _rollback_live_migration() always call rollback_live_migration_at_destination()?

I'm looking at the live migration rollback code and I'm a bit confused. When setting up a live migration we unconditionally run ComputeManager.pre_live_migration() on the destination host to do various things including setting up networks on the host. If something goes wrong with the live mig

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

On Mon, Feb 24, 2014 at 4:20 PM, Georgy Okrokvertskhov < gokrokvertsk...@mirantis.com> wrote: > Hi Keith, > > Thank you for bringing up this question. We think that it could be done > inside Heat. This is a part of our future roadmap to bring more stuff to > Heat and pass all actual work to the he

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 24 Feb 2014 11:13:11 -0500 Russell Bryant wrote: > > Yes, this is a major concern. It has taken an enormous amount of work > to get to where we are, and v3 isn't done. It's a good time to > re-evaluate whether we are on the right path. So I think its important to point out that we pret

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 05:01 PM, Morgan Fainberg wrote: > On the topic of backwards incompatible changes: > > I strongly believe that breaking current clients that use the APIs > directly is the worst option possible. All the arguments about needing > to know which APIs work based upon which backend driver

Re: [openstack-dev] [nova] Future of the Nova API

> The API layer is a actually quite a very thin layer on top of the > rest of Nova. Most of the logic in the API code is really just > checking incoming data, calling the underlying nova logic and then > massaging what is returned in the correct format. So as soon as you > change the format the cos

Re: [openstack-dev] [Murano] Object-oriented approach for defining Murano Applications

Hi Keith, Thank you for bringing up this question. We think that it could be done inside Heat. This is a part of our future roadmap to bring more stuff to Heat and pass all actual work to the heat engine. However it will require a collaboration between Heat and Murano teams, so that is why we want

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 04:01 PM, Morgan Fainberg wrote: TL;DR, “don’t break the contract”. If we are seriously making incompatible changes (and we will be regardless of the direction) the only reasonable option is a new major version. Agreed. I don't think we can possibly consider making backwards-in

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 24 Feb 2014 11:48:41 -0500 Jay Pipes wrote: > It's not about "forcing" providers to support all of the public API. > It's about providing a single, well-documented, consistent HTTP REST > API for *consumers* of that API. Whether a provider chooses to, for > example, deploy with nova-networ

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 05:26 PM, Christopher Yeoh wrote: >>> - Whilst we have existing users of the API we also have a lot more >>> users in the future. It would be much better to allow them to use >>> the API we want to get to as soon as possible, rather than trying >>> to evolve the V2 API and forci

Re: [openstack-dev] [nova] Future of the Nova API

On Tue, Feb 25, 2014 at 8:31 AM, Morgan Fainberg wrote: > On the topic of backwards incompatible changes: > > I strongly believe that breaking current clients that use the APIs > directly is the worst option possible. All the arguments about needing to > know which APIs work based upon which back

Re: [openstack-dev] [nova] Future of the Nova API

It's really easy to just say "don't break the contract." Until we got the level of testing that we currently have in Tempest, the contract was broken pretty regularly. I'm sure there are still breaks in it around the edges where we aren't clamping down on people today. So the history of v2 is far

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 05:49 PM, Michael Davies wrote: > On Tue, Feb 25, 2014 at 8:31 AM, Morgan Fainberg > wrote: > > On the topic of backwards incompatible changes: > > I strongly believe that breaking current clients that use the APIs > directly is the worst opti

[openstack-dev] [Neutron][IPv6] tox error

Hi, guys: I run into this error while running fox…..but it gave me this error…Seems like it is related to Neutron LB. Did you see this issue before? If so, how to fix it? Thanks! Shixiong shshang@net-ubuntu2:~/github/neutron$ tox -v -e py27 ……... tests.unit.test_wsgi.XMLDictSerializerTes

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 04:59 PM, Sean Dague wrote: So, that begs a new approach. Because I think at this point even if we did put out Nova v3, there can never be a v4. It's too much, too big, and doesn't fit in the incremental nature of the project. Does it necessarily need to be that way though? Mayb

Re: [openstack-dev] [nova] Future of the Nova API

On 02/24/2014 06:13 PM, Chris Friesen wrote: > On 02/24/2014 04:59 PM, Sean Dague wrote: > >> So, that begs a new approach. Because I think at this point even if we >> did put out Nova v3, there can never be a v4. It's too much, too big, >> and doesn't fit in the incremental nature of the project.

  1   2   >