I am working with puppet and foreman as puppet UI. Trying to sync NTP module with windows agent. It does not work. But it works with Linux centos7 and ubuntu agent.
Does anyone guide me, please?
The puppetlabs/ntp module's page on the Forge does not list any version of Windows among the supported operating systems. The Puppet PE supported modules page also appears to indicate that puppetlabs/ntp does not support Windows. As far as I can tell, if you want to use Puppet to manage Windows time synchronization configuration then you need to use a different module or roll your own.
And rolling your own might be your best alternative. I find only one likely module on the forge, but it is quite old, does not claim to support recent versions of Puppet, and has a low quality score. It might nevertheless serve your purpose just fine, but if not, then I'm inclined to guess that you won't get much help from the developer.
You could try https://forge.puppet.com/modules/tse/winntp that is the module used in the labs in the official Puppet training courses.
Related
I've installed Caffe on my Windows computer but from what I can tell online most projects that use Caffe to do object detection are using some other forks of Caffe like NvCaffe or the SSD fork. None of these forks are available for Windows.
Does this mean it's not possible to do object detection on the Windows fork or is it just that people prefer not to. Sorry if this is a dumb question but I find the Caffe documentation somewhat lacking when it comes to explaining what features require what fork. I'm using the python interface if that makes any difference.
Thanks for any clarifications!
It is possible to run Caffe-SSD on Windows, but some effort is needed. You need to merge the changes from the Windows branch into the Caffe-SSD. There are some existing solutions for that (https://github.com/runhang/caffe-ssd-windows, https://github.com/gustavkkk/caffe-ssd-win, google for more), but I did not use those, unfortunately. Colleague of mine did it by himself, so it is definitely possible. As soon as you get it compiled and running, you will have a Python interface as well.
I plan to make a proposal for a proof of concept(POC) project employing mesos/sphere targeting the OS IBM AIX. At least for the mesos/sphere slaves.
Short remark: with the term mesos/sphere i subsume both projects, mesos and mesossphere, to be the "framework" projects of that POC.
I have read about the isolation feature and that it uses cgroups and hence a LXC environment. Referencing http://en.wikipedia.org/wiki/LXC, IBM AIX does use an alternative approach and does NOT implement cgroups.
So i can not expect that all features of mesos/sphere will work on IBM AIX. But on the other side i can not pre-evalute from docs and research under which if-s which features might work or are to be configured respectively.
So, targeting IBM AIX as the OS prospectively running mesos/sphere, is/can mesos/sphere ...
designed to work ?
be expected respective to which features not to work ?
be pin pointed to configuration documentation/help that is not expected to work ?
expected to be supported by the community?
under anyone's productive usage?
thanks for trying mesos under AIX!
There is no official support for AIX,so unfortunately also no documentation what might be potential problems.
Did you try building mesos (make && make check) on AIX? That should give a good indicator for potential problems.
To your LXC questions: Mesos supports a number of different ways to isolate processes: See for example mesos-containerizer,docker containerizer or external containerizer.
So even without cgroups Mesos will still work, it will just not be able to isolate tasks with cgroups.
For example I can at least test Mesos fine on my Mac Book (which does not offer cgroups).
Hope this helped,
Joerg
Is Cygwin considered robust and safe enough to be used on enterprise applications?
Do you know Enterprise applications that were developed or using Cygwin?
If you've been using cygwin - how often did you need support? Is there a fine-support for Cygwin? how well was the support you were given?
Thank you very much.
Why on earth would you even consider cygwin towards any sort of enterprise application? Even their site directly gives multiple signs it shouldn't be used for anything critical. You can't run native linux apps and you have to rebuild your app from source if you want it to run. It won't make your apps able to use any *nix functionality like signals, ptys, etc. All it is is a slim Linux type API layer....to answer your question, I don't think anyone would want to use cygwin in an enterprise application.
Like Maz asked, why wouldn't you just run linux? What potential benefits would you ever see coming from cygwin in an enterprise environment?
The best answer to your question may be obtained from the Cygwin web site. The answers obtained there come directly from the maintainers of the Cygwin DLL and ported software.
I'm wondering if anyone has any information or speculation as to when or if there will be a native windows version/port of Node.js.
There is an ongoing effort to provide a mingw port of Node.js. Version 0.3.6+ can be build that way.
However that is still experimental and anything but ready for more than quick and dirty development. Even in case this version matures, I suppose that it will always lag behind the *nix versions, mainly due to the fact that the event loop implementations that Node uses were originally written for those systems and APIs.
The windows version may become stable for development at some point in the future, but I hardly doubt it will ever be usable for production.
July 2011 Update:
#nodejs v0.5.1 is the first to ship with an official Windows executable. We're hoping to get some good feedback.
Microsoft has officially gotten involved with joyent in making node.js work natively on windows.
If one or two Windows C++ developers would put in the effort, then they could fill the gaps in the native Windows version and produce a node.js implementation that would be usable for production.
For now, there is a working Cygwin version and I don't know of any testing that shows it to be unsuitable for production. It certainly works fine (version 0.5.0pre) for development.
Have a look at:
http://www.rafaljonca.org/d/nodejs-windows
Which is based on the work of these guys here
http://node-js.prcn.co.cc/
Both good ways of getting node on windows if you dont have cygwin. However after many heartaches I found developing Node stuff on windows easiest by just using virtualbox with the ubuntu image.
Tnx
GT
I am strictly a Windows Dev and I have wanted to mess around with Node.js for quite a while.
It looks like Microsoft, Rackspace.com and the Node.js team are planning on working together port Node.js to Windows.
So, it's not hear yet but it should be soon. w00t!
The Official Node.js Blog
The first stable version has been released: Release details here.
Be sure to check for the latest version as the link above will go out of date.
It seems to be very counter productive in that so many gems will break on windows. I have been dealing with so many mysql and ruby-mysql gem problems (seg faults occuring in the gem itself, a class called UnixSocket apparently doesn't work well on windows machines, etc etc).
I'm I just wasting my time here? Should I move onto a different scripting language?
I have very little experience with Ruby on Windows but when I was starting with Ruby I was on Windows and I got the general impression that it wasn't a Windows-native system.
So after many years of using primarily Windows, getting into Ruby prompted me to switch back to my original system, Unix, this time to Linux. Ruby did run with less hassle and running bash in its native environment was better than the just-mostly-OK Cygwin. I was happy.
Then my new employer had me switch to the Mac. Now I'm really spoiled, but really happy.
I realize this is subjective but ISTM that Linux was a lot better than windows and the Mac is a lot better than Linux. I could still run Windows in VMWare Fusion if I wanted to, but I don't. I do have some Linux VM's.
I think what I'm really trying to say is that there is a reason Ruby isn't best deployed on Windows. The kind of people who run Ruby are .. I'm trying to think of a non-pejorative word here .. not likely to be found on Windows.
So this is a turning point for you. Yes, .net is a sophisticated and well-documented environment, yes, windows has been reliable for several years now, and yes, it's a respectable system at this point. Yes, it runs Stack Overflow and some of the gurus are Windows guys. But it's just kind of a litmus test for .. darn, missing that word again ..
A lot of people run Windows because they just don't know what else to run. Linux is a good alternative if you have to buy the system yourself. And if you or your employer can afford it, the (Unix-underneath) Mac gives you everything Linux does plus the Mac-specific world.
It's time to choose... :-)
I've been developing with Ruby on Windows for several years, including building and deploying "enterprise" intranet Rails apps running against Oracle, MySQL and SQLServer on both Windows and Solaris servers.
Agreed, there are a few gems that have compiled components whose authors have not built Windows versions - that's OK, it's an open-source platform and they don't have to if they don't want to. Similarly, you're perfectly entitled to (a) ignore libraries that don't have mswin32 or mingw32 versions or (b) give something back by compiling them yourself!
As for the MySQL gem, IIRC on Windows you need the "pure Ruby" adaptor, which does not use the MySQL C API: http://github.com/tmtm/ruby-mysql or gem install ruby-mysql
I don't think you're wasting your time. I've worked with two guys who've done extensive projects on Ruby on Rails apps using Windows XP, like major, long-term projects. They seem to not mind it at all. They both worked on it using the NetBeans IDE. (It has a Ruby-specific version.)
I tried it myself when I first got started with Ruby and didn't run into a lot of errors or problems with gems, though there were some things that worked awkwardly. Usually there was a workaround.
I decided that I greatly preferred using OS X or CentOS Linux for Ruby development. But I know for a fact that working on Windows is possible.
One thing to look out for is that 90% of the Ruby community is on OS X and deploys to Linux, so you'll get more help if you're on one of those OSs.
Another thing to look out for is that the whole Ruby universe and culture is very oriented towards the Unix command line using the bash shell. All your tutorials and stuff are going to kind of assume that. They're going to have instructions like "Go to the shell and run # rake db:migrate and it will be a lot easier to follow those instructions if you have a full-featured shell with command completion, command history, etc. So if you want to work on Windows you might look into installing something like MinGW.