Re: [openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[Elancheran Subramanian]

Yes, there is a config option for *oslo_messaging_rabbit* 
default_notification_retry_attempts 
http://docs.openstack.org/mitaka/config-reference/compute/rpc.html


The problem with Nova and Neutron provide the retry mechanism, there is no 
configuration on nova or neutron, which can be passed onto the 
also_messaging. I will add a patch so that it would pick up from the 
configuration in oslo_messaging itself.  

Thanks & Regards,
Cheran



On 2/14/17, 9:32 PM, "Ken Giusti"  wrote:

>On Tue, Feb 14, 2017 at 2:52 PM, Elancheran Subramanian
> wrote:
>> Hello All,
>> This is reg limiting the number of retries for Kafka driver support on 
>>Nova
>> and Neutron.
>>
>> While trying out the oslo messaging notifications support for Kafka on 
>>Nova
>> and Neutron, the Kafka driver doesn’t support limiting the number of 
>>retries
>> for failed messages. When I checked the code, currently there is no
>> configuration which support that, though the send_notification has retry
>> 
>>https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_d
>>rivers/impl_kafka.py#L336
>> but it’s not set or passed from component’s (nova or neutron’s)
>> configuration. Is there any configuration which I’m missing? Please let 
>>me
>> know.
>>
>
>You haven't missed anything - the kafka driver doesn't provide a means
>to set a default retry via its configuration.
>The expectation is that the caller (nova/neutron) would provide a
>retry value when constructing a Notifier instance.
>
>There was such a config option for the rabbitmq driver
>(rabbit_max_retries) but that was removed because it broke
>*something* - can't remember exactly the reason tho, sorry.
>
>>
>> Thanks in advance,
>> Cheran
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
>-- 
>Ken Giusti  (kgiu...@gmail.com)
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[Elancheran Subramanian]

Hello All,
This is reg limiting the number of retries for Kafka driver support on Nova and 
Neutron.

While trying out the oslo messaging notifications support for Kafka on Nova and 
Neutron, the Kafka driver doesn’t support limiting the number of retries for 
failed messages. When I checked the code, currently there is no configuration 
which support that, though the send_notification has retry 
https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_kafka.py#L336
 but it’s not set or passed from component’s (nova or neutron’s) configuration. 
Is there any configuration which I’m missing? Please let me know.

Thanks in advance,
Cheran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

[Elancheran Subramanian]

On 11/30/16, 4:45 PM, "Joshua Harlow"  wrote:


>Mehdi Abaakouk wrote:
>> Hi,
>>
>> I think my subject is clear :) , but I will add some facts that can help
>> to the decision:
>> * It uses only deprecated python-kafka API [1] [2]
>> * It's not python3 compatible [3]
>> * We still don't have kafka testing in gate
>> So, one year after the driver introduction, this one is still in bad 
>>shape
>> and doesn't match the requirements [4].
>>
>> These reviews looks abandoned/outdated/unmaintained:
>>
>> [1] https://review.openstack.org/#/c/297994/ [2]
>> https://review.openstack.org/#/c/332105/
>>
>> Other links:
>>
>> [3] https://review.openstack.org/#/c/404802/
>> [4]
>> 
>>http://docs.openstack.org/developer/oslo.messaging/supported-messaging-dr
>>ivers.html#testing
>>
>>
>> And of course, we will not drop the code now, but just deprecate it for
>> removal.
>> Cheers,
>>
>
>IMHO, not just yet, dims and I have been trying to use this driver 
>recently (for notifications only in my case) and I am more than willing 
>to try to get the changes needed to get this into a healthy state (from 
>my understanding dims and friends have been working through this as well).
>
>One of the places for gate testing that is still being worked on is the 
>following: https://github.com/jd/pifpaf/pull/28
>
>That will aid with some of the gate testing.
>
>-Josh

As Josh stated above, currently we have back ported the kafka driver to 
Stable/liberty https://github.com/tsecheran/oslo.messaging/pull/2 to get 
the notifications split work for Nova and Neutron in our cloud. It’s 
working fine and in early POC state, we need to still work on that pifpaf 
PR https://github.com/jd/pifpaf/pull/28 for the unit testing. 

- Cheran

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Splitting notifications from rpc (and questions + work around this)

[Elancheran Subramanian]

Hi Dims,
Thanks for sharing… 

Just wanted to check whether there is any development for Nova and Neutron 
going on, which we can leverage?  

Thanks,
Cheran




On 11/3/16, 12:51 AM, "Davanum Srinivas"  wrote:

>Josh,
>
>Kirill Bespalov put together this doc of which components will work
>with separate rpc and notification configurations:
>https://docs.google.com/document/d/1CU0KjL9iV8vut76hg9cFuWQGSJawuNq_cK7vRF
>_KyAA/edit?usp=sharing
>
>From my team, Oleksii Zamiatin is trying to scale up ZMQ beyond 200+
>nodes for RPC.
>
>Ilya Tyaptin's review is stuck because Monasca folks have trouble
>using the newer python-kafka version:
>https://review.openstack.org/#/c/332105/
>https://review.openstack.org/#/c/316259/
>
>As you can tell, we are trying to offer RabbitMQ or ZMQ for RPC and
>RabbitMQ or Kafka for Notifications.
>
>Hope this helps.
>
>Thanks,
>Dims
>
>On Wed, Nov 2, 2016 at 8:11 PM, Joshua Harlow  
>wrote:
>> Hi folks,
>>
>> There was a bunch of chatter at the summit about how there are really 
>>two
>> different types of (oslo) messaging usage that exist in openstack and 
>>how
>> they need not be backed by the same solution type (rabbitmq, qpid,
>> kafka...).
>>
>> For those that were not at the oslo sessions:
>>
>> https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads#Oslo
>>
>> The general gist was though that we need to make sure people really do 
>>know
>> that there are two very different types of messaging usage in openstack 
>>and
>> to ensure that operators (and developers) are picking the right backing
>> technology for each type.
>>
>> So some questions naturally arise out of this.
>>
>> * Where are the best practices with regard to selection of the best 
>>backend
>> type for rpc (and one for notifications); is this something 
>>oslo.messaging
>> should work through (or can the docs team and operator group also help 
>>in
>> making this)?
>>
>> * What are the tradeoffs in using the same (or different) technology 
>>for rpc
>> and notifications?
>>
>> * Is it even possible for all oslo.messaging consuming projects to be 
>>able
>> to choose 2 different backends, are consuming projects consuming the 
>>library
>> correctly so that they can use 2 different backends?
>>
>> * Is devstack able to run with say kafka for notifications and rabbitmq 
>>for
>> rpc (if not, is there any work item the oslo group can help with to make
>> this possible) so that we can ensure and test that all projects can work
>> correctly with appropriate (and possibly different) backends?
>>
>> * Any other messaging, arch-wg work that we (oslo or others) can help 
>>out
>> with to make sure that projects (and operators) are using the right
>> technology for the right use (and not just defaulting to RPC over 
>>rabbitmq
>> because it exists, when in reality something else might be a better 
>>choice)?
>>
>> * More(?)
>>
>> Just wanted to get this conversation started, because afaik it's one 
>>that
>> has not been widely circulated (and operators have been setting up 
>>rabbitmq
>> in various HA and clustered and ... modes, when in reality thinking 
>>through
>> what and how it is used may be more appropriate); this also applies to
>> developers since some technical solutions in openstack seem to be 
>>created
>> due to (in-part) rabbitmq shortcomings (cells v1 afaik was *in* part 
>>created
>> due to scaling issues).
>>
>> -Josh
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>-- 
>Davanum Srinivas :: https://twitter.com/dims
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

[Elancheran Subramanian]

Hello Punal,
We do support both V2 and V3, that’s just a example I’ve stated BTW. We do have 
our own integration tests which are pretty much covers all our integration 
points with openstack. But we would like to leverage the tempest while doing 
our upstream merge for openstack components in CI.

I believe the tests support the include list, how can I exclude test? Any 
pointer would be a great help.

Thanks,
Cheran

From: punal patel mailto:punal.pa...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, August 16, 2016 at 4:16 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

Hi Cheran,

Best practice depends on your test plan and what coverage you. Does your test 
plan covers V3 Identity tests ? If it does and its failing, you should modify 
to make it work for your environment. Fast way to move forward is to exclude 
those tests.

-Punal

On Tue, Aug 16, 2016 at 3:40 PM, Elancheran Subramanian 
mailto:esubraman...@godaddy.com>> wrote:
Hello There,
I’m currently playing with using Tempest as our integration tests for our 
internal and external clouds, facing some issues with api which are not 
supported in our cloud. For ex, listing domains isn’t supported for any user, 
due to this V3 Identity tests are failing. So I would like to know what’s the 
best practice? Like fix those tests, and apply those fix as patch? Or just 
exclude those tests?

Would be great if anyone could share their experience on this.

Thanks & Regards,
Cheran

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [QA] Running Tempest tests for a customized cloud

[Elancheran Subramanian]

Hello There,
I’m currently playing with using Tempest as our integration tests for our 
internal and external clouds, facing some issues with api which are not 
supported in our cloud. For ex, listing domains isn’t supported for any user, 
due to this V3 Identity tests are failing. So I would like to know what’s the 
best practice? Like fix those tests, and apply those fix as patch? Or just 
exclude those tests?

Would be great if anyone could share their experience on this.

Thanks & Regards,
Cheran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Abishek Subramanian (absubram)]

Same here. I’m definitely interested in helping out but not sure how much time 
I can commit to. Will most definitely help out with reviews and other decision 
making process to help ensure magnum-ui is implemented and in the correct 
direction relating to Horizon.

From: Thai Q Tran mailto:tqt...@us.ibm.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, June 4, 2015 at 2:07 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - 
need a vote from the core team

I am interested but not sure how much time I have this release cycle. I can 
take on a more hands-off approach and help review to make sure that magnum-ui 
is align with future horizon directions.

-"Steven Dake (stdake)" mailto:std...@cisco.com>> wrote: 
-
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
From: "Steven Dake (stdake)" mailto:std...@cisco.com>>
Date: 06/04/2015 11:03AM
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need 
a vote from the core team

Hey folks,

I think it is critical for self-service needs that we have a Horizon dashboard 
to represent Magnum.  I know the entire Magnum team has no experience in UI 
development, but I have found atleast one volunteer Bradley Jones to tackle the 
work.

I am looking for more volunteers to tackle this high impact effort to bring 
Containers to OpenStack either in the existing Magnum core team or as new 
contributors.   If your interested, please chime in on this thread.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
We add these UI folks to the magnum-core team and trust them not to +2/+A 
Magnum infrastructure code.  This also preserves us as one team with one 
mission.

Option #2:
We make a new core team magnum-ui-core.  This presents special problems if the 
UI contributor team isn’t large enough to get reviews in.  I suspect Option #2 
will be difficult to execute.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Horizon] FFE request for Firewall Router insertion BP

[Abishek Subramanian (absubram)]

Dear Horizon community,

I would like to request an FFE for the review we have out currently for
the firewall feature in the project dashboard.

The review is at - https://review.openstack.org/#/c/162552/


This feature is very important for the neutron FWaaS community to move the
firewall feature from out of experimental stage.
It allows for firewalls to finally be applied to a router and having
Horizon support for this will greatly enhance the ability to use FWaaS.
The neutron side of the feature got merged just before the K-3 deadline
and there isn¹t a neutron client dependency on Horizon for this.

