Re: [openstack-dev] [devstack][VMware NSX CI] VMware NSX CI fails and don't recheck

[Hirofumi Ichihara]

Hi Salvatore,

Thank you for good news.
I looked VMware NSX CI voted for my patch.

Thanks,
Hirofumi 

2015/01/02 3:07、Salvatore Orlando  のメール：

> Hi VMware NSX CI for Neutron was disabled but unfortunately it kept voting on 
> a few set of patches, always failing for a number of reasons.
> 
> It seems everything is fixed now and all the jobs have been reinstated.
> 
> Salvatore
> 
> On 25 December 2014 at 08:32, Hirofumi Ichihara 
>  wrote:
> Hi Gary,
> 
> Thank you for your response.
> I understand. I’m expecting good news.
> 
> Thanks,
> Hirofumi
> 
> 2014/12/25 15:57、Gary Kotton  のメール：
> 
>> Hi,
>> We have a few CI issues. We are working on them at the moment. I hope that 
>> we get to the bottom of this soon.
>> Thanks
>> Gary
>> 
>> From: Hirofumi Ichihara 
>> Reply-To: OpenStack List 
>> Date: Thursday, December 25, 2014 at 5:41 AM
>> To: OpenStack List 
>> Subject: [openstack-dev] [devstack][VMware NSX CI] VMware NSX CI fails and 
>> don't recheck
>> 
>> Hi,
>> 
>> My patch(https://review.openstack.org/#/c/124011/) received verified-1 from 
>> VMware NSX CI.
>> But my patch isn’t related to VMware so I added comment 
>> “vmware-recheck-patch” according to VMware NSX CI comment.
>> However, VMware NSX CI don’t recheck.
>> 
>> I don’t know recheck word was wrong or CI broke.
>> 
>> Could someone help me?
>> 
>> Thanks,
>> Hirofumi
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][L2-Gateway] Meetings announcement

[Sukhdev Kapur]

Hi Ian,

I do not have one definition per se for the L2 gateway. Every use case
tends to define it in differently :-).  The desire (and goal) is to come up
with "an" API within Kilo cycle, upon which folks can start to build their
use cases, and (hopefully) iteratively come up with an API which covers
most, if not all, use cases.

For past few cycles (going all the way back to Hong Kong summit), we have
been discussing about this API, but, have not been able to converge.

During Paris summit (in the pods), a reasonable number of vendors
participated in the discussion to build upon the proposal made my Maruti
(from HP) to come up with the a "starting point" for this API. Maruti and
Armando (along with others) have been iterating over the spec proposed by
Maruti ( I posted the link on the wiki).

We felt, it is about time that we get together in a regular meeting form to
discuss as to what we have have so far and see how we can make it reality
for Kilo cycle. I realize that this may not fill all the bills. Once we
have a working version, we can alway build upon it and bring in more and
more use case as we move forward.

Please join us on IRC on this Monday and share your wisdom with other
members.

-Sukhdev


On Jan 4, 2015 2:08 AM, "Kevin Benton"  wrote:

> Weasels
>
> On Sat, Jan 3, 2015 at 2:57 PM, Ian Wells  wrote:
>
>> Sukhdev,
>>
>> Since the term is quite broad and has meant many things in the past, can
>> you define what you're thinking of when you say 'L2 gateway'?
>>
>> Cheers,
>> --
>> Ian.
>>
>> On 2 January 2015 at 18:28, Sukhdev Kapur  wrote:
>>
>>> Hi all,
>>>
>>> HAPPY NEW YEAR.
>>>
>>> Starting Monday (Jan 5th, 2015) we will be kicking of bi-weekly meetings
>>> for L2 Gateway discussions.
>>>
>>> We are hoping to come up with an initial version of L2 Gateway API in
>>> Kilo cycle. The intent of these bi-weekly meetings is to discuss issues
>>> related to L2 Gateway API.
>>>
>>> Anybody interested in this topic is invited to join us in these meetings
>>> and share your wisdom with the similar minded members.
>>>
>>> Here is the details of these meetings:
>>>
>>> https://wiki.openstack.org/wiki/Meetings#Networking_L2_Gateway_meeting
>>>
>>> I have put together a wiki for this project. Next week is the initial
>>> meeting and the agenda is pretty much open. We will give introduction of
>>> the members of the team as well the progress made so far on this topic. If
>>> you would like to add anything to the agenda, feel free to update the
>>> agenda at the following wiki:
>>>
>>> https://wiki.openstack.org/wiki/Meetings/L2Gateway
>>>
>>> Look forward to on the IRC.
>>>
>>> -Sukhdev
>>>
>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Kevin Benton
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Eli Qiao]

