Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

[Michael Still]

Jay has now been added to the nova-core group in gerrit.

Cheers,
Michael

On Thu, Jul 31, 2014 at 7:02 AM, Michael Still  wrote:
> Greetings,
>
> I would like to nominate Jay Pipes for the nova-core team.
>
> Jay has been involved with nova for a long time now.  He's previously
> been a nova core, as well as a glance core (and PTL). He's been around
> so long that there are probably other types of core status I have
> missed.
>
> Please respond with +1s or any concerns.
>
> References:
>
>   https://review.openstack.org/#/q/owner:%22jay+pipes%22+status:open,n,z
>
>   https://review.openstack.org/#/q/reviewer:%22jay+pipes%22,n,z
>
>   http://stackalytics.com/?module=nova-group&user_id=jaypipes
>
> As a reminder, we use the voting process outlined at
> https://wiki.openstack.org/wiki/Nova/CoreTeam to add members to our
> core team.
>
> Thanks,
> Michael
>
> --
> Rackspace Australia



-- 
Rackspace Australia

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

[openstack-dev] [Tripleo] photos of whiteboards?

[Robert Collins]

We had a few whiteboard photos taken during the sprint, but I can't
find where they were posted :/

Right now I'm looking for the one with the list of priority CI jobs,

-Rob

-- 
Robert Collins 
Distinguished Technologist
HP Converged Cloud

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

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

[Dan Prince]

On Wed, 2014-07-30 at 14:02 -0700, Michael Still wrote:
> Greetings,
> 
> I would like to nominate Jay Pipes for the nova-core team.
> 
> Jay has been involved with nova for a long time now.  He's previously
> been a nova core, as well as a glance core (and PTL). He's been around
> so long that there are probably other types of core status I have
> missed.
> 
> Please respond with +1s or any concerns.

+1

> 
> References:
> 
>   https://review.openstack.org/#/q/owner:%22jay+pipes%22+status:open,n,z
> 
>   https://review.openstack.org/#/q/reviewer:%22jay+pipes%22,n,z
> 
>   http://stackalytics.com/?module=nova-group&user_id=jaypipes
> 
> As a reminder, we use the voting process outlined at
> https://wiki.openstack.org/wiki/Nova/CoreTeam to add members to our
> core team.
> 
> Thanks,
> Michael
> 



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

[openstack-dev] [all] specs.openstack.org is live

[Andreas Jaeger]

All OpenStack incubated projects and programs that use a -specs
repository have now been setup to publish these to
http://specs.openstack.org. With the next merged in patch of a *-specs
repository, the documentation will get published.

