tracking bug for temp blade.
april, i have this temporary blade set up for you. let me know which vlan i should tag. https://inventory.mozilla.org/en-US/systems/show/9959/
Assignee: server-ops-dcops → vle
colo-trip: --- → scl3
QA Contact: cshields
Woah, that was awesome. We can probably put it in the Observatory VLAN, although, that said, it needs no outbound or inbound connectivity aside from ssh in from the VPN. So if there is a better VLAN for that (like, I think the community VLAN is very strict?) then maybe that's the better place. Thank you so much!
i'm not sure what the observatory VLAN is, is it the VLAN observium is on?
It actually might not exist yet. So in that case, just pick a safe VLAN where it can't damage anything in the very unlikely chance that it gets owned. Thanks!
>just pick a safe VLAN where it can't damage anything in the very unlikely chance that it gets owned. april, after speaking with netops, if you want a VLAN where only you can get in and nothing gets out, we should open a bug with netops to create a VLAN with these policies. otherwise we should use the DMZ VLAN but we can't promise it wont damage/expose anything that's already existing in the VLAN.
That's probably fine. It won't be running anything, and I'll make sure it keeps up to date on it's OS upgrades. :)
blade has been tagged with VLAN 74 (DMZ). :april, please open a bug with MOC to install the o/s and any packages you want on the blade (and any monitoring if necessary). switch1.r302-1.ops.scl3.mozilla.net#show int status | i 15577 Gi3/0/1 asset-15577 connected 74 a-full a-1000 1000BaseX Gi4/0/1 asset-15577 connected 74 a-full a-1000 1000BaseX
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.