A final review version to address comments about UT and also a details
page will be made very shortly.
The review in its current state is ready to test and for anyone to try
out. Please make sure to include the q-fwaas service in your local.conf if
testing.


Requesting Akihiro and David to please sponsor reviews (as discussed on
IRC).

Much thanks and kind regards,

Abishek


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] Question about behavior of override_settings

[Abishek Subramanian (absubram)]

Hi,

This has to do with a patch I have out for review currently -
https://review.openstack.org/#/c/90093/

I believe version 5 to be the proper solution for the problem with the
unit tests that I am trying to fix.
However based on some comments that asked me to try a couple things,
version 7 is the latest one out but
I have a couple of questions regarding the behavior I am observing.


1. The diffs change the running of tests in admin/networks/tests.py -
A small snippet is this addition -
@override_settings(OPENSTACK_NEUTRON_NETWORK={'profile_support': None})
def test_network_create_get_with_no_profile(self):
self.test_network_create_get(test_with_profile=False)


This essentially defines a new UT which invokes an existing one but with
different settings.

This same patch for the similar project/networks/tests.py containing the
exact same test however does not work the same way.
It seems that the override_settings somehow finds fault with the
test.create_stubs of the base test.
I put this down to the possibly the definition of the test class itself.

In admin/networks it is - class NetworkTests(test.BaseAdminViewTests):
Whereas in project/networks it is - class NetworkTests(test.TestCase):

Anyone have any idea what the difference is between the two and also
why the BaseAdminViewTests would affect the settings differently?

Also would appreciate any further reviews on this.


Thanks!
Abishek


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

[openstack-dev] [horizon] Help debugging js files

[Abishek Subramanian (absubram)]

Hi,

I need to make some changes to the horizon.instances.js file and I was 
wondering what the best method would be to help debug issues in this file? Is 
there a debugger or something available to debug this file separately?

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

Re: [openstack-dev] [Horizon][dashboards] Running the 'profile' specific unit tests

[Abishek Subramanian (absubram)]

Just to add to this - Akihiro did mention the usage of @override_settings
I've seen examples of this in existing unit tests and I can implement
something 
similar. 

This will mean however that we will have the test with the default setting
and then the same test again with the override which accepts the
profile_id yes?


On 4/24/14 10:54 AM, "Abishek Subramanian (absubram)" 
wrote:

>Hi all, Akihiro,
>
>I wanted to get a little feedback on the issue regarding the running
>of the dashboard unit tests with the cisco n1k profiles
>(and very soon the cisco DFA profiles) and more specifically
>how to have existing network and instance unit tests run both
>with and without profiles.
>
>Currently there all tests relating to profiles are turned off
>by default. In order to run them, you need to manually go enable
>running them by changing the test/settings.py file.
>
>Based on community feedback and review comments from Akihiro, I raised
>this bug to fix this issue -
>https://bugs.launchpad.net/horizon/+bug/1229819
>I have an initial WIP review out for it as well that I'd appreciate
>feedback on.
>
>
>There are two kinds of 'profile' related tests. One set is directly
>part of the 'router' dashboard. These I have fixed via the review to now
>run always by default.
>There is another set - in existing network and instance launch unit tests.
>The issue with these tests is that the network create and nova server
>create 
>APIs will need a profile_id argument if and only if the appropriate
>neutron plugin is being used.
>
>If not, the neutron APIs will not take a profile_id argument.
>Hence, in horizon, the code checks to see if the profile_id should be
>given or not. 
>Similarly the unit tests mock this same behavior. The dilemma here is how
>to run the same unit test and hence the same portion of actual code once
>with 
>the profiles and once without.
>
>I'd appreciate any suggestions. Please let me know if there are any
>further 
>questions to clarify this problem.
>
>Regards,
>Abishek
>
>
>___
>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] [Horizon][dashboards] Running the 'profile' specific unit tests

[Abishek Subramanian (absubram)]

Hi all, Akihiro,

I wanted to get a little feedback on the issue regarding the running
of the dashboard unit tests with the cisco n1k profiles
(and very soon the cisco DFA profiles) and more specifically
how to have existing network and instance unit tests run both
with and without profiles.

Currently there all tests relating to profiles are turned off
by default. In order to run them, you need to manually go enable
running them by changing the test/settings.py file.

Based on community feedback and review comments from Akihiro, I raised
this bug to fix this issue -
https://bugs.launchpad.net/horizon/+bug/1229819
I have an initial WIP review out for it as well that I'd appreciate
feedback on.


There are two kinds of 'profile' related tests. One set is directly
part of the 'router' dashboard. These I have fixed via the review to now
run always by default.
There is another set - in existing network and instance launch unit tests.
The issue with these tests is that the network create and nova server
create 
APIs will need a profile_id argument if and only if the appropriate
neutron plugin is being used.

If not, the neutron APIs will not take a profile_id argument.
Hence, in horizon, the code checks to see if the profile_id should be
given or not. 
Similarly the unit tests mock this same behavior. The dilemma here is how
to run the same unit test and hence the same portion of actual code once
with 
the profiles and once without.

I'd appreciate any suggestions. Please let me know if there are any
further 
questions to clarify this problem.

Regards,
Abishek


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

Re: [openstack-dev] OpenStack/GSoC 2014 - Reviewing Applications

[Sriram Subramanian]

Davanum, are the scores private or is there a way to make them private?


On Sat, Mar 22, 2014 at 12:07 PM, Davanum Srinivas wrote:

