We have this issue.
We want to automate the deployment of our Continuous Delivery Build Server Tool chain using a Configuration Management tool such us Puppet, Chef or Ansible.
More precisely we have a bunch of tools (e.g. nuget, NUnit, MSBuild etc) that we use in our Continuous Delivery infrastructure. These tools are deployed to Several Build Servers. Maintaining the configuration of them is time consuming and error prone (i.e. different configuration in different Server resulting is error when building our solution using the Continuous Delivery tools).
We want to automate the maintenance of their configurations and we were thinking to use the Configuration Management tools such us Puppet, Chef or Ansible.
The question is: Are these the right tools for achieving the Configuration Management of our Build Server toolchain?
Anyone having experienced the same issue and how do you solve it?
Thanks in Advance
Alberto
Yes. All of these 3 can help you with that. Which one is better is highly opinion-based.
Yes, convergent configuration management tools such as the ones you listed are a widely used and powerful way to manage servers. The question is still very vague so that's about the best I can say.
Related
I could not find the link to download the mulesoft community edition, so I was wondering is it discontinued? if not from where I can download it?
another question is good for integration between two saas platforms?
You can still find the link to download as Mule Kernel: https://developer.mulesoft.com/download-mule-esb-runtime
Mule Kernel (without Anypoint Studio) Download if you are:
Comfortable editing XML directly
Not looking for a graphical modeling and testing environment
Have already created and tested a Mule application and you need to deploy in a separate Mule standalone runtime
I am working on a project and developing with react. I need somewhere to keep my datas. Where do you suggest? I use json-server while I'm following my course. But I'm open for any suggestion. Ofcourse it would be better if it is free at least while working on prototype.
What about mysql, nosql or postgresql? Probably I choose postgre because of it's support which comes with it's popularity
I have used Heroku to deploy production applications and hobby projects. It has a free tier, and it is fast and easy to setup. Databases are supported via addons (including Postgres), some of which have free tiers. Heroku recognizes many applications automatically, but if are using create-react-app, you need to use a buildpack for the deployment.
I am looking to implement some performance monitoring on my ROS server.
I'm running Ubuntu 16.04 running on a VPS. Unfortunately the VPS has no performance statistics. So I'm looking to install a tool or connect to a server that will help me understand the load the server is experiencing.
I'm specifically considering deploying Prometheus. Although it looks like quiet an effort to get it running I figure it's the most comprehensive tool available.
Before I start I want to be sure that this is achievable and it will not impact the ROS performance/capability.
Has anyone implemented performance monitoring? Did you use a particular service or tool and did you use a great document/page to help you install and configure?
Closed. See my comment, in the end I used Datadog, which appears to be very good.
is there a way to directly modify a package in the ssis catalog?
What I'm trying to achieve is "source control" building something like a main repository for me and all other developers. We need more visibility on the packages being built. i.e., when you pull into your own machines and not keep the development on the server, we don’t see what is being done.
You probably want to use version control such as git or Team Foundation Server / Visual Studio Team Services. Using the deployed package as version control is bad practice and might risk breaking it or making it unrecoverable.
Use a VCS, git and VSTS are free.
We want to have scalable Reporting services. And we need to install Custom Rendering Extensions on this scalable Reporting Services. This is the main requirement for us. SQL Azure Reporting doesn't suite the requirements, because it is impossible to extend this service with custom rendering extension. We had an idea to install Reporting Services on each instance separated from SQL Azure and Azure Reporting, but Rendering Extensibility is not available in free editions of SQL Server and it costs too much to use paid edition. The database of these reporting services instances will be stored in SQL Azure and we will be able to leverage scalable Reporting Services tool with the required rendering extension. The problem is price, complexity and no benefits from SQL Azure Reporting. So, we got stuck with Microsoft clouds. And don't see any reasonable solution with Microsoft clouds.
So we considered Reporting Services on EC2 as they have special cloud license. And we are not quite sure whether it is possible to achieve what we need or not.
We've found that it's possible to install SQL Server2008R2 on EC2 so that the data of the database will be stored in EBS which is available to all the instances. So we have scalable Reporting Services in that case.
The question is lying in the Amazon Virtual Images:
We suppose that we need to install predefined configuration with Windows OS and SQL Server 2008R2 and we wonder if it (1) includes Reporting Services, (2)is it possible to install some more software on this predefined virtual machine (rendering extension), (3)is it possible to organize such scalable Reporting Services with Custom Rendering extensions and to leverage load balancing and etc.?
You don't have to use the AWS provided SQL Server 2008 R2 AMI if you don't want to.
If you bring your own licenses, you could go with a base EC2 install, and then install whatever software you want over the top of it.
ie - install the Windows AMI, and then run the SQL Server installation of your choice. The second step then is to install any additional extensions you require.
I would also recommend that once you complete the installation that you create an AMI of it so that you can repeat the installation at a later date.