Hi,
There was some discussion a while back around the VPC implementation in
Openstack. There is a proposal to implement the AWS VPC features in Nova EC2
APIs, but this makes sense for the EC2 compatible API only and may not be
appropriate for an Openstack specify one.
I would like to know w
Comments in line.
JC
On Feb 18, 2014, at 5:21 PM, Rudra Rugge wrote:
> 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 use
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 network. I don't think that this is the expected
behavior
FIP in scope of VPC: I
Vish,
See comments below.
JC
On Feb 18, 2014, at 12:19 PM, Vishvananda Ishaya wrote:
>
> On Feb 18, 2014, at 11:31 AM, Martin, JC wrote:
>
>>
>> I see a lot of good things happening on the hierarchical multi tenancy
>> proposal that Vish made a while back.
>&
Joe,
See my comments in line.
On Feb 18, 2014, at 12:26 PM, Joe Gordon wrote:
> On Tue, Feb 18, 2014 at 10:03 AM, Martin, JC wrote:
>> There was a lot of emails on that thread, but I am not seeing the discussion
>> converging. I would like to reiterate my concerns:
>>
I see a lot of good things happening on the hierarchical multi tenancy proposal
that Vish made a while back.
However, the focus so far is on roles and quota but could not find any
discussion related to resource ownership.
Is the plan to allow the creation of resources within any level of the
We have started a discussion on the proper model to implement a Virtual Private
Cloud (VPC) feature in openstack.
I feel that there was not a lot of discussion on this topic in the past, and
this may be because of the ML tags used.
I am pointing out this discussion to this group with the Neutron
a knob when Neutron is not used.
>>> That will be addressed with the next path.
>>> 2. https://review.openstack.org/#/c/53171
>>> This is the active review for tempest
>>> test cases as requested by Joe Gordon.
>>> Currently abandoned until #1 goes thr
Harshad,
I tried to find some discussion around this blueprint.
Could you provide us with some notes or threads ?
Also, about the code review you mention. which one are you talking about :
https://review.openstack.org/#/c/40071/
https://review.openstack.org/#/c/49470/
https://review.openstack.or
n.
>
>
> Regards
> -Harshad
>
>
>> On Feb 14, 2014, at 10:07 PM, "Martin, JC" wrote:
>>
>> Harshad,
>>
>> I'm not sure to understand what you mean by :
>>> However many of these concepts are not exposed to a AWS custome
ork incrementally towards your definition of VPC we can
> maintain API compatibility to AWS API that we are proposing. As we are
> subset of your proposal and don't expose all features within VPC.
>
> Regards
> -Harshad
>
>
>> On Feb 14, 2014, at 6:22 PM, "Martin, JC&
eneric. One to way is to implement our current proposal to have one VPC
> to one project mapping. As your blueprint matures we will
> move VPC to multiple project mapping.
>
> We feel that instead of throwing away all the work done we can take an
> incremental approach.
>
On Feb 14, 2014, at 11:42 AM, Joe Gordon wrote:
> On Fri, Feb 14, 2014 at 12:09 PM, Martin, JC wrote:
>>
>> There is a Blueprint targeted for Icehouse-3 that is aiming to implement the
>> AWS VPC api. I don't think that this blueprint is providing the necessar
Hi JC,
>
> I have proposed BP to address VPC using domain hierarchy and hierarchical
> administrative boundary.
>
> https://blueprints.launchpad.net/keystone/+spec/hierarchical-administrative-boundary
>
>
> Thanks,
> Arvind
> -Original Message-
> From: Marti
There is a Blueprint targeted for Icehouse-3 that is aiming to implement the
AWS VPC api. I don't think that this blueprint is providing the necessary
constructs to really implement a VPC, and it is not taking into account the
domains, or proposed multi tenant hierarchy. In addition, I could no
Ravi,
It seems that the following Blueprint
https://wiki.openstack.org/wiki/Blueprint-aws-vpc-support
has been approved.
However, I cannot find a discussion with regard to the merit of using project
vs. domain, or other mechanism for the implementation.
I have an issue with this approach as
16 matches
Mail list logo