The index page contains the published repos as of yesterday and it will
be enhanced as more are setup (current patch:
https://review.openstack.org/111476).

For now, you can reach a repo directly via
http://specs.openstack.org/$ORGANIZATION/$project-specs, for example:
http://specs.openstack.org/openstack/qa-specs/

Thanks to Steve Martinelli and to the infra team (especially Clark,
James, Jeremy and Sergey) for getting this done!

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

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

[openstack-dev] [infra][qa][rally] Why we need subunit2sql?

[Boris Pavlovic]

Hi stackers,


Could somebody explain me why we need subunit2sql?

It seems like a part of functionality that is already implemented in Rally:
http://www.mirantis.com/blog/rally-openstack-tempest-testing-made-simpler/

With Rally we can run tempest tests and Rally will parse & store results to
it's DB.
Having one instance of Rally DB in gates will allow us to collect all
results of all tempest runs. As well Rally is already integrated in gates.
So there won't be issues with getting this done.

By the way, Rally team is ready to help with this task.

Thoughts?

Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [HEAT] Qestions on adding a new Software Config element for Opscode Chef

[Thomas Spatzier]

> From: Tao Tao 
> To: openstack-dev@lists.openstack.org
> Cc: Shu Tao , Yan Yan YY Hu
> , Bo B Yang 
> Date: 01/08/2014 22:19
> Subject: [openstack-dev] [HEAT] Qestions on adding a new Software
> Config element for Opscode Chef
>
> Hi, All:
>
> We are trying to leverage Heat software config model to support
> Chef-based software installation. Currently the chef-based software
> config is not in place with Heat version 0.2.9.
>
> Therefore, we do have a number of questions on the implementation
byourselves:
>
> 1. Should we create new software config child resource types (e.g.
> OS::Heat::SoftwareConfig::Chef and
> OS::Heat::SoftwareDeployment::Chef proposed in the https://
> wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config-spec) or
> should we reuse the existing software config resource type (e.g.
> OS::Heat::SoftwareConfig by leveraging group attribute) like the

Right, you should not implement your own resource plugin, but use the
current SoftwareConfig resource and specify 'chef' in the group attribute.

You will have to build an image that contains the right in-instance tools
as described here:
https://github.com/openstack/heat-templates/blob/master/hot/software-config/elements/README.rst

Note that the in-instance hook for handling chef-solo is still in review
and has not yet been merged to the heat-templates repository. Before
building you image, you can pull the changes for the chef config hook from
this review:

https://review.openstack.org/#/c/80229/

> following example with Puppet? What are the pros and cons with
> either approach?
>
>   config:
> type: OS::Heat::SoftwareConfig
> properties:
>   group: puppet
>   inputs:
>   - name: foo
>   - name: bar
>   outputs:
>   - name: result
>   config:
> get_file: config-scripts/example-puppet-manifest.pp
>
>   deployment:
> type: OS::Heat::SoftwareDeployment
> properties:
>   config:
> get_resource: config
>   server:
> get_resource: server
>   input_values:
> foo: fo
> bar: ba
>
> 2. Regarding OpsCode Chef and Heat integration, should our software
> config support chef-solo only, or should support Chef server? In
> another word,  should we let Heat to do the orchestration for the
> chef-based software install or should we continue to use chef-server
> for the chef-based software install?

I would say, with the current chef in-instance hook for Heat, you could use
chef-solo for the software install per package and per server and let Heat
do the overall orchestration.

>
> 3. In the current implementation of software config hook for puppet
> as follows:
>
> heat-templates / hot / software-config / elements / heat-config-puppet /
> install.d / 50-heat-config-hook-puppet
>
> 3.1 why we need a 50-* as a prefix for the heat-config hook name?
>
> 3.2 In the script as follows, what is the "install-packages" script?
> where does it load puppet package? How would we change the script to
> install chef package?
>
> #!/bin/bash
> set -x
>
> SCRIPTDIR=$(dirname $0)
>
> install-packages puppet
> install -D -g root -o root -m 0755 ${SCRIPTDIR}/hook-puppet.py /var/
> lib/heat-config/hooks/puppet
>
> 4. With diskimage-builder, we can build in images with many software
> config elements(chef, puppet, script, salt), which means there will
> be many hooks in the image.
>  However, By reading the source code of the os-refresh-config, it
> seems it will execute only the hooks which has corresponding "group"
> defined in the software config, is that right?

Right, you have to have the group property in your SoftwareConfig resources
set appropriately.

>
> def invoke_hook(c, log):
> # sanitise the group to get an alphanumeric hook file name
> hook = "".join(
> x for x in c['group'] if x == '-' or x == '_' or x.isalnum())
> hook_path = os.path.join(HOOKS_DIR, hook)
>
> signal_data = None
> if not os.path.exists(hook_path):
> log.warn('Skipping group %s with no hook script %s' % (
> c['group'], hook_path))
> else:
>
>
> Thanks a lot for your kind assistance!
>
>
>
> Thanks,
> Tao Tao, Ph.D.
> IBM T. J. Watson Research Center
> 1101 Kitchawan Road
> Yorktown Heights, NY 10598
> Phone: (914) 945-4541
> Email: t...@us.ibm.com___
> 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] [Openstack-stable-maint] Preparing for 2014.1.2 -- branches freeze Aug 7

[Alan Pevec]

> ... above relates only to freeze
> exceptions for critical issues which must be raised and discussed on
> openstack-stable-maint release. Hopefully there won't be any.