在 2015年01月05日 13:02, Punith S 写道:

Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the 
required volume from the volumes table using the id.
if it fails due to foreign key constraints in volume metadata table, 
try deleting the corresponding volume metadata and then try to delete 
the required volume row.


hi Punith, I did as your suggestion, it works. but is that reasonable 
not to delete a error_deleting even that status keeping for a quite long 
time?

thanks.

thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao > wrote:



hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete', then how we
fix it if we got such situation ?
[tagett@stack-01 devstack]$ cinder list

+--++-+--+-+--+--+
|  ID  | Status | Name   
| Size | Volume Type | Bootable | Attached

to  |

+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use |
with_cirros |  4   | lvmdriver-1 |   true   |
428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting |
None|  4   | lvmdriver-1 |  false

|  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting |
None|  4   | lvmdriver-1 |  false

|  |

+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete
7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad
Request (HTTP 400) (Request-ID:
req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.

-- 
Thanks,

Eli (Li Yong) Qiao


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
regards,

punith s
cloudbyte.com 


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thanks,
Eli (Li Yong) Qiao

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Eli Qiao]

在 2015年01月05日 13:31, Eli Qiao 写道:


在 2015年01月05日 13:10, Asselin, Ramy 写道:


Before getting into the database, try the cinder reset-state command. 
It’s available in the horizon ui starting in Juno.


Otherwise use the command line [1].


hi Asselin, appreciate it, sorry for reply to wrong person.


Ramy

[1] 
http://docs.openstack.org/cli-reference/content/cinderclient_commands.html



Hi Punith, the command line is really help , thanks.
but I am not sure I found it in horizon ui(latest upstream version), 
is there a button , or menu to call cinder reset-state in ui ?


*From:*Punith S [mailto:punit...@cloudbyte.com]
*Sent:* Sunday, January 04, 2015 9:02 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Cinder] how to delete a volume which 
is in error_deleting state


Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the 
required volume from the volumes table using the id.


if it fails due to foreign key constraints in volume metadata table, 
try deleting the corresponding volume metadata and then try to delete 
the required volume row.


thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao > wrote:



hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete',  then how
we fix it if we got such situation ?
[tagett@stack-01 devstack]$ cinder list

+--++-+--+-+--+--+
|  ID  | Status | Name   
| Size | Volume Type | Bootable | Attached

to  |

+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros
|  4   | lvmdriver-1 | true   |
428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting |
None|  4   | lvmdriver-1 | false  
|  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting |
None|  4   | lvmdriver-1 | false  
|  |


+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete
7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed:
Bad Request (HTTP 400) (Request-ID:
req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.


-- 


Thanks,

Eli (Li Yong) Qiao


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--

regards,

punith s

cloudbyte.com 



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thanks,
Eli (Li Yong) Qiao


--
Thanks,
Eli (Li Yong) Qiao

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Eli Qiao]

在 2015年01月05日 13:10, Asselin, Ramy 写道:


Before getting into the database, try the cinder reset-state command. 
It’s available in the horizon ui starting in Juno.


Otherwise use the command line [1].

Ramy

[1] 
http://docs.openstack.org/cli-reference/content/cinderclient_commands.html



Hi Punith, the command line is really help , thanks.
but I am not sure I found it in horizon ui(latest upstream version), is 
there a button , or menu to call cinder reset-state in ui ?


*From:*Punith S [mailto:punit...@cloudbyte.com]
*Sent:* Sunday, January 04, 2015 9:02 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Cinder] how to delete a volume which 
is in error_deleting state


Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the 
required volume from the volumes table using the id.


if it fails due to foreign key constraints in volume metadata table, 
try deleting the corresponding volume metadata and then try to delete 
the required volume row.


thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao > wrote:



hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete', then how we
fix it if we got such situation ?
[tagett@stack-01 devstack]$ cinder list

