Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On 10 January 2014 01:46, Sean Dague wrote: > I think we are all agreed that the current state of Gate Resets isn't good. ... > Specifically I'd like to get commitments from as many PTLs as possible that > they'll both directly participate in the day, as well as encourage the rest > of their proje

Re: [openstack-dev] [nova] Bogus -1 scores from turbo hipster

On 9 January 2014 07:05, Samuel Merritt wrote: > On 1/7/14 2:53 PM, Michael Still wrote: >> So applying migration 206 took slightly over a minute (67 seconds). >> Our historical data (mean + 2 standard deviations) says that this >> migration should take no more than 63 seconds. So this only just

Re: [openstack-dev] [Gantt] Looking for some answers...

On 7 January 2014 08:50, Dugger, Donald D wrote: > Pretty much what Vish said. > > In re: History. I think this was the right way, these scheduler files didn't > just spring up from nowhere, maintaining the history is a good thing. Even > when this becomes a separate service knowing where the

Re: [openstack-dev] [nova] where to expose network quota

On 8 January 2014 03:01, Christopher Yeoh wrote: > On Mon, Jan 6, 2014 at 4:47 PM, Yaguang Tang ... > > For the V3 API clients should access neutron directly for quota information. > The V3 API will no longer proxy quota related information for neutron. Also > novaclient will not get the quota in

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 4 January 2014 08:31, Jeremy Stanley wrote: > I really don't understand the aversion to allowing contributors to > police on their own what files they do and don't commit in a review > to an OpenStack project. It all boils down to the following > balancing act: I have *no* aversion to allowin

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 6 January 2014 05:18, Jeremy Stanley wrote: > I think people are conflating two different "global" concepts > here... > > There had been a discussion about synchronizing the .gitignore files > of all projects into one central list (a la openstack/requirements > synchronization): "global" acros

Re: [openstack-dev] [Savanna] Spark plugin status

On 01/09/14 19:12, Matthew Farrellee wrote: This is definitely great news! +2 to the things Sergey mentioned below. Additionally, will you fill out the blueprint or wiki w/ details that will help others write integration tests for your plugin? We already implemented at least some part of the

Re: [openstack-dev] [requirements] - taskflow preventing sqla 0.8 upgrade

On 5 January 2014 02:02, Sean Dague wrote: > So we used to do that the apps against release libraries. And the result was > more and more full day gate breaks. We did 2 consecutive ones in 2 weeks. > > Basically, once you get to be a certain level of coupled in OpenStack we can > no longer let yo

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

Thanks Jay, this is a very useful summary! Some comments inline: On 01/09/2014 06:22 PM, Jay Dobies wrote: I'm trying to hash out where data will live for Tuskar (both long term and for its Icehouse deliverables). Based on the expectations for Icehouse (a combination of the wireframes and what's

Re: [openstack-dev] Devstack on Fedora 20

On 09/01/14 23:27 -0500, Adam Young wrote: On 01/09/2014 04:58 PM, Sean Dague wrote: On 01/09/2014 04:12 PM, Dean Troyer wrote: On Thu, Jan 9, 2014 at 2:16 PM, Adam Young mailto:[email protected]>> wrote: That didn't seem to make a difference, still no cache. The RPMS are

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

On 09/01/14 23:56 +0100, Julien Danjou wrote: On Thu, Jan 09 2014, Jay Pipes wrote: Hope you don't mind, I'll jump in here :) On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: Hi Jeremy Don't you think it is burden for operators if we should choose correct combination of config for multip

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

Jay Pipes wrote: > Personally, I think sooner is better. The severity of the disruption is > quite high, and action is needed ASAP. Having the bug day organized shouldn't prevent people from working on the most pressing issues and get the disruption under control ASAP... I'm confident we'll be le

[openstack-dev] Not able to launch VM From Windows Server 2008 Template.