openstack-stable-maint _list_

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

Re: [openstack-dev] [Openstack-stable-maint] Preparing for 2014.1.2 -- branches freeze Aug 7

[Alan Pevec]

> We have frozen the stable/icehouse branches for intergrated projects for
> release Thurs August 7th in preparation for the 2014.1.2 stable release You
> can view the current queue of proposed patches on gerrit [1].

2014.1.2 is stable Icehouse release so [1] is:

https://review.openstack.org/#/q/status:open+AND+branch:stable/icehouse+AND+(project:openstack/nova+OR+project:openstack/keystone+OR+project:openstack/glance+OR+project:openstack/cinder+OR+project:openstack/neutron+OR+project:openstack/horizon+OR+project:openstack/heat+OR+project:openstack/ceilometer+OR+project:openstack/trove),n,z

> I'd like to request all interested parties review current bugs affecting 
> Havana and help
> ensure any relevant fixes be proposed soon and merged by Thursday, or notify
> the stable-maint team of anything critical that may land late.

s/Havana/Icehouse/ and clarification that above relates only to freeze
exceptions for critical issues which must be raised and discussed on
openstack-stable-maint release. Hopefully there won't be any.

Cheers,
Alan

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

[openstack-dev] [Neutron][LBaaS] New requirement pyasn1_modules needed by Neutron for TLS capability is needed in openstack/requirements project

[Evgeny Fedoruk]

Hi folks,

Since pyasn1_modules is needed by our new common Barbican interactions module,
The package was added to the neutron requirements file by the 
https://review.openstack.org/#/c/109849/ change set.
Gate checks are failing now because this new pyasn1_modules requirement should 
be added to the openstack/requirements as well.

