+1 for the meeting time.
On Dec 10, 2013, at 10:16 AM, Nachi Ueno wrote:
> +1 ! I'll join.
> I'm also working on investigating how to use openstack gating system.
> (This document is still draft version)
> https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPmiATP1F-0BVbuk1eefQalL5Q0/edit#s
Hi JC,
We agree with your proposed model of a VPC resource object. Proposal you are
making makes sense to us and we would like to collaborate further on this.
After reading your blueprint two things come to mind.
1. VPC vision for Openstack? (Your blueprint is proposing this vision)
2. Providin
JC,
BP has been updated with the correct links. I have removed the abandoned
review #3.
Please review #1 and #2.
1. https://review.openstack.org/#/c/40071/
This is the active review.
There is one comment by Sean regarding
adding a knob when Neutron is not used.
That will be addressed
, "jc Martin" wrote:
>Thanks,
>
>Do you have the links for the discussions ?
>
>Thanks,
>
>JC
>
>Sent from my iPhone
>
>> On Feb 17, 2014, at 11:29 AM, Rudra Rugge wrote:
>>
>> JC,
>>
>> BP has been updated with the correct lin
Please see inline:
On Feb 18, 2014, at 2:57 PM, Martin, JC wrote:
> Maybe I should explain this one a bit.
>
> Shared network: If a user has defined a shared network, and they used your
> API to create a VPC, the instances within the VPC will automatically get an
> interface on the shared net
gateway, VPN, NAT etc) was
not added to the blueprint as that was dependent on VPNaas, FWaaS, NATaas.
Comments inline:
On Feb 19, 2014, at 9:05 AM, Martin, JC
mailto:jch.mar...@gmail.com>> wrote:
Comments in line.
JC
On Feb 18, 2014, at 5:21 PM, Rudra Rugge
mailto:rru...@juniper.net&g
Hi Kyle,
I also agree with Mandeep's suggestion of putting a time frame on the
lingering "-2" if the addressed concerns have been taken care of. In my
experience also a sticky -2 detracts other reviewers from reviewing an
updated patch.
Either a time-frame or a possible override by PTL (move to -
On Wed, Aug 6, 2014 at 6:40 PM, Aaron Rosen wrote:
>
> On Wed, Aug 6, 2014 at 5:27 PM, Kevin Benton wrote:
>
>> Web tier can communicate with anything except for the DB.
>> App tier can only communicate with Web and DB.
>> DB can communicate with App.
>>
>> These high-level constraints can then
Hi All,
A blueprint has been registered to add IPAM and Policy
extensions to Neutron. Please review the blueprint and
the attached specification.
https://blueprints.launchpad.net/neutron/+spec/juniper-contrail-ipam-policy-extensions-for-neutron
All comments are welcome.
Thanks,
Rudra
__
Hi All,
The link in the email was incorrect. Please follow the following link:
https://blueprints.launchpad.net/neutron/+spec/ipam-policy-extensions-for-neutron
Thanks,
Rudra
On Oct 3, 2013, at 11:38 AM, Rudra Rugge
mailto:rru...@juniper.net>> wrote:
Hi All,
A blueprint has been regi
s is one example
>https://wiki.openstack.org/wiki/Quantum/VPNaaS )
>
>Especially, I'm interested in src-addresses, dst-addresses, action-list
>properties.
>Also, how can we express any port in your API?
[Rudra] Will add the details of the resources and APIs after separating
the blueprin
Hi Nachi,
Inline response
On 10/4/13 12:54 PM, "Nachi Ueno" wrote:
>Hi Rudra
>
>inline responded
>
>2013/10/4 Rudra Rugge :
>> Hi Nachi,
>>
>> Thanks for reviewing the BP. Please see inline:
>>
>> On 10/4/13 11:30 AM, "Nachi Ueno&
Hi Nachi,
I have split the spec for policy and VPN wiki served as a good reference point.
Please review and provide comments:
https://wiki.openstack.org/wiki/Blueprint-policy-extensions-for-neutron
Thanks,
Rudra
On Oct 4, 2013, at 4:56 PM, Nachi Ueno wrote:
> 2013/10/4 Rudra Rugge :
&g
rvice framework spec/discussion.
Thanks.
> it is also helpful if we could have full list of examples.
[Rudra] Will add more examples.
Cheers,
Rudra
>
> Best
> Nachi
>
>
>
>
>
> 2013/10/7 Rudra Rugge :
>> Hi Nachi,
>>
>> I have split the spe
-neutron
IPAM
Blueprint:
https://blueprints.launchpad.net/neutron/+spec/ipam-extensions-for-neutron
Spec: https://wiki.openstack.org/wiki/Blueprint-ipam-extensions-for-neutron
Thanks,
Rudra
On Oct 3, 2013, at 11:38 AM, Rudra Rugge
mailto:rru...@juniper.net>> wrote:
Hi All,
A bluepri
Hi Greg,
Is there any discussion so far on the scaling of VMs as in launching multiple
VMs
for the same service. It would also have impact on the VIF scheme.
How can we plug these services into different networks - is that still being
worked
on?
Thanks,
Rudra
On Oct 8, 2013, at 2:48 PM, "Regn
Hi All,
Is the extra route extension always tied to the router extension or
can it live in a separate route-table container. If extra-route routes
are available in separate container then sharing of such
containers across networks is possible.
Another reason to remove the dependency would be to
Updated the subject [neutron]
Hi All,
Is the extra route extension always tied to the router extension or
can it live in a separate route-table container. If extra-route routes
are available in separate container then sharing of such
containers across networks is possible.
Another reason to re
/Blueprint-ipam-extensions-for-neutron
Regards,
Rudra
On Oct 9, 2013, at 11:43 AM, Salvatore Orlando
mailto:sorla...@nicira.com>> wrote:
Hi Rudra,
Some comments inline.
Regards,
Salvatore
Il 09/ott/2013 19:27 "Rudra Rugge"
mailto:rru...@juniper.net>> ha scritto:
>
>
where you would need to plug
the VM into different networks?
Thanks,
~Sumit.
On Tue, Oct 8, 2013 at 3:48 PM, Rudra Rugge
mailto:rru...@juniper.net>> wrote:
Hi Greg,
Is there any discussion so far on the scaling of VMs as in launching multiple
VMs
for the same service. It would also ha
Hi Sumit,
Please see inline.
On Oct 9, 2013, at 2:03 PM, Sumit Naiksatam
mailto:sumitnaiksa...@gmail.com>>
wrote:
Hi Harshad,
I agree with you that the "service instance" terminology might be a little
confusing here. The way it was phrased in the original email, I believe it was
meant to s
Here are the blueprints (mentioned by Harshad below) to add complete AWS
VPC compatibility in Openstack. AWS EC2 compatibility already exists in
Openstack.
https://blueprints.launchpad.net/neutron/+spec/ipam-extensions-for-neutron
https://blueprints.launchpad.net/neutron/+spec/policy-extensions-f
Hi All,
A blueprint has been registered to add Amazon VPC API support.
Currently Amazon EC2 API support already exists in Openstack.
Please review the blueprint and the attached specification. The
specification covers all the VPC APIs and describes how it maps
to the Openstack constructs.
Bluepri
In addition there is one more change:
New euca2ools commands have been added to support all the
VPC related CLI.
Thanks,
Rudra
On Aug 13, 2013, at 10:38 PM, Rudra Rugge
mailto:rru...@juniper.net>> wrote:
Hi All,
A blueprint has been registered to add Amazon VPC API support.
Currently
nting the VPC API in
Neutron directly, with the exception of those calls, like RunInstances which
pertain to the compute node.
Regards,
Salvatore
On 14 August 2013 20:27, Rudra Rugge
mailto:rru...@juniper.net>> wrote:
In addition there is one more change:
New euca2ools commands have bee
25 matches
Mail list logo
