Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

On Mon, Oct 28, 2013 at 04:48:45PM -0400, Mike Spreitzer wrote: > Steve Baker wrote on 10/28/2013 04:24:30 PM: > > > On 10/29/2013 02:53 AM, Steven Hardy wrote: > > > ... > > > Can anyone provide me with a clear argument for what the "fundamental > > > differences" actually are? > > ... > > Since

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

On Mon, Oct 28, 2013 at 02:34:44PM -0700, Georgy Okrokvertskhov wrote: > I believe we had a discussion about difference between declarative approach > and workflows. A component approach is consistent with declarative format > as all actions\operations are hidden inside the service. If you want to

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

Nice example.. I think this is certainly a step in the right direction. However, I am a bit lost when trying to figure out how this kind of API (which makes perfect sense at the conceptual level) can be implemented. IMO, when we make the attempt to design the actual implementation that would be

[openstack-dev] [Trove] Design Summit Etherpads

The list of Etherpads for the design summit sessions for Trove is now posted at: https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Trove Feel free to add any relevant notes to the Etherpads. Thanks, Cheers, -Nikhil ___ OpenStack-dev mailing l

Re: [openstack-dev] Full schedule for HongKong summit?

I had the same concern, and only ended up exporting my Sched.org agendas (the sessions I starred) to my own Google agenda (using iCal) in order to see the conflicts. Hope it can helps, -Sylvain Le 29/10/2013 04:08, Lu, Lianhao a écrit : Hi all, Looks like we have http://icehousedesignsummit.

Re: [openstack-dev] Full schedule for HongKong summit?

There is no such mixed calendar. It was made, as far as I remember, because design and summit talks are very different and should be separated. But still, it is not really comfortable. On Tue, Oct 29, 2013 at 11:48 AM, Sylvain Bauza wrote: > I had the same concern, and only ended up exporting m

Re: [openstack-dev] [Neutron] Security groups with XenAPI

Hi Bob, Thanks for the reply. Le 28/10/2013 17:47, Bob Ball a écrit : Hi Simon, Yes, I believe you are right. We were already planning to discuss this very topic at the XenAPI roadmap session at the summit. Hopefully someone will take on tying up this loose end there. Security group suppo

[openstack-dev] [Nova]Ideas of idempotentcy-client-token

Hi all! I proposed 'Idempotency for OpenStack API' as before. In this time, I rewrote BP( https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token ) and I implemented proto of it. I image below use-case. User can't know instance ID when the client has gone away before user get 'cre

[openstack-dev] [Marconi] Design Summit Etherpads

Greetings, Here[0] you can find Marconi's etherpads for the Icehouse Design Summit. [0] https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Marconi -- @flaper87 Flavio Percoco ___ OpenStack-dev mailing list [email protected] ht

[openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

Hi folks, Currently there are two attributes of vips/pools/members that represent a status: 'status' and 'admin_state_up'. The first one is used to represent deployment status and can be PENDING_CREATE, ACTIVE, PENDING_DELETE, ERROR. We also have admin_state_up which could be True or False. I'd

[openstack-dev] Unable to logging to guest console on XCP/xenserver

Hi, I am trying to use Openstack Havana to control XCP hypervisor with neutron OVS plugin. I can launch instances normally but unable to logging to guest console. Please see the below log from nova compute to get a clear idea. Log: 2013-10-29 14:09:10.203 954 AUDIT nova.compute.manager [req-157f

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

Hi Yathi, > > https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit > Would it be possible to provide an alternate link to the doc? The GFW blocks google docs :(. Thanks. -- Koo ___ OpenStack-dev mailing list OpenSt

[openstack-dev] Reminder: Project & release status meeting - 21:00 UTC

One week before the OpenStack Summit in Hong-Kong, this meeting should be short. We will focus on solving the last conflicts with the tentative Design Summit schedule and make it "official". Feel free to add extra topics to the agenda: [1] http://wiki.openstack.org/Meetings/ProjectMeeting All pro

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Irena, Thank you very much for your comments. See inline. --Robert On 10/27/13 3:48 AM, "Irena Berezovsky" mailto:[email protected]>> wrote: Hi Robert, Thank you very much for sharing the information regarding your efforts. Can you please share your idea of the end to end flow? How do yo

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Robert, is it possible to have a IRC meeting? I'd prefer to IRC meeting because it's more openstack style and also can keep the minutes clearly. To your flow, can you give more detailed example. For example, I can consider user specify the instance with -nic option specify a network id, and then

Re: [openstack-dev] [Nova] Preserving ephemeral block device on rebuild?

Hi Rob, I think it looks like a good option - but I'd like to see it exposed as such to the user rather than a change in the default behavior as such. I.e. "rebuild --keep-ephemenral=True " Phil > -Original Message- > From: Robert Collins [mailto:[email protected]] > Sen

Re: [openstack-dev] [Nova] Blueprint review process

On 28 October 2013 15:39, Anne Gentle wrote: > On Mon, Oct 28, 2013 at 9:24 AM, John Garbutt wrote: >> Here is a really bad attempt at codifying what I think about features vs >> bugs: >> 1) If its a new API call, or a change in behaviour, or a new config >> setting, its a feature >> 2) If its ju

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Jiang, Robert, IRC meeting option works for me. If I understand your question below, you are looking for a way to tie up between requested virtual network(s) and requested PCI device(s). The way we did it in our solution is to map a provider:physical_network to an interface that represents t

Re: [openstack-dev] [Nova] Preserving ephemeral block device on rebuild?

On 29 October 2013 23:06, Day, Phil wrote: > Hi Rob, > > I think it looks like a good option - but I'd like to see it exposed as such > to the user rather than a change in the default behavior as such. I.e. > "rebuild --keep-ephemenral=True " Oh, I must not have been clear. That was absol

Re: [openstack-dev] [Nova] Blueprint review process

> John Garbutt wrote: >> On 25 October 2013 11:52, Nikola Đipanov wrote: >>> I don't have the numbers but I have a feeling that what happened in >>> Havana was that a lot of blueprints slipped until the time for feature >>> freeze. Reviewers thought it was a worthwile feature at that point (this >

Re: [openstack-dev] Full schedule for HongKong summit?

Dina Belova wrote: > There is no such mixed calendar. It was made, as far as I remember, > because design and summit talks are very different and should be separated. > > But still, it is not really comfortable. Yes, it's a bit of a trade-off... In the past we had a lot of people, attracted by c

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

On Tue, Oct 29, 2013 at 8:50 AM, haruka tanizawa wrote: > Hi all! > > > I proposed 'Idempotency for OpenStack API' as before. > In this time, I rewrote BP( > https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token ) > and I implemented proto of it. > > > I image below use-case. > Use

Re: [openstack-dev] [Nova] Preserving ephemeral block device on rebuild?

On 29 October 2013 10:20, Robert Collins wrote: > On 29 October 2013 23:06, Day, Phil wrote: >> Hi Rob, >> >> I think it looks like a good option - but I'd like to see it exposed as >> such to the user rather than a change in the default behavior as such. I.e. >> "rebuild --keep-ephemenral=Tr

[openstack-dev] [nova] reason for python-novaclient revert

Andrew Laski correctly called us out for not really proving enough information n the python-novaclient revert yesterday - https://review.openstack.org/#/c/54108/. Appologies there. At the time we were dealing with a gate that grenade was failing every change (for the prior 6 hours), we were all

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

I would love to see a symmetry between Cinder local volumes and Neutron PCI passthrough VIFs. Not entirely sure I have that clear in my head right now, but I just wanted to share the idea: * describe resource external to nova that is attached to VM in the API (block device mapping and/or vif refer

Re: [openstack-dev] Remove vim modelines?

So after over 20 messages in this thread, now what? >From my count we have 3 -, and 12 +1s. Is that enough for consensus? Do we move modelines lines to the bottom? Put them in every file? Or just remove them? https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topi

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

Hi Joe! Thank you for your reply and sharing the information. I am going to rewrite blueprint from many point of view. Sincerely, Haruka Tanizawa 2013/10/29 Joe Gordon > > > > On Tue, Oct 29, 2013 at 8:50 AM, haruka tanizawa wrote: > >> Hi all! >> >> >> I proposed 'Idempotency for OpenStack A

Re: [openstack-dev] Remove vim modelines?

On 28 October 2013 23:54, Joe Gordon wrote: > We don't just gate without telling people, the first two items in hacking > are read pep8 > > http://docs.openstack.org/developer/hacking/ The gate is super useful, but it's reactive, not proactive. And good documentation isn't a replacement for jus

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

On 29 October 2013 06:46, Yathiraj Udupi (yudupi) wrote: > The Instance Group API document is now updated with a simple example request > payload of a nested group, and some description of how the API > implementation should handle the registration of the components of a nested > instance group. >

Re: [openstack-dev] [nova][qa] user-oriented release notes for v3 api?

On 28 October 2013 23:40, Christopher Yeoh wrote: > On Tue, Oct 29, 2013 at 7:22 AM, David Kranz wrote: >> >> As I looked at the havana release notes that talk about the v3 api, and as >> I was reviewing >> "port test_images and test_server_actions into v3 part2" >> https://review.openstack.org/#

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

Hi Joe! Thank you for your help. I wrote BP https://blueprints.launchpad.net/nova/+spec/idempotentcy- client-token again. Could you review it when you have time. > I like the idea but two comments: >> >> * Can you fill out the questions found in >> http://justwriteclick.com/2013/09/17/openstack

Re: [openstack-dev] [nova] Thoughs please on how to address a problem with mutliple deletes leading to a nova-compute thread pool problem

On 25 October 2013 23:23, Chris Behrens wrote: > On Oct 25, 2013, at 3:46 AM, "Day, Phil" wrote: >> Hi Folks, >> >> We're very occasionally seeing problems where a thread processing a create >> hangs (and we've seen when taking to Cinder and Glance). Whilst those >> issues need to be hunted do

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

Going back to Joe's comment: > Can both of these cases be covered by configuring the keystone catalog? +1 If both v1 and v2 are present, pick v2, otherwise just pick what is in the catalogue. That seems cool. Not quite sure how the multiple glance endpoints works in the keystone catalog, but shoul

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

On 29 October 2013 11:56, haruka tanizawa wrote: > Hi Joe! > > Thank you for your help. > I wrote BP > https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token again. > Could you review it when you have time. > > >>> >>> I like the idea but two comments: >>> >>> * Can you fill out the

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

On 28/10/13 04:23, Lakshminaraya Renganarayana wrote: Sorry, Re-posting this with [Heat] in the subject line, because many of us have filters based on [Heat] in the subject line. Hello, A few us at IBM studied Steve Baker's proposal on HOT Software Configuration. Overall the proposed constructs

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

On 28/10/13 14:53, Steven Hardy wrote: On Sun, Oct 27, 2013 at 11:23:20PM -0400, Lakshminaraya Renganarayana wrote: A few us at IBM studied Steve Baker's proposal on HOT Software Configuration. Overall the proposed constructs and syntax are great -- we really like the clean syntax and concise sp

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

I haven't look at the review proposed yet one week ago, but some time ago, we needed something similar for Ironic (nova, ironic and cinder share almost the same code for the glance driver), but didn't make it. In case someone wants to take a look: https://review.openstack.org/#/c/33327/ I'll take

[openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

Hi there, I've been working on this bug [1,2] related with the pluggable external authentication support in Havana. For those not familiar with it, Keystone can rely on the usage of the REMOTE_USER env variable, assuming that the user has been authenticated upstream (by an httpd server). This REMO

Re: [openstack-dev] [TripleO][Nova] summit overlap

On 10/28/2013 06:41 PM, Devananda van der Veen wrote: > I can't make the Wed 2:50 session -- I'm presenting at that time -- but > I don't think it's essential for me to be there anyway. Everything else > LGTM. Thanks! Would you rather be able to attend that one (Smarter resource placement for inte

[openstack-dev] AUTO: Alexandra Shulman-Peleg is out of the office. (returning 31/10/2013)

I am out of the office until 31/10/2013. I am out of office. If required, please contact my manager Dalit Naor ([email protected]). For matters related to the VISION project, please contact Hillel Kolodner ([email protected]). Note: This is an automated response to your message "Re: [openstac

Re: [openstack-dev] Remove vim modelines?

On Tue, Oct 29, 2013 at 11:17 AM, Robert Collins wrote: > On 28 October 2013 23:54, Joe Gordon wrote: > > > > We don't just gate without telling people, the first two items in hacking > > are read pep8 > > > > http://docs.openstack.org/developer/hacking/ > > The gate is super useful, but it's rea

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

Hi Yathi, Thank you for yor example. I have some remarks concerning the JSON format: 1) Member of a group is recursive. A member can be group or an instance. In this case there are two different declaration formats for members, as with http-server-group-1 ("name, "policy", "edge") and Http-Serv

Re: [openstack-dev] Remove vim modelines?

On 10/29/13 at 10:53am, Joe Gordon wrote: So after over 20 messages in this thread, now what? From my count we have 3 -, and 12 +1s. Is that enough for consensus? Do we move modelines lines to the bottom? Put them in every file? Or just remove them? I have no strong feeling either way on kee

Re: [openstack-dev] [Nova] Preserving ephemeral block device on rebuild?

On 10/28/2013 06:17 AM, John Garbutt wrote: > Is there a reason why you could not just use a Cinder Volume for your > data, in this case? Yeah, he was saying that's the long term goal, and an Ironic-targeted feature. > While at a first glance, it feels rather wrong, and un-cloudy, I do > see some

[openstack-dev] [Ceilometer] Suggestions for alarm improvements ...

Hey y'all, Here are a few notes I put together around some ideas for alarm improvements. In order to set it up I spent a little time talking about the Ceilometer architecture in general, including some of the things we have planned for IceHouse. I think Parts 1-3 will be useful to anyone look

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi, sounds like there are enough interests for an IRC meeting before the summit. Do you guys know how to schedule a #openstack IRC meeting? thanks, Robert On 10/29/13 6:17 AM, "Irena Berezovsky" mailto:[email protected]>> wrote: Hi Jiang, Robert, IRC meeting option works for me. If I unders

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

Whilst on this topic, perhaps we should also expand it to discuss support for external authz as well. I know that Adam at Red Hat is working on adding additional authz attributes as env variables so that these can be used for authorising the user in keystone. It should be the same module in Key

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Yunhong, I haven't looked at Mellanox in much detail. I think that we'll get more details from Irena down the road. Regarding your question, I can only answer based on my experience with Cisco's VM-FEX. In a nutshell: -- a vNIC is connected to an external switch. Once the host is booted

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi John, Great to hear from you on Cinder with pcipassthrough. I thought that it would be coming. I like the idea. thanks, Robert On 10/29/13 6:46 AM, "John Garbutt" wrote: >I would love to see a symmetry between Cinder local volumes and >Neutron PCI passthrough VIFs. > >Not entirely sure I ha

Re: [openstack-dev] Remove vim modelines?

On Thu, Oct 24, 2013 at 2:48 PM, Robert Collins wrote: > > > *) They help casual contributors *more* than long time core > contributors : and those are the folk that are most likely to give up > and walk away. Keeping barriers to entry low is an important part of > making OpenStack development acce

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

I am wondering on the execution semantics of these components or software config resources with respect to restart or re-execution. Coming from a iterative development and deployment angle, I would like these software config resources to be idempotent. What are your thoughts? Thanks, LN Steven H

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

Hi It feels like a driver specific topic. So I am not sure we can come to a generic solution in the lbaas core code. Thanks Avishay From: Eugene Nikanorov [mailto:[email protected]] Sent: Tuesday, October 29, 2013 11:19 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neu

[openstack-dev] [Trove] Templates in Trove

I'm pulling this conversation out of the gerrit review as I think it needs more discussion. https://review.openstack.org/#/c/53499/ I want to discuss the design decision to not use Jinja templates for the heat templates. My arguments for using Jinja for heat as well are: 1. We have to rewrite al

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Hi all, I have read thru all the good discussion around software orchestration and what to share my view. I see that there are two threads - this one and [1] - but I am just replying to the one with the more generic topic line. So on the recent twist to have software components implemented as res

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Lots of great info and discussion going on here. One additional thing I would like to mention is regarding PF and VF usage. Normally VFs will be assigned to instances, and the PF will either not be used at all, or maybe some agent in the host of the compute node might have access to the PF for so

Re: [openstack-dev] [Trove] Templates in Trove

Robert, i also have thoughts about templates. Your suggestion is rather complex. Let me explain why is it so: With new datastore support you should update PackageLoader and FilesystemLoader with new filesystem path and package path. I would prefe more easy configuration and store it in next

Re: [openstack-dev] [Heat] Network topologies

Hi Edgar, It seems like this blueprint is related more to building an api that manages a network topology more than one that needs to build out the dependencies between resources to help create the network topology. If we are talking about just an api to "save", "duplicate", and "share" these netw

Re: [openstack-dev] [heat] Proposal for new heat-core member

On 10/25/2013 03:12 PM, Steven Dake wrote: I would like to propose Randall Burt for Heat Core. Please have a vote +1/-1 and take into consideration: https://wiki.openstack.org/wiki/Heat/CoreTeam [1]http://russellbryant.net/openstack-stats/heat-reviewers-180.txt

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

+1 (except possibly for the environmental variables portion, which could and perhaps should be handled through provisioning). On Oct 29, 2013, at 8:35 AM, David Chadwick wrote: > Whilst on this topic, perhaps we should also expand it to discuss support for > external authz as well. I know tha

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

Hi Steve, I am sorry for my confusing message. Just for clarification, I am against adding new abstracts to the HOT template. I just wanted to highlight that in Lakshminarayana proposal there are multiple steps which represent the same component in different stages. This might be confusing, becaus

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

On Tue, Oct 29, 2013 at 01:50:59PM +0100, Zane Bitter wrote: > On 28/10/13 14:53, Steven Hardy wrote: > >On Sun, Oct 27, 2013 at 11:23:20PM -0400, Lakshminaraya Renganarayana wrote: > >>A few us at IBM studied Steve Baker's proposal on HOT Software > >>Configuration. Overall the proposed constructs

[openstack-dev] Hyper-V meeting canceled for today.

Hi Everyone. Many of key individuals are preparing for the summit, and will not be able to attend today, so it's best to postpone the meeting until after the summit. p Peter J. Pouliot, CISSP Senior SDET, OpenStack Microsoft New England Research & Development Center One Memorial Drive,Cambridg

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

Has the case been considered where REMOTE_USER is used with authentication mechanisms where the username is an email address? It will have to keep the @domain part because that's the only thing that makes it unique. Thanks, Kevin From: Álvaro López García

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

"John Garbutt" said: > Going back to Joe's comment: >> Can both of these cases be covered by configuring the keystone catalog? > +1 > > If both v1 and v2 are present, pick v2, otherwise just pick what is in > the catalogue. That seems cool. Not quite sure how the multiple glance > endpoints wor

Re: [openstack-dev] [Trove] Templates in Trove

+1 to Robert's suggestion I think it makes sense to keep all data store templates that are used in the same location. ie. templates/{data-store}/*.template As trove expands its data stores then we have all the templates next to each other. I think it would make it easier to remove/add support for

Re: [openstack-dev] [TripleO][Nova] summit overlap

Based on the current descriptions, I think Instance Group Model looks more important for me. Current schedule appears fine for that. -D On Tue, Oct 29, 2013 at 5:59 AM, Russell Bryant wrote: > On 10/28/2013 06:41 PM, Devananda van der Veen wrote: > > I can't make the Wed 2:50 session -- I'm pre

Re: [openstack-dev] [nova] reason for python-novaclient revert

Zuul just caused my brain to overload ;) thx for the detailed explanation. Sent from my really tiny device... > On Oct 29, 2013, at 3:42 AM, "Sean Dague" wrote: > > Andrew Laskicorrectly called us out for not really proving enough > information n the python-novaclient revert yesterday - >

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

We also need some standardisation on the command line options for the client portion (such as --os-auth-method, --os-x509-cert etc.) . Unfortunately, this is not yet in Oslo so there would be multiple packages to be enhanced. Tim > -Original Message- > From: Alan Sill [mailto:kilohoku.

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

That's right, it is driver-specific, but we can come up with a generic guideline for this. Also, I'm interested in preferred solution for HAProxy. Thanks, Eugene. On Tue, Oct 29, 2013 at 6:43 PM, Avishay Balderman wrote: > Hi > > It feels like a driver specific topic. > > So I am not s

Re: [openstack-dev] Unable to logging to guest console on XCP/xenserver

The trace below seems to be wanting to access the console log, rather than the VNC console. I believe there is a blog post about how to enable this, but basically you need a cronjob to run in dom0 to rotate the logs. This is because the Xen console logging is not ring-based, and therefore with

Re: [openstack-dev] [Trove] Templates in Trove

So I guess the only contention point is to either store the templates by type or by datastore. I don't see the use case where you'd have completely different paths for templates, so there is really no need for two separate template paths. My idea is to group the templates by data_store because as w

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

What is the semantic of "domain" in the current implementation? Until we know this we cant devise a solution. Will the developed solution cater for me logging in via Google using my kent email address (as opposed to my gmail one)? In this case there could be 2 domains (depending upon the seman

Re: [openstack-dev] [Trove] Templates in Trove

I like simple. To me it is easier to break them out into dirs like Robert suggested rather than eventually having a folder full of num_datastore_types * 2 files. As for the structure, I find it more intuitive to have the directories named for the datastore type. within that dir you can have the

Re: [openstack-dev] [Trove] Templates in Trove

Excerpts from Robert Myers's message of 2013-10-29 07:54:59 -0700: > I'm pulling this conversation out of the gerrit review as I think it needs > more discussion. > > https://review.openstack.org/#/c/53499/ > After reading the comments in that review, it seems to me that you don't need a client

Re: [openstack-dev] [Trove] Templates in Trove

+1 for idea suggested in https://review.openstack.org/#/c/54315/. We discussed to store heat templates at separate idea - so, here it is. I think it's ok to store configs in separate dirs: one for configurations and one for heat templates. 2013/10/29 Daniel Salinas > I like simple. To me it

[openstack-dev] [Neutron] Shared network between specific tenants, but not all tenants?

Hi Neutron devs, Are there any plans to support networks that are shared/routed only between certain tenants (not all tenants)? Thanks, -jay ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/

Re: [openstack-dev] [Trove] Templates in Trove

Only trove administrator has access to heat templates, user cannot manipulate templates, if he could we would not need trove at all. And idea is to store only one template per datastore. And, i know that templates could be parametrized. But, keep in mind, that we cannot inject in templates anything

Re: [openstack-dev] [TripleO] Please create and list etherpads for summit sessions

Hi Done for the CI/CD automation session. https://etherpad.openstack.org/p/icehouse-tripleo-deployment-ci-and-cd-automation (and linked from the wiki) Cheers, Chris On 28 October 2013 21:26, Robert Collins wrote: > If you proposed a summit session and it's been accepted you need to > creat

Re: [openstack-dev] [Trove] Templates in Trove

Also using one template for every life situations is a mess, someday it would become himera. And if i don't want to inject something but template relays on some kind of parameter, heat would return exception on attempt to validate template with part of expected parameters. _

Re: [openstack-dev] [Ceilometer] Suggestions for alarm improvements ...

Sandy, Does the framework account for customizable events?: In my use case, I have a network (or some other proprietary way, e.g., some special BUS protocol) attached device that does not fit into openstack node structure. It can generate events. According to these events, Openstack orchestrat

Re: [openstack-dev] [Neutron] Common requirements for services' discussion

Hi, Here is the log from today's meeting: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2013/networking_advanced_services.2013-10-29-15.33.log.html (some action items for a few folks who were present, we will follow up in the next meeting.) Thanks, ~Sumit. On Mon, Oct 2

Re: [openstack-dev] [Neutron] Shared network between specific tenants, but not all tenants?

We have been considering this and have some notes on our concept, but we haven't made a blueprint for it. I will speak amongst my group and find out what they think of making it more public. On 10/29/13 12:26 PM, "Jay Pipes" wrote: >Hi Neutron devs, > >Are there any plans to support networks tha

Re: [openstack-dev] [Heat] Network topologies

Tim, You statement "building an api that manages a network topology more than one that needs to build out the dependencies between resources to help create the network topology" Is exactly what we are proposing, and this is why we believe this is not under Heat domain. This is why we are NOT prop

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

> > I am not a fan of all the specific talk to glance code we have in > > nova, moving more of that into glanceclient can only be a good thing. > > For the XenServer itegration, for efficiency reasons, we need glance > > to talk from dom0, so it has dom0 making the final HTTP call. So we > > would

Re: [openstack-dev] [Neutron] Shared network between specific tenants, but not all tenants?

On 10/29/2013 02:25 PM, Justin Hammond wrote: We have been considering this and have some notes on our concept, but we haven't made a blueprint for it. I will speak amongst my group and find out what they think of making it more public. OK, cool, glad to know I'm not the only one with tenants a

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

"Yathiraj Udupi (yudupi)" wrote on 10/29/2013 02:46:30 AM: > The Instance Group API document is now updated with a simple example > request payload of a nested group, and some description of how the > API implementation should handle the registration of the components > of a nested instance gr

Re: [openstack-dev] [Heat] Network topologies

Hi Edgar, I definitely see the usecase for the idea that you propose. In my opinion, I don't see the reason for moving the management of topology into neutron, Heat already provides this functionality (besides for the part of taking an existing deployment and generating a template file). Also, I

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

Alex Glikson wrote on 10/29/2013 03:37:41 AM: > 1. I assume that the motivation for rack-level anti-affinity is to > survive a rack failure. Is this indeed the case? > This is a very interesting and important scenario, but I am curious > about your assumptions regarding all the other OpenStack

Re: [openstack-dev] [Heat] Network topologies

Aaron, Moving the management of topology? I am not proposing nothing like that, actually could you explain me the current workflow to save a network topology created by Neutron APIs, in order to use it by a different tenant or the owner itself in a different time? Possibly, that is the part that I

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

> * describe resource external to nova that is attached to VM in the API > (block device mapping and/or vif references) > * ideally the nova scheduler needs to be aware of the local capacity, > and how that relates to the above information (relates to the cross > service scheduling issues) I thin

Re: [openstack-dev] [Heat] Network topologies

On 29/10/13 19:33, Edgar Magana wrote: Tim, You statement "building an api that manages a network topology more than one that needs to build out the dependencies between resources to help create the network topology" Is exactly what we are proposing, and this is why we believe this is not under

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

Khanh-Toan Tran wrote on 10/29/2013 09:10:00 AM: > ... > 1) Member of a group is recursive. A member can be group or an > instance. In this case there are two different declaration formats > for members, as with http-server-group-1 ("name, "policy", "edge") > and Http-Server-1 ("name", "reques

Re: [openstack-dev] [Trove] Templates in Trove

I hear you Clint. I'm not an expert on heat templates so it is possible to do this all with one. However I don't want to use Jinja to replace the heat template logic just for sane template loading. We are already using Jinja templates to load custom config files. So it makes sense to re-use the sam

Re: [openstack-dev] [heat] Proposal for new heat-core member

I count enough core +1s. Congrats Randall, well deserved! On 10/26/2013 08:12 AM, Steven Dake wrote: > Hi, > > I would like to propose Randall Burt for Heat Core. He has shown > interest in Heat by participating in IRC and providing high quality > reviews. The most important aspect in my mind of

Re: [openstack-dev] [Nova] Blueprint review process

On 10/28/2013 10:28 AM, Russell Bryant wrote: > 2) Setting clearer expectations. Since we have so many blueprints for > Nova, I feel it's very important to accurately set expectations for how > the priority of different projects compare. In the last cycle, > priorities were mainly subjectively se

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

John Garbutt wrote on 10/29/2013 07:29:19 AM: > ... > Its looking good, but I was thinking about a slightly different approach: > > * I would like to see instance groups be used to describe all > scheduler hints (including, please run on cell X, or please run on > hypervisor Y) I think Yathi's

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Your explanation of the virtual network and physical network is quite clear and should work well. We need change nova code to achieve it, including get the physical network for the virtual network, passing the physical network requirement to the filter properties etc. For your port method, so y

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Henry,why do you think the "service VM" need the entire PF instead of a VF? I think the SR-IOV NIC should provide QoS and performance isolation. As to assign entire PCI device to a guest, that should be ok since usually PF and VF has different device ID, the tricky thing is, at least for some PC

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

I should clarify my comment about invoking Heat to do the orchestration. I think we have a choice between designing a 1-stage API vs a 2-stage API. The 2-stage API goes like this: first the client defines the top-level group and everything inside it, then the client makes more calls to create t

[openstack-dev] HK Neutron Icehouse Design Meetings

Hi, Is there a schedule published for the Neutron Icehouse design meetings listed at http://summit.openstack.org/ Thanks, -hemanth ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

  1   2   >