I pushed a new change set (https://review.openstack.org/#/c/111464) with this 
addition of pyasn1_modules package to the 
global-requirements.txt
 file of openstack/requirements project

Since https://review.openstack.org/#/c/109849/ is depending on it and 
https://review.openstack.org/#/c/109035 (TLS implementation)
is depending on https://review.openstack.org/#/c/109849/ , we need it to be 
approved and merged asap because as it seems to me that
cross-project dependencies are impossible in gerrit, so our two change sets 
will continue failing on the gate until openstack/requirements change set will 
not be merged.

Kyle, Mark, Oleg could you please see the 
https://review.openstack.org/#/c/111464/ change set and help with approving it 
so our dependencies will not fail

Thanks,
Evg



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

Re: [openstack-dev] [Neutron] Route cannot be deleted

[Sayali Lunkad]

Hi Zzelle,

Thanks for the prompt response.
As you mentioned I cleared all the routes using

*neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes
action=clear*
So to see the router status I run this:













*neutron router-show 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
+---+--+|
Field | Value
|+---+--+|
admin_state_up| True ||
external_gateway_info |  ||
id| 2f16d846-b6aa-43a3-adbe-7f91a1389b7f ||
name  | router0  ||
routes|  ||
status| ACTIVE   ||
tenant_id | 315561c9a19e4794ac4f4364c842254f
|+---+--+*
After that I try to unbind the subnet using the command below but the same
problem persists.

*neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
962b8364-a2b4-46cc-95be-28cbab62b8c2
409-{u'NeutronError': {u'message': u'Router interface for subnet
962b8364-a2b4-46cc-95be-28cbab62b8c2 on router
2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required
by one or more routes.', u'type': u'RouterInterfaceInUseByRoute',
u'detail': u''}}

I am confused at this point as all the routes have been cleared but still
it is throwing an error saying the router is required by multiple routes.

Thanks,
Sayali.


On Sat, Aug 2, 2014 at 3:25 PM, ZZelle  wrote:

> First command is of course:
> *   neutron router-show **2f16d846-b6aa-43a3-adbe-*
> *7f91a1389b7f*
> not
> *   neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f*
>
>
> On Sat, Aug 2, 2014 at 11:54 AM, ZZelle  wrote:
>
>> Hi,
>>
>> According to the first error message, the subnet you try to unbind is
>> used in router routes, you can see current router routes using:
>>
>>*neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f*
>>
>> you need to update them before unbind:
>>
>> *   neutron router-update **2f16d846-b6aa-43a3-adbe-*
>> *7f91a1389b7f --routes type=dict list=true destination=...,nexthop=...
>> [destination=...,nexthop=...[...]] *
>> or clear router routes:
>>
>>
>>
>> *   neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes
>> action=clear *
>> And finally retry to unbind the subnet.
>>
>>
>>
>> Cédric,
>> ZZelle@IRC
>>
>>
>> On Sat, Aug 2, 2014 at 9:56 AM, Sayali Lunkad 
>> wrote:
>>
>>> Hi,
>>>
>>> I am facing trouble deleting a router from my openstack deployment.
>>>
>>> I have tried the following commands on the *controller node* and pasted
>>> the output.
>>>
>>> *neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>> 962b8364-a2b4-46cc-95be-28cbab62b8c2
>>> 409-{u'NeutronError': {u'message': u'Router interface for subnet
>>> 962b8364-a2b4-46cc-95be-28cbab62b8c2 on router
>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required
>>> by one or more routes.', u'type': u'RouterInterfaceInUseByRoute',
>>> u'detail': u''}}
>>>
>>>  *neutron port-delete*  ec1aac66-481d-488e-860b-53b88d950ac7
>>> 409-{u'NeutronError': {u'message': u'Port
>>> ec1aac66-481d-488e-860b-53b88d950ac7 has owner network:router_interface and
>>> therefore cannot be deleted directly via the port API.', u'type':
>>> u'L3PortInUse', u'detail': u''}}
>>>
>>>  *neutron router-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>> 409-{u'NeutronError': {u'message': u'Router
>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f still has active ports', u'type':
>>> u'RouterInUse', u'detail': u''}}
>>>
>>> *neutron l3-agent-router-remove* 7a977e23-767f-418e-8429-651c4232548c
>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>> This removes the router from the l3 agent and attaches it to another one
>>> as seen below.
>>>
>>>  *neutron l3-agent-list-hosting-router*
>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>>
>>> +--+--++---+
>>> | id   | host |
>>> admin_state_up | alive |
>>>
>>> +--+--++---+
>>> | 96e1371a-be03-42ed-8141-3b0027d3a82f | alln01-1-csx-net-004 |
>>> True   | :-)   |
>>>
>>> +--+--++---+
>>>
>>>
>>> I have also run the commands below on the *network node* which worked
>>> fine.
>>>
>>> *ip netns delete* qrouter-2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>>
>>> *ovs-vsctl del-port* br-int qr-ec1aac66-48
>>>
>>> Could someone please tell me what can be done to delete the router or is
>>> this some bug  I am hitting.
>>>
>>> Thanks,
>>> Sayali.
>>>
>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> 

Re: [openstack-dev] [Neutron] Route cannot be deleted

[ZZelle]

First command is of course:
*   neutron router-show **2f16d846-b6aa-43a3-adbe-*
*7f91a1389b7f*
not
*   neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f*


On Sat, Aug 2, 2014 at 11:54 AM, ZZelle  wrote:

