Hi,
How does "tag" gets assigned to openvswitch port ?
Port "tap319bae97-0b"
*tag: 1*
Interface "tap319bae97-0b"
It is done by openvswitch-agent, but can someone point me to the details?
Is this has anything to do with network (segment-id) or is it just local to
Yes, sorry my bad for not adding it -
http://logs.openstack.org/39/452539/2/check/gate-vmware-nsx-python27-ubuntu-xenial/14c019c/testr_results.html.gz
Please see the test test_create_port_dns_name
Thanks
Gary
From: Kevin Benton
Reply-To: OpenStack List
Date: Monday, April 3, 2017 at 12:56 AM
To
On 4/2/2017 8:08 PM, Feodor Tersin wrote:
Can you give some more details? How does this actually "merge" or
replace BDMs defined in the image metadata? Is this because we use
device name as part of a hack for a primary key in the database [1]? I
assume it is. The lack of unique constraint in t
> Can you give some more details? How does this actually "merge" or
> replace BDMs defined in the image metadata? Is this because we use
> device name as part of a hack for a primary key in the database [1]? I
> assume it is. The lack of unique constraint in the BDM data model has
> also always be
Hongbin,
Nice. +1 in theory :) the etcd one i have a WIP for the etcd/DLM,
please see here https://review.openstack.org/#/c/445432/
-- Dims
On Sun, Apr 2, 2017 at 8:13 PM, Hongbin Lu wrote:
> Hi devstack team,
>
>
>
> Please find my proposal about consolidating docker installation into one
> pl
Hi devstack team,
Please find my proposal about consolidating docker installation into one place
that is devstack tree:
https://review.openstack.org/#/c/452575/
Currently, there are several projects that installed docker in their devstack
plugins in various different ways. This potentially int
On 4/2/2017 12:35 PM, Feodor Tersin wrote:
Device merging is used by EC2 API at least. This allows us (EC2 API
team) to implement a use case of changing attached volume parameters
when launching an instance from a volume backed image. If the image's
bdms contain several volume descriptions, but a
Do you have a link to a traceback?
On Apr 2, 2017 09:25, "Gary Kotton" wrote:
> Hi,
>
> The change https://review.openstack.org/#/c/402750/ has broken the
> vmware-nsx plugin. I am not sure if this has had effect on any other
> decomposed plugins.
>
> One of the issues that we have is when we cr
On 03/29/2017 03:39 PM, Steve Gordon wrote:
> - Original Message -
>> From: "Davanum Srinivas"
>> To: "Chris Hoge"
>> Cc: "OpenStack Development Mailing List (not for usage questions)"
>> ,
>> "kubernetes-sig-openstack"
>> Sent: Wednesday, March 29, 2017 2:28:29 PM
>> Subject: Re: [open
On 04/02/2017 02:53 PM, Chris Hoge wrote:
> Now that the provider has a repository in the OpenStack project
> namespace, we need to move over the existing set of issues and pull
> requests and create an initial work list for migrating patches and
> fixing existing issues.
>
> I've started up an et
Now that the provider has a repository in the OpenStack project
namespace, we need to move over the existing set of issues and pull
requests and create an initial work list for migrating patches and
fixing existing issues.
I've started up an etherpad where we can track that work[1]. In the longer
Device merging is used by EC2 API at least. This allows us (EC2 API team) to
implement a use case of changing attached volume parameters when launching an
instance from a volume backed image. If the image's bdms contain several volume
descriptions, but a user wants to change some of them for a n
Hi,
The change https://review.openstack.org/#/c/402750/ has broken the vmware-nsx
plugin. I am not sure if this has had effect on any other decomposed plugins.
One of the issues that we have is when we create a PortDNS object under a
transaction we get an exception: DBReferenceError: (sqlite3.Int
On 4/2/2017 10:13 AM, Matt Riedemann wrote:
On 4/1/2017 1:01 PM, Matt Riedemann wrote:
I know we've talked about this over and over and another bug [1]
reminded me of it. We have long talked about removing the ability to
specify a block device name when creating a server or attaching a volume
be
On 4/1/2017 1:01 PM, Matt Riedemann wrote:
I know we've talked about this over and over and another bug [1]
reminded me of it. We have long talked about removing the ability to
specify a block device name when creating a server or attaching a volume
because we can't honor the requested device nam
On 4/1/2017 1:01 PM, Matt Riedemann wrote:
I know we've talked about this over and over and another bug [1]
reminded me of it. We have long talked about removing the ability to
specify a block device name when creating a server or attaching a volume
because we can't honor the requested device nam
On Fri, 2017-03-31 at 17:21 -0600, Alex Schultz wrote:
> Hey folks,
>
> I wanted to raise awareness of the concept of idempotence[0] and how
> it affects deployment(s). In the puppet world, we consider this very
> important because since puppet is all about ensuring a desired state
> (ie. a syste
+1
On 3/31/17, 12:55 AM, "Ihar Hrachyshka" wrote:
On Thu, Mar 30, 2017 at 2:11 PM, Kevin Benton wrote:
> Hi,
>
> I would like to add Miguel Lavalle (mlavalle) to the Neutron drivers team
> [1].
It's not completely clear if you seek support here, but in case you do,
18 matches
Mail list logo
