Bluebear Kodiak 0.0.3 has been released

If I can find the time I will test it today and add some screenshots to this post. You can get it here. Here are the release notes:

This version of Kodiak represents a significant change in our server-communication architecture.

  1. We’ve added a schema-compliant request/argument builder engine that populates requests based on known information. This makes building requests much easier.
  2. A lua scripting engine. Each server connection gets its own independent Lua script.
  3. Independent object pools.
  4. Improved mapping response and control.
  5. Map connection node & link display control.
  6. We’ve created a “plugin api” where a user may build a plugin to communicate with any kind
    of data service. We’ll be publishing information on this on our wiki.
  7. We’ve added a number of “boilerplate” features that will become more apparent in the next
    few releases as we push Kodiak towards our goal of creating an “IT IDE”.
  8. Access for users to create their own scripts. Kodiak’s UI/inspector controls are driven by a “global schema” that allows a user to create their own customized scripts for management. Please visit the bluebear wiki for further information regarding customizing the script engine. As yet, we don’t have a full UI for managing user scripts, but we will shortly.
  9. The remote event log has been removed for this release.
  10. For Windows users who experience the dreaded “SSL certificate bug”, we’ve added a preferences option to bypass the windows SSL stack. This option is accessible from the Preferences menu.
  11. Password vault & credentials storage. Kodiak now has the ability to save username/password pairs in an encrypted password vault, locked with a master password.
  12. Server object creation is disabled while we migrate the control components into the VMWare plugin, we will re-enable these in a couple of days.



You can skip to the end and leave a response. Pinging is currently not allowed.

8 Responses to “Bluebear Kodiak 0.0.3 has been released”

  1. superted says:

    Hello,

    Just installed 0.0.3 and it wont seem to connect, i had the dredded windows issue (running XP) and ive switched to the seperate SSL setting to allow it to work.

    I click login but it just sits there, can press it as many times as i want with no effect?

  2. I tried to connect it to:
    vSphere ESX – Failed
    vSphere vCenter – Failed
    ESX 3.5 – Success

    Haven’t tested vCenter 2.5 U4 though…

  3. superted says:

    Interesting, im on Update 4. Be good to see if anyone else is having this issue with vc update 4?

    Ed

  4. Alan Civita says:

    i tried to connect to vCenter U4, but failed…

  5. Dean says:

    I tried with vCenter 2.5 U3 and it fails with the following in the debug log:

    [10:09:02 GMT+0800]wsfm149vic::Error in task RetrieveInventory:1

    [10:09:02 GMT+0800]wsfm149vic::luaDoString:185: builtin://lua_alchemy/as3/sugar.lua:129: failed to create object of type: ‘com.bluebear.plugins.vmware.model.vo::DatacenterPropertyFilter’
    stack traceback:
    [C]: in function ‘assert’
    luaDoString:185: in main chunk

  6. Dimitris says:

    Looking for an invite. Do you happen to have any left? Thanks…

  7. bodie says:

    Also, looking to test this product out looks great and want to see what all the talk is about.

  8. Ed Marshall says:

    Hello,

    I realise this is an old post however im interested in using something like bluebear to sit on some of our large plasma screens we have for monitoring our systems.

    Can anyone tell me if bluebear is still in development, no new versions since may?

    That or does anyone else know of a good way to get a simple view of the hosts and there status (CPU/ALARMS etc) that you can check with a simple glance. Doesn’t hurt if it looks good to impress the management types!

    Thanks

    Ed

Leave a Reply

Subscribe to RSS Feed Follow me on Twitter!