I didn't have it. I ran across it this afternoon, but wasn't sure if
it did all of the proper setup or if it was the equivalent of enabling
the provider (which as mentioned wasn't enough when I tried manually).
Thanks for confirming, I'll commit it.
On Thu, Sep 5, 2013 at 10:45 PM, Prasanna Santhanam <t...@apache.org> wrote:
> Yes, that is all that is required. This doesn't enable the internal lb
> provider for you?
>
> On Thu, Sep 05, 2013 at 10:41:02PM -0600, Marcus Sorensen wrote:
>> So this look right to you?
>>
>> diff --git a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> index 45bdfce..8e77809 100644
>> --- a/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> +++ b/tools/devcloud-kvm/devcloud-kvm-advanced.cfg
>> @@ -47,6 +47,10 @@
>> {
>> "broadcastdomainrange": "ZONE",
>> "name": "VpcVirtualRouter"
>> + },
>> + {
>> + "broadcastdomainrange": "ZONE",
>> + "name": "InternalLbVm"
>> }
>> ]
>> },
>>
>> On Thu, Sep 5, 2013 at 10:37 PM, Prasanna Santhanam <t...@apache.org> wrote:
>> > On Thu, Sep 05, 2013 at 05:06:02PM -0600, Marcus Sorensen wrote:
>> >> Thanks. It must be the marvin deployment then that's causing me grief.
>> >> I haven't manually filled out the UI in awhile.
>> >
>> > Marvin handles internallbvm deployment as well. Your providers should
>> > now look like below.Then sync marvin and you should be ready to go.
>> >
>> > "providers": [
>> > {
>> > "broadcastdomainrange": "ZONE",
>> > "name": "VirtualRouter"
>> > },
>> > {
>> > "broadcastdomainrange": "ZONE",
>> > "name": "VpcVirtualRouter"
>> > },
>> > {
>> > "broadcastdomainrange": "ZONE",
>> > "name": "InternalLbVm"
>> > }
>> > ],
>> >
>> > see the setup/dev/advanced.cfg. I keep that updated usually.
>> >
>> > --
>> > Prasanna.,
>> >
>> > ------------------------
>> > Powered by BigRock.com
>> >
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