> Hi,
>
> According to the first error message, the subnet you try to unbind is used
> in router routes, you can see current router routes using:
>
>*neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f*
>
> you need to update them before unbind:
>
> *   neutron router-update **2f16d846-b6aa-43a3-adbe-*
> *7f91a1389b7f --routes type=dict list=true destination=...,nexthop=...
> [destination=...,nexthop=...[...]] *
> or clear router routes:
>
>
>
> *   neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes
> action=clear *
> And finally retry to unbind the subnet.
>
>
>
> Cédric,
> ZZelle@IRC
>
>
> On Sat, Aug 2, 2014 at 9:56 AM, Sayali Lunkad 
> wrote:
>
>> Hi,
>>
>> I am facing trouble deleting a router from my openstack deployment.
>>
>> I have tried the following commands on the *controller node* and pasted
>> the output.
>>
>> *neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>> 962b8364-a2b4-46cc-95be-28cbab62b8c2
>> 409-{u'NeutronError': {u'message': u'Router interface for subnet
>> 962b8364-a2b4-46cc-95be-28cbab62b8c2 on router
>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required
>> by one or more routes.', u'type': u'RouterInterfaceInUseByRoute',
>> u'detail': u''}}
>>
>>  *neutron port-delete*  ec1aac66-481d-488e-860b-53b88d950ac7
>> 409-{u'NeutronError': {u'message': u'Port
>> ec1aac66-481d-488e-860b-53b88d950ac7 has owner network:router_interface and
>> therefore cannot be deleted directly via the port API.', u'type':
>> u'L3PortInUse', u'detail': u''}}
>>
>>  *neutron router-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>> 409-{u'NeutronError': {u'message': u'Router
>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f still has active ports', u'type':
>> u'RouterInUse', u'detail': u''}}
>>
>> *neutron l3-agent-router-remove* 7a977e23-767f-418e-8429-651c4232548c
>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>> This removes the router from the l3 agent and attaches it to another one
>> as seen below.
>>
>>  *neutron l3-agent-list-hosting-router*
>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>
>> +--+--++---+
>> | id   | host |
>> admin_state_up | alive |
>>
>> +--+--++---+
>> | 96e1371a-be03-42ed-8141-3b0027d3a82f | alln01-1-csx-net-004 |
>> True   | :-)   |
>>
>> +--+--++---+
>>
>>
>> I have also run the commands below on the *network node* which worked
>> fine.
>>
>> *ip netns delete* qrouter-2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>>
>> *ovs-vsctl del-port* br-int qr-ec1aac66-48
>>
>> Could someone please tell me what can be done to delete the router or is
>> this some bug  I am hitting.
>>
>> Thanks,
>> Sayali.
>>
>>
>>
>> ___
>> 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] Route cannot be deleted

[ZZelle]

Hi,

According to the first error message, the subnet you try to unbind is used
in router routes, you can see current router routes using:

   *neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f*

you need to update them before unbind:

*   neutron router-update **2f16d846-b6aa-43a3-adbe-*
*7f91a1389b7f --routes type=dict list=true destination=...,nexthop=...
[destination=...,nexthop=...[...]]*
or clear router routes:



*   neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes
action=clear*
And finally retry to unbind the subnet.



Cédric,
ZZelle@IRC


On Sat, Aug 2, 2014 at 9:56 AM, Sayali Lunkad 
wrote:

> Hi,
>
> I am facing trouble deleting a router from my openstack deployment.
>
> I have tried the following commands on the *controller node* and pasted
> the output.
>
> *neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
> 962b8364-a2b4-46cc-95be-28cbab62b8c2
> 409-{u'NeutronError': {u'message': u'Router interface for subnet
> 962b8364-a2b4-46cc-95be-28cbab62b8c2 on router
> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required
> by one or more routes.', u'type': u'RouterInterfaceInUseByRoute',
> u'detail': u''}}
>
>  *neutron port-delete*  ec1aac66-481d-488e-860b-53b88d950ac7
> 409-{u'NeutronError': {u'message': u'Port
> ec1aac66-481d-488e-860b-53b88d950ac7 has owner network:router_interface and
> therefore cannot be deleted directly via the port API.', u'type':
> u'L3PortInUse', u'detail': u''}}
>
>  *neutron router-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
> 409-{u'NeutronError': {u'message': u'Router
> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f still has active ports', u'type':
> u'RouterInUse', u'detail': u''}}
>
> *neutron l3-agent-router-remove* 7a977e23-767f-418e-8429-651c4232548c
> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
> This removes the router from the l3 agent and attaches it to another one
> as seen below.
>
>  *neutron l3-agent-list-hosting-router*
> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>
> +--+--++---+
> | id   | host |
> admin_state_up | alive |
>
> +--+--++---+
> | 96e1371a-be03-42ed-8141-3b0027d3a82f | alln01-1-csx-net-004 |
> True   | :-)   |
>
> +--+--++---+
>
>
> I have also run the commands below on the *network node* which worked
> fine.
>
> *ip netns delete* qrouter-2f16d846-b6aa-43a3-adbe-7f91a1389b7f
>
> *ovs-vsctl del-port* br-int qr-ec1aac66-48
>
> Could someone please tell me what can be done to delete the router or is
> this some bug  I am hitting.
>
> Thanks,
> Sayali.
>
>
>
> ___
> 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] How to run 'tempest-dsvm-full' locally

