Skip to main content

2012 r2 series: open source

i keep catching myself getting far wordier than intended in these “summaries.” i’m going to work on that! catching up though. this makes 4 of 9 in this series. remember the days when microsoft was all about NOT developing for competing platforms to edge them out of the market? well, this post titled enabling open source software is all about the loving embrace of open source.

 

open source with windows

common engineering criteria (cec) drives consistency across products by requiring engineering compliance on a variety of factors with goals such as integration, manageability, security, reliability, etc. this same concept extends to all things cloud – private, hybrid, or public.

so what’s all this cec stuff do for open source, you say? well, it means having the same goal. single pane of glass administration, things that work in one environment should translate pretty easily to another, etc. here’s things microsoft has been up to:

  • linux community. microsoft has been pretty involved lately. in fact, they’re even checking in their stuff into the main kernel source code base. i guess “lately” isn’t exactly fair. they started doing work with this kind of stuff back with opsmgr.
  • drivers. ms has created what is called linux integration services (lis). basically, it’s a set of drivers for virtual devices. it contains stuff that allows such things as network and disk operating at near bare hardware performance and support for time sync, shutdown, heartbeat, live backups, and live migrations.
  • r2 updates. supports dynamic memory allocation based on guest need, 2d video drivers, vmbus updates to spread interrupts across multiple virtual cpus, and kexec to support the ability to grab crash dumps.

data center abstraction layer (dal) is a common management abstraction for everything in the datacenter. it’s os agnostic, uses existing dmtf standards-based management. open management infrastructure (omi) is basically the implementation for linux. what started off as a movement in opsmgr has grown to configmgr, vmm, and dpm.

  • opsmgr. nothing new here really. if you are an administrator of opsmgr, then you’re probably already aware of opsmgr’s ability to manage more platforms than just windows.
  • configmgr. i knew this work had extended to managing platforms in configmgr but only recently learned that anti-virus protection is also available.
  • vmm. personalize linux during deployment. deploy from templates (think of sysprep with linux), use a mix of linux and windows in service templates.
  • dpm. live backups of linux guests. file system consistent snapshots (buffers are flushed, capable by linux integration services).
  • powershell cmdlets. these cmdlets actually let you manage any cim based system.

CommandType     Name                                               ModuleName
-----------     ----                                               ----------
Cmdlet          Get-CimAssociatedInstance                          cimcmdlets
Cmdlet          Get-CimClass                                       cimcmdlets
Cmdlet          Get-CimInstance                                    cimcmdlets
Cmdlet          Get-CimSession                                     cimcmdlets
Cmdlet          Invoke-CimMethod                                   cimcmdlets
Cmdlet          New-CimInstance                                    cimcmdlets
Cmdlet          New-CimSession                                     cimcmdlets
Cmdlet          New-CimSessionOption                               cimcmdlets
Cmdlet          Register-CimIndicationEvent                        cimcmdlets
Cmdlet          Remove-CimInstance                                 cimcmdlets
Cmdlet          Remove-CimSession                                  cimcmdlets
Cmdlet          Set-CimInstance                                    cimcmdlets

 

open source on windows

  • common open source application publishing platform (coapp). essentially a package management system like the advanced packaging tool (apt) on linux. coapp packages can be included in visual studio projects.
  • community collaboration. check out the azure gallery. it contains open source apps. also, recently, php was released on the same day for windows which included some significant performance improvements. the real story though is that a windows-version of php was released on the same day other os versions were.
  • oracle. on hyper-v? yup. not just database… but java and weblogic, too.
  • azul systems. jdk will be made available allowing customers to deploy java apps on windows azure using open source java – on both windows and linux.

Comments

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m