+--++-+--+-+--+--+
|  ID  | Status | Name   
| Size | Volume Type | Bootable | Attached

to  |

+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros
|  4   | lvmdriver-1 | true   | 428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting |
None|  4   | lvmdriver-1 | false  
|  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting |
None|  4   | lvmdriver-1 | false  
|  |


+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete
7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad
Request (HTTP 400) (Request-ID:
req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.


-- 


Thanks,

Eli (Li Yong) Qiao


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--

regards,

punith s

cloudbyte.com 



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Thanks,
Eli (Li Yong) Qiao

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Asselin, Ramy]

Before getting into the database, try the cinder reset-state command. It’s 
available in the horizon ui starting in Juno.
Otherwise use the command line [1].

Ramy
[1] http://docs.openstack.org/cli-reference/content/cinderclient_commands.html


From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Sunday, January 04, 2015 9:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] how to delete a volume which is in 
error_deleting state

Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the required 
volume from the volumes table using the id.
if it fails due to foreign key constraints in volume metadata table, try 
deleting the corresponding volume metadata and then try to delete the required 
volume row.

thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao 
mailto:ta...@linux.vnet.ibm.com>> wrote:

hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete',  then how we fix it if we 
got such situation ?
[tagett@stack-01 devstack]$ cinder list
+--++-+--+-+--+--+
|  ID  | Status | Name| Size | 
Volume Type | Bootable | Attached to  |
+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros |  4   | 
lvmdriver-1 |   true   | 428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None|  4   | 
lvmdriver-1 |  false   |  |
+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete  7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad Request 
(HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
ERROR: Unable to delete any of specified volumes.



--

Thanks,

Eli (Li Yong) Qiao

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
regards,

punith s
cloudbyte.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Punith S]

Hi Eli,

you have to log-in to MySQL cinder database , and try deleting the required
volume from the volumes table using the id.
if it fails due to foreign key constraints in volume metadata table, try
deleting the corresponding volume metadata and then try to delete the
required volume row.

thanks

On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao  wrote:

>
> hi all,
> how to delete a cinder volume which is in error_deleting status ?
> I don't find force delete options in 'cinder delete',  then how we fix it
> if we got such situation ?
> [tagett@stack-01 devstack]$ cinder list
>
> +--++-+--+-+--+--+
> |  ID  | Status | Name|
> Size | Volume Type | Bootable | Attached to  |
>
> +--++-+--+-+--+--+
> | 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros |
> 4   | lvmdriver-1 |   true   | 428f0235-be54-462f-8916-f32965d42e63 |
> | 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None|
> 4   | lvmdriver-1 |  false   |  |
> | d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None|
> 4   | lvmdriver-1 |  false   |  |
>
> +--++-+--+-+--+--+
> [tagett@stack-01 devstack]$ cinder delete
> 7039c683-2341-4dd7-a947-e35941245ec4
> Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad Request
> (HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)
> ERROR: Unable to delete any of specified volumes.
>
> --
> Thanks,
> Eli (Li Yong) Qiao
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
regards,

punith s
cloudbyte.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Refactored heat-kubernetes templates

[Steven Dake]

On 01/02/2015 08:39 AM, Lars Kellogg-Stedman wrote:

Hello Kolla folks (et al),

I've refactored the heat-kubernetes templates at
https://github.com/larsks/heat-kubernetes to work with Centos Atomic
Host and Fedora 21 Atomic, and to replace the homegrown overlay
network solution with Flannel.

These changes are available on the "master" branch.

The previous version of the templates, which worked with F20 and
included some Kolla-specific networking logic, is available in the
"kolla" branch:

   https://github.com/larsks/heat-kubernetes/tree/kolla


I just wanted to point out the image I built for Kolla devs to use:

https://fedorapeople.org/groups/heat/kolla/fedora-21-atomic.qcow2

Note this image lacks SELinux support, because SELinux is broken after a 
fedora atomic upgrade (bugs are filed, its being worked on).


Regards
-steve




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Magnum] Proposed Changes to Magnum Core

[Motohiro Ootsuka]

+1 welcome!

Regards,
OTSUKA, Motohiro/Yuanying

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Host health monitoring

[Andrew Beekhof]

