Thanks Marcus,
this helps, I can now enable it in the interface after configuring it
as enabled. Somehow I still have to enable the InternalLbVm provider
in the physical network after configuring it as enabled and can't find
a api call to do this.
On Thu, Oct 17, 2013 at 4:21 PM, Marcus Sorensen <shadow...@gmail.com> wrote:
> Yes, it should supposedly never happen under normal circumstances. The
> issue I had was because I was using a Marvin zone config that needed
> to be updated for the new feature. Added:
>
> {
>
> "broadcastdomainrange": "ZONE",
>
> "name": "InternalLbVm"
>
> }
>
> This should be configured on zone setup as well. To fix it manually, I did:
>
> # list internalloadbalancerelements
>
> # configure internalloadbalancerelement enabled=true id=<the uuid>
>
> On Thu, Oct 17, 2013 at 8:03 AM, Daan Hoogland <daan.hoogl...@gmail.com>
> wrote:
>> Marcus.
>>
>> I ran into this on today's master. Did you follow up on this in 4.2?
>> Or do you have a ticket or wiki page for it?
>>
>> tahnks
>> Daan
>>
>> On Thu, Aug 29, 2013 at 1:57 AM, Marcus Sorensen <shadow...@gmail.com> wrote:
>>> 2. can't figure out how to deploy VPC. In 4.2 it tells me to jump
>>> through a few extra hoops regarding setting up internal loadbalancer
>>> service first, "Provider InternalLbVm should be enabled in at least
>>> one physical network of the zone specified", so I look at my physical
>>> network -> network service providers and see "Internal LB VM" is
>>> disabled, so I try to enable it and get "Provider is not ready, cannot
>>> Enable the provider, please configure the provider first". I'm stuck,
>>> I don't see anything in the UI that would provide a configuration
>>> dialog for the internal lb provider, nor do I see anything in the
>>> global options. It makes me wonder how upgrades will fare if VPCs are
>>> being used.