> Dear Students,
>
> We received the following proposals:
>
> AMES-Cloud (Nagashree Bhat)
> A pre-caching system for OpenStack (Anastasis Andronidis)
> Proposal for Implementing an application-level FWaaS driver
> ((Zorp) Dániel Csubák)
> Cassandra and Redis storage backend for Openstack marconi (Jeremy
> Henriques)
> Openstack-OSLO :Add a New Backend to Oslo.Cache (sai krishna)
> Implement a Fuzz testing framework that can be run on Tempest
> (Manishanker Talusani)
> How to detect network anomalies from telemetry data within Openstack
> (mst89)
> Implement a re-usable shared library for VMware(oslo.vmware) (Masaru
> Nomura)
> Cross-services Scheduler project (Artem Shepelev)
> OpenStack/Marconi: Py3k support (Nataliia)
> Improve benchmarking context mechanism in Rally (Kumar Rishabh)
> Develop a benchmarking suite and new storage backends to OpenStack
> Marconi (Prashanth Raghu)
> Adding Redis as a Storage Backend to OpenStack Marconi (Chenchong Qin)
> Auto Benchmarking System for OpenStack (RobberPhex)
> Developing Benchmarks for Virtual Machines of OpenStack with Rally
> (Tzanetos Balitsaris)
> Add a new storage backend to the OpenStack Message Queuing Service
> (Victoria Martínez de la Cruz)
>
> Dear Mentors
> (ddutta/flwang/julim/hughsaunders/greghaynes/annegentle/sriramhere/arnaudleg/coroner/boris_42/blint/ybudupi/cppcabrera),
>
> Please log into the Google GSoC web-site and review **all** proposals
> within a week (our own deadline - say 29th).
>
> 1) Please click "Wish to mentor" on the left hand side, if you are
> willing to mentor this project.
>Yes, we should have more than one mentor. This is a way to mention
> that you are willing to mentor,
>actual assignment will happen later i believe. So please switch
> this on for all projects you are
>interested in.
>
> 2) If you have a question about a proposal and need a response from
> the candidate, please leave
>a comment for them. If you want to ask a observation/question to
> other mentors or me, leave a
>comment marked "Private"
>
> 3) To assign a score. Please click on the number of start in "My
> score:" at the bottom
> 5 = amazing applicant, could be a module maintainer on completing
> the program
> 4 = strong applicant, will do a good job
> 3 = good applicant, but is somewhat inexperienced
> 2 = is unlikely to do a good job
> 1 = not a good candidate
>
> Please feel free to leave detailed notes on candidates you know well
> for other mentors (Please mark comments as "Private")
>
> If you are not able to help with this exercise, please let me know ASAP.
>
> If anyone else would like to step up and be a Mentor for any of these
> projects/students, please register in the Google GSoC site and let me
> know your "username".
>
> Thanks,
> dims
>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



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

[openstack-dev] [Horizon] Regarding bug/bp https://bugs.launchpad.net/horizon/+bug/1285298

[Abishek Subramanian (absubram)]

Hi all, Akihiro, David,

This is regarding the review for - https://review.openstack.org/#/c/76653/

Akihiro - Thanks for the review as always and as I mentioned in the review
comment 
I completely agree with you. This is a small featurette.

However this is small in that it adds to a chociefield in an existing
forms.py
attribute that I left out which neutron supports.
And so in addition, I also had to add some code to my clean routine and yes
update the string in the create description to include this new option.
I have more test code really, than actual code.

It was small enough, and hence I made request that this be treated as
a bug and not a bp. And only then did I proceed to open the bug.

I will respect what the community decides on this. Please let me know
how we wish to proceed.


Thanks and regards,
Abishek


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

Re: [openstack-dev] OpenStack/GSoC

[Sriram Subramanian]

Victoria,

When you click "My Dashboard" on the left hand side, you will see
Connections, Proposals etc on your right, in the dashboard. Right below
"Connections", there are two links in smaller font, one which is the link
to Connect (circled in blue in the attached snapshot).
If you tried right after creating your profile, try logging out and in.
When I created the profile, I remember having some issues around accessing
profile (not the dashboard, but entire profile).

thanks
-Sriram


On Wed, Mar 12, 2014 at 1:32 PM, Victoria Martínez de la Cruz <
victo...@vmartinezdelacruz.com> wrote:

> Hi,
>
> Thanks for working on the template, it sure ease things for students.
>
> I can't find the "Connect with organizations" link, does anyone have the
> same problem?
>
> I confirm my assistance to tomorrow's meeting, thanks for organizing it! +1
>
> Cheers,
>
> Victoria
>
>
>
> 2014-03-11 14:29 GMT-03:00 Davanum Srinivas :
>
> Hi,
>>
>> Mentors:
>> * Please click on "My Dashboard" then "Connect with organizations" and
>> request a connection as a mentor (on the GSoC web site -
>> http://www.google-melange.com/)
>>
>> Students:
>> * Please see the Application template you will need to fill in on the
>> GSoC site.
>>   http://www.google-melange.com/gsoc/org2/google/gsoc2014/openstack
>> * Please click on "My Dashboard" then "Connect with organizations" and
>> request a connection
>>
>> Both Mentors and Students:
>> Let's meet on #openstack-gsoc channel on Thursday 9:00 AM EDT / 13:00
>> UTC for about 30 mins to meet and greet since all application deadline
>> is next week. If this time is not convenient, please send me a note
>> and i'll arrange for another time say on friday as well.
>>
>> http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T09&p1=43&am=30
>>
>> We need to get an idea of how many slots we need to apply for based on
>> really strong applications with properly fleshed out project ideas and
>> mentor support. Hoping the meeting on IRC will nudge the students and
>> mentors work towards that goal.
>>
>> Thanks,
>> dims
>>
>> ___
>> 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
>
>


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

Re: [openstack-dev] [Horizon] test_launch_instance_post questions

[Abishek Subramanian (absubram)]

Hi all, jpich, amotoki and toshi,

I'm including a link to a small set of diff to show you what I'm trying to
do.
It is obviously a small subset of what I want to do.
https://www.dropbox.com/s/r7khv7gvdcd02gl/launch_instance_post_diff.patch

But to illustrate the issue I am seeing and to help my understanding of
this 
test, all I'm doing is this - I've added a new network in the neutron_data
that is similar to the first network. Then I have replaced the nics
argument 
which is needed to launch an instance. It now takes my new network instead
of
the first network.

However the test fails because when it is run, it is supposed to expect my
new network
but it actually finds the first network in the code.


The problem in code is here -
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashbo
ards/project/instances/workflows/create_instance.py

Lines 700-705:
netids = context.get('network_id', None)
if netids:
nics = [{"net-id": netid, "v4-fixed-ip": ""}
for netid in netids]
else:
nics = None

This part is confusing. In the UT environment, can I please get some help
in understanding how this line

seems to always pick the first network when this particular test is run?


Thanks!


On 3/11/14 9:58 AM, "Abishek Subramanian (absubram)" 
wrote:

>Hi,
>
>Can I please get some help with this UT?
>I am having a little issue with the nics argument -
>nics = [{"net-id": netid, "v4-fixed-ip": ""}
>
>
>I wish to add a second network to this argument, but somehow
>the UT only picks up the first network.
>
>Any guidance will be appreciated.
>
>
>Thanks!
>
>
>On 3/6/14 12:06 PM, "Abishek Subramanian (absubram)" 
>wrote:
>
>>Hi,
>>
>>I had a couple of questions regarding this UT and the
>>JS template that it ends up using.
>>Hopefully someone can point me in the right direction
>>and help me understand this a little better.
>>
>>I see that for this particular UT, we have a total of 3 networks
>>in the network_list (the second network is supposed to be disabled
>>though).
>>For the nic argument needed by the nova/server_create API though we
>>only pass the first network's net_id.
>>
>>I am trying to modify this unit test so as to be able to accept 2
>>network_ids 
>>instead of just one. This should be possible yes?
>>We can have two nics in an instance of just one?
>>However, I always see that when the test runs,
>>in code it only finds the first network from the list.
>>
>>This line of code -
>>
>> if netids:
>>nics = [{"net-id": netid, "v4-fixed-ip": ""}
>>for netid in netids]
>>
>>There's always just one net-id in this dictionary even though I've added
>>a new network in the neutron test_data. Can someone please help me
>>figure out what I might be doing wrong?
>>
>>How does the JS code in horizon.instances.js file work?
>>I assume this is where the network list is obtained from?
>>How does this translate in the unit test environment?
>>
>>
>>
>>Thanks!
>>Abishek
>>
>>
>>___
>>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] [Horizon] Edit subnet in workflows - ip_version hidden?

[Abishek Subramanian (absubram)]

Thanks Radomir.

Yes I've changed it to a readonly. But just wanted to double check
I didn't end up breaking something elsewhere :)

Althouh - how up to date is this code?

These are the actual lines of code -

# NOTE(amotoki): When 'disabled' attribute is set for the ChoiceField
# and ValidationError is raised for POST request, the initial value of
# the ip_version ChoiceField is not set in the re-displayed form
# As a result, 'IPv4' is displayed even when IPv6 is used if
# ValidationError is detected. In addition 'required=True' check
complains
# when re-POST since the value of the ChoiceField is not set.
# Thus now I use HiddenInput for the ip_version ChoiceField as a work
# around.
ip_version = forms.ChoiceField(choices=[(4, 'IPv4'), (6, 'IPv6')],
   #widget=forms.Select(
   #attrs={'disabled': 'disabled'}),
   widget=forms.HiddenInput(),
   label=_("IP Version"))




I don't think ip_version even has an attribute or an option to be set to
'disabled'.
Is this from an old version where the create side got fixed but the update
side was forgotten about?


On 3/11/14 11:30 AM, "Radomir Dopieralski"  wrote:

>On 11/03/14 15:52, Abishek Subramanian (absubram) wrote:
>> Hi,
>> 
>> I had a question regarding the
>> dashboards/project/networks/subnets/workflows.py
>> file and in particular the portion of the ip_version field.
>> 
>> It is marked as a hidden input field for the update subnet class with
>>this
>> note.
>> 
>> # NOTE(amotoki): When 'disabled' attribute is set for the ChoiceField
>> # and ValidationError is raised for POST request, the initial value
>>of
>> # the ip_version ChoiceField is not set in the re-displayed form
>> # As a result, 'IPv4' is displayed even when IPv6 is used if
>> # ValidationError is detected. In addition 'required=True' check
>> complains
>> # when re-POST since the value of the ChoiceField is not set.
>> # Thus now I use HiddenInput for the ip_version ChoiceField as a
>>work
>> # around.
>> 
>> 
>> 
>> Can I get a little more context to this please?
>> I'm not sure I understand why it says this field always is displayed as
>> IPv4.
>> Is this still the case? Adding some debug logs I seem to see that the
>> ipversion is correctly being detected as 4 or 6 as the case may be.
>
>Some browsers (Chrome, iirc) will not submit the values from form fields
>that are disabled. That means, that when re-displaying this form
>(after an error in any other field, for example), that field's value
>will be missing, and the browser will happily display the first option,
>which is ipv4.
>
>Another solution could be perhaps using "readonly" instead of "disabled".
>
>-- 
>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] [Horizon] Edit subnet in workflows - ip_version hidden?

[Abishek Subramanian (absubram)]

Hi,

I had a question regarding the
dashboards/project/networks/subnets/workflows.py
file and in particular the portion of the ip_version field.

It is marked as a hidden input field for the update subnet class with this
note.