> On 9 Dec 2014, at 1:20 am, Roman Dobosz  wrote:
> 
> On Wed, 3 Dec 2014 08:44:57 +0100
> Roman Dobosz  wrote:
> 
>> I've just started to work on the topic of detection if host is alive or
>> not: https://blueprints.launchpad.net/nova/+spec/host-health-monitoring
>> 
>> I'll appreciate any comments :)
> 
> I've submitted another blueprint, which is closely bounded with previous one: 
> https://blueprints.launchpad.net/nova/+spec/pacemaker-servicegroup-driver
> 
> The idea behind those two blueprints is to enable Nova to be aware of host 
> status, not only services that run on such. Bringing Pacemaker as a driver 
> for 
> servicegroup will provide us with two things: fencing and reliable 
> information 
> about host state, therefore we can avoid situations, where some actions will 
> misinterpret information like service state with host state.
> 
> Comments?

Sounds like an excellent idea, is there code for these blueprints? If so, how 
do I get to see it?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Cinder] how to delete a volume which is in error_deleting state

[Eli Qiao]

hi all,
how to delete a cinder volume which is in error_deleting status ?
I don't find force delete options in 'cinder delete',  then how we fix 
it if we got such situation ?

[tagett@stack-01 devstack]$ cinder list
+--++-+--+-+--+--+
|  ID  | Status | Name| Size 
| Volume Type | Bootable | Attached to  |

+--++-+--+-+--+--+
| 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros |  
4   | lvmdriver-1 |   true   | 428f0235-be54-462f-8916-f32965d42e63 |
| 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None|  4   
| lvmdriver-1 |  false |  |
| d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None|  4   
| lvmdriver-1 |  false |  |

+--++-+--+-+--+--+
[tagett@stack-01 devstack]$ cinder delete 
7039c683-2341-4dd7-a947-e35941245ec4
Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad 
Request (HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33)

ERROR: Unable to delete any of specified volumes.

--
Thanks,
Eli (Li Yong) Qiao

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] static files handling, bower/

[Richard Jones]

So just to be clear, as developers we:

1. have a bower.json listing the bower component to use,
2. use bower to fetch and install those to the bower_components directory
at the top level of the Horizon repos checkout, and
3. manually edit static_settings.py when we add a new bower component to
bower.json so it knows the appropriate static files to load from that
component.

Is that correct?

The above will increase the burden on those adding or upgrading bower
components (they'll need to check the bower.json in the component for the
appropriate static files to link in) but will make life easier for the
re-packagers since they'll know which files they need to cater for in
static_settings.py


  Richard


On Mon Dec 22 2014 at 8:24:03 PM Radomir Dopieralski 
wrote:

> On 20/12/14 21:25, Richard Jones wrote:
> > This is a good proposal, though I'm unclear on how the
> > static_settings.py file is populated by a developer (as opposed to a
> > packager, which you described).
>
> It's not, the developer version is included in the repository, and
> simply points to where Bower is configured to put the files.
>
> --
> Radomir Dopieralski
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] Meetup Reminder

[Clint Byrum]

Happy New Year!

Just a friendly reminder to those of you who are interested in TripleO,
we have a three-day Meetup scheduled for February 18-20 in Seattle, WA.
All are welcome, though space is limited to 30 participants. Thus far we
have 8 people signed up in the etherpad:

https://etherpad.openstack.org/p/kilo-tripleo-midcycle-meetup

Please do add yourself to the list if you intend to come. There is
information on hotels and we will add any event notifications and agenda
items that come up.

Thanks, and see you all there!

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova blueprint] Ask for the blueprint of "Enhance iSCSI volume multipath support".

[Michael Still]

On Sun, Jan 4, 2015 at 11:11 PM, liuxinguo  wrote:

> I have seen that the blueprint of “Enhance iSCSI multipath support” for
> cinder have been approved and target in kilo-2, I want to know that will the
> blueprint of "Enhance iSCSI volume multipath support" for nova be
> implemented in Kilo?

The nova spec is not currently approved. I can see that the cinder
spec is approved, but it appears that none of the actual
implementation has landed yet, and we were hesitant in nova to approve
adding a feature which depended on something which didn't exist in
cinder yet. Looking at the cinder patches I think it would be
premature to approve the nova spec until the implementation in cinder
is complete.

