Re: [openstack-dev] [Heat] Heat template example repository

Hi Lance, I am also interested to assisting you on this. Thanks Mohan On 11-May-2017 2:25 am, "Lance Haig" wrote: > Hi, > > I would like to introduce myself to the heat team. > > My name is Lance Haig I currently work for Mirantis doing workload > onboarding to openstack. > >

Re: [openstack-dev] [neutron] multiple vlan provider and tenant networks at the same time?

There are two steps to how this information is used: Step 1: create a network - the type driver config on the neutron-server host will determine which physnet and VLAN ID to use when you create it. It gets stored in the DB. No networking is actually done, we're just making a reservation here.

Re: [openstack-dev] [Ceilometer]

On 09/05/17 10:08 AM, simona marinova wrote: > The Alarming service doesn't work at this point. For example the > command "ceilometer alarm-list" gives the error: > > you should be using aodhclient if you have aodh. > > Now my biggest concern is that the Alarming service database >

Re: [openstack-dev] [neutron] multi-site forum discussion

Hello, Neutron cells aware is not equal to multi-site. There are lots of multi-site deployment options, not limited to nova-cells, whether to use Neutron-cells/Nova-cells in multi-site deployments, it's up to cloud operator's choice. For the bug[3], it's reasonable to make neutron support

Re: [openstack-dev] [neutron] multi-site forum discussion

On 12 May 2017 at 11:47, Morales, Victor wrote: > Armando, > > > > I noticed that Tricircle is mentioned there. Shouldn’t be better to > extend its current functionality or what are the things that are missing > there? > Tricircle aims at coordinating independent

[openstack-dev] [neutron]

Hi folks, At the summit we had a discussion on how to expand get-me-a-network [1]. A few main points were collected during the session: * Make get-me-a-network work with Horizon; * Make get-me-a-network able to auto-assign floating IPs; * Make get-me-a-network able to work with any network

Re: [openstack-dev] [neutron] multi-site forum discussion

Armando, I noticed that Tricircle is mentioned there. Shouldn’t be better to extend its current functionality or what are the things that are missing there? Regards, Victor Morales From: "Armando M." Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [neutron] diagnostics

Hi folks, At the summit we had a forum session [1] to gather feedback on the current diagnostics proposal [2] and help the neutron developer team drive the first implementation of the API proposal. Two main points were brought for discussion: 1) which diagnostics checks to provide to start

[openstack-dev] [neutron] multi-site forum discussion

Hi folks, At the summit we had a discussion on how to deploy a single neutron system across multiple geographical sites [1]. You can find notes of the discussion on [2]. One key requirement that came from the discussion was to make Neutron more Nova cells friendly. I filed an RFE bug [3] so that

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 18 & 19)

If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting The previous week's meeting was

Re: [openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

On 12.5.2017 15:30, Emilien Macchi wrote: On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský wrote: Hi all, the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal to containers) just got a green flag from the CI [1]. I've listed the remaining patches we need

Re: [openstack-dev] [ironic] [tripleo] demo: node auto-discovery with one power button click

Hi Dmitry - > On 11 May 2017, at 15:56, Dmitry Tantsur wrote: > > Hi all! > > While people are enjoying the Forum, I also have something to show. > > I've got a lot of questions about auto-discovery, so I've recorded a demo > of it using TripleO Ocata:

Re: [openstack-dev] [ironic] [tripleo] demo: node auto-discovery with one power button click

On 05/11/2017 07:28 PM, Jiri Tomasek wrote: On 11.5.2017 16:56, Dmitry Tantsur wrote: Hi all! While people are enjoying the Forum, I also have something to show. I've got a lot of questions about auto-discovery, so I've recorded a demo of it using TripleO Ocata:

Re: [openstack-dev] [tripleo] Validations before upgrades and updates

On Mon, May 8, 2017 at 7:45 AM, Marios Andreou wrote: > Hi folks, after some discussion locally with colleagues about improving the > upgrades experience, one of the items that came up was pre-upgrade and > update validations. I took an AI to look at the current status of >

Re: [openstack-dev] [tripleo] [CI] HA and non-HA OVB jobs are now running with Quickstart

On Wed, May 10, 2017 at 11:11 AM, Sagi Shnaidman wrote: > Hi, all > In addition to multinode jobs, we migrated today part of OVB jobs to use > quickstart. > > We had before OVB ha and OVB nonha jobs and together with migrating them to > use quickstart we merged them into one

Re: [openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský wrote: > Hi all, > > the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal to > containers) just got a green flag from the CI [1]. > > I've listed the remaining patches we need to land at the very top of the >

[openstack-dev] [neutron] multiple vlan provider and tenant networks at the same time?

Hi, I wonder how it is possible to setup multiple network interfaces / bridge mappings for VLAN tenants and providers at the same time. E.g. in case of 1 VLAN network for tenant and 1 external VLAN how should neutron bridge mapping work? User interface does not allow to specify the mapping.

Re: [openstack-dev] [magnum] magnum cluster-create for kubernetes-template was failed.

Hi, I also hit the loopingcall error while running magnum 4.1.1 (ocata). It is tracked by this bug: https://bugs.launchpad.net/magnum/+bug/1666790. I cherry picked the fix to ocata locally, but this needs to be done upstream as well. I think that the heat stack create timeout is unrelated to

[openstack-dev] [networking-sfc] Load distribution bug with OVS driver

Hi, this is a follow-up/summary of launchpad bug 1675289 [0]. From the original spec [1], with the OVS driver we should have groups witt the "hash" selection method, and for parameters source IP/port/protocol However this requires OpenFlow 1.5, so we actually have default selection method and