# NOTE(amotoki): When 'disabled' attribute is set for the ChoiceField
# and ValidationError is raised for POST request, the initial value of
# the ip_version ChoiceField is not set in the re-displayed form
# As a result, 'IPv4' is displayed even when IPv6 is used if
# ValidationError is detected. In addition 'required=True' check
complains
# when re-POST since the value of the ChoiceField is not set.
# Thus now I use HiddenInput for the ip_version ChoiceField as a work
# around.



Can I get a little more context to this please?
I'm not sure I understand why it says this field always is displayed as
IPv4.
Is this still the case? Adding some debug logs I seem to see that the
ipversion is correctly being detected as 4 or 6 as the case may be.

Thanks!



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

[openstack-dev] [Horizon] test_launch_instance_post questions

[Abishek Subramanian (absubram)]

Hi,

Can I please get some help with this UT?
I am having a little issue with the nics argument -
nics = [{"net-id": netid, "v4-fixed-ip": ""}


I wish to add a second network to this argument, but somehow
the UT only picks up the first network.

Any guidance will be appreciated.


Thanks!


On 3/6/14 12:06 PM, "Abishek Subramanian (absubram)" 
wrote:

>Hi,
>
>I had a couple of questions regarding this UT and the
>JS template that it ends up using.
>Hopefully someone can point me in the right direction
>and help me understand this a little better.
>
>I see that for this particular UT, we have a total of 3 networks
>in the network_list (the second network is supposed to be disabled
>though).
>For the nic argument needed by the nova/server_create API though we
>only pass the first network's net_id.
>
>I am trying to modify this unit test so as to be able to accept 2
>network_ids 
>instead of just one. This should be possible yes?
>We can have two nics in an instance of just one?
>However, I always see that when the test runs,
>in code it only finds the first network from the list.
>
>This line of code -
>
> if netids:
>nics = [{"net-id": netid, "v4-fixed-ip": ""}
>for netid in netids]
>
>There's always just one net-id in this dictionary even though I've added
>a new network in the neutron test_data. Can someone please help me
>figure out what I might be doing wrong?
>
>How does the JS code in horizon.instances.js file work?
>I assume this is where the network list is obtained from?
>How does this translate in the unit test environment?
>
>
>
>Thanks!
>Abishek
>
>
>___
>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 and GSoC 2014

[Sriram Subramanian]

Davanum,

Now that students are in application phase, how can we mentors help them?

Any meetings planned for the mentors to sync up on next steps.

thanks,
-Sriram


On Mon, Feb 24, 2014 at 12:35 PM, Victoria Martínez de la Cruz <
victo...@vmartinezdelacruz.com> wrote:

> So happy to hear that! Congrats all!
>
>
> 2014-02-24 16:16 GMT-03:00 Davanum Srinivas :
>
> Hi all,
>>
>> We're in! Just got notified by Admin Team that our Organization
>> Application has been accepted. I've updated the etherpad with the full
>> responses from them.
>>
>> https://etherpad.openstack.org/p/gsoc2014orgapp
>>
>> thanks,
>> dims
>>
>> ___
>> 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
>
>


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

[openstack-dev] [Openstack-dev][Horizon] test_launch_instance_post questions

[Abishek Subramanian (absubram)]

Hi,

I had a couple of questions regarding this UT and the
JS template that it ends up using.
Hopefully someone can point me in the right direction
and help me understand this a little better.

I see that for this particular UT, we have a total of 3 networks
in the network_list (the second network is supposed to be disabled though).
For the nic argument needed by the nova/server_create API though we
only pass the first network's net_id.

I am trying to modify this unit test so as to be able to accept 2
network_ids 
instead of just one. This should be possible yes?
We can have two nics in an instance of just one?
However, I always see that when the test runs,
in code it only finds the first network from the list.

This line of code -

 if netids:
nics = [{"net-id": netid, "v4-fixed-ip": ""}
for netid in netids]

There's always just one net-id in this dictionary even though I've added
a new network in the neutron test_data. Can someone please help me
figure out what I might be doing wrong?

How does the JS code in horizon.instances.js file work?
I assume this is where the network list is obtained from?
How does this translate in the unit test environment?



Thanks!
Abishek


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

[openstack-dev] [Cinder] FFE for vmdk-storage-policy-volume-type

[Subramanian]

Hi,

https://blueprints.launchpad.net/cinder/+spec/vmdk-storage-policy-volume-type
.

This is a blueprint that I am working on since Dec 2013 and as far I
remember it was targetted to icehouse-3. Just today I noticed that it was
moved to "future", so should have feel through the cracks for core
reviewers.Is there a chance that this can still make it into icehouse?
Given that the change is fairly isolated in vmdk driver, and that the code
across 4 patches [1] that implement this blueprint has been fairly
reviewed, can I request for an FFE for this one?

Thanks,
Subbu

[1]
https://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:bp/vmdk-storage-policy-volume-type,n,z
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron][IPv6] New Subnet options editable?

[Abishek Subramanian (absubram)]

Hi,

I just wanted to find out if the ipv6_ra_mode and ipv6_address_mode fields
are editable using neutron subnet-update? Or are they meant to be
non-editable
fields like the cidr addresses?

Thanks!

On 2/28/14 10:55 AM, "Abishek Subramanian (absubram)" 
wrote:

>Hi,
>
>I just wanted to find out if anyone had been able to test using Horizon?
>Was everything ok?
>
>Additionally wanted to confirm - the two modes can be updated too yes
>when using neutron subnet-update?
>
>
>Thanks!
>
>On 2/18/14 12:58 PM, "Abishek Subramanian (absubram)" 
>wrote:
>
>>Hi shshang, all,
>>
>>I have some preliminary Horizon diffs available and if anyone
>>would be kind enough to patch them and try to test the
>>functionality, I'd really appreciate it.
>>I know I'm able to create subnets successfully with
>>the two modes but if there's anything else you'd like
>>to test or have any other user experience comments,
>>please feel free to let me know.
>>
>>The diffs are at -  https://review.openstack.org/74453
>>
>>Thanks!!
>>
>


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

