by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 29 21:07
    simaishi unlabeled #584
  • May 29 21:07
    simaishi labeled #584
  • May 29 21:07
    simaishi commented #584
  • May 29 21:07

    simaishi on jansa

    Merge pull request #584 from ag… (compare)

  • May 29 17:00
    chessbyte labeled #584
  • May 29 17:00
    chessbyte unlabeled #584
  • May 29 16:27

    chessbyte on master

    Add supports terminate feature Merge pull request #584 from ag… (compare)

  • May 29 16:27
    chessbyte closed #584
  • May 29 16:07
    agrare assigned #584
  • May 29 12:41
    miq-bot commented #584
  • May 29 12:41
    miq-bot commented #584
  • May 29 12:36
    agrare labeled #584
  • May 29 12:36
    agrare unlabeled #584
  • May 29 12:36
    agrare edited #584
  • May 29 12:36
    agrare synchronize #584
  • May 28 20:35
    miq-bot labeled #584
  • May 28 20:32
    agrare edited #584
  • May 28 20:26
    miq-bot commented #584
  • May 28 20:20
    agrare labeled #584
  • May 28 20:20
    agrare review_requested #584
Fabien Dupont
@fdupont-redhat
Then, functional tests with different version of vCenter is the only way to find out if it would break something, right ?
Adam Grare
@agrare
6.0 is the oldest we have
Also maybe the oldest we support, if this was only needed on older versions maybe we can simplify it
Andrey Menezes
@AndreyMenezes
.0
Fabien Dupont
@fdupont-redhat
@agrare I'll look into it. This will require changes in other repos.
samson7point1
@samson7point1
Are NSX networks not supported in CFME 5.10?
CloudForms doesn't seem to be able to see them at all.
Adam Grare
@agrare
hey @samson7point1 that's not something which is currently supported
samson7point1
@samson7point1
@agrare Is this on the roadmap at all, maybe as a network provider in the future?
Adam Grare
@agrare
@samson7point1 I'd love to support it as a network provider, just time and resources
samson7point1
@samson7point1
@agrare I hear you there
samson7point1
@samson7point1
@agrare I'm still trying to skin this cat and I noticed that the pyvmomi has some support for "opaque networks" - in this case the customer is using NSX-v which is completely external to vCenter. Is it possible for MIQ to support opaque networks (outside the context of NSX specifically).
?
Adam Grare
@agrare
hey we actually had a community user push a PR trying to collect these opaque networks
I think it stalled when trying to link them up to hosts
let me check
samson7point1
@samson7point1
awesome, thanks!
really need an environment to test it in
samson7point1
@samson7point1
Well... I'm not sure how much longer I'll have access to it, but I'm at a customer site with this circumstance right now.
Adam Grare
@agrare
Okay I'll DM you in a little bit, lets see if we can resurect that PR and get some specs recorded to test against
samson7point1
@samson7point1
That would be killer, thanks
To be clear this is actually CloudForms 4.6
samson7point1
@samson7point1
@agrare I don't know if this is related or something else entirely, but when we tested assigning opaque networks to VMs during provisioning, we didn't catch that the NICs were coming up "Disconnected". They were attached to the correct network but not activated. I'm working with the consultants onsite to try to isolate the cause, but I suspect it's at least possible it has something to do with those opaque networks.
Adam Grare
@agrare
can you be more specific about coming up disconnected
samson7point1
@samson7point1
in vCenter the NIC will appear on the VM, but will have a status of "Disconnected".
Adam Grare
@agrare
like miq reports they're disconnected, or on vsphere they're disconnected
can you manually connect them?
samson7point1
@samson7point1
It will have the correct network assigned and everything
I'm trying to get that question answered right now.
Adam Grare
@agrare
it could be that the "start_disconnected" attribute of our guest_devices was set to false for some reason
or it could be that Opaque backing type that I was talking about before
samson7point1
@samson7point1
That's why I mentioned it
I don't have direct access any more, so I'm working vicariously through the consultants onsite.
Okay, it sounds like the customer has decided to call it a day so I'm no going to be able to get anything more from them until Monday.
I'm going to have them try deploying the same template somewhere with a DVS network to see if the opaque networks thing is the common denominator
Adam Grare
@agrare
:+1:
samson7point1
@samson7point1
@agrare So it's monday and the consulants are back onsite. I can confirm that the NICS provisioned in a disconnected state could be connected manually in vCenter.
We're continuing fault isolation.
Adam Grare
@agrare
okay thanks
samson7point1
@samson7point1
Spoke too soon. The customer told us they were able to manually connect but now they're walking that back.
samson7point1
@samson7point1
So it "appeared" to work but eventually failed with "Failed to connect virtual device 'ethernet0'." on the vCenter side.
Adam Grare
@agrare
If they weren't able to fix it without changing the nic then it likely is the backing type issue
samson7point1
@samson7point1
@agrare Okay, this is a doozy, but I think it makes sense. It turns out that when we provision a VM to one of these networks by name, vCenter is creating a new standard network with an identical name and assigning it to the VM.
Adam Grare
@agrare
oh wow
samson7point1
@samson7point1
It just appeared to work.
Adam Grare
@agrare
yeah so we definitely need to change the nic backing
samson7point1
@samson7point1
The funny thing is that if we don't get the name right it doesn't actually work.
Adam Grare
@agrare
that's going to take longer because the type doesn't exist in the broker sdk definition
samson7point1
@samson7point1
It's almost like we stumbled on some kind of bug in the API