I’ve been getting some great response to my previous post, and I wanted to make a few things very clear.

Clarifications

What I’m not doing -

  1. I’m not advocating or dismissing any particular configuration management tool.
  2. I’m not discounting the tough work done by companies and community projects that have created abstractions on managing disparate systems.

What I am attempting to do -

  1. Highlight the challenges of cross-platform management and application management.
  2. Show one of the efforts in providing a standards based management abstraction.
  3. Offer my thoughts on why I see value in that direction and what challenges I see.

Managing the Operating System vs. Managing Applications

There is definitely some confusion around using CIM to manage the OS vs managing applications.

  1. CIM Classes can be used to model applications as well as OS resources.
  2. Most of the “applications” that are packaged as roles and features in Windows Server expose a CIM management API.
  3. WMI is an implementation of the CIM standard and starting with Server 2012 and the Windows Management Framework V3, CIM is exposed via WSMAN.

Hyper-V, File Shares, Clustering, IIS, and others all offer CIM based management models.  Other applications can expose a CIM management model as well.  As long as the host CIM server (WMI on Windows and OMI or OpenPegasus or ???? on Linux based Operating Systems) is operational, applications can also offer their configuration and status via that channel by creating a provider.  To do this on Windows, there is some documentation to get you started:

To do this with OMI, you can find some documentation and source at https://collaboration.opengroup.org/omi/documents.php.

The Current State – Reprise

But, but, tool {fill in your favorite tooling here} already does THAT!!!

There are a number of tools that valiantly strive to provide cross-platform management.  I mentioned several of them in my last post, but there are a number of others.

Yep, it does.  Until…

things change.  The challenge these tools have is that they have had to implement their abstractions against very different implementations.  The problem there is that these things are not stagnant.  The management APIs can change over time and since there is not a standard description of the API or underlying configuration.

If CIM were the standard API exposing the configuration, the underlying implementation details can change, but configuration management and monitoring tooling don’t have to care about that.  The tool vendors and community projects can focus on other value adds for their particular tooling, rather than being forced to continually update the basics.

The Next Steps

We are still in the early stages of the push for CIM and WSMAN.  We’ll have to see how adoption picks up.  The continuing work around OMI holds promise, but it needs a deployment or integration story for various Linux distros and more public providers for managing components of the Linux OS and attendant applications.

There have been some interesting announcements at TechEd in relation to Windows Server 2012 R2 (watch this video and pay attention around 49 minutes in).  I’m going to talk more about this feature and it’s implications and my plans with it in the very near future.

 

«
»
  • Yang Lin

    Tigecycline in vitro antibacterial activity against clinical strains

    Abstract: Objective evaluation of tigecycline ( tetracycline antibiotic ) in vitro antibacterial activity against clinical strains . Methods broth dilution method for tigecycline and other 14 kinds of drugs for nearly two years in the hospital clinical specimens of 400 bacteria were isolated MIC determined by WHONET5.4 statistical software . The results showed that MIC determination : tigecycline against methicillin-resistant Staphylococcus aureus (MRSA) and Enterococcus showed good antibacterial activity in vitro test has three vancomycin-resistant enterococci (VRE), on behalf of tigecycline and linezolid -sensitive display ;Daptomycin, against Gram- negative bacteria Escherichia coli and ESBL-producing Klebsiella spp MIC ∞ are 1trg · mL ~, behind or below meropenem ; present study for tigecycline against Acinetobacter baumannii

    The MIC. (2trg · mL a ) a minimum in all tests of antimicrobial drugs ; against Pseudomonas aeruginosa MIC ∞ value of 16p. g · mL ~.Tigecycline hydrochloride, Conclusion tigecycline against clinical pathogens have good broad-spectrum antimicrobial activity against Pseudomonas aeruginosa Yin poor antibacterial activity.

    Tigecycline (tigecycline) is a derivative of minocycline , is the first clinical application of new glycyl doxycycline antibiotics . Intravenous drug formulations, in 2005 the U.S. Food and Drug Administration (FDA) approval : tigecycline for the treatment of patients aged 18 and older infections caused by susceptible strains , indications include : complicated intra-abdominal infections ( such as complicated appendicitis ,Tigecycline mesylate, burns infections, intra-abdominal abscesses, deep soft tissue infections and infected ulcers ) and complicated skin and soft tissue infections. The drug can overcome the limitations of many two main resistance mechanisms of antimicrobial drug use : efflux pumps and ribosomal protection. 1 shows a lot of old literature : the drug can be used to treat multi-drug resistant , such as MRSA, VRE, producing extended-spectrum 13 -lactamase bacterial infections caused by Enterobacteriaceae .Ofloxacin To understand the in vitro antibacterial activity of the drug , the trial of the 2009 and 2010 clinical isolates from the Ministry of Health, Beijing Hospital, 400 clinical MIC common bacteria were measured to evaluate the in vitro antibacterial activity of the drug .

    Medchemexpress Can provide the above product,its website:http://www.medchemexpress.com