[openstack-dev] [neutron][IPv6] Testing functionality of IPv6 modes using Horizon

[Abishek Subramanian (absubram)]

Hi,

I just wanted to find out if anyone had been able to test using Horizon?
Was everything ok?

Additionally wanted to confirm - the two modes can be updated too yes
when using neutron subnet-update?


Thanks!

On 2/18/14 12:58 PM, "Abishek Subramanian (absubram)" 
wrote:

>Hi shshang, all,
>
>I have some preliminary Horizon diffs available and if anyone
>would be kind enough to patch them and try to test the
>functionality, I'd really appreciate it.
>I know I'm able to create subnets successfully with
>the two modes but if there's anything else you'd like
>to test or have any other user experience comments,
>please feel free to let me know.
>
>The diffs are at -  https://review.openstack.org/74453
>
>Thanks!!
>


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

[openstack-dev] [neutron][IPv6] Testing functionality of IPv6 modes using Horizon

[Abishek Subramanian (absubram)]

Hi shshang, all,

I have some preliminary Horizon diffs available and if anyone
would be kind enough to patch them and try to test the
functionality, I'd really appreciate it.
I know I'm able to create subnets successfully with
the two modes but if there's anything else you'd like
to test or have any other user experience comments,
please feel free to let me know.

The diffs are at -  https://review.openstack.org/74453

Thanks!!


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

Re: [openstack-dev] [cinder]Multiple backends

[Subramanian]

I think you should look at the cinder scheduler code that selects a host
based on the volume type.
https://github.com/openstack/cinder/tree/master/cinder/scheduler.

BTW, cinder dev tend to hang out on #openstack-cinder channel.

Thanks,
Subbu


On Mon, Feb 17, 2014 at 11:35 AM, iKhan  wrote:

> Hi All,
>
> I'm just curious on how the manager.py is choosing backend while creating
> volume, I know volume type is set but where is this being processed?
>
> I am sorry if this is a basic question, but didn't got any help from
> #openstack-dev IRC channel so was left without option to post here.
>
> --
> Thanks,
> IK
>
> ___
> 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] [Openstack][Horizon] switchable switched classes in forms.py

[Abishek Subramanian (absubram)]

Hi,

I can see that the forms.py file can have parameters/inputs that are of class 
type "switchable switched", i.e. this field 'B' will appear on the form if it's 
'switched' based on a choice from a previous field 'A'. Then depending on the 
choice made for 'B', field 'C' will appear on the form.

I want to now find out if the 'choices' for the forms field 'B' can also be 
switched. i.e depending on the choice made in field 'A', the choices that will 
appear for 'B' will change. Is this doable?


Thanks!
Abishek
___
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 run pylint locally?

[Subramanian]

Thanks for the response Dirk. I see very similar output now as shown in the
log when running 'tox -epylint', so I am getting closer. Unfortunately I am
still not able to reproduce the failure shown here
http://logs.openstack.org/17/62217/5/check/gate-cinder-pylint/1272f0a/console.html
.

What seems strange to me is that even when I plain run "pylint -E -i y
cinder" on this branch I still don't see the two lint errors reported in
above link!

- Subbu


On Thu, Feb 13, 2014 at 2:45 PM, Dirk Müller  wrote:

> Hi,
>
> > Here is what I tried:
> > /opt/stack/cinder $ ./tools/lintstack.sh
> >
> > But this does not report any errors even though I am on the same branch.
> > What am I missing?
>
> You might be running against local packages then which have a
> different version / output. The proper way to reproduce the Gate
> errors is by using "tox".
>
> in this case tox -e pylint
>
> Please note that the pylint error is nonvoting, the actual -1 comes
> from the Devstack test run failure.
>
> ___
> 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] [Cinder] How to run pylint locally?

[Subramanian]

