1462495 - [MDC2] Request for 4 more WebRTC VM in Public Vlan

Status: RESOLVED FIXED

(Infrastructure & Operations :: Virtualization, task)

Description

[Mark Richards [:freshness]]

Desired hostname
        webrtc13.mdc2.mozilla.com
        webrtc14.mdc2.mozilla.com
        webrtc15.mdc2.mozilla.com
        webrtc16.mdc2.mozilla.com
    Number of cores
        8 CPUs
    Amount of RAM
        8 GB
    Both with full reservations: 18000/8000
        
    Desired OS
        OVA is VidyoWebRTC-4.2.0.1101.002.ova
        OVA from Vidyo, already shared with Virtualization team
    Amount of disk
        Default
    Special requests
        Pretty please? 

AVOPs will configure IP's, just need them powered on. Please add these to the MDC2>Vidyo Prod>WebRTC Prod folder after creation.  This is preparation for the simultaneous deployment of the new datacenter and WebRTC functionality for Mozilla.

Comment 1

[Chris Knowles [:cknowles]]

We'll need to peruse the resources in MDC2 and decide if this will work given where we are in the migration out of SCL3.  

Also, I've been in some conversations with netops where they've mentioned a desire to have the vidyo equipment in the AV vlan and NAT'd through, rather than directly on the internet like they are in SCL3 - so I'm NI'ing Johnb to see if now would be a time where we should start that.  (rather than setup and then having to forklift everything over at once.  Having some capacity already in the AV vlan might be helpful)

Comment 2

[John B [:johnb]]

Is this in an effort to go live or is this more testing? If this is heading towards live, this needs to move into the AV VLAN.

Comment 3

[Chris Knowles [:cknowles]]

So, two things. 

1) The AV VLAN - given comments here and elsewhere, this feels like a go live push, so I'm proposing that we make the VMs in the AV VLAN:
webrtc13.av.mdc2.mozilla.com
webrtc14.av.mdc2.mozilla.com
webrtc15.av.mdc2.mozilla.com
webrtc16.av.mdc2.mozilla.com

2) resources.  Looking at MDC2, we can take these 4.  But, given that we're in migration mode, we need to reserve resources for things to move into the new datacenters from SCL3 - so further resource requests like this will be met with increasing resistance until we're out of SCL3 and more compute resources have landed in the MDC spaces.

Mark, let me know if this works for you.

Comment 4

[Mark Richards [:freshness]]

Thanks Chris and John,

1) Yes, this is in preparation for go live, so placing these in the av vlan sounds great.  I'll open another bug to migrate all of the infra in MDC1/MDC2 over to the av vlan.

2) ACK  I know that these are big asks, but if this is the max point right now that's "okay."  Once these four are added into the media resource pool, it will allow a total of 72 concurrent participants which should be a good starting point.

tl;dr Both proposals sound good

Comment 5

[Chris Knowles [:cknowles]]

Mark, No need to file a new bug, bug 1461114 is already filed for that work to move to av.

I'll start work on getting those 4 created in the AV vlan - worst case I'll have them for you by Monday.

Comment 6

[Chris Knowles [:cknowles]]

Alright, those are all created:

webrtc13.av.mdc2.mozilla.com - IP: 10.50.86.23 - SN: 255.255.255.0 - GW: 10.50.86.1
webrtc14.av.mdc2.mozilla.com - IP: 10.50.86.24 - SN: 255.255.255.0 - GW: 10.50.86.1
webrtc15.av.mdc2.mozilla.com - IP: 10.50.86.25 - SN: 255.255.255.0 - GW: 10.50.86.1
webrtc16.av.mdc2.mozilla.com - IP: 10.50.86.26 - SN: 255.255.255.0 - GW: 10.50.86.1

I haven't turned them on, but you should have access.  

they've been added to SN, and tracking sheets.  DRS has been applied to keep them from running on the same blades in case of any hardware failure.

Let me know if you need anything else.

Comment 7

[Mark Richards [:freshness]]

This is great, thank you! All 4 machines have been configured.
I've updated bug 1461114 with the firewall rules for the av vlan migration.