[Nikesh Kumar Mahalka]

I want to run 'tempest-dsvm-full' on my local devstack environment as
mentioned in below link:

https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver


Currently i have not proposed a blue-print for cinder driver and my company
have not signed CLA.
So i want to first run  'tempest-dsvm-full' locally.


How can i run this locally without signing any CLA?



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

[openstack-dev] [Neutron] Route cannot be deleted

[Sayali Lunkad]

Hi,

I am facing trouble deleting a router from my openstack deployment.

I have tried the following commands on the *controller node* and pasted the
output.

*neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
962b8364-a2b4-46cc-95be-28cbab62b8c2
409-{u'NeutronError': {u'message': u'Router interface for subnet
962b8364-a2b4-46cc-95be-28cbab62b8c2 on router
2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required
by one or more routes.', u'type': u'RouterInterfaceInUseByRoute',
u'detail': u''}}

 *neutron port-delete*  ec1aac66-481d-488e-860b-53b88d950ac7
409-{u'NeutronError': {u'message': u'Port
ec1aac66-481d-488e-860b-53b88d950ac7 has owner network:router_interface and
therefore cannot be deleted directly via the port API.', u'type':
u'L3PortInUse', u'detail': u''}}

 *neutron router-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f
409-{u'NeutronError': {u'message': u'Router
2f16d846-b6aa-43a3-adbe-7f91a1389b7f still has active ports', u'type':
u'RouterInUse', u'detail': u''}}

*neutron l3-agent-router-remove* 7a977e23-767f-418e-8429-651c4232548c
2f16d846-b6aa-43a3-adbe-7f91a1389b7f
This removes the router from the l3 agent and attaches it to another one as
seen below.

 *neutron l3-agent-list-hosting-router*
2f16d846-b6aa-43a3-adbe-7f91a1389b7f
+--+--++---+
| id   | host |
admin_state_up | alive |
+--+--++---+
| 96e1371a-be03-42ed-8141-3b0027d3a82f | alln01-1-csx-net-004 |
True   | :-)   |
+--+--++---+


I have also run the commands below on the *network node* which worked fine.

*ip netns delete* qrouter-2f16d846-b6aa-43a3-adbe-7f91a1389b7f

*ovs-vsctl del-port* br-int qr-ec1aac66-48

Could someone please tell me what can be done to delete the router or is
this some bug  I am hitting.

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

Re: [openstack-dev] [Trove] Backup/restore namespace config move has leftovers

[Denis Makogon]

суббота, 2 августа 2014 г. пользователь Mark Kirkwood написал:

> On 02/08/14 18:24, Denis Makogon wrote:
>
>  Mark, we don't have to add backup/restore namespace options to datastores
>> that does't support backup/restore feature.
>> You should take a look how backup procedure is being executed at
>> Trove-API service site, see
>> https://github.com/openstack/trove/blob/master/trove/backup/models.py
>> (Method called _validate_can_perform_action)
>>
>> If you'll have another questions, feel free to catch me up at IRC
>> (denis_makogon).
>>
>>
> Thanks Denis - I did wonder if it was an optional specification! Doh!
> However, while I'm a bit ignorant wrt redis and cassandra, I do have a bit
> todo with mongo and that certainly *does* support backup/restore...
>
>
Thank to you too, Mark. There were already filed several BPs related to
back/restore procedure: for Cassandra, for Mongodb( through mongodump and
tayra). Some of them are already hanging at review queue.

Best regards,
Denis Makogon


> Cheers
>
> Mark
>
>
> ___
> 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