Hello All Please help me, I Export Template of Windows Server R2 2008 from XEN server as VHD file. Create a template in cloudstack with this VHD file I tried to launch an instance through this Template. After downloading template it tried to installed for half an hour after that, removes the templ

Re: [openstack-dev] Less option

Flavio Percoco wrote: > On 09/01/14 23:56 +0100, Julien Danjou wrote: >> I also think projects should try to minimize configuration options at >> their minimum so operators are completely lost. Opening the sample >> nova.conf and seeing 696 options is not what I would call user friendly. >> >> And

Re: [openstack-dev] [oslo.config] Centralized config management

On 09/01/14 13:28 -0500, Jay Pipes wrote: On Thu, 2014-01-09 at 10:23 +0100, Flavio Percoco wrote: On 08/01/14 17:13 -0800, Nachi Ueno wrote: >Hi folks > >OpenStack process tend to have many config options, and many hosts. >It is a pain to manage this tons of config options. >To centralize this

Re: [openstack-dev] Not able to launch VM From Windows Server 2008 Template.

Hi Mardan, Assuming that you meant openstack rather than cloudstack(!) then check out the guide at http://blogs.citrix.com/2012/09/06/vhd-to-openstack-using-a-xapi-host-plugin/. VHDs in OpenStack are actually a TGZ - since it can contain a VHD chain - with each VHD renamed to "0.vhd", "1.vhd"

[openstack-dev] [Murano] Bug Triage Event 2014-01-13 11:00 UTC

Hi everyone! This is the announcement of Murano Bug Triage Event that will be held at #murano channel at 11:00 UTC on Monday. Current bug state can be found in our launchpad page . See you there! Kate. ___ OpenSt

Re: [openstack-dev] [Savanna] Spark plugin status

Answers inlined. On Fri, Jan 10, 2014 at 1:05 PM, Daniele Venzano wrote: > On 01/09/14 19:12, Matthew Farrellee wrote: > >> This is definitely great news! >> >> +2 to the things Sergey mentioned below. >> >> Additionally, will you fill out the blueprint or wiki w/ details that >> will help othe

[openstack-dev] [Murano] Bug Triage Event 2014-01-13 11:00 UTC

Hi everyone! This is the announcement of Murano Bug Triage Event that will be held at #murano channel at 11:00 UTC on Monday. Current bug state can be found in our launchpad page . See you there! Kate. ___ OpenSt

Re: [openstack-dev] [nova] where to expose network quota

> -Original Message- > From: Robert Collins [mailto:[email protected]] > Sent: 10 January 2014 08:54 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] where to expose network quota > > On 8 January 2014 03:01, Christopher Yeo

Re: [openstack-dev] Less option

On 10/01/14 11:28 +0100, Thierry Carrez wrote: Flavio Percoco wrote: On 09/01/14 23:56 +0100, Julien Danjou wrote: I also think projects should try to minimize configuration options at their minimum so operators are completely lost. Opening the sample nova.conf and seeing 696 options is not wha

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

On Thu, 2014-01-09 at 16:34 -0800, Joe Gordon wrote: > On Thu, Jan 9, 2014 at 3:01 PM, Jay Pipes wrote: > > > On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: > > > On Thu, Jan 09 2014, Jay Pipes wrote: > > > > > > > Hope you don't mind, I'll jump in here :) > > > > > > > > On Thu, 2014-01

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

