Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

On Fri, Aug 26, 2016 at 09:48:26AM -0700, Clark Boylan wrote: > On Fri, Aug 26, 2016, at 09:03 AM, Joshua Harlow wrote: > > Hi folks (dev and more!), > > > > I was having a conversation with some folks at godaddy around our future > > plans for a developer lab (where we can have various setups

Re: [openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey on irc)

+1. Great work Dave! Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date:

[openstack-dev] [Neutron][Nova] Neutron mid-cycle summary report

Hi Neutrinos, For those of you who couldn't join in person, please find a few notes below to capture some of the highlights of the event. I would like to thank everyone one who helped me put this report together, and everyone who helped make this mid-cycle a fruitful one. I would also like to

[openstack-dev] [tripleo] FFE request for Manila integration

The 3 patches we need to wrap up the Manila integration for TripleO still haven't gotten enough review attention to merge: https://review.openstack.org/#/c/354019 https://review.openstack.org/#/c/354014 https://review.openstack.org/#/c/355394 Since it looks like the Feature Freeze is going to

Re: [openstack-dev] [kolla] OSIC scale testing

Steve and I just setup and kicked off Scenario #4. The Rally test suite is running now. This is "Fourth Deployment" from https://etherpad.openstack.org/p/kolla-N-midcycle-osic This deployment is with two VIPs and TLS is configured on the external VIP. Nodes: 3 control, 12 storage (with ceph),

[openstack-dev] [kolla] OSIC scale testing

Hey folks, We have nearly automated all of the OSIC testing and there are instructions to follow in NEXTSTEPS. They take about 1 hour to execute (to setup a test0 and then all done. We have the cluster until the 30th. I need folks that have access to help out as much as possible between now

Re: [openstack-dev] [tripleo] FFE request for Manila integration

On Sat, Aug 27, 2016 at 12:26:51AM -0400, Ben Swartzlander wrote: > The 3 patches we need to wrap up the Manila integration for TripleO still > haven't gotten enough review attention to merge: > > https://review.openstack.org/#/c/354019 > https://review.openstack.org/#/c/354014 >

Re: [openstack-dev] [tempest][cinder] Clone feature toggle not in clone tests

He is mentioning about the Cinder side: https://review.openstack.org/# /c/147186/ On Fri, Aug 26, 2016 at 7:01 AM, Jordan Pittier wrote: > > > On Thu, Aug 25, 2016 at 7:06 PM, Ben Swartzlander > wrote: > >> Originally the NFS driver did

Re: [openstack-dev] [nova] VM console for VMware instances

On Fri, Aug 26, 2016, at 04:16 AM, Radoslav Gerganov wrote: > On 25.08.2016 18:25, Andrew Laski wrote: > > Is there a reason this has not been proposed to the Nova project, or > > have I missed that? I looked for a proposal and did not see one. > > > > The main reason I developed this out of

Re: [openstack-dev] [Openstack-operators] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016, at 03:44 AM, kostiantyn.volenbovs...@swisscom.com wrote: > Hi, > option 1 (=that's what patches suggest) sounds totally fine. > Option 3 > Allow block device mappings, when present, to mostly determine > instance packing > sounds like option 1+additional logic (=keyword

Re: [openstack-dev] [nova] VM console for VMware instances

On 25.08.2016 18:25, Andrew Laski wrote: > Is there a reason this has not been proposed to the Nova project, or > have I missed that? I looked for a proposal and did not see one. > The main reason I developed this out of tree is that reviewing patches in Nova takes forever. For example this

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting Aug. 26 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-08-26-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-08-26-08.00.txt Log:

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Thu, 25 Aug 2016, Sylvain Bauza wrote: Of course, long-term, we could try to see how to have composite flavors for helping users to not create a whole handful of flavors for quite the same user requests, but that would still be flavors (or the name for saying a flavor composition).

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

+1, great job! 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya : > +1 > > On 25.08.2016 21:08, Stanislaw Bogatkin wrote: > > +1 > > > > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko > > > wrote: > > > > +1 > > > >

Re: [openstack-dev] [Openstack-operators] [Nova] Reconciling flavors and block device mappings

Hi, option 1 (=that's what patches suggest) sounds totally fine. Option 3 > Allow block device mappings, when present, to mostly determine instance packing sounds like option 1+additional logic (=keyword 'mostly') I think I miss to understand the part of 'undermining the purpose of the

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Thu, 25 Aug 2016, Andrew Laski wrote: Allow block device mappings, when present, to mostly determine instance packing. By that I mean that the scheduler only takes into account local disk that would be consumed, but we add additional configuration to Nova which limits the number of instance

Re: [openstack-dev] [TripleO] New bug tagging policy

Hi Steve, On 25 August 2016 at 23:41, Steve Baker wrote: > On 25/08/16 22:30, Julie Pichon wrote: >> >> Hi folks, >> >> The bug tagging proposal has merged, behold the new policy: >> >> >> http://specs.openstack.org/openstack/tripleo-specs/specs/policy/bug-tagging.html >> >>

Re: [openstack-dev] [tempest][cinder] Clone feature toggle not in clone tests

On Thu, Aug 25, 2016 at 7:06 PM, Ben Swartzlander wrote: > Originally the NFS driver did support snapshots, but it was implemented by > just 'cp'ing the file containing the raw bits. This works fine (if > inefficiently) for unattached volumes, but if you do this on an

[openstack-dev] [new][keystone] pycadf 2.4.0 release (newton)

We are mirthful to announce the release of: pycadf 2.4.0: CADF Library This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/pycadf With package available at: https://pypi.python.org/pypi/pycadf Please report issues

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

On Fri, Aug 26, 2016, at 10:43 AM, John Villalovos wrote: > On Fri, Aug 26, 2016 at 9:48 AM, Clark Boylan > wrote: > > As someone that semi frequently has to reproduce gate results my current > > setup involves semi frequently building the infra test images locally > > using

Re: [openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

On 08/26/2016 02:04 PM, James Slagle wrote: On Fri, Aug 26, 2016 at 12:14 PM, Steven Hardy wrote: 1. Mistral API We've made good progress on this over recent weeks, but several patches remain - this is the umbrella BP, and it links several dependent BPs which are mostly

[openstack-dev] [Manila] FFE for "HPE 3PAR Pool feature"

Hello all , I am requesting you all to grant me an exception for Pools feature for HPE 3PAR driver. The patch that implements this feature is: https://review.openstack.org/#/c/329552/ implementing blueprint blueprint

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

On Fri, Aug 26, 2016 at 9:48 AM, Clark Boylan wrote: > As someone that semi frequently has to reproduce gate results my current > setup involves semi frequently building the infra test images locally > using openstack-infra/project-config/tools/build-image.sh then booting >

Re: [openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

On Fri, Aug 26, 2016 at 12:14 PM, Steven Hardy wrote: > > 1. Mistral API > > We've made good progress on this over recent weeks, but several patches > remain - this is the umbrella BP, and it links several dependent BPs which > are mostly posted but need code reviews, please

Re: [openstack-dev] [tacker] Proposing Yong Sheng Gong for Tacker core team

We have enough votes to proceed. Yong - welcome to the Tacker core team! - Sridhar On Tue, Aug 23, 2016 at 12:06 PM, Stephen Wong wrote: > +1 > > On Tue, Aug 23, 2016 at 8:55 AM, Sridhar Ramaswamy > wrote: > >> Tackers, >> >> I'd like to propose

Re: [openstack-dev] [Openstack-operators] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016, at 11:01 AM, John Griffith wrote: > > > On Fri, Aug 26, 2016 at 7:37 AM, Andrew Laski > wrote: >> >> >> On Fri, Aug 26, 2016, at 03:44 >> AM,kostiantyn.volenbovs...@swisscom.com >> wrote: >> > Hi, >> > option 1 (=that's what patches suggest) sounds

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Aug 25, 2016, at 3:19 PM, Andrew Laski wrote: > One other thing to note is that while a flavor constrains how much local > disk is used it does not constrain volume size at all. So a user can > specify an ephemeral/swap disk <= to what the flavor provides but can > have an

Re: [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016 at 10:20 AM, Ed Leafe wrote: > On Aug 25, 2016, at 3:19 PM, Andrew Laski wrote: > > > One other thing to note is that while a flavor constrains how much local > > disk is used it does not constrain volume size at all. So a user can > >

Re: [openstack-dev] [Openstack-operators] [Nova] Reconciling flavors and block device mappings

On 26 Aug 2016, at 17:44, Andrew Laski > wrote: On Fri, Aug 26, 2016, at 11:01 AM, John Griffith wrote: On Fri, Aug 26, 2016 at 7:37 AM, Andrew Laski > wrote: On Fri, Aug 26, 2016, at 03:44

[openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

Hi all, There have been some discussions on $subject recently, so I wanted to give a status update. Next week we will tag our newton-3 release, and we're currently working to either land or defer the remaining features tracked here: https://launchpad.net/tripleo/+milestone/newton-3 We need to

Re: [openstack-dev] [tripleo] collaboration request with vendors

On Thu, Aug 25, 2016 at 5:53 PM, Qasim Sarfraz wrote: > Steven/Emilien, > > PLUMgrid will be happy to collaborate in the effort. A much needed effort > for healthy integration of vendors with TripleO. > > What level of commitment would be expected from our side for this

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

On Fri, Aug 26, 2016, at 09:03 AM, Joshua Harlow wrote: > Hi folks (dev and more!), > > I was having a conversation with some folks at godaddy around our future > plans for a developer lab (where we can have various setups of > networking, compute, storage...) for 'exploring' purposes (testing

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

As someone that semi frequently has to reproduce gate results my current setup involves semi frequently building the infra test images locally using openstack-infra/project-config/tools/build-image.sh then booting this image on my workstation using kvm. With that I can easily run a

Re: [openstack-dev] [TripleO][CI] Need more undercloud resources

On Thu, Aug 25, 2016 at 9:49 AM, James Slagle wrote: > On Thu, Aug 25, 2016 at 5:40 AM, Derek Higgins wrote: >> On 25 August 2016 at 02:56, Paul Belanger wrote: >>> On Wed, Aug 24, 2016 at 02:11:32PM -0400, James Slagle wrote:

[openstack-dev] [release] stable/newton branching schedule

I plan to create the stable/newton branches for non-client libraries on Monday based on the most recently tagged versions according to the deliverable files in openstack/releases. If you *know* you are going to need a bug fix release and want me to hold off, please speak up before Monday morning

Re: [openstack-dev] [all] versioning the api-ref?

On Fri, Aug 26, 2016 at 7:46 AM, Bashmakov, Alexander < alexander.bashma...@intel.com> wrote: > Any more feedback on this? > Hi, I've added a comment on the review. For now, inline text descriptions are best for the context of what you're adding in that particular place. Anne > > > On Aug 18,

[openstack-dev] A daily life of a dev in ${name_your_fav_project}

Hi folks (dev and more!), I was having a conversation with some folks at godaddy around our future plans for a developer lab (where we can have various setups of networking, compute, storage...) for 'exploring' purposes (testing out a new LBAAS for example or ...) and as well as for

Re: [openstack-dev] [all] versioning the api-ref?

Any more feedback on this? > On Aug 18, 2016, at 10:30 AM, Bashmakov, Alexander > wrote: > > Concrete example of an api-ref difference between Mitaka and Newton: > https://review.openstack.org/#/c/356693/1/api-ref/source/v2/images-parameters.yaml > >

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 08/25/2016 01:13 PM, Steve Martinelli wrote: The keystone team is pursuing a trigger-based approach to support rolling, zero-downtime upgrades. The proposed operator experience is documented here: http://docs.openstack.org/developer/keystone/upgrading.html This differs from Nova and

Re: [openstack-dev] [Openstack-operators] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016 at 7:37 AM, Andrew Laski wrote: > > > On Fri, Aug 26, 2016, at 03:44 AM, kostiantyn.volenbovs...@swisscom.com > wrote: > > Hi, > > option 1 (=that's what patches suggest) sounds totally fine. > > Option 3 > Allow block device mappings, when present, to

Re: [openstack-dev] [cinder] [neutron] [ironic] [api] [doc] API status report

Hi cinder block storage peeps: I haven't heard from you on your comfort level with publishing so I went ahead and made the publishing job myself with this review: https://review.openstack.org/361475 Please let me know your thoughts there. Is the document ready to publish? Need anything else to

[openstack-dev] [nova] [os-vif] [neutron] Race in setting up linux bridge

Folks, Today I spotted [1]. It turns out Neutron and Nova might be racing trying to set up the bridge to provide VM with connectivity/dhcp. In the observed failure mode, os-vif fails in [2]. I suppose we might need to protect the bridge creation and make it handle the potential exception. We

Re: [openstack-dev] [freezer] Core team updates

+1 -- Deklan Dieterly Senior Systems Software Engineer HPE On 8/25/16, 9:33 AM, "Mathieu, Pierre-Arthur" wrote: >Hello, > >I would like to propose some modifications regarding the Freezer core >team. > >First, the removal of two inactive members: > -

Re: [openstack-dev] [Manila] FFE for "HPE 3PAR Pool feature"

On 08/26/2016 02:38 PM, Mehta, jay wrote: Hello all , I am requesting you all to grant me an exception for Pools feature for HPE 3PAR driver. The patch that implements this feature is: https://review.openstack.org/#/c/329552/implementing blueprint blueprint hpe3par-pool-support

[openstack-dev] [api] [all] New landing page for API docs collection

Hi all, I've put together a solution for your review to replace developer.openstack.org/api-ref.html with a new landing page. My idea is to repurpose this page: http://developer.openstack.org/api-guide/quick-start/ as a collection point for all the API information. Once this lands, I will redirect

[openstack-dev] [oslo][all] Oslo releases for newton

Hi all, Since its that time of the cycle the following is upon us: 'Final release for non-client libraries' (Aug 22 - 26) So I just wanted to thank all those who have put a lot of hard work into the various olso libraries and denote that going forward we (as a group) should try to work on

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

+1 On 25.08.2016 21:08, Stanislaw Bogatkin wrote: > +1 > > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko > > wrote: > > +1 > > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko >