Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV binding of ports

Hi Irena, My MD has to take care of admin state changes since I have no L2 agent. I think that is what Bob also alluded to. That being said, I am not doing anything specific to handle admin_state_up/down. The SR-IOV port on my device is always going to be up, for now atleast. Thanks, Sandhya

[openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

Hello, Recently, I found a serious issue about network-nodes startup time, neutron-rootwrap eats a lot of cpu cycles, much more than the processes it's wrapping itself. On a database with 1 public network, 192 private networks, 192 routers, and 192 nano VMs, with OVS plugin: N

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

On 03/05/2014 08:52 AM, Christopher Lefelhocz wrote: > I like this plan as it addresses my primary concern of getting deployments > comfortable with the transition. > > We don't mention SDKs in the plan. It seems like getting at least one SDK > to use v3 would provide us additional data in the tr

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

On Tue, Mar 04 2014, Joe Gordon wrote: > So since tools/config/check_uptodate.sh is oslo code, I assumed this > issue falls into the domain of oslo-incubator. > > Until this gets resolved nova is considering > https://review.openstack.org/#/c/78028/ Removing tools/config/oslo.config.generator.rc

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

On Wed, 2014-03-05 at 05:43 +, Kenichi Oomichi wrote: > > -Original Message- > > From: Dan Smith [mailto:d...@danplanet.com] > > Sent: Wednesday, March 05, 2014 9:09 AM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Nova] Concrete

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

I like this plan as it addresses my primary concern of getting deployments comfortable with the transition. We don't mention SDKs in the plan. It seems like getting at least one SDK to use v3 would provide us additional data in the transition. There is clear risk associated with that, but it may

Re: [openstack-dev] [Cinder] Status of multi-attach-volume work

Hi, We decided multi-attach feature must be implemented as an extension to core functionality in Cinder, but currently we have not a clear extension support in Cinder, IMO it's the biggest blocker now. And the other issues have been listed at https://wiki.openstack.org/wiki/Cinder/blueprints/multi

Re: [openstack-dev] [Tempest - Stress Test][qa] : implement a full SSH connection on "ssh_floating.py" and improve it

>>I mean we still have the tempest/stress/actions/ and we could put something >>like that in there. In general I would like to discuss this topic in the next >>QA meeting.. >>@Julien: are you able to join the next meeting? It would be 22:00 UTC. >@Marc : so next Thrusday (3/6/2014) ? Yes I can b

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On Mon, Mar 03, 2014 at 09:19:34AM +0100, Radomir Dopieralski wrote: > On 27/02/14 11:52, Petr Blaho wrote: > > > I agree with you w/r/t to indirection when accessing data but I like the > > idea that when I look at json repsonse I see what type of resource it > > is. That wrapper element describe

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV binding of ports

Hi Robert, Sandhya, I have pushed the reference implementation SriovAgentMechanismDriverBase as part the following WIP: https://review.openstack.org/#/c/74464/ The code is in mech_agent.py, and very simple code for mech_sriov_nic_switch.py. Please take a look and review. BR, Irena -Origina

[openstack-dev] [Murano] Need to fix issues with OpenStack Global Requirements

Hi team, We have some issues with the requirements for different Murano components: link I suggest to discuss these issues in etherpad: https://etherpad.openstack.org/p/MuranoRequi

Re: [openstack-dev] [heat]Policy on upgades required config changes

On Tue, Mar 04, 2014 at 02:06:16PM -0800, Clint Byrum wrote: > Excerpts from Steven Hardy's message of 2014-03-04 09:39:21 -0800: > > Hi all, > > > > As some of you know, I've been working on the instance-users blueprint[1]. > > > > This blueprint implementation requires three new items to be add

[openstack-dev] [Cinder] Status of multi-attach-volume work

Hi What is the current status of the work around multi-attach-volume [1]? We have some cluster related use cases that would benefit from being able to attach a volume from several instances. [1] https://wiki.openstack.org/wiki/Cinder/blueprints/multi-attach-volume Best regards Niklas Widell Eri

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

On 03/04/2014 10:44 PM, Christopher Yeoh wrote: > On Tue, 04 Mar 2014 16:09:21 -0800 > Dan Smith wrote: > >>> What I'd like to do next is work through a new proposal that >>> includes keeping both v2 and v3, but with a new added focus of >>> minimizing the cost. This should include a path away f

Re: [openstack-dev] [Mistral] DSL model vs. DB model, renaming

I think today and I have a good name for package (instead of 'mistral/model') How do you think about to name it 'mistral/workbook'? I.e., It means that it contains modules for work with workbook representation - tasks, services, actions and workflow. This way we able to get rid of any confusing.

[openstack-dev] ALIAS for Domain Quota Management in Nova

Hi, I have implemented the Nova V2 and V3 APIs for Domain Quota Management. But what i want to know whether is there any standard in using the ALIAS for the URLs. For example, i thought of using "domain-quota-sets" or "os-domain-quota-sets". Can any body tell me whether i can use ALIAS like th

Re: [openstack-dev] Incubation Request: Murano

Forgot to provide the email addresses of Paul and Simon in my last mail: paul.lip...@ca.com smo...@de.ibm.com Regards, Thomas > From: Thomas Spatzier/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 05/03/2014 10:21 > Subject: Re: [openstack-dev

Re: [openstack-dev] Incubation Request: Murano

Hi Stan, thanks for sharing your thoughts about Murano and relation to TOSCA. I have added a few comments below. > From: Stan Lagun > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 05/03/2014 00:51 > Subject: Re: [openstack-dev] Incubation Request: Murano > > Hi al

Re: [openstack-dev] [nova] Questions about guest NUMA and memory binding policies

Hi Liuji, I'm the owner of bp support-libvirt-vcpu-topology, There are four main reasons that I did not continue to work on it: 1. the design proposal has not confirmed by core developers of nova 2. this bp is not accepted in Icehouse development stage 3. Daniel expects that this bp should co

Re: [openstack-dev] Incubation Request: Murano

Georgy Okrokvertskhov wrote on 05/03/2014 00:32:08: > From: Georgy Okrokvertskhov > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 05/03/2014 00:34 > Subject: Re: [openstack-dev] Incubation Request: Murano > > Hi Thomas, Zane, > > Thank you for bringing TOSCA to th

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

Well I use a 8 cores 128G RAM physical host :) I did not see much of the CPU consumption for these 100 containers, so I suspect we can use less resources. > -Message d'origine- > De : David Peraza [mailto:david_per...@persistentsys.com] > Envoyé : lundi 3 mars 2014 20:27 > À : OpenStack De

Re: [openstack-dev] [3rd party testing] How to setup CI? Take #2

On 4 March 2014 17:07, Jay Pipes wrote: > I would advise dropping the custom CI setup and going with a method that > specifically uses the upstream openstack-dev/devstack and > openstack-infra/devstack-gate projects. > This sounds great to me. Thank you for all the work you are doing on simplify

<    1   2