On 10 January 2014 07:40, Jiang, Yunhong wrote: > Robert, sorry that I’m not fan of * your group * term. To me, *your > group” mixed two thing. It’s an extra property provided by configuration, > and also it’s a very-not-flexible mechanism to select devices (you can only > select devices based o

Re: [openstack-dev] [Solum] Devstack gate is failing

On Wed, Jan 8, 2014 at 11:20 PM, Noorul Islam Kamal Malmiyoda wrote: > On Wed, Jan 8, 2014 at 11:02 PM, Sean Dague wrote: >> On 01/08/2014 11:40 AM, Noorul Islam Kamal Malmiyoda wrote: >>> >>> On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov" >>> mailto:[email protected]>> wrote: >>

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

In any case, we don't have to decide this now. If we simply allowed the whitelist to add extra arbitrary properties to the PCI record (like a group name) and return it to the central server, we could use that in scheduling for the minute as a group name, we wouldn't implement the APIs for flavors

[openstack-dev] [Glance][All] Pecan migration strategies

Greetings, More discussions around the adoption of Pecan. I'd like to know what is the feeling of other folks about migrating existing APIs to Pecan as opposed to waiting for a new API version as an excuse to migrate the API implementation to Pecan? We discussed this in one of the sessions at t

Re: [openstack-dev] [requirements] - taskflow preventing sqla 0.8 upgrade

On 01/10/2014 04:13 AM, Robert Collins wrote: On 5 January 2014 02:02, Sean Dague wrote: So we used to do that the apps against release libraries. And the result was more and more full day gate breaks. We did 2 consecutive ones in 2 weeks. Basically, once you get to be a certain level of coup

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On 01/10/2014 05:06 AM, Thierry Carrez wrote: Jay Pipes wrote: Personally, I think sooner is better. The severity of the disruption is quite high, and action is needed ASAP. Having the bug day organized shouldn't prevent people from working on the most pressing issues and get the disruption un

[openstack-dev] [Ceilometer] Aggregation discussion

Hi team, I've decided to move discussion about aggregation in mailing list. Here is a description about my idea and I really need your comments. *Idea:* The goal is to improve performance when user gets statistics for meter. Now we have fixed list of statistics (min, max and so on). During reques

Re: [openstack-dev] Devstack on Fedora 20

On Thu, Jan 9, 2014 at 10:27 PM, Adam Young wrote: > Tried wiping out the (installed) python-greenlet rpm and re running, and > that was not installed afterwards, either. I am guessing that the package > install step is getting skipped somehow, after the first run. > That sounds like you need

Re: [openstack-dev] Less option

On Fri, Jan 10, 2014 at 5:16 AM, Flavio Percoco wrote: > On 10/01/14 11:28 +0100, Thierry Carrez wrote: > >> Personally I think we should (and we can) say NO more often. As we get >> > stronger as a dev community it becomes easier, and I think we see more >> "opinionated" choices in younger proje

Re: [openstack-dev] [Openstack] [OpenStack][Sentry]

I've not read the blueprint yet, but I think we'll need another name for it. I'm sure lots of us are running this Sentry in prduction: https://github.com/getsentry/sentry Soren Hansen | http://linux2go.dk/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer

Re: [openstack-dev] [Solum][Pecan][Security] Pecan SecureController vs. Nova policy

Georgy, Pecan hook functions (http://pecan.readthedocs.org/en/latest/hooks.html) are passed a `state` argument, which has a couple of attributes you can make use of. Starting at the `before` hook, you have access to `state.controller`, which is the @pecan.expose() decorated controller/function

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

Apologies for this top post, I just want to move this discussion towards action. I am traveling next week so it is unlikely that I can make the meetings. Sorry. Can we please agree on some concrete actions, and who will do the coding? This also means raising new blueprints for each item of work.

Re: [openstack-dev] [oslo.config] Centralized config management

Excerpts from Doug Hellmann's message of 2014-01-09 12:21:05 -0700: > On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: > > > Hi folks > > > > Thank you for your input. > > > > The key difference from external configuration system (Chef, puppet > > etc) is integration with > > openstack services.

Re: [openstack-dev] [Nova] Detect changes in object model

> If an object A contains another object or object list (called > sub-object), any change happened in the sub-object can't be detected > by obj_what_changed() in object A. Well, like the Instance object does, you can override obj_what_changed() to expose that fact to the caller. However, I think

[openstack-dev] [Climate] Reminder: Meeting today at 1500 UTC

Hi folks, Please keep in mind that our weekly meeting changed its timeslot from Mondays to Fridays 1500 UTC. #openstack-meeting should be available at this time, booking it. -Sylvain ___ OpenStack-dev mailing list [email protected] http

[openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Hi everybody, there is first stab of Deployment Management section with future direction (note that it was discussed as a scope for Icehouse). I tried to add functionality in time and break it down to steps. This will help us to focus on one functionality at a time and if we will be in time

[openstack-dev] [Neutron] Building a new open source NFV system for Neutron

Howdy Stackers! We are developing a new open source Network Functions Virtualization driver for Neutron. I am writing to you now to ask for early advice that could help us to smoothly bring this work upstream into OpenStack Juno. The background is that we are open source developers working to sat

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Jarda, I love how this is progressing. It will be very nice once it's implemented! The iconography seems to be inconsistent. The "!" triangle is used for error conditions and warning conditions; and the "x" hexagon is also used for error conditions. For the Roles usage, will the user be a

Re: [openstack-dev] [wsme] Undefined attributes in WSME

On Thu, Jan 9, 2014 at 12:02 AM, Jamie Lennox wrote: > Is there any way to have WSME pass through arbitrary attributes to the > created object? There is nothing that i can see in the documentation or > code that would seem to support this. > > In keystone we have the situation where arbitrary data

[openstack-dev] Re-using Horizon bits in OpenDaylight

Hello everyone. I would like to know if anyone here has knowledge on how easy it is to use Horizon for something else then OpenStack things? I'm the starter of the "dlux" project that aims to consume the OpenDaylight SDN controller Northbound REST APIs instead of the integrated UI it has now. Tho

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

Thanks for the feedback :) = Stack = There is a single stack in Tuskar, the "overcloud". A small nit here: in the long term Tuskar will support multiple overclouds. Yes, absolutely. I should have added "For Icehouse" like I did in other places. Good catch. There's few pieces of concepts

Re: [openstack-dev] [Neutron][qa]API testing update

Sukhdev, Thanks for your comment. Eugene summarized very well the reason I didin't specify any testing dealing with the ml2 plugin. It Cheers On Thu, Jan 9, 2014 at 11:50 PM, Eugene Nikanorov wrote: > Sukhdev, > > API tests are really not for end-to-end testing; also, tempest tests (both > API

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

As much as the Tuskar Chassis model is lacking compared to the Tuskar Rack model, the opposite problem exists for each project's model of Node. In Tuskar, the Node model is pretty bare and useless, whereas Ironic's Node model is much richer. Thanks for looking that deeply into it :) So, it's n

Re: [openstack-dev] Re-using Horizon bits in OpenDaylight

I have used the Horizon framework for an application other than the OpenStack Dashboard and it worked really well. There is an effort to create a separation between the Horizon framework and the OpenStack Dashboard and once that happens it will be even easier. How hard or difficult it is will

[openstack-dev] [climate] Meeting minutes

Thank everyone who were on our Climate weekly meeting. Meeting minutes: Minutes: http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-01-10-15.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-01-10-15.00.txt Log: http://eavesdrop.openstack.or

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

+1 PCI Flavor. From: Jiang, Yunhong [mailto:[email protected]] Sent: January-10-14 1:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support BTW, I like the PCI flavor :) From: Jiang, Yunhong [mai

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

On 01/10/2014 04:27 PM, Jay Dobies wrote: Thanks for the feedback :) = Stack = There is a single stack in Tuskar, the "overcloud". A small nit here: in the long term Tuskar will support multiple overclouds. Yes, absolutely. I should have added "For Icehouse" like I did in other places. Good

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

On Fri, Jan 10, 2014 at 10:27 AM, Jay Dobies wrote: >> There's few pieces of concepts which I think is missing from the list: >> - overclouds: after Heat successfully created the stack, Tuskar needs to >> keep track whether it applied the post configuration steps (Keystone >> initialization, regis

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Thanks for recording this. A few questions: - I'm guessing the capacity metrics will come from Ceilometer. Will Ceilometer provide the averages for the role or is that calculated by Tuskar? - When on the change deployments screen, after making a change but not yet applying it, how are the pr

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

On Fri, Jan 10, 2014 at 11:01 AM, Imre Farkas wrote: > On 01/10/2014 04:27 PM, Jay Dobies wrote: >>> There's few pieces of concepts which I think is missing from the list: >>> - overclouds: after Heat successfully created the stack, Tuskar needs to >>> keep track whether it applied the post config

Re: [openstack-dev] [Nova] Detect changes in object model

Sounds good to me. The list base objects don't have methods to make changes to the list - so it would be a case of iterating looking at each object in the list. That would be ok. Do we need the contents of the lists to be modified without assigning a new list? - that would need a little more w

Re: [openstack-dev] [Nova] Detect changes in object model

> Sounds good to me. The list base objects don't have methods to make changes > to the list - so it would be a case of iterating looking at each object in > the list. That would be ok. Hmm? You mean for NovaObjects that are lists? I hesitate to expose lists as changed when one of the objects in

Re: [openstack-dev] [TripleO] Installing from packages in tripleo-image-elements

One more related idea related to real packages in TripleO. While I still think using packages is totally cool we may want to make an exception for systemd/upstart scripts. We have some non-standard ordering in our TripleO init scripts that is meaningful and blindly switching to a distro specific

Re: [openstack-dev] [Neutron] Building a new open source NFV system for Neutron

Hi Luke, Very pleased to see this initiative in the OpenStack/NFV space. A dumb question - how do you see this related to the ongoing "[openstack-dev] [nova] [neutron] PCI pass-through network support" discussion on this list? Do you see that work as one component within your proposed arch

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

On Fri, Jan 10, 2014 at 4:01 AM, Mark McLoughlin wrote: > On Thu, 2014-01-09 at 16:34 -0800, Joe Gordon wrote: > > On Thu, Jan 9, 2014 at 3:01 PM, Jay Pipes wrote: > > > > > On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: > > > > On Thu, Jan 09 2014, Jay Pipes wrote: > > > > > > > > > Ho

[openstack-dev] [Neutron] Partially Shared Networks

If anyone is giving any thought to networks that are available to multiple tenants (controlled by a configurable list of tenants) but not visible to all tenants I'd like to hear about it. I'm especially thinking of scenarios where specific networks exist outside of OpenStack and have specific p

[openstack-dev] [marconi] Ichouse roadmap and Graduation tracking

Hi folks, I put together a tracking blueprint for us to refer to in our team meetings: https://blueprints.launchpad.net/marconi/+spec/graduation Also, here is an outline of what I want to a accomplish for Icehouse: https://wiki.openstack.org/wiki/Marconi/roadmaps/icehouse Feedback is w

Re: [openstack-dev] Devstack on Fedora 20

That worked. I incorporated the FORCE_PREREQ=1 change and all good. On 01/10/2014 04:54 AM, Flavio Percoco wrote: On 09/01/14 23:27 -0500, Adam Young wrote: On 01/09/2014 04:58 PM, Sean Dague wrote: On 01/09/2014 04:12 PM, Dean Troyer wrote: On Thu, Jan 9, 2014 at 2:16 PM, Adam

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

Hi Yunhong, I appreciate your comments. Please see inline… --Robert On 1/10/14 1:40 AM, "Jiang, Yunhong" mailto:[email protected]>> wrote: Robert, sorry that I’m not fan of * your group * term. To me, *your group” mixed two thing. It’s an extra property provided by configuration, and al

Re: [openstack-dev] [oslo] Common SSH