I have a quick question on how to run the cinder-gate-pylint locally. I am
trying to reproduce the pylint errors reported by the gate pylint build
here (https://review.openstack.org/#/c/62217/) locally.

Here is what I tried:
/opt/stack/cinder $ ./tools/lintstack.sh

But this does not report any errors even though I am on the same branch.
What am I missing?

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

Re: [openstack-dev] OpenStack-dev Digest, Vol 22, Issue 27

[Abishek Subramanian (absubram)]

Hi Shixiong,

Thanks for the reply and clearing up my question!
The document you've shared - they aren't the only possible combinations
correct?
Each of the two fields can have any one of these four values in any
possible combination yes?

Thanks!

On 2/11/14 7:00 AM, "openstack-dev-requ...@lists.openstack.org"
 wrote:

>Hi, Abishek:
>
>Thank you for taking care of Horizon for IPv6 enhancement. So now we have
>coverage on both CLI and dashboard side. Very exciting!
>
>W.r.t your questions, these two parameters work independently. In other
>words, Horizon should present both options if the interested subnet is
>IPv6. For each parameter, the valid values are:
>   off
>   slacc
>   dhcpv6-stateful
>   dhcpv6-stateless
>
>The CLI command may look like, for example, something below:
>
>neutron subnet-create --ip-version 6 --ipv6_ra_mode off
>--ipv6_address_mode off NETWORK CIDR
>neutron subnet-create --ip-version 6 --ipv6_ra_mode off
>--ipv6_address_mode dhcpv6-stateful NETWORK CIDR
>neutron subnet-create --ip-version 6 --ipv6_ra_mode slaac
>--ipv6_address_mode slaac NETWORK CIDR
>neutron subnet-create --ip-version 6 --ipv6_ra_mode dhcpv6-stateful
>--ipv6_address_mode off NETWORK CIDR
>neutron subnet-create --ip-version 6 --ipv6_ra_mode dhcpv6-stateless
>--ipv6_address_mode dhcpv6-stateless NETWORK CIDR
>
>
>The valid combinations are outlined in the PDF file below.
>
>https://www.dropbox.com/s/9bojvv9vywsz8sd/IPv6%20Two%20Modes%20v3.0.pdf
>
>Please let me know if you have any further questions. Thanks!
>
>Shixiong
>
>


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

[openstack-dev] [Neutron][IPv6] CLI for the new subnet keywords

[Abishek Subramanian (absubram)]

Hi IPv6 experts,

This is regarding the BP -
https://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes

Is it possible to give me a quick example of the
CLI that you envision?
This is so that the Horizon BP can be updated accordingly.

Once the neutron side of things is ready, when creating a subnet,
and the version is IPv6 will now  enable these two options, yes?
Can both options exist or is it

an either/or combination, i.e. either ipv6_ra or ipv6_address?


Thanks!




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

[openstack-dev] [Cinder] Tracking mox to mock unit tests?

[Subramanian]

Is there a bug/bp tracking the overall cinder unit tests move from mox to
mock? Is this targeted to complete in IceHouse?

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

Re: [openstack-dev] [Nova] Security vulnerability contacts

[Sriram Subramanian]

Russell,

(ccing Bryan, Rob)

Thanks for the initiative. We at the OpenStack Security Group
are doing
large part of these tasks now and are looking for more help (particularly
around reviews from people that are intimate to the project internals).
Here are some 
pointerson
how to get involved. You probably are inviting more volunteers for
OSSG,
I am just trying to make it clearer. If not, we need to work to make sure
the efforts are aligned and not duplicated.

Thanks,
-Sriram


On Mon, Nov 18, 2013 at 9:50 AM, Russell Bryant  wrote:

> Greetings,
>
> I'm on a quest to address Nova's project management growing pains and to
> make sure the Nova PTL is never an unnecessary bottleneck.  One area
> that has been identified as needing a small team is handling Nova
> security vulnerability reports.
>
> We have the nova-coresec team on launchpad [1], which is currently all
> of nova-core.  We need to re-work this to be a small subset of nova-core
> that is specifically interested in being the primary contacts for
> security issues.  These people will be responsible for:
>
> 1) Helping determine if a report is legitimate
>
> 2) Pulling in the right expertise as necessary to analyze and/or fix a
> problem
>
> 3) Helping develop fixes for security issues
>
> 4) Helping to review security fixes (they must be reviewed in advance,
> before going to gerrit, because the patches are under embargo)
>
> I'm happy to be on this team, but I would like a few people with broad
> expertise to help out.
>
> For more information on the vulnerability management process, see [2].
>
> Who's in?
>
> [1] https://launchpad.net/~nova-coresec
> [2] https://wiki.openstack.org/wiki/Vulnerability_Management
>
> --
> Russell Bryant
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



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

Re: [openstack-dev] Error while executing 'git review'

[Subramanian]

Looks like a change id conflict with https://review.openstack.org/#/c/52949.
You are letting "git review" auto generate the change id right? For this
case you could try "git commit --amend", remove the change id line if it
matches the change id from this review and then run "git review" again. HTH.

- Subbu


On Tue, Oct 22, 2013 at 6:34 PM, S Sridhar  wrote:

> Hi All,
>
> I worked on bug # 1176683 and
> fixed it. Commit is successful.
>
> sridhar@ubuntu:~/repo/neutron$ git status
> # On branch bug_id_1176683
> nothing to commit (working directory clean)
> sridhar@ubuntu:~/repo/neutron$
>
> But getting following error while posting for review.
>
> sridhar@ubuntu:~/repo/neutron$ git review
> remote: Resolving deltas: 100% (4/4)
> remote: Processing changes: refs: 1, done
> To ssh://saggezz...@review.openstack.org:29418/openstack/neutron.git
>  ! [remote rejected] HEAD -> refs/for/master/bug/1176683 (change 52949
> closed)
> error: failed to push some refs to 'ssh://
> saggezz...@review.openstack.org:29418/openstack/neutron.git'
> sridhar@ubuntu:~/repo/neutron$
>
> Could anyone help in resolving this issue ?
>
> Regards
> Sridhar
>
> ___
> 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] [openstack]ASK: Summit talk on OpenStack on OpenStack/ OpenStack as a Service

[Sriram Subramanian]

Dear Stackers,

I came across a proposed talk related to OpenStack on OpenStack/ OpenStack
as a Service. Couldn't recollect if there were two different talks or the
same. I am interested in learning more - could the speakers ping me offline
please?

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

Re: [openstack-dev] [OSSG] ASK - What is the regular OSSG IRC meetup schedule? #TIA

[Sriram Subramanian]

Thanks Bryan, would like to get involved more. Meet you tomorrow at 10 am
PST/ 1800 UTC.


On Wed, Aug 21, 2013 at 11:07 AM, Bryan D. Payne  wrote:

> Thursdays at 1800 UTC.
> https://wiki.openstack.org/wiki/Meetings/OpenStackSecurity
>
> -bryan
>
>
> On Wed, Aug 21, 2013 at 10:57 AM, Sriram Subramanian <
> sri...@sriramhere.com> wrote:
>
>>
>>
>> --
>> Thanks,
>> -Sriram
>>
>> ___
>> 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
>
>


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

[openstack-dev] [OSSG] ASK - What is the regular OSSG IRC meetup schedule? #TIA

[Sriram Subramanian]

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