ReleaseOperations/Projects/AutomaticProvisioning/Meetings/2014-01-29: Difference between revisions
< ReleaseOperations | Projects | AutomaticProvisioning | Meetings
Jump to navigation
Jump to search
(Created page with "== Followup on Action Items == * look at provisioning tools / cloud stacks -- jake/dustin * continue with JAMF --jake * moving things out of GPO and into puppet or MDT (diffic...") |
|||
| Line 9: | Line 9: | ||
* Can machines keep their existing hostnames through re-images (and fqdn/IP when not changing VLANs)? If so, how should we name them? $hardwaretype$number? $assetag? | * Can machines keep their existing hostnames through re-images (and fqdn/IP when not changing VLANs)? If so, how should we name them? $hardwaretype$number? $assetag? | ||
** Or, asking another way: how much identity do we want to assign to hardware, and how much to instances? | ** Or, asking another way: how much identity do we want to assign to hardware, and how much to instances? | ||
* How should we handle monitoring for these hosts? | |||
Revision as of 17:18, 29 January 2014
Followup on Action Items
- look at provisioning tools / cloud stacks -- jake/dustin
- continue with JAMF --jake
- moving things out of GPO and into puppet or MDT (difficult with Win8 - registration of default browsers is domain-only) --Q
- continue with puppet on windows, with different focus (puppet doesn't run on prod instances) --mark
- plan for VLAN changes, but no implementation this quarter --adam
Round Table
- Can machines keep their existing hostnames through re-images (and fqdn/IP when not changing VLANs)? If so, how should we name them? $hardwaretype$number? $assetag?
- Or, asking another way: how much identity do we want to assign to hardware, and how much to instances?
- How should we handle monitoring for these hosts?