Re: [openstack-dev] [magnum][bp] Power Magnum to run on metalwith Hyper

Hi Jay, Yes, we are working with the community to integrate Hyper with Mesos and K8S. Since Hyper uses Pod as the default job unit, it is quite easy to integrate with K8S. Mesos takes a bit more efforts, but still straightforward. We expect to finish both integration in v0.4 early August. Best, Pen

Re: [openstack-dev] [neutron] Should we document the using of "device:owner" of the PORT ?

What do you think of just blocking all PUTs to that field? Is that a feasible change without inducing widespread riots about breaking changes? On Thu, Jul 16, 2015 at 2:53 AM, Salvatore Orlando wrote: > It is not possible to constrain this attribute to an enum, because there > is no fixed list o

Re: [openstack-dev] [tc][all] Tags, explain like I am five?

Joshua Harlow wrote: >> Tags can be proposed by anyone, not only by the TC and they get >> discussed and voted on gerrit. The proposed tags need to be as objective >> as possible. And there is a working group >> (https://etherpad.openstack.org/p/ops-tags-June-2015) among operators >> trying to defi

Re: [openstack-dev] [Fuel] Getting rid of upgrade tarball

Hi, Vladimir, I like the initiative, just to add some steps: 10) patch to fuel-qa/ and jenkins jobs to change the workflow of upgrades tests, 11) clarification on how upgrade should be tested (against which repositories and ISO images), how update of upgrade rpm should be tested 12) documentation

Re: [openstack-dev] Please add add 'Fuel' to list topic categories

Qiming Teng wrote: > I believe we are all receiving a large number of Fuel related messages > everyday, but not all of us have the abundant bandwidth to read them. > Maybe we can consider adding 'Fuel' to the topic categories we can check > on/off when customising the subscription. > > Currently,

Re: [openstack-dev] [neutron] Should we document the using of "device:owner" of the PORT ?

It is not possible to constrain this attribute to an enum, because there is no fixed list of device owners. Nevertheless it's good to document know device owners. Likewise the API layer should have checks in place to ensure accidental updates to this attributes do not impact control plane function

Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

+1 On Thu, Jul 16, 2015 at 2:04 AM, Brian Haley wrote: > +1 > > > On 07/15/2015 02:47 PM, Carl Baldwin wrote: > >> As the Neutron L3 Lieutenant along with Kevin Benton for control >> plane, and Assaf Muller for testing, I would like to propose Cedric >> Brandily as a member of the Neutron core r

Re: [openstack-dev] [Fuel] Getting rid of upgrade tarball

By the way, first step for this to happen is to move stackforge/fuel-web/fuel_upgrade_system into a separate repository. Fortunately, this directory is not the place where the code is continuously changing (changes are rather seldom) and moving this project is going to barely affect the whole deve

Re: [openstack-dev] [nova] Why is osapi_v3.enabled = False by default?

FYI, this should be part work of https://github.com/openstack/nova-specs/blob/master/specs/liberty/approved/nova-api-remove-v3.rst 2015-07-16 16:27 GMT+08:00 Alex Xu : > > > 2015-07-16 7:54 GMT+08:00 Ken'ichi Ohmichi : > >> 2015-07-16 3:03 GMT+09:00 Sean Dague : >> > On 07/15/2015 01:44 PM, Matt

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

2015-07-15 22:57 GMT+08:00 Matt Riedemann : > > > On 7/15/2015 3:24 AM, Alex Xu wrote: > >> >> >> 2015-07-15 5:14 GMT+08:00 Matt Riedemann > >: >> >> >> >> >> On 7/14/2015 3:43 PM, Cale Rath wrote: >> >> Hi, >> >> I created a patch to fail on

Re: [openstack-dev] [nova] Why is osapi_v3.enabled = False by default?

2015-07-16 7:54 GMT+08:00 Ken'ichi Ohmichi : > 2015-07-16 3:03 GMT+09:00 Sean Dague : > > On 07/15/2015 01:44 PM, Matt Riedemann wrote: > >> The osapi_v3.enabled option is False by default [1] even though it's > >> marked as the CURRENT API and the v2 API is marked as SUPPORTED (and > >> we've fro

[openstack-dev] [neutron][port-security]Could not create vm in network with the port-security-enabled=False

Hi all, I could use the feature port-security-enabled on port. When I create net and subnet neutron net-create net2 --port-security-enabled=False neutron subnet-create net2 6.6.6.0/24 --enable-dhcp=False --name subnet2 it works well. Then i create

[openstack-dev] [Fuel] Getting rid of upgrade tarball

Dear colleagues, I'd like to suggest to get rid of Fuel upgrade tarball and convert this thing into fuel-upgrade rpm package. Since we've switched to online rpm/deb based upgrades, it seems we can stop packaging rpm/deb repositories and docker containers into tarball and instead package upgrade py

Re: [openstack-dev] [magnum][bp] Power Magnum to run on metalwith Hyper

Hi Peng, Just want to get more for Hyper. If we create a hyper bay, then can I set up multiple hosts in a hyper bay? If so, who will do the scheduling, does mesos or some others integrate with hyper? I did not find much info for hyper cluster management. Thanks. 2015-07-16 9:54 GMT+08:00 Peng

Re: [openstack-dev] [Neutron]Request for help to review a patch

As it is a bug fix, perhaps you could add this to the agenda for the next Neutron IRC meeting, in the Bugs section?Regards,       Neil  

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

+ 1 about server_type. I also think it is OK. Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan） IBM China System and Technology Lab, Beijing E-mail: wk...@cn.ibm.com Tel: 86-10-82451647 Address: Building 28(Ring Buil

[openstack-dev] [manila][puppet-manila] Support to configure GlusterFS drivers with Manila shares.

Hi, This patch [1] adds support to configure GlusterFS drivers (both NFS and GlusterFS-Native/FUSE) with Manila shares. I've tested the patch, using packstack patch [2] No obvious errors, looks good. Requesting to review the patch. [1] https://review.openstack.org/#/c/200811/ [2] https://revi

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

I’d be comfortable with server_type. Adrian On Jul 15, 2015, at 11:51 PM, Jay Lau mailto:jay.lau@gmail.com>> wrote: After more thinking, I agree with Hongbin that instance_type might make customer confused with flavor, what about using server_type? Actually, nova has concept of server gro

<    1   2