On Wed, Jan 8, 2014 at 2:31 PM, Sergey Skripnick wrote: > > > >> >> On Wed, Jan 8, 2014 at 10:43 AM, Eric Windisch >>> wrote: >>> >> >> > > > About spur: spur is looks ok, but it a bit complicated inside (it uses > > separate threads for non-blocking stdin/stde

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

Hi Yongli, Please also see my response to Yunhong. Here, I just want to add a comment about your local versus global argument. I took a brief look at your patches, and the PCI-flavor is added into the whitelist. The compute node needs to know these pci-flavors in order to report PCI stats based

Re: [openstack-dev] [oslo] Common SSH

I appreciate that we want to fix the ssh client. I'm not certain that writing our own is the best >answer. I was supposed to fix oslo.processutils.ssh with this class, but it may be fixed without it, not big deal. In his comments on your pull request, the paramiko author recommended loo

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Hi, Thanks for the wireframes and the walkthrough. Very useful. I've a few comments. - I'd like to echo the comments from the recording about "Role" I think the term probably isn't specific enough but I don't have a great suggestion. However, this is probably suited better to the other threa

Re: [openstack-dev] [oslo] Common SSH

On Fri, Jan 10, 2014 at 12:54 PM, Sergey Skripnick wrote: > > I appreciate that we want to fix the ssh client. I'm not certain that >> writing our own is the best >answer. >> > > I was supposed to fix oslo.processutils.ssh with this class, but it may > be fixed without it, not big deal. > > > > >

Re: [openstack-dev] [Neutron] Building a new open source NFV system for Neutron

Hi Mike, On 10 January 2014 17:35, Michael Bright wrote: > Very pleased to see this initiative in the OpenStack/NFV space. Glad to hear it! > A dumb question - how do you see this related to the ongoing > "[openstack-dev] [nova] [neutron] PCI pass-through network support" > > discussion o

Re: [openstack-dev] [oslo] Common SSH

On Fri, Jan 10, 2014 at 12:54 PM, Sergey Skripnick wrote: I appreciate that we want to fix the ssh client. I'm not certain that writing our own is the >>>best >answer. I was supposed to fix oslo.processutils.ssh with this class, but it may be fixed without it, not big deal

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

Ian, thanks for your reply. Please check my response prefix with 'yjiang5'. --jyh From: Ian Wells [mailto:[email protected]] Sent: Friday, January 10, 2014 4:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through

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

Brian, the issue of 'class name' is because currently the libvirt does not provide such information, otherwise we are glad to add that :( But this is a good point and we have considered already. One solution is to retrieve it through some code like read the configuration space directly. But that

Re: [openstack-dev] [horizon] User registrations

Hi I've been thinking of ideas on how to fulfill this user self registration requirement for our startup's "private beta". So far, i'm of the opinion that storage of customer data (contacts, physical address, billing info, etc) by commercial entities can be handled by Keystone via extension(s), (

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

On 10 January 2014 15:30, John Garbutt wrote: > We seemed happy with the current system (roughly) around GPU passthrough: > nova flavor-key set > "pci_passthrough:alias"=" large_GPU:1,small_GPU:2" > nova boot --image some_image --flavor > Actually, I think we pretty solidly disagree on this p

Re: [openstack-dev] Not able to launch VM From Windows Server 2008 Template.

On 2014-01-10 04:21, Mardan Raghuwanshi wrote: > Hello All Please help me, > > I Export Template of Windows Server R2 2008 from XEN server as VHD file. > Create a template in cloudstack with this VHD file > I tried to launch an instance through this Template. > After downloading template

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day - Mon Jan 27th

On 10/01/14 04:30, Sean Dague wrote: > Minor correction, we're going to do this on Jan 27th, to be after the > i2 push, as I don't think there is time organize this prior. > >> Specifically I'd like to get commitments from as many PTLs as possible >> that they'll both directly participate in the d

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Another question: - A Role (sounds like we're moving away from that so I'll call it Resource Category) can have multiple Node Profiles defined (assuming I'm interpretting the + and the tabs in the Create a Role wireframe correctly). But I don't see anywhere where a profile is selected when sc

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

Hey Yunhong, The thing about 'group' and 'flavor' and 'whitelist' is that they once meant distinct things (and I think we've been trying to reduce them back from three things to two or one): - group: equivalent devices at a host level - use any one, no-one will care, because they're either identi

Re: [openstack-dev] [oslo] Common SSH

On Fri, Jan 10, 2014 at 1:32 PM, Sergey Skripnick wrote: > > > >> >> >> On Fri, Jan 10, 2014 at 12:54 PM, Sergey Skripnick < >> [email protected]> wrote: >> >> >>> >>> I appreciate that we want to fix the ssh client. I'm not certain that writing our own is the >>>best >answer.

Re: [openstack-dev] Re-using Horizon bits in OpenDaylight

I've also used the core Horizon bits for dashboards other than the OpenStack dashboard. I can't speak for any current bugs you may run into, but by-and-large the ability to create arbitrary dashboards, tables, workflows, etc. to interact with RESTful APIs works perfectly without the OpenStack bi

Re: [openstack-dev] [nova][documentation][devstack] Confused about how to set up a Nova development environment

On 01/09/2014 06:14 PM, Brant Knudson wrote: On Thu, Jan 9, 2014 at 12:21 PM, Mike Spreitzer > wrote: Brant Knudson mailto:[email protected]>> wrote on 01/09/2014 10:07:27 AM: > When I was starting out, I ran devstack ( http://devstack.org/) on >

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

+100 also :) 2014/1/10 Joe Gordon : > > > > On Fri, Jan 10, 2014 at 4:01 AM, Mark McLoughlin wrote: >> >> On Thu, 2014-01-09 at 16:34 -0800, Joe Gordon wrote: >> > On Thu, Jan 9, 2014 at 3:01 PM, Jay Pipes wrote: >> > >> > > On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: >> > > > On Thu

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Flavio, Clint I agree with you guys. sorry, may be, I wasn't clear. My opinion is to remove every configuration in the node, and every configuration should be done by API from central resource manager. (nova-api or neturon server etc). This is how to add new hosts, in cloudstack, vcenter, and

[openstack-dev] [savanna] team meeting minutes Jan 9

Thanks everyone who have joined Savanna meeting. Here are the logs from the meeting: Minutes: savanna.2014-01-09-18.10.html Log: savanna.2014-01-09-18.10.log.html

Re: [openstack-dev] [Neutron] Partially Shared Networks

On Fri, 2014-01-10 at 17:06 +, CARVER, PAUL wrote: > If anyone is giving any thought to networks that are available to > multiple tenants (controlled by a configurable list of tenants) but > not visible to all tenants I’d like to hear about it. > > I’m especially thinking of scenarios where sp

[openstack-dev] [Neutron][qa] The 'spec' parameter of mock.patch()

I recently saw a case [1] where a misspelled assertion method (asoptt_called_once_with vs assert_called_once_with) did not result in a test failure because the object it was called on was created by mock.patch() without any of the spec/spec_set/autospec parameters being set. Might it make sense

[openstack-dev] [Doc] What's Up Doc? Jan 10 2014

Happy new year everyone. We're hitting the books with a vengeance in 2014. See my 2013 roundup at http://www.openstack.org/blog/2014/01/openstack-documentation-wrap-up-for-2013/ . 1. In review and merged this past week: I'm pleased to announce a refresh on the API Reference listing page thanks to

Re: [openstack-dev] [Neutron][qa] The 'spec' parameter of mock.patch()

+1 but fixing this looks like take not small time 2014/1/10 Maru Newby : > I recently saw a case [1] where a misspelled assertion method > (asoptt_called_once_with vs assert_called_once_with) did not result in a test > failure because the object it was called on was created by mock.patch() > wi

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

Ian, thanks for your reply. Please check comments prefix with [yjiang5]. Thanks --jyh From: Ian Wells [mailto:[email protected]] Sent: Friday, January 10, 2014 12:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-thr

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

On 11 January 2014 00:04, Jiang, Yunhong wrote: > [yjiang5] Really thanks for the summary and it is quite clear. So what’s > the object of “equivalent devices at host level”? Because ‘equivalent > device * to an end user *” is flavor, so is it ‘equivalent to **scheduler**” > or ‘equivalent to **

Re: [openstack-dev] [Neutron] Building a new open source NFV system for Neutron

Hey Luke, If you look at the passthrough proposals, the overview is that part of the passthrough work is to ensure there's an PCI function available to allocate to the VM, and part is to pass that function on to the Neutron plugin via conventional means. There's nothing that actually mandates tha

[openstack-dev] The extra_resource in compute node object

Hi, Paul/Dan For the extra_resource (refer to Dan's comments in https://review.openstack.org/#/c/60258/ for more information), I created a patch set https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:extra_resources,n,z and want to get some feedback.

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

I have to use [yjiang5_1] prefix now :) --jyh From: Ian Wells [mailto:[email protected]] Sent: Friday, January 10, 2014 3:55 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support On 11 January 2014

[openstack-dev] [Swift] Metadata Search API

Rebooting this thread now that I've reorg'd the Wiki page. The proposed REST API spec for searching system and custom metadata in Swift, across accounts, containers, and objects, is now posted at: https://wiki.openstack.org/wiki/MetadataSearchAPI I've also made the first modification to the API

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

> > OK - so if this is good then I think the question is how we could change the 'pci_whitelist' parameter we have - which, as you say, should either *only* do whitelisting or be renamed - to allow us to add information. Yongli has something along those lines but it's not flexible and it distingui

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 2014-01-10 22:00:40 +1300 (+1300), Robert Collins wrote: [...synchronized .gitignore across all projects...] > Out of curiousity, why wouldn't it work? The example I gave earlier in the thread... one project wants autogenerated ChangeLog so it's in their .gitignore but another project wants a h

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 2014-01-10 21:57:33 +1300 (+1300), Robert Collins wrote: > I have *no* aversion to allowing contributors to police things on > their own. [...] I know you don't. It was stated in the message I was replying to (in context you trimmed) that "...the community should not accept or promote any polic

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 11 January 2014 15:39, Jeremy Stanley wrote: > On 2014-01-10 22:00:40 +1300 (+1300), Robert Collins wrote: > [...synchronized .gitignore across all projects...] >> Out of curiousity, why wouldn't it work? > > The example I gave earlier in the thread... one project wants > autogenerated ChangeLo

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

I believe my comment may have been [slightly] misinterpreted. I was simply saying that we shouldn't assume that contributors are allowed to alter their global configuration. When deciding on a policy for ignoring files, we should be careful to choose a policy that does not prevent those users fr

Re: [openstack-dev] [OpenStack-Dev] IDE extensions in .gitignore

On 2014-01-11 03:38:05 + (+), Sam Harwell wrote: > I believe my comment may have been [slightly] misinterpreted. Sorry about that! The wording seemed unnecessarily proscriptive. > I was simply saying that we shouldn't assume that contributors are > allowed to alter their global configurat

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

Comments with prefix [yjiang5_2] , including the double confirm. I think we (you and me) is mostly on the same page, would you please give a summary, and then we can have community , including Irena/Robert, to check it. We need Cores to sponsor it. We should check with John to see if this is di

[openstack-dev] [Horizon][Tuskar] Tuskar-UI navigation

Hey all, I have a question regarding the development of the tuskar-ui navigation. So, to give some background: we are currently working off the wireframes that Jaromir Coufal has developed: http://people.redhat.com/~jcoufal/openstack/tripleo/2013-12-03_tripleo-ui_02-resources.pdf In these wire

  1   2   >