go to post Luca Ravazzolo · May 27, 2016 such a juicy thread! :-DThank you all for sharing all the details.
go to post Luca Ravazzolo · May 20, 2016 Hi Francisif you just want to test things, develop or even go into production without all these issues, why not give Docker containers a try?You'll never be pulling your hair again for these type of issues. You container comes installed (Dockerfile); you just spin it up and when you're done you just dispose of it.However, you'll have other hair-pulling moments for other things but by then you'll be so deep into DevOps, learning and collaboration that you won't notice it :-)Seriously, though, it's a great technology for some perfectly fitting use cases, even production if you embrace microservices and you'll be able to run a CentOS, RH, SUSE or Ubuntu container on your Debian Jessie without a glitch.HTH
go to post Luca Ravazzolo · May 17, 2016 Thanks for sharing the code Tani.IMO I think these type of monitoring should be done directly from the core Caché like from sensors in SYSMONMGR and should be provided by the system. I'm hoping to open source SAM (System Alerting and Monitoring) soon as it was demoed last year. The idea was to have a plug-&-play component to drop on all instances to monitor and an appliance that would gather those warnings and alerts.
go to post Luca Ravazzolo · Mar 25, 2016 @dmitry thanks for the pull request; great idea; all merged now.On the article you're working on: we hope you can share it once translated into English so that a wider audience can benefit from your precious work. Depending on how you spin up containers there are a couple of critical areas I'd like you to describe so that we can all learn from each other experiences here:Data VolumesContainers are ephemeral and although we can mount host volumes we need to think aheadWhat do those volume-drivers offer us? (See Rancher Convoy, Flocker & EMC Rex-Ray, etc.)How integrated are they with the underline FS or SAN? (think snapshots, replication etc.)Networkingif you have more than one node it's tough to get containers to communicate so you'll have to run an overlay network.my two favourites are (a) Weave.works, (b) project Calico and (c) flannel by the CoreOS guys. Both the above aspects are fundamental to have a production system.Let us know how you get on. Hope to see you in Phoenix.
go to post Luca Ravazzolo · Mar 24, 2016 @Dimitri, first of all, you don't have to use ccontainermain, you can script your own solution. It's just a quick-start utility. Caché ccontrol -as the name implies, is the database image control process and does many things. None of them are concerned with keeping the container alive which is not -by definition, a Linux distribution.InterSystems has been testing and running its QD testing suites against Docker containers from the 2nd quarter of 2015. Stating that we support Docker containers means that we support our platform in this environment. However, there are MANY gotchas and anybody interested in "containerizing" their app or more to the point, switching to a micro-service architecture, should approach it as a new platform.
go to post Luca Ravazzolo · Mar 17, 2016 The subject made me smile :) "service" Shouldn't we wrap the above method and expose these services via a RESTful "service" API and even encapsulate the inside system Caché ObjectScript API we have with such "service"?So the above would look something like:GET /server/system/v1/servicesand then of course you'd have all the other methods implemented...
go to post Luca Ravazzolo · Mar 17, 2016 10 years of AWS!some interesting, game changing, considerations http://www.theregister.co.uk/2016/03/17/aws_at_10/
go to post Luca Ravazzolo · Feb 26, 2016 use the calculator for Google herewhile for AWS the cost matrix is hereand you'd be right in thinking that is tough comparing apples with apples :)HTH
go to post Luca Ravazzolo · Feb 26, 2016 Hi Daniel: I had started on this and I was able to produce few variants (AD*, OM* etc.) . You can add more segments, more randomization etc. I'll have to dig out the code. It was part of a larger project...let me know
go to post Luca Ravazzolo · Feb 26, 2016 I never knew that...Now the question is about Atelier of course ;)I guess I could extend the Atelier talks to?
go to post Luca Ravazzolo · Feb 26, 2016 Ansible: a great automation tool with a low learning curve.Thank you Murray!
go to post Luca Ravazzolo · Feb 24, 2016 However, it appears that Google Compute Platform is growing on some people: Spotify just moved from AWS to Googlehttp://www.forbes.com/sites/alexkonrad/2016/02/23/spotify-is-a-big-win-f...
go to post Luca Ravazzolo · Feb 17, 2016 AWS: I find it compelling when you go beyond basics... The UI could do with a refresh but I have all the services I want and even a cloud compute micro-service engine that runs my functions as needed (Lambda)... :)
go to post Luca Ravazzolo · Feb 15, 2016 Thank you Eduard.So it sounds like you use other public cloud providers that offer more enterprise-level solutions like snapshots etc.Do you use DO (DigitalOcean) only for development & testing and other providers for production?Thank you
go to post Luca Ravazzolo · Feb 5, 2016 Thanks for sharing more info Scott. Sorry I'm late on this. Travelling... Deployment & management: This should be totally automated. There shouldn't be the need for a GUI (it slow things down). I've given my views on another thread/post you started on this exact subject. There is much to chew on these things and you might be under time pressure, however, it's an unavoidable point (automation) if we all want to be more competitive. Your last paragraph (human error) highlights why we need to embrace more automation. So to answer the original post question: I'd put my complexity in automation :) I understand what you're saying BTW; I wish you well with this workflow and the whole project. All the best