At this stage this means that this feature is unlikely to land in kilo.

Hope that helps,
Michael

-- 
Rackspace Australia

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova blueprint] Ask for the blueprint of "Enhance iSCSI volume multipath support".

[liuxinguo]

Hi all,

I have seen that the blueprint of "Enhance iSCSI multipath support" for cinder 
have been approved and target in 
kilo-2, I want to know that 
will the blueprint of "Enhance iSCSI volume multipath support" for nova be 
implemented in Kilo?

Any input will be appreciated, thanks!
liu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][L2-Gateway] Meetings announcement

[Kevin Benton]

Weasels

On Sat, Jan 3, 2015 at 2:57 PM, Ian Wells  wrote:

> Sukhdev,
>
> Since the term is quite broad and has meant many things in the past, can
> you define what you're thinking of when you say 'L2 gateway'?
>
> Cheers,
> --
> Ian.
>
> On 2 January 2015 at 18:28, Sukhdev Kapur  wrote:
>
>> Hi all,
>>
>> HAPPY NEW YEAR.
>>
>> Starting Monday (Jan 5th, 2015) we will be kicking of bi-weekly meetings
>> for L2 Gateway discussions.
>>
>> We are hoping to come up with an initial version of L2 Gateway API in
>> Kilo cycle. The intent of these bi-weekly meetings is to discuss issues
>> related to L2 Gateway API.
>>
>> Anybody interested in this topic is invited to join us in these meetings
>> and share your wisdom with the similar minded members.
>>
>> Here is the details of these meetings:
>>
>> https://wiki.openstack.org/wiki/Meetings#Networking_L2_Gateway_meeting
>>
>> I have put together a wiki for this project. Next week is the initial
>> meeting and the agenda is pretty much open. We will give introduction of
>> the members of the team as well the progress made so far on this topic. If
>> you would like to add anything to the agenda, feel free to update the
>> agenda at the following wiki:
>>
>> https://wiki.openstack.org/wiki/Meetings/L2Gateway
>>
>> Look forward to on the IRC.
>>
>> -Sukhdev
>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kevin Benton
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][qa] need some eyes on new(ish) gate bug 1407190

[Kevin Benton]

Good catch. This was a result of the "Don't unnecessarily loop through all
ports/interfaces" patch.[1]

Passing a list of names to "ovs-vsctl list Interface" with an element that
doesn't match an existing port causes an error.[2] This happens when a port
is deleted right after the list of interface names is gathered but before
the "list Interface" command is run. I think the resulting runtime errors
were interfering with the correct operation of the agent.

There is a fix up[3] that adds the '--if-exists' flag that should restore
the previous behavior of not requiring the requested names to exist.
Hopefully that should clear up the issue.


1.
https://github.com/openstack/neutron/commit/3f0bf6cfac2e151d5a4a7f076062b3365bdbf457
2.
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-q-agt.txt.gz#_2015-01-02_15_42_40_999
3. https://review.openstack.org/#/c/144872/

On Sat, Jan 3, 2015 at 4:14 PM, Matt Riedemann 
wrote:

> https://bugs.launchpad.net/neutron/+bug/1407190
>
> Looks like this started on 12/29.  I checked the neutron commits around
> that time and there are some related to ports/interfaces and openvswitch
> but I'm not sure that they contributing to this issue.
>
> I've put a bunch of notes and log links in the bug report, basically there
> is a race in a tempest test where it creates a server and adds two ports to
> it (so a total of three), it waits for each port to be ACTIVE before
> continuing, and then does a show port call by port ID and server ID and
> expects the port to be the same as what it originally created. When this
> fails, the expected port_status is 'ACTIVE' but the actual port_status is
> 'BUILD'.
>
> I've found in the logs where nova/neutron are seeing the port going to
> 'BUILD' state but I don't know enough about the neutron code to tell what
> actually triggers this change, the only place I see 'BUILD' used is in the
> nova event notifier code in neutron which is related to the vif plug/unplug
> callback on nova server boot.
>
> This isn't the top gate bug, but it's got a significant number of hits and
> seems like something that we should be able to reasonably get a quick
> handle on given I think we know when it started (12/29 according to
> logstash, I caught it before the 10 day index in logstash passed).
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kevin Benton
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev